Show TOC

Background documentationIntegration Engine Locate this document in the navigation structure

 

Caution Caution

SAP NetWeaver Administrator for PI and all monitoring tools it includes are not supported for use in production scenarios. We recommend to use Runtime Workbench for PI monitoring in production scenarios. The information provided below is only for reference.

For more information, see SAP notes 1446507 and 1247043.

End of the caution.

The following cache object of the Integration Engine correspond to those of the Central and Non-Central Adapter Engines:

More information: Central and Non-Central Adapter Engines

  • Partners

  • Communication Component

  • Communication channel

    However no adapter modules are displayed for this.

  • Sender agreement

  • Receiver Agreement

The following cache objects are specifically for the Integration Engine:

  • Integration process

    This searches for integration processes. You can use the following selection criteria from the Integration Directory in advanced mode:

    • Partners

    • Integration process

    The detail screen contains information about the selected integration process, and the XML code of the graphical representation of the process.

  • Process Component

    To search for process components, you must enter an Integration Directory name.

    The names of the directory and repository, and the repository namespace are displayed in the detail view.

  • Receiver Determination

    When searching for receiver determinations, you use the same selection criteria as those used to search for receiver agreements.

    The information on the detail screen varies depending on whether you select a standard receiver determination or an enhanced receiver determination.

    • In a standard receiver determination, a list of the configured receivers is displayed.

    • In the case of an enhanced receiver determination, a list of operation mappings (including parameters) for dynamic receiver determination is displayed instead of a receiver list.

    The action that must be executed if no receiver is found is always displayed. Where available, a table of the namespace prefixes is also displayed.

  • Interface Determination

    When searching for interface determinations, you use the same selection criteria as those used to search for receiver determinations.

    The detail screen displays a list of the configured inbound interfaces. Where available, a table of the namespace prefixes is also displayed.

    You can display the parameters and operation mapping for each interface and the parameters for each operation mapping, as well as the corresponding request, response and fault programs.

  • Operation mapping

    When searching for mapping objects, you can use the following selection criteria:

    • Name

    • Namespace

    • Software Component Version

      Here you can either enter the name of the (complete) GUID of a software component version.

    A list of the mapping objects found is displayed.

    The detail screen displays a list of all outbound and inbound interfaces involved, the parameters of the mapping object, as well as the corresponding request, response, and fault programs.

    To display the binding for the parameter of a mapping program, select the program from the list.

  • Alert Category

    When searching for alert categories, you can use the following selection criteria:

    • Name

    • Namespace

    • Software Component Version

    A list of all the alert categories found is displayed, including the GUID of the software component.

    The detail screen contains information about the alert container.