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.

Table 4‒1: Types of plug-in
Type		Description
Basic plug-in		Displayed in the Basic tab. A plug-in provided by JP1/AO. A basic plug-in defines generic processing like email notification and flow repetition.
Content plug-ins	Release plug-ins	Displayed in the Release tab. A plug-in that was imported into JP1/AO by a user releasing a service he or she created in theEditor window. A plug-in in a service templates provided by JP1/AO. A plug-in that was imported into the JP1/AO server by the `importservicetemplate` command and has the released configuration type is also handled as a release plug-in.
Content plug-ins	Development plug-ins	Displayed in the Under Development tab. A plug-in that a user created as a new plug-in, which has not yet been released. A plug-in that is being created based on a copy of an existing plug-in is also classified as a development plug-in. When you build a development service template that includes a development plug-in, the development plug-in is imported into the JP1/AO server and can be executed for testing purposes. A plug-in that was imported into the JP1/AO server by the `importservicetemplate` command and has the debug configuration type is also handled as a development plug-in.

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

To Page Top