JMS Server Configuration Parameters

3-4 Configuring and Managing JMS for Oracle WebLogic Server

3.4 JMS Server Configuration

JMS servers are environment-related configuration entities that act as management containers for JMS queue and topic resources within JMS modules that are specifically targeted to JMS servers. A JMS servers primary responsibility for its targeted destinations is to maintain information on what persistent store is used for any persistent messages that arrive on the destinations, and to maintain the states of durable subscribers created on the destinations. As a container for targeted destinations, any configuration or run-time changes to a JMS server can affect all of its destinations.

3.4.1 JMS Server Configuration Parameters

The WebLogic Server Administration Console enables you to configure, modify, target, and delete JMS server resources in a system module. For a road map of the JMS server tasks, see Configure JMS servers in the Oracle WebLogic Server Administration Console Help. You can configure the following parameters for JMS servers: ■ General configuration parameters, including persistent storage, message paging defaults, a template to use when your applications create temporary destinations, and expired message scanning. ■ Threshold and quota parameters for destinations in JMS system modules targeted to a particular JMS server. For more information about configuring messages and bytes quota for JMS servers and destinations, see Performance and Tuning for Oracle WebLogic Server. ■ Message logging parameters for a JMS servers log file, which contains the basic events that a JMS message traverses, such as message production, consumption, and removal. For more information about configuring message life cycle logging on JMS servers, see Section 10.3, Message Life Cycle Logging. ■ Destination pause and resume controls that enable you to pause message production, message insertion in-flight messages, and message consumption operations on all the destinations hosted by a single JMS Server. For more information about pausing message operations on destinations, see Section 10.5, Controlling Message Operations on Destinations. Some JMS server options are dynamically configurable. When options are modified at runtime, only incoming messages are affected; stored messages are not affected. For Note: WebLogic Domain, WebLogic Server, and WebLogic JMS Server names have additional unique naming requirements when two different WebLogic domains interoperate with each other, or when a client communicates with more than one WebLogic domain. See Section 9.3, Integration and Multi-Domain Best Practices. Note: A sample examplesJMSServer configuration is provided with the product in the Examples Server. For more information about developing basic WebLogic JMS applications, refer to Developing a Basic JMS Application in Programming JMS for Oracle WebLogic Server. 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