Executing Remote Task Manager Objects

Remote Task Manager objects monitor external processes that comply with certain filter criteria. When Jobs are displayed in the Process Monitoring perspective as children of the Remote Task Manager object, their object type is JOBD. The hierarchical view must be activated for this purpose.

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 page includes the following:

Execution Data and Reports

You can access historical data of non-AE operations via the Remote Task Manager's execution data, see Execution Data.

The corresponding report is available when the Store to: Database checkbox has been activated on the agent-specific page.

Controlling the Queue

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 Job Groups (JOBG).

Stop/Go

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

Canceling the Remote Task Manager object has the following consequences:

If the Start SAP jobs is set operations that have not yet started are also canceled. Operations that have already started continue.

If the Start SAP jobs is not set, all operations are canceled.

Ending

The same applies as for Remote Task Manager objects that are canceled (except that it ends on status "ENDED_OK").

Note: 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.