Hi,
Although you installed vCO along with vCenter Server, there are some additional configuration steps that you have to perform to see vCO in the vSphere Web Client:
1. Start the Orchestrator Configuration Service and log in to the Orchestrator configuration interface.
2. Verify that the correct IP is selected from the IP address drop-down menu on the Network tab.
3. On the vCenter Server tab, verify that your vCenter Server plug-in is properly configured, provide the user name and password of a user who has the privileges to manage vCenter Server extensions and save the changes.
4. Start the Orchestrator server service.
Hope this helps,
Margarita
1. Start the Orchestrator Configuration Service and log in to the Orchestrator configuration interface.
2. Verify that the correct IP is selected from the IP address drop-down menu on the Network tab.
3. On the vCenter Server tab, verify that your vCenter Server plug-in is properly configured, provide the user name and password of a user who has the privileges to manage vCenter Server extensions and save the changes.
From the Managed Object Browser
4. Start the Orchestrator server service.
Could you also verify that the vCO is registred correctly in VC.
This can be done using the managed object browser (vc_ip/mob)
More details can be found here :
The most importatnt is to verify that extension list contains only the expected vco registered and it is registerd with correct IP.
Also, there are some integration tips (prepared by Christophe Decanini) that could be helpful:
The following is the screenshot from MOB
Forgot to say, we running two vcenter A & B in linked mode. So vCenter B (Where Orchestrator is installed) is dependent on the vCenter A single sign on.
OK, so the extension is there. Could you click on it, then click on 'server' property, and then verify that 'url' property points to the correct vCO REST URL. In your case, it should be something like 'https://192.168.95.233:8281'
Are there any errors/exceptions in the vCO or web client logs?
Can you guide me how to check logs?
By default, the log files can be found at:
vCO server log -> C:\Program Files\VMware\Infrastructure\Orchestrator\app-server\server\vmo\log\server.log
Web Client log -> C:\ProgramData\VMware\vSphere Web Client\serviceability\logs\vsphere_client_virgo.log
From Managed Object Browser
i have the same problem, but my vcenter server is not in linked mode.
have anyone runnging the web client and orchestrator together correct with ldap credentials configured?
Both vCO server and vSphere Web Client need to be configured with SSO.
If vCO server is configured with LDAP, it won't be able to validate SAML tokens sent by Web Client, and as a result communication between vCO and Web Client (calls to vCO REST API) will fail.
thank you for claification.
It may help you if you successfully integrate SSO for authentication .
For this in VCO configuration manager you need to go to Network -->> SSL Trust Manager
1. Log in to the Orchestrator configuration interface as vmware.
2. Click Network.
3. In the right pane, click the SSL Trust Manager tab.
4. Load the vCenter Single Sign On SSL certificate from a URL or a file.
5. Import from URL
6. Type the URL of the vCenter Single Sign On server:
https://your_vcenter_single_sign_on_server_IP_address:7444 or your_vcenter_single_sign_on_server_IP_address:7444
Next select Authentication
Select Authentication mode SSO
administrator@vsphere.local
SSO password .
please check this work for you
This could be one of two things:
Is there any documentation available on how to register Orchestrator with vCenter manually, or can anyone offer to explain how to do it? I have followed all procedures I can find for doing the integration, but the Orchestrator extension is still not listed in the managed object browser. Thank you for any help.
Here are the steps:
vCO should be configured with SSO as authentication provider. Without this you cannot use vCO in vSphere Web Client