A custom service template consists of plug-ins, (or other service templates) that run the commands or scripts to automate sets of tasks. The plug-ins and services are added as steps and arranged in a sequence to form the operational flow. The service template also needs the mapping of input and output properties to define the flow. Use property groups and service share properties to assist you with defining input and output properties.
Two versions of service templates are available when you access the Service Builder Home window:
- Developing: A new service template begins with a debug version. Testing a service template includes creating services and tasks based on the debug version of the service template. The service template resides in the Developing status and can be copied and modified. If a debug version of a service template is built again, the previous debug version of the service template and its services are deleted, and the related tasks are archived. When a Developing version of a service template is released, the debug version of the service template and all the related services are deleted, and the tasks are archived.
- Released: A released version of a service template has completed testing and is available under the Released status. New services and tasks can be created and run based on a released service template. Released service templates cannot be edited, but can be copied and modified for use in another service template.
You can click the Developing or Released tabs from the Service Builder Home window to access the service templates. By clicking and highlighting a service template, either from the Card View or Table View, you can access details and complete management functions (view, edit, copy, delete, import, or export) for a service template. If necessary, you have the option of creating a new service template, either based on one of the existing templates or from scratch, and then customizing it for your data center.