Previous Topic: Configure the User Store Connection Information

Next Topic: How You Configure CA Access Control for Virtual Environments for SSL Communication

Configure the Connection to the VMware vCenter Server

Configure the connection to VMware vCenter to integrate CA Access Control security features with the managed devices in VMware vCenter Server.

Follow these steps:

  1. From the CA Virtual Appliance Configuration wizard, move to vCenter Connection Configuration.
  2. Complete the fields in the dialog:
    Name

    Defines the name you want to use for the VMware vCenter Connection

    Description

    (Optional) Defines a description for this VMware vCenter Connection

    Server Name

    Defines the DNS name of the VMware vCenter Server you want to manage

    Example: vcenter.company.com

    Username

    Defines the name of a user account with VMware vCenter Server administrative privileges

    Password

    Defines the password of a user account with VMware vCenter Server administrative privileges

  3. Click Next.

    CA Access Control for Virtual Environments validates the settings and continues to the shared secret screen.

  4. Complete the following field:
    Communication Password

    Defines the password used for CA Access Control Enterprise Management Server inter-component communication.

  5. Click Next.

    A summary screen opens.

  6. Review the information and click Finish to complete the wizard.

    CA Access Control for Virtual Environments configures the database and user store for use.

    CA Access Control for Virtual Environments uses the information you specified to try to connect to the VMware vCenter Server. If the information is correct, the connection is set and you can now use VMware vSphere Client to manage your enterprise deployment of CA Access Control for Virtual Environments. If the information is incorrect and CA Access Control for Virtual Environments cannot connect to the VMware vCenter and an error message appears. The message describes the reason the connection could not be established.