If you’ve been following along, whew! Last post in this series and likely the easiest. Let’s do a quick recap.
In our first post we basically went through the process of determining “how do I do what I want to do?” In our case that was making a REST call to UCSD and kicking off a workflow. We used the Postman utility to help accomplish this.
In the second post we went through the process of “how do I get vRealize Orchestrator to do what I want to do?” Here we used some existing sample workflows and made some modifications to do what we wanted, how we wanted.
In this final post we need to expose that workflow to vRealize Automation so that it can be consumed in a catalog.
I’m logged into the vRA instance as a tenant/everything admin for my subtenant. We’ll be looking specifically as “Anything-As-A-Service” or XaaS. These are where you can call vRO workflows directly. Under Design > XaaS > XaaS blueprint, click New.
Now I’ll select the workflow that I created in vRO and hit Next.
The next pages are pretty self explanatory, you can leave them defaults with one exception. Because we made the workflow self-contained (requires no user input) you can delete the Request Form.
Now we want to publish it.
And now that it is published, we can make it available by an entitlement by adding it to an entitled service.
Just a couple of notes here. If you don’t see the item available in the catalog management screen, it is probably not published. And if you put the entitlement as a single item rather than part of a larger service, just remember that you won’t see it in your catalog until it is a member of at least one service.
Now that we’ve taken care of all this, I can browse to my catalog and request the workflow.
You should only have to enter a description in because we kept everything straightforward everywhere else. When you create the XaaS Blueprint you have an option to not even require this page but I like it because it is somewhat of a tracking mechanism.
Now we see the request in vRA go successful.
And once again in UCSD we see the workflow being executed.
I would definitely continue to use this simple methodology (or something like it) as you extend and integrate new things into your environment. And I would also encourage you to continue to copy and extend existing workflows for your own use as well. Remember, shortest path to the goalpost almost always wins.