Setting configuration properties for inbound communication

The configuration of the general properties for ibound communication is described in Defining general properties in ra.xml and Defining the general properties of the resource adapter in weblogic- ra.xml .

At least one OLTP message-driven bean has to be deployed when using inbound communication. The OLTP message-driven bean must implement one of the following message listener interfaces:

• net.fsc.jca.communication.AsyncOltpMessageListener

• net.fsc.jca.communication.OltpMessageListener

• javax.resource.cci.MessageListener

A deployment descriptor has to be created in the file ejb-jar.xml for deploying the OLTP message-driven bean. If the file ejb-jar.xml is not created automatically by an IDE (Integrated Development Enviroment) during the bean development process, you must create this file manually. Additionally, in most cases, the deployment of an OLTP message-driven bean requires also an application server-specific deployment descriptor. In the case of Oracle WebLogic Server, the application server-specific deployment descriptor is stored in the file weblogic-ejb-jar.xml. Examples of an ejb-jar.xml and an orion-ejb-jar.xml file for an OLTP message-driven bean are shown in Example 8 in Example: weblogic-ra.xml (UPIC) and in Example 9 in Examples for ejb-jar.xml and weblogic-ejb-jar.xml .