1.1 Purpose of Major Components

This topic explains the steps required for JMS configuration in cluster mode.

  1. Oracle Banking Corporate Lending
  2. WebLogic Server 12.1.3.0.0

JMS Server

The JMS server acts as a management container for the JMS queue and topic resources defined within JMS modules that are targeted to specific JMS servers. A JMS server's main responsibility is to maintain persistent storage for these resources, maintain the state of the durable subscriber, etc. JMS servers can host a defined set of modules and any associated persistent storage that reside on a WebLogic Server instance.

JMS Module

JMS modules are application-related definitions that are independent of the domain environment. JMS modules group JMS configuration resources (such as queues, topics, and connections factories). These are outside domain configurations. JMS modules are globally available for targeting servers, and clusters configured in the domain, and therefore are available to all the applications deployed on the same target. JMS modules contain configuration resources, such as standalone queue and topic destinations, distributed destinations, and connection factories.

Subdeployment

Subdeployment is also known as Advanced Targeting. Subdeployment resource is a bridge between the group of JMS resources and JMS Servers. While creating a JMS resource, the user needs to choose one Subdeployment.

JMS Resources

Table 1-1 JMS Resources- Description

JMS Resources Description
Queue This defines a point-to-point destination type, which is used for asynchronous peer communications. A message delivered to the queue is distributed to only one customer.
Topic This defines a publish/subscribe destination type, which is used for asynchronous peer communication. A message delivered to the topic is distributed to all topic consumers.
Distributed queue This defines a set of queues that are distributed on multiple JMS servers, but are accessible as a single, logical queue to JMS clients.
Distributed topic This defines a set of topics that are distributed on multiple JMS servers, but which are as accessible as a single, logical topic to JMS clients.
Uniform Distributed Queue This queue members are created uniformly from a common configuration.

Persistence store

A persistent store provides a built-in, high-performance storage solution for WebLogic Server subsystems and services that required persistence. There are two types of mechanisms to store the message -
  1. File-based persistence store - Message is stored in a file
  2. DB-based persistence store - Message is stored in Database.