A Configuring User Messaging Service with AQ JMS

This appendix describes how to configure UMS to use AQ JMS instead of WLS JMS. This can be achieved through the WebLogic Remote Console.

User Messaging Service (UMS) can be configured to use Oracle Streams Advanced Queuing (AQ) JMS. AQ JMS uses a database connection and stores JMS messages in a database that is accessible to an entire WebLogic Server cluster, thus enabling the use of database features and tooling for data manipulation and backup. A typical use case would be enhanced high availability (HA), where the standard whole server migration support is not sufficient. If one UMS node in a cluster fails, then the other nodes will pick messages from the database for the failing UMS node, causing no loss of messages.

The following tasks describe how to configure UMS with AQ JMS through the WebLogic Remote Console.

  1. Log into Oracle WebLogic Remote Console.

    Shutdown all Managed servers in the domain.

  2. Click Edit Tree option in the left panel. Expand Environments and select Domains for configuration changes.

  3. Expand the Services node and navigate to JMS system resource. A page listing the JMS system modules created for this domain is displayed.

  4. Select UMSJMSSystemResource and navigate to the Subdeployments tab. Navigate to the UMSJMSServer running on the cluster you want to reconfigure and un-target all the UMSJMSServer_auto_x servers. Click Save.

  5. Navigate to the Targets tab for UMSJMSSystemResource. Un-target the UMSJMSSystemResource cluster(s) by deselecting the cluster check box. Click Save.

  6. Navigate to UMSAQJMSSystemResource from the JMS Modules table.

  7. Navigate to the Targets tab for UMSAQJMSSystemResource and target the UMSAQJMSSystemResource to the same cluster from which you un-targeted the UMSJMSSYstemResource.

    Save the settings.

  8. Click shopping cart on top right corner and select commit changes. Start all Managed servers in the domain.