11 WebLogic Server Messaging

This chapter describes the typical tasks you need to monitor, control and configure WebLogic messaging components in Fusion Middleware Control 12.1.3.

The WebLogic Server implementation of JMS is an enterprise-class messaging system that is tightly integrated into WebLogic Server. It fully supports the JMS specification, and also provides numerous WebLogic JMS Extensions that go beyond the standard JMS APIs. For more information on WebLogic JMS and other related WebLogic messaging components, refer to the following guides:

This chapter includes the following sections:

Monitor, control, and configure JMS servers

JMS servers act as management containers for JMS queue and topic resources within JMS modules that are specifically targeted to JMS servers.

This section includes the following tasks:

Monitor JMS servers

You can monitor statistics for runtime information for active JMS servers in your domain. You can also access runtime information for a JMS server's destinations, transactions, connections, and server session pools.

To monitor JMS servers deployed to this domain:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

    The JMS Server summary table displays information about the state of each JMS server that has been configured in the current WebLogic Server domain, such as:

    • Name

    • Health

    • Health Reason

    • Persistent Store

    • Target

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

  2. In the table, select the name of the JMS server for which you want to view configuration information.

Monitor a JMS server

You can monitor a variety of runtime statistics for each JMS server in your domain, such as the JMS server's paging store, active destinations, active transactions, active connections, and session pools. View the statistics for a JMS server to look for unusual activity, such as an abnormal number of messages waiting on a destination.

To monitor a specific JMS server:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the name of the server you want to monitor.

  3. Select Monitoring, then select Summary.

    The JMS Server summary table displays runtime statistics for this JMS server, such as:

    • Name

    • Destinations Current

    • Messages Current

    • Messages Pending

    • Messages Received

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

  4. To view monitoring information for this JMS server, select the appropriate pages:

    • Paging Store: displays runtime statistics for the JMS server's paging store.

    • Active Destinations: displays statistics for all active JMS destinations targeted to the JMS server.

    • Active Transactions: displays all active JMS transactions running on the JMS server.

    • Active Connections: displays all active JMS connections to the JMS server. A JMS connection represents an open communication channel between an application and the messaging system and is used to create a session for producing and consuming messages.

    • Active Session Pools: displays all active JMS session pools running on the JMS server.

    • Active Pooled Connections: displays all active pooled connections to the JMS server. A pooled JMS connection is a session pool used by EJBs and servlets that use a resource-ref element in their EJB or servlet deployment descriptor to define their JMS connection factories (also known as a wrapped connection factory). Use this page to monitor JMS connection and session objects, as well as message producer objects that are automatically created when declaring a wrapped JMS connection factory in your EJB or servlet.

Monitor JMS connection session information

A session defines a serial order for both the messages produced and the messages consumed, and can create multiple message producers and message consumers. The same thread can be used for producing and consuming messages.

To monitor session information for a JMS connection:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the name of the server you want to monitor.

  3. Select Monitoring, then select Active Connections.

  4. In the Active Connections table, select the Sessions Current Count number for the connection you want to monitor.

  5. From the Sessions page, you can view detailed information about the session's consumers and producers, such as:

    • Consumers

    • Consumers High

    • Consumers Total

    • Producers

    • Producers High

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

Control JMS server messages

You can temporarily pause all runtime message production, insertion (in-flight messages), and consumption operations on all destinations targeted to a JMS server. These message pausing options allow you to assert administrative control of the JMS subsystem behavior in the event of an external resource failure.

For example, by temporarily pausing message production and insertion on destinations, you can effectively drain all the existing messages for troubleshooting purposes, and then resume production and insertions once the issue has been resolved.

To control messages on a JMS server:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the name of the server you want to control.

  3. Select Control, then select Summary.

  4. In the Summary table, select the row of the JMS server on which you want to control messages.

    The control options are displayed above the table.

  5. Select one of the following message control operations:

    • Click Production, then select Pause to stop production of new messages on all destinations targeted to this JMS server.

      When a JMS server's destinations are paused for production, it prevents any new message production operations from both new and existing producers attached to those destinations. To resume message production, click Production, then select Resume.

    • Click Consumption, then select Pause to stop message consumption on all destinations targeted to this JMS server.

      When a JMS server's destinations are paused for consumption, it prevents any further message consumption operations from those destinations. To resume the consumption of messages, click Consumption, then select Resume.

    • Click Insertion, then select Pause to stop the insertion of in-flight messages on all destinations targeted to this JMS server.

      When a JMS server's destinations are paused for insertion, all the messages that are the result of in-flight work completion are prevented from appearing on the destinations. This occurs in addition to pausing the new message production operations. To resume the insertion of in-flight messages, click Insertion, then select Resume.

For more information, see Configuration Options.

Control active JMS destinations

You can temporarily pause runtime message production, insertion (in-flight messages) and consumption operations on selected destinations targeted to a JMS server.

To control active destinations on a JMS server:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the name of the JMS server you want to control.

  3. Select Control, then select Active Destinations.

  4. In the Active Destinations table, select the row of the destination you want to control.

    The control options are displayed above the table.

  5. Select one of the following destination control operations:

    • Click Production, then select Pause to stop production of new messages on this destination.

      When a JMS server's destinations are paused for production, it prevents any new message production operations from both new and existing producers attached to those destinations. To resume message production, click Production, then select Resume.

    • Click Consumption, then select Pause to stop message consumption on this destination.

      When a JMS server's destinations are paused for consumption, it prevents any further message consumption operations from those destinations. To resume the consumption of messages, click Consumption, then select Resume.

    • Click Insertion, then select Pause to stop the insertion of in-flight messages on this destination.

      When a JMS server's destinations are paused for insertion, all the messages that are the result of in-flight work completion are prevented from appearing on the destinations. This occurs in addition to pausing the new message production operations. To resume the insertion of in-flight messages, click Insertion, then select Resume.

For more information, see Configuration Options.

Control active JMS transactions

You can force commits or rollbacks on selected transactions running on a JMS server.

To control active transactions on a JMS server:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the name of the JMS server you want to control.

  3. Select Control, then select Active Transactions.

  4. In the Active Transactions table, select the row of the transaction you want to control.

    The control options are displayed above the table.

  5. Select one of the following transaction control operations:

    • Click Force Commit to initiate a commit operation.

    • Click Force Rollback to initiate a rollback operation.

For more information, see Configuration Options.

Control active JMS connections

A JMS connection represents an open communication channel between an application and the messaging system and is used to create a session for producing and consuming messages. For troubleshooting purposes, you can destroy selected connections on a JMS server.

To destroy a JMS connection on a JMS sever:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the name of the JMS server you want to control.

  3. Select Control, then select Active Connections.

  4. In the Active Connections table, select the row of the connection you want to destroy.

    The Destroy option is displayed above the table.

  5. Click Destroy to terminate the JMS connection.

For more information, see Configuration Options.

Configure general JMS server properties

After you create a JMS server, you can define optional general properties for message paging, specify a template to use when your applications create temporary destinations, and a desired pausing interval between active scans of destinations for expired messages.

To configure general settings for a JMS server:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the JMS server you want to configure.

  3. Select Configuration, then select General.

    From the General page, you can define the general configuration parameters for a JMS server, including:

    • Name

    • Persistent Store

    • Paging File Locking Enabled

    • Paging Directory

    • Message Buffer Size

    • Hosting Temporary Destinations

    • Module Containing Temporary Template

    • Temporary Template Name

    • Expiration Scan Interval

    For more information about these fields, see Configuration Options.

    Optionally, expand Advanced to define advanced settings for this cluster.

  4. Click Save.

Configure JMS server thresholds and quotas

After you create a JMS server, you can define the upper and lower byte and/or message thresholds for destinations in JMS modules that targeted to this JMS server. Exceeding these thresholds will trigger events such as generating log messages and starting message flow control. In the Quota section, you can specify a maximum size allowed for messages and the number of messages and/or bytes available to a JMS server. You can also select a blocking policy to determine whether the JMS server delivers smaller messages before larger ones when a destination has exceeded its maximum number of messages.

To configure thresholds and quotas for a JMS server:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the JMS server you want to configure.

  3. Select Configuration, then select Thresholds and Quotas.

    From the Thresholds and Quotas page, you can define threshold and quota settings for a JMS server, including:

    • Bytes Threshold High

    • Bytes Threshold Low

    • Messages Threshold High

    • Messages Threshold Low

    • Bytes Maximum

    • Messages Maximum

    • Blocking Send Policy

    • Maximum Message Size

    For more information about these fields, see Configuration Options.

  4. Click Save.

Create a new JMS session pool

A JMS session pool enables 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.

To create a new JMS session pool:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the JMS server you want to configure.

  3. Select Configuration, then select Session Pools.

    The Session Pools table displays information about the session pools that have been created for a JMS server.

  4. Click Create.

  5. On the Create a New JMS Session Pool page, you can define settings for your new session pool, such as:

    • Name

    • Listener Class

    For more information about these fields, see Configuration Options.

  6. Click Create.

Configure JMS server session pools

A JMS session pool enables 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.

To view configuration information for the session pools that have been created for a JMS server:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the JMS server you want to configure.

  3. Select Configuration, then select Session Pools.

    The Session Pools table displays information about the session pools that have been created for a JMS server, including:

    • Name

    • Acknowledge Mode

    • Listener Class

    • Sessions Maximum

    • Transacted

    • Connection Factory

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

Configure a JMS session pool

To configure a specific JMS session pool:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the JMS server you want to configure.

  3. Select Configuration, then select Session Pools.

    In the Session Pools table, select the session pool you want to configure.

  4. Select Configuration.

    From the Configuration page, you can define configuration settings for the JMS session pool, such as:

    • Name

    • Connection Factory

    • Listener Class

    • Acknowledge Mode

    • Sessions Maximum

    • Transacted

    For more information about these fields, see Configuration Options.

  5. Click Apply.

Configure JMS session pool consumers

To view configuration information for the connection consumers associated with a specific JMS session pool:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the JMS server you want to configure.

  3. Select Configuration, then select Session Pools.

    In the Session Pools table, select the session pool you want to configure.

  4. Select Consumers.

    From the Consumers page, you can view configuration information for the connection consumers associated with this JMS session pool, such as:

    • Name

    • Messages Maximum

    • Selector

    • Destination

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

Create session pool notes

To create session pool notes:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the JMS server you want to configure.

  3. Select Configuration, then select Session Pools.

    In the Session Pools table, select the session pool you want to configure.

  4. Select Notes.

  5. On the Notes page, enter your notes.

  6. Click Save.

    For more information about these fields, see Configuration Options.

Create a new connection consumer

Connection consumers are queues or topics that retrieve JMS server sessions and process messages. After you define a session pool, configure one or more connection consumers for each session pool.

To create a new consumer:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the JMS server you want to configure.

  3. Select Configuration, then select Session Pools.

    In the Session Pools table, select the session pool you want to configure.

  4. Select Consumers, then click Create.

  5. On the Create a New Consumer page, you can define settings for your new connection consumer, such as:

    • Name

    • Messages Maximum

    • Selector

    • Destination

    For more information about these fields, see Configuration Options.

  6. Click Create.

Configure and monitor connection consumers

Connection consumers are queues or topics that retrieve JMS server sessions and process messages. After you define a session pool, configure one or more connection consumers for each session pool.

This section includes the following topics:

Configure connection consumers

To configure connection consumers:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the JMS server you want to configure.

  3. Select Configuration, then select Session Pools.

    In the Session Pools table, select the session pool you want to configure.

  4. Select Consumers.

    In the Consumers table, select the consumer you want to configure.

  5. Select Configuration.

    From the Configuration page, you can define configuration settings for the JMS connection consumer, such as:

    • Name

    • Messages Maximum

    • Selector

    • Destination

    For more information about these fields, see Configuration Options.

  6. Click Apply.

Monitor connection consumers

To monitor connection consumers:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the JMS server you want to monitor.

  3. Select Configuration, then select Session Pools.

    In the Session Pools table, select the session pool you want to monitor.

  4. Select Consumers.

    In the Consumers table, select the consumer you want to monitor.

  5. Select Monitoring.

    From the Monitoring page, you can view information about connection consumers, such as:

    • Name

    • Messages Maximum

    • Selector

    • Destination

    • Active

    • Durable

    • Messages Pending

    • Messages Received

    • Bytes Pending

    • Bytes Received

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

Create connection consumer notes

To configure connection consumers:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the JMS server you want to configure.

  3. Select Configuration, then select Session Pools.

    In the Session Pools table, select the session pool you want to configure.

  4. Select Consumers.

    In the Consumers table, select the consumer you want to configure.

  5. Select Notes.

  6. On the Notes page, enter your notes.

    For more information about these fields, see Configuration Options.

  7. Click Save.

Select JMS server targets

To select targets for a JMS server:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the JMS server you want to configure.

  3. Select Targets.

    From the Target dropdown menu, select the server instance or migratable target on which you want to deploy this JMS server.

    For more information, see Configuration Options.

  4. Click Apply.

Create JMS server notes

To create notes for a JMS server:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Servers.

  2. In the JMS Server table, select the JMS server you want to configure.

  3. Select Notes.

  4. On the Notes page, enter your notes.

    For more information, see Configuration Options.

  5. Click Apply.

Monitor and control Store-and-Forward agents

The Store-and-Forward (SAF) service enables WebLogic Server to deliver messages reliably between applications that are distributed across WebLogic Server instances. If the destination is not available at the moment the messages are sent, either because of network problems or system failures, then the messages are saved on a local server instance and are forwarded to the remote destination once it becomes available.

SAF agents are responsible for store-and-forwarding messages between local sending and remote receiving endpoints. A SAF agent can be configured to have only sending capabilities, receiving capabilities, or both. WebLogic JMS SAF only requires a sending agent on the sending side for JMS messages. Whereas, Web Services Reliable Messaging (WSRM) SAF requires both a sending agent and a receiving agent.

This section includes the following tasks:

Monitor SAF agents

To monitor all SAF agents created for this domain:

  1. From the WebLogic Domain menu, select Messaging, then select Store-and-Forward Agents.

    The SAF summary table displays information about the state of each SAF agent that has been configured in the current WebLogic Server domain, such as:

    • Name

    • Agent Type

    • Persistent Store

    • Server

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

  2. In the table, select the name of the SAF agent for which you want to view configuration information.

Monitor a SAF agent

You can monitor a variety of runtime statistics for each SAF agent in your domain, including remote endpoints and conversations.

To view the current statistics for a specific SAF agent:

  1. From the WebLogic Domain menu, select Messaging, then select Store-and-Forward Agents.

  2. In the SAF table, select the name of the SAF agent you want to monitor.

    The Settings for Store-and-Forward Agent page displays monitoring information related to this SAF agent.

  3. To monitor the following SAF agent information, select the appropriate pages:

    • Statistics: displays runtime statistics for this SAF agent.

    • Remote Endpoints: displays monitoring information for the remote endpoints associated with this SAF agent. You can view a table of active messages for a remote endpoint by selecting a remote endpoint. To view the contents of a message, select the message.

    • Conversations: displays monitoring information for the conversations associated with this SAF agent.

Control SAF agents

You can temporarily pause runtime message activity on SAF agents.

To control message operations on a SAF agent:

  1. From the WebLogic Domain menu, select Messaging, then select Store-and-Forward Agents.

  2. In the SAF table, select the name of the SAF agent you want to control.

  3. Select Statistics.

  4. In the Statistics table, select the row of the SAF agent on which you want to control messages.

    The control options are displayed above the table

  5. Select one of the following message control operations:

    • Click Incoming, then select Pause or Resume to control the flow of incoming messages to the SAF agent.

    • Click Forwarding, then select Pause or Resume to control the forwarding of messages to the SAF agent.

    • Click Receiving, then select Pause or Resume to control the receiving of messages to the SAF agent.

For more information, see Configuration Options.

Control SAF remote endpoints

You can control message operations for active remote endpoints associated with a SAF agent.

To control remote endpoints for a SAF agent:

  1. From the WebLogic Domain menu, select Messaging, then select Store-and-Forward Agents.

  2. In the SAF table, select the name of the SAF agent you want to control.

  3. Select Remote Endpoints.

  4. In the Remote Endpoints table, select the row of the remote endpoint you want to control.

    The control options are displayed above the table.

  5. Select one of the following remote endpoint control operations:

    • Click Incoming, then select Pause or Resume to control the flow of incoming messages. The table reflects the remote endpoint's new paused or non-paused state.

    • Click Forwarding, then select Pause or Resume to control the forwarding of messages to the SAF agent. The table reflects the remote endpoint's new paused or non-paused state.

    • Click Expire All to process all pending messages for a remote destination, according to the policy specified by the associated error handling configuration, and then remove them from the remote endpoint.

    • Click Purge All to destroy all conversations and purge all messages on a remote endpoint.

For more information, see Configuration Options.

Control SAF conversations

You can terminate active conversations associated with a SAF agent.

To destroy SAF conversations:

  1. From the WebLogic Domain menu, select Messaging, then select Store-and-Forward Agents.

  2. In the SAF table, select the name of the SAF agent you want to control.

  3. Select Conversations.

  4. In the Conversations table, select the row of the conversation you want to destroy.

    The Destroy option is displayed above the table.

  5. Click Destroy to terminate the SAF conversation.

For more information, see Configuration Options.

Monitor and control JMS resources and modules

JMS system resources are configured and stored as modules similar to standard Java EE modules. Such resources include queues, topics, connection factories, templates, destination keys, quota, distributed queues, distributed topics, foreign servers, and JMS store-and-forward (SAF) parameters. System modules are globally available for targeting to server instances and clusters configured in the domain, and therefore are available to all applications deployed on the same targets and to client applications.

Note:

JMS configuration resources can also be managed as deployable application modules, either with a Java EE application as a packaged module, which is available only to the enclosing application, or as a standalone module that provides global access to the resources defined in that module. For more information about configuring JMS application modules, see "Configuring JMS Application Modules for Deployment" in Administering JMS Resources for Oracle WebLogic Server.

This section includes the following tasks:

Monitor JMS resources

You can view all the resources from all the JMS system modules created in the current WebLogic Server domain. You can also view monitoring information, including the resource's system module, JNDI name, targeted subdeployment resources, and the JMS server, WebLogic server, instance or cluster on which the resource is targeted.

For certain resources, you can monitor detailed statistical information or perform control operations.

To monitor all JMS system resources in the current domain:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Resources and Modules.

  2. Select JMS Resources.

    The JMS Resources table lists all the resources that are defined as part of all JMS system modules configured in the current domain:

    • Connection Factory: defines a set of connection configuration parameters that enable JMS clients to create JMS connections.

    • Destination Key: defines a sort order for messages as they arrive on destinations.

    • Foreign Server: represents a third-party JMS provider that is outside WebLogic Server.

    • Queue: defines a point-to-point (PTP) destination, which enables one application to send a message to another. See Monitor queues.

    • Quota: controls the allotment of system resources available to destinations.

    • SAF Error Handler: specifies the action to be taken when the SAF service fails to forward messages to a remote destination.

    • SAF Imported Destinations: represents a collection of SAF queues and topics that locally represent JMS queues or topics on a remote server instance or cluster. See Monitor SAF imported destinations.

    • SAF Remote Context: specifies the SAF login context that the SAF imported queue or topic uses to connect to a remote destination.

    • Template: provides an efficient means of defining multiple queues and topics with similar configuration settings.

    • Topic: defines a publish/subscribe (pub/sub) destination, which enables an application to send a message to multiple applications. See Monitor topics.

    • Uniform Distributed Queue: represents a single unit of JMS queues that is accessible as a single, logical queue to a client. See Monitor uniform distributed queues.

    • Uniform Distributed Topic: represents a single unit of JMS topics that is accessible as a single, logical topic to a client. See Monitor uniform distributed topics.

    From the JMS Resources table, you can monitor information about each JMS system module resource, such as:

    • Name

    • Type

    • JMS Module Name

    • JNDI Name

    • Subdeployment

    • Targets

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

  3. In the table, select the name of the JMS system resource for which you want to view additional monitoring information.

Monitor queues

To monitor runtime statistics on queues in a JMS system module:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Resources and Modules.

  2. Select JMS Resources.

    The JMS Resources table lists all the resources defined as part of the JMS system modules configured in the current domain.

  3. In the table, select the name of the queue you want to monitor.

    The Monitoring page displays runtime statistics for the queue, including:

    • Name

    • Messages Current

    • Messages Pending

    • Messages Total

    • Consumers Current

    For more information about these fields, see Configuration Options. To control messages, see Control messages on queues.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

Monitor topics

To monitor runtime statistics on topics in a JMS system module:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Resources and Modules.

  2. Select JMS Resources.

    The JMS Resources table lists all the resources defined as part of the JMS system modules configured in the current domain.

  3. In the table, select the name of the topic you want to monitor.

    The Statistics page displays runtime statistics for the topic, such as:

    • Name

    • Messages Current

    • Messages Pending

    • Messages Total

    • Consumers Current

    For more information about these fields, see Configuration Options. To control messages, see Control messages on topics.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

  4. To view additional monitoring information for this topic, select Durable Subscribers.

    The Durable Subscribers page displays additional runtime information for the topic, such as:

    • Client ID

    • Client ID Policy

    • Subscription Name

    • Active

    • Messages Current Count

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

Monitor uniform distributed queues

To monitor statistics for all of the members of a uniform distributed queue in a JMS system module:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Resources and Modules.

  2. Select JMS Resources.

    The JMS Resources table lists all the resources defined as part of the JMS system modules configured in the current domain.

  3. In the table, select the name of the uniform distributed queue you want to monitor.

    The Monitoring page displays runtime statistics for the uniform distributed queue, such as:

    • Name

    • Consumers Current

    • Consumers High

    • Consumers Total

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

Monitor uniform distributed topics

To monitor statistics for all of the members of a uniform distributed topic in a JMS system module:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Resources and Modules.

  2. Select JMS Resources.

    The JMS Resources table lists all the resources defined as part of the JMS system modules configured in the current domain.

  3. In the table, select the name of the uniform distributed topic you want to monitor.

    The Statistics page displays runtime statistics for the uniform distributed topic, such as:

    • Name

    • Consumers Current

    • Consumers High

    • Consumers Total

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

  4. To view additional monitoring information for this uniform distributed topic, select Durable Subscribers.

    The Durable Subscribers page displays additional runtime information for the uniform distributed topic, such as:

    • Client ID

    • Client ID Policy

    • Subscription Name

    • Active

    • Messages Current Count

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

Monitor SAF imported destinations

SAF imported destinations are collections of SAF queues and topics that locally represent JMS queues or topics on a remote server instance or cluster. Each collection of imported destinations is associated with a remote SAF context. They can also share the same JNDI prefix, time-to-live default (message expiration time), and SAF error handling policy.

SAF queues are used for asynchronous and disconnected peer communications. Messages delivered to a SAF queue are temporarily stored for future delivery and are forwarded to a JMS queue on a remote server or cluster when it is reachable.

SAF topics are used for asynchronous and disconnected peer communications. Messages delivered to a SAF topic are temporarily stored for future delivery and are forwarded to a JMS topic on a remote server or cluster when it is reachable.

To monitor SAF imported destinations in a JMS system module:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Resources and Modules.

  2. Select JMS Resources.

    The JMS Resources table lists all the resources defined as part of the JMS system modules configured in the current domain.

  3. In the table, select the name of the SAF imported destination you want to monitor.

  4. To monitor SAF queues, select Configuration, then select Queues.

    The SAF Queues summary page displays the SAF queues created for this SAF imported destination.

    For more information, see Configuration Options.

  5. To monitor SAF topics, select Configuration, then select Topics.

    The SAF Topics summary page displays the SAF topics created for this SAF imported destination.

    For more information, see Configuration Options.

View durable subscriber details

To view configuration details of a durable subscriber running on a JMS topic or uniform distributed topic:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Resources and Modules.

  2. Select JMS Resources.

    The JMS Resources table lists all the resources defined as part of the JMS system modules configured in the current domain.

  3. In the table, select the name of the topic or uniform distributed topic you want to monitor.

  4. Select Monitoring, then select Durable Subscribers.

  5. In the Durable Subscribers table, select the Subscription Name for the durable subscriber on which you want to view configuration details.

    The JMS Durable Subscribers page displays additional runtime information for the durable subscriber, such as:

    • Subscription Name

    • Client ID

    • Client ID Policy

    • Message Selector

    • No Local Messages

    For more information about these fields, see Configuration Options.

Control messages on JMS destination resources

For troubleshooting purposes, you can control operations available for JMS destination resources, such as temporarily pausing runtime message production, consumption, and insertion activity on destinations.

The following destination resources have message control capability:

Control messages on queues

To control messages on queues in a JMS system module:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Resources and Modules.

  2. Select JMS Resources.

    The JMS Resources table lists all the resources defined as part of the JMS system modules configured in the current domain.

  3. In the table, select the name of the queue for which you want to control messages.

  4. Select Control.

  5. In the Control table, select the row of the queue you want to control.

    The control options are displayed above the table.

  6. Select one of the following message control operations:

    • Click Production, then select Pause to stop production of new messages on the selected queue.

      When a queue is paused for production, it prevents new message production operations from both new and existing producers attached to that queue. To resume message production, click Production, then select Resume.

    • Click Consumption, then select Pause to stop message consumption on the selected queue.

      When a queue is paused for consumption, it prevents further message consumption operations from that queue. To resume the consumption of messages, click Consumption, then select Resume.

    • Click Insertion, then select Pause to stop the insertion of in-flight messages on the selected queue.

      When a queue is paused for insertion, all the messages that are the result of in-flight work completion are prevented from appearing on the queue. This occurs in addition to pausing new message production operations. To resume the insertion of in-flight messages, click Insertion, then select Resume.

For more information, see Configuration Options.

Control messages on topics

For troubleshooting purposes, runtime message production, consumption, and insertion activity can be temporarily paused on topics targeted to a JMS system module.

To control messages on topics in a JMS system module:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Resources and Modules.

  2. Select JMS Resources.

    The JMS Resources table lists all the resources defined as part of the JMS system modules configured in the current domain.

  3. In the table, select the name of a JMS topic for which you want to control topics.

  4. Select Control.

  5. In the Control table, select the row of the topic you want to control.

    The control options are displayed above the table.

  6. Select one of the following message control operations:

    • Click Production, then select Pause to stop production of new messages on the selected topic.

      When a topic is paused for production, it prevents new message production operations from both new and existing producers attached to that topic. To resume message production, click Production, then select Resume.

    • Click Consumption, then select Pause to stop message consumption on the selected topic.

      When a topic is paused for consumption, it prevents further message consumption operations from that topic. To resume the consumption of messages, click Consumption, then select Resume.

    • Click Insertion, then select Pause to stop the insertion of in-flight messages on the selected topic.

      When a topic is paused for insertion, all the messages that are the result of in-flight work completion are prevented from appearing on the topic. This occurs in addition to pausing the new message production operations. To resume the insertion of in-flight messages, click Insertion, then select Resume.

For more information, see Configuration Options.

Monitor JMS modules

You can monitor the JMS system modules created for the current domain. The table specifies which resource types are part of each module, as well as the number of assigned resource types, such as 12 queues and one connection factory.

To monitor JMS modules:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Resources and Modules.

  2. Select JMS Modules.

    The JMS Modules table lists all the JMS system modules configured in the current domain and displays the number of JMS system resource types configured for each module, such as:

    • Queues

    • Topics

    • Connection Factories

    • Distributed Queues

    • Distributed Topics

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

  3. In the table, select the name of the JMS module for which you want to view additional monitoring information.

Monitor JMS system module resources

You can monitor general information about the JMS resources that have been created for a specific JMS system module, including queue, topic, connection factories, templates, destination sort keys, destination quota, distributed destinations, foreign servers, and store-and-forward parameters.

To monitor the resources of a specific JMS system module:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Resources and Modules.

  2. Select JMS Modules.

    The JMS Modules table lists all the JMS system modules configured in the current domain.

  3. In the table, select the name of the JMS module that you want to monitor.

  4. Select General.

    The overview table displays general information about the JMS system module and its assigned resources, such as:

    • Name

    • Type

    • JNDI Name

    • Subdeployments

    • Targets

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

  5. Select the name of a JMS resource for detailed statistical information on the selected resource. See Monitor JMS resources.

Monitor JMS system module subdeployments

You can monitor the subdeployments created for a JMS system module. A subdeployment is a mechanism by which JMS module resources (such as queues, topics, and connection factories) are grouped and targeted to a server resource (such as JMS servers, server instances, or cluster).

To monitor the subdeployments of a specific JMS system module:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Resources and Modules.

  2. Select JMS Modules.

    The JMS Modules table lists all the JMS system modules configured in the current domain.

  3. In the table, select the name of the JMS module that you want to monitor.

  4. Select Subdeployments.

    The Subdeployments table displays information about the subdeployments created for a JMS system module in the current WebLogic Server domain, such as:

    • Name

    • Resources

    • Targets

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

Monitor path services

A path service is a persistent map that can be used to store the mapping of a group of messages to a messaging resource, such as a member of a distributed destination or a Store-and-Forward agent. It provides a way to enforce message ordering by pinning messages to a member of a cluster hosting servlets, distributed queue members, or Store-and-Forward agents.

To monitor the path service instances configured in the current domain:

  1. From the WebLogic Domain menu, select Messaging, then select Path Services.

    The Path Services summary table displays monitoring information related to the path service instances that have been configured in the current WebLogic Server domain, such as:

    • Name

    • Target

    • Persistent Store

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

  2. In the Path Services table, select the name of the path service for which you want to view configuration information.

Monitor and configure messaging bridges

A WebLogic messaging bridge is a forwarding mechanism between any two messaging products. Use a message bridge to provide interoperability between separate implementations of WebLogic JMS, or between WebLogic JMS and another messaging product.

This section includes the following tasks:

Monitor messaging bridges

To monitor the messaging bridge instances that have been configured for the current domain:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Bridges.

  2. Select Configuration to display information about the messaging bridge instances that have been configured in the current WebLogic Server domain, such as:

    • Name

    • Source Bridge Destination

    • Target Bridge Destination

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

  3. Select Monitoring to display statistics for all messaging bridges configured on active servers in this domain, such as:

    • Name

    • Server

    • State

    • Description

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

Monitor a messaging bridge

To monitor the status of a specific messaging bridge instance configured for the current domain:

  1. From the WebLogic Domain menu, select Messaging, then select Bridges.

  2. In the Messaging Bridges table, select the name of the messaging bridge you want to monitor.

  3. Select Monitoring.

    The Messaging Bridge summary table displays monitoring information associated with this messaging bridge, such as:

    • Name

    • Server

    • State

    • Description

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

Configure messaging bridge general settings

To configure general settings for a specific messaging bridge instance in the current domain:

  1. From the WebLogic Domain menu, select Messaging, then select Bridges.

  2. In the Messaging Bridges table, select the messaging bridge you want to configure.

  3. Select Configuration, then select General.

    From the General page, you can configure general settings for this messaging bridge instance, such as:

    • Name

    • Source Bridge Destination

    • Target Bridge Destination

    • Selector

    • Quality of Service

    • QOS Degradation Allowed

    • Maximum Idle Time

    • Asynchronous Mode Enabled

    • Durability Enabled

    • Started

    • Preserve Msg Property

    For more information about these fields, see Configuration Options.

  4. Click Apply.

Configure messaging bridge connection retry settings

To configure connection retry settings for a specific messaging bridge instance in the current domain:

  1. From the WebLogic Domain menu, select Messaging, then select Bridges.

  2. In the Messaging Bridges table, select the messaging bridge you want to configure.

  3. Select Configuration, then select Connection Retry.

    From the Connection Retry page, you can configure reconnection parameters for this messaging bridge, such as:

    • Minimum Delay

    • Incremental Delay

    • Maximum Delay

    For more information about these fields, see Configuration Options.

  4. Click Apply.

Configure messaging bridge transaction settings

To configure transactions for a specific messaging bridge instance in the current domain:

  1. From the WebLogic Domain menu, select Messaging, then select Bridges.

  2. In the Messaging Bridges table, select the messaging bridge you want to configure.

  3. Select Configuration, then select Transactions.

    From the Transactions page, you can configure transaction settings for this messaging bridge, such as:

    • Transaction Timeout

    • Batch Size

    • Batch Interval

    For more information about these fields, see Configuration Options.

  4. Click Apply.

Select messaging bridge targets

To select the targets for a specific messaging bridge instance in the current domain:

  1. From the WebLogic Domain menu, select Messaging, then select Bridges.

  2. In the Messaging Bridges table, select the messaging bridge you want to configure.

  3. Select Targets.

    From the Targets page, you can target this messaging bridge to independent servers, clusters, or migratable targets. Select the targets you wish to deploy this messaging bridge on.

    For more information, see Configuration Options.

  4. Click Apply.

Create messaging bridge notes

To create notes for a specific messaging bridge instance in the current domain:

  1. From the WebLogic Domain menu, select Messaging, then select Bridges.

  2. In the Messaging Bridges table, select the messaging bridge you want to configure.

  3. Select Notes.

  4. On the Notes page, enter your notes.

    For more information, see Configuration Options.

  5. Click Save.

Monitor and configure JMS bridge destinations

A JMS bridge destination is a source or target destination in a JMS messaging product. Configure a JMS bridge destination instance for each JMS messaging source and target destination that connects to a messaging bridge.

This section includes the following tasks:

Monitor JMS bridge destinations

To monitor the JMS bridge destinations configured in the current domain:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Bridge Destinations.

    The JMS Bridge Destinations summary table displays monitoring information related to the JMS bridge destinations that have been configured in the current WebLogic Server domain, such as:

    • Name

    • Adapter JNDI Name

    • Adapter Classpath

    For more information about these fields, see Configuration Options.

    Optionally, select View to access the following table options:

    • Columns: add or remove the columns displayed in the table

    • Detach: detach the table (viewing option)

    • Sort: sort the columns in ascending or descending order

    • Reorder: change the order of the columns displayed

    • Query by Example

  2. In the table, select the name of the JMS bridge destination for which you want to view configuration information.

Configure a JMS bridge destination

To configure a specific JMS bridge destination:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Bridge Destinations.

  2. In the JMS Bridge Destinations table, select the JMS bridge destination you want to configure.

  3. Select Configuration.

    From the Configuration page, you can configure settings for this JMS bridge destination, such as:

    • Name

    • Adapter JNDI Name

    • Connection URL

    • Initial Context Factory

    • Connection Factory JNDI Name

    • Destination JNDI Name

    • Destination Type

    • User Name

    • User Password

    • Confirm User Password

    For more information about these fields, see Configuration Options.

  4. Click Apply.

Create JMS bridge destination notes

To configure a specific JMS bridge destination:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Bridge Destinations.

  2. In the JMS Bridge Destinations table, select the JMS bridge destination you want to configure.

  3. Select Notes.

  4. On the Notes page, enter your notes.

    For more information, see Configuration Options.

  5. Click Save.