EIPinCPI – Message Endpoint

December 15, 2019 Bhalchandra Wadekar

This week, we’ll study a pattern as common as Message pattern in messaging known as Message Endpoint.

When do I use this pattern?

Message Endpoint refers to the code that connects to the messaging server and sends or receives messages. Any system that uses messaging to communicate with other systems must write the code to communicate with messaging server, therefore this pattern is one of the most common patterns.

Message Endpoint in CPI

In CPI, I’ll use the JMS Adapter to demonstrate Message Endpoint.

Message Producer


Message Producer

In this simple integration flow, the input is set using a Content ModifierJMS Receiver Adapter is used to send the message to the queue. In this example, the combination of Content Modifier and the JMS Receiver Adapter can be called as a Message Endpoint.

Message Consumer


Message Consumer

In this flow, JMS Sender Adapter is used to read the message from the queue. The Log script logs the message. Here, the code/configuration of JMS Sender Adapter is referred to as Message Endpoint, whereas, the logging can be said to be part of application logic.


Message Endpoint refers to the code in the application that connects to the messaging server and sends or receives the messages.

References/Further Readings

Hope this helps,

About the Author

Bhalchandra Wadekar

Bhalchandra Wadekar is an Integration Enthusiast who authored the Enterprise Integration Patterns in SAP Cloud Platform Integration (#EIPinCPI) series on SAP Blog Community. He is a fan of integration from API Management and Open Connectors to Message Based Integration and Data Integration.

More Content by Bhalchandra Wadekar
Previous Article
EIPinCPI – Canonical Data Model
EIPinCPI – Canonical Data Model

Next Article
EIPinCPI – Messaging Gateway
EIPinCPI – Messaging Gateway