Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Deployment

When the software arrives, several procedures must be performed to deploy the software, as indicated in the following table:

Procedures for deploying software

Procedure

Description

Managing the deployment process

BMC provides several mechanisms to manage the deployment of the software. You can use BMC Change Management to manage the deployment of software into the IT infrastructure as described in Deployment milestone - Rolling out the release to the business. BMC Change Management tracks the tasks involved in deploying the software, and can help you understand the risks or dependencies on the software. BMC also provides solutions to manage the actual deployment.

Deploying the software to existing systems in the IT infrastructure

BMC Configuration Automation for Clients can manage the deployment of software to existing desktops. It uses policies to enforce that the software is deployed only to the systems entitled to have the software.

Managing the "bare metal" provisioning of new systems

You can use BMC BladeLogic and BMC Atrium Orchestrator to manage the bare metal provisioning of systems. BMC Atrium Orchestrator integrates with BMC Change Management to take information about the systems that are being deployed. BMC Atrium Orchestrator works with BMC BladeLogic and with BMC Configuration Automation for Clients to deploy the appropriate software packages to the system.

Accurately populating data into BMC Atrium CMDB

After the software is deployed, BMC discovery products, such as BMC Configuration Automation for Clients and BMC Atrium Discovery and Dependency Mapping (BMC Atrium Discovery), can find the software deployed on the IT infrastructure and populate the data into BMC Atrium CMDB. For information, see the BMC Configuration Automation for Clients Configuration Discovery Integration for CMDB Implementation Guide and CMDB synchronization.

As part of this process, data is normalized and reconciled, as described in Normalizing data and Reconciling data.

Accurately connecting the software represented in BMC Atrium CMDB to the software license certificate that represents the license agreement for that software

BMC Asset Management provides dynamic mechanisms to connect the software that has been deployed and represented in BMC Atrium CMDB. License certificates provide a definition of how to find the software in BMC Atrium CMDB and leverage information from the DML, so that the searches are performed using a consistent, normalized set of data. The license engine uses this information to query BMC Atrium CMDB to find the new or updated software that has been deployed, and to connect that software to the appropriate license certificates. If deployed software cannot be related to a certificate, it is treated as an exception for the software asset manager to evaluate and determine the appropriate action.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments