Show TOC

Performing Background ProcessingLocate this document in the navigation structure

Prerequisites

Context

You can schedule the background processing of routine tasks on the Advanced Adapter Engine in the background job monitor. You can use this monitor to do the following:

  • Manage archiving, deleting, restarting, and recovering jobs for PI messages. For more information about what these jobs are used for, see Background Job Types .

  • Display information about the jobs of the Adapter Framework. These jobs are started by the system, you cannot create and administrate such jobs. For more information, see Adapter Framework .

Procedure


  1. Access the background processing monitor in one of the following ways:

    • Open a browser and go to http://[host]:[port]/pimon to access the Process Integration tools. Then choose Start of the navigation path Monitoring Next navigation step Adapet Engine Next navigation step Background Job Monitor End of the navigation path or Start of the navigation path Configuration and Administration Next navigation step Adapter Engine Next navigation step Background Processing End of the navigation path.

    • Open a browser and go to http://[host]:[port]/nwa to access SAP NetWeaver Administrator. Then choose Start of the navigation path SOA Next navigation step Monitoring Next navigation step PI Background Processing End of the navigation path.

  2. To create, modify, execute, or delete background jobs for messages choose the Adapter Engine Jobs tab.

  3. To view the jobs of the Adapter Framework choose the Adapter Framework Scheduler Jobs tab.

Results

The system displays the background jobs on the Adapter Engine Jobs tab. For more information about editing these jobs, see Managing Jobs , Scheduling Jobs , and Defining Rules .

The system displays the following types of Adapter Framework jobs on the Adapter Framework Scheduler Jobs tab:

  • A labeled job is submitted with a unique job name, and it is synchronized among those nodes where this job is submitted. The labeled job is executed only on one of the nodes where it is submitted, and it can migrate to one of the other nodes after some time.

  • A guest job is submitted without a job name. It is executed only on those nodes where it is submitted, and would not migrate to another node. Some guest jobs can be submitted on every node, and other can be submitted on one particular node where this activity is supposed to be executed.