Preupgrade checks and configuration checks
The following topics are provided:
Overview of the BMC Remedy Configuration Check utility
Use the Configuration Check utility to perform the following type of checks:
- Pre-upgrade checks, before you upgrade any or all components in the BMC Remedy IT Service Management (ITSM) Suite environment
- General configuration checks on your system, before you install any or all components in the BMC Remedy ITSM Suite environment
You can perform pre-upgrade checks and configuration checks on the following components:
- BMC Remedy Action Request (AR) System
- BMC Atrium Core
- BMC Remedy ITSM
- BMC Service Request Management
- BMC Service Level Management
- BMC Remedy ITSM Preconfigured Stack Installer
- Unified Data Management
The output of the BMC Remedy Configuration Check utility is a consolidated report that contains the details of the following information:
| Summary||Name of the check|
|Components on which the checks are performed.|
Type of check (pre-upgrade or configuration check)
|Status of the check|
|Error or warnings||Error message for the checks that failed|
Hints for the checks that failed
|Additional information like actual value and expected value on the checks that failed|
You can view the configuration check report from the GUI, from the command line interface, or by opening the HTML report file (\result\configchecheckerOutput.html) in a browser.
Performing pre-upgrade checks and configuration checks
The following table lists the tasks for using the BMC Remedy Configuration Check utility to perform pre-upgrade and configuration checks.
Obtain the BMC Remedy Configuration Check utility
The configcheckerversionNumber_buildNumber.zip file is bundled with the BMC Remedy AR System installer. For information about how to obtain the files that you need for installation, see in the BMC Remedy AR System documentation.
Note: Ensure that the value of JAVA_HOME is set correctly. Use Java 1.6 or later.
(Optional) Set the configuration check preferences
Before you run the BMC Remedy Configuration Check utility, you can optionally set the following preferences:
|3.||Run the Configuration Check utility|
You can run the BMC Remedy Configuration Check utility in one of the following modes:
|4.||View the log files|
When you run the BMC Remedy Configuration Check utility, a log file is generated and placed in ./configchecker/Logs. Logs can be generated at the Info (default) or Debug level.
For more information, see Viewing configuration check log files and changing logging level.
|5.||View the configuration check reports|
After you run the BMC Remedy Configuration Check utility, it generates a consolidated HTML report from the configuration check result file (configcheckResult.xml). The utility generates a single report for all the components in the BMC Remedy ITSM suite environment that were selected for performing the check.For more information about locating and understanding the configuration check report, see Viewing configuration check reports.
Understand the configuration checks and results
You can run the configuration checks for the various components in the BMC Remedy ITSM Suite environment. The following topics list the pre-upgrade and configuration checks, their expected results, and the corrective actions:
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 Configuration Check utility remotely.
- Server Group environment — For this type of environment, run the BMC Remedy Configuration Check utility from the server in the group on which escalations are enabled. The utility runs against all of the servers.
- If you configured a default 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.
- 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.