bea.com | products | dev2dev | support | askBEA |
|
e-docs > WebLogic Server > Programming WebLogic JMS > Configuration Checklists |
Programming WebLogic JMS |
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.
To support server clusters, configure the following:
To support JTA user transactions, configure the following:
To support JMS transacted sessions, configure the following:
To define message delivery attributes, configure the following:
Note: 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.
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:
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:
Note: You can also specify persistent as the delivery mode when sending messages, as described in Sending Messages.
To support concurrent message processing, configure the following:
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.
Note: Multicasting applies to topics only.
To configure multicasting on a topic, configure the following:
To support durable subscriptions, optionally configure the following:
Note: Alternatively, clients can set the client ID in the connection after the connection is created, as described in Setting Up Durable Subscriptions.
To support destination sort order, configure the following:
To support temporary destinations (queue or topic), configure the following:
To configure thresholds and quotas, configure the following: