Hitachi

JP1 Version 12 JP1/Automatic Operation Service Template Developer's Guide 


6.1 Overview of plug-ins

A plug-in defines processing that executes a task.

There are three types of plug-ins in JP1/AO: basic plug-ins, release plug-ins, and development plug-ins. In the Component area of the Flow tab of the Service Builder Edit window, basic plug-ins and release plug-ins are displayed in the Release tab, and development plug-ins are displayed in the Develops tab.

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 JP1/Automatic Operation Service Template Reference.

Tip

In the Component area of the Flow tab of the Service Builder Edit window, the Services tab displays service components. Service components are release service templates that can be placed as steps in the Flow area. Thus, service components are not included in the plug-ins described in this manual.

Table 6‒1: Types of plug-in

Type

Description

Basic plug-in

  • Displayed in the Release tab.

  • A plug-in provided by JP1/AO. A basic plug-in defines generic processing like email notification and flow repetition.

Content plug-in

Release plug-in

  • Displayed in the Release tab.

  • A plug-in that is imported into JP1/AO by a user releasing a service the user created.

  • A plug-in in a service template provided by JP1/AO.

  • A plug-in that is imported into the JP1/AO server in released configuration, is also handled as a release plug-in.

Development plug-in

  • Displayed in the Develops 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 is imported into the JP1/AO server in debug configuration, is also handled as a development plug-in.

By using plug-ins, you can perform actions like the following:

In JP1/AO, a user can create a custom 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 JP1/Automatic Operation Service Template Reference.

Organization of this section