Configuring Message Processing from PI to BPM

Use

You use a message start event or an intermediate message event in your BPM process to process messages from the Advanced Adapter Engine Extended (AEX) to a BPM process.

In AEX, you configure a communication component representing the BPM process and a communication channel using a receiver SOAP adapter with message protocol XI 3.0. Configure an Integrated Configuration object using the communication component and the communication channel. An inbound service interface defined in the ES Repository determines the structure of messages that are exchanged.

The following procedure only describes steps in the BPM process and objects in AEX that are necessary for message exchange. You have to add other steps of your process. In AEX, add information about the message sender and for example mapping and routing definitions.

Prerequisites

  • You have designed an inbound service interface in ES Repository that you want to use for message processing.

  • The service interface must have interface pattern XI 3.0 compatible.

  • You have created the objects for the business system in Integration Directory of AEX.

Procedure

1. Configure a Process in BPM Process Composer

  1. Create a project in the Process Composer perspective of SAP NetWeaver Developer Studio.

    More information: Creating a Project

  2. Create your process and create a new pool representing the BPM process.

    More information: Creating a Process

  3. Import the inbound service interface from ES Repository.

    More information: Importing Service Interface Definitions

  4. For better overview, create a second passive pool representing the business system the process exchanges messages with via AEX. This step is optional.

    More information: Defining Process Participants Using Pools

  5. To receive messages from AEX in a BPM process, add a message start event or an intermediate message event to your BPM process in Process Composer.

    • To trigger a process instance by an inbound message coming from AEX, use a message start event.

    • If a running process instance should wait for an inbound message coming from AEX, use an intermediate message event.

    • Define data mappings.

      More information: Defining Data Mappings

    More information: Events , Modeling Events

  6. Build and deploy your process.

    For XI 3.0 compatible service interfaces, the BPM system automatically creates an XI endpoint.

    More information: Building and Deploying a Process

2. Configure Message Processing in Integration Directory of AEX

  1. In the Integration Directory of AEX create a communication component representing the BPM process.

    You do not need to create a party.

  2. On the Receiver tab assign the inbound service interface you want to use for message exchange.

    More information: Defining Communication Components

  3. Create a communication channel with the following attributes:

    • Direction: Receiver

    • Adapter type: SOAP

    • Message protocol: XI 3.0

    • Addressing type: URL Address

    • Target URL: http(s)://<hostname>:<port>/MessagingSystem/receive/JPR/XI

      Enter the host name and port of the local system.

    More information: Defining Communication Channels , Configuring the Receiver SOAP Adapter

  4. Create an Integrated Configuration with the following settings:

    • Add information about the business system that is the sender.

    • On the Outbound Processing tab, select the receiver SOAP adapter you defined.

    • On the Receiver tab, select the business component representing the BPM system.

    • On the Receiver Interfaces tab, select the inbound service interface the BPM process uses.

    More information: Configuration Objects (Advanced Adapter Engine) , Defining the Integrated Configuration