Message Inflow Scenario

Purpose

This example scenario is based on a resource adapter for a Telnet client. The endpoint for the messages that the Telnet client sends is a message-driven bean deployed on the SAP AS Java. The bean also implements the message listener interface provided by the resource adapter.

On message receipt, the bean uses the outbound communication function of the resource adapter to get a connection to an external system where it sends the message.

Communication Implementation

Figure 1 represents the communication between the components in this scenario. The application server-side provides the EndpointActivationImpl, which is an implementation of the com.sap.engine.interfaces.endpoint.EndpointActivation interface. It enables the SAP AS Java to invoke the endpointActivation() and endpointDeactivation() methods on the resource adapter JavaBean. With this invocation the server provides an instance of a MessageEndpointFactory, on which the resource adapter invokes createEndpoint() . This creates a server-side proxy to the message-driven bean, that also enables the message endpoint to send transactional notifications to an EIS when a message is processed. To send the messages, the bean uses the onStrReceived() method, which is inherited from the message listener interface that the resource adapter provides. After processing the message, the MDB uses an outbound resource adapter to send a message to the EIS.