OpenLink's installers seldom fail. Furthermore, it is easy to
troubleshoot installer issues, when they occur. Use the following
guidelines to assist your users:
- Obtain the name of the user's installation files.
- Obtain the user's operating system and version. UNIX users
should provide the output of uname -a. Linux users should provide
the output of uname -a and rpm -qa | grep lib.
- Insure that the installation files are compatible with the
user's operating system. Most installers are compatible with the
intended o/s and updated versions of the o/s. For instance, Solaris
2.7 software should run on Solaris 2.7 and 2.8. It may not run on
- Tell users to ftp installation shell scripts in ASCII. .taz,
.dmg, and .zip files require BINARY transfer.
If the problem persists, invite UNIX users to use tar -xvf
to decompress their .taz files. Use of
tar should create a functional installation. However, environment
variables may remain to be set in the product configuration files:
i.e., openlink.sh, openlink.csh, openlink.ini, oplrqb.ini. Ask
Windows users to check their OpenLink installation directories and
registry. Occasionally, Windows installers report registry
problems. However, these same installers create functional
installations with properly configured variables. Consequently,
users should attempt to start their brokers and test their DSNs.
Finally, some Windows users may need to make substantial edits to
their registries after an installer failure. Address this course of
action with expert users. Do not encourage novice users to pursue