You can activate several RemoteTaskManagers that use the same agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host. However, overlaps may occur because of the filter criteria that have been specified. AE ensures that a non-AE operation is only shown in one RemoteTaskManagerIt monitors and controls external Jobs that were not started by the Automation Engine (AE). An AE object type. [Formerly called "QueueManager."]. Automic recommends avoiding that filter criteria overlap when you set them in active RemoteTaskManagers.
In PeopleSoft, the assignment of process-request instance numbers can be reset (e.g. from 200000 to 100000). This is an unusual procedure that has the effect that the PSPRCSRQST table is cleared. Otherwise, the problem of "duplicate keys" would occur. The RemoteTaskManager must be ended and re-activated when the instance number has been reset. There must be no PeopleSoft processes in the AE activitiesDeployment-related activities, because otherwise queueA particular Automation Engine (AE) object type. In AE, a queue determines the maximum number of concurrent tasks, their priorities and the order in which tasks should be executed. In ARA, queues are containers for workflow executions that should be executed at a certain time one after another. items would be missing.
The Activity Window displays external procedures that comply with the filter criteria as subtasks of the RemoteTaskManager (the hierarchical view must be activated for this purpose). This does not apply for jobs that have been started by AE, because the RemoteTaskManager exclusively deals with non-AE operations. When a non-AE operation ends, it is no longer displayed in the Activity Window.
Canceled childA subordinate task (such as a task that runs in a workflow). tasks always remain in the Activity Window and can be deactivated there.
Note that filtering for active SAP jobs can supply incomplete results. Jobs are matched with the SAP system through polling (in intervals). The RemoteTaskManager only displays jobs that are active at this point in time. If a jobAn Automation Engine object type for a process that runs on a target system. is started within a particular interval and ends immediately afterwards, it is not shown in the RemoteTaskManager.
You can also access the statisticsThis is a list of a task's previous runs. of non-AE operations via the RemoteTaskManager's statistics. The corresponding reportA report provides more detailed information about a task's execution or a component. is available when the setting "Transfer job reports to DB" has been activated in the Attributes tab.
SAP Process chains
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 parentThere are different ways of activating objects. The originator of an activation is referred to as the superordinate task (parent). See also: Child; Children and the child(ren) comply with the criteria, their structure will also be displayed in the Activity Window (the hierarchical view must be activated for this purpose).
Process chains that have ended successfully are automatically removed from the Activity Window. Aborted chains remain in it as subordinate tasks of the RemoteTaskManager.
You can also restartA restart refers to the repetition of an object's execution. This action differs from a new start in some parts. process chains. In the Activity Window's context menu, you can select the menu item "Modify taskAn executable object that is running. Tasks are also referred to as activities. - Restart Remote" for this purpose.
The RemoteTaskManager cannnot identify process chains that were activated by an AE job and restarted in SAP.
Note that cold starting the SAP agent can have the effect that the processes that are shown in the RemoteTaskManager are lost.
Whether reports are available depends on what you have specified in the setting "Transfer job reports to DB" (Attributestab).
The RemoteTaskManager does not only monitor but can also activate scheduled SAP jobs when the attribute "Start jobs" is set. Additionally, the maximum number of operations running parallel can also be controlled. The RemoteTaskManager then acts in the same way that a Group objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task acts.
RemoteTaskManager objects can be intercepted using the context menu command "Stop". Doing so has the effect that:
The "Go" command in the context menu cancels the "Stop" condition.
Canceling the RemoteTaskManager object has the following consequences:
The attribute "Start jobs" is set:
The attribute "Start jobs" is not set:
The same procedure applies as for RemoteTaskManagers that are canceled (except that it ends on statusThis represents the condition of a task (such as active, blocked, generating). "ENDED_OK").
Note that jobs are only filtered once. The preliminary ending of a RemoteTaskManager which also starts jobs can trigger the start of non-assigned jobs. These jobs are not filtered when the RemoteTaskManager is reactivated and they can therefore not be controlled by AE.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |