4.1.2 Overview of basic plug-ins, release plug-ins, and development plug-ins
A plug-in defines processing that executes a task.
There are three types of plug-in in JP1/AO: basic plug-ins, release plug-ins, and development plug-ins. Each type is displayed in its own tab in the Plug-in view.
For the sake of expedience, plug-ins are separated into basic plug-ins and content plug-ins according to their origin. For details, see Types of Service Templates and Plug-ins in the manual Job Management Partner 1/Automatic Operation Service Template Reference.
Type |
Description |
|
---|---|---|
|
||
|
||
|
By using plug-ins, you can perform actions like the following:
-
Sending notification emails and controlling flow repetition
-
Transfer files and folders between the JP1/AO server and a remote host
-
Connect to a remote host and execute commands and scripts
In JP1/AO, a user can create a custom plug-in as a content plug-in. Users can also create plug-ins that connect to a remote host and execute commands and scripts, and incorporate these plug-ins into a service template.
When JP1/AO executes a content plug-in, it uses WMI to connect to operation target devices that are running Windows, and SSH to connect to UNIX devices. For details about basic plug-ins, see the description of basic plug-ins in the manual Job Management Partner 1/Automatic Operation Service Template Reference.
Related topics
-
4.1.7 Locale set for operation target devices during plug-in execution
-
4.1.8 Character set used for communication by JP1/AO during plug-in execution
-
4.1.9 Setting a specific character set during plug-in execution
-
A.1(2) Configuration types assigned to service templates and plug-ins by build and release operations