Upgrading in a Java SE deployment

You upgrade Decision Server Rules in a Java™ SE deployment.

Before you begin

Follow these steps if you are using Decision Server Rules in aJava SE deployment. These steps apply to application servers that include Tomcat and WebSphere® Liberty.

In-place upgrading of the Rule Execution Server and Decision Warehouse databases is not necessary when you do a rolling upgrade from 8.11.x or later because the database schemas are compatible with the database schema of 9.6.0.

Prerequisites for this task:

  • Make sure that all the Operational Decision Manager components are at the same initial version level when you start your rolling upgrade to the target version (version 9.6.0).
  • Install the Rule Execution Server of the target version on the same computer that accesses the Rule Execution Server database.
  • Back up the client web applications.
  • If you are using the WebSphere Liberty server, you should upgrade the features as shown in the following example:
    <!-- Enable features --> <featureManager> <feature>servlet-4.0</feature> <feature>jsp-2.3</feature> <feature>jdbc-4.1</feature> <feature>appSecurity-3.0</feature> <feature>concurrent-1.0</feature> </featureManager>
    See Step 1: Deploying the Rule Execution Server management archive.

Procedure

  1. For the target version, deploy the Rule Execution Server console management WAR file (res.war) for your supported application server, which is JDK 21.
  2. Update the DecisionService.war HTDS to the target version.
  3. Verify that the Rule Execution Server console of the target version is connected to the Rule Execution Server database, and that the console is using the same IP addresses as the previous version.
    To continue operations at execution time, the console must point to the same IP address as the previous version for the TCP/IP notification. This constraint is not mandatory for the JMX notification.
  4. If you have rule sessions in Java client applications, replace all the Operational Decision Manager .jar files and third-party .jar files under the Java client application class path in the previous version with the corresponding .jar files under the Java client application class path of the target version.
  5. Replace the <installDir>/exeutionserver/lib/jrules-res-tools.jar file with the one for the target version. With this file, you can use Ant tasks to do such operations as generating and deploying a RuleApp archive.

Results

Diagram shows the results of the Operational Decision Manager rolling upgrade for the execution stack for the distributed platform.
  • The Rule Execution Server console is at the target version.
  • All execution stacks are upgraded to the target version.

What to do next

Update Decision Center.