3.2.3 System configuration examples

(1) When you want to reduce the work required of the system administrator to use Operational Contents

To reduce the work required of the system administrator to use Operational Contents, we recommend a system configuration in which the editing environment also serves as the execution environment.

Figure 3‒1: System configuration example (editing environment is also the execution environment)

Running the editing environment and the execution environment on a single server machine can reduce the system administrator's workload, because no effort is required to export to the execution environment Operational Contents that have been created in the editing environment. On the other hand, there are other points to consider, such as the fact that the workload on the server might become large when many users access the server at the same time.

To Page Top

(2) When you want to protect users from the effects of editing mistakes

In order to ensure that users are not affected by editing mistakes while Operational Contents are being created, we recommend a system configuration that separates the editing environment from the execution environment.

Figure 3‒2: System configuration example (separate editing and execution environments)

When you run the editing environment and the execution environment on separate machines, you must export the Operational Contents created in the editing environment and import them into the execution environment. In this case, the execution environment remains unaffected by editing mistakes, for example if an Operational Content is accidentally made private or is deleted while it is being used.

To Page Top

(3) When you want to balance the system workload

In order to balance the workload on the system, we recommend a system configuration that divides the execution environment among multiple servers.

Figure 3‒3: System configuration example (multiple execution environments)

It is also possible to run execution environments on multiple server machines when using the configuration in (2) When you want to protect users from the effects of editing mistakes. Under this configuration, you can expect the benefits of reduced server workload and increased system availability. Note that when there are multiple execution environments, it is necessary to export the Operational Contents created in the editing environment and import them into all the execution environments.

To Page Top

(4) When you want to develop plugins and custom windows

In order to develop plugins and custom windows, we recommend a system configuration that includes a development environment.

Figure 3‒4: System configuration example (with development environment)

A development environment for developing User Plugins is necessary if you want to create sophisticated Operational Contents that use User Plugins. The User Plugins you develop in the development environment are first deployed to the editing environment. These User Plugins must also be deployed to the execution environment when the Operational Contents created in the editing environment are imported into the execution environment.

To Page Top

(5) When you want to link with other JP1 products

Figure 3‒5: System configuration example (linked with other JP1 products)

User authentication by JP1/Base is required in order to use the JP1 Link Plugin.

In configurations with multiple editing or execution environments, JP1/Base must be installed in each environment, but a single authentication server can be shared across the system. In the case of the diagram shown in Figure 3-5 System configuration example (linked with other JP1 products), because the JP1/Base in the editing environment is used as the authentication server, the JP1/Base in the execution environment can use the authentication server in the editing environment to perform user authentication.

For the versions of JP1/Base that can be used in Navigation Platform, see 3.3.2 Types of user authentication that can be used in Navigation Platform. For details about the JP1/Base user authentication functions and authentication servers, see the JP1/Base User's Guide.

We also recommend specifying the same language setting on the OS running the JP1 products and the OS running the Navigation Platform execution and editing environments.

If you do specify a different language setting on the OS running the JP1 products and the OS running the Navigation Platform execution and editing environments, make sure that you use ASCII character encoding for the data to be linked between them. If you use a non-ASCII character encoding, characters might become garbled.

To Page Top