CA RiskMinder UNIX Installation Guide › Upgrading RiskMinder › Upgrading to Release 3.1 › Performing Pre-Upgrade Tasks

Performing Pre-Upgrade Tasks

Important! Perform the upgrade procedure on the system where the Administration Console is installed.

Perform the following pre-upgrade tasks before you begin the upgrade procedure:

• If you are upgrading from RiskFort 1.x to 3.1, migrate all your proposed configuration data to production. Only active data is migrated and available after upgrade.

  Note: If you are upgrading from RiskFort 2.x or 3.0.x to 3.1, both proposed and active configuration data get migrated.

• From release 3.1 onward, a rule with a score of 0 no longer carries the ALLOW advice. Instead, a score of 0 implies SILENT, which means that the rule is executed but is not used for scoring. In addition, if the default score was 0 before the upgrade, then the default rule score is changed to 1 during the upgrade.

  Note: For information about changing the score of a rule, see the administration guide for your RiskMinder release.

• Custom add-on rule types that you created in release 2.x or earlier releases are not migrated during the upgrade. The feature to create a custom add-on rule type by importing an XML file has been deprecated. If your RiskMinder deployment contains custom add-on rule types, then it is recommended that you delete them before the upgrade.
• If the mnemonic of an existing rule is the same as the mnemonic of a rule that is newly introduced or modified by the upgrade, then the upgrade fails. The same issue is encountered if the name of an existing rule is the same as the name of a new rule. To avoid this issue:
  1. Use the administration console to compare the mnemonics of your existing rules with the mnemonics of the rules that are newly introduced or modified by the upgrade.

     The following table lists the rules that are newly introduced or modified by the upgrade:

1. If the mnemonic of an existing rule matches the mnemonic of a new rule, delete the existing rule and then re-create it. While you are re-creating the rule, give it a different mnemonic. Follow the same approach if the name of an existing rule matches the name of a new rule.

   Note: For information about deleting and creating rules, see the administration guide for your current RiskMinder release.

• In release 2.x, you can have a rule, ruleset, or miscellaneous rule configuration refer to another rule, ruleset, or miscellaneous rule configuration. This feature is not available in release 3.1. Perform the following steps for each rule, ruleset, or miscellaneous rule configuration that refers to another rule, ruleset, or miscellaneous rule configuration:
  1. Log in to the Administration Console as a GA or OA.
  2. If you have logged in as the GA and you want to perform this procedure for a system ruleset, click the Services and Server Configurations tab.
  3. If you have logged in as the GA or OA to perform this procedure for a single organization:

     Activate the Organizations tab.

     Click the Search Organization link under Manage Organizations.

     Click the Search button on the Search Organization page to display the list of organizations.

     Click the name of the organization.

     Click the RiskFort Configuration tab.

  4. Under the Rules Management section on the side-bar menu, click the link for the rule, ruleset, or miscellaneous rule configuration that refers to another rule, ruleset, or miscellaneous rule configuration.
  5. Select Use Own.
  6. Select Copy from an Existing Ruleset.
  7. From the Ruleset Name list, select the ruleset to which this rule, ruleset, or miscellaneous rule configuration was referring.
  8. Click Save.
  9. Migrate the changes to production.

     Note: For detailed information about migrating the changes to production and refreshing the cache, see the CA RiskMinder Administration Guide.

• The upgrade process is supported only in the offline mode. Shut down the following gracefully:
  • RiskFort Server
  • Case Management Queuing Server
  • Any application servers where Administration Console and User Data Service are deployed
• If Administration Console is open, close it.
• Open the $ARCOT_HOME/conf/arcotcommon.ini file in a text editor, and then perform the following steps:
  1. Ensure that the primary database details are correct. The upgrade tool uses the database that is configured in this file for the upgrade.
  2. If you have configured a backup database, then you must disable the backup database by commenting out the lines containing the following properties in the arcot/db/backupdb section of the arcotcommon.ini file:
     • URL.1
     • AppServerConnectionPoolName.1
     • Username.1
  3. Include the following section in the arcotcommon.ini file:

     [arcot/crypto/device]
     HSMDevice=S/W
     

  4. Save and close the arcotcommon.ini file.
• Ensure that you have JDK 1.5 or later installed on the system where you plan to upgrade.
• Ensure that the database on which you plan to upgrade is available throughout the upgrade process.
• Ensure that the database on which you plan to upgrade is disabled for replication.
• Back up the database containing the RiskMinder schema.
• If you require multi-byte character or internationalization support in RiskMinder and if your database does not currently support multi-byte data, then migrate the database to a character set that supports multibyte data. For more information, see Configuring Database Server.
• Consider the requirements, such as rollback segment size, which are based on data volume, before running the upgrade tool.
• Ensure that you have the database privileges that are required to upgrade RiskMinder. For the complete list of privileges, see Database Privileges Required for Upgrade.
• If you have stored user details in an LDAP repository in the previous release, ensure that the LDAP server is available throughout the upgrade process.
• Ensure that the ARCOT_HOME environment variable is set to the directory where RiskFort is installed.
• Copy the contents of your existing ARCOT_HOME directory to a new directory.

  Here, ARCOT_HOME refers to the base directory that contains the entire directory structure that was created by the existing RiskMinder installation. Typically, ARCOT_HOME is install_location/arcot/.

  ARCOT_HOME_BACKUP refers to the backup directory into which you copy the contents of the existing the ARCOT_HOME directory. If you encounter any errors during upgrade, use the ARCOT_HOME_BACKUP directory to revert to the initial setup.