Moab HPC Suite Basic Edition 7.1.4

Transcription

1 Moab HPC Suite Basic Edition Installation Guide March 2013

2 2013 Adaptive Computing Enterprises, Inc. All rights reserved. Distribution of this document for commercial purposes in either hard or soft copy form is strictly prohibited without prior written consent from Adaptive Computing Enterprises, Inc. Adaptive Computing, Cluster Resources, Moab, Moab Workload Manager, Moab Viewpoint, Moab Cluster Manager, Moab Cluster Suite, Moab Grid Scheduler, Moab Grid Suite, Moab Access Portal, and other Adaptive Computing products are either registered trademarks or trademarks of Adaptive Computing Enterprises, Inc. The Adaptive Computing logo and the Cluster Resources logo are trademarks of Adaptive Computing Enterprises, Inc. All other company and product names may be trademarks of their respective companies. Adaptive Computing Enterprises, Inc S. East Bay Blvd., Suite 300 Provo, UT (801) Scan to open online help ii

3 Contents Welcome v Installation overview 1 Installing TORQUE 3 Installing Moab Workload Manager 5 Installing Moab Web Services 11 Installing Moab Viewpoint 17 Installing Moab Cluster Manager 21 Component documentation 23 iii

4

5 Welcome Welcome to the Moab HPC Suite Basic Edition Installation Guide, which will help you install your Moab HPC Suite. This guide includes detailed instructions for installing each component of the suite so that you can quickly get up and running. This guide is intended for system administrators who are responsible for installing the Moab HPC Suite Basic Edition. The Moab HPC Suite Basic Edition version contains the following components: Moab Workload Manager TORQUE Moab Web Services Moab Viewpoint Moab Cluster Manager To get started with installing your Moab HPC Suite, please see Installation overview on page 1. v

6

7 Installation overview The installation process of the Moab HPC Suite includes installing the separate components in the suite. This guide contains detailed instructions for installing each component. Many individual components have dependencies on other components. (These dependencies are listed in the "Requirements" section of each component's installation instructions.) However, if you do not require a certain component (Moab Viewpoint, for example), you do not have to install it. The install instructions for each component include information about system requirements and dependencies. Some include prerequisite instructions that you will need to complete before you begin the install. Please read this information carefully, and make sure you have installed all the dependencies and packages that are necessary in order to avoid errors during the Moab HPC Suite install process. To install the Moab HPC Suite, install the packages in the following order: 1. Install TORQUE (see Installing TORQUE on page 3). 2. Install Moab Workload Manager (see Installing Moab Workload Manager on page 5). 3. Install Moab Web Services (see Installing Moab Web Services on page 11). 4. Install Moab Viewpoint (see Installing Moab Viewpoint on page 17). 5. Install Moab Cluster Manager (see Installing Moab Cluster Manager on page 21). Related topics Welcome on page v 1

8

9 Installing TORQUE These instructions describe how to install and start TORQUE. Requirements The following software is required to run TORQUE 4.1.4: libxml2-devel package (package name may vary) openssl-devel package (package name may vary) ANSI C compiler. The native C compiler is recommended if it is ANSI; otherwise use gcc. A fully POSIX make. If you are unable to "make" PBS with your make, we suggest using gmake from GNU. Tcl/Tk version 8 or higher if you plan to build the GUI portion of TORQUE or use a Tcl based scheduler. If you use cpusets, libhwloc 1.1 or later is required (for TORQUE and later) Dependencies and packages installation Use the following commands to install the required TORQUE dependencies and packages (listed in the Requirements section above). RHEL [root]# yum update [root]# yum install make libxml2-devel openssl-devel gcc gcc-c++ CentOS [root]# yum update [root]# yum install make libxml2-devel openssl-devel gcc gcc-c++ Prerequisites TORQUE requires certain ports to be open for essential communication: For client communication to pbs_server, all privileged ports must be open (ports under 1024). For pbs_server communication to pbs_mom, the default port is For pbs_mom to pbs_server, the default port is For more information on how to configure the ports that TORQUE uses for communication, see Configuring Ports. 3

10 Installing TORQUE To install TORQUE 1. Run each of the following commands in order. [root]# tar xzvf torque tar.gz [root]# cd torque [root]#./configure [root]# make [root]# make install For information on what options are available to customize the./configure command, see Customizing the install. 2. Configure the trqauthd daemon to start automatically at system boot. [root]# cp contrib/init.d/trqauthd /etc/init.d/ [root]# chkconfig --add trqauthd [root]# echo /usr/local/lib > /etc/ld.so.conf.d/torque.conf [root]# ldconfig [root]# service trqauthd start 3. The make packages command can be used to create self-extracting packages that can be copied and executed on your nodes. For information on creating packages and deploying them, see Compute nodes. You will also want to scp the init.d scripts to the compute nodes and install them there. 4. Populate the /var/spool/torque/server_name file with the hostname of the pbs_server. [root]# echo <pbs_server's_hostname> > /var/spool/torque/server_name 5. Initialize serverdb by executing the torque.setup script. [root]#./torque.setup root 6. Add nodes to the /var/spool/torque/server_priv/nodes file. As an example, a single node with two processors could be specified with mgtnode np=2. For information on syntax and options for specifying compute nodes, see Specifying compute nodes. 7. Configure pbs_server and pbs_mom to start automatically at system boot, and then start their daemons. [root]# cp contrib/init.d/pbs_server contrib/init.d/pbs_mom /etc/init.d [root]# chkconfig --add pbs_server [root]# chkconfig --add pbs_mom [root]# chkconfig pbs_mom on [root]# chkconfig pbs_server on [root]# service pbs_server restart [root]# service pbs_mom start Related topics Installation overview on page 1 Installing Moab Workload Manager on page 5 Component documentation on page 23 4

11 Installing Moab Workload Manager These instructions describe how to install and start Moab Workload Manager (MWM). Requirements Hardware requirements: Quad-core processor At least 12 GB of RAM 100 GB disk space Supported operating systems: MWM has been tested on the following variants of Linux: CentOS (5.7, 6.0, and 6.2) Red Hat (5 and 6.1) Scientific Linux (6.1) SuSE (11 SP1 and 11 SP2) MWM has historically worked, but has not been tested, on the following operating systems: Debian AIX Host operating system software dependencies: ExtUtils::MakeMaker Perl module XML::LibXML Perl module (perl-xml-libxml) libcurl perl-libwww-perl (may be named differently on non-rhel distributions) Supported architectures: Intel IA-64 Intel/AMD x86-64 Supported resource managers: TORQUE SLURM 5

12 Installing Moab Workload Manager Dependencies and packages installation Use the following commands to install the required Moab Workload Manager dependencies and packages (listed in the Requirements section above). RHEL [root]# yum update [root]# yum install make perl-extutils-makemaker perl-xml-libxml libcurl perllibwww-perl CentOS [root]# yum update [root]# yum install make perl-extutils-makemaker perl-xml-libxml libcurl perllibwww-perl To install Moab Workload Manager If you have not met the hardware and host operating system software requirements listed above, you will likely encounter errors when trying to install Moab Workload Manager. 1. Run each of the following commands in order: [root]# tar xzvf moab xxxx.tar.gz (where xxxx can be one of: generic, genericodbc, torque, torque-odbc) [root]# cd moab [root]#./configure <option> [root]# make perldeps [root]# make install In some cases, you might want to customize the location of the MWM home directory, the server daemon, and the client commands. You can make these configurations by using the./configure options. (For a complete list of./configure options, use./configure --help.) We strongly recommend that you configure Moab with the --with-init and --with-profile options. Here are some examples of commonly used./configure options: Option Description Example --withhomedir Specifies the location of the Moab configuration directory and the MOABHOMEDIR environment variable. The default location is /opt/moab. MOABHOMEDIR is automatically set on some distributions during installation, when the --with-profile option is enabled. [root]#./configure -- withhomedir=/var/moab 6

13 Installing Moab Workload Manager Option Description Example Enables the installation of a distribution-specific /etc/init.d/moab service startup script. This option is required if you want to install this script onto a new system. If you do not set this option, you must manually set up the MWM daemon service. The startup script is located at OS/EL/etc/init.d/moab. [root]#./configure -- with-init --prefix Specifies the location of the binaries and libraries of the MWM install. The default location is /opt/moab. [root]#./configure -- prefix=/usr/local --withinit --withprofile Enables the installation of distribution-specific /etc/profile.d/moab. [c]sh setup script for bash and cshell. The MOABHOMEDIR, PERL5LIB, PATH and MANPATH environment variables are setup to specify where the new moab configuration, scripts, binaries and man pages reside. If you do not set this option, these scripts are not installed, and you must manually perform this set up. The environment setup scripts are located at OS/EL/etc/profile.d/moab.[c]sh. [root]#./configure -- with-profile 2. (ONLY if installing on non-rhel distributions) Copy the appropriate init.d file, set the permissions on it, and configure MWM to start automatically at system boot. * If Debian distribution, do the following * [root]# cp contrib/init.d/moab_debian_init /etc/init.d/moab * If SLES distribution, do the following * [root]# cp contrib/init.d/moab_sles_init /etc/init.d/moab [root]# chmod 755 /etc/init.d/moab [root]# chkconfig --add moab * If chkconfig doesn't work, try the following * [root]# update-rc.d moab defaults 3. Modify the MWM configuration file. [root]# vim /opt/moab/etc/moab.cfg Do the following: a. Verify that SUBMITCMD is set up for your TORQUE resource manager (change RMCFG[hostname] to RMCFG[torque]), and that it points to a valid qsub executable. For example: RMCFG[torque] SUBMITCMD=/usr/local/bin/qsub 7

14 Installing Moab Workload Manager b. ONLY if you are using Moab Viewpoint, add "tomcat" to the list of administrator USERS. For example: ADMINCFG[1] USERS=root,tomcat Also, make sure that you set ENABLEPROXY to "true": ADMINCFG[1] ENABLEPROXY=TRUE 4. If you ran the./configure --with-profile option, source the following file to add the MWM home directory to your current shell $PATH environment. [root]#. /etc/profile.d/moab.sh 5. Copy your license file into the same directory as moab.cfg (/opt/moab/etc/ by default). For example: [root]# cp moab.lic $MOABHOMEDIR/etc/moab.lic To verify the current status of your license, use moab --about. MWM checks the status of the license every day just after midnight. At 60 and 45 days before, and daily from 30 days before license expiration to and including the license expiration date, MWM sends an e- mail to all level 1 administrators informing them of the pending MWM license expiration. A log record is also made of the upcoming expiration event. For the notifications to occur correctly, you must enable administrator notification (see "Notifying Administrators of Failures" in the Moab Workload Manager Administrator Guide) and moab.cfg must contain addresses for level 1 administrators. For example: ADMINCFG[1] USERS=u1,u2,u3[,...] USERCFG[u1] u1@company.com USERCFG[u2] u2@company.com USERCFG[u3] u3@company.com MAILPROGRAM DEFAULT MWM has an internal license that enables some functionality for a limited time for evaluation purposes. If you want to enable adaptive energy management, dynamic multi-os provisioning, grid management, and other features, or if you want to evaluate MWM for a longer period, contact evaluation support. Use mdiag -S -v to see which features your license supports. 6. Start MWM. [root]# service moab start 7. Submit a sleep job as a non-root user and verify the job is running. [root]# su - user [user]$ echo sleep 150 msub [user]$ showq Related topics Installation overview on page 1 Installing TORQUE on page 3 8

15 Installing Moab Workload Manager Component documentation on page 23 9

16

17 Installing Moab Web Services These instructions describe how to deploy Moab Web Services (MWS) to a Tomcat server. Requirements Hardware requirements: Dual core processor At least 4 GB of RAM Software requirements: Moab Workload Manager Oracle /Sun Java 6 Runtime Environment Apache Tomcat 6 MongoDB or later Dependencies and packages installation Use the following commands to install the required Moab Web Services dependencies and packages (listed in the Requirements section above). RHEL [root]# yum update [root]# yum install tomcat6 CentOS The correct version of Tomcat is not automatically installed on CentOS 5. The example below ensures that the right build of Tomcat 6 is installed. [root]# rpm -Uvh ' [root]# cd /etc/yum.repos.d [root]# wget ' [root]# yum update [root]# yum install tomcat6 tomcat6-webapps tomcat6-admin-webapps To install Moab Web Services You must deploy Moab Web Services on the same server as Moab Workload Manager. 11

18 Installing Moab Web Services 1. Make sure that you have first installed and configured Moab Workload Manager as desired (for details, see Installing Moab Workload Manager on page 5). 2. Generate a secret key to be used for communication between MWM and MWS. Here is a suggested script that you can use to generate the key: dd if=/dev/urandom count=18 bs=1 2>/dev/null base64 > /opt/moab/etc/.moab.key chown root /opt/moab/etc/.moab.key chmod 400 /opt/moab/etc/.moab.key ln -f /opt/moab/etc/.moab.key /opt/moab/.moab.key 3. Start MWM. service moab start 4. Install MongoDB version or later on the MWM server using packages (recommended) or manual installation. Installation method Instructions Packages (recommended) Install the packages (available from the Mongo-provided repositories for CentOS and Fedora or Ubuntu and Debian). After installing the packages, start MongoDB and arrange for it to start automatically during server startup. For CentOS and Fedora, here are some examples: /sbin/chkconfig mongod on /etc/init.d/mongod start For Ubuntu and Debian examples, see these instructions. Manual (not recommended) Follow these instructions. Be sure to start the Mongo server (mongod) after installation and arrange for it to start automatically during server startup (for example, by writing and registering an /etc/init.d script). 5. Install and enable the 64-bit version of Oracle Java SE 6 JRE. For example: sh jre-6u33-linux-x64-rpm.bin rm -f /usr/bin/java ln -s /etc/alternatives/java /usr/bin/java /usr/sbin/alternatives --install /usr/bin/java java /usr/java/latest/bin/java 1 /usr/sbin/alternatives --set java /usr/java/latest/bin/java You can verify the Java installation by running the following command: java -version The output should look similar to this: 12

19 Installing Moab Web Services java version "1.6.0_33" Java(TM) SE Runtime Environment (build 1.6.0_33-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode) 6. Create the MWS home directory (for more information, see the "Configuration" section of the Moab Web Services Reference Guide), and the etc, hooks, plugins, and log subdirectories. You will need to give the Tomcat user "read" access to all directories and "write" access to the plugins and log directories. The default location for the MWS home directory is /opt/mws. These instructions assume the default location. Here is an sample script for this setup: mkdir -p /opt/mws/etc /opt/mws/hooks /opt/mws/plugins /opt/mws/log chown -R tomcat /opt/mws # Depending on your OS, the Tomcat username might be tomcat6. chmod -R 555 /opt/mws chmod u+w /opt/mws/plugins /opt/mws/log 7. Extract the contents of the MWS download tarball into a temporary directory. For example: mkdir /tmp/mws-install cd /tmp/mws-install tar xvzf $HOME/Downloads/mws tar.gz cd /tmp/mws-install/mws Set up the MWS configuration file by doing the following: a. Copy mws-config-hpc.groovy to the MWS home etc/ sub-directory, and rename it to mwsconfig.groovy. cp mws-config-hpc.groovy /opt/mws/etc/mws-config.groovy b. Give the Tomcat user "read" access to the /opt/mws/etc/mws-config.groovy file. c. In the /opt/mws/etc/mws-config.groovy file, make the following changes: Modify the moab.secretkey setting to match the MWM secure key you generated earlier (contained in /opt/moab/etc/.moab.key). Change the default MWS password (auth.defaultuser.password) to a password of your choosing. (Optional) Change the default MWS username (auth.defaultuser.username) to any value you like. [root]# vi /opt/mws/etc/mws-config.groovy... moab.secretkey = "<ENTER-KEY-HERE>" moab.server = "localhost" moab.port = // Change these to be whatever you like. auth.defaultuser.username = "admin" auth.defaultuser.password = "adminpw" 13

20 Installing Moab Web Services If you do not change auth.defaultuser.password, your MWS will not be secure (because anyone reading these instructions would be able to log into your MWS). Here are some tips for choosing a good password. 9. Set the following parameters in your Tomcat CATALINA_OPTS: CATALINA_OPTS="-Xms256m -Xmx3g -XX:MaxPermSize=384m -DMWS_HOME=/opt/mws" Where you choose to store CATALINA_OPTS depends on various factors, including operating system and sysadmin preference. Here are some suggestions: CentOS 5 and 6: /etc/tomcat6/tomcat6.conf Red Hat Enterprise Linux 5 and 6: /etc/tomcat6/tomcat6.conf SUSE Linux Enterprise Server 11: /etc/tomcat6/tomcat6.conf Ubuntu 10.04: /etc/default/tomcat6 10. Start Tomcat, and deploy mws.war. For example: chkconfig tomcat6 on service tomcat6 start cp /tmp/mws-install/mws-7.1.0/mws.war /var/lib/tomcat6/webapps 11. Navigate to in a web browser to verify that MWS is running (you will see some sample queries and a few other actions). 12. Log in to MWS to verify that your credentials are working. (Your login credentials are the auth.defaultuser.username and auth.defaultuser.password values you set in the /opt/mws/etc/mws-config.groovy file.) 14

21 Installing Moab Web Services If you encounter problems, or if the application does not seem to be running, see the steps in the "Troubleshooting Installation "section of the Moab Web Services Reference Guide. Related topics Installation overview on page 1 Installing Moab Workload Manager on page 5 Installing Moab Viewpoint on page 17 Component documentation on page 23 15

22

23 Installing Moab Viewpoint These instructions describe how to install and start Moab Viewpoint. Requirements Hardware requirements: 16 GB disk space Software requirements: Moab Workload Manager version Moab Web Services version Apache Tomcat 6 MySQL version 5.1 or later JDBC Driver for MySQL (Connector/J) (available from MySQL or another trusted source) Supported web browsers: Mozilla Firefox 3.5 or later Internet Explorer 7.0 or later Dependencies and packages installation Use the following commands to install the required Moab Viewpoint dependencies and packages (listed in the Requirements section above). RHEL [root]# yum update [root]# yum install tomcat6 mysql mysql-server CentOS The correct version of Tomcat is not automatically installed on CentOS 5. The example below ensures that the right build of Tomcat 6 is installed. [root]# rpm -Uvh ' [root]# cd /etc/yum.repos.d [root]# wget ' [root]# yum update [root]# yum install tomcat6 tomcat6-webapps tomcat6-admin-webapps mysql mysql-server 17

24 Installing Moab Viewpoint To install Moab Viewpoint 1. Create the Viewpoint database. MySQL 5.1 is the supported database for Moab HPC Suite. You must create the database and give the user full access to that database. For information on creating databases and granting access with other database vendors, consult the documentation for that vendor. While MySQL is the only supported database for Viewpoint, the use of other databases with Moab HPC Suite is possible. Please contact Adaptive Computing Support for more information. For information on creating databases and granting access with other database vendors, consult the documentation for that vendor. Do the following: a. Run these commands. [root]# chkconfig mysqld on [root]# service mysqld start [root]# /usr/bin/mysql_secure_installation b. When you are prompted for the current root password, press Enter. When you are asked to set the root password, use and select y for all options. c. Create the Viewpoint database and grant the following permissions (remember to run commands in context): [root]# mysql -u root -p Enter password: mysql> CREATE DATABASE viewpoint; Query OK, 1 row affected (0.08 sec) mysql> GRANT ALL ON viewpoint.* TO viewpoint@localhost IDENTIFIED BY 'p@ssw0rd'; Query OK, 0 rows affected (0.31 sec) mysql> GRANT ALL ON viewpoint.* TO viewpoint@ IDENTIFIED BY 'p@ssw0rd'; Query OK, 0 rows affected (0.31 sec) FLUSH PRIVILEGES; Query OK, 0 rows affected (0.31 sec) 2. Untar the Viewpoint tarball, and create the initial tables required for an HPC Viewpoint. [root]# tar xzvf viewpoint tar.gz [root]# mysql -u root -p viewpoint < viewpoint-7.1.4/sql/mysql/setup_hpc.sql 3. Verify that the script ran correctly by running a third party client such as SQuirrel SQL or by using your database vendor's own client tool (for instance, run mysql -u <username> -p <password>). As a best practice, create a schema if you are running PostgresSQL. It is recommended that you call the schema viewpoint. If you choose not to create one, set public as the schema name when you configure the setup.properties file. 4. Install the JDBC Driver for MySQL (available from MySQL or another trusted source). [root]# tar xvzf mysql-connector-java-x.x.x.tar.gz [root]# cd mysql-connector-java.x.x.x [root]# cp mysql-connector-java.x.x.x-bin.jar /usr/share/tomcat6/lib 5. Create the Viewpoint home directory. 18

25 Installing Moab Viewpoint [root]# mkdir /opt/viewpoint 6. Navigate to the Viewpoint extraction directory, and deploy the war files (reporting.war is optional). [root]# cd viewpoint-7.1.0/ [root]# cp dist/*.war /var/lib/tomcat6/webapps/ It is recommended that you do not run more than one instance of Viewpoint within Tomcat. 7. Copy the setup.properties.[db_type] file to the Viewpoint home directory and change the name to setup.properties (removing the.[db_type] extension). [root]# cp templates/setup.properties.mysql /opt/viewpoint/setup.properties 8. Open setup.properties for modification. [root]# vi /opt/viewpoint/setup.properties Change the username and password to what you set when you configured the database. dbuser=<viewpoint> 9. Set the Tomcat user as the owner of the Viewpoint home directory. Restart Tomcat. [root]# chown -R tomcat:tomcat /opt/viewpoint [root]# service tomcat6 restart If you are running Fedora, you must start Tomcat by navigating to $CATALINA_home/bin/ and run startup.sh as root: [root]# $CATALINA_HOME/bin/startup.sh 10. Verify that Viewpoint was correctly installed by directing your browser to the Viewpoint URL (for example: or ip address]:8080/moab), and logging in with the default username and password (admin/admin). 11. Update the Viewpoint connection to MWS. a. From the Administration > Configuration menu, click MWS connection. b. Update the Username and Password fields to match the username and password you configured in the /opt/mws/etc/mws-config.groovy file and click Update. c. Restart Tomcat. [root]# service tomcat6 restart Related topics Installation overview on page 1 Installing Moab Workload Manager on page 5 Installing Moab Web Services on page 11 Component documentation on page 23 19

26

27 Installing Moab Cluster Manager These instructions describe how to install and start Moab Cluster Manager (MCM). Requirements Prerequisites Moab Workload Manager You will need to install Oracle /Sun Java SE 6 or higher, which includes a Java Runtime Environment (JRE) version 1.6 or higher. You must obtain a JRE from Oracle. MCM will not run correctly on JREs from other vendors, such as GCJ or OpenJDK. The Linux and Windows builds of MCM come bundled with the correct JRE. However, if you install the generic Unix version of MCM, you will need to download a JRE separately. You can check which version of Java you have installed by running the following command: $ java -version The output should look similar to this: java version "1.6.0_33" Java(TM) SE Runtime Environment (build 1.6.0_33-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03, mixed mode) To install Moab Cluster Manager on a Linux/Unix system 1. Download the latest build of the tar file from the Adaptive Computing website: The mcm-7.1.x-[build number].linux.tar.gz builds come with a bundled JRE. The mcm-7.1.x-[build number].tar.gz builds do not include a JRE. 2. Move the tar file to your home directory, or another directory you have access to (for example, /home/username/), and unpack the tar file (tar -xzvf xxxx.tar.gz). 3. Change directories to the newly unpacked MCM directory. 4. Start MCM by running the following script: $ mv mcm-7.1.x-xxxx.tar.gz /home/bob $ cd /home/bob $ tar zxvf mcm-7.1.x-xxxx.tar.gz $ cd mcm-7.1.x-xxxx/ $./mcm & 5. The MCM script checks for the existence of a compatible JRE and then runs MCM. 21

28 Installing Moab Cluster Manager After you accept the license, you will see the Connection Wizard. For information about configuring MCM to connect to Moab Workload Manager, see the "Connection Wizard" section in the Moab Cluster Manager User Guide. To install Moab Cluster Manager on a Windows system 1. Download the latest build executable from the Adaptive Computing website. 2. Double-click the installation file. 3. Follow the MCM installer instructions to install MCM. Once it has completed, the installer creates Start Menu and Desktop icons that you can use to start MCM. The default destination folder for MCM is either C:\Program Files\Moab Cluster Manager or C:\Program Files\(x86)\Moab Cluster Manager (depending on what version of Windows you are running). 4. Double-click the Moab Cluster Manager icon on the Desktop to run MCM. After you accept the license, you will see the Connection Wizard. For information about configuring MCM to connect to Moab Workload Manager, see the "Connection Wizard" section in the Moab Cluster Manager User Guide. MCM will not have permissions to create log files if you are installing on a Windows 7 system. (This is because MCM does not have permission to write to sub-folders of C:\Program Files or C:\Program Files (x86) unless it is run as an administrator.) If you are running Windows 7 and need to see log files, you can change the log file path to a location where the user running MCM has write permissions. You can make this configuration in the C:\Program Files (x86)\moab Cluster Manager\conf\long4j.properties file by setting the log4j.appender.roll.file property. For example, if you want logs to be written to C:\Users\Bob\AppData\Local (where Bob is the user running MCM), modify the log4j.appender.roll.file property as follows: log4j.appender.roll.file=${user.home}/appdata/local/mcm.log Related topics Installation overview on page 1 Installing Moab Workload Manager on page 5 Component documentation on page 23 22

29 Component documentation The individual components of the suite have more options and allow for more configuration than can be contained in this guide. Refer to the individual component guides for more information. TORQUE TORQUE Administrator Guide: HTML PDF Moab Workload Manager Moab Workload Manager Administrator Guide: HTML PDF Moab Web Services Moab Web Services Reference Guide: HTML PDF Moab Viewpoint Moab Viewpoint for Moab HPC Suite Setup Guide: HTML PDF Moab Viewpoint for Moab HPC Suite User Guide: HTML PDF Moab Cluster Manager Related topics Moab Cluster Manager User Guide: HTML PDF Installation overview on page 1 Welcome on page v 23

30