Add or modify an MLLP application pickup

About application pickups for MLLP

A community application pickup is an object that specifies how you want your local community to consume messages from a back-end application. In this case, Interchange is in a server role, consuming an MLLP client application request.

Add an MLLP application pickup

Prerequisite

You must have a community defined.

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 Application pickup in the navigation graphic to open the Application pickups page.
  4. Click Add an application pickup.
  5. Choose the message protocol No packaging and click Next.
  6. Complete the From address page and click Next.
  7. Complete the To address page and click Next.
  8. On the Choose transport protocol page, select MLLP and click Next.
  9. Configure the MLLP server:
    • Server name – Server name, for example MyServer.
    • Port – MLLP Server access port on your hosting machine.
    • Clients must use TLS to connect to this server – Select this option if you require TLS for this connection.
    • This server requires client authentication. The partner must present an authentication certificate trusted by the server when connecting – If you selected the TLS requirement option above, select this option to require your partners to submit a certificate to verify their identity before the pickup allows the connection. Clear this option to use non-authenticated MLLP. If you select this option, you must add an authentication certificate for the partner.
  10. Enter a name for the pickup to identify it in the user interface. Hint: Enter a name that is easily identifiable in a list of pickups in the user interface.
  11. Click Finish.

Modify an MLLP application pickup

After you create an MLLP application pickup, you can view and modify fields that define the pickup.

MLLP (embedded) settings tab

  • Embedded MLLP server – Name of the embedded MLLP server. To make changes in the embedded server name or connection parameters, click View settings for this embedded server.
  • Local URL – You cannot modify this setting from this page. 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.
  • URL used by partners – The URL used by MLLP client partners to connect to this server. This URL is part of the partner profile when you export it. The host, port and path may be different than the values in the local URL. If your network uses a load balancer or firewall, contact your network administrator for the correct value.

MLLP TLS (embedded) settings tab

  • Embedded MLLP TLS server – Name of the embedded MLLP server. To make changes in the embedded server name or connection paramters, click View settings for this embedded server.
  • Local URL – You cannot modify this setting from this page. 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.
  • URL used by partners – The URL used by MLLP client partners to connect to this server. This URL is part of the partner profile when you export it. The host, port and path may be different than the values in the local URL. If your network uses a load balancer or firewall, contact your network administrator for the correct value.

From address tab

See From address and To address tabs.

To address tab

See From address and To address tabs.

Message attributes tab

See Message attributes tab.

EDI Splitter tab

See EDI splitter tab.

Inline processing tab

See Inline processing tab.

Schedule tab

See Schedule tab.

Advanced tab

  • Back up the files that go through this transport – Indicates whether the system backs up copies of the messages it retrieves from integration or receives from partners.
  • Backing up files is strongly recommended. This is required for the system to perform fail-over operations such as attempting to send messages again (retries) in case of a transport connection failure. Without backups, a message in process cannot be recovered if the server or a processing node stops or restarts. Backups also are needed if you want the ability to resubmit messages to back-end applications or resend messages to partners. Backup files are stored in \<install directory>\common\data\backup, unless you specify otherwise.
  • Restrict maximum file size for this transport – Optionally specify the maximum size of files that this transport can handle. If Interchange receives a file larger than the maximum, the file is rejected and a message is written to the events log.
  • Maximum files per polling interval – The highest number of messages the system can retrieve each time it polls.
  • Polling interval (seconds) – The interval, in seconds, Interchange waits before polling for messages to retrieve.

Related topics

Related Links