You can use the CPS to test the scenarios shown in Table 26 between you and your participants.
Scenario | Destination for Connection | URL |
---|---|---|
One-way outbound from the Community Manager to a participant. Simulating Community Manager. |
VTP_Owner |
VTP_OWNER |
One-way inbound from participant to Community Manager. Simulating participant. |
VTP_TP |
Not applicable in this scenario. |
Two-way outbound from Community Manager to participant (Upload Request). Simulating Community Manager. |
VTP_Owner |
VTP_OWNER |
Two-way inbound from participant to Community Manager (Upload Request). Simulating participant. |
VTP_TP |
VTP_TP |
Two-way outbound from Community Manager to participant (Upload Response). Simulating participant. |
VTP_TP |
VTP_TP |
Two-way inbound from participant to Community Manager (Upload Response). Simulating Owner. |
VTP_Owner |
VTP_Owner |
This section describes the steps involved in configuring the CPS to simulate two one-way RosettaNet (RN) interactions. The steps are not fully described here. They are described with more detail in the Hub Configuration Guide.
You will see the directories and hub configuration settings that are used by the CPS, and you will have a better understanding of how the CPS can be helpful in debugging routing between participants.
Community Manager:
Set up an HTTP sink gateway for the manager. This is an HTTP gateway that sends to URL http://<console-ip>:<console-port>/console/sink.
The sink gateway should be specified as the default CPS participant and CPS Manager gateway for the Community Manager.
Community participant:
Set up an HTTP sink gateway for the participant just as you did for the Community Manager.
RosettaNet PIP XML files:
The 3A4 interaction is the scenario described here. The participant-to-manager simulation uses XML that contains the 3A4 Purchase Order Request content.
The manager-to-the participant simulation uses XML that complies with the 3A4 Purchase Order Confirmation RNSC content. These XML files reside on your local file system.
Please refer to the Hub Configuration Guide for related information. When you create the files, remember that the to and from Ids must match those of the Community Manager and the participant in the appropriate places in these files.
Configuring the Console and Router Servers:
If you plan to use encryption or signing in your simulation, you need a pair of public-key and private-key certificates. Use p8 format for the private keystore and der format for the public certificate.
## VTP
ibm.bcg.certs.vtp.CertificateDir=C:/{INSTALL DIR}/common/security/vtp
ibm.bcg.certs.vtp.Certificate=testcert.der
ibm.bcg.certs.vtp.PrivateKey=testkey.p8
ibm.bcg.certs.vtp.Passwd=password
ibm.bcg.certs.vtp.VerifySig=false
ibm.bcg.vtp.RouterIn=C:/{INSTALL DIR}/common/router_in
Configuring 3A4 Connectivity:
If you are familiar with RosettaNet routing, configure RosettaNet connectivity between a Community participant and the Community Manager using the following steps.
If you are not familiar with RosettaNet routing, refer to the Hub Configuration Guide for assistance when performing the following tasks:
Upload the following files in the order shown. The files are located in the /B2Bintegrate/rosettanet directory of the installation CD:
If you have sample 3A4 Request XML and 3A4 RNSC XML files in your file system, you can use the Community Participant Simulator to exercise all of the internal routing function. Click on the Community Participant Simulator tab and then click the Browse button. Select a file from the file system containing the content that you want to route, and then click the Route button.
The document will be read from the file system and uploaded to the hub. It is passed to the Document Manager for routing, and the routing that you have configured in the hub will be used.