Chapter 4. Decision Server ZIP file installation and configuration

You can install Decision Server using the rhdm-7.4-kie-server-jws.zip file available from the Red Hat Decision Manager 7.4.0 Add Ons (rhdm-7.4.0-add-ons.zip) file on the Customer Portal .

4.1. Installing Decision Server from ZIP files

Decision Server provides the runtime environment for business assets and accesses the data stored in the assets repository (knowledge store). You can use ZIP files to install Decision Server on an existing Red Hat JBoss Web Server 5.1.0 server instance.

Note

To use the installer JAR file to install Decision Server, see Chapter 3, Using the Red Hat Decision Manager installer.

  • The Red Hat Decision Manager 7.4.0 Add Ons (rhdm-7.4.0-add-ons.zip) file has been downloaded, as described in Chapter 2, Downloading the Red Hat Decision Manager installation files.
  • A backed-up Red Hat JBoss Web Server 5.1.0 server installation is available. The base directory of the Red Hat JBoss Web Server installation is referred to as JWS_HOME.
  • Sufficient user permissions to complete the installation are granted.

Procedure

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

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

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

  3. Copy the JWS_TEMP_DIR/rhdm-7.4-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 copy 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.23.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. Add the following line to the <host> element in the JWS_HOME/conf/server.xml file after the last Valve definition:

    <Valve className="org.kie.integration.tomcat.JACCValve" />
  8. Open the JWS_HOME/tomcat/conf/tomcat-users.xml file in a text editor.
  9. 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"/>
  10. 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