Step 9: Configuring JMS settings

In this step, on each of the managed servers, you configure JMS (Java Messaging Service) settings. JMS in WebLogic is used by the Data Enrichment plugins and must be configured in the Endeca Server cluster if you will use Data Enrichment plugins (known as Enrichments in Studio).

For general information on JMS, see https://docs.oracle.com/middleware/1213/wls/INTRO/jms.htm#INTRO224.

In the Endeca Server cluster, for each Managed node in the WebLogic domain, JMS queues must be configured on each of the Managed Servers, so that the Data Enrichment plugins can use them for their internal communication within the Data Enrichment Framework Java application running in WebLogic domain (the Data Enrichment Framework application is installed once you install Endeca Server).

This procedure describes the steps for one of the Managed Servers, Managed-1. Repeat the steps for each Managed Server. The instructions for each step indicate the names you should use on each Managed Server.

To configure JMS settings in the WebLogic domain for Endeca Server:

  1. Go to WebLogic console, and click Lock and Edit, to switch to edit mode.
  2. For each Managed Server, create a new JMS Server:
    1. Select Services > Messaging > JMS Servers > New
    2. Specify Name as oracle.endeca.enrichments.JMSServer-1, for Managed-1. For Managed-2 and Managed-3, the names should be *.JMSServer-2 and *.JMSServer-3, respectively.
    3. Specify Target as Managed-1, Managed-2, or Managed-3, respectively.
  3. For each Managed Server machine, create a new JMS module:
    1. Select Services > Messaging > JMS Modules > New
    2. Specify Name as oracle.endeca.enrichments.Module-1, for Managed-1. For Managed-2 and Managed-3, the names should be *.Module-2 and *.Module-3, respectively.
    3. Specify Target as Managed-1, Managed-2, or Managed-3, respectively.
  4. Within each module, create a new subdeployment:
    1. Select Subdeployments tab, and then select New.
    2. Specify Name as oracle.endeca.enrichments.Subdeployment-1, for Managed-1. For Managed-2 and Managed-3, specify their corresponding names respectively, such as oracle.endeca.enrichments.Subdeployment-2 for Managed-2, and oracle.endeca.enrichments.Subdeployment-3, for Managed-3.
    3. Specify Target as oracle.endeca.enrichments.JMSServer-1, on Managed-1. On Managed-2 and Managed-3, specify targets respectively.
  5. Create JMS resources (which will include a connection factory and three queues). To create a connection factory:
    1. Select Configuration tab, and then select New.
    2. Select Connection Factory.
    3. Specify Name as ConnectionFactory, JNDI Name as jms/ConnectionFactory
    4. Select Next > Advanced Targeting and specify Subdeployments as oracle.endeca.enrichments.SubDeployment-1, for Managed-1. For Managed-2 and Managed-2, specify subdeployments respectively.
    5. Specify Target as oracle.endeca.enrichments.JMSServer-1, for Managed-1. For Managed-2 and Managed-3, specify targets respectively.
  6. Create three queues, with names TaskQueue, ProcessedRecordQueue, and UnprocessedRecordQueue, on each of the Managed Servers.
    1. Select Configuration tab, and then select New.
    2. Select Queue and specify, for Managed-1, Name as TaskQueue, JNDI Name as jms/TaskQueue, Subdeployments as oracle.endeca.enrichments.SubDeployment-1, Target as oracle.endeca.enrichments.JMSServer-1. For Managed-2 and Managed-3, specify the same values for all fields, except choose their respective subdeployments and targets.
    3. Select Configuration tab, and then select New.
    4. Select Queue and specify, for Managed-1, Name as ProcessedRecordQueue, JNDI Name as jms/ProcessedQueue, and the same subdeployments and targets that you specified for the TaskQueue. For Managed-2 and Managed-3, select their respective subdeployments and targets.
    5. Select Configuration tab, and then select New.
    6. Select Queue and specify, for Managed-1, Name as UnprocessedRecordQueue, JNDI Name as jms/UnprocessedRecordQueue, and the same subdeployments and targets that you specified for the TaskQueue. For Managed-2 and Managed-3, select their respective subdeployments and targets.
  7. Click Activate Changes to save your changes, and then click Release Configuration to unlock the console.

After you have successfully installed and deployed an Endeca Server cluster, you can verify its status. You can also optionally add additional machines to its WebLogic domain (so that you can start additional Endeca Server instances), and, if you have previously created an Endeca Server data domain in the Endeca Server installed on a single machine, you can migrate this data domain to the Endeca Server cluster.

For information on all these tasks, see Verifying a cluster installation and deployment.