Red Hat Training

A Red Hat training course is available for Red Hat Decision Manager

Chapter 4. Configuring Oracle WebLogic Server for Decision Server

Before you deploy Decision Server with Oracle WebLogic Server, you must configure system properties, security settings, JMS requirements, and other properties on Oracle WebLogic Server. These configurations promote an optimal integration with Decision Server.

Prerequisites

  • Oracle WebLogic Server is installed and running.
  • You are logged in to the WebLogic Administration Console.

4.1. Configuring the Decision Server group and users

You must assign users to a kie-server group in the WebLogic Administration Console to enable the container-managed authentication mechanisms in Oracle WebLogic Server.

Procedure

  1. In the WebLogic Administration Console, click Security Realms.
  2. Choose your desired security realm or click New to create a new security realm.
  3. Navigate to Users and Groups → Groups → New and create the kie-server group.
  4. Navigate to Users → New and create a new user.

  5. Enter a user, such as server-user, and a password for this new user and click OK.

    Important

    Make sure that the selected user name does not conflict with any known title of a role or a group. For example, if there is a role called kie-server, then do not create a user with the user name kie-server.

  6. Click the newly created user, then return to the Groups tab.
  7. Use the selection tool to move the kie-server group from the Available field to the Chosen field, and click Save.

4.2. Configuring Java Message Service (JMS)

The Java Message Service (JMS) is a Java API that Decision Server uses to exchange messages with other application servers such as Oracle WebLogic Server and IBM WebSphere Application Server. You must configure your application server to send and receive JMS messages through Decision Server to ensure proper collaboration between the two servers.

4.2.1. Create a JMS server

You must create a JMS server in order to use JMS.

Procedure

  1. In the WebLogic Administration Console, navigate to Services → Messaging → JMS Servers.
  2. Click New to create a new JMS server.
  3. Enter a name for your JMS server and click Next.
  4. Select the target server chosen for the Decision Server deployment.
  5. Click Finish.

4.2.2. Create a JMS module

You must create a JMS module to store your JMS resources, such as connection factories and queues.

Prerequisite

You have created a JMS server.

Procedure

  1. In the WebLogic Administration Console, navigate to Services → Messaging → JMS Modules.
  2. Click New to create a module.
  3. Enter a module name and click Next.
  4. Select the target server chosen for the Decision Server deployment and click Finish.
  5. Click the newly created module name and then click Subdeployments.
  6. Click New to create a subdeployment for your module.
  7. Give your subdeployment a name and click Next.
  8. Select the check box to choose the previously created JMS server.
  9. Click Finish to complete the subdeployment configuration.

4.2.3. Create JMS connection factories

To enable messaging with Decision Server, you must create certain JMS connection factories for sending and receiving messages.

Prerequisites

  • You have created a JMS server.
  • You have created a JMS module.

Procedure

  1. In the WebLogic Administration Console, navigate to Services → Messaging → JMS Modules to see a list of JMS modules.
  2. Select your previously created module and click New to create a new JMS resource.
  3. Select Connection Factory and click Next.
  4. For each of the following required connection factories, enter the name of the connection factory (for example, KIE.SERVER.REQUEST) and the JNDI name (for example, jms/cf/KIE.SERVER.REQUEST) and click Next. The connection factory automatically selects the servers assigned to the JMS Module as the default.
  5. Click Finish to add the connection factory, and repeat for each required factory.

4.2.3.1. JMS connection factories for Decision Server

The following are the required Java Message Service (JMS) connection factories that enable JMS messaging with Decision Server:

Table 4.1. Required JMS connection factories for Decision Server

NameDefault valueUsed for

KIE.SERVER.REQUEST

jms/cf/KIE.SERVER.REQUEST

Sending all requests to Decision Server

KIE.SERVER.RESPONSE

jms/cf/KIE.SERVER.RESPONSE

Receiving all responses produced by Decision Server

4.2.4. Create JMS queues

JMS queues are the destination end points for point-to-point messaging. You must create certain JMS queues to enable JMS messaging with Decision Server.

Prerequisites

  • You have created a JMS server.
  • You have created a JMS module.

Procedure

  1. In the WebLogic Administration Console, navigate to Services → Messaging → JMS Modules to see the list of JMS modules.
  2. Select your previously created module, then click New to create a new JMS resource.
  3. Select Queue and click Next.
  4. For each of the following required queues, enter the name of the queue (for example, KIE.SERVER.REQUEST) and the JNDI name (for example, jms/KIE.SERVER.REQUEST) and then click Next.
  5. Choose the JMS module subdeployment that connects to the JMS server.
  6. Click Finish to add the queue, and repeat for each required queue.

4.2.4.1. JMS queues for Decision Server

The following are the required Java Message Service (JMS) queues that enable JMS messaging with Decision Server:

Table 4.2. Required JMS queues for Decision Server

NameDefault valueUsed for

KIE.SERVER.REQUEST

jms/KIE.SERVER.REQUEST

Sending all requests to Decision Server

KIE.SERVER.RESPONSE

jms/KIE.SERVER.RESPONSE

Receiving all responses produced by Decision Server

4.3. Setting system properties in Oracle WebLogic Server

Set the system properties listed in this section on your Oracle WebLogic Server before you deploy Decision Server.

Procedure

  1. Set the following system property to increase the Java Virtual Machine (JVM) memory size: 

    USER_MEM_ARGS=-Xms512m -Xmx1024m

    If you do not increase the JVM memory size, Oracle WebLogic Server freezes or causes deployment errors when deploying Decision Server.

  2. Specify the following system properties for Decision Server on the Oracle WebLogic Server instance:

    Table 4.3. System properties for Decision Server

    NameValueDescription

    kie.server.jms.queues.response

    jms/queue/KIE.SERVER.RESPONSE

    The JNDI name of JMS queue for responses used by the Decision Server.

    org.kie.server.domain

    OracleDefaultLoginConfiguration

    JAAS LoginContext domain used to authenticate users when using JMS.

    org.jbpm.server.ext.disabled

    true

    Disables Decision Central features, which are not supported in RHDM. If not set, Decision Server will work, but will show error messages during start up.

    org.jbpm.ui.server.ext.disabled

    true

    Disables Decision Central features, which are not supported in RHDM. If not set, Decision Server will work, but will show error messages during start up.

    org.jbpm.case.server.ext.disabled

    true

    Disables Decision Central features, which are not supported in RHDM. If not set, Decision Server will work, but will show error messages during start up.

  3. Set the same property values in the JAVA_OPTIONS environment variable: 
JAVA_OPTIONS="-Dkie.server.jms.queues.response=jms/queue/KIE.SERVER.RESPONSE
 -Dorg.kie.server.domain=OracleDefaultLoginConfiguration
 -Dorg.jbpm.server.ext.disabled=true
 -Dorg.jbpm.ui.server.ext.disabled=true
 -Dorg.jbpm.case.server.ext.disabled=true"

4.4. Stopping and restarting Oracle WebLogic Server

After you have configured all required system properties in Oracle WebLogic Server, stop and restart the Oracle server to ensure that the configurations are applied.

Procedure

  1. In the WebLogic Administration Console, navigate to Change Center → Lock & Edit.
  2. Under Domain Structure, click Environment → Servers → Control.
  3. Select the server that you want to stop and click Shutdown.
  4. Select When Work Completes to gracefully shut down the server or select Force Shutdown Now to stop the server immediately without completing ongoing tasks.
  5. On the Server Life Cycle Assistant pane, click Yes to complete the shutdown.

  6. After the shutdown is complete, navigate to the domain directory in the command terminal, WLS_HOME/user_projects/<DOMAIN_NAME>. For example: 

    WLS\user_projects\mydomain

  7. Enter one of the following commands to restart Oracle WebLogic Server to apply the new configurations:

    On UNIX-based operating systems: 

    startWebLogic.sh

    On Windows operating systems: 

    startWebLogic.cmd
  8. Open the Administration Console in a web browser (for example, http://localhost:7001/console/) and log in with your credentials.