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 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.

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 consumes from back-end applications and 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 <B2Bi_shared_directory>\common\data\backup, unless you specify otherwise.
  • Message processing
  • Select an option to set the processing mode for messages consumed on this pickup:
    • Limited – Use only message handler and community delivery settings for message processing and routing.
    • Standard – Perform message processing and ignore community delivery settings. This option enables the full array of B2Bi processing options.
  • Restrict maximum file size for this transport – Use this option to specify the maximum size of files a transport can handle.
  • If the pickup consumes a file larger than the specified maximum, the file is rejected and a message is written to the events log.
  • Express the maximum size in bytes. Do not use commas. For example, a kilobyte is 1024 bytes, a megabyte is 1048576 bytes, a gigabyte is 1073741824 bytes. The smallest maximum allowed is 1000 bytes. On the opposite extreme, you can enter the largest number the field can accommodate.
  • Override reported message direction – Select this option to override the default Direction value that is reported to Sentinel. You can then select the direction value to apply to the processing of all messages that are consumed by this pickup:
    • Inbound
    • Outbound
    • Internal
    • External
  • For details about this feature, see Override flow direction reporting to Sentinel.
  • 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, B2Bi waits before polling for messages to retrieve.

Related topics

Related Links