Show TOC Start of Content Area

Background documentation Using JMS Resources from Two and More Applications  Locate the document in its SAP Library structure

Use

There are some cases in which you need to use one and the same JMS resources from more than one application.

Since the jms-resources.xml is part of an enterprise application, all JMS resources are visible only to this particular application, that is, they are local for this application. To use the same JMS resources in two different applications you have to put the same jms-resources.xml in both enterprise applications or to deploy the jms-resources.xml as a standalone application. There is no other way to specify in application’s deployment descriptors that you want to use JMS resources, which are already deployed by another application.

Several applications with the same jms-resources.xml

If you choose to put the same jms-resources.xml in, for example, two enterprise applications, the JMS Connector service, which is responsible for managing the lifecycle of the JMS resources, creates more than one JNDI references for each JMS resource. No matter how many JNDI references are created, the physical JMS resource remains only one. In this way the messages sent to such JMS destination are visible from both applications.

Note

If you have two applications that use the same JMS resources, you have to maintain one and the same file, jms-resources.xml, in two different places, for example two different projects in the Developer Studio.

jms-resources.xml as a standalone application

You can deploy standalone jms-resources.xml, using the Telnet command:

> add jmsconnector

> deploy_jms_resources /path/to/jms-resources.xml

This command is part of the jmsconnector group. In this way the JMS resources become visible for all other applications.

End of Content Area