Enterprise Integration Pattern Part 7 of 7[Message Endpoint]

Message Endpoint

Message Endpoint! This is just a code piece of code which sits between the data application and the message channel. The R&R (role and responsibility) of this module is to:

1. Interpret the data coming from the Data Application. This can be as simple as calling a Java method from data application which sits inside another Java class. Can be implemented in a number of ways though!
2. Creates a connection to the message channel to which the Data application is intended to connect and receive the data.
3. Creates a message structure and populates the same with the contents from the Data Application.
4. Transmits the message to the Message Channel
5. If allowed, wait for the response and respond back to the Data Application if this is a 2-way communication.

The same is applicable on the Receiver applications side.

Hence we can classify Message Endpoint as:

1. Consumer End Point [Also known as “Out-bound Connector/Adapter”]
2. Receiver End Point [Also known as “In-bound Connector/Adapter”]

I hope you like the explanation. Share your thoughts on the same.