Skip to main content
Feedback

MLLP Server operation

The MLLP Server operation contains the inbound MLLP settings and preferences for communicating with a specific trading partner. Your trading partner should provide the information to configure the operation.

MLLP Info tab

The MLLP Info tab content changes depending on which Route by setting you choose. If you choose to route by data identifiers (default), select the document standard and enter the sender and receiver information as appropriate for the standard. If you choose to route by Route Key, you can add the routing key that you configured on the MLLP Server Settings panel and users who have permission to access those ports. For more information about routing, refer to the Boomi Community article How MLLP Server Document routing works.

The operation supports only the Listen action.

  • Route by - You can route by data identifiers extracted from EDI messages received on any port or by routing keys associated with the port in the MLLP Server.

Route by data identifiers

  • Document Standard - Select HL7 or X12 as the document standard.

Identify the sending trading partner in the From Identifiers section:

HL7 standardX12 standard
From Application - Sending trading partner's application ID.Sender Interchange ID - Sending trading partner's Interchange ID.
From Facility - Sending trading partner's facility ID.Sender Interchange ID Qualifier - Sending trading partner's Interchange ID Qualifier.
  • Client SSL Certificate - The client SSL certificate.

Identify the receiving trading partner in the To Identifiers section:

HL7 standardX12 standard
To Application - Receiving trading partner's application ID.Receiver Interchange ID - Receiving trading partner's Interchange ID.
To Facility - Receiving trading partner's facility ID.Receiver Interchange ID Qualifier - Receiving trading partner's Interchange ID Qualifier.

Route by route key

If you choose Route Key for the Route by setting, configure the following:

  • Route Key - Enter the value associated with one or more ports in the Boomi runtime where the process will be deployed. For more information about routing keys, refer to MLLP Server Settings panel.

  • Trusted CAs - Trusted CAs are added to the global MLLP Server trust store. The client certificate presented in the SSL handshake must match exactly one of the users configured in the user list or be signed by one of the Trusted CA certificates for the listener to be invoked. Enter a username (required) and an SSL certificate (optional) for each.

  • Users - Add users and enter a username (required) and an SSL certificate (optional) for each.

Important

If you add SSL certificates to users or Trusted CAs, each must have a different SSL certificate.

Options section

The following settings are available for both HL7 and X12 document standards:

  • Auto Acknowledge? - Determines whether the MLLP Server automatically acknowledges received documents. When enabled for an HL7 transmission, an Accept ACK message is generated when also requested by the sender in the MSH.15 header value. When enabled for an X12 message, a simple interchange with a TA1 segment is generated when also requested by the sender in the ISA.14 header value. For more information, refer to the Boomi Community article How Acknowledgments Work in the MLLP Server Connector.

    Enable additional MSH fields

    You can use the custom property com.boomi.connector.mllpserver.useAdditionalAckFields to receive additional MSH fields in HL7 messages. Refer to Properties panel, custom tab for information about setting custom properties.

    The default value for this property is false. When false, the MSH header reflects the original message's version ID and contains fields up through to the MSH.12 Version ID.

    When set to true, the version of the ACK message matches the version of the received HL7 message. Fields are set up through MSH.24 as appropriate for the specified version.

    FieldValue
    MSH.13 Sequence NumberNot supported by Boomi. Value is an empty string.
    MSH.14 Continuation PointerNot supported by Boomi. Value is an empty string.
    MSH.15 Accept Acknowledgment TypeAlways set to "NE" (never) as acknowledgments are not acknowledged.
    MSH.16 Application Acknowledgment TypeAlways set to "NE" (never) as acknowledgments are not acknowledged.
    MSH.17 Country CodeSet to the country code of the operating system where the runtime is installed.
    MSH.18 Character SetSet to the runtime's default character set.
    MSH.19 Principal Language Of MessageSet to the language of the operating system where the runtime is installed.
    MSH.20 Alternate Character Set Handling SchemeNot supported by Boomi. Value is an empty string.
    MSH.21 Message Profile IdentifierResponds with the value of the originator's MSH.21 field.
    MSH.22 Sending Responsible OrganizationResponds with the value of the originator's MSH.22 field.
    MSH.23 Receiving Responsible OrganizationResponds with the value of the originator's MSH.23 field.
    MSH.24 Sending Network AddressResponds with the value of the originator's MSH.24 field.
    MSH.25 Receiving Network AddressResponds with the value of the originator's MSH.25 field.
    note

    This property does not affect acknowledgment messages generated by the Trading Partner HL7 connector.

  • Log Messages? - If selected, messages are logged in the outbound work/MLLP folder of the basic runtime.

Archiving tab

See the topic Connector operation’s Archiving tab for more information.

Tracking tab

See the topic Connector operation’s Tracking tab for more information.

Response codes for non-standard data

If the Route By key calls a process and Auto Acknowledge is enabled, the server sends responses based on the standard used in the document: an ACK message for HL7 and an interchange with a TA1 segment for X12. However, if the standard is neither HL7 nor X12, a plain text code is sent in the response.

For HL7, the code is returned as a string in the MSA.3 segment and for X12, the TA1.05 segment.

CodeCondition
OKProcess execution is successful, Auto Acknowledge is enabled
ERR_ROUTEUnable to return a route between the MLLP server and listener process by data identifier or route key
ERR_CERTThe client certificate does not match the listener process certificate
ERR_PROCESSProcess execution failed, Auto Acknowledge is enabled
note

ERR_ROUTE and ERR_CERT acknowledgments are not controlled by by the Auto Acknowledge setting. If you want to turn off acknowledgments for these errors, you must set the custom property com.boomi.connector.mllpserver.autoAckOnError to false on the basic runtime.

For more information about MLLP Server acknowledgments, refer to the Boomi Community article How Acknowledgments work in the MLLP Server connector.

On this Page