7-2 Programming Resource Adapters for Oracle WebLogic Server
Figure 7–1 Messaging and Transactional Inflow Architecture
7.1.1 Architecture Components
Figure 7–1 contains the following components:
■
A client application, which connects to an application running on WebLogic Server, but which also needs to connect to an EIS
■
An external system in this case, an EIS or Enterprise Information System
■
An application component an EJB that the client application uses to submit outbound requests to the EIS through the resource adapter
■
A message endpoint application a message-driven bean and possibly other J2EE components used for the receipt of inbound messages from the EIS through the
resource adapter
■
The WebLogic Server Work Manager and an associated thread or threads to which the resource adapter submits Work instances to process inbound messages
and possibly process other actions.
■
An external Transaction Manager, to which the WebLogic Server Transaction Manager is subordinate for transactional inflow of messages from the EIS
■
The WebLogic Server Connector container in which the resource adapter is deployed. The container manages the following:
–
A deployed resource adapter that provides bi-directional inbound and outbound communication to and from the EIS.
–
An active Work instance.
Message and Transactional Inflow 7-3
– Multiple managed connections MC1, ..., MCn, which are objects representing
the outbound physical connections from the resource adapter to the EIS.
– Connection handles C-handle returned to the application component from
the connection factory of the resource adapter and used by the application component for communicating with the EIS.
– One of perhaps many activation specifications. There is an activation
specification ActivationSpec that corresponds to each specific message listener type, MLT-j. For information about requirements for an
ActivationSpec class, see Chapter 12, Message Inflow in the J2CA 1.5
Specification http:java.sun.comj2eeconnector
. –
One of the connection pools maintained by the container for the management of managed connections for a given ManagedConnectionFactory in this
case, MCF-2. A Connector container could include multiple connection pools, each corresponding to a different type of connections to a single EIS or even
different EISes.
– A MessageEndpointFactory created by the EJB container and used by the
resource adapter to create proxies to MessageEndpoint instances MDB instances from the MDB pool.
■
An external message source, which could be an EIS or Message Provider
7.1.2 Inbound Communication Scenario
