
VMware vRealize Orchestrator Cookbook
By :

Integrating Orchestrator into the vCenter Web Client enables vCenter Server users to directly run Orchestrator workflows just by right-clicking vCenter objects. The vRA-integrated Orchestrator is already configured with the SSO that vRA uses.
vCO 5.5 (and higher) requires an SSO server 5.5, as it won't work with an SSO 5.1 server.
We need an up-and-running Orchestrator as well as access to vCenter Web Client.
Make sure that you set the Orchestrator Network configuration (see the Configuring the network section in the Important Orchestrator base configurations recipe)
You should be comfortable with using one of the methods described in the Two ways to configure Orchestrator recipe.
You should have an AD group for your vCOAdministrators with at least one user in it. You can use the precreated SSO group [email protected]. The account [email protected] is a member of this group.
Again both configuration methods are shown. Choose the one you're most comfortable with.
If you are using the Orchestrator installation that came with vCenter, you can skip this step.
[IP or FQDN of SSO server]:7444
as the URL and click on Import.[email protected]
).[IP or FQDN of SSO server]:7444
as the URL.[IP or FQDN of SSO server]:7444
as the URL.[email protected]
).The integration of Orchestrator with vCenter Web Client requires us to also configure the vCenter Server plugin.
Wait until the workflow is successfully finished.
In the Web Client only one Orchestrator Server can be paired to each vCenter Server. To configure the pairing, follow these steps:
Since vCenter Server 5.1, vSphere Web Client is (or better, should be) the main method for accessing vCenter. Orchestrator completely integrates with vSphere Web Client, making it possible for Orchestrator workflows to be executed directly from vSphere Web Client.
You can configure which workflows can be run from the vSphere Web Client. We will discuss this configuration in detail in the Orchestrator and vSphere Web Client recipe in Chapter 5, Basic Orchestrator Operations.
Using SSO for Orchestrator login requires that you log in into Orchestrator Client or vSphere Web Client using a user that is a member of the group you defined as vCOAdmins. If you used the [email protected] group, you can add other SSO and AD groups or users to this group via the SSO group membership configuration.
Change the font size
Change margin width
Change background colour