2.2.1 System Plugins

(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.

1. The occurrence of a failure is confirmed in the JP1/IM window.

2. In order to determine how to handle the failure, an Operational Content is invoked from the JP1/IM or JP1/IM-SS window.

3. 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.

4. 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