8.2.6 Registering the JP1/AJS3 service in the cluster software

(1) For JP1/AJS3 - Manager and JP1/AJS3 - Agent

Register the JP1/AJS3 service for the logical host in the cluster software that will be used. For details about how to register the service, see the documentation for the cluster software.

Information to set in the cluster software

• The service name you register in the cluster software is JP1_AJS2_logical-host-name, which is registered in the environment settings.

• Set the cluster software so that the secondary node can inherit the IP address and shared disk together with the service from the primary node. In addition, set the cluster software so that the application program is also inherited.

• Set the cluster software so that JP1/AJS3 starts after the secondary node has inherited the IP address and shared disk, and JP1/Base has started on the secondary node.

Starting and stopping the JP1/AJS3 services

• The JP1/AJS3 services registered in the cluster software must be started and stopped by using the cluster software.

Monitoring JP1/AJS3 operation

• The cluster software monitors whether the JP1/AJS3 service is running.

• When the following environment setting parameter is set, the JP1/AJS3 services are stopped whenever the embedded database service is stopped due to an irrecoverable error, so that the cluster software can detect the error.

  environment setting parameter	Explanation
  "RDBCHECKINTERVAL"=	Checks the connection with the embedded database service, and automatically stops the scheduler service whenever disconnection is detected.

  For details about these environment parameters, see 20.4 Setting up the scheduler service environment.

Cautionary notes:

• If you use queueless jobs, see 8.2.7 Setting up the queueless job execution environment.

• After setup required for cluster system operation has been completed, before you start the first JP1/AJS3 service, check whether JP1/AJS3 Database _JFn^# services have stopped. If JP1/AJS3 Database _JFn services are running, stop them, and then start the first JP1/AJS3 service. You do not need to stop JP1/AJS3 Database _JFn services again after cluster system operation has started.

• You do not have to register JP1/AJS3 Database _JFn^# services for the cluster software that will be used. If the JP1/AJS3 - Manager version is earlier than 10-00, you do not have to register JP1/AJS3 Database ClusterService _JFn^# services.

#:

_JFn is the embedded database setup identifier used by JP1/AJS3 services on a logical host.

To Page Top

(2) For JP1/AJS3 - Web Console

Register JP1/AJS3 - Web Console services in the cluster software to be used. For details about the procedure for registration, see the documentation for the cluster software to be used.

Before registering the services in the cluster software, in Windows Control Panel, open the Services administrative tool, and then change the Startup Type setting for the services to be registered from Automatic to Manual.

Services to be registered in the cluster software

Register the services in the cluster software as follows:

1. In Windows Control Panel, open the Services administrative tool.

2. In the Startup Type setting for the services to be registered, change Automatic to Manual.

   The following services must be registered in the cluster software:

   - JP1/AJS3 HTTP Server service

   - JP1/AJS3 Web Application Server service

   Change the Startup Type setting for these services from Automatic to Manual.

3. Register the JP1/AJS3 HTTP Server service and JP1/AJS3 Web Application Server service in the cluster software.

Cautionary notes

• Make sure that the secondary node can inherit the IP address and shared disk together with the JP1/AJS3 - Web Console services from the primary node.

• Make sure that the JP1/AJS3 - Web Console services start after the secondary node has inherited the IP address and shared disk.

• For other notes, see Installation Procedures and System Generation Precautions in the Release Notes.

Starting and stopping the services

The services registered in the cluster software must be started and stopped by using the cluster software.

Monitoring service operations

The cluster software monitors whether the services are running.

To Page Top