This documentation applies to the 8.1 version of Remedy ITSM Deployment, which is in "End of Version Support." You will not be able to leave comments.

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:

AR System Server Configuration check

Description

This check validates the following:

  • That escalations are enabled.
  • That the maximum number of filters (Filter-Max-Total) is set to 500000.
  • That the maximum stack size of filters (Filter-Max-Stack) set to 10000.
  • That a private RPC is set in the plug-in configuration file (pluginsvr_config.xml) for the Command Automation Interface (CAI) plug-in. If a private RPC is set, the utility checks the ar.cfg (ar.conf) file for a definition of the private queue.
Type Configuration check
Check / Expected Result

The following validations are performed:

  • If escalations are disabled, in single server environment, following error message is displayed:
    Escalations are disabled  on localhost: <hostname>
  • If the maximum number of filters is not set to 500000 (Filter-Max-Total is less than 500000), following error message is displayed:
    Filter-Max-Total:<current value>, is set less than 500000.
  • If the maximum stack size of filters is not set to 10000, following error message is displayed:
    Filter-Max-Stack:<current value>, is set less than 10000.
  • If the CAI plug-in configuration does not have a private RPC, following informative message is displayed:
    For CAI Plugin private RPC queue make sure enough threads are allocated.
  • If the private RPC for CAI plug-in is set in the plug-in configuration file (pluginsvr_config.xml), but a private queue is not defined in the ar.cfg (ar.conf) file, following error message is displayed:
    Private-RPC is configured in pluginsvr_config.xml but not in ar.cfg (ar.conf) for CAI plugin: <RPC port number>
Corrective Actions Following are the corrective actions:
  • Enable escalations, if they are not already enabled.
  • Set the maximum number of filters to 500000.
  • 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 ar.cfg (ar.conf) file, provide the definition for the private RPC queue in the ar.cfg (ar.conf) file. 

Remedy App Server Password check

Description This check validates if the BMC Remedy Configuration Check utility can communicate with the BMC Remedy AR System server using the password provided for members of the server group.
Type Configuration 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, following message is displayed:
The check could not verify the password for: 'Remedy Application Service' on '<hostname>' : <full error message>.

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

Data Management Load File Path check

Description

This check validates the following:

  • That the Data Management load file path is correctly set in the SYS:System Setting form.
  • That the BMC Remedy Configuration Check utility can write to the directory specified in the path.
Type Configuration check
Check / Expected Result

 Following validations are performed:

  • If the Data Management load file path is not set in the SYS:System Setting form, following error message is displayed:
    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, following error message is displayed:
    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, following error message is displayed:
    The check cannot read or write to the Data Management Load Path: '<file path>'.
Corrective Actions

Following are the 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:

  • KA376995
  • KA388875
  • KA387027

UDM Plugin Configuration check

Description

 This check validates the following:

  • That 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.
  • That in a single server environment, Server-Connect-Name is present in the UDM:Config form
  • That in a server group environment:
    • The UDM:Config form contains an entry for each AR System server in the group.
    • Escalations are enabled on at least one of the AR System servers in the group.
Type  Configuration check
Check / Expected Result

 Following validations are performed:

  • If the Carte server is down, following error message is displayed:
    Connection failed to Carte server: <hostname> : <port num>.
  • In a single-server environment, if Server Connect Name is missing in the UDM:Config form, following error message is displayed:
    Server Connect Name '<hostname>' is missing in UDM:Config form.
  • In a server-group environment:
    • If an entry for a server group member is missing in the UDM:Config form, following error message is displayed:
      Server group member '<server group member>' is missing in UDM:Config form.
    • If the ranking form is not configured for Escalations and escalations are disabled on all members, following message is displayed:
      Escalations are disabled on all the server group members.

Corrective Actions Following are the corrective actions:
  • Ensure that the Carte server is running.
  • In a single server environment, ensure that the Server Connect Name is present in the UDM:Config form.
  • In a server group environment:
    • Ensure that escalations are enabled on at least one of the AR System servers in the group.
    • Ensure that the UDM:Config form contains an entry for each server in the server group.

For more information about using the BMC Remedy Configuration Check utility for UDM and error messages, see Checking the Data Management environment: version 8.1.02 and later .

Related Topics

BMC Remedy AR System checks

BMC Atrium Core checks

BMC Remedy ITSM checks

BMC Service Level Management checks

BMC Service Request Management checks

BMC Remedy ITSM Preconfigured Stack Installer checks

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

Comments