Routing of non-AS and non-ebMS messages

For messages that are received through non-AS and non-ebMS protocols, the B2B gateway determines the routing policy in terms of the message type.

The B2B gateway can receive non-AS and non-ebMS messages through a protocol such as HTTP, FTP, and IBM® MQ. The B2B gateway determines the routing policy in terms of the message type.
  • For X12 and EDIFACT messages, the B2B gateway parses the message contents to find the partner identifiers from the ISA and UNA headers.
  • For XML messages, the B2B XPath routing policy defines how to find the partner identifiers. For more information, see B2B XPath routing policy.
  • For binary messages, a DataPower® administrator must configure the document routing preprocessor to route messages properly. With the document routing preprocessor, you can implement a custom parser to extract trading partner identifiers and set the document routing variables. You can create a stylesheet or a GatewayScript file as the document routing preprocessor.
    Stylesheet
    The routing stylesheet uses XSLT 1.0 stylesheet with standard DataPower extensions and traverses an empty tree as the input context. The stylesheet examines information from transport headers and other noncontent sources to select trading partners. The default stylesheet is store:///b2b-routing.xsl.
    GatewayScript
    The GatewayScript program examines information from protocol headers and payloads to select trading partners. The GatewayScript program can read the input data as different types such as JSON and XML from the input or INPUT context. A sample Gateway script file is store:///gatewayscript/example-b2b-routing.js.
    To use the document routing preprocessor, complete the following procedures.
    1. Make a copy of the sample stylesheet or GatewayScript file.
    2. Edit the file to the needs of a particular B2B gateway.
    3. Update the document routing preprocessor with the file location.

    You can configure each B2B gateway with a different routing preprocessor. You cannot configure a B2B gateway to use both a stylesheet and GatewayScript file as the routing processor.