This figure shows the runtime architecture of Oracle JMS Web Services. The figure shows a client application that connects by HTTP to an OC4J server. The figure includes an Oracle AQ Database backend, and an independent JMS client.

The figure includes six steps connected by numbered arrows.

  1. The client connects by HTTP to a JMS Servlet within OC4J. The client performs a "Send" operation in this step, sending a message to the JMS Servlet.

  2. The JMS Servlet sends the message to JMS DEST 1. JMS DEST1 is an Oracle OJMS destination (within Oracle AQ).

  3. An OJMS client processes the message on JMS DEST1.

  4. The OJMS client produces a new message on JMS DEST2.

  5. The JMS Web Service client performs a receive operation (step 6), the JMS servlet receives a message from JMS DEST 2 (5) and sends it by HTTP to the JMS client.