Previous Topic: Using the arrfclient Tool to Refresh Server InstancesNext Topic: Shutting Down a Server Instance

CA RiskMinder Administration Guide › Managing RiskMinder Server Instances › Updating Server Instance Configurations

Updating Server Instance Configurations

You can update the instance attributes, logging configurations, and database configurations for the RiskMinder Server and Case Management Queuing Server instances.

To update instance-specific configurations:

  1. Ensure that you are logged in as the MA.
  2. Activate the Services and Server Configurations tab in the main menu, and ensure that the RiskFort tab in the submenu is active.
  3. Under the Instance Configuration section, click the Instance Management link to display the page.
  4. Click the link corresponding to the instance whose configuration you want to update.

    The page to update the instance-specific configuration appears.

  5. In the Instance Attributes section:
    1. Select the check box to Change the Instance Name of your RiskMinder Server or Case Management Queuing Server instance.
    2. Specify name for the instance in the New Instance Name field.
  6. In the Logging Configuration section, specify values as described in the following table.

Field

Description

Transaction Log Directory

The directory to store the transaction log files. The path can be an absolute path or relative to ARCOT_HOME.

Rollover After (in Bytes)

The maximum number of bytes the log file can contain. When the log files reach this size, a new file with the specified name is created and the old file is moved to the backup directory.

Transaction Log Backup Directory

The backup directory to store the older transaction log files. The path can be an absolute path or relative to ARCOT_HOME.

Log Level

The severity level of the logged entry. Fatal, WARNING, INFO, and DETAIL are the supported levels in decreasing order of severity.

See "Supported Severity Levels" in appendix for more information.

Log Timestamps in GMT

Select this option if you want to time stamp the logged information using GMT.

RiskMinder enables you to either use the local time zone or GMT to timestamp the logged information.

Enable Trace Logging

An additional logging flag that logs the Entering and Exiting log for each function called during processing. By default, this flag is disabled. Enabling this flag logs huge amount of data for debugging. You must not enable this flag in production unless advised by CA Support.
  1. In the Database Configurations section, specify values as described in the following table.

Field

Description

Minimum Connections

The minimum number of connections that will be created between RiskMinder Server and the database.

Maximum Connections

The maximum number of connections that can be created between RiskMinder Server and the database.

Increment Connections by

The value by which to increment the connections when all database connections in the pool are exhausted and used by the existing threads, and if any of the threads requests for a new database connection.

Monitor Thread Sleep Time (in Seconds)

The time interval after which the database monitor thread polls the database to check if the database is active and functional.

Monitor Thread Sleep Time in Fault Conditions (in Seconds)

Same as Monitor Thread Sleep Time. But this value is used only when the database monitor thread detects any failure. This value must be less than the Monitor Thread Sleep Time because polling must be done at frequent intervals in the case of any failure.

Log Query Details

When enabled, this option logs all the Oracle, MS SQL, or MySQL database queries executed by the Server. By default, this option is disabled and must be enabled only when debugging is required as in the case of Enable Trace Logging.

Monitor Database Connectivity

If this option is enabled, the Server creates the database monitor thread. Else, database monitoring is disabled.

Auto-Revert to Primary

When the connection to the primary database fails, the Server falls back to the backup database. If this option is enabled, the Server automatically reverts to the primary database when it is up and running.
  1. Click Save to save your changes.
  2. Refresh or restart your server instance depending on the parameters that you have updated.

    For instructions on how to do this, see "Refreshing a Server Instance" and "Restarting a Server Instance".