5-6 Programming Resource Adapters for Oracle WebLogic Server
valueHelloFromsetTestClassPathGoodDayvalue property
property nameunique_ra_idname
valueeisablackbox-xa.oracle.900value property
properties connection-properties
connection-instance connection-definition-group
connection-definition-group connection-factory-interfacejavax.sql.DataSourceCopy
connection-factory-interface connection-instance
jndi-nameeis900eisaBlackBoxXATxConnectorJNDINAME3jndi-name connection-properties
pool-params initial-capacity2initial-capacity
max-capacity10max-capacity capacity-increment1capacity-increment
shrinking-enabledtrueshrinking-enabled shrink-frequency-seconds60shrink-frequency-seconds
pool-params properties
property nameConnectionURLname
valuejdbc:oracle:thin:bcpdb:1531:bay920;create=true;autocommit=falsevalue property
property nameXADataSourceNamename
valueOracleXAPoolBvalue property
property nameTestClassPathname
valueHelloFromsetTestClassPathGoodDayvalue property
property nameunique_ra_idname
valueeisablackbox-xa-two.oracle.900value property
properties connection-properties
connection-instance connection-definition-group
outbound-resource-adapter weblogic-connector
5.3 Configuring Inbound Connections
The J2CA 1.5 Specification http:java.sun.comj2eeconnector
permits you to configure a resource adapter to support inbound message connections. The
following are the main steps for configuring an inbound connection:
1.
Provide a JNDI name for the resource adapter in the weblogic-ra.xml deployment descriptor. See
jndi-name in
Table A–1, weblogic-connector subelements
Connection Management 5-7
2.
Configure a message listener and ActivationSpec for each supported inbound message type in the ra.xml deployment descriptor. For information about
requirements for an ActivationSpec class, see Chapter 12, Message Inflow in the J2CA 1.5 Specification.
3.
Within the packaged enterprise application, include a configured EJB message-driven bean MDB. In the resource-adapter-jndi-name element of
the weblogic-ejb-jar.xml deployment descriptor, provide the same JNDI name assigned to the resource adapter in the previous step. Setting this value
enables the MDB and resource adapter to communicate with each other.
4.
Configure the security identity to be used by the resource adapter for inbound connections. When messages are received by the resource adapter, work must be
performed under a particular security identity. See Section 8.4, Configuring
Security Identities for Resource Adapters.
5.
Deploy the resource adapter as discussed in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.
6.
Deploy the MDB. For more information, see Message-Driven EJBs in Oracle Fusion Middleware Programming Enterprise JavaBeans for Oracle WebLogic Server and
Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.
Example 5–3 shows how an inbound connection with two message listeneractivation
specs could be configured in the ra.xml deployment descriptor:
Example 5–3 Example of Configuring an Inbound Connection
inbound-resourceadapter messageadapter
messagelistener messagelistener-type
weblogic.qa.tests.connector.adapters.flex.InboundMsgListener messagelistener-type
activationspec activationspec-class
weblogic.qa.tests.connector.adapters.flex.ActivationSpecImpl activationspec-class
activationspec messagelistener
messagelistener messagelistener-type
weblogic.qa.tests.connector.adapters.flex.ServiceRequestMsgListener messagelistener-type
activationspec activationspec-class
weblogic.qa.tests.connector.adapters.flex.ServiceRequestActivationSpec activationspec-class
activationspec messagelistener
messageadapter inbound-resourceadapter
5.4 Configuring Connection Pool Parameters
