Setting up the sample involves setting up WebSphere Partner Gateway, WebSphere MQ, and WebSphere InterChange Server. 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 all the scenarios of the PIP sample. The setup for System B and C is the same except where noted.
See the Hub Configuration Guide for more information on creating gateways.
Use the default values for all other parameters.
Parameter | Value to type or select |
Address |
The URL for the JNDI service that stores the JMS objects required by WebSphere Partner Gateway to route the documents. For WebSphere MQ JMS, the file system JNDI can be leveraged. If the file system JNDI is leveraged, the format of the address is as follows: file:///<user_defined_MQ_JNDI_bindings_path> The directory contains the bindings file for the file-based JNDI. This field is required. |
Authentication Required |
If enabled, user name and password are supplied with JMS or SMTP messages. |
Auto Queue |
If enabled, documents are placed in a temporary repository if the gateway is placed offline. If disabled and the gateway is placed offline, the document fails to route and an error occurs. |
Configuration Point Handlers |
Used to specify which handlers are used for preprocessing and postprocessing. |
Description |
Optional description of the gateway. |
Gateway Name |
Name used to identify the gateway. Note: Gateway Name is a user-defined free format field. While uniqueness is not required, users should use different names for individual gateways to avoid potential confusion. |
JMS Factory Name |
Name of the Java(TM) class the JMS provider will use to generate connection to the JMS queue. |
JMS JNDI Factory Name |
Factory name used to connect to the name service. |
JMS Message Class |
Class of message. |
JMS Message Type |
Type of JMS message. |
JMS Queue Name |
Queue name where JMS messages are stored. |
Number of Threads |
Number of threads allocated for routing a document. Default value is 3. This parameter is available to Hub Admin users only. |
Online / Offline |
Indicate whether the gateway is online or offline. If offline, documents are queued until the gateway is placed online. |
Password |
Password for secure access through the participant firewall. |
Provider URL Packages |
Name of classes or JAR file that Java uses to understand JMS Context URL. |
Retry Count |
Maximum number of times the system tries to send a document before it fails. Default value is 3. |
Retry Interval |
Amount of time that the gateway should wait in between retry attempts. Default value is 300 (5 minutes). |
Status |
Indicates whether the gateway is enabled or disabled. If disabled, documents passing through the gateway fail processing. |
Transport |
Protocol for routing documents. |
User Name |
User name for secure access through the participant firewall. |
Validate Client IP |
Validates the IP address of the sending partner before processing the document. Used with the Gateway that is selected as a source Gateway for a connection. |
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. That is, if you are creating System B, type the URL for System C. Example: http://<IPAddress of System C:57080>/bcgreceiver/submit/test |
For the other parameters, use the default values.
Refer to the Hub Configuration 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) |
To set WebSphere MQ to support the sample, create the following queues in the Queue Manager:
Consult the WebSphere MQ documentation for information on how to create the queues.
The following procedure describes how to set up WebSphere InterChange Server so that it has the settings and resources it needs to run all the scenarios of the PIP sample. For more information on any of the steps in the procedure, see the WebSphere InterChange Server documentation.
Attribute | Value |
CTX_InitialContextFactory | com.sun.jndi.fscontext.RefFSContextFactory |
ReplyToQueue | The name of the queue in which the JMS Connector puts the messages |
UnsubscribedQueue | CWLD_Unsubscribed |
CTX_ProviderURL | The URL of the JMS context provider |
InProgressQueue | CWLD_InProgress |
DataHandlerConfigMO | MO_DataHandler_Default |
MessageResponseResultProperty | CWLD_Result |
DataHandlerMimeType | Attachment |
QueueConnectionFactoryName | The queue connection factory created in WebSphere MQ |
ErrorQueue | CWLD_Error |
InputQueue | The name of the queue that the JMS Connector polls for incoming messages |
Port | Connector |
RequestFromBackend | PortConnector |
RequestToWBIC | JMSConnector |
EventToWBIC | JMSConnector |
EventFromBackend | PortConnector |
ResponseFromWBIC | JMSConnector |
ResponseToBackend | PortConnector |
Port | Connector |
RequestFromWBIC | JMSConnector1 |
RequestToBackend | PortConnector |
EventFromBackend | PortConnector |
EventFromWBIC | JMSConnector1 |
ResponseFromBackend | PortConnector |
ResponseToWBIC | JMSConnector1 |
Port | Connector |
RequestFromBackend | PortConnector |
RequestToWBIC | JMSConnector |
EventToWBIC | JMSConnector |
EventFromBackend | PortConnector |
Port | Connector |
RequestFromWBIC | JMSConnector1 |
RequestToBackend | PortConnector |
EventFromBackend | PortConnector |
EventFromWBIC | JMSConnector1 |
Port | Connector |
NOFFromWBIC | JMSConnector |
NOFToBackend | PortConnector |
EventFromWBIC | JMSConnector |
EventToBackend | PortConnector |
Port | Connector |
NOFFromWBIC | JMSConnector1 |
NOFToBackend | PortConnector |
EventFromWBIC | JMSConnector1 |
EventToBackend | PortConnector |
To run Scenario 1, do the following:
Please refer to the Enterprise Integration Guide for more information about the properties under JMSDynMO.
Collaboration Success: Collaboration Name {The collaboration name}, Scenario Name SendRequest, BLOCK Name SendBO.
This indicates that the 3A4 request has been successfully posted to the JMS connector.
Please refer to the Integration Overview Guide for more information about the properties under JMSDynMO.
Collaboration Success: Collaboration Name {The collaboration name}, Scenario Name SendResponse, BLOCK Name SendBO.
The Port Connector receives the 3A4 response message is received in the Port Connector. This is the 3A4 response at the buyer's back-end process. Select the response and click Reply success.
To run Scenario 2, run Scenario 1 and then do the following:
Please refer to the Enterprise Integration Guide for more information about the properties under JMSDynMO.
Collaboration Success: Collaboration Name {The collaboration name}, Scenario Name SendEvent, BLOCK Name SendEvent.
This indicates the event message has been successfully posted to the JMS connector.
To run Scenario 3, do the following:
Please refer to the Enterprise Integration Guide for more information about the properties under JMSDynMO.
Collaboration Success: Collaboration Name {The collaboration name}, Scenario Name SendRequest, BLOCK Name SendBO.
This indicates the 3C3 request has been successfully posted to the JMS connector.