From address and To address tabs

The following fields are displayed on the maintenance pages for all types of pickups:

  • Specify the address – Specifies that the trading engine should always use a fixed address for the sender or receiver. You can click Pick party to launch a wizard that helps you locate the community or partner you want. The “from” or “to” party must be set up as a community or partner in the user interface.
  • Address must be determined by either message attribute configuration or by protocol address only – Select this option if the “from” or “to” address or both is configured using the Message attributes tab. This option is available only for the file system transport.
  • Use the protocol address but if protocol address is missing, parse the document for the address – Select this option to use the protocol address if available. If not available, the additional parse settings below apply.
  • Always parse for the address – Specifies that the trading engine should always parse the message for the sender or receiver address.
  • For messages from partners, however, the trading engine still checks the protocol header for the sender and receiver. A message with an unknown sender or receiver in the header is rejected. The always parse option for inbound messages is for finding the identity of true senders or true receivers.
  • For messages picked up from integration, the always parse option tells the trading engine to find the sender or receiver in the message body. Messages from integration do not have protocol headers.
  • The additional parse settings below apply.

Additional parse settings

  • If the document is EDI, parse for the address – If an EDI document is picked up, use the “to” and “from” addresses specified within it. Properly formatted EDI documents contain this information.
    • Perform enhanced EDI parsing to match partner messaging IDs – This setting applies to X12, EDIFACT, and TRADACOMS. If selected, the trading engine performs additional parsing of the header information to create routing IDs with a colon separator between values. For example, information from an EDIFACT file would be parsed in the following format:

    ID:interchange ID:internal ID:sub-internal ID

    • When this parsing option is elected, communities and partners must have matching routing IDs in the same format. For example, if the “from” address in a parsed message is ID:interchange ID:value3:value4, the partner must have the same routing ID.
    • When this option is not selected, “to” and “from” addresses in messages are parsed only for ActivatorID and ID values. For example, 1:partner is parsed as the sender and rendered as partner1 in the user interface.
    • Note that TRADACOMS only has two, optional values that can be parsed. They must match one of the following patterns:
    • A:
      :B
    • A:B
  • If the document is XML, use XPaths to locate the address – If an XML document is picked up, use the “to” and “from” addresses specified by the XPaths within it. XML Path Language or XPath is a language for addressing parts of an XML document.
    • Document type – For XML, select a document type from the available list for the From XPath or To XPath fields. These fields are for specifying the XPaths of the message sender or receiver. If you use a document type not listed, click XPath and use the wizard to specify the XPaths using your example of the XML document. You can use the XPath wizard for the “from” or “to” address or both. Using the XPath wizard requires knowledge of XML.

Related Links