Upgrading an existing BMC Server Automation UCS Manager environment

To upgrade an existing environment, you must perform the following tasks:

1. Upgrade all system components  from previous versions to the current version, including:
   • BMC Server Automation Application Server
   • BMC Server Automation Console
   • RSCD agent on the BMC Server Automation UCS Manager server
2. Distribute configuration objects to the BMC Server Automation UCS Manager server. Use the following procedures:
   1. Deregister old custom configuration objects on the BMC Server Automation UCS Manager server.
   2. Distribute new configuration objects to the BMC Server Automation UCS Manager server.
   3. Restart the RSCD agent on the BMC Server Automation UCS Manager server.
   4. Optionally, remove the old configuration objects from the BMC Server Automation Object Dictionary.

Deregistering configuration objects

To remove custom configuration objects from UCS Manager servers, create and run a Deregister Configuration Object Job. This job removes all implementation files associated with a custom configuration object from the UCS Manager server.

To deregister old configuration objects from the BMC Server Automation UCS Manager server

1. In the console, open the Servers folder.
2. Right-click the name of the BMC Server Automation UCS Manager server and select Administration Task > Deregister Configuration Objects.
   The Distribute Configuration Objects Job wizard opens.

3. In addition to whatever other options you choose, make sure to include the following items:

   Panel	Selection
   General	Specify a name for the job.
   Selected Configuration Objects	Select the Show all configuration object versions option at the top of this panel.
   	Select one of the following objects (whichever one appears in your list): BladeLogic UCS Manager V3 (from version 8.0 SP1) BladeLogic UCS Manager V2 (from version 8.0) BladeLogic UCS Manager v801,000 (from version 8.1)

   For detailed information about Deregister Configuration Object Jobs, see Creating or modifying Deregister Configuration Object Jobs.

Now that you have deregistered the old configuration objects, you can proceed with distributing the new configuration objects.

Deleting objects from the Object Dictionary

The Configuration Object Dictionary retains the object definitions even though you deregistered the objects from all servers. You can remove the older versions of the UCS Manager custom configuration objects from the dictionary.

To delete a custom configuration object from the Configuration Object Dictionary

1. Make sure that the previous version of the UCS custom configuration object is not registered on any server managed by BMC Server Automation. If necessary, execute a Deregister Configuration Objects Job on the server.

2. Make sure that the latest version of any policy-based objects (that is, component templates and server object-based Snapshot and Audit Jobs) do not refer to the custom configuration object that you want to remove. To remove known dependencies, manually open the definition for each policy-based object and delete the dependency.

   Note

   You can skip this step now and wait until the system displays a list of dependencies. See step 5.

3. From the Configuration menu, select Config Object Dictionary View. The Configuration Object Dictionary opens.
4. From the left-most drop-down box in the Config Object Dictionary view, select Server Objects.

5. From the list of server objects, locate the old versions of BladeLogic UCS Manager. Right-click and select Delete Configuration Object. A message prompts you to confirm your action.

   Note

   Make sure that you are not deleting the current version. 

   If there are dependencies on the objects that you try to delete, the Found Dependencies dialog displays the dependent objects. You need to delete the dependencies, as described in step 2.