In the VMM Service Template, you can visually arrange the various services and customize the options for them quickly and easily. This is one of the final steps before publishing the service in the service catalog and self-service portal. All of the components are already built; here, we are just putting them together. You can easily add more applications as needed.
Bear in mind that we are simply arranging systems together and not affecting application code in any way. The application code has to be written to talk amongst the various services. The best practice is to use names for systems and services, and never to hard-code dependencies. The templates should be able to build and resolve service names and locations dynamically.
While we don't show it, when we publish this application to the self-service portal, users can come to the portal, request an application and fill just a few relevant bits of information such as application name. The tehcincal bits should all be buried out of site. When they request the service, their permissions are validated and the request kicks off a workflow. That work flow could be fully automated or at any point, you could interject a person to take actions. It's entirely up to you.
Mike Fratto is a principal analyst at Current Analysis, covering the Enterprise Networking and Data Center Technology markets. Prior to that, Mike was with UBM Tech for 15 years, and served as editor of Network Computing. He was also lead analyst for InformationWeek Analytics ... View Full Bio