Installing BMC Configuration Drift Management
Important
Drift Management has been deprecated from BMC CMDB. The documentation provided for Drift Management is also deprecated and provided for information only.
See Deprecated features.
The BMC Configuration Drift Management (Drift Management) application runs on the BMC Remedy Action Request (AR) System platform and consumes configuration data stored in the BMC Atrium Configuration Management Database (CMDB) product.
BMC Configuration Drift Management focuses on audit, verification, and management of infrastructure changes ("drifts") in your datacenter IT environment.
BMC Configuration Drift Management also integrates with other business processes, such as Change Management and Incident Management, to provide the initial steps towards the automation of datacenter operations. Integration with Change Management links changes in the datacenter environment to approved change requests.
The BMC Configuration Drift Management installation comprises the following stages:
Stage 1: Perform pre-installation procedures for BMC Configuration Drift Management
Stage 2: Install BMC Configuration Drift Management
Stage 3: Perform post-installation procedures for BMC Configuration Drift Management
Stage 1: Perform pre-installation procedures for BMC Configuration Drift Management
Step | Action | Additional information |
|---|---|---|
1. | This allows you to restore AR System to its preinstallation state if you encounter problems. | |
2. | Activate the licenses for all BMC applications that you need to work with Drift Management. | License BMC Atrium CMDB, Change Management, Incident Management, Flashboard Server, and so on, before you install them. Ensure that you apply all the licenses you need. |
| 3. | In Windows 2003 environments, you get an error if the framedyn.dll file is not in the system directory. As a result, the installer cannot capture available memory. To fix the problem, Microsoft has published a Knowledge Base entry and workaround to replace the missing framedyn.dll file. | |
| 4. | Verify the amount of TEMP space needed by the installer. | The Drift Management installer needs to use a large amount of disk space at initialization time, several times larger than the space required by the installed Drift Management application. This is because the installer self-extracts its contents to a temporary directory before it can run. The location of this temporary directory is dependent on the underlying operating system. |
| 5. |
Best practice When installing the application on Linux, we recommend that you perform the installation as a root user. However, you can perform the installation as a non-root user. | |
| 6. | Handle issues with installing Drift Management on an Oracle database. | If you are installing Drift Management on an AR System server with an Oracle database, the installation sometimes stops due to the BMC Remedy Action Request (AR) System server timing out. |
Stage 2: Install BMC Configuration Drift Management
| Step | Action | Additional information |
|---|---|---|
| 1. | You must run the installations from the server that is running BMC Remedy AR System and be logged in to that server with sufficient administrator privileges (or non-root for Linux). Note: You can use any of the described methods to perform the installation. | |
| 2. | Install Drift Management with the CLI installer | |
| 3. |
Stage 3: Perform post-installation procedures for BMC Configuration Drift Management
| Step | Action | Additional information |
|---|---|---|
| 1. | Perform post-installation procedures for BMC Configuration Drift Management | Perform these activities to ensure that the application is activated and runs as expected by your user community. You must download and apply the latest patches (when they become available). |
Comments
Log in or register to comment.