Defining advanced characteristics for a B2B gateway

How to define advanced characteristics for a B2B gateway.

Procedure

  1. Access the B2B gateway to modify.
  2. Click the Advanced tab.
  3. From the Service priority list, select the priority of the service.
  4. Set the protocol-specific MDN URL or email address to send the asynchronous MDN.
    These properties can be overridden by the configuration of the destination for the external partner.
    For an AS1 handler
    1. In the Default AS1 MDN return email field, set the default email address.
    2. From the AS1 MDN SMTP server connection list, select the SMTP server connection that describes how to send the MDN response to the specified email address.
    For an AS2 handler
    In the Default AS2 MDN return URL field, set the default URL.
    For an AS3 handler
    In the Default AS3 MDN return URL field, set the default URL.

    For AS2 and AS3, this URL is for the firewall or proxy between the external partner and the B2B gateway. When the firewall or proxy does not forward the MDN, the B2B gateway keeps retransmitting the message to the external partner.

  5. From the Processor type list, set the types of the document routing preprocessor to run against messages that are not received through AS or ebMS protocols.
  6. Optional: If you select to use GatewayScript, click Enable preprocessor GatewayScript debug from action list to detect and diagnose errors in your document routing preprocessor script.
    To debug a file, make sure that the file contains one or more debugger; statements at the points in your script where you want to start debugging.
  7. From the File location list, select a stylesheet or a GatewayScript file to use as the document routing preprocessor.
    You need to create a custom stylesheet or GatewayScript file and select the file from the list.
    • A stylesheet examines information from transport headers and other noncontent sources to select relevant trading partners. The default stylesheet is store:///b2b-routing.xsl.
    • A GatewayScript file examines information from transport headers and payloads to select relevant trading partners. A GatewayScript file can parse messages of different data types, such as JSON, XML, and non-XML. A sample GatewayScript file is store:///gatewayscript/example-b2b-routing.js.
    When the processor type is GatewayScript, the file must end with a .js extension.