Managing Durable Topic Subscribers

8-8 Configuring and Managing JMS for Oracle WebLogic Server

8.2.2.7 Exporting Messages

Exporting a message results in a JMS message that is converted to either XML or serialized format. The source destination must be in a production-paused state. Temporary destinations enable an application to create a destination, as required, without the system administration overhead associated with configuring and creating a server-defined destination.

8.2.3 Managing Transactions

When a message is produced or consumed as part of a global transaction, the message is essentially locked by the transaction and will remain locked until the transaction coordinator either commits or aborts the JMS branch. If the coordinator is not able to communicate the outcome of the transaction to the JMS server due to a failure, the messages associated with the transaction may remain pending for a long time. The JMS server transaction management features available through the Administration Console allow you to: ■ Identify in-progress transactions for which a JMS server is a participant. ■ Identify messages associated with a JMS transaction branch. ■ Force the outcome of pending JMS transaction branches, either by committing them or rolling them back. ■ Manage JMS client connections. You can view all the JMS connections on a particular WebLogic Server instance and get address and port information for each process that is holding a connection. You can also terminate a connection. For more information on using the Administration Console to manage transactions for a JMS server, see JMS Server: Monitoring: Active Transactions in the Oracle WebLogic Server Administration Console Help. For more information on JMS transactions, see Using Transactions with WebLogic JMS in Programming JMS for Oracle WebLogic Server.

8.2.4 Managing Durable Topic Subscribers

You can view a list of durable subscribers for a given topic, browse messages associated with a subscriber, create and delete subscribers, and delete selected messages or purge all messages for a subscription. For more information, see Manage topic durable subscribers in the Oracle WebLogic Server Administration Console Help. Note: For more information about production-paused states, see Section 10.5.2, Production Pause and Production Resume. Note: Generally, JMS applications can use the JMSReplyTo header field to return a response to a request. However, the information in the JMSReplyTo field is not a usable destination object and will not be valid following export or import. 9 Best Practices for JMS Beginners and Advanced Users 9-1 9 Best Practices for JMS Beginners and Advanced Users The following sections provide advice and best practices for beginning JMS users as well as advanced JMS users: ■ Section 9.1, Configuration Best Practices ■ Section 9.2, Targeting Best Practices ■ Section 9.3, Integration and Multi-Domain Best Practices ■ Section 9.4, Understanding WebLogic JMS Client Options ■ Section 9.5, Understanding WebLogic URLs ■ Section 9.6, Strict Message Ordering Best Practices ■ Section 9.7, High Availability Best Practices ■ Section 9.8, JMS Performance and Tuning

9.1 Configuration Best Practices

The following sections outline a basic procedure on how to configure JMS applications: 1. Section 9.1.1, Configure JMS Servers and Persistent Stores. 2. Section 9.1.2, Configure a JMS Module 3. Section 9.1.3, Configure JMS Resources 4. Section 9.1.4, Configure SAF Agents, Stores, and Imported Destination

9.1.1 Configure JMS Servers and Persistent Stores.

Before you start configuring JMS servers and persistent stores, consider the following: ■ Destinations, connection factories, and other JMS resources are configured separately from their host JMS servers and persistent stores. The best practice steps for configuring JMS resources will be described later. ■ If you plan to leverage WebLogic distributed destinations, you will need to configure a WebLogic cluster with a JMS server and a custom persistent store on each WebLogic server in the cluster. WebLogic JMS distributed destination features require a WebLogic cluster to work. ■ Migratable targets are only supported with clusters. If you are not using a cluster, you may want to reconsider and use a cluster of size one. This enables the use of