Migrating from Red Hat JBoss BRMS 6.4 to Red Hat Decision Manager 7.0

Prerequisites

1. In BRMS 6.4 Business Central, look up the names of the repositories that contain your project. The default repository name is repository1 .
2. Stop BRMS 6.4 Business Central.
3. Locate the .niogit directory. In the default installation, its location is $EAP_home/bin/.niogit . This location can be changed with the org.uberfire.nio.git.dir system property in the $EAP_home/standalone/configuration/standalone.xml file. The system property can also be set with a -D option in the command that starts Business Central.
4. Install the Red Hat Decision Manager, including Decision Central, on the same host as BRMS 6.4 Business Central, using a separate JBoss EAP installation. For instructions, see Installing Red Hat Decision Manager on premise.

Procedure

1. Log in to Red Hat Decision Manager 7.0 Decision Central.
2. In the main menu, select Projects.
3. Click the icon and select Import Project.

4. In the Repository URL field, type the URL:

   file://<path>/.niogit/<repository>.git

   For example, if the location of the .niogit directory is /opt/eap7.0/bin/.niogit and you want to import projects from the repository1 repository:

   file:///opt/eap7.0/bin/.niogit/repository1.git

5. Click Import.
6. Select the projects to import and click Import.

7. A NoRemoteRepositoryException exception might be displayed. In this case complete the following steps:

   1. In a shell terminal, change to the repository subdirectory (under the .niogit) directory you are importing
   2. List the remotes: git remote -v

   3. Remove all listed remotes: git remote remove <remote-name>

      For example:

      $ /opt/eap7.0/bin/.niogit/repository1.git
      $ git remote -v
      origin  https://github.com/guvnorngtestuser1/guvnorng-playground (fetch)
      origin  https://github.com/guvnorngtestuser1/guvnorng-playground (push)
      $ git remote remove origin

      Then import the projects again. (You can add the remotes in the new repository later if necessary).

8. Wait for the importing and indexing to complete.
9. Repeat the process for any other repositories that you wish to import.

Procedure

1. Open the pom.xml file of the project.

2. Remove the <version> tag from any dependencies under the following groups:

   • org.kie
   • org.drools
   • org.jbpm
   • org.optaplanner

3. Add the following dependency under the <dependencies> tag within the <dependencyManagement> section:

   <dependency>
     <groupId>org.jboss.bom.rhdm</groupId>
     <artifactId>rhdm-platform-bom</artifactId>
     <version>${rhdm.version}</version>
     <scope>import</scope>
     <type>pom</type>
   </dependency>

   Where ${rhdm.version} is the version of the org.jboss.bom.rhdm:rhdm-platform-bom artifact in the Maven repository for Red Hat Decision Manager 7.0. You can view the version of the artifact by entering the repository and navigating to maven-repository/org/jboss/bom/rhdm/rhdm-platform-bom directory; the name of the only subdirectory in this directory is the version. For example, 7.0.0.GA-redhat-1 .

4. If your code uses any Drools CDI annotations (@KReleaseId , @KContainer, @KBase, @KSession), also add the following dependency:

   <dependency>
     <groupId>org.drools</groupId>
     <artifactId>drools-cdi</artifactId>
   </dependency>

   This dependency is necessary because the CDI extension for processing the annotations is now defined using a separate module. Without this dependency, the annotations do not work.

5. Replace the legacy org.guvnor dependency (if applicable) with the new org.uberfire dependency.

   Legacy org.guvnor dependency:

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

   New org.uberfire dependency:

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

6. Update the version of the project artifact and save the pom.xml file.
7. Rebuild the project, using a regular Maven build.
8. If build errors or subsequent execution errors happen, resolve them using the information in Section 3.1, “Troubleshooting build and execution errors in migrated Java projects”.

Procedure

1. Install Red Hat Decision Manager 7.0 Decision Server on the same host as a BRMS 6.4 KIE Server. Use a separate JBoss EAP installation. For instructions, see Installing Red Hat Decision Manager on premise.
2. Configure the Red Hat Decision Manager 7.0 Decision Server to bind to the same port as the BRMS 6.4 KIE Server. (The default settings are the same).

3. Configure the Decision Server to use a Maven repository that contains your decision services (KJAR files). Use one of the following approaches:

   • Use the same KJAR files as of the BRMS 6.4 KIE Server. To copy the Maven configuration, copy the value of the kie.maven.settings.custom system property from the old version $EAP_home/standalone/configuration/standalone.xml file to the same file in the new version.
   • Upgrade your decision services to the new version. For instructions, see Chapter 2, Migrating projects in Decision Central and Chapter 3, Migrating Java projects. Upload the new KJAR files to a Maven repository. Then configure the Decision Server to use the repository:
   1. Create a settings.xml file for the Maven repository

   2. In the $EAP_home/standalone/configuration/standalone.xml file for Red Hat Decision Manager 7.0 Decision Server, under the <system-properties> tag, set the kie.maven.settings.custom property to the full pathname of the settings.xml file, for example:

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

      In this case, you need to change the version of the KJAR files. Change the version of the services that you start accordingly. You can still use the same container name to ensure maximum compatibility with existing clients.

4. Stop the BRMS 6.4 KIE Server.
5. Start the Red Hat Decision Manager 7.0 Decision Server.
6. Use the API to start the necessary decision services. For instructions, see Packaging and deploying a decision service.