Configuring Message Processing from BPM to PI

Use

You use an automated activity to process messages from a BPM process to the Advanced Adapter Engine Extended (AEX).

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

The following procedure only describes the steps and objects necessary for message exchange between the BPM process and the AEX. You have to add the other steps of your process. In AEX, add the receiver and for example mapping and routing definitions.

Prerequisites

You have designed an outbound service interface in ES Repository that you want to use in your message processing.
The service interface must have interface pattern XI 3.0 compatible. Other interface patterns are not supported.
You have created the objects for the business system in Integration Directory of AEX.

Procedure

1. Configure a Process in BPM Process Composer

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

More information: Creating a Project
Create your process and create a new pool representing the BPM process.

More information: Creating a Process
Import an outbound service interface from ES Repository.

More information: Importing Service Interface Definitions
When modeling your process, create a second, passive pool for the business system that you exchange messages with using AEX. This is an optional step.

More information: Defining Process Participants Using Pools
To send messages from a BPM process to AEX, define an automated activity in the BPM process.
1. Assign the imported outbound service interface to the automated activity.
2. The service reference type is automatically set to WS. In the Type field select XI.
  
  Note
  
  Service reference type XI cannot be combined with WS and RFC types in one Service Group.
3. Under Custom properties enter the sender component name.
  Note
  
  You can change the sender component name in SAP NetWeaver Administrator.
  1. Choose SOA Application and Scenario Communication Application Communication and select your application.
  2. Select the service group and service reference and select Edit .
  3. Select the Configuration tab and change the entry in the Sender Component field.
4. Define data mappings.
  
  More information: Defining Data Mappings
More information: Modeling Automated Activities
Build and deploy your process.

More information: Building and Deploying a Process

2. Configure Message Processing in Integration Directory of AEX

In the Integration Directory of AEX create a communication component representing your BPM process. Reuse the name you defined for the sender component in your BPM process.

You do not need to create a party.
On the Sender tab, assign the outbound service interface you want to use for message processing.

More information: Defining Communication Components
Create a communication channel with the following attributes:
- Direction: Sender
- Adapter type: SOAP
- Message protocol: XI 3.0
More information: Defining Communication Channels , Configuring the Sender SOAP Adapter
Create an Integrated Configuration and provide the following information for the sender:
- Select the communication component representing the BPM process.
- Select the outbound interface the BPM process uses.
After creating the Integrated Configuration, select on the Inbound Processing tab the sender SOAP adapter you defined.

Add information about the business system that is the receiver.

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