1.6 List of service template development features
The following table lists the features of JP1/AO that are used in the development of service templates.
Feature |
Description |
Reference |
|
---|---|---|---|
Service template management |
Creating and editing service templates |
Users can create new custom service templates. Users can also edit existing service templates, replacing parameters such as the service template name, description, service properties, and custom file to suit their needs. |
|
Listing service templates |
You can display a list of service templates. |
||
Copying service templates |
You can copy a service template. You can then create a new service template by editing the copy. |
||
Deleting service templates |
You can delete a service template. |
||
Setting display information for service templates |
You can create a service resource file that defines the information displayed for a service template. |
2.6 Setting display information for service templates in resource files |
|
Flow management |
Adding steps |
You can insert processing where it is needed by adding a step to a flow. You can also edit the definition information for a step. |
|
Connecting relational lines |
After adding a step, you can define its place in the execution order by connecting relational lines. |
||
Plug-in management |
Listing plug-ins |
You can display a list of plug-ins. |
|
Creating plug-ins |
Users can create custom plug-ins to suit their needs. |
||
Editing plug-ins |
You can edit plug-ins. This might involve changing the name, input properties, output properties, remote commands, or other aspects of a plug-in. Note that you cannot edit the plug-ins provided in the standard JP1/AO package. |
||
Deleting plug-ins |
You can delete development plug-ins and release plug-ins. |
||
Copying plug-ins |
You can copy a plug-in. You can then create a new plug-in by editing the copy. |
||
Setting plug-in display information |
You can create a plug-in resource file that defines the information displayed for a plug-in, such as its name and description. |
||
Validation of service templates |
Building service templates |
When you build a service template, the JP1/AO system creates a package of the service template you are developing and imports it to the JP1/AO server. Use this feature when you need to validate a service template. |
|
Debugging service templates |
You can check the operation of a service template you have built and identify any issues. If the debug process reveals an issue in the flow or in a plug-in, you can edit the service template or plug-in from the Editor window. |
||
Testing service template operation |
You can add and execute a service based on a service template you have built, and test the service for issues. If the test identifies an issue in the service, you can edit the service template or plug-in in the Editor window. |
||
Build and release |
Releasing service templates |
After validating a service template, you can release it. This creates a package from the service template which is imported to the JP1/AO server. You cannot edit a service template after releasing it. If your development environment and active environment are separate, you will need to import the service template manually. |
|
Importing service templates |
If your development and active environments are on different servers, this feature imports released services to the active environment. |