1. Payments Weblogic JMS Configuration
  2. Introduction
  3. Introduction

Introduction

Below is brief description on major components in Weblogic JMS Server architecture

JMS Server

JMS server acts as management container for JMS queue and topic resources defined within JMS modules that are targeted to specific that JMS server. A JMS server's main responsibility is to maintain persistent storage for these resources, maintain the state of durable subscriber and 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 configuration. JMS modules are globally available for targeting to servers and clusters configured in the domain and therefore are available to all the applications deployed on the same targeted. 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. When you create a JMS resource you need to choose one Subdeployment.

JMS Resources
  1. Queue: defines a point-to-point destination type, which are used for asynchronous peer communications. A message delivered to queue is distributed to only one customer.
  2. Topic: defines a publish/subscribe destination type, which are used for asynchronous peer communication. A message delivered to topic is distributed to all topic consumers.
  3. Distributed queue: defines a set of queues that are distributed on multiple JMS servers, but are accessible as a single, logical queue to JMS clients.
  4. Distributed topic: defines a set of topics that are distributed on multiple JMS servers, but which as accessible as a single, logical topic to JMS clients.
  5. Uniform Distributed Queue: 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 type of mechanism 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.

Parent topic: Introduction