The Community Participant Simulator (CPS) can be used before and after the Hub Community goes live to simulate production traffic (requests, responses, and acknowledgments) between the Community Manager and a participant.
The purpose of the CPS is:
The Community Manager uses the cps to verify that documents are formatted correctly and contain valid business content.
The CPS gives the Community Manager the ability to test their back-end systems (routers and receivers) without initiating the test from their own back-end applications, and without requiring a participant to transmit data. As a result, they can test without engaging test systems or technical support personnel.
To initiate the test, the Community uploads a test document. This feature only accepts RNIF v2.0; it is not compatible with RNIF 1.1. The test document must be a RosettaNet Service Content file; you cannot upload a RosettaNet Object (RNO). Service Content is the primary component of the payload of a RosettaNet Business Message. It is an XML document that represents the business content specified by a particular PIP. The payload also includes any file attachments.WebSphere Partner Gateway uses the test document to identify routing and processing information.
The CPS does not generate receipt acknowledgments. If a 3A4 confirmation is sent to CPS, the Document Manager closes the exchange with an 0A1.
Note that the installation process creates a sink gateway (that is, a bit bucket) to receive acknowledgments during the testing process:
http://<hostname>:<port#>/console/sink
or
https://<hostname>:<port#>/console/sink
This chapter contains the following sections: