Red Hat Training

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

Chapter 5. Installing and running the standalone Decision Server Controller

You can configure Decision Server to run in managed or unmanaged mode. If Decision Server is unmanaged, you must manually create and maintain containers. If Decision Server is managed, the standalone Decision Server Controller manages the Decision Server configuration and you interact with the Controller to create and maintain containers.

The standalone Decision Server Controller is integrated with Decision Central. If you install Decision Central, use the Exection Server page to create and maintain containers. However, if you do not install Decision Central, you can install the standalone Decision Server Controller and use the REST API or the Decision Server Java Client API to interact with it.

5.1. Setting environment variables for the Controller

Set the environment variables listed in this section.

Prerequisites

  • Decision Server installed on an Oracle Weblogic Server instance

  • The Controller installed on an Oracle Weblogic Server instance

    Note

    Red Hat recommends that you install Decision Server and the standalone Decision Server Controller on different servers in production environments. However, if you install Decision Server and the standalone Decision Server Controller on the same server, for example in a development environment, make these changes on the same Oracle Weblogic Server instance.

  • On Decision Server nodes, a user with the kie-server role
  • On the Controller server nodes, a user with the kie-server role

Procedure

  1. Specify the following JVM property values on the Oracle Weblogic Server instance where the Controller is installed:

    • org.kie.server.user: A user with the kie-server role.
    • org.kie.server.pwd: The password for the user specified in the org.kie.server.user property.

  2. Specify the following JVM property values on the Oracle Weblogic Server instance where Decision Server is installed:

    • org.kie.server.controller.user: A user with the kie-server role
    • org.kie.server.controller.pwd: The password for the user specified for the org.kie.server.controller.user property
    • org.kie.server.id: The ID or name of the Decision Server installation, for example, rhdm700-decision-server-1
    • org.kie.server.location: http://<HOST>:<PORT>/kie-server/services/rest/server

    • org.kie.server.controller: The URL of the standalone Decision Server Controller, for example http://<HOST>:<PORT>/controller/rest/controller

      In the preceding examples:

    • <HOST> is the ID or name of the Decision Server host, for example, localhost or 192.7.8.9.
    • <PORT> is the port of the Decision Server host, for example, 7001.

5.2. Installing the Controller

This section describes how to install the Controller on Oracle Weblogic Server.

You can install the Controller and use the REST API or the Decision Server Java Client API to interact with it.

Prerequisites

  • An Oracle Weblogic Server instance configured as described in this document
  • Sufficient user permissions to complete the installation.

Procedure

  1. Download the rhdm-7.0-controller-ee7.zip file by clicking Download next to Red Hat Decision Manager 7.0.0 Add Ons on the Product Downloads page of the Red Hat Customer Portal.
  2. Unzip the rhdm-7.0.0.GA-add-ons.zip file. The rhdm-7.0-controller-ee7.zip file is in the unzipped directory.
  3. Create a user and password for the Controller in the kie-server group, for example controller/pwd1234. For information about creating users, see Section 3.3, “Configuring security settings”.
  4. Navigate to Deployments to view all existing applications.
  5. Click Install.
  6. Navigate to the extracted archive location for the controller.war file and select it. Click Next to continue.
  7. Select Install this deployment as an application as the targeting style and click Next.
  8. Keep the application name as controller and set the security model to DD Only. Leave the remaining options as default and click Next to continue.
  9. In the Additional Configuration section, choose No, I will review the configuration later and click Finish.

  10. To verify that the Controller is working on Oracle Weblogic Server, enter the following command: 

    curl -X GET "http://<HOST>:<PORT>/controller/rest/controller/management/servers" -H  "accept: application/xml" -u '<CONTROLLER>:<CONTROLLER_PWD>'

    In this command, replace <CONTROLLER> and <CONTROLLER_PWD> with the user credentials that you created in this section.

    The output of this command provides information about the Decision Server instance.

Note

Alternatively, you can use the Decision Server Java API Client to access the Controller.