About JMS Web Services

JDeveloper lets you create web services that let you put messages on and take messages off JMS destinations. One specific application of this is to create JMS web services from message-driven beans (MDB), a type of Enterprise JavaBean that listens for messages on a JMS destination and acts according to the content of the message.

Each JMS web service is configured to transfer messages to and from a specific JMS destination or pair of destinations. A JMS web service can have the following operations:

A service can offer both operations, and on any single service you can choose whether the send and receive operation act upon the same JMS destination. In the case where they do not, the send operation will set JMS properties on sent messages that indicate the JMS destination on which responses are expected.

JMS web services can be deployed to Oracle Application Server and Oracle Application Server Containers for J2EE (OC4J). OC4J/JMS is not supported in Oracle9iAS 9.0.3 or OC4J 9.0.3. OJMS is the JMS interface onto Oracle AQ in the database, and it is Oracle's J2EE 1.3 compliant JMS provider.

To run a JMS web service deployed to OC4J 9.0.3 or Oracle9iAS 9.0.3, you should configure OC4J to hand over the JMS implementation to OJMS. For more information, refer to "Oracle9iAS Containers for J2EE (OC4J) - Java Message Service (JMS) - Frequently Asked Questions" on the Oracle Technology Network at http://www.oracle.com/technology/tech/java/oc4j/htdocs/OC4J-JMS-FAQ.html .

For more information about JMS, refer to Oracle Application Server Containers for J2EE User's Guide: Part Number B10322-01 which is available as part of the Oracle Application Server 10g documentation set, or at the Oracle Technology Network at http://www.oracle.com/technology/documentation/appserver10g.html.


Deploying to the Oracle Application Server or Standalone OC4J
Deploying Web Services

 

Copyright © 1997, 2004, Oracle. All rights reserved.