Executing Remote Task Manager Objects
You can activate several Remote Task Manager objects that use the same agent. However, overlaps may occur because of the filter criteria that have been specified.
This topic provides information on the following:
- Recommendations for filtering the tasks
- Historical data: Executions and Reports
- Controlling SAP queues
- Stopping/Starting the Remote Task Manager
- Canceling the Remote Task Manager
- Ending the Remote Task Manager
The Automation Engine ensures that an external operation is included in only one Remote Task Manager object. Automic recommends avoiding that filter criteria overlap when you set them in active Remote Task Manager objects.
The following recommendations apply when setting the filter for PeopleSoft and SAP Process Chains:
-
In PeopleSoft, the assignment of process-request instance numbers can be reset, for example from 200000 to 100000. This is an unusual procedure with the effect that the PSPRCSRQST table is cleared. Otherwise, duplicate keys would occur. The Remote Task Manager object must be ended and re-activated when the instance number has been reset. There must be no PeopleSoft processes in the Tasks window of the Process Monitoring perspective, because otherwise queue items would be missing.
-
The SAP agent retrieves all the process chains that comply with the specified filter criteria. If the filters only apply to the child processes of a process chain, only the child processes will be displayed. If the process chain parent and the child(ren) comply with the criteria, their structure will also be displayed in the Tasks window (the hierarchical view must be activated for this purpose).
Process chains that have ended successfully are automatically removed from the Tasks window. Aborted chains remain in it as subordinate tasks of the Remote Task Manager object.
You can also restart process chains from the Tasks window.
Please take the following into account when working with JOBQ objects for SAP process chains:
- The Remote Task Manager object cannot identify process chains that were activated by an Automation Enginejob and restarted in SAP.
- Cold starting the SAP agent can have the effect that the processes that are shown in the Remote Task Manager object are lost.
- Whether reports are available depends on what you have specified in Store to, whether Database or File, on the agent-specific definition page.
Note that filtering for active SAP jobs can supply incomplete results. Jobs are matched with the SAP system through polling (in intervals). The Remote Task Manager object displays only jobs that are active at this point in time. If a job is started within a particular interval and ends immediately afterwards, it is not shown in the Remote Task Manager object.
You can access historical data of non-AE operations via the Remote Task Manager's execution data, see Execution Data Overview.
The corresponding report is available when the Store to: Databas checkbox has been activated on the agent-specific page.
The Remote Task Manager object does not only monitor but it can also activate scheduled SAP jobs when the attribute Start SAP jobs is set. Additionally, the maximum number of operations running in parallel can be also controlled. In this case, the Remote Task Manager object acts similarly to a Group Object (JOBG).
Remote Task Manager objects can be intercepted via the Stop command from the Tasks window. Doing so has the effect that:
- The Remote Task Manager object does not accept new operations that meet the specified filter criteria.
- Running operations are not stopped.
- Child Post Processes of operations that end during a Stop are processed.
- Operations do not start anymore if the attribute Start SAP jobs has been activated.
The Go command in the context menu cancels the Stop.
Canceling the Remote Task Manager object has the following consequences:
| If | then... |
|---|---|
| The attribute Start SAP jobs is set |
Operations that have not yet started are also canceled Operations that have already started continue |
| The attribute Start SAP jobs is not set | All operations are canceled |
The same applies as for Remote Task Manager objects that are canceled (except that it ends on status "ENDED_OK").
Note that jobs are only filtered once. The preliminary ending of a Remote Task Manager object which also starts jobs can trigger the start of non-assigned jobs. These jobs are not filtered when the Remote Task Manager is reactivated and, therefore, they cannot be controlled by the Automation Engine.
See also: