2.9.5 Settings for running a logical host in a non-cluster environment

(a) Preparing the logical host environment

Provide a disk area and IP address for the logical host to create a logical host environment.

• Disk area for the logical host

  Create storage directories on the local disk for the files that will be used by JP1/Advanced Shell separately from the directories used by the physical host and the JP1-series products on other logical hosts.

• IP address for the logical host

  Allocate in the OS the IP address that will be used by JP1/Advanced Shell for the logical host. It can be a real IP address or an alias IP address. Make sure that the IP address can be uniquely identified from the logical host.

  The prerequisites for these tasks are the same as for operation in a cluster system. However, the conditions related to cluster software do not apply because JP1/Advanced Shell is not run in a cluster environment.

In 2.9 Running in a cluster configuration, replace the information about shared disk and logical IP address with the disk area and IP address allocated above for the logical host.

• Estimating performance

  When you estimate performance, determine whether JP1/Advanced Shell can be run as a system in terms of the following:

  • Determine whether there are enough resources to run multiple JP1-series products in the system. If there are not enough resources, the system might not function correctly or adequate performance might not be realized.

(b) Specifying environment information for the logical host

Specify environment information for the logical host using the same procedure as for the active server in a cluster system. For details about the specification of environment information for cluster operation, see 2.9.2 Specifying environment information for cluster operation. Note that in a cluster system, the environment information must be specified on both servers involved in system switchover, but for a logical host that is run in a non-cluster environment, specify the environment information only on the server on which JP1/Advanced Shell will be run.

(a) In AIX

• Setting up the automatic start function at system startup

  You use the following mkitab command to have the user-reply functionality's management daemon start automatically at the time of system startup:

  mkitab "record-of-user-reply-functionality-management-daemon-for-logical host:2:wait:/opt/jp1as/sbin/adshmdctl -h logical-host-name start"

  Set the user-reply functionality's management daemon for the logical host to start after the logical host services of linked JP1-series products have started. For example, to have JP1/Base and JP1/IM - Manager on the logical host start automatically in this order, execute mkitab commands as follows:

  mkitab -i record-of-JP1-Base-for-logical-host "record-of-JP1/IM-Manager-for-logical-host:2:wait:/etc/opt/jp1cons/jco_start.cluster logical-host-name"
  mkitab -i record-of-JP1/IM-Manager-for-logical-host "record-of-user-reply-functionality-management-daemon-for-logical host:2:wait:/opt/jp1as/sbin/adshmdctl -h logical-host-name start"

• Setting up the automatic termination function at system shutdown

  To have the user-reply functionality's management daemon terminate automatically at the time of system shutdown, you must edit /etc/rc.shutdown to add the following code so that the user-reply functionality's management daemon for the logical host stops before any of the logical host services of linked JP1-series products are stopped:

  test -x /opt/jp1as/sbin/adshmdctl && /opt/jp1as/sbin/adshmdctl -h logical-host-name stop
      :
  termination processing for services of linked JP1-series products
      :

(b) In Linux

• Creating automatic start and stop scripts

  Create automatic start and stop scripts for the logical host in the /etc/rc.d/init.d directory. The following shows an example:

  #!/bin/sh
   
  JP1_HOSTNAME=logical-host-name
   
  case $1 in
  'start')
        if [ -x /opt/jp1as/sbin/adshmdctl ]
        then
                /opt/jp1as/sbin/adshmdctl -h $JP1_HOSTNAME start
                touch /var/lock/subsys/lock-file-name
        fi
        ;;
  'stop')
        if [ -x /opt/jp1as/sbin/adshmdctl ]
        then
                /opt/jp1as/sbin/adshmdctl -h $JP1_HOSTNAME stop
                rm -f /var/lock/subsys/lock-file-name
        fi
        ;;
  esac
   
  exit 0

  Specify for the lock file name the symbolic link name created for automatic stop without the leading numeric part (KXX part). For example, if the symbolic link name for automatic stop is K01_JP1_AS_CLUSTER, specify _JP1_AS_CLUSTER.

• Creating a symbolic link for automatic startup

  Create a symbolic link to the created automatic start and stop scripts in the /etc/rc.d/rcN.d directory (N indicates the execution level at startup). You must name the symbolic link in such a manner that the user-reply functionality's management daemon is started after the logical host services of the linked JP1-series products have been started. For details about how to create symbolic links, see 2.8.3(1) Starting and terminating the user-reply functionality's management daemon automatically.

• Creating a symbolic link for automatic termination

  Create a symbolic link to the created automatic start and stop scripts in the /etc/rc.d/rcN.d directory (N indicates the execution level at termination). You must name the symbolic link in such a manner that the user-reply functionality's management daemon is terminated before the logical host services of the linked JP1-series products are stopped. For details about how to create symbolic links, see 2.8.3(1) Starting and terminating the user-reply functionality's management daemon automatically.

Note that the user is responsible for creating the automatic start and stop scripts for the logical host services of the linked JP1-series products and the symbolic links to the created automatic start and stop scripts. For details about the names of automatic start and stop scripts for the logical host services of linked JP1-series products and the names of symbolic links, see the manuals for the linked JP1-series products.

(c) In HP-UX

• Creating automatic start and stop scripts

  Create the automatic start and stop scripts for the logical host in the /sbin/init.d directory. The following shows an example:

  #!/bin/sh
   
  ## Set Environment-variables
  PATH=/sbin:/bin:/usr/bin:/opt/jp1as/sbin
  export PATH
  JP1_HOSTNAME=logical-host-name
   
  case $1 in
  start_msg)
        echo "Start Advanced Shell - adshmd $JP1_HOSTNAME"
        ;;
  stop_msg)
        echo "Stop Advanced Shell - adshmd $JP1_HOSTNAME"
        ;;
  'start')
        if [ -x /opt/jp1as/sbin/adshmdctl ]
        then
                /opt/jp1as/sbin/adshmdctl -h $JP1_HOSTNAME start
        fi
        ;;
  'stop')
        if [ -x /opt/jp1as/sbin/adshmdctl ]
        then
                /opt/jp1as/sbin/adshmdctl -h $JP1_HOSTNAME stop
        fi
        ;;
  esac
   
  exit 0

• Creating a symbolic link for automatic startup

  Create a symbolic link to the created automatic start and stop scripts in the /sbin/rc2.d directory. You must name the symbolic link in such a manner that the user-reply functionality's management daemon is started after the logical host services of the linked JP1-series products have been started. For details about how to create symbolic links, see 2.8.3(1) Starting and terminating the user-reply functionality's management daemon automatically.

• Creating a symbolic link for automatic termination

  Create a symbolic link to the created automatic start and stop scripts in the /sbin/rc1.d directory. You must name the symbolic link in such a manner that the user-reply functionality's management daemon is terminated before the logical host services of the linked JP1-series products are stopped. For details about how to create symbolic links, see 2.8.3(1) Starting and terminating the user-reply functionality's management daemon automatically.

Note that the user is responsible for creating the automatic start and stop scripts for the logical host services of the linked JP1-series products and the symbolic links to the created automatic start and stop scripts. For details about the names of automatic start and stop scripts for the logical host services of linked JP1-series products and the names of symbolic links, see the manuals for the linked JP1-series products.

(d) In Solaris

• Creating automatic start and stop scripts

  Create the automatic start and stop scripts for the logical host in the /etc/init.d directory. The following shows an example:

  #!/bin/sh
   
  JP1_HOSTNAME=logical-host-name
   
  case $1 in
  'start')
        if [ -x /opt/jp1as/sbin/adshmdctl ]
        then
                /opt/jp1as/sbin/adshmdctl -h $JP1_HOSTNAME start
        fi
        ;;
  'stop')
        if [ -x /opt/jp1as/sbin/adshmdctl ]
        then
                /opt/jp1as/sbin/adshmdctl -h $JP1_HOSTNAME stop
        fi
        ;;
  esac
   
  exit 0

• Creating a symbolic link for automatic startup

  Create a symbolic link to the created automatic start and stop scripts in the /etc/rc2.d/ directory. You must name the symbolic link in such a manner that the user-reply functionality's management daemon is started after the services of the linked JP1-series products have been started. For details about how to create symbolic links, see 2.8.3(1) Starting and terminating the user-reply functionality's management daemon automatically.

• Creating a symbolic link for automatic termination

  Create a symbolic link to the created automatic start and stop scripts in the /etc/rc0.d/ directory. You must name the symbolic link in such a manner that the user-reply functionality's management daemon is started after the services of the linked JP1-series products have been started. For details about how to create symbolic links, see 2.8.3(1) Starting and terminating the user-reply functionality's management daemon automatically.

Note that the user is responsible for creating the automatic start and stop scripts for the logical host services of linked JP1-series products and the symbolic links to the created automatic start and stop scripts. For details about the names of automatic start and stop scripts for the logical host services of linked JP1-series products and the names of symbolic links, see the manuals for the linked JP1-series products.