bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

JMS

In the JMS area of the Administration Console, you can configure and monitor JMS servers, connection factories, destinations (physical queues and topics), distributed destinations (sets of physical queue and topic members within a WebLogic Server cluster), destination templates, destination sort order (using destination keys), persistent stores, session pools, and connection consumers.

You can also accomplish the following tasks:

- Set up custom JMS applications.

- Define thresholds and quotas.

- Enable any desired JMS features, such as server clustering, concurrent message processing, destination sort ordering, persistent messaging, message paging, message flow control, and message load balancing.

JMS Server Tasks

A JMS server manages connections and message requests on behalf of clients. You must first configure a JMS server before you can configure any destinations or consumers.

Create a JMS Server

1. Expand the JMS node and the Servers node. The JMS Servers table displays in the right pane showing all the JMS servers defined in your domain.

2. Click the Configure a new JMS Server text link. A dialog displays in the right pane showing the tabs associated with configuring a new JMS server.

3. On the Configuration General tab, enter values in the Name, Store, Paging Store, and Temporary Template attribute fields. For more information about JMS server general attributes, see Attributes.

4. Click Create to create a JMS server instance with the name you specified in the Name field. The new instance is added under the JMS Servers node in the left pane. A Destinations node and a Session Pools node are automatically added under the new server instance by default.

5. On the Configuration Thresholds & Quotas tab, enter values in the Bytes and/or Messages Maximum, Threshold, and Paging attribute fields. For more information about the Thresholds & Quota attributes, see Attributes. Click Apply to save your changes.

6. On the Targets tab, target a server target instance or a migratable target on which to deploy the JMS server, as explained in Assign a JMS Server.

7. Click Apply to assign the JMS server.

Clone a JMS Server

1. Expand the JMS node and the Servers node.

2. The JMS Servers table displays in the right pane showing all the JMS servers defined in your domain.

3. Click the Clone icon in the row of the JMS server that you want to clone. A dialog shows the tabs associated with cloning a JMS server.

4. On the Configuration General tab, enter values in the Name, Store, Paging Store, and Temporary Template attribute fields. For more information about JMS server general attributes, see Attributes.

5. Click Create to create a JMS server instance with the name you specified in the Name field. The new instance is added under the JMS Servers node in the left pane. A Destinations node and a Session Pools node are automatically added under the new server instance by default.

6. On the Configuration Thresholds & Quotas tab, enter values in the Bytes and/or Messages Maximum, Threshold, and Paging attribute fields. For more information about the Thresholds & Quota attributes, see Attributes. Click Apply to save your changes.

7. On the Targets tab, assign the JMS server to a server target instance or to a migratable target.

   For more information, see Assign a JMS Server.

Assign a JMS Server

1. Under the JMS Servers node in the left pane, click the node for the JMS server instance that you want to assign. A dialog displays in the right pane showing the tabs associated with this instance.

2. Click the Targets tab.

3. Complete the following steps for the Servers and/or Migratable Servers tabs:

   1. Servers tab—On the Targets list, select the 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.

   2. Migratable Servers tab—On the Targets list, select the migratable target where you want to deploy the JMS server. Migratable targets define a set of WebLogic Server instances in a cluster that can potentially host an exactly-once service, such as JMS. When a migratable target server boots, the JMS server boots as well on the user-preferred server in the cluster. However, a JMS server and all of its destinations can migrate to another server within the cluster in response to a server failure or due to a scheduled migration or system maintenance.

4. Click Apply to save your assignments.

Delete a JMS Server

1. Expand the JMS node and the Servers node.

2. The JMS Servers table displays in the right pane showing all the JMS servers defined in your domain.

3. Click the Delete icon in the row of the JMS server that you want to delete. A dialog prompts you to confirm your deletion request.

4. Click Yes to delete the JMS server. The JMS server instance under the Servers node is deleted.

Monitor All Active JMS Connections

1. Expand the Servers node.

2. Select the WebLogic Server instance where you want to monitor JMS connections.

3. Select the Monitoring tab in the right pane.

4. Select the JMS tab. Totals for JMS server and connection statistics are displayed in the JMS dialog.

5. Click the Monitor all Active JMS Connections text link. A table displays showing all active JMS connection for the server.

Monitor All Active JMS Servers

1. Expand the JMS node.

2. Click the Servers node. The JMS Servers information displays in the right pane showing all the JMS servers defined in your domain.

3. Click the JMS server that you want to monitor from the JMS server list, or from the JMS Servers table displayed in the right pane.

4. Click the Monitoring tab to display the monitoring data.

5. Click the Monitor all Active JMS Servers text link in the right pane. A table displays showing all instances of the JMS server deployed across the WebLogic Server domain.

Monitor All Active JMS Destinations

1. Expand the JMS node and the Servers node.

2. The JMS Servers table displays in the right pane showing all the JMS servers defined in your domain.

3. Click the JMS server that you want to monitor from the JMS server list, or from the JMS Servers table displayed in the right pane.

4. Click the Monitoring tab to display the monitoring data.

5. Click the Monitor all Active JMS Destinations text link. A table displays in the right pane showing all active JMS destinations for the current domain.

Monitor All Active JMS Session Pools

1. Expand the JMS node and the Servers node.

2. The JMS Servers table displays in the right pane showing all the JMS servers defined in your domain.

3. Click the JMS server that you want to monitor from the JMS server list, or from the JMS Servers table displayed in the right pane.

4. Click the Monitoring tab to display the monitoring data.

5. Click the Monitor all Active JMS Session Pools Runtime text link. A table displays showing all active JMS session pools for the current domain.

Monitoring Durable Subscribers

1. Expand the JMS node and the Servers node.

2. The JMS Servers table displays in the right pane showing all the JMS servers defined in your domain.

3. Click the JMS server that you want to monitor from the JMS server list in the left pane, or from the JMS Servers table displayed in the right pane.

4. Click the Monitoring tab to display the monitoring data.

5. Click the Monitor all Active JMS Destinations text link. A table displays in the right pane showing all active JMS destinations for the current domain.

6. Click the Monitor all Durable Subscribers text link. Durable Subscribers information is displayed in a table in the right pane for all durable subscribers running (if any) for the destination topics listed in the table.

7. To view durable subscriber information for a specific topic, click the icon (or actual number) in the Durable Subscribers column for the desired topic.

Connection Factory Tasks

Connection factories are objects that enable JMS clients to create JMS connections. A connection factory supports concurrent use, enabling multiple threads to access the object simultaneously. After defining a JMS server, you can configure one or more connection factories to create connections with predefined attributes.

Create a JMS Connection Factory

1. Expand the JMS node.

2. Click the Connection Factories node. The JMS Connection Factories table displays in the right pane showing all the connection factories defined in your domain.

3. Click the Configure a new JMS Connection Factory text link. A dialog displays in the right pane showing the tabs associated with configuring a new connection factory.

4. On the Configuration General tab, enter values in the attribute fields. For more information about general connection factory attributes, see Attributes.

5. Click Create to create a connection factory instance with the name you specified in the Name field. The new instance is added under the JMS Connection Factories node in the left pane.

6. On the Transactions tab, enter attribute values for transaction time-out, whether or not Java Transaction API (JTA) user transactions are allowed, and whether or not a transaction (XA) queue or XA topic connection factory is returned. For more information about connection factory transaction attributes, see Attributes. Click Apply to save your changes.

7. On the Flow Control tab, enter attribute values that will allow a message producer to adjust its message flow. For more information about connection factory flow control attributes, see Attributes. Click Apply to save your changes.

8. On the Targets tab, assign the connection factory to a WebLogic Server instance or a server cluster:

   - Servers--On the Targets list, select the WebLogic Server instance that you want to associate with the connection factory.

   - Clusters--On the Targets list, select the WebLogic Server instances that you want to associate with the connection factory to support clustering.

9. Click Apply to save your changes.

Clone a JMS Connection Factory

1. Expand the JMS node.

2. Click the Connection Factories node. The JMS Connection Factories table displays in the right pane showing all the connection factories defined in your domain.

3. Click the Clone icon in the row of the connection factory that you want to clone. A dialog shows the tabs associated with cloning a connection factory.

4. On the Configuration General tab, enter values in the attribute fields. For more information about general connection factory attributes, see Attributes.

5. Click Create to create a connection factory instance with the name you specified in the Name field. The new instance is added under the JMS Connection Factories node in the left pane.

6. On the Transactions tab, enter attribute values for transaction time-out, whether or not Java Transaction API (JTA) user transactions are allowed, and whether or not a transaction (XA) queue or XA topic connection factory is returned. For more information about connection factory transaction attributes, see Attributes. Click Apply to save your changes.

7. On the Flow Control tab, enter attribute values that will allow a message producer to adjust its message flow. For more information about connection factory flow control attributes, see Attributes. Click Apply to save your changes.

8. Assign the JMS Connection Factory to a WebLogic Server instance or a server cluster.

   For more information see "Assign a JMS Connection Factory".

Delete a JMS Connection Factory

1. Expand the JMS node.

2. Click the Connection Factories node. The JMS Connection Factories table displays in the right pane showing all the connection factories defined in your domain.

3. Click the Delete icon in the row of the connection factory that you want to delete. A dialog prompts you to confirm your deletion request.

4. Click Yes to delete the connection factory. The connection factory instance under the JMS Connection Factories node is deleted.

Assign a JMS Connection Factory

You can target a WebLogic Server instance or a server cluster. Targets enable you to limit the set of servers, groups, and/or clusters on which a connection factory may be deployed.

1. Click the instance node in the left pane under JMS Connection Factories for the connection factory you want to assign. A dialog displays in the right pane showing the tabs associated with this instance.

2. Click the Targets tab.

3. Complete the following steps for the Servers or Clusters tabs:

   1. Select one or more targets in the Available column that you want to assign to the connection factory.

   2. Click the mover control to move the targets you selected to the Chosen column.

4. Click Apply to save your assignments.

JMS Destination Tasks

A destination identifies a queue or topic. After defining a JMS server, you can configure its destinations. You can configure one or more destinations for each JMS server.

You configure destinations explicitly or by configuring a destination template that can be used to define multiple destinations with similar attribute settings, as described in JMS Template Tasks.

Create a JMS Queue

1. Expand the JMS node and the Servers node.

2. Select a JMS server instance under Servers.

3. Click the Destinations node. The JMS Destinations table displays in the right pane showing all the JMS queues.

4. Click the Configure a new JMS Queue text link. A dialog shows the tabs associated with configuring a new queue.

5. Enter values in the attribute fields.

6. Click Create to create a queue instance with the name you specified in the Name field. The new instance is added under the Destinations node in the left pane.

7. Click the remaining tabs individually and change the attribute fields or accept the default values as assigned.

8. Click Apply to save any changes you made.

Clone a JMS Queue

1. Expand the JMS node and the Servers node.

2. Expand a JMS server instance under Servers.

3. Click the Destinations node. The JMS Destinations table displays in the right pane showing all the JMS queues.

4. Click the Clone icon in the row of the queue that you want to clone. A dialog shows the tabs associated with cloning a queue.

5. Enter values in the attribute fields.

6. Click the Create button in the lower right corner to create a queue instance with the name you specified in the Name field. The new instance is added under the Destinations node in the left pane.

7. Click the remaining tabs individually and change the attribute fields or accept the default values as assigned.

8. Click Apply to save any changes you made.

Delete a JMS Queue

1. Expand the JMS node and the Servers node.

2. Expand a JMS server instance under Servers.

3. Click the Destinations node. The JMS Destinations table displays in the right pane showing all the JMS queues.

4. Click the Delete icon in the row of the queue that you want to delete. A dialog prompts you to confirm your deletion request.

5. Click Yes to delete the queue. The queue instance under the Destinations node is deleted.

Create a JMS Topic

1. Expand the JMS node and the Servers node.

2. Expand a server instance under Servers.

3. Click the Destinations node. The JMS Destinations table displays in the right pane showing all the JMS topics.

4. Click the Create a new JMS Topic text link. A dialog shows the tabs associated with configuring a new topic.

5. Enter values in the attribute fields.

6. Click the Create button in the lower right corner to create a topic instance with the name you specified in the Name field. The new instance is added under the Destinations node in the left pane.

7. Click the remaining tabs individually and change the attribute fields or accept the default values as assigned.

8. Click Apply to save any changes you made.

Clone a JMS Topic

1. Expand the JMS node and the Servers node.

2. Expand a server instance under Servers.

3. Click the Destinations node. The JMS Destinations table displays in the right pane showing all the JMS topics.

4. Click the Clone icon in the row of the topic that you want to clone. A dialog shows the tabs associated with cloning a topic.

5. Enter values in the attribute fields.

6. Click the Create button in the lower right corner to create a topic instance with the name you specified in the Name field. The new instance is added under the JMS Destinations node in the left pane.

7. Click the remaining tabs individually and change the attribute fields or accept the default values as assigned.

8. Click Apply to save any changes you made.

Delete a JMS Topic

1. Expand the JMS node and the Servers node.

2. Expand a server instance under Servers.

3. Click the Destinations node. The JMS Destinations table displays in the right pane showing all the JMS topics.

4. Click the Delete icon in the row of the topic that you want to delete. A dialog prompts you to confirm your deletion request.

5. Click Yes to delete the topic. The topic instance under the Destinations node is deleted.

JMS Template Tasks

A JMS template provides an efficient means of defining multiple destinations with similar attribute settings:

- You do not need to re-enter every attribute setting each time you define a new destination; you can use the JMS template and override any setting to which you want to assign a new value.

- You can modify shared attribute settings dynamically simply by modifying the template.

Create a JMS Template

1. Expand the JMS node.

2. Expand the Templates node. The JMS Templates table displays in the right pane showing all the templates defined in the domain.

3. Click the Configure a new JMS Template text link. A dialog displays in the right pane showing the tabs associated with configuring a new template.

4. Enter a value in the Name attribute field.

5. Click Create to create a template instance with the name you specified in the Name field. The new instance is added under the Templates node in the left pane.

6. Click the remaining tabs individually and change the attribute fields or accept the default values as assigned.

7. Click Apply to save any changes you made.

Clone a JMS Template

1. Expand the JMS node.

2. Expand the Templates node. The JMS Templates table displays in the right pane showing all the templates defined in the domain.

3. Click the Clone icon in the row of the template that you want to clone. A dialog shows the tabs associated with cloning a new template.

4. Enter a value in the Name attribute field.

5. Click the Create button in the lower right corner to create a template instance with the name you specified in the Name field. The new instance is added under the Templates node in the left pane.

6. Click the remaining tabs individually and change the attribute fields or accept the default values as assigned.

7. Click Apply to save any changes you made.

Delete a JMS Template

1. Expand the JMS node.

2. Expand the Templates node. The JMS Templates table displays in the right pane showing all the templates defined in the domain.

3. Click the Delete icon in the row of the JMS template that you want to delete. A dialog prompts you to confirm your deletion request.

4. Click Yes to delete the template. The JMS template instance under the Templates node is deleted.

Destination Keys Tasks

Use destination keys to define the sort order for a specific destination.

Create a JMS Destination Key

1. Expand the JMS node.

2. Expand the Destination Keys node. The JMS Destinations Keys table displays in the right pane showing all the destination keys.

3. Click the Create a new JMS Destination Key text link. A dialog shows the tabs associated with configuring a new destination key.

4. Enter values in the attribute fields.

5. Click Create to create a destination key instance with the name you specified in the Name field. The new instance is added under the Destination Keys node in the left pane.

Clone a JMS Destination Key

1. Expand the JMS node.

2. Expand the Destination Keys node. The JMS Destinations Keys table displays in the right pane showing all the destination keys.

3. Click the Clone icon in the row of the destination key that you want to clone. A dialog shows the tabs associated with cloning a destination key.

4. Enter values in the attribute fields.

5. Click Create to create a destination key instance with the name you specified in the Name field. The new instance is added under the Destination Keys node in the left pane.

Delete a JMS Destination Key

1. Expand the JMS node.

2. Expand the Destination Keys node. The JMS Destinations Keys table displays in the right pane showing all the destination keys.

3. Click the Delete icon in the row of the destination key that you want to delete. A dialog prompts you to confirm your deletion request.

4. Click Yes to delete the destination key. The destination key instance under the Destination Keys node is deleted.

JMS File Store Tasks

A JMS file store consists of a file that is used for persistent messaging.

Create a JMS File Store

1. Expand the JMS node.

2. Expand the Stores node. The JMS Stores table displays in the right pane showing all the JMS stores.

3. Click the Create a new JMS File Store text link. A dialog shows the tabs associated with configuring a new file store.

4. Enter values in the attribute fields.

5. Click Create to create a file store instance with the name you specified in the Name field. The new instance is added under the Stores node in the left pane.

Clone a JMS File Store

1. Expand the JMS node.

2. Click the Stores node. The JMS Stores table displays in the right pane showing all the JMS stores.

3. Click the Clone icon in the row of the file store that you want to clone. A dialog shows the tabs associated with cloning a file store.

4. Enter values in the attribute fields.

5. Click Create to create a file store instance with the name you specified in the Name field. The new instance is added under the Stores node in the left pane.

Delete a JMS File Store

1. Expand the JMS node.

2. Click the Stores node. The JMS Stores table displays in the right pane showing all the JMS stores.

3. Click the Delete icon in the row of the file store that you want to delete. A dialog prompts you to confirm your deletion request.

4. Click Yes to delete the file store. The file store instance under the Stores node is deleted.

JMS JDBC Store Tasks

A JMS JDBC store consists of a database that is used for persistent messaging.

Create a JMS JDBC Store

1. Expand the JMS node.

2. Expand the Stores node. The JMS Stores table displays in the right pane showing all the JMS stores.

3. Click the Create a new JMS JDBC Store text link. A dialog shows the tabs associated with configuring a new JDBC store.

4. Enter values in the attribute fields.

5. Click Create to create a JDBC store instance with the name you specified in the Name field. The new instance is added under the Stores node in the left pane.

Clone a JMS JDBC Store

1. Expand the JMS node.

2. Expand the JMS Stores node. The JMS Stores table displays in the right pane showing all the JMS stores.

3. Click the Clone icon in the row of the JDBC store that you want to clone. A dialog shows the tabs associated with cloning a JDBC store.

4. Enter values in the attribute fields.

5. Click Create to create a JDBC store instance with the name you specified in the Name field. The new instance is added under the Stores node in the left pane.

Delete a JMS JDBC Store

1. Expand the JMS node.

2. Click the JMS Stores node. The JMS Stores table displays in the right pane showing all the JMS stores.

3. Click the Delete icon in the row of the JDBC store you want to delete. A dialog prompts you to confirm your deletion request.

4. Click Yes to delete the JDBC store. The JDBC store instance under the Stores node is deleted.

Session Pools Tasks

Server session pools enable an application to process messages concurrently. Once you have defined a JMS server, optionally, you can configure one or more session pools for each JMS server.

Create a JMS Session Pool

1. Expand the JMS node and the Servers node.

2. Expand a JMS server instance under Servers.

3. Click the Session Pools node. The Session Pools table displays in the right pane showing all the session pools.

4. Click the Configure a new JMS Session Pool text link. A dialog shows the tabs associated with configuring a new session pool.

5. Enter values in the attribute fields.

6. Click Create to create a session pool instance with the name you specified in the Name field. The new instance is added under the Session Pools node in the left pane.

Clone a JMS Session Pool

1. Expand the JMS node and the Servers node.

2. Expand a JMS server instance under Servers.

3. Click the Session Pools node. The Session Pools table displays in the right pane showing all the session pools.

4. Click the Clone icon in the row of the session pool that you want to clone. A dialog shows the tabs associated with cloning a session pool.

5. Enter values in the attribute fields.

6. Click Create to create a session pool instance with the name you specified in the Name field. The new instance is added under the Session Pools node in the left pane.

Delete a JMS Session Pool

1. Expand the JMS node and the Servers node.

2. Expand a server instance under Servers.

3. Click the Session Pools node. The Session Pools table displays in the right pane showing all the session pools.

4. Click the Delete icon in the row of the session pool that you want to delete. A dialog prompts you to confirm your deletion request.

5. Click Yes to delete the session pool. The session pool instance under the Session pools node is deleted.

Connection Consumers Tasks

Connection consumers are queues (Point-To-Point) or topics (Pub/Sub) that retrieve server sessions and process messages. Once you have defined a session pool, you can configure one or more connection consumers for each session pool.

Create a JMS Connection Consumer

1. Expand the JMS node and the Servers node.

2. Expand a JMS server instance under Servers.

3. Expand the Session Pools node, and then click a session pool instance.

4. Click the Consumers node. The JMS Consumers table displays in the right pane showing all the connection consumers.

5. Click the Configure a new JMS Connection Consumer text link. A dialog shows the tabs associated with configuring a new connection consumer.

6. Enter values in the attribute fields.

7. Click Create to create a connection consumer instance with the name you specified in the Name field. The new instance is added under the Consumers node in the left pane.

Clone a JMS Connection Consumer

1. Expand the JMS node and the Servers node.

2. Expand a JMS server instance under Servers.

3. Expand the Session Pools node, and then click a session pool instance.

4. Click the Consumers node. The JMS Consumers table displays in the right pane showing all the connection consumers.

5. Click the Clone icon in the row of the connection consumer that you want to clone. A dialog shows the tabs associated with cloning a connection consumer.

6. Enter values in the attribute fields.

7. Click Create to create a connection consumer instance with the name you specified in the Name field. The new instance is added under the Consumers node in the left pane.

Delete a JMS Connection Consumer

1. Expand the JMS node and the Servers node.

2. Expand a JMS server instance under Servers.

3. Expand the Session Pools node, and then click a session pool instance.

4. Click the Consumers node. The JMS Consumers table displays in the right pane showing all the connection consumers.

5. Click the Delete icon in the row of the connection consumer that you want to delete. A dialog prompts you to confirm your deletion request.

6. Click Yes to delete the connection consumer. The connection consumer instance under the Consumers node is deleted.

JMS Distributed Destination Tasks

You can configure multiple physical JMS destinations as members of a single distributed destination set that can be served by multiple WebLogic Server instances within a cluster. Once properly configured, your producers and consumers are able to send and receive to the distributed destination. WebLogic JMS then distributes the messaging load across all available physical destinations within the distributed destination. When a physical destination becomes unavailable, traffic is then redirected toward other available physical destinations in the set.

Warning: In general, BEA highly recommends deploying a distributed destination homogeneously across the cluster using similar configurations for each participating JMS server and it's associated physical destinations. This includes issues like ensuring that there are identical security permissions on all participating distributed members, or if persistent messaging is configured, ensuring that all members are associated with a JMS store.

Create a JMS Distributed Queue

1. Expand the JMS node and the Distributed Destinations node.

2. Click the Configure a new Distributed Queue text link in the right pane. A dialog shows the tabs associated with configuring a new distributed queue.

3. On the Configuration General tab, enter values in the Name, JNDI Name, Load Balancing Policy, and Forward Delay attribute fields. For more information about Distributed Queue general attributes, see Attributes.

4. Click Create to create a distributed queue instance with the name you specified in the Name field. The new instance is added under the Distributed Destinations node in the left pane.

5. On the Configuration Thresholds & Quotas tab, enter values in the Bytes and/or Messages attribute fields. For more information about the Thresholds & Quota attributes, see Attributes. Click Apply to save your changes.

6. If you want to automatically create queue members on JMS servers that are either in a cluster or on individual servers that are not part of a cluster, click the Auto Deploy tab to define the WebLogic Server targets for the distributed queue. Otherwise, skip to the next step to manually create queue members.

7. To manually create queue members for the distributed queue, on the Configuration Members tab click the Configure a new Distributed Queue Member link. A Configuration tab displays in the right pane for configuring a new distributed queue member.

8. On the Configuration tab, enter values in the Name, JMSQueue, and Weight attribute fields. For more information about the Distributed Queue Members attributes, see Attributes.

9. Click Create to a new distributed queue member. The new member is added to the Distributed Queue table.

10. Repeat steps 8-10 to continue manually adding members to the distributed queue.

Delete a JMS Distributed Queue

1. Expand the JMS node and the Distributed Destinations node.

2. The Distributed Destinations table displays in the right pane showing all the distributed queues and topics.

3. Click the Delete icon in the row of the distributed queue that you want to delete. A dialog prompts you to confirm your deletion request.

4. Click Yes to delete the distributed queue. Another dialog prompts you to confirm your deletion request.

5. Click Continue to return to the Distributed Queue table. The distributed queue is deleted from the Distributed Queue table.

Create a JMS Distributed Topic

1. Expand the JMS node and the Distributed Destinations node.

2. Click the Configure a new Distributed Topic text link in the right pane. A dialog shows the tabs associated with configuring a new distributed queue.

3. On the Configuration General tab, enter values in the Name, JNDI Name, and Load Balancing Policy attribute fields. For more information about Distributed Topic general attributes, see Attributes.

4. Click Create to create a distributed queue instance with the name you specified in the Name field. The new instance is added under the Distributed Destinations node in the left pane.

5. On the Configuration Thresholds & Quotas tab, enter values in the Bytes and/or Messages attribute fields. For more information about the Thresholds & Quota attributes, see Attributes. Click Apply to save your changes.

6. If you want to automatically create topic members on JMS servers that are either in a cluster or on individual servers that are not part of a cluster, click the Auto Deploy tab to define the WebLogic Server targets for the distributed topic. Otherwise, skip to the next step to manually create topic members.

7. To manually create topic members for the distributed topic, on the Configuration Members tab click the Configure a new Distributed Topic Member link. A Configuration tab displays in the right pane for configuring a new distributed topic member.

8. On the Configuration tab, enter values in the Name, JMSTopic, and Weight attribute fields. For more information about the Distributed Topic Members attributes, see Attributes.

9. Click Create to a new distributed topic member. The new member is added to the Distributed Topic table.

10. Repeat steps 8-10 to continue manually adding members to the distributed topic.

Delete a JMS Distributed Topic

1. Expand the JMS node.

2. Expand the Distributed Destinations node. The Distributed Destinations table displays in the right pane showing all the distributed queues and topics.

3. Click the Delete icon in the row of the distributed topic that you want to delete. A dialog prompts you to confirm your deletion request.

4. Click Yes to delete the distributed topic. Another dialog prompts you to confirm your deletion request.

5. Click Continue to return to the Distributed Topic table. The distributed topic is deleted from the Distributed Topic table.

Create a JMS Distributed Queue Member

1. Expand the JMS node.

2. Expand the Distributed Destinations node. The Distributed Destinations table displays in the right pane showing all the distributed queues and topics.

3. Click the distributed queue that you want to add a member to. The Distributed Queue table shows all the distributed queue members that belong to the distributed queue.

4. Click the Configure a new Distributed Queue Member text link. A dialog shows the tabs associated with configuring a new distributed queue.

5. Enter values in the attribute fields.

6. Click Create to create a distributed queue member with the name you specified in the Name field. The new member is added to the Distributed Queue Member table in the right pane.

7. Click Apply to save any changes you made.

Delete a JMS Distributed Queue Member

1. Expand the JMS node.

2. Expand the Distributed Destinations node. The Distributed Destinations table displays in the right pane showing all the distributed queues and topics.

3. Click the distributed queue that you want to delete a member from. The Distributed Queue table shows all the distributed queue members that belong to the distributed queue.

4. Click the Delete icon in the row of the distributed queue member that you want to delete. A dialog prompts you to confirm your deletion request.

5. If you want to also remove the underlying physical queue, select the Also Delete check box.

6. Click Remove to delete the distributed queue member (and the underlying physical queue if selected).

7. The Distributed Queue table redisplays in the right pane. The distributed queue member is deleted from the Distributed Queue table.

Create a JMS Distributed Topic Member

1. Expand the JMS node.

2. Expand the Distributed Destinations node. The Distributed Destinations table displays in the right pane showing all the distributed queues and topics.

3. Click the distributed topic that you want to add a member to. The Distributed Topic table shows all the distributed topic members that belong to the distributed topic.

4. Click the Configure a new Distributed Topic Member text link. A dialog shows the tabs associated with configuring a new distributed topic.

5. Enter values in the attribute fields.

6. Click Create to create a distributed topic member with the name you specified in the Name field. The new member is added to the Distributed Topic table in the right pane.

7. Click Apply to save any changes you made.

Delete a JMS Distributed Topic Member

1. Expand the JMS node.

2. Expand the Distributed Destinations node. The Distributed Destinations table displays in the right pane showing all the distributed queues and topics.

3. Click the distributed topic that you want to delete a member from. The Distributed Topic table shows all the distributed topic members that belong to the distributed topic.

4. Click the Delete icon in the row of the distributed topic member that you want to delete. A dialog prompts you to confirm your deletion request.

5. If you want to also remove the underlying physical queue, select the Also Delete check box.

6. Click Remove to delete the distributed topic member (and the underlying physical topic if selected).

7. The Distributed Topic table redisplays in the right pane. The distributed topic member is deleted from the Distributed Topic table.