1.5.3 General procedure for creating new plug-ins and adding them to service templates
Users can create custom plug-ins and add them to service templates as steps.
You might use this procedure when:
You want to create a new plug-in and define processing that executes a command.
Required knowledge
General procedure
Task |
Mandatory/optional |
Refer to |
|
---|---|---|---|
1 |
Create a plug-in. |
Mandatory |
|
2 |
Copy the release service template that you want to edit. |
Optional |
|
3 |
Add a plug-in you created as a step in a flow. |
Mandatory |
|
4 |
Add and delete related steps when adding a step affects the flow of processing. |
Optional |
3.4 Adding and editing steps, 3.5.3 Operations that can be performed on steps and relational lines |
5 |
Set step properties when editing a plug-in affects step properties. |
Optional |
|
6 |
Set service properties when editing a plug-in affects service properties. |
Optional |
|
7 |
Validate the edited service template#. |
Optional |
|
8 |
Release a completed service template and prepare to create the service. |
Mandatory |
|
9 |
To move the service template from the development environment to another environment, export the service template, and then import it to the destination environment. |
Optional |
5.5.1 Procedure for exporting service templates, 5.6.1 Procedure for importing service templates |
10 |
Create, edit, and execute the service. |
Mandatory |
JP1/Automatic Operation Administration Guide
|
- #
If the validation process finds an issue with the service template, repeat tasks 1 to 7 as needed.