Remote Task Manager Object (JOBQ)
Remote Task Manager objects monitor and control external processes (that is, non-Automation Engine operations).
Object Definition
Object class: Executable object
Object type/Short name: JOBQ
Default Object Templates (and subcategories):
-
PeopleSoft processes: PS > PROCESSREQUEST
-
All SAP jobs: R3 > ALLJOBS
-
Especially intercepted SAP: R3 > INTERCEPTEDJOBS
-
Java: R3 > JAVAJOBS
-
SAP process chains: PROCESSCHAINS
This topic provides information on the following:
- Background
- Tracking External PeopleSoft Processes
- Important considerations for SAP
- Adding Processing Steps to External Operations
See also Defining Remote Task Manager Objects.
This object allows you to display, start, cancel, intercept and monitor external operations, that is, operations that run on applications outside the Automation Engine.
In a Remote Task Manager object you collect the filter criteria that identify the external tasks that you want to control. The external processes that comply with those criteria are then displayed on the Tasks window of the Process Monitoring perspective as sub-tasks of the Remote Task Manager object (the hierarchical view must be activated for this purpose). Their object type is JOBD. For example:
As JOBQ objects deal exclusively with external transactions, they are no longer displayed in the Process Monitoring as soon as they have ended. Only canceled child tasks remain visible and can be deactivated.
Tracking External PeopleSoft Processes
For the Remote Task Manager to be able to control and keep track of processes that are independent of the Automation Engine, the following prerequisites must be met:
- The connection between the Automation Engine and the target PeopleSoft system is up and running.
-
A Login object is available that provides the necessary PeopleSoft credentials (username and password).
This Login object is specified in the
APPLICATION_LOGIN
key available in the UC_HOSTCHAR_DEFAULT static variable contains. Its default value isERP_LOGIN
.Whenever the Remote Task Manager requests data, this Login object is used in the background.
The UC_HOSTCHAR_DEFAULT static variable is supplied with client 0.
See UC_HOSTCHAR_DEFAULT - Host Characteristics.
Important Considerations for SAP
Defining the filter criteria is very intuitive. However, take the following into account when doing it:
- By default, no filter criteria are set and the AE submits wildcards in the direction of SAP. Therefore, submitting a JOBQ without modifying a single filter criterion might result in many jobs that are returned.
- Modifications made in the JOBQ object definition while it is running do not affect its results.
- The Java scheduler is case-sensitive. Keep this in mind when entering the filter criteria.
- In JOBQ objects with type PS or JAVAJOBS wildcard characters cannot be used for specifying filter criteria.
- For SAP-related jobs, however, you can use "*" and "?" to specify the following filter values:
- All SAP jobs (R3>ALLJOBS): Job name, Job count, Job group
- Intercepted jobs (R3>INTERCEPTEDJOBS): Job name, Job count, User Name (job initiator), Scheduled start time
- Processed chains (R3>PROCESSCHAINS)
- SAP jobs can be started via JOBQ objects if the Start SAP Jobs checkbox is activated in the Attributes page of the JOBQ definition, see Attributes Page.
- In JOBQ objects with type R3>PROCESSCHAINS the options Filtering and Start SAP Jobs in the Attributes are not available because they are useless for these tasks.
- JOBQ objects for CCMS jobs allows you to filter jobs that are NOT in the Scheduled status. For technical reasons, they cannot be started automatically, since they run within SAP.
- In the case of JOBQ objects for R3>PROCESSCHAINS, when you select the option to transfer job reports to the Automation Engine database, either all reports or no reports are transferred. All reports refers to both the chain and its steps.
- JOBQ objects cannot start intercepted child jobs without parents if hierarchical filtering has been specified. To be able to do so, make sure that you have activated Flat in the Attributes page.
Adding Processing Steps to External Operations
In the Child Post Process page you can add a script to be processed after the tasks returned by the JOBQ object have ended.
See also: