Chapter 6 Migrating from Earlier Versions : Upgrading From Version 3.0.0

Upgrading From Version 3.0.0
If you are upgrading from version 3.0.0, and you use Decision Manager, you must perform some steps before and after installing BusinessEvents.
Backing Store Schema Change
Backing store schema changed in 3.0.1. See Updating an Existing Backing Store Database Schema in TIBCO BusinessEvents User’s Guide for instructions to update the schema.
Before Installing the Current Version
 
Task A Back up Configuration Files
The installer overwrites configuration files for RMS and Decision Manager. Before running the installer, backup these configuration files.
If you have not made changes to the configuration files, you can skip this step.
BE_HOME/rms/bin/be-rms.tra
BE_HOME/DecisionManager/config/bui-config.tra
BE_HOME/DecisionManager/DecisionManager.ini
Where BE_HOME is the BusinessEvents installation directory. By default the installation directory on Windows is C:\tibco\be\3.0
Task B Back up Project Directories
Existing RMS and decision projects remain untouched during the update process, but, as with all valuable data, it is recommended to keep backups.
Task C Act on All Decision Table Change Commitments for All Worklists
Before migrating, clear all worklists.
The format of the data files used to track Worklist items has changed in version 3.0.1. These changes are due to newly added Worklist features and additional information associated with each commitment request.
As a result, earlier versions of these data files will not work with the current version of Decision Manager.
The current version of Decision Manager adds additional configuration options to allow you to customize the location of the data files used to track Worklist items in the future. (See Changes in The RMS Engine Properties File).
After Installing the Current Version
Carefully read the following sections and make all changes that are relevant to your situation.
Save all Decision Tables Created in Earlier Versions Before Exporting
After checking out a decision table created in BusinessEvents version 3.0 or earlier, you cannot immediately export the decision table.
First open the decision table in the Decision Manager editor. This action converts the decision table to the current format.
Decision Manager and RMS
Configuration Changes in Decision Manager and RMS: Ensure you have updated your configuration to account for the following changes.
New Resources Require Permissions in Project Access Control Files
You must configure permissions for the following new resources:
For Example:

 
<resources>
...
  <resource id="TABLE" type="DECISIONTABLE"/>
</resources>
<entries>
  <entry>
    <role name="RULE_ADMINISTRATOR" />
    <permissions>
      ...
      <permission resourceref="#TABLE">
        <action type="read">ALLOW</action>
      </permission>
    </permissions>
  </entry>
</entries>

 
Failure to include these new resources in the access configuration file could result in the following error message:
Project checkout failed. : Insufficient privileges for checkout
For an example of an access configuration file (including these new resources), see the following config directories:
BE_HOME/rms/examples/CreditCardApplication/config
BE_HOME/rms/examples/AirlineFlightSystem/config
Changes in The RMS Engine Properties File
The following properties are changed in or added to theBE_HOME/rms/bin/ be-rms.tra file:
RMS now supports multiple projects. You can keep all of your RMS projects in a single projects directory. This new property define the path to the projects directory.
By default, the path is set to BE_HOME/rms/examples.
Either move RMS projects to this location, or update the property to point to a different location.
Note  Single-project mode is still supported. See TIBCO BusinessEvents Decision Manager for configuration details.
To support large decision tables, the amount of RAM allocated for the heap has increased from 256MB to 1024MB.
This new property defines the location of the workflow configuration file. The concept of a decision project workflow is new in this release.
As mentioned in After Installing—Check and Update Properties Files and All UNIX Installations—Check and Update Properties Files, set the value of this property to your actual hostname. The value as shipped is as follows:
This new property enables you to configure where to store the database that maintains all project Worklist information. The default location is BE_HOME/rms/bdb.
When RMS is configured to support multiple projects, the authentication configuration file (which defines users, passwords, and role memberships for RMS) applies to all projects managed by RMS. The value is interpreted differently depending on whether you use multi-project or single project mode:
In multi-project mode, the configuration setting that defines where the authentication file is located is defined relative to the baselocation property.
Changes in The Decision Manager Configuration File
The tibco.bui.codegen.prepend_classpath property in the bui-config.tra file has been changed.
An additional parameter has been provided to enable extension of the classpath used to find JAR files containing custom Java functions.
Changes in the DecisionManager.ini File
The DecisionManager.ini file defines custom arguments to the JVM when running Decision Manager.
In order for Decision Manager to handle very large decision projects, the RAM allocated to the application has increased as follows:
-Xms1024m
-Xmx1024m