Installing and configuring Red Hat Decision Manager on Red Hat JBoss Web Server

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.3.0.jar

   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.3.0.jar

   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.3.0.jar

   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 Web Server 5.0.1 or higher 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.

   You cannot install Business Central on Red Hat JBoss Web Server. You can only install it on Red Hat JBoss EAP. However, you can install Decision Server and the headless Decision Manager controller on Red Hat JBoss Web Server. The headless Decision Manager controller is used to manage Decision Server. Install the headless Decision Manager controller if you plan to manage multiple Decision Server instances.

5. Create a user and click Next. By default, the new user is given the admin, kie-server, and rest-all roles. The kie-server role is required to acces Decision Server REST capabilities.

   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 Business 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, and 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.3.0.jar <path-to-file>

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.3.0.jar -console

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

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

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.2 or Red Hat JBoss Web Server 5.0.1

3. Enter the parent directory of an existing Red Hat JBoss Web Server 5.0.1 or higher installation.

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

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 Business 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?

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 Server, repeat these steps to install the headless Decision Manager controller on a separate server.

Procedure

1. Unzip the rhdm-7.3.0-add-ons.zip file.

2. From the unzipped rhdm-7.3.0-add-ons.zip file, extract the following files:

   • rhdm-7.3-kie-server-jws.zip
   • rhdm-7.3-decision-engine.zip

   In the following instructions, the directory that contains the extracted rhdm-7.3-kie-server-jws.zip file is called JWS_TEMP_DIR and the directory that contains the extracted rhdm-7.3-decision-engine.zip file is called ENGINE_TEMP_DIR.

3. Copy the JWS_TEMP_DIR/rhdm-7.3-kie-server-jws/kie-server.war directory to the JWS_HOME/tomcat/webapps directory.

   Note

   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 Web Server instance.

4. Remove the .war extensions from the kie-server.war folder.
5. Move the kie-tomcat-integration-7.18.0.Final-redhat-00002.jar file from the ENGINE_TEMP_DIR directory to the JWS_HOME/tomcat/lib directory.
6. Move the jboss-jacc-api-<VERSION>.jar, slf4j-api-<VERSION>.jar, and slf4j-jdk14-<VERSION>.jar files from the ENGINE_TEMP_DIR/lib directory to the JWS_HOME/tomcat/lib directory, where <VERSION> is the version artifact file name, in the lib directory.
7. Unzip the rhdm-7.3.0-maven-repository.zip file.

8. Copy the following libraries from the unzipped Maven repository to the JWS_HOME/tomcat/lib folder:

   org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec
   org.jboss.integration:narayana-tomcat
   org.jboss.narayana.jta:narayana-jta
   org.jboss:jboss-transaction-spi

9. Add the following line to the <host> element in the TOMCAT_HOME/conf/server.xml file after the last Valve definition:

   <Valve className="org.kie.integration.tomcat.JACCValve" />

10. Open the JWS_HOME/tomcat/conf/tomcat-users.xml file in a text editor.

11. Add users and roles to the JWS_HOME/tomcat/conf/tomcat-users.xml file. In the following example, <ROLE_NAME> is a role supported by Red Hat Decision Manager. <USER_NAME> and <USER_PWD> are the user name and password of your choice:

    <role rolename="<ROLE_NAME>"/>
    <user username="<USER_NAME>" password="<USER_PWD>" roles="<ROLE_NAME>"/>

    If a user has more than one role, as shown in the following example, separate the roles with a comma:

    <role rolename="admin"/>
    <role rolename="kie-server"/>
    <user username="rhdmUser" password="user1234" roles="admin,kie-server"/>

12. Complete one of the following steps in the JWS_HOME/tomcat/bin directory:

    • On Linux or UNIX, create the setenv.sh file with the following content:

      CATALINA_OPTS="-Xmx1024m
       -Dorg.jboss.logging.provider=jdk
       -Dorg.jbpm.server.ext.disabled=true
       -Dorg.jbpm.ui.server.ext.disabled=true
       -Dorg.jbpm.case.server.ext.disabled=true"

    • On Windows, add the following content to the setenv.bat file:

      set CATALINA_OPTS="-Xmx1024m -Dorg.jboss.logging.provider=jdk -Dorg.jbpm.server.ext.disabled=true -Dorg.jbpm.ui.server.ext.disabled=true -Dorg.jbpm.case.server.ext.disabled=true

Procedure

1. Generate a Maven project. A pom.xml file is automatically generated when you create a Maven project.

2. Edit the pom.xml file to add more dependencies and new repositories.

   Maven downloads all of the JAR files and the dependent JAR files from the Maven repository when you compile and package your project.

Procedure

1. In the settings.xml file, declare the repositories that your Red Hat Decision Manager projects use. Usually, this is either the online Red Hat Decision Manager Maven repository or the Red Hat Decision Manager Maven repository that you download from the Red Hat Customer Portal and any repositories for custom artifacts that you want to use.
2. Ensure that Business Central or Decision Server is configured to use the settings.xml file, for example by specifying the kie.maven.settings.custom=<path_to_settings.xml> property.

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.3.0.GA-redhat-00002</version>
      <type>pom</type>
      <scope>import</scope>
     </dependency>
    </dependencies>
   </dependencyManagement>
   <dependencies>
   <!-- Your dependencies -->
   </dependencies>

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 Business Central, specify all dependencies required for your projects. In projects that you author in Business Central, the basic decision engine dependencies are provided automatically by Business 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:business-central-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>

   • 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>

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

     Client dependency

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

   • 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>