1. Administering Oracle WebLogic Server with Fusion Middleware Control
  2. WebLogic Server Messaging

11 WebLogic Server Messaging

This chapter describes the typical tasks you need to create, monitor, control and configure WebLogic Server messaging components.

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 Server JMS Extensions that go beyond the standard JMS APIs. For more information on WebLogic Server JMS and other related WebLogic Server messaging components, refer to the following guides:

This chapter includes the following sections:

JMS servers

JMS servers act as management containers for JMS queue and topic resources within JMS modules that are specifically targeted to JMS servers. You can create, monitor, control, and configure JMS servers.

This section includes the following tasks:

Parent topic: WebLogic Server Messaging

Create JMS servers

JMS servers are environment-related configuration entities that act as management containers for JMS queue and topic destinations in JMS modules that are targeted to them. Multiple JMS modules can be targeted to each JMS server in a domain.

To create a JMS server:

  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.

  2. Click Create.

    Note:

    Once you create a JMS server, you cannot rename it. Instead, you must delete it and create another JMS server that uses the new name.

  3. Define the configuration options for your JMS server on each page of the following sections.
  4. Then, click Create.

Parent topic: JMS servers

General Settings

On the General Settings page, define the following settings for this JMS server:

  • In Name, enter a name for this JMS server.

  • In Scope, select the scope in which you would like this new JMS server to be created.

  • In Persistent Store, select a pre-configured custom file or JDBC store that will be used by the JMS server or click the Create a Store button to create a store on the fly.

    If you leave this field set to none, then the JMS server will use the default file store that is automatically configured on each targeted server instance. For more information about configuring stores, see Configure a file store.

    Note:

    When a JMS server is targeted to:

    • A migratable target, it cannot use the default store, so a custom store must be configured and targeted to the same migratable target.

    • A dynamic cluster, a custom persistent store must target the same dynamic cluster or the default store available on each dynamic cluster member.

For more information about these fields, see Configuration Options.

Parent topic: Create JMS servers

Targets

On the Targets page, select the server instance, dynamic cluster, or migratable server target on which to deploy the JMS server.

See Configuration Options.

Parent topic: Create JMS servers

Review

On the Review page, review the configuration for this JMS server.

See Configuration Options.

Parent topic: Create JMS servers

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

    • Scope

    • 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.

Parent topic: JMS servers

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.

      See Configuration Options.

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

      See Configuration Options.

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

      See Configuration Options.

    • 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.

      See Configuration Options.

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

      See Configuration Options.

    • 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.

      See Configuration Options.

Parent topic: JMS servers

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

Parent topic: Monitor a JMS server

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 let you 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.

See Configuration Options.

Parent topic: JMS servers

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.

See Configuration Options.

Parent topic: JMS servers

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.

See Configuration Options.

Parent topic: JMS servers

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.

See Configuration Options.

Parent topic: JMS servers

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 settings for a JMS server, including:

    • Name

    • Scope

    • 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.

Parent topic: JMS servers

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.

Parent topic: JMS servers

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.

Parent topic: JMS servers

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

Parent topic: JMS servers

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.

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 Connection 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.

Parent topic: JMS servers

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:

Parent topic: JMS servers

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.
  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 menu, select the server instance or migratable target on which you want to deploy this JMS server.

    See Configuration Options.

  4. Click Apply.

Parent topic: JMS servers

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.
  5. Click Apply.

Parent topic: JMS servers

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 Server 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:

Parent topic: WebLogic Server Messaging

Create Store-and-Forward agents

The Store-and-Forward (SAF) service uses SAF agents to deliver messages reliably between applications that are distributed across WebLogic Server instances. A SAF agent can be configured to have only sending capabilities, receiving capabilities, or both. JMS SAF only requires a sending agent on the sending side for JMS messages. Whereas, WSRM SAF requires both a sending agent and a receiving agent.

To create a Store-and-Forward agent:

  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.

  2. Click Create.

    Note:

    Once you create a SAF agent, you cannot rename it. Instead, you must delete it and create another SAF agent that uses the new name.

  3. Define the configuration options for your SAF agent on each page of the following sections.
  4. Then, click Create.

Parent topic: Store-and-Forward agents

General Settings

On the General Settings page, define the following settings for this SAF agent:

  • In Name, enter a name for this SAF agent.

  • In Scope, select the scope in which you would like this new SAF agent to be created.

  • In Persistent Store, select a custom persistent store if you want a dedicated store for SAF messages or click Create a New Store to configure a new custom store.

    If you leave this field set to none, then the SAF agent will use the default file store that is automatically configured on each targeted server instance. For more information about configuring stores, see Configure a file store.

    Note:

    When a SAF agent is targeted to a migratable target, it cannot use the default store. Therefore, a custom store must be configured and targeted to the same migratable target.

  • In Agent Type, select one of the following:

    • Sending-only: Configures an agent that stores messages in persistent storage, forwards messages to the receiving side, and re-transmits messages when acknowledgements do not come back in time.

    • Receiving-only: Configures an agent that detects and eliminates duplicate messages sent by a receiving agent, and delivers messages to the final destination.

    • Both: Configures an agent that has sending and receiving agent functionality.

    Note:

    JMS SAF users should select Sending-only since JMS SAF doesn't require a configured receiving agent.

For more information about these fields, see Configuration Options.

Targets

On the Targets page, select the server instance, cluster, or migratable target where you want to deploy the SAF agent.

A migratable target is a logical target that serves as a grouping of services, such as a SAF agent, and which is active on only server member in a cluster. High availability is achieved by migrating a migratable target from one server member to another when a problem occurs on the original server.

See Configuration Options.

Note:

Oracle recommends targeting the SAF agent to a migratable target, so that a member server will not be a single point of failure. However, if a SAF agent is targeted to a migratable target, it cannot be targeted to any other server targets, including an entire cluster.

Review

On the Review page, review the configuration for this SAF agent.

See Configuration Options.

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

    • Scope

    • 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.

Parent topic: Store-and-Forward agents

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. Select Monitoring.
  4. To monitor the following SAF agent information, select the appropriate pages:

    • Statistics: displays runtime statistics for this SAF agent.

      See Configuration Options.

    • 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.

      See Configuration Options.

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

      See Configuration Options.

Parent topic: Store-and-Forward agents

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 Monitoring, then 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.

See Configuration Options.

Parent topic: Store-and-Forward agents

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 Monitoring, then 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.

See Configuration Options.

Parent topic: Store-and-Forward agents

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 Monitoring, then 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.

See Configuration Options.

Parent topic: Store-and-Forward agents

Configure SAF agent general settings

To configure general settings for a SAF sending or receiving agent:

  1. From the WebLogic Domain menu, select Messaging, then select Store-and-Forward Agents.
  2. In the SAF table, select the SAF agent you want to configure.
  3. Select Configuration, then select General.

    From the General page, you can view and define basic and advanced properties for this SAF agent, such as:

    • Name

    • Scope

    • Persistent Store

    • Agent Type

    • Conversation Idle Time Maximum

    • Sending Agent Attributes

    • Receiving Agent Attributes

    For more information about these fields, see Configuration Options.

  4. Click Apply.

Parent topic: Store-and-Forward agents

Configure SAF agent thresholds and quotas

To configure thresholds and quotas 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 SAF agent you want to configure.
  3. Select Configuration, then select Thresholds and Quotas.

    From the Thresholds and Quotas page, you can define message threshold and quota settings for this SAF agent, such as:

    • Bytes Threshold High

    • Bytes Threshold Low

    • Messages Threshold High

    • Messages Threshold Low

    • Bytes Maximum

    • Messages Maximum

    • Maximum Message Size

    For more information about these fields, see Configuration Options.

  4. Click Apply.

Parent topic: Store-and-Forward agents

Select SAF agent targets

To select targets 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 SAF agent you want to configure.
  3. Select Targets.

    From the Target menu, select the server instance, cluster, or migratable target on which you want to deploy this SAF agent

    See Configuration Options.

  4. Click Apply.

Parent topic: Store-and-Forward agents

Create SAF agent notes

To create notes 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 SAF agent you want to configure.
  3. Select Notes.
  4. On the Notes page, enter your notes.
  5. Click Apply.

Parent topic: Store-and-Forward agents

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:

Parent topic: WebLogic Server Messaging

Create JMS resources

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.

To create a JMS system resource:

  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.

  3. Click Create.

    Note:

    Once you create a JMS resource, you cannot rename it. Instead, you must delete it and create another JMS resource that uses the new name.

  4. Define the configuration options for your JMS resource on each page of the following sections.
  5. Then, click Create.

    The new JMS resource is added to the JMS Resources table.

Parent topic: JMS resources and modules

Resource Type

On the Resource Type page, choose the type of JMS resource that you would like to create. You can choose to create the following JMS resource types:

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

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

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

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

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

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

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

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

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

  • 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.

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

See Configuration Options.

Parent topic: Create JMS resources

JMS System Module

On the JMS System Module page, select a JMS system module for this JMS resource:

  • In JMS Module, click the icon to select the JMS system module in which you would like to create this JMS resource from the JMS module table.

    If the table is empty or does not contain the JMS module you need, then click Create a New JMS Module to create a JMS module, and then select the JMS module from the table.

  • The Scope field identifies the scope of the selected JMS module.

For more information about these fields, see Configuration Options.

Parent topic: Create JMS resources

Properties

On the Properties page, define the settings for your JMS system resource. Properties depend on the JMS system resource type:

Connection Factory

On the Properties page, define the settings for your connection factory:

  • Resource Type identifies the JMS resource type.

  • In Name, enter a name for the connection factory.

    Once you create a connection factory, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  • In JNDI Name, enter a name for accessing the connection factory within the JNDI name space. Applications use the JNDI Name to look up the connection factory.

    If you do not specify a JNDI name for the connection factory, then it will not be available for JNDI lookup even after the connection factory has been targeted to a server resource. Therefore, you will only be able to access the connection factory in an application-scoped context.

  • In Notes, enter notes about the configuration for this connection factory.

  • In Client ID Policy, select Restricted if only one connection that uses this policy can exist in a cluster at any given time for a particular Client ID. Select Unrestricted if connections created using this policy can specify any Client ID, even when other restricted or unrestricted connections already use the same Client ID.

  • In Subscription Sharing Policy, select Exclusive if all subscribers created using this connection factory cannot share subscriptions with any other subscribers. Select Sharable if subscribers created using this connection factory can share their subscriptions with other subscribers, regardless of whether those subscribers are created using the same connection factory or a different connection factory.

    Consumers can share a non-durable subscriptions only if they have the same Client ID and Client ID Policy; consumers can share a durable subscription only if they have the same Client ID, Client ID Policy, and Subscription Name.

  • In Prefetch Mode for Synchronous Consumer, specifies whether a synchronous consumer will prefetch messages sent from the server to the client in one server access.

  • In Maximum Messages per Session, specify the maximum number of messages that can exist for an asynchronous session and that have not yet been passed to the message listener. When the Synchronous Prefetch Mode is enabled, this value also affects synchronous sessions with a message consumer that will prefetch messages in one server access.

  • Under Distributed Destination Load Balancing, select the appropriate checkboxes if you want to enable load balancing and server affinity.

  • Under Transaction, in Enable XA connection factory, select whether an XA queue or XA topic connection factory is used, instead of a standard queue or topic connection factory.

    An XA factory is required for JMS applications to use JTA user-transactions, but is not required for transacted sessions.

  • In Transacted session transaction timeout, specify the timeout value (in seconds) for all transactions on connections created with this connection factory.

For more information about these fields, see Configuration Options.

Parent topic: Properties

Destination Key

On the Properties page, define the settings for your destination key:

  • Resource Type identifies the JMS resource type.

  • In Name, enter a name for this destination key.

  • In Notes, enter notes about the configuration of this destination key.

  • In Sort Key, select a message sort key from the menu or enter the name of a message header field on which to sort.

  • In Key Type, select the expected property type for the sort key. (This setting is ignored for message header field keys, which have an implied type.)

  • In Direction, select the direction in which the key will sort messages (ascending or descending).

For more information about these fields, see Configuration Options.

Parent topic: Properties

Quota

On the Properties page, define the settings for your quota:

  • Resource Type identifies the JMS resource type.

  • In Name, enter a name for this quota.

  • In Notes, enter notes about the configuration for this quota

  • In Policy, select the delivery policy to determine whether to allow smaller message send requests to be satisfied before larger ones when a destination has exceeded its message quota.

    The default FIFO (first in, first out) policy blocks subsequent newer sender requests until there is enough space for the first request in line, or denies the newer requests with a quota exception if the newer requests time out.

    The Preemptive policy allows newer smaller send requests to preempt previous larger requests when there is sufficient space for smaller messages on the destination, but not sufficient space for the older larger requests.

  • Select Shared by multiple destinations to specify whether this quota is shared by destinations that refer to it.

  • In Total number of bytes that can be stored in a destination, enter the total number of bytes that can be stored in a destination that uses this quota.

  • In Number of messages that can be stored in a destination, enter the total number of messages that can be stored in a destination that uses this quota.

For more information about these fields, see Configuration Options.

Parent topic: Properties

JMS Template

On the Properties page, define the settings for your JMS template:

  • Resource Type identifies the JMS resource type.

  • In Name, enter a name for this JMS template.

  • In Notes, enter notes about the configuration for this JMS template.

For more information about these fields, see Configuration Options.

Parent topic: Properties

JMS Queue

On the Properties page, define the settings for your JMS queue:

  • Resource Type identifies the JMS resource type.

  • In Name, enter a name for the queue.

    Once you create a queue, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  • In Notes, enter notes about the configuration for this JMS queue.

  • In JNDI Name, enter a name for accessing the queue within the JNDI name space. Applications use the JNDI Name to look up the queue.

    If you do not specify a JNDI name for the queue, then it will not be available for JNDI lookup even after it has been targeted to a JMS server. Therefore, you will only be able to access the queue using the javax.jms.queueSession.createqueue() API or in an application-scoped context.

  • If you are using a configured JMS template to define the queue's settings, in Template, select the template for the queue.

For more information about these fields, see Configuration Options.

Parent topic: Properties

Uniform Distributed Queue

On the Properties page, define the settings for your uniform distributed queue:

  • Resource Type identifies the JMS resource type.

  • In Name, enter a name for the uniform distributed queue.

    Once you create a uniform distributed queue, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  • In Notes, enter notes about the configuration for this uniform distributed queue.

  • In JNDI Name, enter the JNDI name used to look up the uniform distributed queue within the JNDI namespace. Applications use the JNDI Name to look up the distributed queue.

    If you do not specify a JNDI name for the distributed queue, then it will not be available for JNDI lookup even after it has been targeted to a server resource. Therefore, you will only be able to access the distributed queue using the javax.jms.queueSession.createqueue() API or in an application-scoped context.

  • Optionally, in Template, specify the template to use when creating this uniform distributed queue. Templates provide an efficient means of defining multiple destinations with similar configuration values.

  • Under Distributed Configuration, in Load Balancing Policy, specify a policy (Round Robin or Random) for how messages are distributed to the members of this distributed queue.

  • In Unit-of-Ordering Routing, specify how the distributed queue members are selected as the destination for a message. If set to Hash, then the producer computes the queue member. If set to Path Service, then the configured Path Service determines the queue member.

  • In Set Forward Delay, select Forward delay to specify the amount of time, in seconds, that a queue member with messages, but with no consumers, will wait before forwarding its messages to other queue members that do have consumers, or select No messages are forwarded.

For more information about these fields, see Configuration Options.

Parent topic: Properties

JMS Topic

On the Properties page, define the settings for your JMS topic:

  • Resource Type identifies the JMS resource type.

  • In Name, enter a name for the topic.

    Once you create a topic, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  • In Notes, enter notes about the configuration for this JMS topic.

  • In JNDI Name, enter a name for accessing the topic within the JNDI name space. Applications use the JNDI Name to look up the topic.

    If you do not specify a JNDI name for the topic, then it will not be available for JNDI lookup even after it has been targeted to a JMS server. Therefore, you will only be able to access the topic using the javax.jms.topicSession.createtopic() API or in an application-scoped context.

  • If you are using a configured JMS template to define the topic's settings, in Template, select the template for the topic.

For more information about these fields, see Configuration Options.

Parent topic: Properties

Uniform Distributed Topic

On the Properties page, define the settings for your uniform distributed topic:

  • Resource Type identifies the JMS resource type.

  • In Name, enter a name for the uniform distributed topic.

    Once you create a uniform distributed topic, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  • In Notes, enter notes about the configuration for this uniform distributed topic.

  • In JNDI Name, enter the JNDI name used to look up the uniform distributed topic within the JNDI namespace. Applications use the JNDI Name to look up the distributed topic.

    If you do not specify a JNDI name for the distributed topic, then it will not be available for JNDI lookup even after it has been targeted to a server resource. Therefore, you will only be able to access the distributed topic using the javax.jms.topicSession.createtopic() API or in an application-scoped context.

  • Optionally, in Template, select a template to define configuration values.

  • Under Distributed Configuration, in Forwarding Policy, specify Replicated to allow a member to replicate (forward) information to other members of the distributed topic.

  • In Load Balancing Policy, specify how messages are distributed to the members of this destination.

  • In Unit-of-Order Routing, specify how the distributed topic members are selected as the destination for a message. If set to Hash, then the producer computes the topic member. If set to Path Service, then the configured Path Service determines the topic member.

For more information about these fields, see Configuration Options.

Parent topic: Properties

Remote SAF Context

On the Properties page, define the settings for your remote SAF context:

  • Resource Type identifies the JMS resource type.

  • In Name, enter the name for the remote SAF context.

  • In Notes, enter notes about the configuration for this remote SAF context.

  • In Compression Threshold, specify the number of bytes for a serialized message body so that any message that exceeds this limit triggers message compression.

  • In Reply to Remote SAF Context, specify the name of the remote SAF context used by the replyTo destination in the remote cluster or server.

  • Select Specify the Login Context to specify a URL, user name and password when using this remote SAF context.

  • In URL, specify the URL that the imported queue or topic uses to connect to the remote destination.

  • In User Name, specify the user name that the imported queue or topic gives to the remote destination.

  • In Password, enter the password that the imported queue or topic gives to the remote destination.

  • In Confirm Password, confirm the specified password.

For more information about these fields, see Configuration Options.

Parent topic: Properties

SAF Error Handling

On the Properties page, define the settings for your SAF error handling resource:

  • Resource Type identifies the JMS resource type.

  • In Name, enter a name for the SAF error handling resource.

    Once you create a SAF error handling resource, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  • In Notes, enter notes about the configuration for this SAF error handling resource.

  • In SAF Error Handling Policy, select the policy type for this SAF error handling resource:

    • Discard:

    • Log: specify the log format or add a new log format for this SAF error handling resource.

    • Redirect: select an error destination for this SAF error handling resource.

    • Always-forward:

For more information about these fields, see Configuration Options.

Parent topic: Properties

SAF Import Destination

On the Properties page, define the settings for your SAF import destination:

  • Resource Type identifies the JMS resource type.

  • In Name, enter a name for the SAF imported destinations resource.

    Once you create a SAF imported destination, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  • In Notes, enter notes about the configuration for this SAF import destination.

  • In JNDI Prefix, specify a prefix that is appended to the remote destination JNDI name.

    If you do not specify a JNDI name for the SAF imported destination, then it will not be available for JNDI lookup even after the SAF imported destination has been targeted to a server resource. Therefore, you will only be able to access the SAF imported destination in an application-scoped context.

  • In Remote SAF Context, select a remote context instance. If necessary, create a new remote SAF context and then select it from the menu.

  • In SAF Error Handling, select an error handling instance. If necessary, create a new SAF error handling resource and then select it from the menu.

  • In Message Unit-of-Order Routing,

  • In SAF Default Time-to-Live, specify a default Time-to-Live value, in milliseconds, for JMS messages. The expiration time set on JMS messages will override this value unless the Enable SAF Default Time-to-Live checkbox is selected.

  • Select Enable SAF Default Time-to-Live to override the expiration time set on JMS messages with the value specified this field.

For more information about these fields, see Configuration Options.

Parent topic: Properties

Foreign Server

On the Properties page, define the settings for your foreign server:

  • Resource Type identifies the JMS resource type.

  • In Name, enter a name for the foreign server.

    Once you create a foreign server, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  • In Notes, enter notes about the configuration for this foreign server.

  • In JNDI Initial Context Factory, enter the name of the class that must be instantiated to access the JNDI provider. This class name depends on the provider and vendor that are being used.

  • In JNDI Connection URL, enter the URL that WebLogic Server uses to contact the JNDI provider. The syntax of this URL depends on which JNDI provider is being used. For WebLogic JMS, leave this field blank if you are referencing WebLogic JMS objects within the same cluster.

  • In JNDI Properties Credential, specify any credentials that must be set for the JNDI provider. These Credentials will be part of the properties that will be passed directly to the constructor for the JNDI provider's InitialContext class. When connecting to a remote domain, you must specify the secure password for the domain (e.g., remote_domain_password) along with the domain username in the JNDI Properties field.

  • In Confirm JNDI Properties Credential, re-enter any credentials that must be set for the JNDI provider.

  • In JNDI Properties, specify any additional properties that must be set for the JNDI provider.

    These properties will be passed directly to the constructor for the JNDI provider's InitialContext class. When connecting to a remote domain, you must specify the secure username for the domain using the following format: java.naming.security.principal=remote_domain_username

    Note:

    The JNDI Properties values may be a name=value list of properties, separated by commas.

For more information about these fields, see Configuration Options.

Parent topic: Properties

Targets

On the Targets page, specify the targeting policy for this JMS resource:

  • Select Default to the parent module's target to use the default targeting.

  • Select Subdeployment targeting to choose an existing subdeployment or to create a new one.

    • To select an existing subdeployment for the connection factory, select one from the Subdeployment Name menu. When a valid subdeployment is selected, its targeted JMS server(s), server(s), or cluster appear as selected in the Targets box. (A subdeployment with stand-alone destinations can only be targeted to a single JMS server.)

    • To create a new subdeployment for the connection factory, click the Create a New Subdeployment button. See ADD CREATE SUBDEPLOYMENT TAKSK HERE.

For more information about these fields, see Configuration Options.

Parent topic: Create JMS resources

Review

On the Review page, review the configuration for this JMS resource.

See Configuration Options.

Parent topic: Create JMS resources

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 settings 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 queues and Monitor SAF topics.

    • 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

    • Scope

    • 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.

Parent topic: JMS resources and modules

Monitor, control, and configure queues

A JMS queue is based on the point-to-point (PTP) messaging model, which enables one application to send a message to another. PTP messaging applications send and receive messages using named queues. A queue sender (producer) sends a message to a specific queue. A queue receiver (consumer) receives messages from a specific queue.

You configure queues explicitly or by configuring a JMS template that can be used to define multiple queues with similar option settings, as described in Configure JMS templates.

Note:

To help manage recovered or rolled back messages, you can also configure a target error destination for messages that have reached their redelivery limit. However, the error destination must be targeted to same JMS server as the other queues in a module.

Some queue options are dynamically configurable. When options are modified at runtime, only incoming messages are affected; stored messages are not affected.

This section includes the following tasks:

Parent topic: JMS resources and modules

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.
  4. Select Monitoring.

    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.

    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 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.

See Configuration Options.

Configure general queue settings

After you create a queue, you can define general property values, such as selecting a destination key for sorting messages as they arrive on the queue, or a selecting JMS template if you are using one to configure properties for multiple queues.

To define general configuration settings for a 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 queue you want to configure.
  4. Select Configuration, then select General.

    From the General page, you can view and configure general settings for this queue, such as:

    • Name

    • Scope

    • JNDI Name

    • Template

    • Targeting policy

    • Subdeployment

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure advanced queue settings

After you create a queue, you can define advanced property values, such as specifying unit-of-order parameters, attaching the credentials of message senders, or defining unit-of-work parameters.

To define advanced configuration settings for a 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 queue you want to configure.
  4. Select Configuration, then select Advanced Configuration.

    From the Advanced Configuration page, you can configure additional settings for this queue, such as:

    • Pause Message Production at Startup

    • Pause Message Consumption at Startup

    • Pause Message Insertion at Startup

    • Auto-generate Unit-of-Order Name

    • Attach Sender Credential

    • Local JNDI Name

    • Create Destination Identifier

    • SAF Export Policy

    • Messaging Performance Preference

    • Unit-of-Work (UOW) Message Handling Policy

    • Expiration Time for Incomplete UOW Messages

    • Destination Keys

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure queue message delivery failure options

After you create a queue, you can change the default message delivery failure values, like defining a message redelivery limit, selecting a message expiration policy, and specifying an error destination for expired or undeliverable messages.

To define general configuration settings for a 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 queue you want to configure.
  4. Select Configuration, then select Delivery Failure.

    From the Delivery Failure page, you can configure message delivery settings for this queue, such as:

    • Expiration Policy

    • All Headers

    • Headers

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure queue message delivery overrides

After you create a queue, you can define message delivery override values that can override those specified by a message producer.

To configure message delivery overrides for a queue:

  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 configure.
  4. Select Configuration, then select Delivery Overrides.

    From the Delivery Overrides page, you can define override settings for this queue, such as:

    • Delivery Mode Override

    • Time-to-Deliver Override

    • Priority Override

    • Time-to-Live Override

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure queue message logging

After you create a queue, you can enable the logging of message life cycle information into a JMS message log file. A message life cycle is an external view of the basic events that a JMS message traverses through, such as message production, consumption, and removal. The content of the message log always includes message ID and correlation ID, but you can also configure information like message type and user properties.

To configure life cycle logging for messages on this queue:

  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 configure.
  4. Select Configuration, then select Logging.

    From the Logging page, you can configure message life cycle logging options for this queue, such as:

    • Enable Message Logging

    • All Headers

    • Headers

    • All Properties

    • Properties

    • User-defined Properties

    • All Body

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure queue thresholds and quotas

After you create a queue, you can change the default upper and lower byte and/or message thresholds for the queue. Exceeding these thresholds will trigger events, such as generating log messages and starting message flow control. You can also specify a maximum size allowed for messages on the queue, and select a pre-configured quota, which determines the maximum number of bytes or messages that the queue is allowed to store to conserve memory use.

If a JMS template is specified for this queue, then the default values imply that the actual value will come from the template, see Configure JMS template thresholds and quotas. A JMS server can also manage thresholds and certain quota settings for all destinations in a JMS module targeted to that JMS server, see Configure JMS server thresholds and quotas.

To configure thresholds and quotas for a 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 queue you want to configure.
  4. Select Configuration, then select Thresholds and Quotas.

    From the Thresholds and Quotas page, you can define message threshold and quota settings for this queue, such as:

    • Bytes Threshold High

    • Bytes Threshold Low

    • Messages Threshold High

    • Messages Threshold Low

    • Quota

    • Maximum Message Size

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Create queue notes

To create notes about a queue:

  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 create notes.
  4. Select Notes.
  5. On the Notes page, enter your notes.
  6. Click Save.

Monitor and configure uniform distributed queues

A distributed queue is a single unit of JMS queues that are accessible as a single, logical queue to a client (for example, a distributed queue has its own JNDI name). The members of the unit are usually distributed across multiple servers within a cluster, with each queue member belonging to a separate JMS server.

By configuring uniform distributed queues, WebLogic Server uniformly creates the necessary members on the JMS servers to which a JMS module is targeted. This ensures the consistent configuration of all distributed destination parameters, particularly in regards to weighting, security, persistence, paging, and quotas across a cluster.

This section includes the following tasks:

Parent topic: JMS resources and modules

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.
  4. Select Monitoring.

    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

Configure general uniform distributed queue settings

After you create a uniform distributed queue, you can modify and define general property values, such as selecting a destination key for sorting messages as they arrive on the members of the distributed queue.

To define general configuration settings for 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 configure.
  4. Select Configuration, then select General.

    From the General page, you can view and configure general settings for this uniform distributed queue, such as:

    • Name

    • Scope

    • JNDI Name

    • Template

    • Load Balancing Policy

    • Unit-of-Ordering Routing

    • Set the Forward Delay

    • Reset Delivery Count On Forward

    • Targeting policy

    • Subdeployment

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure advanced uniform distributed queue settings

After you create a distributed queue, you can define advanced property values, such as specifying unit-of-order parameters and attaching the credentials of message senders.

To define advanced configuration settings for 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 configure.
  4. Select Configuration, then select Advanced Configuration.

    From the Advanced Configuration page, you can configure additional settings for this uniform distributed queue, such as:

    • Pause Message Production at Startup

    • Pause Message Consumption at Startup

    • Pause Message Insertion at Startup

    • Auto-generate Unit-of-Order Name

    • Attach Sender Credential

    • Local JNDI Name

    • Create Destination Identifier

    • SAF Export Policy

    • Messaging Performance Preference

    • Unit-of-Work (UOW) Message Handling Policy

    • Expiration Time for Incomplete UOW Messages

    • Destination Keys

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure uniform distributed queue message delivery failure options

After you create a uniform distributed queue, you can change the default message delivery failure values, like defining a message redelivery limit, selecting a message expiration policy, and specifying an error destination for expired or undeliverable messages.

To define general configuration settings for 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 configure.
  4. Select Configuration, then select Delivery Failure.

    From the Delivery Failure page, you can configure message delivery settings for this uniform distributed queue, such as:

    • Expiration Policy

    • All Headers

    • Headers

    • All Properties

    • Properties

    • All Body

    • Error Destination

    • Redelivery Limit

    • Redelivery Delay Override

    • Expiration Logging Format

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure uniform distributed queue message delivery overrides

After you create a uniform distributed queue, you can define message delivery override values that can override those specified by a message producer.

To configure message delivery overrides for a uniform distributed queue:

  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 configure.
  4. Select Configuration, then select Delivery Overrides.

    From the Delivery Overrides page, you can define override settings for this uniform distributed queue, such as:

    • Delivery Mode Override

    • Time-to-Deliver Override

    • Priority Override

    • Time-to-Live Override

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure uniform distributed queue message logging

After you create a uniform distributed queue, you can enable the logging of message life cycle information into a JMS message log file. A message life cycle is an external view of the basic events that a JMS message traverses through, such as message production, consumption, and removal. The content of the message log always includes message ID and correlation ID, but you can also configure information like message type and user properties.

To configure life cycle logging for messages on this uniform distributed queue:

  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 configure.
  4. Select Configuration, then select Logging.

    From the Logging page, you can configure message life cycle logging options for this uniform distributed queue, such as:

    • Enable Message Logging

    • All Headers

    • Headers

    • All Properties

    • Properties

    • User-defined Properties

    • All Body

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure uniform distributed queue thresholds and quotas

After you create a uniform distributed queue, you can change the default upper and lower byte and/or message thresholds for the distributed queue members. Exceeding these thresholds will which trigger events such as generating log messages and starting message flow control. You can also select a pre-configured quota, which specifies the maximum number of bytes or messages that the distributed queue is allowed to store to conserver memory use. You can also specify a maximum size allowed for messages on the distributed queue.

To configure thresholds and quotas for 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 configure.
  4. Select Configuration, then select Thresholds and Quotas.

    From the Thresholds and Quotas page, you can define message threshold and quota settings for this uniform distributed queue, such as:

    • Bytes Threshold High

    • Bytes Threshold Low

    • Messages Threshold High

    • Messages Threshold Low

    • Quota

    • Maximum Message Size

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Create uniform distributed queue notes

To create notes about a uniform distributed queue:

  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 for which you want to create notes.
  4. Select Notes.
  5. On the Notes page, enter your notes.
  6. Click Save.

Monitor, control, and configure topics

A JMS topic is based on the publish/subscribe (pub/sub) messaging model, which enables an application to send a message to multiple applications. Pub/sub messaging applications send and receive messages by subscribing to a topic. A topic publisher (producer) sends messages to a specific topic. A topic subscriber (consumer) retrieves messages from a specific topic.

You configure topics explicitly or by configuring a JMS template that can be used to define multiple topics with similar option settings, as described in Configure JMS templates.

Note:

To help manage recovered or rolled back messages, you can also configure a target error destination for messages that have reached their redelivery limit. The error destination must be targeted to same JMS server as the other topics in the module.

Some topic options are dynamically configurable. When options are modified at runtime, only incoming messages are affected; stored messages are not affected.

This section includes the following tasks:

Parent topic: JMS resources and modules

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.
  4. Select Monitoring, then select Statistics.

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

    • Name

    • Messages Current

    • Messages Pending

    • Messages Total

    • Consumers Current

    • Subscription Messages Limit

    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. 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

    • Messages deleted due to Subscription limit

    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

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 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.

See Configuration Options.

Configure general topic settings

After you create a topic, you can define general property values, such as selecting a destination key for sorting messages as they arrive on the topic, or a selecting JMS template if you are using one to configure properties for multiple topics.

To define general configuration settings for a 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 topic you want to configure.
  4. Select Configuration, then select General.

    From the General page, you can view and configure general settings for this topic, such as:

    • Name

    • Scope

    • JNDI Name

    • Template

    • Targeting policy

    • Subdeployment

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure advanced topic settings

After you create a topic, you can define advanced general property values, such as specifying unit-of-order parameters and attaching the credentials of message senders.

To define advanced configuration settings for a 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 topic you want to configure.
  4. Select Configuration, then select Advanced Configuration.

    From the Advanced Configuration page, you can configure advanced settings for this topic, such as:

    • Pause Message Production at Startup

    • Pause Message Consumption at Startup

    • Pause Message Insertion at Startup

    • Auto-generate Unit-of-Order Name

    • Attach Sender Credential

    • Local JNDI Name

    • Create Destination Identifier

    • SAF Export Policy

    • Messaging Performance Preference

    • Unit-of-Work (UOW) Message Handling Policy

    • Expiration Time for Incomplete UOW Messages

    • Destination Keys

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure topic message delivery failure options

After you create a topic, you can change the default message delivery failure values, like defining a message redelivery limit, selecting a message expiration policy, and specifying an error destination for expired or undeliverable messages.

To define general configuration settings for a 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 topic you want to configure.
  4. Select Configuration, then select Delivery Failure.

    From the Delivery Failure page, you can configure message delivery settings for this topic, such as:

    • Expiration Policy

    • All Headers

    • Headers

    • All Properties

    • Properties

    • User-defined Properties

    • All Body

    • Error Destination

    • Redelivery Limit

    • Redelivery Delay Override

    • Expiration Logging Format

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure topic message delivery overrides

After you create a topic, you can define message delivery override values that can override those specified by a message producer.

To configure message delivery overrides for a 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 you want to configure.
  4. Select Configuration, then select Delivery Overrides.

    From the Delivery Overrides page, you can define override settings for this topic, such as:

    • Delivery Mode Override

    • Time-to-Deliver Override

    • Priority Override

    • Time-to-Live Override

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure topic message logging

After you create a topic, you can enable the logging of message life cycle information into a JMS message log file. A message life cycle is an external view of the basic events that a JMS message traverses through, such as message production, consumption, and removal. The content of the message log always includes message ID and correlation ID, but you can also configure information like message type and user properties.

To configure life cycle logging for messages on this 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 you want to configure.
  4. Select Configuration, then select Logging.

    From the Logging page, you can configure message life cycle logging options for this topic, such as:

    • Enable Message Logging

    • All Headers

    • Headers

    • All Properties

    • Properties

    • User-defined Properties

    • All Body

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure topic multicast settings

After you configure a topic, you can define multicast parameters that enable the delivery of messages to a select group of hosts that subsequently forward the messages to subscribers.

To configure multicast options for this 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 you want to configure.
  4. Select Configuration, then select Multicast.

    From the Multicast page, you can configure multicast options for this topic, such as:

    • Multicast Address

    • Multicast TTL

    • Multicast Port

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure topic thresholds and quotas

After you create a topic, you can change the default upper and lower byte and/or message thresholds for the topic. Exceeding these thresholds will trigger events, such as generating log messages and starting message flow control. You can also specify a maximum size allowed for messages on the topic, and select a pre-configured quota, which determines the maximum number of bytes or messages that the topic is allowed to store to conserve memory use.

If a JMS template is specified for this topic, then the default values imply that the actual value will come from the template, see Configure JMS template thresholds and quotas. A JMS server can also manage thresholds and certain quota settings for all destinations in a JMS module targeted to that JMS server, see Configure JMS server thresholds and quotas.

To configure thresholds and quotas for a 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 topic you want to configure.
  4. Select Configuration, then select Thresholds and Quotas.

    From the Thresholds and Quotas page, you can define message threshold and quota settings for this topic, such as:

    • Bytes Threshold High

    • Bytes Threshold Low

    • Messages Threshold High

    • Messages Threshold Low

    • Quota

    • Maximum Message Size

    • Topic Subscription Message Limit

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Create topic notes

To create notes about a 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 for which you want to create notes.
  4. Select Notes.
  5. On the Notes page, enter your notes.
  6. Click Save.

Monitor and configure uniform distributed topics

A distributed topic is a single unit of JMS topics that are accessible as a single, logical topic to a client (for example, a distributed topic has its own JNDI name). The members of the unit are usually distributed across multiple servers within a cluster, with each topic member belonging to a separate JMS server.

By configuring uniform distributed topics, WebLogic Server uniformly creates the necessary members on the JMS servers to which a JMS module is targeted. This ensures the consistent configuration of all distributed destination parameters, particularly in regards to weighting, security, persistence, paging, and quotas across a cluster.

This section includes the following tasks:

Parent topic: JMS resources and modules

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.
  4. Select Monitoring.

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

    • Name

    • Consumers Current

    • Consumers High

    • Consumers Total

    • Subscription Messages Limit

    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. 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

    • Messages deleted due to Subscription limit

    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 general uniform distributed topic settings

After you create a uniform distributed topic, you can modify and define general property values, such as selecting a destination key for sorting messages as they arrive on the members of the distributed topic.

To define general configuration settings for 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 configure.
  4. Select Configuration, then select General.

    From the General page, you can view and configure general settings for this uniform distributed topic, such as:

    • Name

    • Scope

    • JNDI Name

    • Template

    • Load Balancing Policy

    • Unit-of-Order Routing

    • Targeting policy

    • Subdeployment

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure advanced uniform distributed topic settings

After you create a uniform distributed topic, you can define advanced property values, such as specifying unit-of-order parameters and attaching the credentials of message senders.

To define advanced configuration settings for 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 configure.
  4. Select Configuration, then select Advanced Configuration.

    From the Advanced Configuration page, you can configure advanced settings for this uniform distributed topic, such as:

    • Pause Message Production at Startup

    • Pause Message Consumption at Startup

    • Pause Message Insertion at Startup

    • Auto-generate Unit-of-Order Name

    • Attach Sender Credential

    • Local JNDI Name

    • Create Destination Identifier

    • SAF Export Policy

    • Messaging Performance Preference

    • Unit-of-Work (UOW) Message Handling Policy

    • Expiration Time for Incomplete UOW Messages

    • Destination Keys

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure uniform distributed topic message delivery failure options

After you create a uniform distributed topic, you can change the default message delivery failure values, like defining a message redelivery limit, selecting a message expiration policy, and specifying an error destination for expired or undeliverable messages.

To define general configuration settings for 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 configure.
  4. Select Configuration, then select Delivery Failure.

    From the Delivery Failure page, you can configure message delivery settings for this uniform distributed topic, such as:

    • Expiration Policy

    • All Headers

    • Headers

    • All Properties

    • Properties

    • User-defined Properties

    • All Body

    • Error Destination

    • Redelivery Limit

    • Redelivery Delay Override

    • Expiration Logging Format

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure uniform distributed topic message delivery overrides

After you create a uniform distributed topic, you can define message delivery override values that can override those specified by a message producer.

To configure message delivery overrides for a 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 uniform distributed topic you want to configure.
  4. Select Configuration, then select Delivery Overrides.

    From the Delivery Overrides page, you can define override settings for this uniform distributed topic, such as:

    • Delivery Mode Override

    • Time-to-Deliver Override

    • Priority Override

    • Time-to-Live Override

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure uniform distributed topic message logging

After you create a uniform distributed topic, you can enable the logging of message life cycle information into a JMS message log file. A message life cycle is an external view of the basic events that a JMS message traverses through, such as message production, consumption, and removal. The content of the message log always includes message ID and correlation ID, but you can also configure information like message type and user properties.

To configure life cycle logging for messages on this 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 uniform distributed topic you want to configure.
  4. Select Configuration, then select Logging.

    From the Logging page, you can configure message life cycle logging options for this uniform distributed topic, such as:

    • Enable Message Logging

    • All Headers

    • Headers

    • All Properties

    • Properties

    • User-defined Properties

    • All Body

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure uniform distributed topic multicast settings

After you configure a distributed topic, you can define multicast parameters that enable the delivery of messages to a select group of hosts that subsequently forward the messages to subscribers.

To configure multicast options for this 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 uniform distributed topic you want to configure.
  4. Select Configuration, then select Multicast.

    From the Multicast page, you can configure multicast options for this uniform distributed topic, such as:

    • Multicast Address

    • Multicast TTL

    • Multicast Port

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure uniform distributed topic thresholds and quotas

After you create a uniform distributed topic, you can change the default upper and lower byte and/or message thresholds for the distributed topic members. Exceeding these thresholds will which trigger events such as generating log messages and starting message flow control. You can also select a pre-configured quota, which specifies the maximum number of bytes or messages that the distributed topic is allowed to store to conserver memory use. You can also specify a maximum size allowed for messages on the distributed topic.

To configure thresholds and quotas for 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 configure.
  4. Select Configuration, then select Thresholds and Quotas.

    From the Thresholds and Quotas page, you can define message threshold and quota settings for this uniform distributed topic, such as:

    • Bytes Threshold High

    • Bytes Threshold Low

    • Messages Threshold High

    • Messages Threshold Low

    • Quota

    • Maximum Message Size

    • Topic Subscription Message Limit

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Create uniform distributed topic notes

To create notes about a 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 uniform distributed topic for which you want to create notes.
  4. Select Notes.
  5. On the Notes page, enter your notes.
  6. Click Save.

Configure connection factories

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.

This section includes the following tasks:

Parent topic: JMS resources and modules

Configure general connection factory settings

To define general configuration settings for a connection factory 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 connection factory you want to configure.
  4. Select Configuration, then select General.

    From the General page, you can view and configure settings for this connection factory, such as:

    • Name

    • Scope

    • JNDI Name

    • Client ID Policy

    • Subscription Sharing Policy

    • Prefetch Mode for Synchronous Consumer

    • Maximum Messages per Session

    • Load Balancing Enabled

    • Server Affinity Enabled

    • XA Connection Factory Enabled

    • Transaction Timeout

    • Targeting Policy

    • Subdeployment

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure advanced connection factory settings

To define advanced configuration settings for a connection factory 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 connection factory you want to configure.
  4. Select Configuration, then select Advanced Configuration.

    From the Advanced Configuration page, you can define advanced configuration settings for this connection factory, such as:

    • Client ID

    • Allow Close() Within onMessage()

    • Client Acknowledge Policy

    • Multicast Overrun Policy

    • Local JNDI Name

    • Reconnect Policy

    • Reconnect Blocking Time

    • Total Reconnect Time

    • Attach JMSXUserId

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure connection factory default delivery settings

After you configure a connection factory, you can define various default message delivery settings. For example, if a client does not specify certain delivery settings then the value of those settings can be controlled with the default delivery settings on this page. In addition, you can associate a unit-of-order with all sessions created from a factory configured with unit-of-order enabled, and, optionally, a name provided. As a result, all sessions created from this connection factory will have unit-of-order enabled. All messages produced from the same session will belong to the same unit-of-order. Messages from different sessions belong to different unit-of-orders.

To define default deliver settings for a connection factory 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 connection factory you want to configure.
  4. Select Configuration, then select Default Delivery.

    From the Default Delivery page, you can configure default delivery settings for this connection factory, such as:

    • Default Delivery Mode

    • Default Priority

    • Default Time-to-Deliver

    • Default Redelivery Delay

    • Default Compression Threshold

    • Default Time-to-Live

    • Send Timeout

    • Default Unit-of-Order for Producer

    • User-generated Unit-of-Order Name

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Configure connection factory flow control

Flow control allows you to tell a JMS server or destination to slow down message producers when it determines that it is becoming overloaded. Specifically, when a JMS server or destination exceeds its specified bytes or messages thresholds, it instructs producers to limit their message flow (messages per second).

To configure message flow control on a connection factory:

  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 connection factory you want to configure.
  4. Select Configuration, then select Flow Control.
  5. In Flow Control Enabled, enable or disable flow control.

    If you are using the flow control feature, then you can define the flow control configuration settings for this connection factory, such as:

    • Flow Minimum

    • Flow Maximum

    • Flow Interval

    • Flow Steps

    • One-Way Send Mode

    • One-Way Send Window Size

    For more information about these fields, see Configuration Options.

  6. Click Apply.
Create connection factory notes

To create notes about a connection factory:

  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 connection factory for which you want to create notes.
  4. Select Notes.
  5. On the Notes page, enter your notes.
  6. Click Save.

Configure destination keys

As messages arrive on a specific destination, by default they are sorted in FIFO (first-in, first-out) order, which sorts ascending based on each message's unique JMSMessageID. However, you can use a destination key to configure a different sorting scheme for a destination, such as LIFO (last-in, first-out).

After you configure a destination key, you can select it from within a destination resource, such as a queue, topic, distributed queue, distributed topic, or JMS template if you are using templates to configure your destinations.

This section includes the following tasks:

Parent topic: JMS resources and modules

Configure destination key settings

To define general configuration settings for a destination key 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 destination key you want to configure.
  4. Select Configuration.

    From the Configuration page, you can view and define configuration settings for this destination key, such as:

    • Name

    • Scope

    • Sort Key

    • User-defined Sort Key

    • Key Type

    • Direction

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Create destination key notes

To create notes about a destination key:

  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 destination key for which you want to create notes.
  4. Select Notes.
  5. On the Notes page, enter your notes.
  6. Click Save.

Configure quotas for destinations

JMS quotas are used to control the allotment of system resources available to destinations. For example, you can specify the number of bytes or messages that a destination is allowed to store, or specify whether the quota can be shared be all destinations that refer to it.

Once you configure a quota, you can select it on the Thresholds and Quota page from within a destination resource, such as a queue, topic, distributed queue, distributed topic, or JMS template if you are using templates to configure your destinations.

This section includes the following tasks:

Parent topic: JMS resources and modules

Configure quota settings

To define general configuration settings for a quota 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 quota you want to configure.
  4. Select Configuration.

    From the Configuration page, you can view and define configuration settings for this quota, such as:

    • Name

    • Scope

    • Policy

    • Shared by multiple destination

    • Total number of bytes that can be stored in a destination

    • Total number of messages that can be stored in a destination

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Create quota notes

To create notes about a quota:

  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 quota for which you want to create notes.
  4. Select Notes.
  5. On the Notes page, enter your notes.
  6. Click Save.

Configure JMS templates

A JMS template provides an efficient means of defining multiple JMS queues and topics with similar configuration settings. Instead of re-entering configuration settings each time you define a new queue or topic, you can use a template and override the settings for which you want to assign a new value.

Once you configure a JMS template, you can select it from within a queue or topic resource.

This section includes the following tasks:

Parent topic: JMS resources and modules

Configure JMS template settings

To view general configuration settings for a JMS template 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 JMS template you want to configure.
  4. Select Configuration, then select General.

    From the General page, you can view configuration settings for this JMS template, such as:

    • Name

    • Scope

    For more information about these fields, see Configuration Options.

Parent topic: Configure JMS templates

Configure advanced JMS template settings

After you create a template, you can define advanced property values, such as specifying unit-of-order parameters, attaching the credentials of message senders, or defining unit-of-work parameters.

To define advanced configuration settings for a JMS template 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 JMS template you want to configure.
  4. Select Configuration, then select Advanced Configuration.

    From the Advanced Configuration page, you can define advanced configuration settings for this JMS template, such as:

    • Pause Message Production at Startup

    • Pause Message Consumption at Startup

    • Pause Message Insertion at Startup

    • Aut-generate Unit-of-Order Name

    • Attach Sender Credential

    • Local JNDI Name

    • Create Destination Identifier

    • SAF Export Policy

    • Messaging Performance Preference

    • Unit-of-Work (UOW) Message Handling Policy

    • Expiration Time for Incomplete UOW Messages

    • Sorting Destination Keys

    For more information about these fields, see Configuration Options.

  5. Click Apply.

Parent topic: Configure JMS templates

Configure JMS template message delivery failure settings

After you create a JMS template, you can change the default message delivery failure values for destinations, like defining a message redelivery limit, selecting a message expiration policy, and specifying an error destination for expired messages.

To configure message redelivery options for a JMS template 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 JMS template you want to configure.
  4. Select Configuration, then select Delivery Failure.

    From the Delivery Failure page, you can define delivery failure settings for destinations created from this JMS template, such as:

    • Expiration Policy

    • All Headers

    • Headers

    • All Properties

    • Properties

    • User-defined Properties

    • All Body

    • Error Destination

    • Redelivery Limit

    • Redelivery Delay Override

    • Expiration Logging Format

    For more information about these fields, see Configuration Options.

  5. Click Apply.

Parent topic: Configure JMS templates

Configure JMS template message delivery overrides

After you create a JMS template, you can define message delivery override values that can override those specified by a message producer.

To configure message delivery overrides for a JMS template 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 JMS template you want to configure.
  4. Select Configuration, then select Delivery Overrides.

    From the Delivery Overrides page, you can configure delivery override settings for this JMS template, such as:

    • Delivery Mode Override

    • Time-to-Deliver Override

    • Priority Override

    • Time-to-Live Override

    For more information about these fields, see Configuration Options.

  5. Click Apply.

Parent topic: Configure JMS templates

Configure JMS template message logging

After you create a JMS template, you can enable the logging of message life cycle information for destinations into a JMS message log file. A message life cycle is an external view of the basic events that a JMS message traverses through, such as message production, consumption, and removal. The content of the message log always includes message ID and correlation ID, but you can also configure information like message type and user properties.

To configure destination logging for a JMS template 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 JMS template you want to configure.
  4. Select Configuration, then select Logging.

    From the Logging page, you can configure destination logging settings for this JMS template, such as:

    • Enable Message Logging

    • All Headers

    • Headers

    • All Properties

    • Properties

    • User-defined Properties

    • All Body

    For more information about these fields, see Configuration Options.

  5. Click Apply.

Parent topic: Configure JMS templates

Configure JMS template multicast settings

After you configure a JMS template, you can define multicast parameters for topics that enable the delivery of messages to a select group of hosts that subsequently forward the messages to subscribers.

To configure multicast options for a JMS template 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 JMS template you want to configure.
  4. Select Configuration, then select Multicast.

    From the Multicast page, you can configure multicast settings for this JMS template, such as:

    • Multicast Address

    • Multicast TTL

    • Multicast Port

    For more information about these fields, see Configuration Options.

  5. Click Apply.

Parent topic: Configure JMS templates

Configure JMS template thresholds and quotas

After you create a JMS template, you can define upper and lower message/byte threshold and quota values for queues and topics created from a JMS template.

To configure thresholds and quotas for a JMS template 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 JMS template you want to configure.
  4. Select Configuration, then select Thresholds and Quotas.

    From the Thresholds and Quotas page, you can define threshold and quota settings for this JMS template, such as:

    • Bytes Threshold High

    • Bytes Threshold Low

    • Messages Threshold High

    • Messages Threshold Low

    • Quota

    • Maximum Message Size

    • Topic Subscription Message Limit

    For more information about these fields, see Configuration Options.

  5. Click Apply.

Parent topic: Configure JMS templates

Create JMS template notes

To create notes about a JMS template:

  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 JMS template for which you want to create notes.
  4. Select Notes.
  5. On the Notes page, enter your notes.
  6. Click Save.

Parent topic: Configure JMS templates

Configure remote SAF contexts

A remote SAF context resource specifies the login context that the imported SAF queue or SAF topic uses to connect to a remote destination.

This section includes the following tasks:

Parent topic: JMS resources and modules

Configure general SAF remote context settings

To define general configuration settings for a SAF remote context 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 remote context you want to configure.
  4. Select Configuration.

    From the Configuration page, you can view and configure general settings for this SAF remote context, such as:

    • Name

    • Scope

    • URL

    • User Name

    • Password

    • Confirm Password

    • Compression Threshold

    • ReplyTo Remote SAF Context

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Create SAF remote context notes

To create notes about a SAF remote context:

  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 remote context for which you want to create notes.
  4. Select Notes.
  5. On the Notes page, enter your notes.
  6. Click Save.

Configure SAF error handling resources

A SAF error handling resource specifies the action to be taken when the SAF service fails to forward messages to a remote destination.

This section includes the following tasks:

Parent topic: JMS resources and modules

Configure general SAF error handler settings

To define general configuration settings for a SAF error handler 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 error handler you want to configure.
  4. Select Configuration.

    From the Configuration page, you can view and configure general settings for this SAF error handler, such as:

    • Name

    • Scope

    • Message Handling Policy

    • Log Format

    • Error Destination

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Create SAF error handler notes

To create notes about a SAF error handler:

  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 error handler for which you want to create notes.
  4. Select Notes.
  5. On the Notes page, enter your notes.
  6. Click Save.

Configure 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.

This section includes the following tasks:

Parent topic: JMS resources and modules

Configure general SAF imported destination settings

To define general configuration settings for a foreign server 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 configure.
  4. Select Configuration, then select General.

    From the General page, you can view and configure settings for this SAF imported destination, such as:

    • Name

    • JNDI Prefix

    • Remote SAF Context

    • SAF Error Handling

    • Enable SAF Default Time-to-Live

    • SAF Default Time-to-Live

    • Message Unit-of-Order Routing

    • Targeting Policy

    • Subdeployment

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Monitor SAF queues

To view the SAF queues that have been created for this SAF imported destination:

  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 for which you want to monitor SAF queues.
  4. Select Configuration, then select Queues.

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

    See Configuration Options.

  5. To create a new SAF queue, click Create. See Create SAF queues and SAF topics.
Monitor SAF topics

To view the SAF topics that have been created for this SAF imported destination:

  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 for which you want to monitor SAF topics.
  4. Select Configuration, then select Topics.

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

    See Configuration Options.

  5. To create a new SAF topic, click Create. See Create SAF queues and SAF topics.
Create SAF queues and SAF topics

This section includes the following topics:

Create a SAF queue

A SAF queue represents a JMS queue in a remote server or cluster. 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.

To create a SAF queue for this SAF imported destination:

  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 for which you want to create an SAF queue.
  4. Select Configuration, then select Queues.
  5. Click Create.
  6. On the Create a New SAF Queue page, define the following settings for this SAF queue:

    • Name

    • Remote JNDI Name

    For more information about these fields, see Configuration Options.

  7. Click Create.
Create a SAF topic

An imported SAF topic represents a topic in a remote server or cluster. 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 create a SAF topic for this SAF imported destination:

  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 for which you want to create an SAF topic.
  4. Select Configuration, then select Topics.
  5. Click Create.
  6. On the Create a New SAF Topic page, define the following settings for this SAF topic:

    • Name

    • Remote JNDI Name

    For more information about these fields, see Configuration Options.

  7. Click Create.
Create SAF imported destination notes

To create notes about a SAF imported destination:

  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 for which you want to create notes.
  4. Select Notes.
  5. On the Notes page, enter your notes.
  6. Click Save.

Configure SAF queues and SAF topics

A SAF queue represents a JMS queue in a remote server or cluster. 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.

An imported SAF topic represents a topic in a remote server or cluster. 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.

This section includes the following tasks:

Parent topic: JMS resources and modules

Configure general settings for SAF queues

To configure general configuration settings for this SAF queue:

  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 for which you want to configure SAF queues.
  4. Select Configuration, then select Queues.
  5. In the Queues table, select the name of the SAF queue you want to configure.
  6. Select Configuration.

    From the Configuration page, you can view and configure settings for this SAF queue, such as:

    • Name

    • Remote JNDI Name

    • Local JNDI Name

    • Persistent QOS

    • Non-Persistent QOS

    • SAF Error Handling

    • Enable SAF Default Time-to-Live

    • SAF Default Time-to-Live

    • Message Unit-of-Order Routing

    For more information about these fields, see Configuration Options.

  7. Click Apply.
Configure logging for SAF queues

After you create a SAF queue, you can enable the logging of message life cycle information into a JMS message log file. A message life cycle is an external view of the basic events that a JMS message traverses through, such as message production, consumption, and removal. The content of the message log always includes message ID and correlation ID, but you can also configure information like message type and user properties.

To configure life cycle logging for messages on this SAF queue:

  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 for which you want to configure SAF queues.
  4. Select Configuration, then select Queues.
  5. In the Queues table, select the name of the SAF queue for which you want to configure logging.
  6. Select Logging.

    From the Logging page, you can configure logging settings for this SAF queue, such as:

    • Enable Message Logging

    • All Headers

    • Headers

    • All Properties

    • Properties

    • User-defined Properties

    • All Body

    For more information about these fields, see Configuration Options.

  7. Click Apply.
Create notes for SAF queues

To create notes for this SAF queue:

  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 for which you want to configure SAF queues.
  4. Select Configuration, then select Queues.
  5. In the Queues table, select the name of the SAF queue for which you want to create notes.
  6. Select Notes
  7. On the Notes page, enter your notes.
  8. Click Save.
Configure general settings for SAF topics

To configure general configuration settings for this SAF 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 SAF imported destination for which you want to configure SAF topics.
  4. Select Configuration, then select Topics.
  5. In the Topics table, select the name of the SAF topic you want to configure.
  6. Select Configuration.

    From the Configuration page, you can view and configure settings for this SAF topic, such as:

    • Name

    • Remote JNDI Name

    • Local JNDI Name

    • Persistent QOS

    • Non-Persistent QOS

    • SAF Error Handling

    • Enable SAF Default Time-to-Live

    • SAF Default Time-to-Live

    • Message Unit-of-Order Routing

    For more information about these fields, see Configuration Options.

  7. Click Apply.
Configure logging for SAF topics

After you create a SAF topic, you can enable the logging of message life cycle information into a JMS message log file. A message life cycle is an external view of the basic events that a JMS message traverses through, such as message production, consumption, and removal. The content of the message log always includes message ID and correlation ID, but you can also configure information like message type and user properties.

To configure life cycle logging for messages on this SAF 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 SAF imported destination for which you want to configure SAF topics.
  4. Select Configuration, then select Topics.
  5. In the Topics table, select the name of the SAF topic for which you want to configure logging.
  6. Select Logging.

    From the Logging page, you can configure logging settings for this SAF topic, such as:

    • Enable Message Logging

    • All Headers

    • Headers

    • All Properties

    • Properties

    • User-defined Properties

    • All Body

    For more information about these fields, see Configuration Options.

  7. Click Apply.
Create notes for SAF topics

To create notes for this SAF 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 SAF imported destination for which you want to configure SAF topics.
  4. Select Configuration, then select Topics.
  5. In the Topics table, select the name of the SAF topic for which you want to create notes.
  6. Select Notes
  7. On the Notes page, enter your notes.
  8. Click Save.

Configure foreign servers

A foreign server represents a JNDI provider that is outside WebLogic Server. It contains information that allows a local WebLogic Server instance to reach a remote JNDI provider, thereby allowing for a number of foreign connection factory and destination objects to be defined on one JNDI directory.

After defining a foreign server, you can configure foreign connection factory and destination objects (queues or topics). You can configure one or more foreign connection factories and destinations for each foreign server.

This section includes the following tasks:

Parent topic: JMS resources and modules

Configure general foreign server settings

To define general configuration settings for a foreign server 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 foreign server you want to configure.
  4. Select Configuration, then select General.

    From the General page, you can view and configure settings for this foreign server, such as:

    • Name

    • Scope

    • JNDI Initial Context Factory

    • JNDI Connection URL

    • JNDI Properties Credential

    • Confirm JNDI Properties Credential

    • JNDI Properties

    • Targeting Policy

    • Subdeployment

    For more information about these fields, see Configuration Options.

  5. Click Apply.
Create foreign destinations

A foreign destination represents either a queue or a topic. It contains the destination JNDI name that is looked up on the foreign JNDI provider and the JNDI name that the destination is mapped to on the local WebLogic Server.

When the foreign destination is looked up on the local server, a lookup is performed on the remote JNDI directory, and the destination object is returned from that directory.

To create a foreign destination:

  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 foreign server for which you want to create destinations.
  4. Select Configuration, then select Destinations.

    The Destinations table displays information about the foreign destinations that have been created for a foreign server.

  5. Click Create.
  6. On the Create a New Foreign Destination page, define the following settings for your new foreign destination:

    • Name

    • Local JNDI Name

    • Remote JNDI Name

    For more information about these fields, see Configuration Options.

  7. Click Create.
Monitor foreign destinations

To view configuration information for the foreign destinations that have been created for a foreign server:

  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 foreign server for which you want to view destinations.
  4. Select Configuration, then select Destinations.

    The Destinations table displays information about the destinations that have been created for a foreign server, including:

    • Name

    • Local JNDI Name

    • Remote JNDI Name

    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 foreign destinations

A foreign destination (topic or queue) is a destination on a remote server. When this destination is looked up on the local server, a look-up will be performed automatically on the remote JNDI directory, and the object will be returned from that directory.

To configure a foreign destination:

  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 foreign server for which you want to configure destinations.
  4. Select Configuration, then select Destinations.

    In the Destinations table, select the foreign destination you want to configure.

  5. Select Configuration.

    From the Configuration page, you can view and configure settings for this foreign destination, such as

    • Name

    • Local JNDI Name

    • Remote JNDI Name

    For more information about these fields, see Configuration Options.

  6. Click Apply.
  7. To create notes about the foreign destination, select Notes.
  8. On the Notes page, enter your notes.
  9. Click Save.
Create foreign connection factories

A foreign connection factory contains the JNDI name of the connection factory in the remote JNDI provider, the JNDI name that the connection factory is mapped to in the local WebLogic Server JNDI tree, and an optional user name and password.

The foreign connection factory creates non-replicated JNDI objects on each WebLogic Server instance that the parent foreign server is targeted to. (To create the JNDI object on every node in a cluster, target the foreign server to the cluster.)

To create a foreign connection factory:

  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 foreign server for which you want to create connection factories.
  4. Select Configuration, then select Connection Factories.

    The Connection Factories table displays information about the foreign connection factories that have been created for a foreign server.

  5. Click Create.
  6. On the Create a New Foreign Connection Factory page, define the following settings for your new foreign connection factory:

    • Name

    • Local JNDI Name

    • Remote JNDI Name

    For more information about these fields, see Configuration Options.

  7. Click Create.
Monitor foreign connection factories

To view configuration information for the foreign connection factories that have been created for a foreign server:

  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 foreign server for which you want to view connection factories.
  4. Select Configuration, then select Connection Factories.

    The Connection Factories table displays information about the foreign connection factories that have been created for a foreign server, including:

    • Name

    • Local JNDI Name

    • Remote JNDI Name

    • User Name

    • Password

    • Connection Health Checking

    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 foreign connection factories

A foreign connection factory is a connection factory that resides on another server instance and is accessible through JNDI. A remote connection factory can be used to refer to another instance of WebLogic Server running in a different cluster or server, or a foreign provider, as long as that provider supports JNDI.

To configure a foreign connection factory:

  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 foreign server for which you want to configure connection factories.
  4. Select Configuration, then select Connection Factories.

    In the Connection Factories table, select the foreign connection factory you want to configure.

  5. Select Configuration.

    From the Configuration page, you can view and configure settings for this foreign connection factory, such as

    • Name

    • Local JNDI Name

    • Remote JNDI Name

    • User Name

    • Connection Health Checking

    For more information about these fields, see Configuration Options.

  6. Click Apply.
  7. To create notes about the foreign connection factory, select Notes.
  8. On the Notes page, enter your notes.
  9. Click Save.
Create foreign server notes

To create notes about a foreign server:

  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 foreign server for which you want to create notes.
  4. Select Notes.
  5. On the Notes page, enter your notes.
  6. Click Save.

Create JMS modules

JMS resources are configured and stored as modules similar to standard Java EE modules. You can administratively configure and manage JMS modules as global system resources.

To create a JMS system module:

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

    The JMS Modules summary table displays information about the state of each JMS module that has been configured in the current WebLogic Server domain.

  3. Click Create.

    Note:

    Once you create a JMS module, you cannot rename it. Instead, you must delete it and create another JMS module that uses the new name.

  4. Define the configuration options for your JMS module on each page of the following sections.
  5. Then, click Create.

Parent topic: JMS resources and modules

General Settings

On the General Settings page, define the following settings for this JMS module:

  • In Name, enter a name for this JMS module.

  • In Scope, select the scope in which you would like this new JMS module to be created.

  • In Descriptor File, optionally enter a name for the JMS module's underlying descriptor file. The system will automatically add a "-jms.xml" extension to this name. If you do not provide a name, then a default name is assigned.

For more information about these fields, see Configuration Options.

Parent topic: Create JMS modules

Targets

On the Targets page, select the server instance or cluster target on which to deploy the JMS system module.

See Configuration Options.

Parent topic: Create JMS modules

Review

On the Review page, review the configuration for this JMS module.

See Configuration Options.

Parent topic: Create JMS modules

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.

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 information about all of the JMS system modules configured in the current domain, as well as displays the number of JMS system resource types configured for each module, such as:

    • Name

    • Scope

    • 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.

Parent topic: JMS resources and modules

Configure JMS system modules

JMS 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. You can administratively configure and manage JMS modules as global system resources.

This section includes the following tasks:

Parent topic: JMS resources and modules

Configure resources for JMS system modules

After creating a JMS system module, you can configure resources for the module, including stand-alone queues and topics, distributed queues and topics, connection factories, JMS templates, destination sort keys, destination quota, foreign servers, and JMS SAF (store-and-forward) parameters.

To configure the resources for 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 configure.
  4. Select General.

    From the General page, you can view general information about the JMS system module, such as Name and Descriptor File Name.

    The summary table displays information about the resources assigned to this JMS modules, such as:

    • Name

    • Type

    • JNDI Name

    • Subdeployment

    • Scope

    • 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. Optionally, in the table, select the name of a JMS resource for detailed statistical information about the selected resource. See Monitor JMS resources.
  6. Optionally, click Create to create a new JMS resource for this JMS module. See Create JMS resources.
Configure subdeployments in JMS system modules

You can create and manage subdeployments for your JMS resources. 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, SAF agents, or a cluster).

For example, you can group a connection factory with stand-alone queues or topics in a subdeployment targeted to a specific JMS server, which guarantees that all these resources are co-located to avoid extra network traffic. Another advantage of such a configuration would be if the targeted JMS server needs to be migrated to another WebLogic server instance, then the connection factory and all its connections will also migrate along with the JMS server's destinations. However, when stand-alone queues or topics are members of a subdeployment, a connection factory can only be targeted to the same JMS server.

To manage the subdeployments of a JMS 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 for which you want to configure subdeployments.
  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

  5. Optionally, in the table, select the name of a subdeployment to view and configure subdeployment settings.
  6. Optionally, click Create to create a new subdeployment for this JMS module. See Create JMS system module subdeployments.
Create JMS system module subdeployments

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, SAF agents, or a cluster).

For example, you can group a connection factory with stand-alone queues or topics in a subdeployment targeted to a specific JMS server, which guarantees that all these resources are co-located to avoid extra network traffic. Another advantage of such a configuration would be if the targeted JMS server needs to be migrated to another WebLogic server instance, then the connection factory and all its connections will also migrate along with the JMS server's destinations. However, when stand-alone queues or topics are members of a subdeployment, a connection factory can only be targeted to the same JMS server.

To create a JMS module subdeployment:

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

    The JMS Modules summary table displays information about the state of each JMS module that has been configured in the current WebLogic Server domain.

  3. In the table, select the name of the JMS module for which you want to create subdeployments.
  4. Select Subdeployments.

    The Subdeployments table displays information about the subdeployments created for a JMS system module in the current WebLogic Server domain.

  5. Click Create.
  6. On the Create a New Subdeployment page, define the following settings for this subdeployment:

    • In Subdeployment Name, enter a name for the subdeployment.

    • Select targets for this subdeployment:

      • In the Clusters and Servers section, select each cluster and server instance on which you want to deploy the resources associated with the subdeployment, or select specific server instances within a cluster.

        Clusters are available only when the JMS system module is part of a clustered WebLogic Server environment.

      • In the JMS Servers section, select each JMS server instance on which you want to deploy the resources associated with the subdeployment.

      • In the SAF Agents section, select each SAF agent on which you want to deploy the resources associated with the subdeployment.

    For more information about these fields, see Configuration Options.

  7. Click Create.
Target JMS system module subdeployments

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, SAF agents, or a cluster).

To target a JMS module subdeployment:

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

    The JMS Modules summary table displays information about the state of each JMS module that has been configured in the current WebLogic Server domain.

  3. In the table, select the name of the JMS module for which you want to create subdeployments.
  4. Select Subdeployments.

    The Subdeployments table displays information about the subdeployments created for a JMS system module in the current WebLogic Server domain.

  5. In the table, select the name of the subdeployment you want to target.
  6. On the Subdeployments page, select the targets for this subdeployment:

    • In the Clusters and Servers section, select each cluster and server instance on which you want to deploy the resources associated with the subdeployment, or select specific server instances within a cluster.

      Clusters are available only when the JMS system module is part of a clustered WebLogic Server environment.

    • In the JMS Servers section, select each JMS server instance on which you want to deploy the resources associated with the subdeployment.

    • In the SAF Agents section, select each SAF agent on which you want to deploy the resources associated with the subdeployment.

    For more information about these fields, see Configuration Options.

  7. Click Apply.
Target JMS system modules

After you create a JMS system module, you can deploy it on one or more servers, clusters, or even to specific servers within a cluster.

To target a 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 target.
  4. Select Targets.

    On the Targets page, select the targets for this JMS module:

    • In the Server section, select each server instance on which you want to deploy the JMS system module.

    • In the Cluster section, select each cluster on which you want to deploy the JMS system module, or select specific server instances within a cluster.

      The Cluster section is available only when the JMS system module is part of a clustered WebLogic Server environment.

    For more information about these fields, see Configuration Options.

  5. Click Save.
Create JMS system module notes

To create notes about a 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 for which you want to create notes.
  4. Select Notes.
  5. On the Notes page, enter your notes.
  6. Click Save.

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.

This section includes the following tasks:

Parent topic: WebLogic Server Messaging

Create path services

To create a path service:

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

    The Path Services summary table displays information about the state of each path service that has been configured in the current WebLogic Server domain.

  2. Click Create.

    Note:

    Once you create a path service, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  3. Define the configuration options for your path service on each page of the following sections.
  4. Then, click Create.

Parent topic: Path services

General Settings

On the General Settings page, define the following settings for this path service:

  • In Name, enter a name for this path service.

  • In Scope, select the scope in which you would like this new path service to be created.

  • In Persistent Store, select a custom persistent store if you want a dedicated store for SAF messages or click Create a New Store to configure a new custom store.

    Otherwise, leave this field set to None when using the default Persistent Store since it requires no configuration. For more information about configuring stores, see Configure a file store.

    Note:

    When a path service is targeted to a migratable target, it cannot use the default store, so a custom store must be configured and targeted to the same migratable target. And, as a best practice, the path service and its store should be the only users of that migratable target.

For more information about these fields, see Configuration Options.

Parent topic: Create path services

Targets

On the Targets page, select a cluster member or migratable target where you want to deploy the path service.

A migratable target is a logical target that serves as a grouping of services, such as a path service, and which is active on only server member in a cluster. High availability is achieved by migrating a migratable target from one server member to another when a problem occurs on the original server.

See Configuration Options.

Note:

Oracle recommends targeting the path service to a migratable target, so that a member server will not be a single point of failure. A path service can also be automatically migrated from an unhealthy server instance to a healthy server instance, with the help of the server health monitoring services.

Parent topic: Create path services

Review

On the Review page, review the configuration for this path service.

See Configuration Options.

Parent topic: Create path services

Monitor path services

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.

Parent topic: Path services

Configure 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.

This section includes the following tasks:

Parent topic: Path services

Configure path service general settings

To configure general settings for a specific path service in the current domain:

  1. From the WebLogic Domain menu, select Messaging, then select Path Services.
  2. In the Path Services table, select the path service you want to configure.
  3. Select Configuration.

    From the General page, you can view and define general settings for this path service, such as:

    • Name

    • Scope

    • Persistent Store

    For more information about these fields, see Configuration Options.

  4. Click Apply.

Parent topic: Configure path services

Select path service targets

To select the targets for a specific path service in the current domain:

  1. From the WebLogic Domain menu, select Messaging, then select Path Services.
  2. In the Path Services table, select the path service you want to configure.
  3. Select Targets.

    From the Targets page, you can target this path services to a member of a cluster or to a migratable target. Select the target on which you wish to deploy this path service.

    See Configuration Options.

  4. Click Apply.

Parent topic: Configure path services

Create path service notes

To create notes for a specific path service in the current domain:

  1. From the WebLogic Domain menu, select Messaging, then select Path Services.
  2. In the Path Services table, select the path service you want to configure.
  3. Select Notes.
  4. On the Notes page, enter your notes.
  5. Click Save.

Parent topic: Configure path services

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:

Parent topic: WebLogic Server Messaging

Create messaging bridges

A messaging bridge instance communicates with the configured source and target bridge destinations. For each mapping of a source destination to a target destination, whether it is another WebLogic JMS implementation, or a third-party JMS provider, you must configure a messaging bridge instance. Each instance defines the source and target destination for the mapping, a message filtering selector, a quality of service (QOS), transaction semantics, and reconnection parameters.

To create a messaging bridge instance:

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

    The Messaging Bridges Configuration summary table displays information about each messaging bridge that has been configured in the current WebLogic Server domain.

  2. Click Create.

    Note:

    Once you create a messaging bridge instance, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  3. Define the configuration options for your messaging bridge on each page of the following sections.
  4. Then, click Create.

Parent topic: Messaging bridges

General Settings

On the General Settings page, define the following settings for this messaging bridge:

  • In Name, enter a name for this messaging bridge.

  • In Scope, select the scope in which you would like this new messaging bridge to be created.

  • In Selector, specify the filter for messages that are sent across the messaging bridge instance.

  • In Quality of Service, select the QOS (quality of service) for this messaging bridge instance.

  • Select or deselect the Started checkbox to specify the initial operating state of a targeted messaging bridge instance.

For more information about these fields, see Configuration Options.

Parent topic: Create messaging bridges

Source Bridge Destination

On the Source Bridge Destination page, select an existing source destination or create a new source destination.

If the drop-down box is empty or does not contain the source destination you need, then click New Destination to create a source destination, and then select the source destination from the drop-down box.

See Configuration Options.

Parent topic: Create messaging bridges

Target Bridge Destination

On the Target Bridge Destination page, select an existing target destination or create a new target destination.

If the drop-down box is empty or does not contain the target destination you need, then click New Destination to create a target destination, and then select the target destination from the drop-down box.

See Configuration Options.

Parent topic: Create messaging bridges

Targets

On the Targets page, select a target for your messaging bridge instance.

See Configuration Options.

Parent topic: Create messaging bridges

Review

On the Review page, review the configuration for this messaging bridge instance.

See Configuration Options.

Parent topic: Create messaging bridges

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

    • Scope

    • Server

    • State

    • Description

    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

Parent topic: Messaging bridges

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

    • Scope

    • 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

Parent topic: Messaging bridges

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

    • Scope

    • 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.

Parent topic: Messaging bridges

Configure messaging bridge high availability settings

The high availability settings are applicable for a bridge when it is:

  • Not targeted

  • Targeted to a cluster

The high availability settings are not applicable to a bridge when it is:

  • Targeted directly to a server (within a configured cluster or standalone)

  • Targeted to a migratable target

To configure high availability 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 High Availability, and choose a Distribution Policy and Migration Policy combination of either Distributed/Off (the default) or Singleton/On-Failure.

    For the Singleton case, optionally select the Initial Boot Delay Seconds, Fallback Delay Seconds, and/or Partial Cluster Stability Delay Seconds.

    For more information about these fields, see Configuration Options.

  4. Click Apply.

Parent topic: Messaging bridges

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 settings for this messaging bridge, such as:

    • Minimum Delay

    • Incremental Delay

    • Maximum Delay

    For more information about these fields, see Configuration Options.

  4. Click Apply.

Parent topic: Messaging bridges

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.

Parent topic: Messaging bridges

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.

    See Configuration Options.

  4. Click Apply.

Parent topic: Messaging bridges

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.
  5. Click Save.

Parent topic: Messaging bridges

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:

Parent topic: WebLogic Server Messaging

Create JMS bridge destinations

A JMS bridge destination instance defines the actual source and target JMS bridge destinations within the WebLogic domain.

You need to configure a JMS bridge destination instance for each actual source and target destination to be mapped to a messaging bridge instance. Therefore, when you finish defining attributes for a source JMS bridge destination, repeat these steps to configure a target JMS bridge destination, or vice versa.

To create a JMS bridge destination:

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

    The JMS Bridge Destinations summary table displays information about each JMS bridge destination that has been configured in the current WebLogic Server domain.

  2. Click Create.

    Note:

    Once you create a JMS bridge destination, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  3. Define the configuration options for your JMS bridge destination on each page of the following sections.
  4. Then, click Create.

Parent topic: JMS bridge destinations

General Settings

On the General Settings page, define the following settings for this JMS bridge destination:

  • In Name, enter a name for this JMS bridge destination.

  • In Scope, select the scope in which you would like this new JMS bridge destination to be created.

  • In Adapter JNDI Name, specify the JNDI name of the adapter used to communicate with the bridge destinations.

  • In Connection URL, specify the connection URL for this JMS bridge destination.

  • In Connection Factory JNDI Name, specify the connection factory's JNDI name for this JMS bridge destination.

  • In Destination JNDI Name, specify the destination JNDI name for this JMS bridge destination.

For more information about these fields, see Configuration Options.

Review

On the Review page, review the configuration for this JMS bridge destination.

See Configuration Options.

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.

Parent topic: JMS bridge destinations

Configure JMS bridge destinations

This section includes the following tasks

Parent topic: JMS bridge destinations

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

    • Scope

    • 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 create notes for a 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.
  5. Click Save.

JMS smoke test

To browse JMS destinations, browse messages in a specific JMS destination, and create and send JMS messages:

  1. From the WebLogic Domain menu, select Messaging, then select JMS Smoke Test.
  2. In JMS Destinations, browse for JMS destinations configured in the domain by provider and type.
  3. In JMS Messages, enter a message selector expression to filter JMS messages.
  4. To create and send a JMS message, click Create.

    You can also view, purge, export, or import JMS messages by clicking the appropriate buttons.

See Configuration Options.

Parent topic: WebLogic Server Messaging