![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The Responder private process uses this message to handle inbound requests. A ResponderRequest message is created for each transaction in each interchange from the received inbound EDI document. A ResponderInterchange message is created for each interchange from the received inbound EDI document.Figure 17 Responder Inbound Requestprefix.installation.standardID.RESPONDER.REQUESTExample: AX.BC.BC-ACME.X12.RESPONDER.REQUESTprefix.installation.RESPONDER.REQUESTExample: AX.BC.BC-ACME.RESPONDER.REQUESTTIBCO BusinessConnect sends the ResponderInterchange message to the private process when it receives an interchange from the trading partner.
prefix.installation.standardID.RESPONDER.INTERCHANGEExample: AX.BC.BC-ACME.X12.RESPONDER.INTERCHANGEprefix.installation.RESPONDER.INTERCHANGEExample: AX.BC.BC-ACME.RESPONDER.INTERCHANGE
Table 27 ResponderInterchange Contains a constant value: EDI/Inbound/Interchange TIBCO BusinessConnect sends the message ResponderInterchangeComplete to the private process upon receiving an interchange from the trading partner when the option under General>Inbound>Enable Interchange Complete Message is enabled.prefix.installation.standardID.RESPONDER.INTERCHANGE.COMPLETEExample: AX.BC.BC-ACME.X12.RESPONDER.INTERCHANGE.COMPLETEprefix.installation.RESPONDER.INTERCHANGE.COMPLETEExample: AX.BC.BC-ACME.RESPONDER.INTERCHANGE.COMPLETE
Table 28 ResponderInterchangeComplete Contains a constant value: EDI/Inbound/Interchange This field is populated with the location of the XML file created during EDI to XML conversion validation when the option Enable Audit Report Logging is enabled for a participant in the General tab for Inbound.This file is created only by the internal conversion engine and gives full reporting information of the transactions that are validated. A valid location must be entered for the trading host for the corresponding protocol. The protocol requires the parameter AuditReportLogging to be available to the TIBCO BusinessConnect Palette, which is available under the Advanced tab.
Figure 18 Responder Outbound Synchronous Responseprefix.installation.standardID.RESPONDER.RESPONSEExample: AX.BC.BC-ACME.X12.RESPONDER.RESPONSEprefix.installation.RESPONDER.RESPONSEExample: AX.BC.BC-ACME.RESPONDER.RESPONSE
Table 29 ResponderResponse ID of operation to be performed. Format: interchange_version/group_version/operation TIBCO BusinessConnect generates the closure message, and sends it to the local private process in the ResponderRequest upon receiving a request for a synchronous request-response operation. The private process must return this closure contents in the ResponderResponse message to ensure that TIBCO BusinessConnect can match it with the original Responder request message. XML string representing the response message body or TIBCO Rendezvous/JMS representation of an XML file. The XML must conform to the .xsd generated by EDISIM for the transaction type. If a Responder uses this message class to send a HIPAA 275 Patient Information message, the HL7 message itself is embedded in this field. See the TIBCO HL7 Integration Server Guide for more information. If the Responder TIBCO BusinessConnect failed to successfully post the acknowledgment to the Initiator, the statusMsg field indicates the cause of the error.prefix.installation.standardID.RESPONDER.ACKExample: AX.BC.BC-ACME.X12.RESPONDER.ACKprefix.installation.RESPONDER.ACKExample: AX.BC.BC-ACME.RESPONDER.ACK
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |