rameuniver
Enthusiast
Enthusiast

unable to integrate vcenter orchestrator with web client

I am unable to see the Orchestrator Server on web client

vCenter Server IP : 192.168.95.233

Orchestrator: Installed along with the vCenter

Please find the attached image

25 Replies
Margarita
VMware Employee
VMware Employee

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

0 Kudos
rameuniver
Enthusiast
Enthusiast

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.

1.jpg

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.

3.JPG

From the Managed Object Browser

4. Start the Orchestrator server service.

0 Kudos
igaydajiev
VMware Employee
VMware Employee

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 :

VMware vSphere 5.1

The most importatnt is to verify that extension list contains only the  expected vco registered and it is registerd with correct IP.

0 Kudos
iiliev
VMware Employee
VMware Employee

Also, there are some integration tips (prepared by Christophe Decanini) that could be helpful:

http://communities.vmware.com/docs/DOC-20368

rameuniver
Enthusiast
Enthusiast

The following is the screenshot from MOB

pastedImage_1.png

0 Kudos
rameuniver
Enthusiast
Enthusiast

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.

0 Kudos
iiliev
VMware Employee
VMware Employee

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?

0 Kudos
rameuniver
Enthusiast
Enthusiast

Can you guide me how to check logs?

0 Kudos
iiliev
VMware Employee
VMware Employee

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

0 Kudos
rameuniver
Enthusiast
Enthusiast

From Managed Object Browser

1.JPG

0 Kudos
r0ck
Enthusiast
Enthusiast

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?

0 Kudos
iiliev
VMware Employee
VMware Employee

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.

r0ck
Enthusiast
Enthusiast

thank you for claification.

0 Kudos
HariRajan
Hot Shot
Hot Shot

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

Thanks & Regards in Plenteous . Hari Rajan
0 Kudos
vfk
Expert
Expert

This could be one of two things:

  1. Some times vCenter Orchestrator is not registered with vCenter so you will have to manually add it, this is the vsphere web client.
  2. This could also authorisation issue, you don't have the appropriate permission for vCenter Orchestrator, if you login with the admin account you have used to configure orchestrator then everything should appear.  Check C:\Program Files\VMware\Infrastructure\Orchestrator\app-server\logs\server.txt file for any authorisation issues.

--- If you found this or any other answer helpful, please consider the use of the Helpful or Correct buttons to award points. vfk Systems Manager / Technical Architect VCP5-DCV, VCAP5-DCA, vExpert, ITILv3, CCNA, MCP
0 Kudos
nassar3
Contributor
Contributor

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.

0 Kudos
vfk
Expert
Expert

Here are the steps:

  1. Login into vSphere web client
  2. On homepage click on vCenter Orchestrator
  3. On the navigation menu on the left, clock Orchestrator Server
  4. Select manage tab, you should server listed if configured, it possibly it is not correct dns name.
  5. Edit configuration and type fqdn or IP and test connection, if you have correct permissions everything should just click into place.
--- If you found this or any other answer helpful, please consider the use of the Helpful or Correct buttons to award points. vfk Systems Manager / Technical Architect VCP5-DCV, VCAP5-DCA, vExpert, ITILv3, CCNA, MCP
malhi_o
Enthusiast
Enthusiast


Two Certificates should be imported from vCenter

https:// yourvCenterIP.local

https:// YourvCenterIP.local:7444 for SSO

ivand
VMware Employee
VMware Employee

vCO should be configured with SSO as authentication provider. Without this you cannot use vCO in vSphere Web Client