Did you run a Distribute Configuration Object Job on your vCenter server? This job adds the vCenter Server configuration object node.
You should also take a look in the installation manual. For version 8.1 (SP2) you should read page 167 and 168.
And did you create the connection instance for the vCenter SDK?
1 of 1 people found this helpful
It seems like you have done step 1 and 2. Work your way down this list and you will be able to manage you virtual environment in no time .
1. Download, install and license the Windows VC Agent on the vCenter Server.
2. Enroll this agent into the appserver.
3. Once the import of the CO and enrollment of the agent are complete, go to a Job Group, right click -> New -> Administration Task -> Distribute Configuration Objects to create a new Distribute CO Job.
4. In the job wizard, give the name of the job, and in the next screen, select the VMware Virtual Center CO from the Global Configuration Objects list. In the following screens, select the target server as the vCenter agent that you have enrolled and execute the job.
5. The job succeeds. (If it does not, make sure that you are executing it against the correct server and also make sure that the agent has the permissions mentioned above)
6. In the RCP Client, go to Configuration -> Property Dictionary. Here browse the Built-in Property Classes -> Connection class.
7. Go to the instances tab and create a new instance. This new instance would be the one that contains the connection details for the vCenter server. Give an appropriate name for this instance.
8. Edit the following Properties here:
CONNECTION_USER - Enter the name of an administrator of VMware vCenter
CONNECTION_URL - Enter the web url of the sdk of the vCenter server. (eg: https://<vCenter-Server-Name>/sdk)
CONNECTION_PASSWORD - Enter the password of the user that is mentioned in the above CONNECTION _USER property.
Save this instance.
9. Now go to the Built-in Property Classes -> Virtualization class.
One can notice that for each vCenter server one has added, there would be an instance already created for it with the same name.
10. Edit the instance for the server you have added above. Notice in the 'VIRTUAL_ENTITY_TYPE' property that BMC BladeLogic has already detected that this is a VMware vCenter Server.
Edit the 'VIRTUAL_ENTITY_CONNECTION' property to point to the Connection instance that we created in the previous steps. Save this instance.
11. Now live browse the server. An additional VMware Virtual Center node is now visible to the user.
12. If all data was entered correctly, when the user clicks on the Virtual Center node, 6 new nodes are brought up below, namely:
13. One can now go ahead and live browse these nodes and perform different actions on these nodes.
Thank you very much for the replies. I had follewed al the steps. jus removed the target and added back in the Distributed CO and ran the job. The node appeared.
I got another issue. Am tying to create virtual machine deploy job. I created a Virtual Guest Package(VGP),configured it and saved. Next step is creating a Virtual Guest Job. I selected the VGP, the TARGET,which is one of the ESX host. In the next step of creating job,we need to select the datastore. It shows an error saying 'Following datastore(s) does not match with the target'. When i browse the datastore, none of the datastores appear. But i could browse the datastore while creating VGP. What might be the reason?Is there any othr configuration that I missed?
Thanks in advance.
A VGP will show all datastores available. You must make sure the ESX target you select actually has access to the datastore you have selected as this will not be the case.
Select a datastore that has your ESX target as a member of that datastore.
Hey.. they are accessable from the ESX host. It works through VI client. Also I tried using the local datastore of the ESX host. Even that gives the same error.
They are either not mapped to the right host or the user you have defined in the connection instance does not have the correct permissions.
I have had similar issue, resolution was to upgrade the VC RSCD agent to the latest with SP3.
Wil SP3 work on the normal BL 8.1.00? Wont there be any mismatch?
Post the output of an agentinfo command ran from the appserver against your vCenter server
And you don’t see the VM Ware object when you live browse the system? Have you tried licensing your agent on the vCenter? I see it is only running on a demo license, and that may be causing an issue.
No, the appserver and VC need to be on the same version afaik. (really it’s the vmware COs that need to match versions)