Your installer should copy a subset of the files that are installed by the SQL Anywhere installer. You must keep the same directory structure.
You should preserve the permissions on the files when you copy them from your reference SQL Anywhere installation. In general, all users and groups are allowed to read and execute all files.
The administration tools require JRE 1.6.0. You should not substitute a later patch version of the JRE unless you have a specific need to do so.
For Linux/Solaris, the administration tools require the 32-bit version of JRE 1.6.0. The MobiLink server requires the 64-bit version of JRE 1.6.0. For Mac OS X, the administration tools require the 64-bit version. You should not substitute a later patch version of the JRE unless you have a specific need to do so. Not all platform versions of the JRE are bundled with SQL Anywhere. The platforms that are included with SQL Anywhere support Linux on x86/x64 and Solaris SPARC. Other platforms versions must be obtained from the appropriate vendor. For example, if you are working with a Linux install, copy the entire jre_1.6.0_linux_sun_i586 tree, including subdirectories.
If the platform that you require is included with SQL Anywhere, copy the JRE files from an installed copy of SQL Anywhere 12. Copy the entire tree, including subdirectories.
The following tables list the files required for each of the administration tools and the Sybase Central plug-ins. Make a list of the files you need, and then copy them into the directory structure outlined above.
The tables show files with the folder designation binXX. Depending on the platform, there are 32-bit and 64-bit versions of these files, in the bin32 and bin64 folders respectively. If you are installing 32-bit and 64-bit administration tools, then you must install both sets of files in their respective folders.
The tables show files with the folder designation libXX. Depending on the platform, there are 32-bit and 64-bit versions of these files, in the lib32 and lib64 folders respectively. If you are installing 32-bit and 64-bit administration tools, then you must install both sets of files in their respective folders.
The creation of several links is required for the administration tools and Sybase Central plug-ins.
For Linux and Solaris, create symbolic links for all the shared objects that you deploy. Also, create a symbolic link in $SQLANY12/sun. The symbolic link for Linux is jre160_x86 for the 32-bit JRE. The symbolic link for other systems is jre_160. Here are some examples:
libdblib12_r.so -> $SQLANY12/lib32/libdblib12_r.so.1 jre160_x86 -> $SQLANY12/sun/jre_1.6.0_linux_sun_i586 (Linux) jre160 -> $SQLANY12/sun/jre_1.6.0_solaris_sun_sparc (Solaris)
For the MobiLink plug-in on 64-bit Linux, create an additional symbolic link in $SQLANY12/sun. The symbolic link for Linux is jre160_x64 for the 64-bit JRE.
jre160_x64 -> $SQLANY12/sun/jre_1.6.0_linux_sun_x64 (Linux)
For Mac OS X, shared objects have a .dylib extension. Symlink (symbolic link) creation is necessary for the following dylibs:
libdbjodbc12.jnilib -> libdbjodbc12.dylib libdblib12_r.jnilib -> libdblib12_r.dylib libdbput12_r.jnilib -> libdbput12_r.dylib libmljodbc12.jnilib -> libmljodbc12.dylib
The tables show files with the designation [LL]. There are several message files each supporting a different language. If you want to install support for different languages, you have to add the resource files for these languages. For more information, see International message and context-sensitive help files.
Discuss this page in DocCommentXchange.
|Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1|