Deploying administration tools

Subject to your license agreement, you can deploy a set of administration tools including Interactive SQL, Sybase Central, and the SQL Anywhere Console utility.

The simplest way to deploy the administration tools is to use the Deployment Wizard. For more information, see Using the Deployment Wizard.

For information about system requirements for administration tools, see [external link] SQL Anywhere Supported Platforms and Engineering Status.

Deployment of the administration tools can be simplified by the use of initialization files. Each of the launcher executables for the administration tools (Sybase Central, Interactive SQL, the Console utility, and MobiLink Monitor) can have a corresponding .ini file. This eliminates the need for registry entries and a fixed directory structure for the location of the JAR files. Each launcher executable requires its own .ini file. These are located in the same directory and with the same file name as the executable file.

dbconsole.ini This is the name of the Console utility initialization file.
dbisql.ini This is the name of the Interactive SQL initialization file.
mlmon.ini This is the name of the MobiLink Monitor initialization file.
scjview.ini This is the name of the Sybase Central initialization file.

The initialization file will contain the details on how to load the database administration tool. For example, the initialization file may contain some or all of the following lines:

JRE_DIRECTORY=<path> This is the location of the required JRE. The JRE_DIRECTORY specification is required.
VM_ARGUMENTS=<any required VM arguments> VM arguments are separated by semicolons (;). Any path values that contain blanks should be enclosed in quotation marks. VM arguments can be discovered by using the -batch option of the administration tool (for example, scjview -batch) and examining the file that is created. The VM_ARGUMENTS specification is optional.
JAR_PATHS=<path1;path2;...> A delimited list of directories which contain the JAR files for the program. They are separated by semicolons (;). The JAR_PATHS specification is optional.
ADDITIONAL_CLASSPATH=<path1;path2;...> Classpath values are separated by semicolons (;). The ADDITIONAL_CLASSPATH specification is optional.
LIBRARY_PATHS=<path1;path2;...> These are paths to the DLLs/shared objects. They are separated by semicolons (;). The LIBRARY_PATHS specification is optional.
APPLICATION_ARGUMENTS=<arg1;arg2;...> These are any application arguments. They are separated by semicolons (;). Application arguments can be discovered by using the -batch option of the administration tool (for example, scjview -batch) and examining the file that is created. The APPLICATION_ARGUMENTS specification is optional.

Here are the contents of a sample initialization file for Sybase Central.

JRE_DIRECTORY=c:\Sun\JRE160_x86
VM_ARGUMENTS=-Xmx200m
JAR_PATHS=c:\scj\jars;c:\scj\jhelp
ADDITIONAL_CLASSPATH=
LIBRARY_PATHS=c:\scj\bin
APPLICATION_ARGUMENTS=-screpository=C:\Documents and Settings\All Users\Application Data\Sybase Central 6.0.0;-installdir=c:\scj

This scenario assumes that a copy of the 32-bit Sun JRE is located in c:\Sun\JRE160_x86. As well, the Sybase Central executable and shared libraries (DLLs) like jsyblib600 are stored in c:\scj\bin. The SQL Anywhere JAR files are stored in c:\scj\jars. The Sun JavaHelp 2.0 JAR files are stored in c:\scj\jhelp.

Note

When you are deploying applications, the personal database server (dbeng11) is required for creating databases using the dbinit utility. It is also required if you are creating databases from Sybase Central on the local computer when no other database servers are running.

Deploying administration tools on Windows without InstallShield
Deploying administration tools on Linux/Unix/Mac OS X
Configuring the administration tools
Deploying dbisqlc

Send feedback about this page via email or DocCommentXchange