Dynamic MLLP Adapter
Starting with BizTalk Server 2013 R2, the MLLP adapter properties can be configured at Runtime using a One-Way or Two-Way (Request-Response) send port.
Dynamic Properties
The following properties are in the GlobalPropertySchemas namespace:
| Property | Description |
|---|---|
| Message(MLLP.acceptableACKCodes)=”All ACK Codes”; | Values include: - All ACK Codes - AA and CA - AA, CA, AE and CE - AA, CA, AR and CR This is similar to the Acceptable ACK Codes property in a Static MLLP Send Port. |
| Message(MLLP.CarriageReturn)=”0d”; | ASCII Carriage Return Character |
| Message(MLLP.endBlockDelimiter)=”1c”; | ASCII End Block Character |
| Message(MLLP.startBlockDelimiter)=”0b”; | ASCII Start Block Character |
| Message(MLLP.timeout)=”60000”; | Period after which inactive sending socket on BTAHL7 server will timeout(0 is no timeout) |
| SendPortName(Microsoft.XLANGs.BaseTypes.Address) = “127.0.0.1:11000”; | Address and Port for routing the message |
| SendPortName(Microsoft.XLANGs.BaseTypes.TransportType) = “MLLP”; | Type of Adapter (MLLP) |
Additional
When creating a multipart message in an orchestration for HL7, create the message parts in this following order:
MSH Segment
BodySegments
ZSegments
If you specify the message parts in a different order, the following error occurs:
WrongBodyPartException
The adapter route properties can be specified on the orchestration to support dynamic routing.
See Also
Configuration Parameters for Send and Receive Adapters
MLLP Receive Adapter Processing
MLLP Send Adapter Processing
Processing MLLP-encoded Messages
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for