Installing and configuring Decision Server on IBM WebSphere Application Server

Procedure

1. Download IBM Installation Manager version 1.8.5 or later from the IBM Installation Manager and Packaging Utility download links page. IBM Installation Manager is required for installing IBM WebSphere.

2. Extract the downloaded archive and run the following command as the root user in the new directory:

   sudo ./install

   The IBM Installation Manager opens.

3. Go to File → Preferences and click Add Repository.
4. In the Add Repository window, enter the repository URL for IBM WebSphere 9.0. You can find all the repository URLs in the Online product repositories for IBM WebSphere Application Server offerings page of the IBM Knowledge Center.
5. In your command terminal, navigate to the IBM WebSphere Application Server folder location that you specified during the installation.

6. Change to the /bin directory and run a command similar to the following example to create an IBM WebSphere profile, user name, and password. A profile defines the run time environment. The profile includes all the files that the server processes in the runtime environment and that you can change. The user is required for login.

   sudo ./manageprofiles.sh -create -profileName testprofile -profilePath /profiles/testprofile  -adminUserName websphere -adminPassword password123

7. In your command terminal, navigate to the bin directory within the profile that you created (for example, /profiles/testprofile/bin) and run the following command to start the IBM WebSphere Application Server instance:

   sudo ./startServer.sh <SERVER_NAME>

   <SERVER_NAME> is the IBM WebSphere Application Server name defined in Servers → Server Types → IBM WebSphere Application Servers of the WebSphere Integrated Solutions Console.

8. Open the following URL in a web browser:

   http://<HOST>:9060/ibm/console

   <HOST> is the system name or IP address of the target server.

   For example, to start the WebSphere Integrated Solutions Console for a local instance of IBM WebSphere running on your system, enter the following URL in a web browser:

   http://localhost:9060/ibm/console

9. When the login page of the WebSphere Integrated Solutions Console appears, enter your administrative credentials.

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.4
2. Download Red Hat Decision Manager 7.4.0 Decision Server for All Supported EE7 Containers.
3. Extract the rhdm-7.4.0-kie-server-ee7.zip archive to a temporary directory. In the following examples this directory is called TEMP_DIR.

4. Repackage the kie-server.war directory:

   1. Navigate to the TEMP_DIR/rhdm-7.4.0-kie-server-ee7/kie-server.war directory.
   2. Select the contents of the TEMP_DIR/rhdm-7.4.0-kie-server-ee7/kie-server.war directory and create the kie-server.zip file.
   3. Rename kie-server.zip to kie-server.war. This is the file that you will use to deploy Decision Server.
   4. If desired, copy the new kie-server.war file to a location that is more convenient to deploy from.
5. In the WebSphere Integrated Solutions Console, navigate to Applications → Application Types → WebSphere Enterprise Applications.
6. Click Install.
7. Navigate to the kie-server.war file that you repackaged and select it to upload.

8. Select Fast Path and click Next.

   The Install New Application wizard opens.

9. Change the Application Name to kie-server and click Next.
10. Map the Decision Server modules to servers according to your specific requirements and click Next.
11. For Bind Listeners for Message-Driven Beans, select Activation Specification for both beans, enter jms/activation/KIE.SERVER.REQUEST in the Target Resource JNDI Name field, and enter the jms/cf/KIE.SERVER.REQUEST JNDI name for the KIE.SERVER.REQUEST connection factory.
12. In the Map Virtual Hosts for Web Modules section, keep the default values and click Next.
13. Set the context root to kie-server.
14. In the Metadata for Modules section, keep the default values and click Next.
15. Click Finish to install Decision Server and click Save to save the changes to the master configuration.

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.4
2. Download Red Hat Decision Manager 7.4.0 Add-Ons.
3. Extract the downloaded rhdm-7.4.0-add-ons.zip file to a temporary directory.
4. Extract the rhdm-7.4.0-add-ons.zip file to a temporary directory. In the following examples this directory is called TEMP_DIR.
5. Extract the rhdm-7.4.0-add-ons/rhdm-7.4-controller-ee7.zip file.

6. Repackage the controller.war directory:

   1. Navigate to the TEMP_DIR/rhdm-7.4.0-add-ons/rhdm-7.4-controller-ee7/controller.war directory.
   2. Select the contents of the TEMP_DIR/rhdm-7.4.0-add-ons/rhdm-7.4-controller-ee7/controller.war directory and create the controller.zip file.
   3. Rename controller.zip to controller.war. This is the file that you will use to deploy the headless Decision Manager controller.
   4. If desired, copy the new controller.war file to a location that is more convenient to deploy from.
7. In the WebSphere Integrated Solutions Console, navigate to Applications → Application Types → WebSphere Enterprise Applications.
8. Click Install.
9. Navigate to the controller.war file that you repackaged and select it to upload.

10. Select Fast Path and click Next.

    The Install New Application wizard opens.

11. Change the Application Name to controller and click Next.
12. Map the headless Decision Manager controller modules to servers according to your specific requirements and click Next.
13. For Bind Listeners for Message-Driven Beans, select Activation Specification for both beans, enter jms/activation/KIE.SERVER.REQUEST in the Target Resource JNDI Name field, and enter the jms/cf/KIE.SERVER.REQUEST JNDI name for the KIE.SERVER.REQUEST connection factory.
14. In the Map Virtual Hosts for Web Modules section, keep the default values and click Next.
15. Set the context root to controller.
16. In the Metadata for Modules section, keep the default values and click Next.
17. Click Finish to install the headless Decision Manager controller and click Save to save the changes to the master configuration.

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.4.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.

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

     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>
       <artifactId>uberfire-rest-client</artifactId>
     </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>

3. If you use a decision engine with persistence support in your project, you must declare the following hibernate dependencies in the dependencyManagement secion of your pom.xml file by copying the version.org.hibernate-4ee7 property from the Red Hat Business Automation BOM file:

   Hibernate dependencies in decision engine with persistence

   <!-- hibernate dependencies -->
   <dependencyManagement>
     <dependencies>
       <dependency>
       <groupId>org.hibernate</groupId>
       <artifactId>hibernate-entitymanager</artifactId>
       <version>${version.org.hibernate-4ee7}</version>
       </dependency>
   
       <dependency>
       <groupId>org.hibernate</groupId>
       <artifactId>hibernate-core</artifactId>
       <version>${version.org.hibernate-4ee7}</version>
       </dependency>
     </dependencies>
   </dependencyManagement>

Procedure

1. Create a JCEKS keystore.
2. When prompted, enter the password for the Decision Server user that you created.

3. Set the system properties listed in the following table:

   Table 8.1. System properties used to load a Decision Server JCEKS

   System property	Placeholder	Description
   kie.keystore.keyStoreURL	<KEYSTORE_URL>	URL for the JCEKS that you want to use, for example file:///home/kie/keystores/keystore.jceks
   kie.keystore.keyStorePwd	<KEYSTORE_PWD>	Password for the JCEKS
   kie.keystore.key.server.alias	<KEY_SERVER_ALIAS>	Alias of the key for REST services where the password is stored
   kie.keystore.key.server.pwd	<KEY_SERVER_PWD>	Password of the alias for REST services with the stored password
   kie.keystore.key.ctrl.alias	<KEY_CONTROL_ALIAS>	Alias of the key for default REST Process Automation Controller where the password is stored
   kie.keystore.key.ctrl.key.ctrl.pwd	<KEY_CONTROL_PWD>	Password of the alias for default REST Process Automation Controller with the stored password

4. Start Decision Server to verify the configuration.