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:

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

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

  3. Click OK to open the object definition pages.

  4. On the JOBQ specific age 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.
  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.

  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 Process Pages.

  7. Save your changes.

See also: