Modify an AS4 embedded server pickup

When you add a trading pickup, the wizard prompts you to provide a basic set of parameters. After you create the pickup, you can open the maintenance page for the pickup to view and manage a comprehensive set of parameters. Some of these parameters were automatically set when you added the object, and can only be modified after you add the object.

Procedure

  1. In the Interchange user interface, select Trading configuration > Manage trading configuration.
  2. From the list of communities, click the name of a community to display the Summary page for that community.
  3. Click Trading pickup in the navigation graphic to open the community's Trading pickups page.
  4. From the list of available pickups, click the name of an AS4 (embedded)  pickup to open the maintenance page for that pickup.
  5. View and modify fields as required. The fields are described in the following section.
  6. After making any modifications, click Save changes.

AS4 trading pickup (embedded) maintenance fields

HTTP (embedded) settings tab

Click the Global HTTP server link to view the HTTP server configuration.

The Local URL field displays the local port and path the embedded HTTP server uses. A server starts on each computer in the cluster using this information. If you have only one computer, only one server is started.

The URL used by partners field displays the URL that your partners use to send AS4 messages to this exchange.

Accounts tab

Use the settings on this tab to create accounts to provide name and password information for the use of user-name tokens in the SOAP headers of AS4 messages that you consume.

You can create two different types of users on this tab:

  • AS4 user – This is an account that globally represents an AS4 remote trading partner. This is not limited to a specifically-defined remote partner. For security reasons it is generally preferable to use the Partner user account, below.
  • Partner user – This is an account that specifies the authentication information of a specific user account of a remote trading partner.

You can use either account type to provide a user-name token in an AS4 message you send.

To create a new Partner account:

  1. Under the Partner table, click Add.
  2. In the text box. click the text "click choose a party" and from the popup page, select the partner from whom you want to receive pushed AS4 files. Click OK.
  3. Create a user for the selected partner by entering a username and password. Click Save.

To create a AS4 (global community) account:

  1. Under the AS4 table, click Add.
  2. Click Create a new user.
  3. Enter a username and password. Click Save.

Advanced tab

Use the settings on this tab to specify how to process the inbound messages that you consume through this pickup.

Header section:

  • Parse SOAP headers into message metadata – Select this option if you want SOAP headers to be carried as metadata attributes with the message.
  • XPath reference to SOAP header to parse – If you selected the previous option (Parse SOAP headers into message metadata), enter an XPath expression to resolve the header.
  • Click Add to display the Local XPath field and then enter an XPath expression. Enter any legal XPath expression. Xpath wildcard syntax is permitted. If the expression resolves to more than one node, only the value of the first matching node is included in the metadata value.

Body / Attachments section:

  • Process SOAP body – Select this option to process the contents of the SOAP body of the consumed message.
  • Process attachments – Select this option to process the attachments of the consumed SOAP message.

Processing section:

  • Generate receipt – You must select this option if the sending participant is expecting AS4 receipts. If the sending participant expects receipts but you do not select this option, the message exchange will fail and a receipt failure message will be written to the TE.LOG or to Message Tracker of the AS4 user message sender.
    • Synchronous response generated in back end – Select this option to have the back-end application generate synchronous responses.
    • If this option is not selected, the synchronous response is generated within Interchange. By default, this option is not selected.
    • If this option is selected, Interchange keeps the inbound HTTP connection open so a synchronous response can be built by the back-end system. The response built by the backend uses the message ID that was generated by the inbound AS4 user message, to send back the response in the form of a receipt. Once Interchange receives it, the response is packaged and sent over the open HTTP connection.
    • If selected, you must create a receipt or error MMD for Interchange to pick up from the backend.
  • Restrict maximum file size for this transport – Optionally specify the maximum size of files that this transport can handle. If the trading engine receives a file larger than the maximum, the file is rejected and a message is written to the events log.

Related topics

Related Links