You can configure Orchestrator to connect to your vCenter Server instances for running workflows over the objects in your vSphere infrastructure.
About this task
To manage the objects in your vSphere inventory by using the vSphere Web Client, make sure that you configure the Orchestrator server to work with the same vCenter Single Sign-On instance to which both vCenter Server and vSphere Web Client are pointing. You must also ensure that Orchestrator is registered as a vCenter Server extension. You register Orchestrator as a vCenter Server extension when you specify a user (by providing the user name and password), who has the privileges to manage vCenter Server extensions.
- Log in to the Orchestrator configuration interface as vmware.
- Click vCenter Server, and click the New vCenter Server Host tab.
- From the Available drop-down menu, select Enabled.
This means that you plan to orchestrate the vCenter Server instance.
- In the Host text box, type the IP address or the DNS name of the machine on which the vCenter Server instance you want to add is installed.
- In the Port text box, retain the default value, 443.
- (Optional) Select the Secure channel check box to establish a secure connection to your vCenter Server system.
- In the Path text box, retain the default value, /sdk.
This value is the location of the SDK that you use for connecting to your vCenter Server instance.
- Select the method you want to use for managing user access on the vCenter Server system.
Share a unique session
Creates only one connection to vCenter Server.
In the User name and Password text boxes, type the credentials for Orchestrator to use to establish the connection to the vCenter Server host.
The user that you select must be a valid user with privileges to manage vCenter Server extensions and a set of custom defined privileges. Orchestrator uses these credentials to monitor the vCenter Web service, typically to operate Orchestrator system workflows.
Session per user
Creates a new session to vCenter Server. This might rapidly use CPU, memory, and bandwidth.
Select this option only if your vCenter Server is in an Active Directory domain or if vCenter Server Single Sign-On is enabled.
The user that you select must be a valid user with privileges to manage vCenter Server extensions.
The user account that you select is also used by the policy engine to collect statistical and other data. If the user that you select does not have enough privileges, the policy engine cannot access the necessary parts of the vCenter Server inventory and thus cannot collect the necessary data.
- Click Apply changes.
The URL to the newly configured vCenter Server instance is added to the list of defined hosts.
- Repeat 2 through 9 for each vCenter Server instance.
What to do next
Import the SSL certificates for each vCenter Server instance that you defined.