Start the Installer on a Mac OS X or Other UNIX System

1. Log on to the machine as a non-root user. This user will own all files you install. If you are going to install new products into an existing Software AG installation directory (that contains products from the same release), log on to the machine as the same non-root user that installed the existing products.

2. Open your installation email from Software AG. Follow the instructions to download the Software AG Installer for UNIX. Copy the product license files attached to the email to the machine on which you are going to install.

3. Shut down all non-Software AG applications that are running on the machine on which you are going to install. If these applications are not shut down, product files might become corrupted.

4. If you are going to install new products into an existing Software AG installation directory (that contains products from the same release):

Products in the directory that are running must be shut down or the installer will not be able to update key files that are locked by the operating system. The installer will automatically shut down many of these products (and restart them after installation). However, there are some products that you must or might want to shut down manually before running the installer (and restart manually after installation is complete). See your product installation guide for detailed information.

Check whether a file named afterInstallAsRootLog.txt exists in the Software AG installation directory. If it does, execute the Software AG_directory /bin/beforeInstallAsRoot script.

Note:

Only install products from a single release in an installation directory. Do not mix products from different releases in the same installation directory. Doing so is not supported, and you will experience problems or be unable to access functionality.

5. Install a 32- or 64-bit JDK to run the installer and the uninstaller. For information on supported JDKs for Mac OS X and other UNIX systems, see the product system requirements on the Software AG Documentation Website.

6. Check whether the CLASSPATH, LD_LIBRARY_PATH (Linux), LIBPATH (AIX), or SHLIB_PATH (HP-UX) environment variable points to a JDK or JRE that is earlier than version 7. If so, either remove the path or edit the variables to point to a JDK or JRE that is version 7 or later.

7. The user file-creation mode mask (umask) can affect the file permissions for newly created files and directories. Make sure the umask you are using for installation will not prevent users from accessing and executing these files.

a. Allow the remote machine to access your local machine’s X11 display. If your local machine is a UNIX system, you can use the command xhost +remote_machine . If your local machine runs a X11 emulation on Windows, you might have to set a property in your emulation software.

b. Log on to the remote machine and set the shell variable DISPLAY to the value of your local machine’s X11 display. For example, if you are using a sh, ksh, or bash shell, you can use export DISPLAY=local_machine:0.0. If you are using a csh or tcsh shell, you can use setenv DISPLAY local_machine:0.0.

d. On Mac OS X, you can only install in GUI mode in the Mac OS X desktop, or in console mode in a terminal session. There is no way to use a remote X11 display like with other UNIX systems.

9. As you move through the wizard, the installer stores some of the files it requires in a temporary directory. The way you start the installer depends on the temporary directory you want to use. If you cancel the installer and later restart it on the same machine, the installer will use the stored files rather than downloading them from the installer server again, to improve performance. After a successful installation, the installer deletes the stored files.

If you want the installer to use the default temporary directory, run this command:

If you want the installer to use a different temporary directory than the default, run this command:

Note:

You might receive Java messages when you start the installer. For example, you might receive warning messages about system preferences, or about unlocking connections. You can ignore these messages.

Note:

If your temporary directory contains thousands of files, this process might take one minute or longer. The installer will display Initializing system resources during this time. If you want to speed up this process, delete the files in your temporary folder.