Overview and Prerequisites

Use

In order to successfully configure SAP Process Integration, you need to perform additional post-installation activities to configure the involved Application Server ABAP and Application Server Java. Which particular activities are relevant depends on the use case and technical prerequisites of your installation.

You can find the relevant activities and links to the corresponding configuration documentation in SAP Solution Manager (transaction SOLAR_LIBRARY ) under Start of the navigation pathSolutions/Applications Next navigation step Basic Configuration Next navigation step Configuration Structures Next navigation step SAP NetWeaver <Release>End of the navigation path. Choose the configuration structures Application Server ABAP and Application Server Java.

The configuration of Process Integration comprises 3 products:

  1. Process Integration (PI) Dual Stack

  2. Advanced Adapter Engine Extended (AEX)

  3. Process Orchestration (PI-CP)

    To configure Process Orchestration (PI-CP) you need the Java role Administrator.

Installation Check

Before you start to configure a product, you first have to check whether it was installed successfully. To check whether installation was successful, proceed as follows:

  • Start the SAP NetWeaver Administrator.

  • Choose Start of the navigation pathConfiguration Next navigation step Scenarios Next navigation step Configuration WizardEnd of the navigation path. The Configuration Wizard: Overview screen appears.

  • Choose Show all Functional Units. A new window appears.

I. Process Integration (PI) Dual Stack

  1. Process Integration (PI) Dual Stack was successfully installed if the following functional units are displayed:

    Functional Unit

    Usage Type

    CM Services (Change Management Services)

    Application Server Java

    Java Data Archiving

    Application Server Java Extensions

    Java Foundation

    Application Server Java

    SAP Process Integration (PI)

    Application Server Java Extended or Process Integration

    Services Registry

    Application Server Java

    System Landscape Directory

    Application Server Java

    XML Data Archiving Service

    Application Server Java Extensions

  2. To configure Process Integration (PI) Dual Stack, select the SAP NetWeaver Process Integration (PI) functional unit. As a result, any additional functional units that are needed will also be selected according to the following table (if they do not already have the status Enabled):

    Functional Unit

    Usage Type

    Status

    Java Foundation

    Application Server Java

    Disabled

    SAP Process Integration (PI)

    Application Server Java Extended or Process Integration

    Disabled

    System Landscape Directory

    Application Server Java

    Disabled

  3. To start the configuration, choose Enable automatically.

  4. To check whether the configuration was successful, return to the Configuration Wizard: Overview screen and choose History of Executed Configuration Tasks.

  5. Select your Session ID and choose View Log (in case of errors, download the log and attach it to an error message). The navigation tree on the left side of the screen shows the successful configuration of the following entries:

    • Initial setup of functional unit SLD (EDEN)

    • Initial setup of functional unit Java Foundation (LM)

    • PI Configuration (LM)

  6. As a result of the successful configuration, all the functional units have the status Enabled according to the following table:

    Functional Unit

    Usage Type

    Status

    Java Foundation

    Application Server Java

    Enabled

    SAP Process Integration (PI)

    Application Server Java Extended or Process Integration

    Enabled

    System Landscape Directory

    Application Server Java

    Enabled

    If you want to configure Process Integration (PI) Dual Stack manually, see Configuring Process Integration (PI) Dual-Stack .

II. Advanced Adapter Engine Extended (AEX)

See Configuring Advanced Adapter Engine Extended (PI-AEX)

  1. Advanced Adapter Engine Extended (AEX) was successfully installed if the following functional units are displayed:

    Functional Unit

    Usage Type

    Status

    Advanced Adapter Engine Extended (AEX)

    Advanced Adapter Engine Extended or Process Integration

    Disabled

    CM Services (Change Management Services)

    Application Server Java

    Disabled

    Java Data Archiving

    Application Server Java Extensions

    Disabled

    Java Foundation

    Application Server Java

    Disabled

    Services Registry

    Application Server Java

    Disabled

    System Landscape Directory

    Application Server Java

    Disabled

    XML Data Archiving Service

    Application Server Java Extensions

    Disabled

  2. To configure Advanced Adapter Engine Extended (AEX), select the Advanced Adapter Engine Extended (AEX) functional unit.

  3. To start the configuration, choose Enable automatically.

  4. To check whether the configuration was successful, return to the Configuration Wizard: Overview screen and choose History of Executed Configuration Tasks.

  5. Select your Session ID and choose View Log (in case of errors, download the log and attach it to an error message). The navigation tree on the left side of the screen shows the successful configuration of PI Advanced Adapter Engine Extended initial setup (LM).

  6. As a result of the successful configuration the Advanced Adapter Engine Extended (AEX) functional unit has the status Enabled.

    If you want to configure Process Integration (PI) Dual Stack manually, see Manual Configuration for Advanced Adapter Engine Extended.

III. Process Orchestration (PI-CP)

  1. Process Orchestration (PI-CP) was successfully installed if the following functional units are displayed:

    Functional Unit

    Usage Type

    Advanced Adapter Engine Extended (AEX)

    Advanced Adapter Engine Extended

    CM Services (Change Management Services)

    Application Server Java

    Composite Application Framework Runtime

    Composite Application Framework

    Composition Environment Platform

    Composition Environment Platform

    ECM Integration core

    Composition Environment Platform

    ECM Integration Services

    Composition Environment Platform

    Java Data Archiving

    Application Server Java Extensions

    Java Foundation

    Application Server Java

    Portal

    EP Core - Application Portal or Composition Environment Platform

    Process Integration and Orchestration Package

    No usage type

    Process Server

    Business Process Management and Business Rules Management

    Rules Server

    Business Process Management and Business Rules Management

    Services Registry

    Application Server Java

    System Landscape Directory

    Application Server Java

    Universal Worklist

    EP Core - Application Portal or Composition Environment Platform

    Visual Composer

    Composition Environment Platform

    XML Data Archiving Service

    Application Server Java Extensions

  2. To configure Process Orchestration (PI-CP), select the Process Integration and Orchestration Package functional unit. As a result, any additional functional units that are needed will also be selected according to the following table (if they do not already have the status Enabled):

    Functional Unit

    Usage Type

    Status

    Advanced Adapter Engine Extended (AEX)

    Advanced Adapter Engine Extended

    Disabled

    Composite Application Framework Runtime

    Composite Application Framework

    Disabled

    Composition Environment Platform

    Composition Environment Platform

    Disabled

    Java Foundation

    Application Server Java

    Disabled

    Process Integration and Orchestration Package

    No usage type

    Disabled

    Process Server

    Business Process Management and Business Rules Management

    Disabled

    Rules Server

    Business Process Management and Business Rules Management

    Disabled

    System Landscape Directory

    Application Server Java

    Disabled

  3. To start the configuration, choose Enable automatically.

  4. To check whether the configuration was successful, return to the Configuration Wizard: Overview screen and choose History of Executed Configuration Tasks.

  5. Select your Session ID and choose View Log (in case of errors, download the log and attach it to an error message). The navigation tree on the left side of the screen shows the successful configuration of the following entries:

    • Initial setup of functional unit SLD (EDEN)

    • Initial setup of functional unit Java Foundation (LM)

    • PI Advanced Adapter Engine Extended initial setup (LM)

    • BPM All Configuration Tasks Combined (LM)

    • Process Integration Compact Edition initial setup (LM)

  6. As a result of the successful configuration, all the functional units have the status Enabled according to the following table:

    Functional Unit

    Usage Type

    Status

    Advanced Adapter Engine Extended (AEX)

    Advanced Adapter Engine Extended

    Enabled

    Composite Application Framework Runtime

    Composite Application Framework

    Enabled

    Composition Environment Platform

    Composition Environment Platform

    Enabled

    Java Foundation

    Application Server Java

    Enabled

    Process Integration and Orchestration Package

    No usage type

    Enabled

    Process Server

    Business Process Management and Business Rules Management

    Enabled

    Rules Server

    Business Process Management and Business Rules Management

    Enabled

    System Landscape Directory

    Application Server Java

    Enabled