Installing on UNIX

The following procedure explains how to install MCS in a UNIX environment. You must uninstall any existing version before installing the new version.

To provide server scalability and failover protection, you can install MCS on multiple servers across your network, creating a server cluster. For more information, refer to Managing MCS Servers and Clusters, Overview.

You can install using either the default Attachmate HTTP engine, or a Websphere or WebLogic application server. If you use WebLogic, your WebLogic domain must exist before you begin the installation. If you need to create a new domain, do so using one of the methods provided by BEA.

To install MCS and the MCS agent

If necessary, create your WebLogic domain.
Insert the MCS CD into the CD-ROM drive, and then copy the appropriate file from the CD to your computer.

For this environment
Copy this file

Most UNIX environments MCS_3.0_UNIX.tar.gz

OS/390 and z/OS USS environments MCS_3.0_USS.tar.gz
For most UNIX environments, type the following from the command line to expand the archive into its own empty directory:
gunzip -c MCS_3.0_UNIX.tar.gz | tar xvf -

-or-

For OS/390 and z/OS USS environments, unzip the MCS_3.0_USS.tar.gz file on your desktop, transfer the .tar file to the mainframe, and then use the tar command to expand the archive, as follows:

tar -xovf MCS_3.0_USS.tar
Change to the MCS directory and run ./setup.sh.
Read and accept the terms of the license agreement.

Follow the prompts.

For details about the installation prompts, see Installation Prompts for UNIX.

For Solaris, the installer searches for required patches, and warning messages are displayed for each patch that isn't found. (Patches are not required for Solaris 9).
All servers in a cluster must have the same MCS management components installed. If you want to add a server to an existing MCS cluster, all servers in the cluster must run on the same Web application server and under the same operating system. You must also make sure that you specify the same configuration options (port numbers, for example) for each server installation.

After the installation has completed, review the summary information, and then press ENTER.

Installation Notes

Installing with Limited Rights
If you are not logged on as the root user, or if you do not have root-level rights, your installation location may be limited to your own home directory.
Using the Bourne Shell
If you use sh as your shell, the server will stop whenever the shell exits because it does not ignore the SIGTERM signal sent by the shell. This is due to an error in Sun Java 2 SDK version 1.4.2.
This is not an issue if you run MCS as a daemon; if you use a different shell, such as csh, ksh, or bash for installing MCS with the HTTP engine; or if you use the UNIX nohup command to start the HTTP engine. For example:

nohup ./httpengine.sh start
Installing on Computers with Inadequate Memory
To avoid errors associated with attempting to run on a computer with limited RAM or virtual memory, edit attachmate_installdir/catalina.sh before running the installation. Change the first value in the following line to something smaller:
```
JAVA_OPTS=\"-Xms256m -Xmx256m \"\\
```
For example:
```
JAVA_OPTS=\"-Xms32m -Xmx256m \"\\
```
If you do not make these changes, you may encounter problems such as being unable to log in to MCS. You can check for associated errors in the setup.log, for example, "unable to allocate memory," or "heap allocation failure."
Adjusting the Java VM Heap Size
The Java VM heap size may need to be adjusted to allow for the number of sessions or threads running in your environment. As noted in the preceding section, this option can be changed in attachmate_installdir/HTTPEngine/bin/catalina.sh, either before or after installation.
Running as a z/OS Started Task
During installation, procedures, contained in InstalledLocation/HTTPEngine.PROC and HTTPEnginep.PROC, are created that can be added as members of your PROCLIB so that you can run MCS as a z/OS started task. For information about started tasks, contact your system administrator or refer to the documentation for your host computer.


	Management & Control Services, Overview
	Installation Prompts for UNIX
	Performing an Unattended Installation on UNIX