You can enable the Adaptive Decision Manager (ADM) service by connecting the Pega 7 Platform server cluster to an external WebLogic server that runs the ADM service. To establish the connection, configure the Java Message Service (JMS) on an external ADM server and ensure that each Pega 7 Platform server has a Foreign (JMS) Server that points to this ADM server.

• Prerequisites
• Setting up the Java Message Service on the ADM server
• Setting up a JMS Foreign Server on a WebLogic installation that contains the Pega 7 Platform servers

Prerequisites

Ensure that the following prerequisites are met before performing the procedures in this tutorial:

• The Java Message Service is configured for the Pega 7 Platform server cluster.
• You have experience in operating the WebLogic server software.
  This tutorial provides high-level steps for enabling the connection between the Pega 7 Platform server cluster and the server running the ADM service. For detailed instructions about how to operate the WebLogic server software, refer to the Oracle WebLogic documentation.

Setting up the Java Message Service on the ADM server

Use the WebLogic Server Administration Console to configure the JMS on the ADM server.

1. Log in to the WebLogic Server Administration Console by providing the host name and IP address of the ADM server and the credentials from your system administrator.
2. Create a JMS server named ADM JMS Module.
3. Set the target of the ADM JMS Module to the name of the server that runs the ADM service.
4. Navigate to the Default Configuration tab of the ADM JMS Module and perform the following actions:
   1. Create a queue resource with the following parameters:
      • Name: ADM Queue
      • JNDI Name: jms/admRequestDestination
   2. Create a subdeployment for ADM Queue that targets the ADM JMS Server.
   3. Create a connection factory that has the following parameters:
      • Name: ADM Request Connection Factory
      • JNDI Name: jms/admRequestConnectionFactory

Setting up a JMS Foreign Server on a WebLogic installation that contains the Pega 7 Platform servers

You must define the ADM server as a Foreign JMS Server resource and configure the associated connection factory and queue resources on each WebLogic installation that contains a Pega 7 Platform server that you want to use as part of the ADM service.

1. Log in to the WebLogic Server Administration Console by providing the host name and IP address of the Pega 7 Platform server and the credentials from your system administrator.
2. Use the Domain Structure tree to navigate to the JMS Modules section. Because the JMS Service for the Pega 7 Platform is configured on this server, you will see the following (or similarly named) module:

   

3. Open the JMS Module for the Pega 7 Platform and perform the following actions:
   1. Add a foreign server named ADM Server.
   2. Add all Pega 7 Platform servers as targets of the ADM Server foreign server.
4. Navigate to the General tab of the ADM Server resource that you created.
5. Add a JNDI Connection URL of your ADM server WebLogic installation.
   For example, provide a URL in the format t3://<IP address>:<port>, where t3 is the RMI protocol that is used by WebLogic.
6. Navigate to the Destinations tab of the ADM Server resource.
7. Create a Foreign JMS Destination object by providing the following configuration details:
   • Name: ADM Queue
   • Local JNDI Name: jms/admRequestDestination
   • Remote JNDI Name: jms/admRequestDestination
8. Navigate to the Connection Factories tab of the ADM Server resource.
9. Create a foreign connection factory by providing the following configuration details:
   • Name: ADM Connection Factory
   • Local JNDI Name: jms/admRequestConnectionFactory
   • Remote JNDI Name: jms/admRequestConnectionFactory
10. Restart every node in the cluster for the changes to take effect. Disregard any messages in the WebLogic Server Administration Console when the changes are activated.

You have defined your ADM server as a JMS Foreign Server, connected that server to the Pega 7 Platform servers through its targets, and mapped both the ADM queue and connection factory from the local JNDI (on the Pega 7 Platform servers) to the remote JNDI (on the ADM server).