Installation Guide for Oracle Database with WebLogic

10.3 HotFix 3
- 10.5 HotFix 2
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

Step 2. Configuring JMS Message Queues

Before you manually deploy the Hub Server applications, configure JMS message queues. Also, to troubleshoot issues, you might need to manually configure JMS message queues. For example, if the automated queue creation process fails or the queues accidentally drop after installation, you need to manually configure message queues.

The Services Integration Framework (SIF) uses a message-driven bean on the JMS message queue to process incoming asynchronous SIF requests. Configure the message queue and the connection factory for the application server that you use for the MDM Hub implementation. When you configure a JMS message queue, you also create a connection factory.

To configure the JMS message queue, perform the following tasks:

Create a JMS server and module.

Create a connection factory for the module.

Add JMS message queues to the module.

Create a subdeployment queue.

Add a JMS message queue for smart search.

When you create JMS message queues for the MDM Hub in a clustered environment, ensure that you select a target server that you can migrate. When you configure the JMS module, make the target “

All servers in the cluster

”. For more information, see the WebLogic documentation.

Manually Deploying the Hub Server Applications (Conditional)

Step 1. Create a JMS Server and Module

Step 2. Configure a Connection Factory for the Module

Step 3. Add Message Queues to the Module

Step 4. Create a Subdeployment Queue

Step 5. Create a JMS Queue for Smart Search

Download Guide

Watch

Comments

Communities