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:
Refer to "Uninstalling RiskMinder" for more information.
Note: For installation instructions, see the CA RiskMinder Installation and Deployment Guide that is shipped with the corresponding release.
This section describes the tasks that you must perform after upgrading to release 3.1.
Follow these steps:
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.
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.
Note: For more information about setting the organization-specific base currency code, see Managing Global Configurations" in the CA RiskMinder Administration Guide.
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:
To modify a rule expression:
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.
The Rules and Scoring Management page appears.
The configuration information for the specified ruleset appears.
The Rule Builder page opens.
Note: For detailed information about migrating a rule to the production environment and refreshing the cache, see the CA RiskMinder Administration Guide.
Copyright © 2013 CA.
All rights reserved.
|
|