Tomcat not fully functioning after vCenter install

[ProjecktMayh3m]

I'm running into some issues getting the Orchestrator database setup (http://communities.vmware.com/message/1775113#1775113), but I think I've got bigger issues.

I can browse to http://localhost:8080 but as soon as I try starting the Tomcat Manager (localhost:8080/manager/html) I get a HTTP 404 error.

http://localhost:8443 returns a page, but it is only a few random ASCII characters.

any thoughts?

[ProjecktMayh3m]

I'm nearly done with my first Orchestrator configuration, but am stuck at the last step and I think it is still related to Tomcat. I've created a new vCenter Server connection, but get a 404 not found error:

Error connecting to: https://hostname:443/sdk

My browser is prompted to accept the self signed SSL certificate, but I immediately get a 404 when trying to access "/sdk". If I turn off SSL and browser to it on port 80, I get the same thing.

As previously mentioned, I can't get the Tomcat Manager to pull up either. It also presents a 404.

[AureusStone]

Strange.

When you are adding the vCenter server to Orchestrator are you using an account with full rights?

I don't think you should be able to browse to https://pcac1pap01.core.ind:443/sdk.  Can you browse to https://pcac1pap01.core.ind:443/mob that is usually a good test to see if the connection is working.  Use the same account to connect to mob, as you are using to connect to your vCenter server in Orchestrator configuration.

Are you able to import your SSL certificates under Network->SSL Certificate?

Could you possibly attach a screenshot of the information you are entering in to the "New vCenter Server Host" wizard?

[ProjecktMayh3m]

1)  I *can* browse to https://localhost/mob. Although I'm not quite sure what this proves or disproves. I still can use the Tomcat Manager. Many of the links on the default Apache page don't work. Status, Tomcat Manager, Tomcat Documentation, etc.... most of the local pages.

2) The SSL cert imports fine. No problems.

3) Attached is a screenshot. I can successfully use the "Connection test"... I can also successfully, fail authentication (oxymoron).

Soooo... stupid question now. All of the install documentation I have for Orchestrator stops at the vCenter Server. I can't seem to get the Orchestrator client to connect to anything. I'm pointing it to the localhost (vCenter Server) via the machines IP and I've tried a bunch of different credentials. No go. What's the next step now that vCenter Orchestrator Configuration gives me a "green light" on everything?

Thanks for the noob patience....

[AureusStone]

I assume if you ping the vCenter server with the short name it works fine?  I use the FQDN, but short name should be fine as long as DNS can resolve the full name.

Also can you try using the option "Share a unique session" and reenter your username and password

Have you tried restarting the service "VMware VirtualCenter Management Webservices" on your vCenter server.

Also have a look in your Tomcat logs.

\\VMware\Infrastructure\tomcat\logs

[AureusStone]

Also to connect using the orchestrator.  Host name should be the FQDN of the Orchestrator server.

Username should be in the form of username@domain

Make sure the user you are logging in with is in the VCO administrators group.

[ProjecktMayh3m]

I changed my login credentials to the user@domain format and got in to the Orchestrator Client.

A bit disappointed. I expected vCenter to be more like MS SCVMM, but I guess I don't have the right licenses. A call to my sales engineer tomorrow is in order.

Thanks for your assistance.