Performing configuration checks


The pre-upgrade and configuration checks are invoked automatically by the following product installers:

Click here to expand the product list
  • BMC Remedy Action Request (AR) System
  • BMC Atrium Core 
  • BMC Remedy ITSM
  • BMC Remedy ITSM Process Designer
  • BMC Service Level Management 
  • BMC Service Request Management
  • Unified Data Management
  • BMC Remedy Smart Reporting

The installers use the following information to invoke the checks: 

  • The product being deployed 
  • The installer mode: install or upgrade
  • Whether or not the system is a primary server or a non-administrative secondary server

Best practice
BMC recommends that you rely on the installer to run the pre-upgrade checks.

To evaluate configuration settings and the environment outside of an install or upgrade, we encourage you to run configuration checks by running the BMC Remedy Configuration Check utility manually. 

In this topic

Overview of the BMC Remedy Configuration Check utility

Config_Check_Utility_Infographic.png

The output of the BMC Remedy Configuration Check utility is a consolidated report that contains the following details:

Section

Description

 Summary


Name of the check

Components on which the checks are performed.

Type of check (pre-upgrade or configuration check)

Status of the check

Details

Message (Error, Warning, Info)

Hints for the checks that failed

Additional information such as actual value and expected value on the checks that failed

You can view the configuration check report directly from the installer, from the Configuration Check utility interface, from the command line interface, or by opening the HTML report file (\result\configchecheckerOutput.html) in a browser.

Diagnosing and resolving the configuration check results

The following topics list the pre-upgrade and configuration checks, their expected results, and the corrective actions:

Manually running pre-upgrade checks and configuration checks

The following table lists the tasks for running the BMC Remedy Configuration Check utility outside of the installer to perform pre-upgrade and configuration checks.

Tip

For platform components, you must run the checks before installing BMC Remedy AR System and after installing BMC Atrium Core.  

Configuration checks on a single server and in a server group environment

How you run the BMC Remedy Configuration Check utility depends on your environment:

  • Single Server environment — If your environment uses a single BMC Remedy AR System server, run the BMC Remedy Configuration Check utility directly on the AR System server that you use for your data load jobs. Do not run the BMC Remedy Configuration Check utility remotely.

  • Server Group environment — For this type of environment, run the BMC Remedy Configuration Check utility from the server on which escalations are enabled.

    Notes

    • If you configured a designated carte server, you need to address only the error or warning messages that the BMC Remedy Configuration Check utility issues for the Carte server. You can safely ignore the messages issued for the other AR System servers in the group. For more information, see Configuring Data Management: Recommendations 

    • If you configured a default Carte server and are running load balancing in your environment, you must also pay attention to any error or warning messages related to the Pentaho plug-in that the BMC Remedy Configuration Check utility issues for all of the AR System servers in the group.
    • In a server group environment, while upgrading the AR System servers, ensure that you run the BMC Remedy Configuration Check utility before you upgrade any server in the server group.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*