Learn more about Platform products at http://www.platform.com

[ Platform Documentation ] [ Title ] [ Contents ] [ Previous ] [ Next ] [ Index ]



Installing LSF Desktop Support


This chapter describes how to install LSF desktop support. To ensure a complete and error-free installation, use the Installation Overview.

Contents

[ Top ]


Installation Overview

These are the steps you complete when installing LSF desktop support components.

To install all components:

[ Top ]


Converting the LSF Server Host to a Desktop Server

These instructions explain how to convert an LSF server host to a desktop server, once:

You must follow these instructions for each LSF server host to convert to a desktop server.

This process:

To convert to a desktop server:

  1. Prepare the LSF server host for conversion to a desktop server:
    1. LSF desktop support requires dedicated Web servers (Apache and Tomcat). If you have either or both of those servers installed on this host, LSF desktop support can use them, provided they use the correct ports. LSF desktop support requires that Apache and Tomcat use port 80. If you do not have existing Web servers on this host, the installation script installs them.
    2. If you have Web servers currently running on this host, shut them down.
    3. Make sure no other applications are using port 80. These must be dedicated for use by the desktop server itself.
  2. Untar the software distribution package in the directory on the LSF server host where you will install the desktop server. For example:

    cd AC_INSTALL
    zcat lsf7Update2_desktop_linux-x86.tar.Z | tar xvf -

  3. Specify the configuration parameters. On the LSF server host, in the install directory, edit the file install.config: (The entries can be in any order, and the actual order in the sample install.config may vary.)
    • LSF_ENVDIR parameter. Required. Specify the location of the LSF configuration file lsf.conf, which is a shared file. For example:
      LSF_ENVDIR="/usr/local/lsf/mnt/conf"
      
    • ACH_TOP parameter. Required. Specify the full path to the top-level installation directory where you want the desktop server software installed. For example:
      ACH_TOP="/usr/local/lsfac"
      

      We recommend that ACH_TOP be within the local file system.

    • STATSDIRECTORY parameter. Required. Specify the path to the directory where you want all job completion logs stored. This is also the location where directory service connection logs are stored if directory services is enabled. It is recommended that this be a shared directory (for example NFS).
    • SERVER_NAME parameter. Optional. Specify a valid DNS name or IP address for your desktop server if it is different from the specified host name. If your host does not have a registered DNS name, enter its IP address here. This is the name sent back to Web clients. For example:
      SERVER_NAME=achost.lsf.acme.com
      
    • JAVA_HOME parameter. Optional. If Java Runtime Environment (J2RE) is already installed on this host, and you want to use it for LSF desktop support, specify the directory where it is installed. By default, achinstall installs JRE under ACH_TOP/j2sdk1.4.1_01. For example:
      JAVA_HOME="/usr/local/j2sdk1.4.1_01"
      
    • APACHE_HOME parameter. Optional. If an Apache server is already installed on this host, and you want to use it for LSF desktop support, change it to use port 80 and shut it down until the installation is completed. Then, in the APACHE_HOME parameter, specify the directory where it is installed. For example:
      APACHE_HOME="/usr/local/apache"
      
    • TOMCAT_HOME parameter. Optional. If a Tomcat server is already installed on this host, and you want to use it for LSF desktop support, change it to use port 80 and shut it down until the installation is completed. Then, in the TOMCAT_HOME parameter, specify the directory where it is installed. For example:
      TOMCAT_HOME="/usr/local/jakarta-tomcat-4.1.30-LE-jdk14"
      
    • USER_NAME/GROUP_NAME parameter. Optional. Specify a user or a group name if you want the Web servers to run under a user or group name other than nobody. For example:
      USER_NAME=acweb
      
    • DIRECTORYSERVICE parameter. Specifies whether this desktop server is also a Directory Services host. If you are implementing automatic load balancing, you must specify yes for this parameter for at least one server, and no for the remaining servers.

      If you are not implementing automatic load balancing, let this value default to yes. For example:

      DIRECTORYSERVICE=yes
      
    • CONFIGDIRECTORY parameter. Optional. Specifies the path to where the configuration files (SEDConfig.xml and MED.lst) used by Directory Services are located. Defaults to ACH_TOP/config. For example:
      CONFIGDIRECTORY="/usr/local/config"
      
    • AC_SERVER_LIST parameter. Optional. Specifies a list of desktop servers to which it sends desktop clients. If you are implementing automatic load balancing, and this server is a Directory Services host, specify the list of fully qualified (for example, DNS resolvable) names for all desktop servers to which this Directory Service host will refer desktop clients, and gather statistics from. Separate the names with a space. For example:
      AC_SERVER_LIST="test.acme.com test1.acme.com"
      

      If you are not implementing automatic load balancing, you do not need to specify a value here. The value defaults to this desktop server.

    • DIGESTAUTH parameter. Specifies whether to configure digest authentication. If digest authentication is used, all requests to the desktop server are authenticated. For details, see Authenticating Users and Controlling User Access. The default value of this parameter is no.
    • ACCESS_CONTROL parameter. Optional. Specifies the permission settings of multiple directories and files. Possible values are yes or no. The default value is no. If ACCESS_CONTROL is set to yes, global read and write access is revoked, and only owners can access files and directories, which implies that lsfadmin may not be able to view job-related files.
  4. Save the install.config configuration file.
  5. Install the desktop server software:

    Change to the LSF desktop support installation directory (where the files reside after you untar the package) and run the following as root:

    cd AC_INSTALL
    ./achinstall -f install.config
    
    


    If your LSF cluster enables EGO management of LSF daemons, you must run the following command to log on to EGO before runnnig achinstall:
    egosh user logon -u Admin -x Admin

  6. If you want to set the default as no file caching of jobs on desktop clients, then once the installation is complete, edit /etc/med.conf, and add the following line:
    LSB_MED_CACHEFILE_DEFAULT=No
    

    For additional information about LSB_MED_CACHEFILE_DEFAULT and cache control, see Desktop Server Configuration Settings.

  7. Repeat the above steps for each LSF server host where you want to install the desktop server.

[ Top ]


Enabling Desktop Support on LSF

When the desktop server is defined, you need to enable LSF desktop support on the LSF master host.

To enable LSF desktop support:


If your LSF cluster enables EGO management of LSF daemons, you must run the following command to log on to EGO before runnnig acsetup:
egosh user logon -u Admin -x Admin

  1. Log on as root or the primary LSF administrator:
  2. Run the following command:

    acsetup

  3. When prompted, specify the location of LSF_ENVDIR, which is the location of lsf.conf.
  4. When prompted, specify a list of the desktop server host names, separating the names with commas (,). The names you specify here must exactly match the names specified in lsf.cluster. For example, if the full DNS name is specified in lsf.cluster, you must specify the full DNS name here.

Changes acsetup makes

When you run acsetup, it does the following:

  1. Ensures you are a primary LSF administrator
  2. Adds the following parameters to lsf.conf:
    • LSB_CHUNK_NO_RLIMIT=Y
    • LSB_MBD_CONNTIMEOUT=60
    • LSF_ENABLE_EXTSCHEDULER=Y
  3. Adds the following parameters to med.conf:
    • LSB_SBD_CONNTIMEOUT=60
    • LSB_SBD_READTIMEOUT=300
  4. Adds the parameter MAX_JOB_NUM to lsb.params.
  5. Adds a new host type for LSF desktop support called AC to lsf.shared.
  6. Adds a new resource called activecluster to lsf.shared.
  7. Updates LSF host configuration in lsf.cluster.clustername.
  8. Creates a host limit for LSF desktop support in lsb.resources. This specifies the number of active jobs that can run on each desktop server. By default, this is set to fifty. For example: SLOTS=50. This should be set to the maximum number of desktop clients that will be connecting to a particular desktop server.
  9. Creates the default LSF desktop support queue AC_QUEUE in lsb.queues.

    Review the settings of the following parameters in AC_QUEUE:

    • RUNLIMIT is the expected application run time. For example, if the average run time is 30 minutes and should never exceed 180 minutes, it is set to:
      RUNLIMIT=30 180
      

      If only one value is specified, then it is the maximum run time.


      Note: The value of RUNLIMIT in the queue is scaled based on the CPU factor of the execution host. In Platform LSF desktop support, it is scaled by the speed of the desktop server rather than by the speed of the desktop client. Therefore, in the queue, you should set DEFAULT_HOST_SPEC=pc_host_model. For additional information refer to the Platform LSF Reference.

    • CHUNK_JOB_SIZE is the number of jobs queued on the desktop server from the LSF master for each job slot. Therefore, if the expected run time of jobs is low, the value of CHUNK_JOB_SIZE should be high; if the expected run time of jobs is high, the value of CHUNK_JOB_SIZE should be low.

      The total number of jobs that can be queued on the desktop server from the LSF master is SLOTS (defined in lsb.resources) * CHUNK_JOB_SIZE (defined in lsb.queues).

  10. Reconfigures LIM.
  11. Restarts mbatchd.

[ Top ]


Excluding Desktop Servers from LSF Queues

If LSF users in your organization typically specify that their LSF jobs can run on any available LSF host (specifying -R "type==any" in a bsub command), you may need to configure your LSF queues to exclude the desktop servers from the list of eligible hosts, to avoid running standard LSF jobs on an LSF desktop support host.

To exclude desktop servers:

  1. Edit lsb.queues for this cluster.
  2. In the HOSTS parameter for each LSF queue, exclude the desktop servers. For example:

    HOSTS=~AChost1 ~AChost2

  3. Reconfigure the cluster by running badmin reconfig.

[ Top ]


Checking Web Server Availability

The Apache and Tomcat Web servers should have been started by achinstall. You can verify that they are running before you proceed.

To verify Apache Web server is running:

If this is unsuccessful, check ACH_TOP/apache/logs for details.

To verify Tomcat Web server is running:

  1. Open a Web browser at: http://host_name
  2. Click both links.

If either or both links open unsuccessfully, check ACH_TOP/jakarta-tomcat- 4.1.30-LE-jdk14/logs for details.

[ Top ]


Enabling Caching on the Desktop Client

Overview

The desktop client transparently uses Microsoft Explorer's caching mechanism to manage the cache. It uses the Microsoft Windows Internet Explorer's cache directory to upload and download files. In Windows 2000, Windows 2003 Server, and Windows XP, the desktop client runs as the LocalSystem account.

To enable file caching on the desktop client:

  1. Specify Write permission for the Everyone account running on all desktop clients on the cache folder. (The default permissions are Read & Execute, List Folder Contents, and Read.)


    Tip: The location of the cache is defined by the following registry key:
    HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\
    CurrentVersion\Explorer\User Shell Folders\Cache
    .

  2. Set the caching policy. It is defined by the following registry key:
    HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\
    CurrentVersion\InternetSettings\SyncMode5.
    
    


    Note: If SyncMode5 does not exist in HKEY_USERS\.DEFAULT\Software\
    Microsoft\Windows\CurrentVersion\InternetSettings,
    manually add it as a REG_DWORD registry key.

    Set the REG_DWORD value to one of the following:

    Value Option in Internet Explorer Description
    0
    Never
    Never checks whether a newer version of a page exists since it was last accessed. Always obtains a page from the cache.
    2
    Every time you start Internet Explorer
    Checks whether a newer version of a page exists only if the page was last accessed during a previous session of Internet Explorer or on a previous day. Otherwise, obtains a page from the cache.
    3
    Every visit to the page
    Every visit to a page, the browser checks for a newer version of a stored page. Never obtains a page from the cache.
    4
    Automatically
    Checks whether a newer version of a page exists only if the page was last accessed during a previous session of Internet Explorer or on a previous day. Over time, if some images on the page are changing infrequently, Internet Explorer checks for new images even less frequently. Otherwise, obtains a page from the cache.


    Tip: You should set SyncMode5 to 3, which means that every visit to the page, the browser checks for a newer version.

  3. Restart the desktop client so that the change in settings will take effect.

[ Top ]


Installing the Desktop Client

The desktop client is the component that resides on desktop client computers distributed throughout your installation. These are the computers where the jobs are run.

Overview

All desktop client users run the installation on their machines, and users are not prompted for any installation options. Installation options are read from a file containing the configuration values for their desktop clients. This method requires that you edit a setup file prior to the installation. The desktop client user does not need to specify any values during the installation. This method enables you change the default configurations for large numbers of desktop clients.

If you have a firewall

If you are using a firewall, the desktop client service sed.exe must be granted privileges to access the Internet.

If you have auto-locking enabled on your firewall, you must allow sed.exe to access the Internet at all times. Otherwise, the desktop client will not work. Some firewalls have features that disable Internet access after some idle time or when a screen saver runs. Check your firewall.

To install the desktop client:

  1. Download the file sedsetup.cmd from ftp.platform.com. Place it in a central location.
  2. Edit sedsetup.cmd and define the following parameters:

    Parameter Optional/
    Required
    Description
    INSTALLDIR
    Optional
    If you want to change the default directory for the program files on the desktop client, specify the appropriate directory. The default is Program Files\Platform Computing\LSF desktop support. For example:
    INSTALLDIR=Program Files\Platform Computing\
    LSF_AC

    If you have machines with different locations for the \Program Files folder, for example C:\ or D:\, you can comment out this parameter by placing a rem before set INSTALLDIR, and the setup program automatically detects the correct directory. If you comment out this directory, you also need to remove the following INSTALLDIR=\%INSTALLDIR%\" (including the space after the quote character (")) from the line at the end of sedsetup.cmd.
    MEDURL.
    Required
    Specifies a default URL where the desktop client can go to request jobs if the Directory Services host is not available. For example:
    MEDURL=http://host_name/servlet/SedSoap
    MEDDSURL
    Required
    Specifies the URL for the Directory Services. This is the URL where the desktop client gets its configuration. If directory services is used, this should point to the directory services location. For example:
    MEDDSURL=http://host_name/servlet/DynamicSEDConfig
    ENABLEDISKQUOTA
    Optional
    For Windows 2000 with NTFS only. For more information, see Windows 2000 with NTFS.
    SEDUSERDISKQUOTA
    Optional
    For Windows 2000 with NTFS only. For more information, see Windows 2000 with NTFS.
    SEDUSERDISKQUOTARATIO
    Optional
    For Windows 2000 with NTFS only. For more information, see Windows 2000 with NTFS.
    SEDPOLLINTERVAL
    Optional
    If you want to change the amount of time between requests for work from an idle desktop client, specify the time the desktop client waits before requesting another job. Use this value to reduce network congestion at the desktop server. Specify the time in seconds. The default is 300 seconds, which is 5 minutes.For example:
    SEDPOLLINTERVAL=900
    SCREENSAVERMODE
    Obsolete
    This parameter is obsolete and has been replaced by SEDMode. The following information is included for backward compatibility only.
    • Setting this to Off is equivalent to setting SEDMode to Always.
    • Setting this to On is equivalent to setting SEDMode to Screensaver.
    For additional information, see SEDMode.
    • If SCREENSAVERMODE is not defined, then the value of SEDMode is used.
    • If SCREENSAVERMODE is defined, then the value of SEDMode is ignored and a warning is logged in the SED log file.
      Recommended value: Set to Off so that jobs can always run on the desktop.
    SEDSYSTRAYINSTALL
    Optional
    Specify whether to install the desktop client system tray during installation. Specify Yes or No. Any character other than Yes or No is interpreted as No. The default is Yes. For example:
    SEDSYSTRAYINSTALL=Yes
    Recommended value: Set to No so that the desktop client system tray is not installed.
    SEDSYSTRAYINSTSTART
    Optional
    Applies only when SEDSYSTRAYINSTALL is set to Yes. Specify whether to start the desktop client system tray after installation. Specify Yes or No. Any character other than Yes or No is interpreted as No. The default is Yes. For example:
    SEDSYSTRAYINSTALL=Yes
    Recommended value: Set to No, since the desktop system tray is not installed.
    SEDSYSTRAYSHORTCUT
    Optional
    Applies only when SEDSYSTRAYINSTALL is set to Yes. Specify whether to add a system tray shortcut to the program menu. Specify Yes or No. Any character other than Yes or No is interpreted as No. The default is Yes. For example:
    SEDSYSTRAYSHORTCUT=Yes
    Recommended value: Set to No, since the desktop system tray is not installed.
    SEDUSERNAME
    Optional
    Specifies the user name for the desktop client user. This can be a local user name or an existing domain user name, in the format domain\user. The default user name is seduser.
    SEDUSERCRED
    Optional
    Specifies the user credential for the desktop client user. To obtain the user credential, run the SEDPassword command, as described in Generating user credentials. The credential is used to create the password for a new desktop client user, and to authenticate the password of an existing user. The installer does not check the validity of the password.
    SEDUSERLOCALGROUP
    Optional
    Specify the local group the new user is to join. This applies only when the user does not currently exist. For an existing user ID, this parameter is ignored.
    SEDDisableCache
    Optional
    Indicates whether the desktop client is allowed to write to the cache. Valid values are yes, true, false, and no (the default), case insensitive.
    • yes or true indicates that the desktop client does not write to the cache, however it still retrieves valid files from the cache.
    • no or false indicates that the desktop client can write to the cache. However, when submitting a job, the user can disable writing to the cache for a specific file. For additional information, refer to the Platform LSF Desktop Support User's Guide.
    Note that the LSB_MED_CACHEFILE_DEFAULT parameter in med.conf prevents all desktop clients connecting to a specific desktop server from caching files. For additional information, see Desktop Server Configuration Settings.
    MEDUSERNAME
    Optional
    Indicates the user name for authentication to the desktop server.
    MEDUSERCRED
    Optional
    Indicates the user credential for authentication to the desktop server. To obtain the user credential, run the SEDPassword command. The installer does not check the validity of the password.
    SEDModeSelectableByUser
    Optional
    Indicates whether the desktop client mode is configurable by the desktop client user. Valid values are yes or no. Otherwise, the default value is used. Default value is yes (case insensitive). For additional information, see Setting the conditions for a desktop client requesting work.
    SEDMode
    Optional
    Indicates the desktop client mode. Valid values are Screensaver (the default), Always, Idle, and Logon (case insensitive). Otherwise, the default value is used. The default value is Screensaver. For additional information, see Setting the conditions for a desktop client requesting work.
    SEDConsoleIdle
    Optional
    If the desktop client is running in idle mode, this parameter specifies the period of keyboard or mouse inactivity in seconds before the desktop client can request work. The default is 900 seconds (15 minutes). Any integer above 300 seconds is a valid value. Otherwise, the default value is used, and a warning is logged in the SED log file.
    SEDSuspendOnBattery
    Optional
    Indicates whether jobs can run if the desktop client is running on a machine using battery power (e.g. a laptop computer). If this parameter is set to Yes, then if the desktop client switches to battery power:
    • Any running job is terminated and the desktop server is notified of the termination
    • The desktop client cannot start running jobs

Windows 2000 with NTFS

The following parameters are optional and applicable only to Windows 2000 with NTFS. If you want to limit the amount of disk space the desktop client can use while running work, set the following parameters as described below:

Parameter Description
ENABLEDISKQUOTA
Enable disk quota by ensuring the value is set to Yes. This specifies to use the values for SEDUSERDISKQUOTA and/or SEDUSERDISKQUOTARATIO. If you specify a value for one of the parameters, that value is used. If you specify a value for both parameters, the value that is greater is used. If you do not specify a value for either parameter, the defaults apply, and the value that is the greater of the two is used. For example:
ENABLEDISKQUOTA=Yes S
Recommended value: Set to No so that disk quota, specified by either SEDUSERDISKQUOTA or SEDUSERDISKQUOTARATIO, described below, is not used.
SEDUSERDISKQUOTA
Set the maximum number of megabytes the desktop client can use by specifying the number in MB. The default is 100 MB. For example:
SEDUSERDISKQUOTA=500
SEDUSERDISKQUOTARATIO
Set the maximum percentage free disk space the desktop client can use by specifying a number from 1 to 100. For example, 50% would be specified as 50. The default is 33%. For example:
SEDUSERDISKQUOTARATIO=50


Note: If both the SEDUSERDISKQUOTA and SEDUSERDISKQUOTARATIO parameters are defined, the parameter with the greater value is used.

  • Save sedsetup.cmd.
  • Make sure that sedsetup.cmd resides in the same directory containing lsf7.0_desktop.msi, from which the users install LSF desktop support. If you changed the name or location of lsf7.0_desktop.msi, you can modify the SETUPMSI variable in sedsetup.cmd to reflect the change.
  • Instruct the users to run sedsetup.cmd to install the desktop client software.

    Generating user credentials

    Secure passwords

    LSF desktop support increases security with HP ProtectTools Authentication Services. Therefore, if you are using a secure password when you run SEDPassword.exe, you must prefix it with <SE>\.

    For example, if the password is my_password, you run:

    SEDPassword "<SE>\my_password"

    To generate user credentials:

    1. Locate the file SEDPassword.exe.
    2. Run SEDPassword.exe as follows:

      SEDPassword.exe password

      where password is the correct password for the user ID you specify for the SEDUSERNAME parameter. SEDPassword.exe generates an authorization string you will use in the SEDUSERCRED parameter for the silent installation of the clients. For example:

      C:\lsf_desktop7.0>SEDPassword.exe barney
      Encrypted length: 8
      Encrypted data:
      0xf8, 0x7b, 0xd7, 0x18, 0x29, 0xf4, 0xf6, 0x7d
      
    3. Copy the text in the Encrypted data and paste it into the SEDUSERCRED parameter as follows:

      SEDUSERCRED=0xf8, 0x7b, 0xd7, 0x18, 0x29, 0xf4, 0xf6, 0x7d

    Setting up screen-saver mode

    To run the desktop client in screen-saver mode, you can use any screen saver. However, the desktop client must have a screen saver enabled. In a corporate network environment, an IT administrator can often enable screen savers on all desktop clients. However, in an ISP environment, the desktop client user may need to enable the screen saver.

    If you specified Screensaver in sedsetup.cmd during installation, then the desktop client mode is already set to Screensaver and the desktop client screen saver is set as the default screen saver for the user who installs the desktop client.

    When screen-saver mode is enabled on the desktop client, the user can choose which mode to run in by selecting an option in the Details dialog box.

    If you do not enable screen-saver mode during the silent installation of the desktop client, a user can later enable a screen saver and select screen-saver mode as required.

    To change the system tray icon:

    1. Create five bitmap files with the following attributes:
      • Each file is saved in .BMP format.
      • The image in each file uses the 256 Colors color setting.
      • The image in each file is 138 pixels by 138 pixels.
      • The files should have the following names (each name describes the circumstance in which it will be used):

      This file Is used when...
      sed_idle.bmp
      The desktop client is not currently running a job for LSF desktop support.
      sed_complete.bmp
      The job that was running on the desktop client has completed.
      sed_running.bmp
      A job is currently running on the desktop client.
      sed_disabled.bmp
      LSF desktop support is disabled
      sed_error.bmp
      There is an error.

    2. Place all files in the LSF desktop support directory on each desktop client, for example: C:\Program Files\Platform Computing\LSF desktop support.


      Note: The customized system tray icon loads only if all five bitmap files exist and meet the requirements described above.

    To replace these bitmap files on multiple desktop clients, either:

    [ Top ]


    Install LSF Desktop Reports

    At least one LSF desktop server (MED) host is installed correctly.

    Contents

    Top-level directories

    The reporting feature resides in the perf directory, which is a subdirectory of the top- level LSF installation directory. This document uses LSF_TOP to refer to the top-level LSF directory and LSF_TOP/perf to describe the perf directory.

    Download and deploy the LSF desktop reports package

    1. Obtain the LSF desktop reports package from Platform Computing.

      The LSF desktop reports package is only available for Linux hosts.

    2. Copy the LSF desktop reports package into a temporary directory.

      For example, copy the package into your home directory.

      cp lsf_desktop_7Update2_reports.tar ~
      
    3. Extract the package to the temporary directory. For example:
      cd ~
      tar xvf lsf_desktop_7Update2_reports.tar
      

      The LSF desktop reports content is installed in the ego subdirectory under your temporary directory.

    4. Copy the ego subdirectory to the top level EGO directory. For example:
      cd ../EGO_TOP
      cp -r ~/ego .
      

      The installation is successful if the following file exists: LSF_TOP/perf/ego/version/lib/perf_lsfdesktop_loader.jar.

    5. Create the LSF desktop data schema for your database.

      For example, for the Derby database, run the following commands to create the schema:

      ij.sh
      ij> connect 'jdbc:derby://database_host:port_number/app';
      ij> run 
      '$LSF_TOP/perf/ego/version/DBschema/Derby/lsfdesktopdata.sq
      l';
      ij> exit;
      

      where

      • database_host is your database host
      • port_number is the port number used to connect to your database host

      If you are using a production database, create the database schema as described in the Administering Platform LSF.

    [ Top ]


    Configure and Test LSF Desktop Reports on your Cluster

    Configure a unique loader controller (plc) service for every LSF desktop server (MED) host, depending on where your MED hosts are installed.

    Contents

    Configure the loader controller for MED hosts in an NFS or a shared directory

    For MED hosts in an NFS or a shared directory, you do not need to create a new loader controller. Configure the original loader controller to collect the MED data.

    1. In the command console, open the EGO service directory (EGO_ESRVDIR).
      cd LSF_CONFDIR/ego/cluster_name/eservice/esc/conf/services
      
    2. Edit plc_service.xml.
    3. Add the AC_TOP environment variable to specify the path to the MED host Tomcat server.

      For example, if MED_TOP is the top-level directory where the LSF desktop server is installed, add the following line:

      <ego:EnvironmentVariable name="AC_TOP">MED_TOP/jakarta-tomcat-4.1.30-LE-
      jdk14</ego:EnvironmentVariable>
      
    4. In the command console, stop all services and restart EGO on the master host to activate these changes.
      egosh service stop all
      egosh ego restart master_host_name
      

    Create new loader controllers for local MED hosts

    For local MED hosts, you need to configure a local loader controller on each local MED host. Perform the following steps on each local MED host to configure a local loader controller.

    1. Obtain the name of the local MED host.

      Run the hostname command while logged in to the local MED host.

    2. Configure a new loader controller as described in Configure the new loader controller.
    3. In the command console, open the PERF configuration directory.
      cd LSF_TOP/perf/conf
      
    4. Create a new directory with the same name as the one you specified in the new loader controller configuration file.

      For example, if the local host is hostMED1,

      mkdir plc_hostMED1
      
    5. Copy the contents from the old loader controller directory to the new controller. For example:
      cp plc/* plc_hostMED1
      
    6. Remove the redundant EGO and LSF configuration files from the new loader controller directory, and remove the redundant LSF desktop configuration files from the old loader controller directory.

      For example, delete plc_ego.xml and plc_lsf.xml from the plc_hostMED1 directory, and delete plc_lsfdesktop.xml from the plc directory.

      rm plc_hostMED1/plc_ego.xml
      rm plc_hostMED1/plc_lsf.xml
      rm plc/plc_lsfdesktop.xml
      
    7. Create a new loader controller service as described in Create new loader controllers for local MED hosts.
    8. In the command console, stop all services and restart EGO on the master host to activate these changes.
      egosh service stop all
      egosh ego restart master_host_name
      

    Configure the new loader controller

    1. In the command console, open the EGO service directory.
      cd LSF_TOP/perf/conf
      
    2. Copy the current plc.xml configuration file to a new configuration file with the name of the local MED host. For example
      cp plc.xml plc_hostMED1.xml
      
    3. Edit the new configuration file.

      For example, edit plc_hostMED1.xml.

      Change the port number to a new, unique port number that is not being used by another process.

      Edit the <Port> tag to use a new number.


      Tip:  Run netstat -an to see if the new port is already being used by an existing process..

    4. Specify a new loader controller configuration directory.

      Edit the <PLCDir> tag to change the default directory from plc to a new loader controller directory with the name of the local MED host. For example

      <PLCDir>plc_hostMED1</PLCDir>
      

    Create a new loader controller service

    1. In the command console, open the EGO service directory.
      cd LSF_CONFDIR/ego/cluster_name/eservice/esc/conf/services
      
    2. Copy the current plc_service.xml file to a new service configuration file with the name of the local MED host. For example:
      cp plc_service.xml plc_hostMED1_service.xml
      
    3. Edit the new service configuration file.

      For example, edit plc_hostMED1_service.xml.

    4. Change the service name to that of the new loader controller service.

      Navigate to the <sc:ServiceDefinition> tag and edit the ServiceName paramater. For example:

      <sc:ServiceDefinition ... ServiceName="plc_hostMED1" ...>
      
    5. Edit the command that runs the plc script using the old loader controller configuration file to use the new loader controller configuration file:

      Navigate to a line resembling the following and change plc.xml to the name of the new loader controller configuration file.

      <ego:Command>.../perf/etc/plc.sh -f plc.xml ...</ego:Command>
      

      For example:

      <ego:Command>.../perf/etc/plc.sh -f plc_hostMED1.xml ...</ego:Command>
      
    6. Add the AC_TOP environment variable to specify the path to the MED host Tomcat server.

      For example, if MED_TOP is the top-level directory where the LSF desktop server is installed, add the following line:

      <ego:EnvironmentVariable name="AC_TOP">MED_TOP/jakarta-tomcat-4.1.30-LE-
      jdk14</ego:EnvironmentVariable>
      
    7. Change the JobController command that runs the plc script using the old loader controller configuration file to use the new loader controller configuration file.

      Navigate to a line resembling the following and change plc.xml to the name of the new loader controller configuration file:

      <ego:JobController>.../perf/etc/plc.sh -k -f plc.xml ...</ego:JobController>
      

      For example:

      <ego:JobController>.../perf/etc/plc.sh -k -f plc_hostMED1.xml 
      ...</ego:JobController>
      
    8. Change the resource requirement to specify the MED host as an execution host.

      Navigate to the <ego:ResourceRequirement> tag and specify the MED host. For example:

      <ego:ResourceRequirement>select('hostMED1')</ego:ResourceRequirement>
      
    9. Change the consumer ID from a management host ID to an execution host ID.

      Navigate to the <ego:ConsumerID> tag and change the consumer tree to point to applications. For example:

      <ego:ConsumerID>/SampleApplications/EclipseSamples</ego:ConsumerID>
      
    10. Optional. Change the resource group name from a management host to an execution host.

      Navigate to the <ego:ResourceGroupName> tag and change the name to ComputeHosts.


      If the MED host is an EGO management host, you can skip this step.

    [ Top ]


    [ Platform Documentation ] [ Title ] [ Contents ] [ Previous ] [ Next ] [ Index ]


          Date Modified: January 29, 2009
    Platform Computing: www.platform.com

    Platform Support: support@platform.com
    Platform Information Development: doc@platform.com

    Copyright © 1994-2009 Platform Computing Corporation. All rights reserved.