10.1.4 Configuring JP1/Service Support in a cluster system

(1) Overview of the configuration of JP1/Service Support in a cluster system

The following figure shows an example configuration of JP1/Service Support in a cluster system.

Figure 10‒2: Example configuration of JP1/Service Support in cluster use

• JP1/Service Support supports the active-standby configuration. It does not support the active-active configuration (multiplex startup of logical hosts on each server).

• This configuration is composed of multiple physical hosts, the entire of which makes up one logical host and has one logical IP address. When you register the configuration in the cluster software, the shared disk and logical IP address are required as prerequisite resources.

• The cluster software controls failover.

• The scope of cluster use is the internal components of JP1/Service Support shown below. The cluster software monitors the status of these components.

  • Web server

  • WWW container server

  • Item management database server

  • Task practice service

• The Item management database, database-related files, and log files are stored on the shared disk. These types of data are inherited when a failover occurs.

  Note that each physical host manages various definition files independent of others. When JP1/Service Support uses definition files, it reads the definition files on the active server (physical host). The active server and the standby server switch each time a failover occurs. Therefore, you need to keep the contents of the definition files the same both on the primary node and the secondary node after a user edits a definition file.

• You need to set up the Item storage database on the shared disk.

To Page Top

(2) Files on the shared disk

After you set up JP1/Service Support for cluster environment, the files below are created on the shared disk. These files are necessary for executing JP1/Service Support on a logical host.

Table 10‒3: Files on the shared disk

Type of shared file	Folder name
Item management database	shared-folder\db\
Database-related files	shared-folder\dbms\Setup_Input_HA\
Log files	shared-folder\log\
Cluster environment files	shared-folder\tools\setup\

Note that the Item storage database is not created when you set up JP1/Service Support in the cluster environment. You need to create the database in a separate operation.

Note that because the shared disk is used by both the primary node and the secondary node, if the disk becomes unavailable, the cluster environment for JP1/Service Support will be unavailable. Therefore, you need to take necessary measures, such as using a different power supply for the shared disk from the ones for the hosts.

To Page Top

(3) JP1/Service Support services and processes

Contrary to other JP1 products, such as JP1/IM - Manager, JP1/AJS, and JP1/Base, in JP1/Service Support, cluster environment settings will not create services dedicated to the logical host. JP1/Service Support uses the services created during installation without change. You can use these services as the services for a cluster environment if you set up JP1/Service Support for cluster environment.

The table below lists the JP1/Service Support services used for cluster operation. Register these services in the cluster software, and then execute the services.

Table 10‒4: JP1/Service Support services

Display name	Service name	Internal component name
JP1/Service Support - Web Service	JP1_Service Support-WebService	Web server
JP1/Service Support	JP1_Service Support	WWW container server
JP1/Service Support - DB Server	HiRDBEmbeddedEdition_JS0	Item management database server
JP1/Service Support - DB Cluster Service	HiRDBClusterService_JS0	Item management database server (Service for cluster)
JP1/Service Support - Task Service	JP1_ServiceSupport-TaskService	Task practice service

The Display name column lists the names displayed when you select Control Panel, Administrative Tools, and then Services. If you control the services by using a net command (net start or net stop) from the cluster software, specify a name listed in the Display name column for the net command.

The Service name column lists the service names used to register in WSFC. Specify a name listed in the Service name column for the service name of WSFC.

Notes:

• After you install JP1/Service Support, only JP1/Service Support - DB Server among the JP1/Service Support services is registered with the startup type Automatic. If you run JP1/Service Support in a cluster system with this setting unchanged, a failover fails. Therefore, after you set up JP1/Service Support on both the primary node and the secondary node, you need to change this setting from Automatic to Manual.

• For cluster use, if the value of the use key is false in all the sections for commands in the Definition file for the task practice service (jp1imss_service_setting.conf), the JP1/Service Support - Task Service service fails to start. This causes a failover. Therefore, in a cluster environment, you must set the value of the use key to true in at least one section. Also, if you do not want to use JP1/Service Support - Task Service service in a cluster environment, do not register this service in the cluster software.

  Note

  Relationship between JP1/Service Support services and processes

  Abnormal termination of a JP1/Service Support service triggers a failover. A JP1/Service Support service terminates abnormally when a closely related process terminates abnormally. The following table lists the processes that affect the services.

Table 10‒5: Processes that affect services

Service (display name)	Processes that affect the service
JP1/Service Support - Web Service	httpsd.exe
JP1/Service Support	jss_service.exe and cjstartweb.exe
JP1/Service Support - DB Server	pdprcd.exe
JP1/Service Support - DB Cluster Service	pdsha.exe
JP1/Service Support - Task Service	jss_taskservice.exe

To Page Top