|
Unix deployments are different from Windows deployments in some ways:
Directory structure For Linux/Unix/Mac OS X installations, the directory structure is as follows:
| Directory | Contents |
|---|---|
| /opt/sqlanywhere10/bin | Executable files, License files |
| /opt/sqlanywhere10/lib | Shared objects and libraries |
| /opt/sqlanywhere10/res | String files |
On AIX, the default root directory is /usr/lpp/sqlanywhere10 instead of /opt/sqlanywhere10.
On Mac OS X, the default root directory is /Applications/SQLAnywhere10/System instead of /opt/sqlanywhere10.
File suffixes In the tables in this chapter, the shared objects are listed with a suffix of .so or .so.1. The version number, 1, could be higher as updates are released. For simplicity, the version number is often not listed.
For HP-UX, the suffix can be .sl.1 or .so.1. For AIX, the suffix does not contain a version number so it is simply .so.
Symbolic links Each shared object is installed as a symbolic link (symlink) to a file of the same name with the additional suffix .1 (one). For example, libdblib10.so is a symbolic link to the file libdblib10.so.1 in the same directory. For HP-UX, the symbolic link suffix is .sl.
The version suffix .1 could be higher as updates are released and the symbolic link must be redirected, accordingly.
Threaded and non-threaded applications Most shared objects are provided in two forms, one of which has the additional characters _r before the file suffix. For example, in addition to libdblib10.so.1, there is a file named libdblib10_r.so.1. In this case, threaded applications must be linked to the shared object whose name has the _r suffix, while non-threaded applications must be linked to the shared object whose name does not have the _r suffix. Occasionally, there is a third form of shared object with _n before the file suffix. This is a version of the shared object that is used with non-threaded applications.
Character set conversion If you want to use database server character set conversion, you need to include the following files:
Environment variables On Linux/Unix, environment variables must be set for the system to be able to locate SQL Anywhere applications and libraries. It is recommended that you use the appropriate file for your shell, either sa_config.sh or sa_config.csh (located in the directory /opt/sqlanywhere10/bin) as a template for setting the required environment variables. Some of the environment variables set by these files include PATH, LD_LIBRARY_PATH, SQLANY10, and SQLANYSH10.
For a description of how SQL Anywhere looks for files, see How SQL Anywhere locates files.