Defining Remote Task Manager Objects

The steps for defining Remote Task Manager (JOBQ) objects are the same as for any other object.

1. In the Process Assembly perspective click Add Object. On the Add Object dialog, select Remote Task Manager > <sub-type>. For information on how to add objects, see Adding Objects.

   A Remote Task Manager object definition is made up of the following pages:

   • Common pages that are always available, no matter what type of object you are defining:

     • Defining the General Page

     • Defining the Version Management Page

     • Defining the Documentation Page

   • Pages that are always available for executable objects

     • Defining the Process Pages in Jobs

     • Defining the Attributes Page

     • Defining the Variables Page

     • Defining the Prompt Sets Page

     • Defining the Rollback Page

     • Registering External Output Files

   • The Remote Task Manager page described here.

   Note: You can also create Remote Task Manager objects directly from the combo boxes that serve to select objects, see Using AWI Combo Boxes.

2. On the Object Name dialog enter the name of the new object. Choose it carefully. For more information, see Best Practices: Naming Conventions for Objects.

3. Click OK to open the object definition pages.

4. On the JOBQ specific page, do the following:

   1. The first section on this page is specific to the target system and it is called accordingly (SAP All Jobs, SAP Intercepted Jobs, SAP Java Scheduler Jobs, SAP Process Chains, PeopleSoft Processes). Here you specify the filter criteria that will identify the external jobs that this JOBQ object will manage and monitor. Depending on the type of target system, the labels on this page differ but the mechanics of defining the filter are always the same:

      1. The first dropdown list contains the attributes of the external job that you want to filter for. After you have added a list entry as filter criterion, it is removed from the dropdown list to ensure that your filters return unique results.

      2. Depending on your selection, the search operator changes dynamically to allow you to enter the appropriate value.
      3. Enter or select the value in the field on the right hand side.
      4. Click Add to apply this filter criterion. Continue collecting the filter criteria you need.
      5. Switch to the Child Post Process page if you want to define an additional script that should be processed after the child tasks are finished. The script is processed for each child task.

   2. (Relevant for ALLJOBS, INTERCEPTEDJOBS and PROCESSCHAINS)

      In the SAP Connection section you can select the R3 Connection object that contains the login data and credentials that the Agent needs to connect to the SAP target system on which the Job will be executed.

      Important! Depending on how you system is configured, your administrator can have already assigned a Connection object to the SAP Agent that will execute the Job. If this is the case, if you leave this field empty, the Connection object assigned to the Agent will be used. If, on the other hand, you select a different Connection object here, your Job definition has priority and the object you select here is used.

      The table below indicates what happens depending on where the Connection object is assigned:

      Connection object assigned to Agent	Connection object assigned to Job	Result
      YES	NO	The Connection object assigned to the Agent is used by default.
      YES	YES	The Connection object assigned to the Job is used.
      NO	YES	The Connection object assigned to the Job is used.
      NO	NO	The Job fails because it cannot connect to the target system.

5. On the Attributes page , specify settings that control the execution of the SAP and PeopleSoft Jobs. For example, you allocate them resources and define the number of simultaneous executions that you allow. See Defining the Attributes Page.

6. Optionally, on the Child Post Process page enter the script that you want to be processed after the child tasks have finished. The script is processed for each child task. For more information, see Defining the Process Pages in Jobs.

7. Save your changes.