Step 3: Set environment variables

To run the administration tools, several environment variables must be defined or modified. This is usually done in the sa_config.sh file, which is created by the SQL Anywhere installer. To use the sa_config.sh file, just copy it and set SQLANY16 to point to the deployment location.

Otherwise, to set the environment up, you must do the following:

Set the following environment variable:
SQLANY16="SQL-Anywhere-install-dir"

Set the PATH to include one of the following:

32-bit Linux and Solaris

$SQLANY16/bin32:

64-bit Linux and Solaris

$SQLANY16/bin64:

Set LD_LIBRARY_PATH to include the following:

32-bit Linux and Solaris

$SQLANY16/lib32: $SQLANY16/lib64: $SQLANY16/bin32/jre170/lib/i386/client: $SQLANY16/bin32/jre170/lib/i386/server: $SQLANY16/bin32/jre170/lib/i386: $SQLANY16/bin32/jre170/lib/i386/native_threads

64-bit Linux and Solaris

$SQLANY16/lib32: $SQLANY16/lib64: $SQLANY16/bin64/jre170/lib/amd64/client: $SQLANY16/bin64/jre170/lib/amd64/server: $SQLANY16/bin64/jre170/lib/amd64: $SQLANY16/bin64/jre170/lib/amd64/native_threads

On Mac OS X, the administration tools make use of a shell script stub launcher called sa_java_stub_launcher.sh, generated at install time and placed inside the Contents/MacOS folder of each Java application bundle. As generated, the script sources the System/bin64/sa_config.sh file to set up the environment and then runs the JavaApplicationStub binary, which starts the actual Java application. For deployment purposes, sa_java_stub_launcher.sh can be modified as required to set up the environment. The name of the script can be changed by modifying the Info.plist file inside the Java application bundle and changing the string value of the key CFBundleExecutable.

Discuss this page in DocCommentXchange.