Chapter 3. Installing supporting tools

Procedure

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

2. Edit pom.xml 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. Declare the BOM in pom.xml. For example:

   Example 3.1. BOM for Red Hat Decision Manager 7.0.0

   <dependencyManagement>
    <dependencies>
     <dependency>
      <groupId>org.jboss.bom.rhdm</groupId>
      <artifactId>rhdm-platform-bom</artifactId>
      <version>7.0.0.Final-redhat-4</version>
      <type>pom</type>
      <scope>import</scope>
     </dependency>
    </dependencies>
   </dependencyManagement>
   <dependencies>
   <!-- Your dependencies -->
   </dependencies>

   Copy to Clipboard Toggle word wrap

2. Declare dependencies needed for your project in the <dependencies> tag.

   • For a basic Red Hat Business Automation project, declare the following dependencies:

     Embedded jBPM Engine Dependencies

     <dependency>
       <groupId>org.jbpm</groupId>
       <artifactId>jbpm-kie-services</artifactId>
     </dependency>
     
     <!-- Dependency needed for default WorkItemHandler implementations. -->
     <dependency>
       <groupId>org.jbpm</groupId>
       <artifactId>jbpm-workitems-core</artifactId>
     </dependency>
     
     <!-- Logging dependency. You can use any logging framework compatible with slf4j. -->
     <dependency>
       <groupId>ch.qos.logback</groupId>
       <artifactId>logback-classic</artifactId>
       <version>${logback.version}</version>
     </dependency>
     
     <dependency>
       <groupId>org.kie</groupId>
       <artifactId>kie-api</artifactId>
     </dependency>

     Copy to Clipboard Toggle word wrap

   • For a Red Hat Business Automation project that uses CDI, declare the following dependencies:

     CDI-Enabled jBPM Engine dependencies

     <dependency>
       <groupId>org.kie</groupId>
       <artifactId>kie-api</artifactId>
     </dependency>
     
     <dependency>
       <groupId>org.jbpm</groupId>
       <artifactId>jbpm-kie-services</artifactId>
     </dependency>
     
     <dependency>
       <groupId>org.jbpm</groupId>
       <artifactId>jbpm-services-cdi</artifactId>
     </dependency>

     Copy to Clipboard Toggle word wrap

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

     Embedded Drools 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>
     <dependency>
         <groupId>org.kie.server</groupId>
         <artifactId>kie-server-api</artifactId>
     </dependency>
     
     <!-- Dependency for Red Hat JBoss BRMS functionality. -->
     <dependency>
       <groupId>org.drools</groupId>
       <artifactId>drools-core</artifactId>
     </dependency>
     
     <dependency>
       <groupId>org.kie</groupId>
       <artifactId>kie-api</artifactId>
     </dependency>

     Copy to Clipboard Toggle word wrap

   • To create a remote client for Red Hat Business Automation or Red Hat Decision Manager, declare the following dependencies:

     Client Dependencies

     <dependency>
       <groupId>org.uberfire</groupId>
       <artifactId>uberfire-rest-client</artifactId>
     </dependency>

     Copy to Clipboard Toggle word wrap

   • To use assets in KJAR packaging, the recommended way is to include kie-maven-plugin:

     Kie Maven Plugin

     <packaging>kjar</packaging>
     <build>
      <plugins>
       <plugin>
        <groupId>org.kie</groupId>
        <artifactId>kie-maven-plugin</artifactId>
        <version>7.0.0.Final-redhat-4</version>
        <extensions>true</extensions>
       </plugin>
      </plugins>
     </build>

     Copy to Clipboard Toggle word wrap

Procedure

1. Start Red Hat JBoss Developer Studio.
2. Click Help Install New Software.
3. Click Add to enter the Add Repository menu.
4. Provide a name next to the Name field and add the following URL in the Location field: https://devstudio.jboss.com/11/stable/updates/integration-stack/.
5. Click OK.
6. Select the JBoss Business Process and Rule Development feature from the available options, click Next, and then click Next again.
7. Read the license and accept it by selecting the appropriate radio button, and click Finish.
8. Restart Red Hat JBoss Developer Studio after the installation process finishes.

Procedure

1. Start Red Hat JBoss Developer Studio.
2. To open the Drools view, click Window Open Perspective Other, select Drools, select specific views, and click OK.
3. Click Window Show View Other…​ and select Server Servers to add the server view.
4. Right click the Servers panel and select New Server to open the server menu.
5. Click JBoss Enterprise Middleware JBoss Enterprise Application Platform 7.1+ and click Next to define the server.

6. Set the home directory by clicking the Browse button. Navigate to theRed Hat JBoss EAP directory where Red Hat Decision Manager is installed.

   To configure the Red Hat Decision Manager server, select the Red Hat JBoss EAP directory where Red Hat Decision Manager is installed.

7. Provide a name for the server in the Name field, ensure that the configuration file is set, and click Finish.

Procedure

1. In Red Hat JBoss Developer Studio, select the server from the Server tab and click the start icon to start your server.

2. Enter the following command in a terminal to start the Secure Shell server, if it is not running already.

   /sbin/service sshd start

   Copy to Clipboard Toggle word wrap
   Note

   This command is specific to Linux and Apple Macintosh. On these platforms, if sshd has already been started, this command fails. If this happens, you may safely ignore this step.

3. In Red Hat JBoss Developer Studio , select File Import…​ and navigate to the Git folder. Open the Git folder to select Projects from Git and click Next.
4. Select the repository source as Clone URI and click Next.
5. Enter the details of the Git repository in the next window and click Next.
6. Select the branch you wish to import in the following window and click Next.
7. To define the local storage for this project, enter (or select) a non-empty directory, make any configuration changes and click Next.
8. Import the project as a general project in the following window and click Next.
9. Name the project and click Finish.

Procedure

1. Select your server from the Server tab and click the start icon to start the server.
2. In Red Hat JBoss Developer Studio, select File Import…​ and navigate to the Git folder. Open the Git folder to select Projects from Git and click Next.
3. Select the repository source as Existing local repository and click Next.
4. Select the repository that is to be configured from the list of available repositories and click Next.
5. In the dialog window that opens, select the Import as general project radio button from the Wizard for project import group and click Next.
6. Name the project and click Finish.