This documentation supports the 9.1 version of BMC Remedy ITSM Deployment.

To view the latest version, select the version from the Product version menu.

Unified Data Management (UDM) checks

This topic covers information on the checks performed by the BMC Remedy Configuration Check utility for Unified Data Management (UDM). It also describes the expected results of the checks and corrective actions to be taken if a check fails. The following checks are included:

BMC recommends that you run all the pre-upgrade checks before you upgrade to a higher version. If you encounter any error or warning, address the issue as it may prevent a successful upgrade.

Check ARServer Configuration

Description

This check validates the following conditions:

  • Escalations are enabled on at least one of the AR System servers in the ARSystemServerGroupOperationRanking form.
  • The maximum number of filters (Filter-Max-Total) is set to 500000.
  • The Filter_API_Timeout is set to 300 seconds.
  • The asynch_op_api_timeout is set to 300 seconds.
  • The max_params_retries is set to 3.
  • The maximum stack size of filters (Filter-Max-Stack) is set to 10000.
  • A private RPC is specified in the plug-in configuration file (pluginsvr_config.xml) for the Command Automation Interface (CAI) plug-in. If a private RPC is specified, the utility checks the ar.cfg (ar.conf) file for a definition of the private queue. The check validates following in the ar.cfg file:
    • The Port number is 390693.
    • The min thread is 1 and max thread is 6.
TypeConfiguration check
Check / Expected Result
  • If escalations are disabled on all the members in the ARSystemServerGroupOperationRanking form, the check fails and displays an error message:
    Escalations are disabled  on all the server group members.

  • In single server environment, if escalations are disabled, the check fails and displays the following error message:
    Escalations are disabled  on localhost: <hostname>
  • If the maximum number of filters is not set to 500000 (Filter-Max-Total is less than 500000), the check fails and displays the following error message:
    Filter-Max-Total:<current value>, is set less than 500000.
  • If Filter_API_Timeout is not set to 300 seconds, the check fails and displays the following error message:
    Filter-API-Timeout:<current value>, is less than 300
  • If asynch_op_api_timeout is not defined, the check fails and displays the following error message:
    The check could not retrieve the asynch_op_api_timeout in the 
    pluginsvr_config.xml,
    Please define the asynch_op_api_timeout with value 300.
  • If asynch_op_api_timeout is not set to 300 seconds, the check fails and displays the following error message:
    asynch_op_api_timeout:<current value>, is less than 300.
  • If max_params_retires is not defined, the check fails and displays the following error message:
    The check could not retrieve the max_params_retries in the 
    pluginsvr_config.xml,
    Please define the max-params-retries with value 300.
  • If max_params_retries is not set to 3, the check fails and displays the following error message:
    max_params_retries:<current value>, is less than 3.
  • If the maximum stack size of filters is not set to 10000, the check fails and displays the following error message:
    Filter-Max-Stack:<current value>, is set less than 10000.
  • If the CAI plug-in configuration does not have a private RPC, the check displays the following informative message:
    For CAI Plugin private RPC queue make sure enough threads are alocated.
  • If the private RPC for CAI plug-in is specified in the plug-in configuration file (pluginsvr_config.xml), but a private queue is not defined in the ar.cfg(ar.conf) file, the check fails and displays the following error message:
    Private-RPC is configured in pluginsvr_config.xml but not in ar.cfg (ar.conf)
    for CAI plugin: <RPC port number>
    • If a matching port is not defined, the check fails and displays the following error message:

      The check could not retrieve the PRIVATE-RPC-SOCKET from the ar.cfg file.
    • If the values for the minimum and maximum threads are less than the expected values of 1 and 6 respectively, the check fails and displays the following error message:

      You must allocate more threads for the CAI plugin private RPC queue.
Corrective Actions
  • Ensure that escalations are enabled on at least one of the AR System servers in the ARSystemServerGroupOperationRanking form.
  • Set the maximum number of filters to 500000.
  • Set Filter_API_Timeout to the following values:
    • For BMC Remedy ITSM version 9.1 and later, set the value to 300 seconds.
    • For BMC Remedy ITSM versions earlier than 9.1, set the value to 600 seconds.
  • Set asynch_op_api_timeout to 300 seconds.
    • For BMC Remedy ITSM version 9.1 and later, set the value to 300 seconds.
    • For BMC Remedy ITSM versions earlier than 9.1, set the value to 600 seconds.
  • Set max_params_retries to 3.
  • Set the maximum stack size of filters to 10000.
  • In the plug-in configuration file (pluginsvr_config.xml), configure a private RPC for the CAI plug-in.
  • If the private RPC for the CAI plug-in is configured in the plug-in configuration file (pluginsvr_config.xml), but the private queue is not defined in the Centralize Configuration, provide the definition for the private RPC queue in the Centralize Configuration. 
    • Set the value of the Port number as 390693 in the ar.cfg file.
    • Set the min thread to 1 and max thread to 6.

Go to top

Check Remedy Application Service Password

DescriptionThis check verifies whether the BMC Remedy Configuration Check utility can communicate with the BMC Remedy AR System server by using the password provided for members of the server group.
TypeConfiguration check
Check / Expected Result

If the BMC Remedy Configuration Check utility cannot communicate with the BMC Remedy AR System server by using the password provided for members of the server group, the check fails and displays the following error message:
The check could not verify the password for: 'Remedy Application Service' on '<hostname>' : <full error message>.

Corrective ActionsUpdate the password on UDM:RAppPassword form for the suggested server.

Go to top

Check Data Management Load File Path

Description

This check verifies whether the following conditions are met:

The Data Management load file path is correctly set in the SYS:System Setting form.

The BMC Remedy Configuration Check utility can write to the directory specified in the path.

TypeConfiguration check
Check / Expected Result

If the Data Management load file path is not set in the SYS:System Setting form, the check fails and displays the following error message:
Data Management Load Path not set in System Setting.

If the Data Management load file path set in the SYS:System Setting form is invalid, the check fails and displays the following error message:
Can not read or write Data Management Load Path: '<file path>'.

If the Data Management load file path set in the SYS:System Setting form is valid, but the BMC Remedy Configuration Check utility cannot write to the specified directory, the check fails and displays the following error message:
The check cannot read or write to the Data Management Load Path: '<file path>'.

Corrective Actions

If the Data Management load file path is not set or it is set incorrectly in the SYS:System Setting form, set the appropriate file path.

Ensure that the appropriate permissions are set on the shared directory: Run a test again by using the Test button on the SYS:System Setting form, and validate the permissions on the directory. The test should pass.  

For additional information about UDM settings, see the article Remedy 8 - Data Management Settings on BMC Communities, or see the following knowledge articles:

KA000062702

KA000051260

Go to top

Check SQL DB Configuration

Description

This check validates the following attributes of the MS SQL server:

READ_COMMITTED_SNAPSHOT is set to ON.

XACT_ABORT option is OFF.

Note:

This check is specific to Microsoft Windows OS and the MS SQL database.
For other combination of OS and database, the status of the check remains Not run.

Type

Configuration check 

Check / Expected Result

If READ_COMMITTED_SNAPSHOT is ON and XACT_ABORT is OFF, the check is successful.

If READ_COMMITTED_SNAPSHOT is OFF or XACT_ABORT is ON, the check fails.

Corrective ActionsPerform the following corrective actions:

To find the current setting of Read Committed Snapshot, use the following command:
SELECT is_read_committed_snapshot_on FROM sys.databases

where name = 'ARSystem';

If the current setting of Read Committed Snapshot is OFF, turn ON the Read Committed Snapshot setting on the target MSSQL server:

  • Stop the AR System server.
  • Run the following SQL command:
    ALTER DATABASE ARSystem SET READ_COMMITTED_SNAPSHOT ON;
  • Restart the AR System server.

To get the current setting of the XACT_ABORT option, use the following command:
DBCC USEROPTIONS;

If the current setting of XACT_ABORT is ON, set this option to OFF on the target MS SQL server:

  • Stop the AR System server.
  • Run the following SQL command:
    SETXACT_ABORT OFF;
  • Restart the AR System server.

Go to top

Check UDM plugin config

Description

 This check verifies whether the following conditions are met:

The BMC Remedy Configuration Check utility can communicate with the Carte server by opening a socket connection for each entry in the UDM:Config form.

In a single server environment, Server-Name is present in the UDM:Config form

In a server group environment:

  • The UDM:Config form contains an entry for each AR System server in the group.
  • Server-Connect-Name is present in the UDM:Config form.

The check verifies whether the Is Default check box is enabled for the servers configured in the UDM:Config form. If the check box is enabled, the check validates the connectivity to the default server.
Note: If the Is Default check box is not enabled for any servers in the UDM:Config form, the Configuration Check utility verifies the connectivity to non-default servers.

TypeConfiguration check
Check / Expected Result

If the Carte server is down, the check fails and displays an error message.

In a single-server environment, if Server-Name is missing in the UDM:Config form, the check fails and displays an error message.

In a server-group environment:

  • If an entry for a server group member is missing in the UDM:Config form, the check fails and displays an error message.
  • If Server-Connect-Name is not present in the UDM:Config form, the check fails and displays an error message.

If the connectivity to the default or non-default server is not established, the check fails and displays an error message.

Corrective Actions

Ensure that the Carte server is running.

In a single server environment, ensure that the Server-Name is present in the UDM:Config form.

In a server group environment:

  • Ensure that the UDM:Config form contains an entry for each server in the server group.
  • Ensure that Server-Connect-Name is present in the UDM:Config form.


Ensure the connectivity to the default or non-default server by checking:

  • The AR System Server is up and running.
  • You have provided a correct password to log in to the server.

For more information about using the BMC Remedy Configuration Check utility for UDM and error messages, see Running the Configuration Check Utility for UDM .

Related topics

BMC Atrium Core checks

BMC Remedy AR System checks

BMC Remedy ITSM checks

BMC Remedy ITSM Process Designer checks

BMC Service Level Management checks

BMC Service Request Management checks

Was this page helpful? Yes No Submitting... Thank you

Comments