Installing vCO plugin for vCac

[Harkamals]

I am not getting to configure the plugin, anyone can guide ? Essentially it asked for vCac host name and I choose basic authentication with session details and it always throws error validating the certificates.

certificates are good when I Browse through IE.

thanks in advance.

[VirExprt]

Are you able to Import Plugin to the vCO configuration? Please make sure to import vCAC certificate in vCO before performing this action.

While configuring vCAC plugin from vCO client, Make sure that you provide FQDN of the server and do not put HTTP/HTTPS

Wokflow will validate certificate on it`s own.

Hope this could help you fixing your issue.

BR,

MG

[cdecanini_]

Basic Authentication is not supported. You need to use NTLM authentication.

Also if your vCAC was not setup to support https you need to duplicate the "Add a vCAC host workflow" and remove the "Manage SSL certificate" step.

All these issues will be fixed in next release of vCAC / vCAC plug-in for vCO.

[SimonSparksBetf]

Hi Christophe,

When will the next version of the vCAC Plug-in for vCO be available.

We are running vCAC v5.2 and vCO 5.1

Simon Sparks

Betfair

[cdecanini_]

Hi Simon,

I am pushing internally to get an updated public release since I have some nice packages requiring fixes.

You should be able to use the released vCAC plug-in against 5.2 as long as you do not get into the same issues I experienced. If you do you should definitely open an SR which will increase the chances of having an updated release quicker.

Christophe.

[SimonSparksBetf]

I am running the following code and it is not registering the vCAC host it is looking for HTTP and out vCAC is on HTTPS

vCACVcacHostManager.addVcacHost({

  name: "vCAC",

  hostAddress: "vcac.prod.domain.local",

  type: "NTLM",

  sessionMode: "Shared Session",

  username: "service_account_username",

  password: authPassword,

  workstation: "",

  domain: "PROD",

  connectionTimeout: 30.0,

  operationTimeout: 60.0

});

[cdecanini_]

Try to add https:// in front of the hostname

[SimonSparksBetf]

When I add https:// in front of the host name I get the following exception

java.lang.RuntimeException: java.net.UnknownHostException: https

[SimonSparksBetf]

Out vCAC v 5.2 is deployed in the configuration show on page 1 of this PDF entitled "vCAC Deployment Profiles"

http://www.vmware.com/pdf/vcac-52-reference-architecture.pdf

[cdecanini_]

Not sure how to solve this. I am running on http here and with a different version of the plug-in that is not yet publicly available.

You should definitely open a GSS SR.

[SimonSparksBetf]

Ok ,i'll raise the SR now.

[SimonSparksBetf]

The SR Number is 13336191506, the issue is with Business Critical Support.

Hopefully they will pass it over to Enterprise Applications guys in the US so I get a quick resolution.

[cdecanini_]

The support team already got in touch with me and getting support from engineering.

[SimonSparksBetf]

We are running CO on Windows so the build number is not the same as the virtual appliance version of vCO.

For a production environment what do VMware recommend now ?

Should we be using the Windows version of vCO or the Virtual Appliance version of vCO ?

[cdecanini_]

Both are supported in production so it is really a matter of choice. For the VA you have to connect it to a directory service & external DB for production use.

Some customers prefer Windows because they get a desktop & tools & have standard backup applications for example. Some prefer the VA because it is simpler to deploy, they prefer SSH, lower footprint / no licence cost / no patch tuesday of the VA.

What is different is the upgrade process. Maybe some customers can give their feedback on upgrading on windows vs upgrading the VA.

[EV_Simon]

Good to hear that we won't need to upgrade the current version of vCO. One question I do have tho is do we have to re-install vCAC because we installed it with HTTPS or can we do something in a config file somewhere to change it to HTTP instead?

[cdecanini_]

The released vCAC plug-in for vCO is supposed to support https. One thing it did not have OOTB was a workflow to add a vCAC host to the vCO inventory supporting http.

The upcoming release has a workflow that support both (you just have to add http:// before the hostname to support http). This is why I suggested contacting GSS to get the newer version (or eventually get the current version working with https if GSS can figure out).

In any case you should not have to change the vCAC installation to HTTP to have the plug-in working. You may do it for testing but I would recommend against it in production.

[EV_Simon]

Thats great news again , just waiting on delivery of the new plugin then (Sparky has gone home for the day now).

[SimonSparksBetf]

We now have the new vCAC Plugin for vCO and it worked first time with vCAC v5.2 the new plugin version is 5.1.0.236

[cdecanini_]

This is the version I am running and advised BCS to get from engineering / Product Management for you. Glad they could go through the process promptly.