Previous Topic: Reinstalling RiskMinder on a Distributed SystemNext Topic: Reviewing Configuration Changes After Upgrade


(In Error Scenario Only) Reverting to Your Initial Setup

During upgrade, if there are any warnings during the RiskMinder Server startup and if your transactions fail, then you may want to revert to your initial setup.

Follow these steps:

  1. Uninstall RiskMinder 3.1.

    Refer to "Uninstalling RiskMinder" for more information.

  2. Install the RiskMinder version that you want to revert to. For example, 1.x or 2.x.

    Note: For installation instructions, see the CA RiskMinder Installation and Deployment Guide that is shipped with the corresponding release.

  3. Navigate to the location where ARCOT_HOME_BACKUP directory is available.
  4. Copy the contents of ARCOT_HOME_BACKUP to your current ARCOT_HOME.
  5. Replace the ArcotAccessKeyProvider.dll file in <JAVA_HOME used by Application Server>\jre\bin with the backup that you created while performing the procedure described in Migrating the Database to Release 2.2.7 for Arcot Common Components.
  6. Deploy the web components, such as the Administration Console and UDS.
  7. Start RiskMinder Server and Case Management Queuing Server.
  8. Test the installation.

Performing Post-Upgrade Tasks

This section describes the tasks that you must perform after upgrading to release 3.1.

Follow these steps:

  1. During the upgrade, the following tables may be created in the RiskMinder database:

    These temporary tables are used only during the upgrade process. Because these tables are not required by RiskMinder, drop them from the database if they exist.

  2. If you disabled database replication before upgrade, then after you upgrade to RiskMinder 3.1 enable replication for the backup database.
  3. If you configured SSL for the following ports in RiskMinder 2.2.7, then reconfigure SSL.

    Reconfigure SSL as follows:

    This configuration is required because most administrative tasks, such as instance management and protocol configuration, are done using these ports in Administration Console in release 3.1.

    Note: For instructions on setting up SSL between Administration Console and RiskMinder Server or Case Management Queuing Server, see "Configuring SSL" in the CA RiskMinder Administration Guide.

  4. Set the Base Currency Code for your organization from the Miscellaneous Configurations screen.

    Note: For more information about setting the organization-specific base currency code, see Managing Global Configurations" in the CA RiskMinder Administration Guide.

  5. If there are any rules with a score of 0 and you want to use these rules for scoring, then change the score to a nonzero value, like 1 or 2.

Replacing Deprecated Rules with New Rules

Four of the predefined rules have been deprecated in release 3.1. Alternative rules have been introduced for these deprecated rules. The following table lists the deprecated and new rules and rule mnemonics:

Deprecated Rule Name and Rule Mnemonic

New Rule Name and Rule Mnemonic

DeviceID Known (DEVICEIDCHECK)

Unknown DeviceID (UNKNOWNDEVICEID)

Device MFP Match (SIGMATCH)

Device MFP Not Match (MFPMISMATCH)

User Associated with DeviceID (USERDEVICEASSOCIATED)

User Not Associated with DeviceID (USERDEVICENOTASSOCIATED)

User Known (USERKNOWN)

Unknown User (UNKNOWNUSER)

Important! Although these rules have been deprecated, they are still available and can be used after the upgrade. However, it is recommended that you replace each deprecated rule with the corresponding new rule by making the required changes in the rule expression.

For any of the four deprecated rules, if the rule evaluates to No, then the rule is considered to have matched and it is used for scoring. In contrast, each of the other predefined rules is considered to have matched when they evaluate to Yes.

In each of the four new rules that is introduced in release 3.1, if the rule evaluates to Yes, then the rule is considered to have matched. In this way, the four new rules are consistent with the other predefined rules.

The following table lists examples that highlight the difference between the deprecated rules and new rules:

Sample Use Case

Deprecated Rule

Deprecated Rule Result

New Rule

New Rule Result

User does not exist in the RiskMinder database.

USERKNOWN

No

UNKNOWNUSER

Yes

DeviceID does not exist in the RiskMinder database.

DEVICEIDCHECK

No

UNKNOWNDEVICEID

Yes

MFP does not exist in the RiskMinder database.

SIGMATCH

No

MFPMISMATCH

Yes

User is not associated with the DeviceID.

USERDEVICEASSOCIATED

No

USERDEVICENOTASSOCIATED

Yes

Follow these steps:

  1. Log in to the administration console.
  2. In the Rule Configurations Report for all organizations and rulesets, verify whether any of the mnemonics that are listed in the Rule expression column of the report belong to the list of deprecated mnemonics.
  3. If a rule uses a deprecated mnemonic and if you do not want to use the deprecated mnemonic, use the corresponding new mnemonic.

    To modify a rule expression:

    1. Log in to the administration console as the 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 Rules and Scoring Management link.

      The Rules and Scoring Management page appears.

    5. From the Select a Ruleset list, select the ruleset for which this configuration is applicable.

      The configuration information for the specified ruleset appears.

    6. Click the rule that you want to modify.

      The Rule Builder page opens.

    7. Make the required changes in the Rule being developed text field.
    8. Save the changes and close the Rule Builder page.
  4. Migrate the modified rule to the production environment, and then refresh the cache.

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