I realized that although I have covered several of the SovLabs modules already with some fine use cases, I might have jumped the gun a little and not fully explained what this SovLabs business is and how I got to those points. I often receive the question “is it a vRealize Orchestrator plug-in?” and so realize a little introduction is in order. To answer that question, the answer is Yes* but also No*. The asterisks are quite necessary in order to provide a fair answer because, yes, while it’s a vRealize Orchestrator plug-in it is far, far more than that and goes way beyond any other vRealize Orchestrator plug-in. It’s also No because it is a vRealize Automation plug-in as well. If you’re confused and want to finally discover for yourself what the heck this thing is, then this article is for you so read on for the answer, because today we’re going to show how SovLabs works from absolute scratch starting with a clean vRealize Automation platform.

Back to the question of whether SovLabs is merely a vRealize Orchestrator plug-in, the clear answer is yes and no. It is true that SovLabs comes packaged as a vRealize Orchestrator plug-in (in fact, the largest plug-in ever for vRealize Orchestrator at over 100 MB for the 2018.1 release) in the VMOAPP format. Note that this is not a vRealize Orchestrator package. This is a true plug-in that contains compiled Java code and not simply a tinker’s toolkit filled with a few actions and workflows. It’s hardcore stuff.

This is the sole artifact that is needed and it gets installed inside vRealize Orchestrator. However, it is actually a vRealize Automation plug-in because of how it interfaces with vRealize Automation without any intervention on your side (minus an initial configuration workflow). And, actually, if you were to go to the Solution Exchange, you wouldn’t even find SovLabs under the vRealize Orchestrator category. Instead, all their modules are found under the vRealize Automation category and for good reason as you’ll soon see. So, “yes,” it is a vRealize Orchestrator plug-in and “yes” it is a vRealize Automation plug-in. To see exactly what I mean, I’m going to go through the entire process of installing and setting up the SovLabs plug-in from a brand new, pristine install of vRealize Automation so you can understand why this designation is true.


Right, so I just installed a fresh vRealize Automation 7.3.1 system consisting of a single appliance and a single Windows IaaS server. This is all we need for the minimal installation footprint. I’ve only done two things after the installer wizard completed: created one single tenant (called “demo”) and prep the internal vRealize Orchestrator system for the installation of the SovLabs plug-in. There is actually a script prepared by SovLabs and available on their documentation page here which performs this task for you. It does a few things to vRealize Orchestrator:

  • Sets up krb5.conf to allow Kerberos authentication
  • Allows access to local processes
  • Configures js-io-rights.conf
  • Increases Java heap size of Control Center

The last bullet there is probably the most important as without increasing the heap size of Control Center, the plug-in—owing to its size—will not upload successfully. And, departing for a moment, on the matter of its size, I also get the question “why is this thing so big?” Not only does this one plug-in file contain dozens of different modules (i.e., everything you see on their website) but it encapsulates a number of different SDKs so SovLabs is entirely self-sufficient. Other than the vRealize Automation plug-ins built into vRealize Orchestrator, it relies upon no other plug-ins to function. In this regard it is many, many plug-ins rolled into one. Even things like vCenter, mail, and other more core bits of functionality, it depends on nothing else to ensure the utmost of stability. Because they can “own” these SDKs, there isn’t risk or fear that upgrading the vRealize Orchestrator-provided vCenter plug-in, for example, will break all your SovLabs integrations, and that’s a very important thing to ensure.

Now that we have a basic tenant in vRealize Automation and we have prepped vRealize Orchestrator, it’s time to install the plug-in. Head over to the Control Center (you must start the


service on the appliance first) and go to Manage Plug-Ins. Browse and find the SovLabs plug-in.

Install the plug-in and restart the vRealize Orchestrator services over on the Startup Options page. It’ll take several minutes for the server to recover because this is one big boy. Once it shows the running state is good, go back and make sure you see the plug-in listed.

Now, if we’ve got that set up, it’s time to login to vRealize Orchestrator which, for many, is the only time they’ll ever have to login again regardless of how many changes they want to make or new modules they want to use.

If we flip over to the Workflows menu, we should see a new SovLabs folder with all the various things it imported. It’s quite a huge list as you can see.

Although there is only one thing to run from the SovLabs side, there are two others that serve as prerequisites for doing so, and that is to add the vRealize Automation host and the vRealize Automation IaaS host into the configuration. These steps are required regardless, so you’d have to do them anyway.

I’ll spare the additional walk-through of these simple workflows as they can be found in numerous other blogs and articles. But, suffice to say, they’re very straightforward and ran without incident.

I’ll expand the trees under the Inventory option just to make sure I can see things in the system after running those two workflows.

Now I’ve got that, it’s time to run the sole SovLabs configuration workflow. Before doing so, I want to again stress the fact that I have done zero configuration inside of vRealize Automation aside from creating a bare-bones tenant called “demo” and giving it one business group. I have no catalog items, no entitlements, and no blueprints (“Azure machine” comes with vRealize Automation).

Let’s run this SovLabs configuration workflow now.

Start the workflow, and let’s fill out the few screens.

Accept the license agreement (per always) and click Next.

The vRealize Automation Tenant Name up top comes from the vRealize Automation config workflow we ran earlier, and we see the one and only business group I created in the second field there. Yes, we want to create the vRealize Automation Catalog Service, and we need to give it a group (which must already be synched) in order to create the entitlement. I’ve provided it my vCAC Admins group here, which I pulled in from my AD environment. And Yes we want to publish the license content. Click Next.

This is a new install so no upgrading of content is necessary, however if you did upgrade your plug-in, this is what you’d re-run and choose “Yes” here.

Defaults to Yes but we do want to install the workflow (EBS) subscriptions. Click Submit and watch it run through its stuff.

I actually made an error and said my group was “” which it wasn’t. The actual group was “” so I had to go back and fix that. Woops! But I want to be absolutely transparent about every single step in this process, so I have not edited out my boo-boo. I’ve redacted nothing in this process, including my errors, so you can truly see everything involved in going from zero to SovLabs.

But after fixing that security group, the workflow ran right through.

Now, that’s better! Let me go into the catalog to see what happened.

Whoa, what is this??

The SovLabs plug-in created this automagically! If I go back and check those places in vRealize Automation that were previously empty, I now see stuff is there.

And, again, all this created by the plug-in as the result of that one configuration workflow.

Ok, so now we have the ability to add a license. Where is the rest of the stuff?? “So far this isn’t very exciting,” I know you’re saying. Let’s add my license and see what happens next.

If I flip over to the vRO client and expand License -> vRealize Automation ASD, I see it running through the Add License workflow.

Hmm, publish content? Interesting. Depending on what modules your license entitles you to use, this could be a quick or very long wait. Lots of complexity is happening behind the scenes, so be patient.

After about 7 minutes (because I have everything licensed), it completes.

Now, go back to the vRealize Automation catalog and have your mind blown away.

The plug-in decoded the license, found which modules were entitled, and published only that content for you, automatically, to the vRealize Automation catalog. If you now pause to take a tour through vRealize Automation, you’ll see a whole host of accompanying things like XaaS resource actions and mappings to facilitate these new things. How about check out the Subscriptions portion of vRealize Automation?

That’s TWO PAGES’ worth of brand new event broker subscriptions which you didn’t have to create yourself. And, remember, all we’ve done in this case is run a single vRealize Orchestrator workflow. Everything else is self-published beginning with the Add License catalog item. This isn’t something a vRealize Orchestrator plug-in does, which is why SovLabs isn’t just a vRealize Orchestrator plug-in. It pushes things intovRealize Automation based on how you configure it. There is nothing you need to monkey with inside vRealize Orchestrator, and nothing outside of the catalog in vRealize Automation. Everything from soup to nuts is instantiated and configured for you based on simple, easy-to-use catalog items.

Folks, let me just be honest for a second, this is amazing. The fact that it does all the heavy lifting for you is remarkable. If you’ve ever tried to interface a regular vRealize Orchestrator plug-in with vRealize Automation to actually get it to do stuff, you’d find it’s not a very quick or fun process and is fraught with peril and creates copious opportunity for human error. All of that is done for you with SovLabs. I really hate to use the term “game changing” because I feel it’s often employed to create artificial sales and marketing hype, but in this case it couldn’t be more appropriate. When you enable someone with absolutely zero vRealize Orchestrator experience and minimal vRealize Automation experience to extend their own CMP out to other infrastructure in very advanced ways and in a simple fashion, you change the game of extensibility entirely.

From this point, you can begin to configure and then consume the modules according to your extensibility needs. So, for example, if we wanted to configure Custom Naming (the most popular module and is amazingly flexible), we are now poised to do so. This process is shown quite well in Dailyhypervisor’s blog post here and in my article here. At the end, once both configuration catalog items are requested and run, out pops a Property Group which, again, is an entirely automated process and can be attached to a blueprint of your choosing. Rinse and repeat with other modules. You’re now up and running with SovLabs!

I hope I’ve now finally answered the question “what is SovLabs?” And I hope that at this point you understand the answer that it is far more than just a vRealize Orchestrator plug-in. It is, in fact, a vRealize Automation plug-in which is unmatched by anything else out there in the marketplace. You run one configuration workflow, and the rest is entirely driven by vRealize Automation. There may never be the need to return to vRealize Orchestrator again after that point, and that’s not something you can say for any other plug-in in existence. Go forth and extend vRealize Automation to your heart’s content!

Recommended Reading