This section describes how to set up BMC BladeLogic Server Automation in a VMware vSphere environment.
To set up BMC BladeLogic Server Automation in a VMware vSphere environment, you:

• install a special vCenter agent on a vCenter server
• add the vCenter server to the BMC BladeLogic Server Automation console

• use the BMC BladeLogic Server Automation console to perform configuration tasks that complete the setup.

  Warning

  Note

  This document uses VMware vCenter and VMware Virtual Center interchangeably.

Step 1: Review minimum requirements for VMware environments

This section describes the minimum requirements for setting up BMC BladeLogic Server Automation in VMware environments.

System requirements

To employ BMC BladeLogic Server Automation in a VMware vSphere virtual environment, you must have the following minimum configuration:

• ESX Host (version 3.0, 3.5, 3i, 4.0 and 4i)
• vCenter Server (vSphere versions 2.5, 4, and 4.1)

Required access and privileges

Application Server

The Application Server requires access to the web service on the target (the vCenter server).

Agent

The agent requires administrative privileges. The Exports file should contain an entry such as '* rw, user=administrator'.

vCenter privileges

BMC BladeLogic Server Automation requires, at the minimum, Read Only permission for all objects in vCenter. BMC BladeLogic Server Automation requires administrative permissions for any areas to which you want to deploy, or those that you may want to modify.
For example, if you want to deploy new VMs for a specific cluster, then you would require:

• Read only permissions for the entire vCenter
• Administrative privileges for the cluster (and any additional permissions, to create VMs on the cluster)

vCenter user privileges

The vCenter user should have the privileges defined in the following table.

Privileges for vCenter user

Entity	Privileges for role
VMs	All privileges
Host/Cluster/Resource pools/Data Center/Folder	Read access to all properties/configuration information for all the entities Create VMs privilege on the required set
Storage	Read access to all properties/configuration information for all the entities Create VMs on the required storages
Network	All privileges, for deployment and modifications

Step 2: Install the vCenter server agent

1. Install the WindowsAgent VC on the vCenter server, as described in Installing RSCD agents. Be sure to install the WindowsAgent VC that is specifically designated for use with a vCenter server.
2. Open the c:\windows\rsc\exportsfile and edit the last line so it reads:
   • rw,user=administrator*
3. Open a command window and run the following command from the system where NSH is installed:
   agentinfovCenterServerHostname
    The agentinfo command displays various types of information, including a listing for operating system. The operating system should be a Microsoft Windows operating system and the letters "VC" should be appended somewhere on the same line, which signifies that it is a Windows machine with vCenter running on it.
4. License the agent, as described in Licensing agents.

Step 3: Add the vCenter server to BMC BladeLogic Server Automation

 To add the server to the console, complete the following steps:

1. From within the BMC BladeLogic Server Automation console, add the vCenter server as a managed server to a server group (right-click a server group and select Add Server ).
2. Select Configuration > Property Dictionary View.
3. Browse the Built-in Property Classes > Connection class.

4. Click the Instances tab.
    A Connection instance is automatically created with the name Connection_nameofVCenterEnrolled, where nameofVCenterEnrolled is the name of the vCenter server.This new instance contains the connection details for the vCenter server.

   Warning

   Note

   If a Connection instance is already associated with the Virtualization instance then a new instance is not automatically created.

5. Set the following properties for the new Connection instance and save the instance:

Property	Value
CONNECTION_URL	Enter the web URL of the SDK of the vCenter server (for example, *https://*{_}vCenterServerName{_}*/sdk\* (https://*_vCenterServerName_*/sdk*) ). Note : This name should match the VMware vCenter server name registered in BMC BladeLogic Server Automation.
CONNECTION_USER	Enter the name of an administrator of VMware vCenter, or another user with required privileges.
CONNECTION_PASSWORD	Enter the password of the user that is mentioned in the above property.

To distribute the vCenter configuration object on the vCenter server, complete the following steps:

1. From the BMC BladeLogic Server Automation console, navigate to the Jobs folder.
2. Right-click a job group and select New > Administration Task > Distribute Configuration Objects.
3. Provide a name for the Job and click Next.
4. Expand the Global Configuration Objects list, select the VMware vCenter Server object, and add it to the Selected Configuration Objects section. Click Next.
5. On the Targets panel, select the vCenter agent installed on the vCenter host.
6. Click Finish, and execute the job.
   For details, see Distributing configuration objects.
   You can now use the BMC BladeLogic Server Automation console to Live browse server and access the Virtual Center node.
   For more information on adding a server and setting its properties, see the BMC BladeLogic Server Automation User Guide and the BMC BladeLogic Server Automation online help.