Modify an MLLP trading pickup

After you create an MLLP trading 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. See MLLP (embedded) fields .
  • 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. See MLLP (embedded) fields .
  • 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.

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 Activator receives a file larger than the maximum, the file is rejected and a message is written to the events log.

Related Links