BMC Remedy AR System enables you to define global-level and local-level configurations for the settings under Centralized Configuration. When you upgrade to version 18.05, global-level configurations are not set automatically, except for the shared configurations indicated with an asterisk (*).
When you upgrade to version 18.05, you can migrate configurations by using either of the following methods:
- Ensure that all servers in the server group are upgraded to version 18.05
- When you upgrade to version 18.05, you have two versions of AR API JAR file. You must use the arapi91_build004.jar AR API JAR file located at the following location:
- When you are retrieving the configurations that has global-level value set, you must use the Configuration API from the arapi91_build004.jar AR API JAR file. For more information, see in BMC Remedy AR System online documentation.
- If you want to use BMC Remedy AR System version 18.05 with BMC Remedy IT Service Mangement version 9.1.04, you must upgrade to BMC Remedy IT Service Management with version 9.1.04.002 and apply a hotfix.
- Global-level configurations are supported if you upgrade only BMC Remedy AR System to version 18.05 and continue to use the previous versions of BMC Remedy IT Service Mangement.
Migrating configurations by using the Server Group Configuration screen
You can use the Server Group Configuration screen of the Remedy Management Console to set the local-level and global-level configurations. This screen enables you to move an individual setting across local-level and global-level configurations.
For more information about using the Server Group Configuration screen, see in BMC Remedy AR System online documentation.
Migrating configurations by using the CCS Reconciliation utility
The CCS Reconciliation utility (
arccsrecon.sh) can migrate all the local-level configurations to global-level configurations except for plug-in server components. When migrating the configurations, the utility honors the out-of-the-box scope defined for each configuration. For example, if any configuration has a LOCAL_ONLY scope, the utility does not move this setting to the global-level configuration.
The utility sets a effective configuration value based on the following considerations:
- If local-level configuration value for all the components are the same, the utility removes the local-level configuration value and sets global-level configuration value. However, the change occurs only if the the setting does not have LOCAL-ONLY scope.
- If local-level configuration value for all the components are the same and the global-level configuration value is different, the utility updates the global-level configuration value and deletes the local-level configuration value.
Overview of CCS Reconciliation utility
This utility runs in two modes:
Mode Description Reporting mode
This is the default mode. Use this mode if you want to view the settings that are common to the server group.
In this mode the utility performs the following actions:
- Recommends whether you can set global-level or local-level configuration value for a group of settings.
- Gives a report of settings that will be moved to the global-level configurations.
You can analyze the report to identify which settings will change when you run the utility in the Migration mode.
This mode moves the settings across local-level and global-level. If local-level and global-level configuration values are the same, the utility deletes the local-level configuration values.
Best practiceBefore you run the utility in migration mode, we recommend taking backup of existing configurations. You can take the database backup or you can use the Backup button on the Server Group Configuration screen.
The utility provides help for all parameters you are using in the command.
- You can access logs generated by this utility at the following location:
- This utility does not process
com.bmc.arsys.pluginServercomponent type. Use the Server Group Configuration screen to configure settings for this component. For more information, see in BMC Remedy AR System online documentation.
To migrate configurations using the CCS Reconciliation utility
This utility (arccsrecon.bat or arccsrecon.sh) is available in the <AR Install Dir>/<artools> folder. Use the following command and its options to run the utility:
- Go to the command prompt.
Run the utility in the report mode to produce the report.
arccsrecon [-u] [-p] [-a] [-x] [-t] [-timeout] [-mode] [-reportPath] [-d] [-type] [-c] [-e]
Review the report and then proceed to run the utility in the Migration mode.
CCS Reconciliation utility options
The following table describes the
arccsrecon command options, which can be used in any order in the command.
|Name that identifies the user account for the AR System server|
Password for the user account
If the user account has no password, use
Name of the external authentication string or Windows NT domain
This option is related to the Login window's Authentication field. For more information, see in BMC Remedy AR System online documentation.
|Name of the server to connect to.|
TCP port number to connect to
If the port number is unknown, use
Time, in seconds. Specify API timeout values. The format is as follows:
The default values for
Note: You must specify all three values even if you want to set a single timeout value.
For example, if you want to set the Long timeout value to 600 seconds, use the following command:
|Mode (report or migrate) to run the utility. The default mode is report.|
Path of the file where the utility generates a report based on the component type.
Note: If you do not specify the report path, the report is generated in the directory from where you are running the utility.
For example, <current dir>/ccs_reports/CCSReport_<current time stamp>.csv
Flag to indicate whether to delete setting from the local-level configuration or not.
0— Do not delete (Default)
Type of settings that needs to be considered.
0— NON_LOCAL_ONLY (Default)
Comma-separated list of component types for which you want to run this utility.
Note: Use this flag if you want to use this utility for specific components. If you do not specify this flag, the utility processes all component types that are available in your environment.
|Comma-separated list of component types that you want this utility to ignore.|