5-8 Oracle Fusion Middleware Upgrade Guide for Java EE
Oracle WebLogic Server provides direct equivalents for the in-memory and file-based JMS providers.
For more information, see Overview of JMS and WebLogic Server in Oracle Fusion Middleware Configuring and Managing JMS for Oracle WebLogic Server.
5.3.2.2 Creating and Managing JMS Resources in OC4J and Oracle WebLogic Server
In OC4J, you configure JMS connection factories and destinations for a JMS server on an individual OC4J instance. The connection factories and destinations are then
mapped to resource providers or JMS connectors.
In WebLogic Server, you create JMS resources within an WebLogic JMS module. JMS modules are targeted to a WebLogic JMS Server within a domain. WebLogic JMS
servers provide a central point which allows for the configuration of message persistence, durable subscribers, message paging, and quotas for their targeted JMS
destinations.
To upgrade the JMS configuration in your OC4J environment to Oracle WebLogic Server:
1.
Create a set of WebLogic JMS servers with configurations that reflect the OC4J environment’s JMS resource providers, connectors, connection factories and
destination configurations.
2.
Create a WebLogic Server JMS module for each set of JMS connection factories and destinations with common configurations.
3.
Populate the module with JMS connection factories and destinations that have the same JNDI name as their equivalent version in OC4J.
4.
Finally, target the JMS modules to the appropriate WebLogic JMS server within the domain.
For more information, see Oracle Fusion Middleware Configuring and Managing JMS for Oracle WebLogic Server.
5.3.3 Configuring OC4J Remote JMS Resources on Oracle WebLogic Server
In OC4J, you configure remote destinations and connection factories for third-party JMS providers such as WebSphereMQ, Tibco, and SonicMQ as part of a JMS connector
configuration.
In Oracle WebLogic Server, you access remote destinations through the WebLogic Server Foreign Server resources, which enable users to integrate external JMS
providers with WebLogic Server. The Foreign Server resources provide a mapping between a domain’s JNDI tree and external remote JNDI names of JMS destinations
and connection factories.
To upgrade an OC4J external JMS provider configuration to an Oracle WebLogic Server domain, create a JMS module that contains a foreign server. Then create a set of
foreign connection factories and foreign destinations that can serve as a proxy to the remote destinations that need to be accessed from the domain.
For more information, see Configuring Foreign Server Resources to Access Third-Party JMS Providers in the Oracle Fusion Middleware Configuring and Managing
JMS for Oracle WebLogic Server.
