2.2.1 System Plugins

System Plugins are Plugin Parts provided by Navigation Platform that do not require program development. The System Plugins include the following:

Data Store Plugin
JP1 Link Plugin
JavaScript Plugin (JavaScript needs to be written.)

In this manual, plugins to control the input and output of data are referred to generically as I/O Plugins.

I/O Plugins of the System Plugins include the following:

Data Store Plugin
Automatic Operation Property Output Plugin
Automatic Operation Service Execution Plugin
Automatic Operation Window URL Creation Plugin
JP1 Event Status Change Plugin
JP1 Event information output plugin
Service Support Window URL Creation Plugin
JavaScript Plugin
I/O Plugins of the User Plugins

Plugins that do not communicate with a server are referred to as Offline Plugins and non-offline plugins Online Plugins. Offline Plugins include the following:

Data Store Plugin
JavaScript Plugin^#

#: If using JavaScript Plugin offline, it is necessary to select the Execute in the browser check box in the Attribute Settings window of the JavaScript Plugin part in advance.

Organization of this subsection

(1) Data Store Plugin processing and behavior diagram
(2) JP1 Link Plugin processing and behavior diagram
(3) JavaScript Plugin processing and behavior diagram

(1) Data Store Plugin processing and behavior diagram

Using the Data Store Plugin, the input and output of data within an Operational Content can be managed, and values that are entered or selected by the user can be inherited and displayed by other nodes. The following is an example of an Operational Content that uses the Data Store Plugin.

Figure 2‒4: Example of Operational Content using the Data Store Plugin

In this example, by placing a Data Store Plugin in each node, the data entered in nodes 1 and 2 is inherited by node 3, which outputs it for display.

To Page Top

(2) JP1 Link Plugin processing and behavior diagram

Using the JP1 Link Plugin, an Operational Content in Navigation Platform can be linked to other JP1 products in external systems. The following figure illustrates the Operational Flow when Navigation Platform is linked to other JP1 products.

Figure 2‒5: Operational Flow when Navigation Platform is linked to other JP1 products

The figure represents the flow of operations as follows.

The occurrence of a failure is confirmed in the JP1/IM window.
In order to determine how to handle the failure, an Operational Content is invoked from the JP1/IM or JP1/IM-SS window.
The failure is handled by interacting with the Operational Content.

In some cases, the failure can be handled more efficiently by invoking the JP1/AO window from the Operational Content.
The information that the failure has been handled is reflected in the JP1/IM window.

Note that development of a User Plugin is required in the event you wish to exchange data with external programs or databases that are not JP1 products,.

To Page Top

(3) JavaScript Plugin processing and behavior diagram

An overview of the JavaScript Plugins is illustrated below.

Figure 2‒6: Overview of JavaScript Plugins

A JavaScript Plugin allows you to write server-side JavaScript running on a server or client-side JavaScript running on a web browser (on a client) that uses data from Operational Contents as input or output.

In this way, you can execute any processing that can be programmed with JavaScript by using JavaScript Plugins, without the need to develop User Plugins. The JavaScript written in a JavaScript Plugin is saved as part of Operational Contents.

Furthermore, with JavaScript Plugins, you can invoke a specified URL by using an API (JavaScript API) provided by Navigation Platform. For example, you can invoke a Web API (REST API, etc.) released on the cloud or the Web server from a JavaScript Plugin.

To Page Top