Linux and UNIX Considerations
X terminal
Verify that X terminal is installed. It is required for QAD Enterprise Edition Linux and UNIX installations.
Korn Shell
All of the scripts delivered on QAD media use Korn shell (ksh) syntax. The Korn shell must be installed in the default location (/bin/ksh) and available to the user account being employed to install QAD Enterprise Edition. If the Korn shell is not present in your system, you must install it before proceeding. The installation process varies by platform; for example, for Red Hat Enterprise Linux, you run the following command as root:
yum install ksh
Red Hat Enterprise Linux 7 (64-bit)
Red Hat Enterprise Linux 7 64-bit lacks some compatibility libraries that are required to install QDT. You can install these libraries by running the following command as a root user:
yum install glibc.i686
Attempting to run ./install.ksh without these libraries can fail and produces an error message similar to the following:
./install.ksh[21]: exec: ./install_linux: not found
Red Hat 7 64-bit may lack the compatibility libraries required to run QDT (qadinst). Install the missing libraries if you encounter the following problem:
ERROR:
qadinst_RH6_64bit: symbol lookup error: auto/Tk/PNG/PNG.so: undefined symbol: Perl_xs_apiversion_bootcheck.
The OS packages required to resolve this issue are:
• libX11-1.6.0-2.2.el6.x86_64
• libX11-1.6.0-2.1.el7.i686
AIX
If Concurrent I/O (CIO) is enabled, you cannot launch QDT on AIX. Disable CIO or move QDT to another file system on the server and launch QDT from the new location.
By default, AIX limits user files to a maximum size of 1 GB. You must increase this limit to at least 2 GB for the user account being employed to install QAD Enterprise Edition on AIX.
Installation Group and User
Linux and UNIX installations require a group called qad and a user called mfg on the database server. All installation and maintenance programs store pertinent information under the mfg user home directory. This information enables QAD scripts to automatically and reliably find data about installed products and lets you maintain your system without having to log on as root.
1 Using your Linux or UNIX system administration utility, create a group called qad with a group ID (gid) of 65535 (65535 is the user ID of the files on the QAD media).
2 Create a user called mfg with a user ID of 65535.
a Assign the Korn shell to this user. All of the scripts delivered on QAD media use Korn shell (ksh) syntax.
b For the mfg user, set the $HOME environment variable to a user directory to which working and temporary files can be written.
c Assign the standard umask permissions and security setting of 022.
Environment Variables
Update the mfg user .profile to include the DLC and PATH variables. Set the variables as follows:
• DLC: Progress OpenEdge installation directory
• JAVA_HOME: Java Development Kit installation directory
• CATALINA_HOME: Tomcat installation directory
• PATH: To include $DLC/bin, $JAVA_HOME/bin, and $CATALINA_HOME/bin
Depending on your flavor of Linux or UNIX, you may also need to set the following variables for the shared library path:
• SHLIB_PATH
• LD_LIBRARY_PATH
Expat XML Parser (HP-UX Only)
If you are installing on an HP Platform running HP-UX, you must install a C library for parsing XML. The Expat XML Parser is a free, open-source application that provides this functionality.
You can obtain the source code using the project’s SourceForge page at:
http://expat.sourceforge.net/
Precompiled depot files for HP are available at:
http://hpux.connect.org.uk/hppd/hpux/Development/Tools/expat-2.1.0/
The QAD Deployment Toolkit has a limitation when it is used on HP ia64 (Itanium) platforms. Install the depot files for the Itanium 2 and PA-RISC 2.0 before you install the QAD software.