5.4.1 Overview of service template release
Release is the process of making a service template available to other users after it has undergone validation processing. When successfully released, a service template is packaged and can be created as a service.
Note that you cannot edit a service template or its plug-ins after the service template has been released. To edit a released service template or its plug-ins, you need to copy the service template or plug-in and edit the copy.
Objective
Perform a release operation when you want to use a service template in the active environment. A released service template is packaged as a service template of the Release configuration type, and imported to the JP1/AO server.
Number of releases
You can release a service template only once. When you release a service template, the pre-release development service template is deleted. Any services that were created from the development service template prior to release are deleted, and associated tasks are archived. Debug services and debug tasks are deleted.
For details about the specific service templates, services, tasks, debug services, and debug tasks that are deleted and archived during a release operation, see A.1(5) Deletion and archiving of service templates, services, and tasks during build and release operations.
Assigned configuration type
After its release, a service template is assigned the Release configuration type. In addition to users in the Admin and Develop roles, users in the Modify and Submit roles can configure and execute release service templates and the associated services and tasks that were created. Note that you cannot edit a service template or its plug-ins after the service template has been released. To edit a released service template or its plug-ins, you need to copy the service template or plug-in and edit the copy. For details about the configuration types assigned to service templates and plug-ins by the release processing, see A.1(2) Configuration types assigned to service templates and plug-ins by build and release operations.
Output destinations of service templates
When you release a service template, a service template package is created in the folder shown below with the name vendor-ID_name_version.st.
You can also save a service template package in any folder by exporting the released service template.
- In a Windows non-cluster system
JP1/AO-installation-folder\develop\output
- In a Linux non-cluster system
/var/opt/jp1ao/develop/output
- In a Windows cluster system
shared-folder-name\develop\output
- In a Linux cluster system
shared-folder-name/develop/output