Use this page to create a new Transaction Manager. Transaction Managers handle synchronous requests from client machines.
Navigation: Site Map > Transaction Managers (under Application Services) > (B) Create New or (B) Edit
Enabled
Check this box if this transaction manager is enabled.
Manager
The name of the transaction manager.
Short Name
The short name for your transaction manager.
Application
The application associated with the transaction manager.
The combination of an application and the short name you specify here uniquely defines the transaction manager.
Program Library
Select a library of immediate transaction programs to make available to your manager. Your manager can only run immediate transaction programs that are registered in the selected program library. Transaction managers can run only those immediate transaction programs listed in their program library. They can also run transaction programs that use any other type of transaction program executable.
Use the Work Shifts section to assign work shifts to your manager. A work shift defines the dates and times the manager is enabled, as well as the number of processes the manager can start running during the work shift.
To add a work shift, use the Add from Available Shifts button.
For each work shift listed, the following is displayed:
Sleep Seconds
The sleep time for a transaction manager determines how often a manager will check to see if it should shut down.
Suggestion: Set the sleep time to be very brief during periods when the number of requests submitted is expected to be high.
Processes
The number of operating system processes you want your work shift to run simultaneously. Each process can run a concurrent request.
For example, if a work shift is defined with three (3) target processes, the manager can run up to three requests simultaneously.
If you are operating in a parallel concurrent processing environment and you want your manager to operate on a specific node, select the name of the node.
The primary node, if available, is the node your concurrent manager operates on. If the primary node or the database instance on it goes down, your concurrent manager migrates to its secondary node. Your concurrent manager migrates back to its primary node when that node becomes available.
Nodes must be previously registered with Oracle Applications, using the Nodes form in Oracle Applications.