Hitachi

JP1 Version 12 JP1/Automatic Operation Service Template Developer's Guide 


A.1 Reference information for build and release operations

Organization of this subsection

(1) Structure of debug and release processes and how they differ

The debug and release processes create a package of a service template. Perform a debug operation when you want to validate a service template, and a release operation when you want to make the service template available in the active environment.

The following figure shows the structure of the debug and release processes.

Figure A‒1: Structure of build and release processes

[Figure]

The following table lists the differences between build and release processes.

Table A‒1: Differences between build and release

Operation

Objective

Number of executions

Configuration type assigned to service template package

File name of service template package

Can development service template be edited after operation?

Build

Validate a service template

Any number of times

Debug configuration

vendor-ID_name_version_d.st

Yes

Release

Make a service template available in the active environment

Once

Release configuration

vendor-ID_name_version.st

No

Legend:

Yes: Can be edited. No: Cannot be edited.

(2) Configuration types assigned to service templates and plug-ins by debug and release operations

JP1/AO assigns a configuration type to the service templates and plug-ins in a service template package (*.st) according to its stage in the development process (debug or release). The following table lists the configuration types assigned to service templates and plug-ins.

Table A‒2: Configuration types assigned by build and release operations

Service template or plug-in

Assigned configuration type

When built

When released

Development service template

Debug configuration

Release configuration

Plug-in#

Basic plug-in or release plug-in (release configuration)

Release configuration

Release configuration

Development plug-in (debug configuration)

Debug configuration

Release configuration

#

You cannot build or release individual plug-ins. A development plug-in becomes a release plug-in when you release a service template that contains that plug-in. A development plug-in remains as such when you build a service template that contains the plug-in.

(3) Build or release operations performed on multiple instances of the same service template or plug-in

If you repeatedly build a service template during its development, or you build then later release a service template, the same service template or plug-ins might have already been imported. The behavior of the build or release operation in this scenario depends on the configuration type of the service template or plug-in.

Note that the same service template (or same plug-in) means a service template or plug-in with the same vendor ID, service template ID (plug-in ID), and service template version (plug-in version). The plug-ins referred to below are those used by the service template being built or released.

When building a service template

  • The service template is overwritten.

  • Development plug-ins in the service template you are building are overwritten.

  • Release plug-ins in the service template you are building are not overwritten.

When releasing a service template

  • The service template is overwritten and becomes a release service template.

  • Development plug-ins in the released service template become release plug-ins.

  • Release plug-ins in the released service template are not overwritten.

(4) Ability to display window items by service template configuration type and the user role

The configuration type of the service template and the role of the user determine whether service templates and elements (services, tasks, and histories) created from service templates appear in the Services window and the Tasks window. The following table describes whether these items appear in the user interface for each combination of configuration type and user role.

Table A‒3: Ability to display window items by service template configuration type and user role

Configuration type of the service template

Managed element

Displayed in the Services window and Tasks window

Admin

Develop

Modify

Submit

Debug configuration

Service template

Y

N

N

Service

Y

N

N

Task

Y

N

N

History

Y

N

N

Release configuration

Service template

Y

Y

N

Service

Y

Y

Y

Task

Y

Y

Y

History

Y

Y

VO

Legend:

Y: Can be viewed and manipulated. VO: Can only be viewed. N: Cannot be viewed or manipulated.

(5) Deletion and archiving of service templates, services, and tasks during build and release operations

When you build or release a development service template, JP1/AO automatically deletes service templates and services and archives tasks. Debug services and debug tasks are automatically deleted.

Note that service templates and services are deleted and tasks archived even if the build or release process fails. Debug services and debug tasks are also deleted.

Figure A‒2: Deletion and archiving of elements during build and release operations

[Figure]