WebSphere Process Server artifacts
The PIP sample consists of four business integration modules:
PIP3A4Buyer, BuyerEventDispatcher, PIP3A4Seller, and SellerEventDispatcher.
PIP3A4Buyer and BuyerEventDispatcher are for the buyer side, and
PIP3A4Seller and SellerEventDispatcher are for the seller side.
The PIP sample uses the index.jsp file, business objects, WSDL Interfaces,
and BPEL processes listed in this section to support the scenarios.
Business objects
The PIP sample uses the following business objects:
- PIP3A4Request - The following business objects are required for PIP 3A4 request messages:
- BCG_PIP3A4PurchaseOrderRequest - This
is the top-level object for the PIP 3A4 request message. The same
object is used for both scenarios 1 and 2. The same business object
structure is used for the buyer and seller processes with different
namespaces. For the buyer process, it uses the http://PIP3A4Buyer namespace,
and for the seller process, it uses the http://Partner namespace. This
business object contains the attachment business object (of type
array), package headers business object, and payload wrapper business
object as child business objects.
- BCG_PayloadContainer_Pip3A4PurchaseOrderRequest -
This is the wrapper business object for the PIP3A4 request. This
business object contains the information about the payload, such
as encoding and content type. The same business object structure
is used for the buyer and seller processes with different namespaces.
For the buyer process, it uses the http://PIP3A4Buyer namespace,
and for the seller, it uses the http://Partner namespace.
- Pip3A4PurchaseOrderRequest - This is the
payload business object of the PIP3A4 request. This represents service
content of the PIP 3A4 request. Refer to the Enterprise Integration Guide for
information about how this business object can be created.
- PIP3A4Response - The following business
objects are required for the PIP 3A4 response message:
- BCG_PIP3A4PurchaseOrderConfirmation -
This is the top-level object for the PIP 3A4 confirmation message.
The same object is used for both scenarios 1 and 2. The same business
object structure is used for the buyer and seller processes with
different name spaces. For the buyer process, it uses the http://Partner
namespace, and for seller, it uses the http://PIP3A4Seller namespace.
This business object contains the attachment business object (of type
array), package headers business object, and payload wrapper business object
as child business objects.
- BCG_PayloadContainer_Pip3A4PurchaseOrderConfirmation -
This is the wrapper business object for the PIP3A4 confirmation.
This business object contains the information about the payload,
such as encoding and content type. The same business object structure
is used for the buyer and seller processes with different namespaces.
For the buyer process, it uses the http://Partner namespace, and
for seller process, it uses the http://PIP3A4Seller namespace.
- Pip3A4PurchaseOrderConfirmation - This
is the payload business object of the PIP3A4 confirmation. This
represents the service content of PIP 3A4 response. Refer to the Enterprise Integration Guide for
information about how this business object can be created.
- EventNotification - For EventNotification,
the following business objects are required and reside on the BuyerEventDispatcher
and Seller EventDispatcher modules:
- BCG_EventNotification - This is the top-level
object for the event notification message. The same object is used
for both scenarios 1 and 2. The same business object structure is
used for the buyer and seller event dispatchers with the same namespaces,
http://EventNotification. This business object contains the attachment
business object (of type array), package headers business object,
and payload wrapper business object, as child business objects.
- BCG_PayloadContainer_EventNotification -
This is the wrapper business object for the event notification message.
This business object contains the information about the payload,
such as encoding and content type. The same business object structure
is used for the buyer and seller event dispatchers with the same
namespace, http://EventNotification.
- EventNotification - This is the payload
business object of the event notification message. This business
object is in the namespace, which is http://www.ibm.com/websphere/bcg/2003/v1.0/xmleventnotification.
The PIP sample already has these business objects. However, if you need to obtain this business object, you can follow following steps:
- Navigate to the Package_RNIFV02.02.zip file in the WebSphere
Partner Gateway product directory.
- Extract the zip file to a temporary directory.
- XMLEvent_v1.0ns.xsd gives the business object.
- Pip0A1FailureNotification - For FailureNotification,
the following business objects are required and reside on BuyerEventDispatcher
and Seller EventDispatcher:
- BCG_Pip0A1FailureNotification - This is
the top-level object for the event notification message. This object
is used for scenario 2. The same business object structure is used
for the buyer and seller event dispatcher with the same namespace,
http://PIP0A1. This business object contains the attachment business
object (of type array), package headers business object, and payload
wrapper business object, as child business objects.
- BCG_PayloadContainer_ Pip0A1FailureNotification -
This is the wrapper business object for the event notification message.
This business object contains the information about the payload,
such as encoding and content type. The same business object structure
is used for the buyer and seller processes with the same name space,
http://PIP0A1.
- Pip0A1FailureNotification - This is the
payload business object of the PIP 0A1 failure notification. This
represents the service content of PIP 0A1 failure notification.
Refer to the Enterprise Integration Guide for
information about how this business object can be created.
- BCG_AttachmentType - The attachment container
is the common business object for request, confirmation, event notification,
and failure notification. The same business object structure is
used for the buyer processes, buyer event dispatcher, seller processes,
and seller event dispatcher with different namespaces, and each process
and event dispatcher contains two different instances of the business object.
For the buyer process, it uses the http://PIP3A4Buyer namespace
for request and the http://Partner namespace for confirmation, and
for the seller process, it uses the http://PIP3A4Seller namespace
for confirmation and the http://Partner namespace for request. For
the event dispatchers, it uses the http://EventNotification and
http://PIP0A1 for failure notification message.
- BCG_PackagingHeaders - The packaging headers
business object is the common business object for request, confirmation,
event notification, and failure notification. This business object
contains the information about the JMS headers, content type, and
length. The same business object structure is used for the buyer and
seller processes and event dispatchers with different namespaces,
and each process or event dispatcher contains two different instances
of the business object. For the buyer process, it uses the http://PIP3A4Buyer
namespace for request, and the http://Partner namespace for confirmation,
and for the seller process, it uses the http://PIP3A4Seller namespace
for the confirmation, and the http://Partner namespace for request.
For the event dispatchers, it uses the http://EventNotification
and http://PIP0A1 for failure notification message.
WSDL Interfaces
The PIP sample uses the following interfaces:
- ReceiveRequest - This interface is used
for receiving the request from the JSP file.
Operation Name: receiveRequestMessage
Input variable: recvReq
Input parameter type: BCG_Pip3A4PurchaseOrderRequest
Operation type: One-way
- SendRequest - This interface is used for
sending the request to WebSphere Partner Gateway.
Operation Name: sendRequestMessage
Input variable: sendReq
Input parameter type: BCG_Pip3A4PurchaseOrderRequest
Operation type: One-way
- ReceiveConfirmation - This interface is
used for receiving the confirmation message from WebSphere Partner
Gateway (for the buyer) or from the JSP file (for the seller).
Operation Name: receiveConfirmationMessage
Input variable: recvConfirm
Input parameter type: BCG_Pip3A4PurchaseOrderConfirmation
Operation type: One-way
- SendConfirmation - This interface is used
for sending the confirmation message to WebSphere Partner Gateway.
Operation Name: sendConfirmationMessage
Input variable: sendConfirm
Input parameter type: BCG_Pip3A4PurchaseOrderConfirmation
Operation type: One-way
- BCGToEventDispatcher - This interface
is used for receiving the event/failurenotification from WebSphere
Partner Gateway. This interface has the following two operations:
1
Operation Name: processEvent
Input variable: eventBO
Input parameter type: BCG_EventNotification
Operation type: One-way
2
Operation Name: processPIP0A1
Input variable: pipBO
Input parameter type: BCG_Pip0A1FailureNotification
Operation type: One-way
- BackendToEventDispatcher - This interface
is used for receiving the event notification from the JSP file.
Operation Name: processBackendEvent
Input variable: eventBO
Input parameter type: BCG_EventNotification
Operation type: One-way
- BackendEventNotifier - This interface
is used for sending the event notification to the PIP process.
Operation Name: processBackendEvent
Input variable: backendEventBO
Input parameter type: BCG_EventNotification
Operation type: One-way
- BCGEventNotifier - This interface is used
for sending the event notification to WebSpher Partner Gateway.
Operation Name: processBCGEvent
Input variable: eventBO
Input parameter type: BCG_EventNotification
Operation type: One-way
- PIP0A1Notifier - This interface is used
for sending the failure notification to WebSpher Partner Gateway.
Operation Name: processPIP0A1
Input variable: pip0A1BO
Input parameter type: BCG_Pip0A1FailureNotification
Operation type: One-way
BPEL processes
The PIP sample uses the following processes:
- PIP3A4BuyerBPEL - This buyer BPEL process
processes the incoming and outgoing messages at the buyer side and
logs the appropriate messages in the Systemout.log file. See Figure 4 for an example.
- IP3A4SellerPBPEL - This seller BPEL process
processes the incoming and outgoing messages at the seller side
and logs the appropriate messages in the Systemout.log file. See Figure 5 for an example
Figure 4. Example of PIP3ABuyerBPEL process
Figure 5. Example of PIP3ASellerBPEL process
