Configuring Basic JMS System Resources 3-5
more information about the default values for all JMS server options, see JMSServerBean and JMSServerRuntimeMBean in the Oracle WebLogic Server MBean
Reference.
3.4.2 JMS Server Targeting
You can target a JMS server to either an independent WebLogic Server instance or to a migratable target server where it will be deployed.
■
Weblogic Server instance — Server target where you want to deploy the JMS server. When a target WebLogic Server boots, the JMS server boots as well. If no
target WebLogic Server is specified, the JMS server will not boot.
■
Migratable Target — Migratable targets define a set of WebLogic Server instances in a cluster that can potentially host an exactly-once service, such as a JMS server.
When a migratable target server boots, the JMS server boots as well on the specified user-preferred server in the cluster. However, a JMS server and all of its
destinations can be migrated to another server within the cluster in response to a server failure or due to a scheduled migration for system maintenance. For more
information on configuring a migratable target for JMS services, see
Section 4.2, Migration of JMS-related Services.
For instructions on specifying JMS server targets using the Administration Console, see Change JMS server targets in the Oracle WebLogic Server Administration Console
Help. For JMS Server targeting best practices, see Section 9.2, Targeting Best Practices.
3.4.3 JMS Server Monitoring Parameters
You can monitor run-time statistics for active JMS servers, destinations, and server session pools.
■
Monitor all Active JMS Servers — A table displays showing all instances of the JMS server deployed across the WebLogic Server domain.
■
Monitor all Active JMS Destinations — A table displays showing all active JMS destinations for the current domain.
■
Monitor all Active JMS Session Pool Runtimes — A table displays showing all active JMS session pools for the current domain.
For more information about monitoring JMS objects, see Chapter 8, Monitoring JMS
Statistics and Managing Messages.
3.4.4 Session Pools and Connection Consumers
Server session pools enable an application to process messages concurrently. After you define a JMS server, you can configure one or more session pools for each JMS server.
Some session pool options are dynamically configurable, but the new values do not take effect until the JMS server is restarted. See Defining Server Session Pools in
Programming JMS for Oracle WebLogic Server.
Note: Session pool and connection consumer configuration objects
were deprecated in WebLogic Server 9.x. They are not a required part of the J2EE specification, do not support JTA user transactions, and
are largely superseded by Message-Driven Beans MDBs, which are a required part of J2EE. For more information on designing MDBs, see
Programming Message-Driven Beans for Oracle WebLogic Server.
3-6 Configuring and Managing JMS for Oracle WebLogic Server
Connection consumers are queues Point-to-Point or topics PubSub that will retrieve server sessions and process messages. After you define a session pool,
configure one or more connection consumers for each session pool. See Defining Server Session Pools in Programming JMS for Oracle WebLogic Server.
3.5 JMS System Module Configuration
