You will need to have Java SE 6 or higher installed on your system to run MCM. Java SE 6 comes with a Java Runtime Environment (JRE) version 1.6. You must obtain a JRE from Oracle. MCM will not run correctly on JREs from other vendors, such as GCJ or OpenJDK. The linux build of MCM comes bundled with a JRE. However, if you are using the generic Unix version of MCM, you will need to download a JRE separately.
To see which version of Java you are running, you can type java at a command prompt.
$ java -version java version "1.6.0_31" Java(TM) SE Runtime Environment (build 1.6.0_31-b04) Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)
These install instructions assume a basic familiarity with Unix/Linux file systems, and commands such as ls, tar, mv, etc.
The installation steps are as follows:
$ 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 &
![]() |
The default target folder 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. |
![]() |
If you're running Windows 7, MCM by default will NOT have permissions to create log files. This is because MCM will not have permission to write to subfolders of C:\Program Files or C:\Program Files (x86) unless it is run as an administrator. This may not be a concern. However, if you need to see log files, you can change the log file path to a folder where the user running MCM has permission to write to. To do this, edit the C:\Program Files (x86)\Moab Cluster Manager\conf\long4j.properties file and change the log4j.appender.ROLL.File property. For example, to cause logs to be written to C:\Users\Bob\AppData\Local, where Bob is the user running MCM, modify the property as shown below: log4j.appender.Roll.File=${user.home}/AppData/Local/mcm.log |
(Undefined variable: MyVariables.!CopyrightInfo!)