Remote Task Manager (JOBQ)

{"URL":["*.*/awa/pa_view_JOBQ_PS","*.*/awa/pa_view_JOBQ_R3"],"heroDescriptionIdentifier":"ice_JOBQIntro","customCards":[{"id":"ice_DefJOBQ","title":"Defining JOBQ Objects","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/Objects/obj_RemoteTaskManager_Defining.htm","languages":["en-us"]},{"id":"ice_BestPracticesJOBQ","title":"Best Practices","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/Objects/obj_remote_task_manager.htm","languages":["en-us"]},{"id":"ice_ConsiderationsJOBQ","title":"Important Considerations","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/Objects/obj_remote_task_manager.htm","languages":["en-us"]},{"id":"ice_ExecuteJOBQ","title":"Executing and Working with JOBQ Tasks","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/Objects/obj_remote_task_manager_Execution.htm","languages":["en-us"]},{"id":"ice_JOBQAttributes","title":"Remote Task Manager Attributes","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/Objects/obj_remote_task_manager_attributes.htm","languages":["en-us"]},{"id":"ice_monitoring_restarting_peoplesoft","title":"Monitoring and Restarting External Tasks","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/ProcMonitoring/PM_ExternalTasks.htm","languages":["en-us"]},{"id":"ice_Object_AnalyzeLastExecution","title":"Analyzing the Last Execution","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/Objects/obj_WkgWithAnalyzeExecData.htm","languages":["en-us"]},{"id":"ice_working_with_objects","title":"Working with Objects","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/Objects/obj_WorkingWithOverview.htm","languages":["en-us"]},{"id":"ice_AWIs_CommonFunctions","title":"Common Functions","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/_Common/CommonFunctions/CF_OverviewOfChapter.htm","languages":["en-us"]},{"id":"ice_UnderstandingPA","title":"Understanding the Process Assembly Perspective","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/AWA/Objects/ProcessAssembly.htm","languages":["en-us"]},{"id":"ice_Overview_AWI","title":"Understanding the User Interface","type":"customize","url":"https://docs.automic.com/documentation/webhelp/english/ALL/components/DOCU/*.*/Automic%20Automation%20Guides/Content/_Common/GettingStarted/GS_OverviewAWI.htm","languages":["en-us"]}]}

Remote Task Manager (JOBQ) objects manage and monitor external operations, that is, processes that do not run in Automic Automation but on SAP or PeopleSoft. You can think of them as queues where you define the filter criteria that identify the external SAP and PeopleSoft jobs that you want to monitor from Automic Automation. When the external jobs that meet those criteria run, they are displayed in the Process Monitoring perspective as children of the JOBQ object and their object type is JOBD.

Note: In the case of SAP Process Chains, the SAP Agent retrieves all the process chains that comply with the specified filter criteria. If the filters apply to only the child processes of a process chain, only the child processes are displayed. If the process chain parent and the children comply with the criteria, their structure is also displayed in the Tasks list.

JOBQ objects deal exclusively with external transactions. This is why they are no longer displayed in the Process Monitoring once they have successfully ended. Only canceled/aborted child tasks remain visible and can be deactivated.

Automic Automation provides the following templates to create Remote Task Manager Jobs:

PS (PeopleSoft)
- PROCESSREQUEST
R3 (SAP)
- ALLJOBS for all SAP jobs
- INTERCEPTEDJOBS for especially intercepted SAP jobs
- JAVAJOBS for SAP Java jobs
- PROCESSCHAINS for SAP process chains

Object class: Executable object

Object type/Short name: JOBQ

This page includes the following:

Best Practices for JOBQ Objects

Consider the following when configuring a JOBQ object:

Automic Automation ensures that an external operation is included in only one JOBQ object. Avoid defining overlapping filter criteria when you set them in active JOBQ objects.
In PeopleSoft, you can reset the assignment of process-request instance numbers, for example from 200000 to 100000. This is an unusual procedure that clears the PSPRCSRQST table to avoid duplicate keys. You must stop and reactivate the JOBQ object when the instance number has been reset. When you stop it, make sure that there are no PeopleSoft processes in Process Monitoring perspective before reactivating it.
Take the following into account with JOBQ objects for SAP Process Chains:
Filtering for active SAP jobs can render incomplete results because Automic Automation polls the SAP system at specific intervals. The JOBQ object displays only jobs that are active at this point in time. If a job starts within an interval and ends immediately afterward, it is not displayed as child of the JOBQ task.

Important Considerations for JOBQ Objects

Defining the filter criteria that determines the jobs that the JOBQ object will monitor is very intuitive. However, take the following into account when doing it:

JOBQ Jobs and wildcard characters
- By default, no filter criteria are set and Automic Automation submits wildcards to SAP. This means that if you do not set any filter criteria, the JOBQ will return many jobs.
- You cannot use wildcard characters in JOBQ objects with type PS or JAVAJOBS.
- However, you can use "*" and "?" in SAP JOBQ objects 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)
If you modify a JOBQ definition that is already running, these changes do not affect its current results.
The Java scheduler is case-sensitive. Keep this in mind when entering the filter criteria.
To be able to start SAP jobs through a JOBQ object, you must activate the Start SAP Jobs option on the JOBQ's Attributes page page, Runtime Parameters section, see Defining the Attributes Page.
JOBQ objects with type R3>PROCESSCHAINS do not have the Filtering and Start SAP Jobs options on the Attributes page because they are useless for these tasks.
Also for JOBQ objects for R3>PROCESSCHAINS, if you select the Job Report to AE option on the Attributes page 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 for CCMS jobs let you filter jobs that are NOT in Scheduled status. For technical reasons, they cannot be started automatically, since they run within SAP.
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.

This section includes the following pages: