vCAC 6.0.1 plugin for vCO 5.5

[Aristizabal]

Hello,

Has anybody tried to configure the new vCAC 6.0.1 plugin on vCO 5.5 (appliance)?. I installed the plugin without issues but now I am having trouble running the "Add a vCAC host" workflow against a vCAC 6.0.1 installation.

All the blogs I have seen look like they are using an older version of the vCAC plugin, which do not ask for the tenant information.

I always get the following error:

org/springframework/oxm/UnmarshallingFailureException (Workflow:Add a vCAC host / Add a VCAC host (item0)#58067) - vCAC6.X-XXXX

Thanks,

Juan.

[qc4vmware]

The old plugin was actually asking for the IaaS server if I remember correctly.  That is still part of the plugin but now there is the new option for adding the vCAC (Cafe) server as well which enables all the new functionality. 

[Aristizabal]

That's a good point. Unfortunately the workflow that adds the IaaS server needs the vCAC host as an input parameter, so I won't be able to add the IaaS server yet.

I am wondering if this has to do with my version of vCO, which is the appliance version 5.5.  The embedded vCO for vCAC 6.0.1 is version 5.5.1, so it could not be compatible. Although the installation of the plugin was successful. 

[cdecanini_]

I was successful setting up both the IaaS part and CAFE part using the 5.5.1 appliance (that is part of vSphere 5.5 U1 release).

It may also work with the embedded vCO in vCAC 6.01 but may not on the previous versions including vCO 5.5.

[Aristizabal]

Thanks for replying. I'll deploy a new 5.5.1 vCO appliance and try it. By the way, the reason I am doing this is to add vCO workflows to state changes during VM provisioning; it used to be different on vCAC 5.2 where you had to add properties to the blueprint, but it looks like now everything is done using the advanced service designer.

[cdecanini_]

There are two different things in 6.0 :

• Infrastructure as a Service which has a lifecycle that can be extended with the state change workflows as in 5.2
• ASD which allows to create new services to provision catalog item for anything you have a workflow for (XaaS - Anything as a service). It also provides day 2 operations for vCenter VMs provisioned in IaaS.

And 2 APIs

• The IaaS one covered by the vCAC IaaS plug-in (that shipped with 6.0). This one contains extensibility workflow allowing to automate the assignment of vCO workflows to state changes & blueprints.
• The "CAFE" one which cover the new services including tenant, catalog management, approval and many other covered by the vCAC "CAFE" plug-in.

These 2 plug-ins are combined into the vCAC 6.01 plug-in.

[qc4vmware]

I don't know if this will be helpful to you at all but here are the answers I supplied the plugin which successfully added my host.

Hostname: vcacuidev02  // This is obviously just a label so it could be anything

Host URL: https://cafeserver.yourcompany.com // just the https path to the cafe server

Tenant: vsphere.local // for the default tenant

Automatically install SSL certificates : Yes

Connection Timeout: 30.0

Operation Timeout 60.0

Session Mode: Shared Session

Authentication username: adminuser@yourcompany.com // user that is in the administrative group

[Aristizabal]

On the host URL did you enter the IaaS server or the URL that you use to access the vcac appliance?  like https://[vcac-vapp]/shell-ui-app/org/myorg, I got a different error this time:

port out of range:-1 - https://[vcac-vapp]/shell-ui-app

Thanks,

[stvkpln]

How odd... when I try and add the vCAC Appliance, I'm getting InternalError: handshake alert:  unrecognized_name (Workflow:Import a certificate from URL / Validate (item1)#6) every single time... the vCAC Appliance is the only thing that kicks back a problem, and I can successfully log in and function.

Weird. I guess I'll have to open a ticket on it when I get a chance.

[Aristizabal]

Ok, I finally got it working on the external appliance version 5.5.1.  In vCAC 6.0 the configuration of the vCAC appliance used to say CAFE Host server, in 6.0.1 it is labeled vCAC Host.

Using Host URL = vCAC appliance as: https://[vcac appliance FQDN]      did the job.

For the record, it doesn't work with vCO 5.5, I tried with the same settings above and got an error message.

Thanks for the help.

[rszymczak]

Anything new on this? I'm also unable to add the vcac appliance and keep getting the handshake alert error.

[rszymczak]

Well I'm not sure whats wrong with the workflows, but they seem not to be consistent. After re-running the add procedure around 20 times using the same input parameters it suddenly worked.

[BrendaSwarts]

I am experiencing the InternalError: handshake alert: unrecognized_name (Workflow:Import a certificate from URL / Validate (item1)#6) when running the Add a vCAC host workflow.  Is there a know solution to this issue?  If I just run the Import a certificate from URL workflow it errors at connecting to the url although I can connect successfully through IE.

[rszymczak]

yes: copy the ssl-check workflow, remove all checks and only leave the script that actually imports the certificate into the vco keystore. next copy the add vcac host workflow and remove the import ssl workflow part (which you already just ran manually). it should work.

[BrendaSwarts]

Success!  Thank you.

[santoshdalvider]

Hi Sir ,

I am also facing the same error : InternalError: handshake alert:  unrecognized_name (Workflow:Import a certificate from URL / Validate (item1)#6) . when you are saying copy the ssl check workflow , can you please explain that from where i can do this .

Regards,
Sandy