The PIP sample uses the business objects, collaboration templates, and the persistence schema listed in this section to support the scenarios.
The PIP sample uses the following business objects:
The PIP sample uses the following collaboration templates:
The collaboration template has the following ports:
PortName | BusinessObject | Description |
RequestFromBackend | BCG_Pip3A4PurchaseOrderRequest | Receives the request from the back-end |
RequestToWBIC | BCG_Pip3A4PurchaseOrderRequest | Sends the request to WebSphere Partner Gateway |
EventFromBackend | BCG_EventNotification | Receives the PIP cancellation request from the back-end |
EventToWBIC | BCG_EventNotification | Sends the PIP cancellation event to WebSphere Partner Gateway |
ResponseFromWBIC | BCG_Pip3A4PurchaseOrderConfirmation | Receives the response from WebSphere Partner Gateway |
ResponseToBackend | BCG_Pip3A4PurchaseOrderConfirmation | Sends the response to the back-end |
Configuration Properties:
The collaboration template has the following ports:
PortName | BusinessObject | Description |
RequestFromWBIC | BCG_Pip3A4PurchaseOrderRequest | Receives the request from WebSphere Partner Gateway |
RequestToBackend | BCG_Pip3A4PurchaseOrderRequest | Sends the request to the back-end |
EventFromBackend | BCG_EventNotification | Receives the PIP cancellation event from the back-end |
EventFromWBIC | BCG_EventNotification | Receives the PIP acknowledgment event from WebSphere Partner Gateway |
ResponseFromBackend | BCG_Pip3A4PurchaseOrderConfirmation | Receives the response from the back-end |
ResponseToWBIC | BCG_Pip3A4PurchaseOrderConfirmation | Sends the response to WebSphere Partner Gateway |
Configuration Properties
The collaboration template has the following ports:
PortName | BusinessObject | Description |
RequestFromBackend | BCG_Pip3C3InvoiceNotification | Receives the notification from the back-end |
RequestToWBIC | BCG_Pip3C3InvoiceNotification | Sends the notification to WebSphere Partner Gateway |
EventToWBIC | BCG_EventNotification | Receives the PIP acknowledgment event from WebSphere Partner Gateway |
EventFromBackEnd | BCG_EventNotification | Receives the PIP cancellation event from the back-end |
Configuration Properties
The collaboration template has the following ports:
PortName | BusinessObject | Description |
RequestFromWBIC | BCG_Pip3C3InvoiceNotification | Receives the request from WebSphere Partner Gateway |
RequestToBackend | BCG_Pip3C3InvoiceNotification | Sends the request to the
back-end |
EventFromBackEnd | BCG_EventNotification | Receives the PIP cancellation event from the back-end |
EventFromWBIC | BCG_EventNotification | Receives the PIP acknowledgement event from WebSphere Partner Gateway |
Configuration Properties
The collaboration template has the following ports:
PortName | BusinessObject | Description |
NOFFromWBIC | BCG_Pip0A1FailureNotification | Receives the PIP 0A1 from WebSphere Partner Gateway |
NOFToBackend | BCG_Pip0A1FailureNotification | Sends the PIP 0A1 to the back-end |
EventFromWBIC | BCG_EventNotification | Receives the PIP acknowledgement event from WebSphere Partner Gateway |
EventToBackEnd | BCG_EventNotification | Sends the Acknowledgment event to the back-end |
Configuration Properties
DB_CONN_POOL_NAME
Default Value = CWLDPool
The PIP sample uses a database table to persist the IDs and status of the PIP messages. The following table describes the schema of the database table:
Column | Corresponding JMSProperties attribute | Description |
Senderid | x-aux-sender-id | The ID of the initiator of the PIP |
Receiverid | x-aux-receiver-id | The ID of the destination of the PIP |
Documentid | x-aux-msg-id | The ID of the message assigned by the process initiating the PIP |
PIPInstanceid | x-aux-process-instance-id | The ID of the PIP to which the message belongs |
Msgid | x-aux-system-msg-id | The ID of the message assigned by the system sending the PIP message |
Status | x_aux_event_status_code | The state of the PIP: 0 - Initiated 100 - Ack received 800 - PIP terminated by back-end 900 - Exception received |
DocType | None | The type of message: REQ - for request message RESP - for response message NOTI - for notification message 0A1 - for Failure notification message |