Previous Topic: Configuring RiskMinder PropertiesNext Topic: Enabling the RiskMinder Model

CA RiskMinder Administration Guide › Managing Global Configurations › Configuring RiskMinder Properties › Configuring RiskMinder Properties at the System Level

Configuring RiskMinder Properties at the System Level

In addition to the organization-specific RiskMinder configurations described in Configuring RiskMinder Properties, a GA can configure certain parameters at the system level.

To configure RiskMinder properties at the system level:

  1. Ensure that you are logged in as a GA.
  2. Activate the Services and Server Configurations tab.
  3. Click the RiskFort option on the submenu of the tab
  4. Under General RiskFort Configurations section on the side-bar menu, click the Miscellaneous Configurations link to display the page.
  5. Specify the parameters that the GA can configure at the system level, as described in the following table.

Parameter

Default Value

Description

Next Action Date Cut-Off for Including a Case in Queue Rebuild (in Seconds)

1800

The duration before a case is added to the Queue rebuild.

Number of Records to Be Fetched in One Chunk From Database When Exporting Analyze Transactions Report (Configure this according to the maximum heap memory available on the application server.)

5000

If the number of records to export is very high, The RiskMinder application fetches datasets in chunks of small sizes to ensure that the application server does not run out of memory. If the application server has sufficient heap memory available, you can increase this value so that the RiskMinder application makes fewer number of queries to the database. This results in improved performance.

Maximum Duration for Search on Analyze Transaction Screen (in Days)

180

Maximum duration for which search is allowed in the Analyze Transaction screen.

Frequency of Automatic Queue Rebuild Schedule (in Seconds)

1800

Frequency at which the case scheduler automatically rebuilds Queues.

Note: The other parameters are described in the previous topic.

  1. Refresh all deployed RiskMinder Server instances.

    See "Refreshing the Cache" for instructions on how to do this.