Installation Options

You now have two options when you install Process Manager. You can either:

  • Install just with LSF (outside of EGO).

  • Install as a Platform EGO service. This is the default.

    Tip:

    Note: Process Manager must be installed on one of the LSF management hosts. If failover is enabled, both the primary host and the failover host should belong to LSF management hosts.

Why should I install as an EGO service?

If you have an EGO cluster with LSF running, you can install as an EGO service. This transfers control of Process Manager to EGO through the Platform Management Console. The primary advantage is the ability to fail over Process Manager server to another host.

Default installation

For a default installation on either Windows or UNIX, follow the applicable installation instructions in the following guides:


Book

File

Installing Platform Process Manager (Windows)

ppm_install_windows.pdf

Installing Platform Process Manager (UNIX)

ppm_install_unix.pdf


If you have chosen the default installation in a Windows environment, you may want to set up failover.

Set up Windows failover (default installation)

If you are installing with the default installation option and want to enable Windows failover, you must enable JFD failover on Windows.

  1. Decide which host will be the primary host, and which host will be the fail-over host. For example, the primary host is HOSTP, the failover host is HOSTF.

  2. Install LSF cluster. Both HOSTP and HOSTF should belong to the cluster. If you already have an LSF cluster installed, add HOSTP and HOSTF to the cluster.

  3. Make sure LSF administrator is in Administrators group on both primary host (HOSTP) and failover host (HOSTF), and has all required privileges:

    • Act as part of the operating system

    • Debug programs

    • Increase quotas

    • Log on as a service

    • Replace a process level token

    • Back up files and directories

    • Restore files and directories

    • Bypass traverse checking

  4. Make sure the LSF administrator has read/write permission on %JS_HOME% and %LSF_TOP%\conf\passwd.lsfuser.

  5. Start to install Process Manager on the primary host, but make sure to specify a shared directory as the Destination Folder. The path should use a UNC (Universal Naming Convention), not a mapped drive. For example, %JS_HOME% could be \\HOSTS\ppm7.

  6. By default, Process Manager is installed as a Windows service. After the installation is complete, change the startup type of Process Manager from Automatic to Manual to prevent it from being started up automatically when the machine reboots. From the Platform Management Console, stop the Process Manager service first if it is started.

  7. Modify js.conf to enable failover.

    JS_HOST = HOSTP
    JS_FAILOVER = true
    JS_FAILOVER_HOST =  HOSTF
    JS_FAILOVER_QUEUE = jfd_failover

    Make sure LSF_ENVDIR is correctly specified.

  8. Modify/Add system environment variables on both HOSTP and HOSTF.

    1. Add the following paths:

      JS_ENVDIR=\\HOSTS\ppm7\conf
      JS_HOME=\\HOSTS\ppm7
      JS_SERVERDIR=\\HOSTS\ppm7\7\etc
      JS_VERSION=7
    2. Update the PATH environment variable to include %JS_HOME%\7\bin

    On the primary host, all environment variables were already set during installation.

  9. Configure a queue dedicated for jfd failover in lsb.queue.

    1. Make sure the QUEUE_NAME matches the name specified in JS_FAILOVER_QUEUE in the js.conf file.

      Begin Queue
      QUEUE_NAME   = jfd_failover
      PRIORITY     = 100
      NICE         = 10
      PREEMPTION   = PREEMPTIVE
      RERUNNABLE   = yes
      REQUEUE_EXIT_VALUES = 1 2 3 4 5 6 7 9 127 128 255
      JOB_CONTROLS = TERMINATE [jadmin stop]
      DESCRIPTION  = Dedicated queue for Process Manager server with\ fail-over capability.
      End Queue
    2. Run badmin reconfig to enable the queue.

    RERUNNABLE = yes: JFD runs as a rerunnable job. If it is not set to yes, failover will not work.

    PREEMPTION = PREEMPTIVE: Makes jfd_failover queue a preemptive queue. Even if JFD is submitted to LSF as a regular job, it should have high priority. When JFD and other jobs compete for the same resource (for example, a job slot), it should be able to preempt low-priority jobs.

    REQUEUE_EXIT_VALUES = 1 2 3 4 5 6 7 9 127 128 255: JFD is automatically requeued when it exits with the specified exit values:

    • Exit value 1 or 9, JFD is manually killed via command or through task manager.

    • Exit value 2,3,4,5,6,7,127,128,255, JFD exits due to daemon failure.

    JOB_CONTROLS = TERMINATE [jadmin stop]: When JFD is being terminated with bkill, the actual action will be jadmin stop so the JFD can exit cleanly.

    The JFD will not be requeued in the following situations:

    • JFD fails to start due to license failure.

    • JFD fails to start because another JFD is running on the same host and listening on the same port.

    • JFD fails to start because another JFD is running on a different host under the same %JS_HOME%.

    • JFD fails to start due to certain configuration errors (such as wrong LSF_ENVDIR in the js.conf file).

Control the JFD

  • Use jadmin start to start JFD. You can only run this command successfully when failover is enabled.

  • Run jadmin stop to stop jfd. Do not manually kill the jfd process.