Setting up the sample involves setting up WebSphere Partner Gateway, WebSphere Admin Console, and WebSphere Process Server. As explained in the section Topology used by the sample, system A is running WebSphere Process Server, System B is running WebSphere Partner Gateway for buyer, and system C is running WebSphere Partner Gateway for seller. Messages in the sample flow in the following manner:
The following sections describe how to do this.
The following procedure describes how to set up WebSphere Partner Gateway so that it has the settings and resources it needs to run the scenarios of the PIP sample. The following steps describe the setup for both System B and System C.
See the Administrator Guide for more information on creating gateways.
Parameter | Value to type or select |
---|---|
Gateway Name |
Type the name for the gateway, as follows: System B:
System C:
|
Transport |
JMS |
Target URI |
iiop://<System_A_IP_addresss:2089>/ If you have installed WebSphere Partner Gateway using the embedded WebSphere option, you must specify the target URI as follows: File:///<user_defined_MQ_JNDI_bindings_path> For more information, refer to the Enterprise Integration Guide. |
JMS Factory Name |
Type the name of the JMS factory, as follows: System B: PIP3ABuyer/PIP3A4BuyerQCF
|
JMS Queue Name |
Type the name of the JMS queue, as follows: System B:
System C:
|
JMS JNDI Factory Name |
com.ibm.websphere.naming.WsnInitialContextFactory If you have installed WebSphere Partner Gateway using embedded WebSphere option, please refer to the Enterprise Integration Guide. |
JMS Message Class |
TextMessage |
Parameter | Value to type or select |
---|---|
Gateway name | Type any name for the gateway |
Transport | HTTP/1.1 |
Target URI |
Type the URL for the other WebSphere Partner Gateway system, as follows: System B: http://<IP_Address_of_System_C:57080>/bcgreceiver/submit/test
|
For the other parameters, use the default values.
Refer to the "Uploading packages" section in the Administrator Guide for information on uploading packages. If packages for the other RNIF version or another version of the PIP have already been loaded, set the Overwrite Data parameter to Yes.
You can verify that the packages have been uploaded by clicking Hub Admin > Hub Configuration > Document Flow Definition. Click All and look for the following in the RNIF (V02.00) and Backend Integration packages:
Package: RNIF (V02.00) Protocol: RosettaNet (V02.00) Document Flow: 3A4 (V02.02) "Request Purchase Order" Activity: Request Purchase Order
Package: Backend Integration (1.0) Protocol: RNSC (1.0) Document Flow: 3A4 (V02.02) "Request Purchase Order" Activity: Request Purchase Order
Package: Backend Integration (1.0) Protocol: XMLEvent (1.0)
Package: Backend Integration (1.0) Protocol: XMLEvent (1.0)
Package: Backend Integration (1.0) Protocol: XMLEvent (1.0)
Package: Backend Integration (1.0) Protocol: RNSC (1.0) Document Flow: 0A1 (V02.00) "Notification of Failure" Activity: Distribute Notification of Failure
Source | Target |
Package: Backend Integration (1.0) Protocol: XMLEvent (1.0) Document Flow: XMLEvent (1.0) |
Package: Backend Integration (1.0) Protocol: RNSC (1.0) Document Flow: 0A1 (V02.00) Activity: Distribute Notification of Failure (N/A) |
Source | Target |
Package: Backend Integration (1.0) Protocol: XMLEvent (1.0) Document Flow: XMLEvent (1.0) |
Package: Backend Integration (1.0) Protocol: XMLEvent (1.0) Document Flow: XMLEvent (1.0) |
The following procedure describes how to create JMS resources required on System A to run all the scenarios of the PIP sample.
The following queues are required on PIP3A4Buyer service integration bus:
Queue name | JNDI name |
---|---|
RequestQ | RequestQ/PIP3A4Buyer |
ResponseQ | ResponseQ/PIP3A4BuyerGW |
EventForBCG | EventFromBCG/PIP3A4BuyerGW |
EventToBCG | EventToBCG/PIP3A4Buyer |
The following queues are required on PIP3A4Seller service integration bus:
Queue name | JNDI name |
---|---|
RequestQ | RequestQ/PIP3A4Seller |
ResponseQ | ResponseQ/PIP3A4SellerGW |
EventForBCG | EventFromBCG/PIP3A4SellerGW |
EventToBCG | EventToBCG/PIP3A4Seller |
Column | Type | Description |
---|---|---|
PIPINSTANCEID | VARCHAR(80) | PIP instance identifier. Uniquely identifies a PIP process. |
REQDOCID | VARCHAR(80) | Requesting document identifier |
PROCNAME | VARCHAR(20) | Name of the process |
STATUS | VARCHAR(10) | It can take two values: START: if given process instance is still running. STOP: if given process instance is not running. |
The following procedure describes how to set up WebSphere Process Server so that it has the settings and resources it needs to run all the scenarios of the PIP sample.
The element may not have duplicate name and target namespace.
The following steps describe how to run Scenario 1.
*** Seller Process :: Confirmation with DocId($$$$$)Received from Backend for the request with DocID($$$$$) ***
*** Seller Process :: Received Confirmation with DocID($$$$$) assigned to outbound port for the request with DocId($$$$$) ***
*** Seller Process :: Confirmation with DocID($$$$$) Sent to Trading partner for the request with DocId($$$$$) ***
The seller's WebSphere Partner Gateway (System C) receives a 3A4 confirmation message. It then sends the 3A4 confirmation RNIF message to the buyer's WebSphere Partner Gateway (System B). The buyer's WebSphere Partner Gateway (System B) receives the RNIF message and converts it to RNSC. It then sends a 3A4 RNSC (as backend integration packaging message over JMS) to the JMS queue configured in WebSphere Partner Gateway (System B) JMS gateway.
*** Buyer Side ::Received Confirmation from Trading partner ***
The following steps describe how to run Scenario 2.
###############################################
Associated Process for the Event having PIPInstanceID ==> $$$$$ is not active
###############################################
This indicates that the XML Event has been successfully posted to the EventToBCG/PIP3A4Seller queue.
###############################################
Associated Process for the PIP0A1 having failed PIPInstanceID ==> $$$$ is not active
###############################################