Configuration Checklists

The following sections provide monitoring checklists for various WebLogic JMS features:

For more information on setting the configuration attributes, see "Configuring JMS" in the Administration Console Online Help.

 

Server Clusters

To support server clusters, configure the following:

  • Target a connection factory to one or more independent server instances, to all servers in a cluster, or to selected servers in a cluster on the Target and Deploy tab on the Connection Factories node
  • Target a JMS server to an independent server instance or to migratable target on the Target and Deploy tab on the JMS Servers node

 

JTA User Transactions

To support JTA user transactions, configure the following:

  • Connection factory JTA user transaction mode by selecting the XA Connection Factory Enabled check box under the Configuration - Transactions tab on the Connection Factories node

 

JMS Transactions

To support JMS transacted sessions, configure the following:

  • Connection factory transaction timeout value by setting the Transaction Timeout attribute under the Configuration - Transactions tab on the Connection Factories node
  • Session pool transaction mode by selecting the Transacted check box under the Configuration tab on the Session Pools node

 

Message Delivery

To define message delivery attributes, configure the following:

  • Connection factory priority, time-to-live, time-to-deliver, and delivery mode attributes under the Configuration - General tab on the Connection Factories node
  • Destination priority, time-to-live, time-to-deliver, and delivery mode override attributes under the Configuration - Overrides tab on the Destinations node
  • Destination redelivery delay, redelivery limit, and error destination attributes under the Configuration - Redelivery tab on the Destinations node
Note that these settings can also be set dynamically by the message producer when sending a message or using the set methods, as described in Sending Messages.

The destination configuration attributes take precedence over all other settings.

 

 

Asynchronous Message Delivery

To define the maximum number of messages that may exist for an asynchronous session and that have not yet been passed to the message listener, configure the following:

  • Message maximum attribute under the Configuration - General tab on the Connection Factories node

 

Persistent Messages

Note: Topic destinations are persistent if - and only if - they have durable subscriptions. For more information about durable subscriptions, see Setting Up Durable Subscriptions.

To support persistent messaging, configure the following:

  • Create a JMS file store or JMS JDBC store using the Stores node.
  • Select the file or JDBC store on the JMS server by using the Store attribute on the Configuration - General tab on the JMS Servers node.

    Note: No two JMS servers can use the same backing store.

  • Establish the default message delivery mode by setting one of the following attributes to Persistent:

    • Default Delivery Mode attribute under the Configuration - General tab on the Connection Factories node.
    • Delivery Mode Override attribute under the Configuration - Overrides tab on the Destination node. (This setting can also be set to No Delivery. If no JMS template is specified for this destination, then No-Delivery means the Delivery Mode will not be overridden. Otherwise, No-Delivery means that the value comes from the JMS.

      Note: You can also specify persistent as the delivery mode when sending messages, as described in Sending Messages.

 

Concurrent Message Processing

To support concurrent message processing, configure the following:

  • Server session pool attributes under the Configuration tab on the Session Pools node
  • Connection consumer attributes under the Configuration tab on the Connection Consumers node

Note: Server session pool factories, used for concurrent message processing, are not configurable. WebLogic JMS defines one ServerSessionPoolFactory object, by default: weblogic.jms.ServerSessionPoolFactory:<name>, where <name> specifies the name of the JMS server on which the session pool is created. For more information about using server session pool factories, refer to Defining Server Session Pools.

 

Multicasting

Note: Multicasting applies to topics only.

To configure multicasting on a topic, configure the following:

  • Multicast address, multicast port, and multicast time-to-live (TTL) under the Configuration - Multicast tab on the Destination node
  • Maximum number of outstanding messages by setting the Messages Maximum attribute under the Configuration - General tab on the Connection Factories node
  • Overrun policy used when the number of outstanding messages reaches the Messages Maximum value by setting the Overrun Policy attribute under the Configuration - General tab on the Connection Factories node

 

Durable Subscriptions

To support durable topic subscriptions, configure the following:

  • Create a JMS file store or JMS JDBC persistent store using the Stores node.
  • Target the configured store to your JMS server by selecting it from the Store attribute's drop-down list on the JMS Server - > Configuration - > General tab.

    Note: No two JMS servers can use the same backing store.

  • Set the client ID on either a JMS connection factory or in the topic connection, as follows:

    • One method is to configure a connection factory with the client identifier (client ID). For WebLogic JMS, this means configuring a separate connection factory instance for each client ID. Then, on each connection factory, specify a unique client ID for clients with durable subscriptions using the Client ID attribute on the Connection Factory - > Configuration - > General tab. Applications then look up their own topic connection factories in JNDI and use them to create connections containing their own client IDs.
    • The other "preferred" method is for an application that can set its client ID in the topic connection after the connection is created by calling a connection method, as described in Setting Up Durable Subscriptions. By using this alternative approach, you can use the default connection factory (if it is acceptable for your application) and avoid the need to modify the configuration information.

 

Destination Sort Order

To support destination sort order, configure the following:

  • Key attributes under the Configuration tab on Destination Keys node
  • Destination Keys under Configuration - General tab on Destinations node

 

Temporary Destinations

To support temporary destinations (queue or topic), configure the following:

  • A JMS template for the JMS server (in the same domain) under the Configuration - General tab on the Templates node
  • A JMS template to be used by the JMS server for temporary destinations by setting the Temporary Template attribute for the JMS server under the Configuration - General tab on the JMS Servers node

 

Thresholds and Quotas

To configure thresholds and quotas, configure the following:

  • Message and byte thresholds and quotas (maximum number, and high and low thresholds) under the Configurations - Thresholds tab on the JMS Server node
  • Message and byte thresholds and quotas (maximum number, and high and low thresholds) under the Configurations - Thresholds tab on the Destination node
  • Maximum number of sessions that can be retrieved from a session pool by setting the Sessions Maximum attribute under the Configurations tab on the Session Pools node
  • Maximum number of messages that can be accumulated by a connection consumer by setting the Messages Maximum attribute under the Configuration tab of the Consumers node

Skip navigation bar  Back to Top Previous Next