How to enable Advanced Service Designer in vCAC 6

So you got past the initial setup and install of vCAC 6. You have already provisioned several Windows or Linux blue prints and now you want to play with the advanced service designer. But wait? Where is the advanced services tab in vCAC?

media_1388794556458.png

Humm, you have everything licensed correctly and you are logged in as the administrator that was configured in the tenant configuration. What gives? Well, as I found out there is a bit more to do to configure this functionality.

Let’s walk through how to configure the advanced services. First off, the advanced services and advanced service designer in vCAC 6 leverage vCenter Orchestrator or as we call it “vCO” for short. vCenter Orchestrator is shipped with vCAC 6 as an embedded application on the vCAC appliance server however you can also use an existing vCO 5.1 or 5.5 instance. The embedded appliance is already installed for you but we need to do a couple things to configure vCAC to use it.

First, click the Administration Tab, then Groups, then the plus sign to add a new group

media_1388796335590.png

Now type in an Active Directory group that will be granted the Service Architect role (I already created the group in AD and added myself to it, yes, it’s nice being King of the castle)

media_1388796574353.png

You have now added your admin account to the role as service architect

But wait….I still don’t see the Tab for advanced services?

ASDConfig

You will need to log out and log back in again.

Log in and you will see the new tab

media_1388796888250.png

Jackpot!! There it is! Was that so hard???

media_1388796955771.png

Tune in next week when I show you how to configure a simple Day 2 operation using the new advanced service designer. Bye for now and happy Clouding!!

Remember sharing is caring!

4 Replies to “How to enable Advanced Service Designer in vCAC 6”

  1. Pingback: Newsletter: January 18, 2014 | Notes from MWhite

  2. If you get any time to do AD:User and AD:UserGroup fields in a Service Blueprint against active directory endpoints that are bound in an OU that has more than 100 entries, please blog about it. VCAC 6.0.1 ASD is only returning 100 AD objects to us via LDAP (in sub tenant of default).

    • @SeanK, we have the same problem, searches using the AD plugin in ASD blueprints are not working – rarely find the user. Searches using the same plugin natively in vCO work fine.

      Did you ever resolve this problem?

  3. Pingback: 19-05-15 | Virtual Fabric

Leave a Reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.