Dear Scn Users.
This document gives the approach of integrating PI with NWBPM and NWBRM.
Below is the scenario going to be implemented
Communicating PI With BPM:
To trigger a message from PI to BPM, a receiver soap channel with XI 3.0 Message protocol should be configured with target URL as mentioned below
http://XXXYYYZZZ/MessagingSystem/receive/JPR/XIWhere XXXYYYZZZ will be replaced by the respective PI hosts.
And for sending the message back from BPM to PI, a Soap sender channel should be configured with soap as message protocol should be configured, however
communication happens through JPR (Java proxy runtime).
And as like normal PI scenarios ICOs should be created for sending messages from PI to BPM and from BPM to PI.
So an Inbound interface should be configured with “stateless (XI 3.0 compatible) pattern to be used in ICO for communicating with Interface.And same applies for sending message from BPM to PI .And outbound interface should be configured to trigger message from BPM to PI which will be used in SAP PI.
So in NWBPM in addition to the service interfaces that we used in SAP PI for communicating with external systems, we need to create addition interfaces for
communication to SAP PI.And also operation mappings can be imported from ESR in to NWDS and can be used in NWBPM scenarios.
BRM Overview:
BRM is Business rule management which is used to define our business rules. Take an example of a retail store, where the dealer wants to give some discount based on the product, the quantity. In this case BRM comes in to picture where the dealer can define his own rules and define tables based on the individual customer and product, quantity to calculate the discount. From PI 7.31 it is called as process orchestration (SAP PO),combination of PI, BPM and BRM. Below table can be taken as an example for BRM.
This is an example of a BRM table. This rule can be published as webservice and can be called from PI to get the discount rates.
BRM will be published as webservice. To communicate with BRM
1.A Soap receiver channel with Soap as message protocol should be configured,
2.An UDF should be written in PI mapping to call the webservice using the above
The target URL can be obtained from Webservice navigator once the BRM is published as an URL.
Steps in PI:
1.A Data type needs to be created for defining BRM.
2.Four service interfaces to be created to send and receieve message from BPM.
3.A message mapping with UDF to call BRM(Soap channel will be called in this UDF).
4.Sender and receiver channels as per the requriement.In addition to this Soap channels for BPM and BRM communication as discussed.
Steps involved in BRM:
Open NWDS->Open Perspective->Rules composer.
Then open a new project and name your project.
In BRM for defining tables a message type is created export the data type XSD ,save it as localfile and import it in the BRM.
Then select the project resources and in the aliases tab select the required fields for output and Input.
Now required fields are selected for BRM table. Create the BRM table by selecting Tables ->New BRM table and the required fields.
And define the ruleset. Here default rule is used; it can be modified as per the requirement.(IF Boolean true the Hike table will be evaluated)
And Rule should be published as a webservice
Then BRM is deployed. This BRM will be called by UDF(with soap channel in it) and hike percentage will be calculated.
More information can be found in the below link
Steps in BPM:
A Bpm Pattern need to be created as shown below.
This pattern will collect the messages for 60 secs then call BRM using the operation mapping and sends the output(after calculating salary hike using BRM.
Below blogs can be referred for BPM steps.In salary calculation step the message mapping having the UDF for BRM lookup will be imported.
http://scn.sap.com/docs/DOC-55811
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/08/21/collect-pattern-in-nw-bpm
Once this BPM is deployed,We can send a message from PI which will call NWPM,which inturn will call BRM to decide and salary and then finaly output will be returned with salary hike percentage,as per the below sample output XML.
