5.1.2 Overview of building
Building is the process of preparing a service template you created or edited in the Editor window for testing. When successful, a build operation creates a package of the service template which you can then use to debug the service template or add a service to the server.
Objective
Perform a build operation to prepare a development service template for validation. The service template you build is packaged as a debug configuration service template and imported to the JP1/AO server.
Number of executions
You can build a service template any number of times. If the debug process or an operation test reveals an issue with the service template, the user repeats the series of operations from amending the development service template or development plug-in to checking its operation until all issues are resolved.
When you edit and rebuild a service template that has already been through a debug process, JP1/AO deletes the debug service and debug task generated the last time the service template was built. When you rebuild a service template after testing its operation, JP1/AO deletes the services added from the service template and archives tasks. For details about the services and tasks archived and deleted during build operations, see A.1(5) Deletion and archiving of service templates, services, and tasks during build and release operations.
Assigned configuration type
After building, a service template is assigned the Debug configuration type. Only users assigned the Admin or Develop role can view and work with Debug configuration type service templates and the associated services and tasks.
Output destinations of service templates
When you build a service template, a service template package is created in the following folder with the name vendor-ID_name_version_d.st:
- In a non-cluster system
-
JP1/AO-installation-folder\develop\output
- In a cluster system
-
shared-folder-name\develop\output
Related topics