Error Message Format
When an error occurs, TIBCO BusinessConnect Container Edition - RosettaNet Protocol terminates the transaction and publishes an ErrorNotify message.
Note: Do not use ErrorNotify messages to send transaction errors to BusinessConnect Container Edition. You cannotify BusinessConnect Conatiner Edition of a transaction error in the status field of a BCResponseFromPPmessage.
BusinessConnect communicates state changes using advisory messages. See Appendix A, PIP States for a list of states and their descriptions
Class ErrorNotify
Installation prefix.installation.ERROR (JMS queue)
Message Fields
Field | Type | Description |
---|---|---|
statusCode | Integer | One of the internal error codes. See Advisory and Error Status Codes for a description of each code |
details | String | A description of the error |
statusMsg | String | The name of the error. See PIP States. |
msgDirection | String | Either Inbound or Outbound. This field indicates the direction of the message. |
operationID | String | A three-part ID of the form: PIP/version/activity. |
transaction ID | String | (Optional but recommended) Used by the private process to cross-reference this PIP |
standardID | String | The string "RosettaNet". |
timestamp | String | The timestamp for this message. |
host | String | The trading host. |
tpName | String | The trading partner in this transaction. |
extraInfo | String | A series of name-value pairs separated by a comma and space character. For example: rnifVersion=1.1, pipCode=3A4, ... The name-value pairs in this field are the same as the data in the RNAdvisoryInfo object. See RNAdvisoryInfo Object for a description of each name-value pair. |
Copyright © Cloud Software Group, Inc. All rights reserved.