Copyright © Cloud Software Group, Inc. All Rights Reserved

Initiator Messages

Initiator Outbound Request

The Initiator private process uses this message to handle outbound requests.

Figure 2 Initiator Outbound Request

.

Rendezvous Subject Name

prefix.installation.standardID.INITIATOR.REQUEST

Example: AX.BC.BC-ACME.B2B-X12.INITIATOR.REQUEST

JMS Queue Name

prefix.installation.INITIATOR.REQUEST

Example: AX.BC.BC-ACME.INITIATOR.REQUEST

Message Name

InitiatorRequest

Table 12 Initiator Request

Field	Type	Required	Description
standardID	String	Yes	B2B-X12, B2B-EDIFACT, B2B-TEXT, B2B-TRADACOMS
operationID	String	Yes	ID of operation to be performed. Format: interchange_version/group_version/transactionoperation Example: 00403/005010/850
transactionID	String	Yes	An ID unique within Initiator private process's environment for this transaction. The private process creates this ID.
tpName	String	Yes	Trading partner name.
encoding	String	No	The encoding used in the request. Example: UTF--16. When sending UTF-16 encoded request of EDI documents, this field should have a value of UTF-16.
closure	Any	Yes	The closure message is sent to the private process.
request	String	No	A string representing the message body or TIBCO Rendezvous/JMS representation of an EDI file.
inputFile	String	No	Optional. Specifies the full path of the file where the EDI request is stored. If this is specified, the request is read from the file. The request field takes precedence.

Initiator Inbound Response

This message indicates if a InitiatorRequest has been successfully sent to your trading partner. If the requesting operation is a synchronous operation, this message contains the synchronous response EDI message received from the trading partner

Figure 3 Initiator Inbound Response

Rendezvous Subject Name

prefix.installation.standardID.INITIATOR.RESPONSE

Example: AX.BC.BC-ACME.B2B-X12.INITIATOR.RESPONSE

JMS Queue Name

prefix.installation.INITIATOR.RESPONSE

Example: AX.BC.BC-ACME.INITIATOR.RESPONSE

Message Name

InitiatorResponse

Table 13 InitiatorResponse (Sheet 1 of 2)

Field	Type	Required	Description
response	String	No	A string representing the message body or TIBCO Rendezvous/JMS representation of an EDI file.
standardID	String	Yes	B2B-X12, B2B-TEXT, B2B-TRADACOMS, B2B-EDIFACT.
operationID	String	Yes	ID of operation to be performed. Format: interchange_version/group_version/transactionoperation Example: 00403/005010/850
transactionID	String	Yes	The response's transaction ID.
statusCode	Integer	Yes	200 success. Otherwise, one of the error codes. See Appendix B, Status and Error Codes.
statusMsg	String	Yes	OK, or the string representing the cause of the error. In this case, the response might be an error document. See Appendix B, Status and Error Codes.
duplicate	Boolean	No	Set to true if the private process sent a duplicate document.
closure	Any	Yes	The private process generates the closure message and sends it to TIBCO BusinessConnect. TIBCO BusinessConnect is required to return this closure contents back in the InitiatorResponse to ensure that the private process can match it with the original InitiatorRequest.

Copyright © Cloud Software Group, Inc. All Rights Reserved