BEA Home | Events | Solutions | Partners | Products | Services | Download | Developer Center | WebSUPPORT
| WebLogic Server Doc Home | Console Online Help | Previous Topic | Next Topic | Contents | Index | View as PDF

JMS Server

Create a JMS Server

1. Click to expand the JMS node.

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

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

4. Enter values in the attribute fields.

5. Click Create to create a 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 JMS Destinations node and a Session Pools node are automatically added under the new server instance by default.

6. Assign the JMS Server to a WebLogic Server.

For more information, see Assign a JMS Server.

Clone a JMS Server

1. Click to expand the JMS node.

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

3. Click the Clone icon in the row of the server you want to clone. A dialog displays in the right pane showing the tabs associated with cloning a server.

4. Enter values in the attribute fields.

5. Click Create to create a 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 JMS Destinations node and a Session Pools node are automatically added under the new server instance by default.

6. Assign the JMS Server to a WebLogic Server.

For more information, see "Assign a JMS Server".

Delete a JMS Server

1. Click to expand the JMS node.

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

3. Click the Delete icon in the row of the server you want to delete. A dialog displays in the right pane prompting you to confirm your deletion request.

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

Monitor All Active JMS Services

1. Click to expand the JMS node.

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

3. Click the Monitor all Active JMS Services text link. A dialog displays in the right pane showing all active JMS services for the current domain

Monitor All Instances of a JMS Server

1. Click to expand the JMS node.

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

3. Click the Monitor All Instances icon in the row of the server you want to monitor. A dialog displays in the right pane showing all instances of the server deployed across the server domain.

Monitor All Active JMS Destinations

1. Click to expand the JMS node.

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

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

Monitor All Active JMS Session Pools

1. Click to expand the JMS node.

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

3. Click the Monitor all Active JMS Session Pools Runtime text link. A dialog displays in the right pane showing all active JMS session pools for the current domain.

Assign a JMS Server

1. Click the instance node in the left pane under JMS Servers for the server 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 Clusters tabs:

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

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

   3. Click Apply to save your assignments.

Configuration

General

Attribute | Description | Range of Values | Default Value
--- | --- | --- | ---
Name | Name of the JMS server. This attribute is not dynamically configurable. | Java identifier, unique within specific cluster | MyJMS Server[-n]
Store | The existing persistent store for the JMS server. A persistent store may only be used by one JMS server. A value of none specifies that no persistent messaging is supported. If no persistent store is specified, then destinations on this server will not support persistent messages or durable subscribers. This attribute is not dynamically configurable. | Existing persistent store name or none | none
Paging Store | The name of the persistent store where non-persistent messages are paged for the JMS server. A paging store cannot be the same store used for persistent messages or durable subscribers. A paging store may only be used by one JMS server. A value of none specifies that message paging is not supported. If no paging store is specified, then the server and destinations will not support message paging. Note: Using a JDBC store is not recommended for paging since the amount of traffic and subsequent lack of performance would make such a configuration undesirable. | Existing persistent store or none | none
Temporary Template | Name of an existing JMS template used to create all temporary destinations, including temporary queues and temporary topics. The attribute values for a temporary destination are derived from the this JMS template. If provided as part of the template, the Store attribute values are ignored because temporary destinations do not support persistent messaging. This attribute is dynamically configurable. Note: If this attribute is set to none, attempts to create a temporary destination (queue or topic) will fail. | JMS template name or none | none (The default values for the destination attribute are used.)

Thresholds and Quotas

Attribute | Description | Range of Values | Default Value
--- | --- | --- | ---
Bytes Maximum | Maximum number of bytes that may be stored in the JMS server. A value of -1 specifies that there is no limit on the number of bytes that can be stored in the JMS server. This attribute is dynamically configurable. | -1, 0 through 263-1, Greater than or equal to Bytes Threshold High | -1
Bytes Threshold High | Upper threshold value based on the number of bytes stored in the JMS server. If the number of bytes exceeds this threshold—and if bytes paging is enabled and a paging store has been configured—then server bytes paging is started, and a message is logged on the server indicating a high threshold condition. A value of -1 specifies that server bytes paging and threshold log messages are disabled for the JMS server. This attribute is dynamically configurable. Note: Bytes paging cannot be dynamically disabled by resetting the Bytes High Threshold to -1. To disable paging, you could set the Bytes High Threshold to a very large number (max is 263-1), so that paging would not be triggered. | -1, 0 through 263-1, Less than or equal to Bytes Maximum, >Bytes Threshold Low | -1
Bytes Threshold Low | Lower threshold value based on the number of bytes stored in the JMS server. If the number of bytes falls below this threshold, then server bytes paging is stopped (if paging is occurring), and a message is logged on the server indicating that the threshold condition has cleared. A value of -1 specifies that server paging and threshold log messages are disabled for the JMS server. This attribute is dynamically configurable. | -1, 0 through 263-1, <Bytes Threshold High | -1
Bytes Paging Enabled | Flag for specifying whether or not bytes paging is enabled on the JMS server. If this flag is not selected, then server bytes paging is explicitly disabled. If this flag is selected, a paging store has been configured, and both the Bytes Threshold Low and Bytes Threshold High attribute values are greater than -1, then server bytes paging is enabled. If either the Bytes Threshold Low or Bytes Threshold High attribute is undefined, or defined as -1, then server bytes paging is implicitly disabled—even though this flag is selected. | Boolean Enabled = selected Disabled = not selected | Not selected
Messages Maximum | Maximum number of messages that may be stored in the JMS server. A value of -1 specifies that there is no limit on the number of messages that can be stored in the JMS server. This attribute is dynamically configurable. | -1, 0 through 263-1, Greater than or equal to Messages Threshold High | -1
Messages Threshold High | Upper threshold value based on the number of messages stored in the JMS server. If the number of messages exceeds this threshold—and if messages paging is enabled and a paging store has been configured—then server messages paging is started, and a message is logged on the server indicating a high threshold condition. A value of -1 specifies that server messages paging and threshold log messages are disabled for the JMS server. This attribute is dynamically configurable. Note: Messages paging cannot be dynamically disabled by resetting the Messages High Threshold to -1. To disable paging, you could set the Messages High Threshold to a very large number (max is 263 -1), so that paging would not be triggered. | -1, 0 through 263-1, Less than or equal to Messages Maximum, >Messages Threshold Low | -1
Messages Threshold Low | Lower threshold value based on the number of messages stored in the JMS server. If the number of messages falls below this threshold, then server messages paging stops (if paging is occurring), and a message is logged on the server, indicating that the threshold condition has cleared. A value of -1 specifies that server paging and threshold log messages are disabled for the JMS server. This attribute is dynamically configurable. | -1, 0 through 263-1, <Messages Threshold High | -1
Messages Paging Enabled | Flag for specifying whether or not messages paging is enabled on the JMS server. If this flag is not selected, then server-level messages paging is explicitly disabled. If this flag is selected, a paging store has been configured, and both the Messages Threshold Low and Messages Threshold High attribute values are greater than -1, then serve-level messages paging is enabled. If either the Messages Threshold Low or Messages Threshold High attribute is undefined, or defined as -1, then server-level messages paging is implicitly disabled-even though this flag is selected. | Boolean Enabled = selected Disabled = not selected | Not selected

Monitoring

Monitor All Active JMS Services

Attribute | Description | Range of Values | Default Value
--- | --- | --- | ---
Server | Service name | N/A | N/A
Connections | Current number of connections | N/A | N/A
Connections High | Greatest number of connections at any given time | N/A | N/A
Connections Total | Total number of connections | N/A | N/A
Servers | Current number of servers | N/A | N/A
Servers High | Greatest number of servers at any given time | N/A | N/A
Servers Total | Total number of servers | N/A | N/A

Monitor All Instances of JMS Server

Attribute | Description | Range of Values | Default Value
Name | Name of JMS server |  | N/A
Destinations | List of destinations. |  | N/A
Destinations High | Greatest number of instantiated destinations at any given time. |  | N/A
Destinations Total | Total number of instantiated destinations. |  | N/A
Bytes Current | Current number of bytes stored across all destinations in the JMS server. |  | N/A
Bytes Pending | Number of bytes sent and received that are pending the result of an uncommitted transaction or an acknowledgement. |  | N/A
Bytes Received Count | Total number of bytes received for all destinations. |  | N/A
Bytes Threshold Time | Amount of time spent in a bytes threshold condition. |  | N/A
Messages Current | Current number of messages stored across all destinations. |  | N/A
Messages High | Greatest number of messages stored across all destinations at a given time. |  | N/A
Messages Received | Total number of messages received for all destinations. |  | N/A
Messages Threshold Time | Amount of time spent in a messages threshold condition. |  | N/A
Messages Total | Total number of messages stored across all destinations |  | N/A
Session Pools | List of session pools defined for the JMS server. |  | N/A
Session Pools High | Greatest number of session pools at any given time. |  | N/A
Session Pools Total | Total number of instantiated sessions pools. |  | N/A

Monitor Destinations

Attribute | Description | Range of Values | Default Value
--- | --- | --- | ---
Destination | Destination name. |  | N/A
Server | Associated server name. |  | N/A
Consumers | Current number of registered message consumers. |  | N/A
Consumers High | Greatest number of registered message consumers at any given time. |  | N/A
Consumers Total | Total number of registered message consumers. |  | N/A
Bytes Current | Current number of bytes stored. |  | N/A
Bytes Pending | Number of unacknowledged and uncommitted transactional bytes stored. |  | N/A
Bytes Received | Number of bytes received. |  | N/A
Bytes Threshold Time | Amount of time that the destination has spent in a bytes threshold condition since the last time the server was booted. |  | N/A
Messages | Current number of messages stored at this destination. |  | N/A
Messages High | Greatest number of messages stored at any given time. |  | N/A
Messages Pending | Number of unacknowledged and uncommitted transactional messages stored. |  | N/A
Messages Received | Number of messages received. |  | N/A
Messages Threshold Time | Amount of time that the destination spent in a message threshold condition. |  | N/A

Monitor Server Session Pools

Attribute | Description | Range of Values | Default Value
--- | --- | --- | ---
Session Pool | Name of session pool. |  |
Server | Name of associated server. |  |
Consumers | List of consumers. |  |
Consumers High | Greatest number of consumers on the session pool at any given time. |  |
Consumers Total | Total number of consumers. |  |

Targets

Attribute | Description | Range of Values | Default Value
--- | --- | --- | ---
Targets | This attribute provides a list of potential targets. Currently a JMS server can have a maximum of one target. | List | No targets are chosen.

Notes

Attribute | Description | Range of Values | Default Value
--- | --- | --- | ---
Notes | This attribute provides a space for user-supplied information. | The value must be an alphanumeric string. | Null

Copyright © 2001 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.