Messaging Support in Oracle Java Cloud Service - SaaS Extension

This section describes how Oracle Java Cloud Service - SaaS Extension supports messaging.

Using JMS in Oracle Java Cloud Service - SaaS Extension

When an Oracle Java Cloud Service - SaaS Extension instance is deployed, WebLogic JMS servers and destinations are created by default.

When the instance is deployed, one set of a connection factory, queue, and topic are created on each managed server. This allows client applications to use WebLogic JMS out-of-the-box, without having to configure it. Applications can look-up and use the following JNDI names in their applications:

  • local-connection-factory

  • local-queue

  • local-topic

Note that you cannot change or update the local JMS configuration.

The Oracle Java Cloud Service - SaaS Extension SDK includes a Maven plug-in project that allows you to deploy message-driven beans (MDBs) samples on your Oracle Java Cloud Service - SaaS Extension instance. The deployed MDBs will listen on the local destinations (queue and topic) that are automatically created as part of the local JMS configuration. The connection factory is registered in JNDI as local-connection-factory while the queue and topic are registered as local-queue and local-topic, respectively. For more information, navigate to the $SDK_HOME/samples/maven/messagedrivenbean directory (where SDK_HOME is the directory containing your Oracle Java Cloud installation) and open mdb-intructions.html in your web browser.