Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Configuring inbound communication

&pagelevel(3)&pagelevel

The configuration of the general properties for ibound communication is described in Defining general properties in 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. Example of an ejb-jar.xml for an OLTP message-driven bean is shown in Example 3 in Examples for ejb-jar.xml.