Red Hat Training

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

Chapter 3. Configuring Oracle WebLogic Server

3.1. Setting environment variables

You must set the environment variables listed in this section on your Oracle WebLogic Server before you deploy Decision Server.

JVM memory size

Set the following environment variable to increase the JVM memory size: 

USER_MEM_ARGS=-Xms512m -Xmx1024m

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

JVM custom properties

You must specify the following Decision Server property values on the Oracle WebLogic Server instance:

  • com.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager: Uses BeanManager to look up extensions. This avoids conflicts across multiple instances. Set to true.
  • kie.server.jms.queues.response: JNDI name of the response queue for the Decision Server. Set to jms/KIE.SERVER.RESPONSE.
  • org.kie.server.domain: JAAS LoginContext domain used to authenticate users when using JMS. Set to OracleDefaultLoginConfiguration.

  • Set the values of the following properties to true to disable the jBPM functionality of Decision Server:

    • org.jbpm.server.ext.disabled
    • org.jbpm.ui.server.ext.disabled
    • org.jbpm.case.server.ext.disabled

Set these property values in the JAVA_OPTIONS environment variable: 

JAVA_OPTIONS="-Dkie.server.jms.queues.response=jms/KIE.SERVER.RESPONSE
 -Dorg.org.kie.server.domain=OracleDefaultLoginConfiguration
 -Dcom.sun.jersey.server.impl.cdi.lookupExtensionInBeanManager=true
 -Dorg.jbpm.server.ext.disabled=true
 -Dorg.jbpm.ui.server.ext.disabled=true
 -Dorg.jbpm.case.server.ext.disabled=true"

3.2. Starting Oracle WebLogic Server

The instructions in this section describe how to start Oracle WebLogic Server in a standalone Oracle WebLogic Server domain.

Note

If you are already running an instance of Oracle WebLogic Server that uses the same listener port as the one to be used by the server you are starting, you must stop the first server before starting the second server.

Procedure

  1. At the command prompt, navigate to the domain directory, `WLS_HOME/user_projects/<DOMAIN_NAME>''. For example: 

    WLS\user_projects\mydomain

  2. Enter one of the following commands to start Oracle WebLogic Server:

    • On UNIX-based system: 

      startWebLogic.sh

    • On Microsoft Windows: 

      startWebLogic.cmd

      The startup script displays a series of messages, finally displaying a message similar to the following: 

      <Dec 8, 2017 3:50:42 PM PDT> <Notice> <WebLogicServer> <000360> <Server started in RUNNING mode>

  3. Open the following URL in a web browser: 

    http://<HOSTNAME>:<PORT>/console

    In this command:

    • HOSTNAME is the system name or IP address of the host server

    • PORT is the address of the port on which the host server is listening for requests (7001 by default)

      For example, to start the Administration Console for a local instance of Oracle WebLogic Server running on your system, enter the following URL in a web browser address field: 

      http://localhost:7001/console/

      If you started the Administration Server using secure socket layer (SSL), you must add s after http, as follows: https://hostname:port/console

  4. When the login page appears, enter your administrative credentials.

3.3. Configuring security settings

Complete the steps in this section to enable the container-managed authentication mechanisms provided by the Oracle WebLogic Server:

Procedure

  1. In the WebLogic administrative 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 to display the groups list for your security realm.
  4. Click New to create the kie-server group.
  5. Click the Users tab and click New to create a new user.

  6. Enter a name and password for this new user, for example server-user/ password1234, 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, you should not create a user with the user name kie-server.

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

3.4. Configuring Java Message Service

You must configure Oracle WebLogic Server to send and receive Java Message Service (JMS) messages through Decision Server.

3.4.1. Create a JMS server

You must create a JMS server before you can use JMS.

Procedure

  1. 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 Central deployment.
  5. Click Finish to complete the JMS Server creation.

Create a JMS module

A JMS module stores your JMS resources, such as connection factories and queues. Use the following steps to create a new JMS module.

Procedure

  1. Navigate to Services → Messaging → JMS Modules.
  2. Click New to create a new module.
  3. Provide your module with a name and click Next to advance to the next configuration screen.
  4. Select the target server chosen for the Decision Server deployment.
  5. Click Finish to complete the JMS module creation.
  6. Click the newly created module’s name, then click Subdeployments.
  7. Click New to create a subdeployment for your module.
  8. Give your subdeployment a name and click Next.
  9. Click the box to select the previously created JMS server.
  10. Click Finish to complete the subdeployment configuration.

Create JMS connection factories

To send and receive messages from Decision Server, you must create a JMS connection factory for receiving messages and another JMS connection factory for sending messages. The following connection factories are required:

  • KIE.SERVER.REQUEST: for all requests to Decision Server.

    Default value: jms/cf/KIE.SERVER.REQUEST.

  • KIE.SERVER.RESPONSE: for receiving all responses produced by Decision Server.

    Default value: jms/cf/KIE.SERVER.RESPONSE.

Perform the following steps for each connection factory.

Procedure

  1. Navigate to Services → Messaging → JMS Modules to see a list of JMS modules.
  2. Select your previously created module, then click New to create a new JMS resource.
  3. Select Connection Factory and click Next.
  4. 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 complete the connection factory creation.

Create JMS queues

JMS queues are the destination end points for point-to-point messaging. You must create the following JMS queues:

  • KIE.SERVER.REQUEST: for all requests to the Decision Server.

    Default value: jms/KIE.SERVER.REQUEST.

  • KIE.SERVER.RESPONSE: for the Decision Server responses.

    Default value: jms/KIE.SERVER.RESPONSE.

Repeat the following steps to create each queue:

  1. 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. 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 complete the queue creation.