![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
If the TpName and receiver qualifier ID are sent from the private process, TpName takes precedence over the receiver qualifier ID of the per message field. The TpName is selected first; if it is not present, the receiver qualifier ID is selected.Figure 15 Initiator Outbound Requestprefix.installation.standardID.INITIATOR.REQUESTExample: AX.BC.BC-ACME.X12.INITIATOR.REQUESTprefix.installation.INITIATOR.REQUESTExample: AX.BC.BC-ACME.INITIATOR.REQUEST
Table 23 Initiator Request ID of operation to be performed. Format: interchange_version/group_version/transactionoperation Overrides the default parameters of the host and trading partner configuration on a per-message basis. For overriding parameters for the interchange header, the ID and qualifier are validated against the list of domain identities for the host and the trading partner. See EnvelopeInfo.X12 The parameters for X12 are:InterchangeHeaderInfo present in the class EDIInterchangeInfo has several overridable fields that are part of the participant Interchange Header tab. The following fields are overridable:InterchangeHeaderInfo present in the class EDIInterchangeInfo has several overridable fields that are part of the participant Interchange Header tab. perMessage (cont) EDIFACT The parameters for EDIFACT are:InterchangeHeaderInfo present in the class EDIInterchangeInfo has several overridable fields that are part of the participant Interchange Header tab. The following fields are overridable:UNBS001Identifier: Syntax identifier
UNBS001ServiceCodeList: Service code list directory version numberUNBS001CharacterEncoding: Character encoding, codedUNBS002InternalID: Interchange sender internal identification. Identification (such as a division, branch, or computer system/process) specified by the sender of the interchange; to be included, if agreed, by the recipient in the response interchange to facilitate internal routing.UNBS002SubInternalID:Interchange sender internal sub-identification. Sub-level of the server internal identification when further sub-level identification is required.UNBS003InternalID: Interchange recipient internal identification/Routing AddressUNBS003SubInternalID: Interchange recipient internal sub-identificationNote: The values entered in the InterchangeHeaderInfo Node of the perMessage field in TIBCO BusinessConnect Palette are not validated when XML to EDI conversion happens for the X12 and EDIFACT protocol. Users should send appropriate valid values from the private process. InterchangeHeaderInfo present in the class EDIInterchangeInfo has several overridable fields that are part of the participant Interchange Header tab. The following fields are overridable:UNBS001Identifier: Syntax identifier
UNBS001ServiceCodeList: Service code list directory version numberUNBS001CharacterEncoding: Character encoding, codedUNBS002InternalID: Interchange sender internal identification. Identification (such as a division, branch, or computer system/process) specified by the sender of the interchange; to be included, if agreed, by the recipient in the response interchange to facilitate internal routing.UNBS002SubInternalID:Interchange sender internal sub-identification. Sub-level of the server internal identification when further sub-level identification is required.UNBS003InternalID: Interchange recipient internal identification/Routing AddressUNBS003SubInternalID: Interchange recipient internal sub-identificationNote: The values entered in the InterchangeHeaderInfo Node of the perMessage field in BusinessConnect Palette are not validated when XML to EDI conversion happens for X12 and EDIFACT protocols. Users should send appropriate valid values from the private process. An string representing the 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. The final destination file name is comprised of destinationFileName and a file extension. The file extension default value is .dat and is derived from the property edi.outbound.contentDisposition.fileExtension, which is located under System Settings > Activated Protocol Plug-ins and Properties > tibEDI. See also Setting the Transport Subject Dynamically for more details. Note: When user-defined control numbers are specified, the conversion engine will not ensure the uniqueness and does not validate the control numbers against the control number sequences that are maintained internally. However, transactions constructed with user-defined control numbers will be recorded for acknowledgment reconciliation. See ControlNumberInfo. Note : It is supported by X12, EDIFACT, TEXT, and TRADCOMS protocols. Note : It is supported by X12, EDIFACT, TEXT, and TRADCOMS protocols. Note: Attachments are ignored if both the content and fileName elements are empty, if both elements are configured, the content element takes precedence. Based on the subject specified in the configuration of the transports EMAIL, AS1, or AS2-HTTP/S, the subject field is overridable by the private process mimeSubject. Users set macros that are case-insensitive either at the configuration or at private process mimeSubject and the macro field is substituted by the TIBCO BusinessConnect EDI Protocol powered by Instream runtime engine. The values pertain to the interchange level for X12 and EDIFACT protocols and non-interchange field values for Gateway protocol.The TEXT protocol does not have InterchangeCtrlNum or InterchangeVerNum and, therefore, the transport subject field with macros
•
•
Values specific to the EDI Interchange document level values, such as InterchangeID/Qualifier (SenderID/ReceiverID, SenderQual/ ReceiverQual), InterchangeVerNum and InterchangeCtrlNum will not get populated in this scenario.The subject in transport configuration can be overridden with the mimesubject from the private process:
• Non-batching only (non-Gateway trading partner or Gateway trading partner)
− When the private process mimeSubject field is set with a value that contains some macro fields to TIBCO BusinessConnect, this value should override the value set in the Transport subject and should be dynamically updated if there are macros passed, such as in #(DocID)- #(tpName)- #(SenderID).
− When mimeSubject is not set, the Transport subject value should be dynamically updated if there are macros passed, such as in #(DocID)- #(tpName)- #(SenderID).
• Batching (Gateway or protocol trading partner)Overriding of the mimeSubject field is not supported for the batching.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 partnerFigure 16 Initiator Inbound Responseprefix.installation.standardID.INITIATOR.RESPONSEExample: AX.BC.BC-ACME.X12.INITIATOR.RESPONSEprefix.installation.INITIATOR.RESPONSEExample: AX.BC.BC-ACME.INITIATOR.RESPONSEThe Initiator TIBCO BusinessConnect uses this message to create a notify message that it sends back to its private process to indicate that a previously sent transaction has been successfully reconciled upon receiving an acknowledgment from the trading partner. 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.INITIATOR.ACKExample: AX.BC.BC-ACME.X12.INITIATOR.ACKprefix.installation.INITIATOR.ACKExample: AX.BC.BC-ACME.INITIATOR.ACK
Table 25 TransactionAckFromTradingPartner ID of operation to be performed. Format: interchange_version/group_version/operation
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |