5.2 Installation prerequisites (for cluster systems)

Before installing JP1/AO in a cluster system, you must check and prepare the installation environment.

• Conflicting products

  Before you start installation of JP1/AO, uninstall the following conflicting products:

  • JP1/AJS3 - Manager

  • JP1/AJS3 - Agent

  • JP1/AJS2 - Manager

  • JP1/AJS2 - Agent

• OS and cluster software

  • The OS must be one of the following:

    • Windows Server 2008 R2 Enterprise

    • Windows Server 2008 R2 Datacenter

    • Windows Server 2012 Datacenter

    • Windows Server 2012 Standard

    • Windows Server 2012 R2 Datacenter

    • Windows Server 2012 R2 Standard

  • The cluster software must be Windows Server Failover Cluster (WSFC).

  • Patches and service packs required by JP1/AO and the cluster software must have been applied.

• Configuration

  • The environment of each server must be the same so that the same processing can be performed in the event of failover.

  • The cluster must be configured with two or more servers.

• Disk

  Files must be protected by a method such as a journaling file system so that data will not be lost in the event of a system shutdown.

• Network

  • Communication must be possible by using the IP address that corresponds to the host name (result of execution of the hostname command). It must not be possible for a program such as the cluster software to set a status that disables communication.

  • The correspondence between the host name and the IP address cannot be changed while JP1/AO is operating. It must not be possible for programs, such as the cluster software and name server, to change the correspondence.

  • The LAN board corresponding to the host name must have the highest priority in the network bind settings. Priority must not be given to any other LAN board, including a heartbeat LAN board.

• DNS operation

  Host names must have been entered without the domain name. Because JP1/Base does not support FQDN-format host names, FQDN-format host names cannot be used in JP1/AO either.

• Environment variables

  The JP1/Base environment variable JP1_HOSTNAME must not be set as a system environment variable or a user environment variable. This might prevent the service from starting.

• Shared disk

  To prevent data corruption on the active server in the event of failover, make sure that all the conditions listed below have been met. If the conditions are not met, problems might occur that prevent JP1/AO from working properly, including errors, data loss, and failure to start.

  • JP1/AO must not be installed on the shared disk.

  • A shared disk that can be carried over from the active server to the standby server must be available.

  • The shared disk must have been allocated before JP1/AO was started.

  • Allocation of the shared disk cannot be released during JP1/AO execution.

  • Allocation of the shared disk must be released after JP1/AO has stopped.

  • The shared disk must be locked so that it will not be accessed improperly by multiple servers.

  • Files must be protected by a method such as a journaling file system so that data will not be lost in the event of a system shutdown.

  • The contents of files must be protected and inherited in the event of a failover.

  • Forced failover must be available in the event that the shared disk is being used by a process at the time of a failover.

  • If JP1/AO needs to be started or stopped as part of the recovery process when failure is detected on the shared disk, you must be able to start or stop JP1/AO from the cluster software.

• Logical host name, IP address

  Check the conditions below so that recovery actions can be performed in the event of failure in a LAN board. If the conditions are not met, communication errors will prevent JP1/AO from working correctly until the LAN boards are swapped or failover to another server is achieved by the cluster software or some other means.

  • The name of the logical host must be 32 bytes or less.

  • Characters other than alphanumeric characters and hyphens (-) must not be used in the host name.

  • Inheritable logical IP addresses must be available for communications.

  • It must be possible for a unique logical IP address to be obtained from the logical host name.

  • The logical host names must be set in the hosts file or name server, and must be reachable via TCP/IP communication.

  • The logical IP addresses must be assigned before JP1/AO starts.

  • The logical IP addresses cannot be deleted during JP1/AO execution.

  • The correspondence between the logical host name and the logical IP address cannot change during JP1/AO execution.

  • The logical IP addresses must not be deleted until after JP1/AO has stopped.

  • In the event of a network failure, the cluster software must be able to manage the recovery process so that JP1/AO does not have to handle the recovery. If JP1/AO needs to be started or stopped as part of the recovery process, the cluster software must issue the start or stop request to JP1/AO.

• Port numbers

  The port number for connecting to the Web server must be the same in both the active server and the standby server. If the port numbers are not the same, the JP1/AO operations window will not be displayed in the Web browser when the servers are swapped at failover. If you change the port number, make sure that the new port number is the same on both the active server and standby server.

To Page Top