Installing and configuring Red Hat Decision Manager on Red Hat JBoss EAP 7.1

Procedure

1. In a terminal window, navigate to the directory where you downloaded the installer JAR file and enter the following command:

   java -jar rhdm-installer-7.1.0.jar

   Copy to Clipboard Toggle word wrap
   Note

   When running the installer on Windows, you may be prompted to provide administrator credentials during the installation. To prevent this requirement, add the izpack.mode=privileged option to the installation command:

   java -Dizpack.mode=privileged -jar
   rhdm-installer-7.1.0.jar

   Copy to Clipboard Toggle word wrap

   Furthermore, when running the installer on a 32-bit Java virtual machine, you might encounter memory limitations. To prevent this issue, run this command:

   java -XX:MaxHeapSize=4g -jar
   rhdm-installer-7.1.0.jar

   Copy to Clipboard Toggle word wrap

   The graphical installer displays a splash screen and a license agreement page.

2. Click I accept the terms of this license agreement and click Next.
3. Specify the Red Hat JBoss EAP 7.1 server home where you want to install Red Hat Decision Manager and click Next.

4. Select the components that you want to install and click Next.

   Note

   You can install Decision Central and Decision Server on the same server. However, you should install Decision Central and Decision Server on different servers in production environments. To do this, run the installer twice.

5. Create a user and click Next. By default, the new user is given the admin, kie-server, and rest-all roles. To select another role, deselect admin. For more information, see Chapter 2, Roles and users.

   Note

   Make sure that the specified user name is not the same as an existing user, role, or group. For example, do not create a user with the user name admin.

   The password must have at least eight characters and must contain at least one number and one non-alphanumeric character, but not & (ampersand).

   Make a note of the user name and password. You will need them to access Decision Central and Decision Server.

6. On the Installation Overview page, click Next to start the installation. The Installation Overview page lists the components that you will install.
7. When the installation has completed, click Next.
8. When Processing finished appears at the top of the screen, click Next to complete the installation.

9. If desired, click Generate Installation Script and Properties File to save the installation data in an XML file, then click Done. You can use this file to automatically install Red Hat Decision Manager on the same type of server. Note that you must change the installpath parameter in the XML file to specify the path of the new server that you want to install Red Hat Decision Manager on. Enter the following command to perform an installation with the XML file:

   java -jar rhdm-installer-7.1.0.jar <path-to-file>

   Copy to Clipboard Toggle word wrap

Procedure

1. In a terminal window, navigate to the directory where you downloaded the installer file and enter the following command:

   java -jar rhdm-installer-7.1.0.jar -console

   Copy to Clipboard Toggle word wrap

   The command-line interactive process will start and display the End-User License Agreement.

   press 1 to continue, 2 to quit, 3 to redisplay.

   Copy to Clipboard Toggle word wrap

2. Read the license agreement, enter 1, and press Enter to continue:

   Specify the home directory of one of the following servers:  Red Hat JBoss EAP 7.1 or Red Hat JBoss Web Server 5.0

   Copy to Clipboard Toggle word wrap

3. Enter the parent directory of an existing Red Hat JBoss EAP 7.1 installation.

   The installer will verify the location of the installation at the location provided. Enter 1 to confirm and continue.

   Note

   You can install Decision Central and Decision Server on the same server. However, you should install Decision Central and Decision Server on different servers in production environments.

4. Follow the instructions in the installer to complete the installation.

   Note

   When you create the user name and password, make sure that the specified user name does not conflict with any known title of a role or a group. For example, if there is a role called admin, you should not create a user with the user name admin.

   The password must have at least eight characters and must contain at least one number and one non-alphanumeric character (not including the character &).

   Make a note of the user name and password. You will need them to access Decision Central and Decision Server.

5. When the installation has completed, you will see this message:

   Would you like to generate an automatic installation script and properties file?

   Copy to Clipboard Toggle word wrap
6. Enter y to create an XML file that contains the installation data, or n to complete the installation. If you enter y, you are prompted to specify a path for the XML file.
7. Enter a path or press the Enter key to accept the suggested path.
8. If you installed only Decision Central, repeat these steps to install Decision Server on a separate server.

Procedure

1. Extract the rhdm-7.1.0-decision-central-eap7-deployable.zip file to a temporary directory. In the following examples this directory is called TEMP_DIR.

2. Copy the contents of the TEMP_DIR/rhdm-7.1.0-decision-central-eap7-deployable/jboss-eap-7.1 directory to EAP_HOME. When prompted, merge or replace files.

   Warning

   Ensure the names of the Red Hat Decision Manager deployments you are copying do not conflict with your existing deployments in the Red Hat JBoss EAP instance.

Procedure

1. Extract the rhdm-7.1.0-kie-server-ee7.zip archive to a temporary directory. In the following examples this directory is called TEMP_DIR.

2. Copy the TEMP_DIR/rhdm-7.1.0-kie-server-ee7/rhdm-7.1.0-kie-server-ee7/kie-server.war directory to EAP_HOME/standalone/deployments/.

   Warning

   Ensure the names of the Red Hat Decision Manager deployments you are copying do not conflict with your existing deployments in the Red Hat JBoss EAP instance.

3. Copy the contents of the TEMP_DIR/rhdm-7.1.0-kie-server-ee7/rhdm-7.1.0-kie-server-ee7/SecurityPolicy/ to EAP_HOME/bin. When asked to overwrite files, click Replace.
4. In the EAP_HOME/standalone/deployments/ directory, create an empty file named kie-server.war.dodeploy. This file ensures that Decision Server is automatically deployed when the server starts.

Procedure

1. In a terminal application, navigate to the EAP_HOME/bin directory.

2. Create a user with the admin role that you will use to log in to Decision Central. In the following command, replace <username> and <password> with the user name and password of your choice.

   $ ./add-user.sh -a --user <USERNAME>  --password <PASSWORD> --role admin

   Copy to Clipboard Toggle word wrap
   Note

   Make sure that the specified user name is not the same as an existing user, role, or group. For example, do not create a user with the user name admin.

   The password must have at least eight characters and must contain at least one number and one non-alphanumeric character, but not & (ampersand).

3. Create a user with the kie-server role that you will use to log in to Decision Server.

   $ ./add-user.sh -a --user <USERNAME>  --password <PASSWORD> --role kie-server

   Copy to Clipboard Toggle word wrap

4. Make a note of your user names and passwords.

   Note

   If you installed Decision Central and Decision Server in the same server instance, you can create a single user that has both of these roles:

   $ ./add-user.sh -a --user <USERNAME>  --password <PASSWORD> --role admin,rest-all,kie-server

   Copy to Clipboard Toggle word wrap

   You should install Decision Central and Decision Server on different servers in production environments.

Procedure

1. In the Decision Central EAP_HOME/standalone/configuration/standalone-full.xml file, uncomment the following properties in the <system-properties> section and replace <USERNAME> and <USER_PWD> with the credentials of a user with the kie-server role:

      <property name="org.kie.server.user" value="<USERNAME>"/>
      <property name="org.kie.server.pwd" value="<USER_PWD>"/>

   Copy to Clipboard Toggle word wrap

2. In the Decision Server EAP_HOME/standalone/configuration/standalone-full.xml file, uncomment the following properties in the <system-properties> section.

     <property name="org.kie.server.controller.user" value="<CONTROLLER_USER>"/>
     <property name="org.kie.server.controller.pwd" value="<CONTROLLER_PWD>"/>
     <property name="org.kie.server.id" value="<KIE_SERVER_ID>"/>
     <property name="org.kie.server.location" value="http://<HOST>:<PORT>/kie-server/services/rest/server"/>
     <property name="org.kie.server.controller" value="<CONTROLLER_URL>"/>

   Copy to Clipboard Toggle word wrap

3. Replace the following values:

   • Replace <CONTROLLER_USER> and <CONTROLLER_PWD> with the credentials of a user with the rest-all role.
   • Replace <KIE_SERVER_ID> with the ID or name of the Decision Server installation, for example, rhdm-7.1.0-decision_server-1.
   • Replace <HOST> with the ID or name of the Decision Server host, for example, localhost or 192.7.8.9.

   • Replace <PORT> with the port of the Decision Server host, for example, 8080.

     Note

     The org.kie.server.location property specifies the location of Decision Server.

   • Replace <CONTROLLER_URL> with the URL of Decision Central. Decision Server connects to this URL during startup.

     • If you installed Decision Central using the installer or Red Hat JBoss EAP zip installations, <CONTROLLER_URL> has this format:

       http://<HOST>:<PORT>/decision-central/rest/controller

     • If you are running Decision Central using the standalone.jar file, <CONTROLLER_URL> has this format:

       http://<HOST>:<PORT>/rest/controller

Procedure

1. Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:

   • Product: Decision Manager
   • Version: 7.1
2. Download Red Hat Decision Manager 7.1.0 Add Ons (the rhdm-7.1.0-add-ons.zip file).
3. Unzip the rhdm-7.1.0-add-ons.zip file. The rhdm-7.1-controller-ee7.zip file is in the unzipped directory.
4. Extract the rhdm-7.1-controller-ee7 archive to a temporary directory. In the following examples this directory is called TEMP_DIR.

5. Copy the TEMP_DIR/rhdm-7.1-controller-ee7/controller.war directory to EAP_HOME/standalone/deployments/.

   Warning

   Ensure that the names of the headless Decision Manager controller deployments you are copying do not conflict with your existing deployments in the Red Hat JBoss EAP instance.

6. Copy the contents of the TEMP_DIR/rhdm-7.1-controller-ee7/SecurityPolicy/ directory to EAP_HOME/bin. When asked to overwrite files, select Yes.
7. In the EAP_HOME/standalone/deployments/ directory, create an empty file named controller.war.dodeploy. This file ensures that the headless Decision Manager controller is automatically deployed when the server starts.

Procedure

1. In a terminal application, navigate to EAP_HOME/bin.

2. Enter the following command:

   • On Linux or UNIX-based systems:

     $ ./standalone.sh

     Copy to Clipboard Toggle word wrap

   • On Windows:

     standalone.bat

     Copy to Clipboard Toggle word wrap

3. To verify that the headless Decision Manager controller is working on Red Hat JBoss EAP, enter the following command where <CONTROLLER> and <CONTROLLER_PWD> is the user name and password combination that you created in Section 9.1.1, “Creating a headless Decision Manager controller user”. The output of this command provides information about the Decision Server instance.

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

   Copy to Clipboard Toggle word wrap

Procedure

1. Declare the Red Hat Business Automation BOM in the pom.xml file:

   <dependencyManagement>
    <dependencies>
     <dependency>
      <groupId>com.redhat.ba</groupId>
      <artifactId>ba-platform-bom</artifactId>
      <version>7.1.0.GA-redhat-00002</version>
      <type>pom</type>
      <scope>import</scope>
     </dependency>
    </dependencies>
   </dependencyManagement>
   <dependencies>
   <!-- Your dependencies -->
   </dependencies>

   Copy to Clipboard Toggle word wrap
2. Declare dependencies required for your project in the <dependencies> tag. After you import the product BOM into your project, the versions of the user-facing product dependencies are defined so you do not need to specify the <version> sub-element of these <dependency> elements. However, you must use the <dependency> element to declare dependencies which you want to use in your project.

3. For standalone projects that are not authored in Decision Central, specify all dependencies required for your projects. In projects that you author in Decision Central, the basic decision engine dependencies are provided automatically by Decision Central.

   • For a basic Red Hat Decision Manager project, declare the following dependencies, depending on the features that you want to use:

   • For a basic Red Hat Decision Manager project, declare the following dependencies:

     Embedded decision engine dependencies

     <dependency>
       <groupId>org.drools</groupId>
       <artifactId>drools-compiler</artifactId>
     </dependency>
     
     <!-- Dependency for persistence support. -->
     <dependency>
       <groupId>org.drools</groupId>
       <artifactId>drools-persistence-jpa</artifactId>
     </dependency>
     
     <!-- Dependencies for decision tables, templates, and scorecards.
     For other assets, declare org.drools:drools-workbench-models-* dependencies. -->
     <dependency>
       <groupId>org.drools</groupId>
       <artifactId>drools-decisiontables</artifactId>
     </dependency>
     <dependency>
       <groupId>org.drools</groupId>
       <artifactId>drools-templates</artifactId>
     </dependency>
     <dependency>
       <groupId>org.drools</groupId>
       <artifactId>drools-scorecards</artifactId>
     </dependency>
     
     <!-- Dependency for loading KJARs from a Maven repository using KieScanner. -->
     <dependency>
       <groupId>org.kie</groupId>
       <artifactId>kie-ci</artifactId>
     </dependency>

     Copy to Clipboard Toggle word wrap

   • To use the Decision Server, declare the following dependencies:

     Client application Decision Server dependencies

     <dependency>
       <groupId>org.kie.server</groupId>
       <artifactId>kie-server-client</artifactId>
     </dependency>

     Copy to Clipboard Toggle word wrap

   • To create a remote client for Red Hat Decision Manager, declare the following dependency:

     Client dependency

     <dependency>
       <groupId>org.uberfire</groupId>
     </dependency>

     Copy to Clipboard Toggle word wrap

   • When creating a JAR file that includes assets, such as rules and process definitions, specify the packaging type for your Maven project as kjar and use org.kie:kie-maven-plugin to process the kjar packaging type located under the <project> element. In the following example, ${kie.version} is the Maven library version listed in What is the mapping between Red Hat Decision Manager and the Maven library version?:

     <packaging>kjar</packaging>
     <build>
      <plugins>
       <plugin>
        <groupId>org.kie</groupId>
        <artifactId>kie-maven-plugin</artifactId>
        <version>${kie.version}</version>
        <extensions>true</extensions>
       </plugin>
      </plugins>
     </build>

     Copy to Clipboard Toggle word wrap

Procedure

1. Create a Maven settings.xml file with connection and access details for your external repository. For details about the settings.xml file, see the Maven Settings Reference.
2. Save the file in a known location, for example, /opt/custom-config/settings.xml.
3. In your Red Hat Decision Manager installation directory, navigate to the standalone-full.xml file. For example, if you use a Red Hat JBoss EAP installation for Red Hat Decision Manager, go to $EAP_HOME/standalone/configuration/standalone-full.xml.

4. Open standalone-full.xml and under the <system-properties> tag, set the kie.maven.settings.custom property to the full path name of the settings.xml file.

   For example:

   <property name="kie.maven.settings.custom" value="/opt/custom-config/settings.xml"/>

   Copy to Clipboard Toggle word wrap
5. Start or restart Decision Central and Decision Server.

Procedure

1. Start Red Hat JBoss EAP and open Decision Central in a web browser.
2. Copy a PNG format image to the EAP_HOME/standalone/deployments/decision-central.war/img/ directory in your Red Hat Decision Manager installation.
3. In the EAP_HOME/standalone/deployments/decision-central.war/img/ directory, either move or rename the existing login-screen-logo.png file.
4. Rename your PNG file login-screen-logo.png.
5. To change the project logo that appears above the User name and Password fields, replace the default image RHDM_Logo.svg with a new SVG file.
6. Force a full reload of the login page, bypassing the cache, to view the changes. For example, in most Linux and Windows web browsers, press Ctrl+F5.

Procedure

1. Start Red Hat JBoss EAP, open Decision Central in a web browser, and log in with your user credentials.
2. Copy your new application header image in the SVG format to the EAP_HOME/standalone/deployments/decision-central.war/banner/ directory in your Red Hat Decision Manager installation.
3. Open the EAP_HOME/standalone/deployments/decision-central.war/banner/banner.html file in a text editor.

4. Replace logo.svg in the <img> tag with the file name of your new image:admin-and-config/

   <img src="banner/logo.svg"/>

   Copy to Clipboard Toggle word wrap
5. Force a full reload of the login page, bypassing the cache, to view the changes. For example, in most Linux and Windows web browsers, press Ctrl+F5.