If a failure occurs during the processing of a PIP message, Business Integration Connect uses the 0A1 PIP as the mechanism to broadcast the failure to the participant or back-end system that sent the message. For example, say a back-end system initiates a 3A4 PIP. Business Integration Connect processes the RNSC message and sends a RosettaNet message to a participant. Business Integration Connect waits for the response to the RosettaNet message until the waiting time reaches the timeout limit. Once this occurs, Business Integration Connect creates a 0A1 PIP and sends it to the participant. The 0A1 PIP identifies the exception condition so that the participant can then compensate for the failure of the 3A4 PIP.
To provide failure notification, upload a 0A1 package and create a PIP connection to the participant using this package.
To change the RosettaNet contact information with the 0A1 PIP, you must edit the BCG.Properties file, located in the <install_root>/wbic/config directory.
These fields populate the contact information within the 0A1 PIP. Fax is optional (value can be empty), but the rest are required.
The phone numbers are limited to 30 bytes in length. The other fields are unlimited in length. When they are changed, the router will need to be restarted.