Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 11.0.0 » SQL Anywhere Server - Programming » Deploying SQL Anywhere » Deploying databases and applications » Deploying administration tools » Deploying administration tools on Windows without InstallShield

 

Step 5: Registering the Sybase Central plug-ins

This step involves the configuration of Sybase Central. If you are not installing Sybase Central, you can skip it.

Sybase Central requires a configuration file that lists the installed plug-ins. Your installer must create this file. Note that it contains full paths to a number of JAR files that may change depending on where the software is installed.

The file is called .scRepository600. On Windows XP/200x, it resides in the %allusersprofile%\application data\Sybase Central 6.0.0 folder. On Windows Vista, it resides in the %ProgramData%\Sybase Central 6.0.0 folder. It is a plain text file that contains some basic information about the plug-ins that Sybase Central should load.

On Windows Vista, all users should have read access to the directory that contains the .scRepository600 file. This can be done using the following command. To do this manually, open an administrator command prompt window (right-click Command Prompt and click Run As Administrator).

icacls "%ProgramData%\Sybase Central 6.0.0" /grant everyone:F

The provider information for SQL Anywhere is created in the repository file using the following commands.

scjview.exe -register "C:\Program Files\SQL Anywhere 11\java\sqlanywhere.jpr"

The contents of the sqlanywhere.jpr file looks like this (some entries have been split across multiple lines for display purposes). The AdditionalClasspath lines must be entered on a single line in the .jpr file.

PluginName=SQL Anywhere 11
PluginId=sqlanywhere1100
PluginClass=ianywhere.sa.plugin.SAPlugin
PluginFile=C:\Program Files\SQL Anywhere 11\java\saplugin.jar
AdditionalClasspath=
    C:\Program Files\SQL Anywhere 11\java\isql.jar;
    C:\Program Files\SQL Anywhere 11\java\salib.jar;
    C:\Program Files\SQL Anywhere 11\java\JComponents1100.jar;
    C:\Program Files\SQL Anywhere 11\java\jlogon.jar;
    C:\Program Files\SQL Anywhere 11\java\debugger.jar;
    C:\Program Files\SQL Anywhere 11\java\jodbc.jar
ClassloaderId=SA1100
InitialLoadOrder=0

The sqlanywhere.jpr file was created in the java folder of the SQL Anywhere installation when you originally installed SQL Anywhere. Use it as the model for the .jpr file that you must create as part of the install process. There are also versions of this file for MobiLink, QAnywhere, and UltraLite called mobilink.jpr, qanywhere.jpr, and ultralite.jpr respectively. They are also located in the java folder.

Here is a portion of the .scRepository600 file that was created using the process described above. Some entries have been split across multiple lines for display purposes. In the file, each entry appears on a single line:

#  Version: 6.0.0.1154
#  Fri Feb 22 10:22:20 EST 2008
#
SCRepositoryInfo/Version=4
#
Providers/sqlanywhere1100/Version=11.0.0.1297
Providers/sqlanywhere1100/UseClassloader=true
Providers/sqlanywhere1100/ClassloaderId=SA1100
Providers/sqlanywhere1100/Classpath=
    C:\\Program Files\\SQL Anywhere 11\\java\\saplugin.jar
Providers/sqlanywhere1100/Name=SQL Anywhere 11
Providers/sqlanywhere1100/AdditionalClasspath=
    C:\\Program Files\\SQL Anywhere 11\\java\\isql.jar;
    C:\\Program Files\\SQL Anywhere 11\\java\\salib.jar;
    C:\\Program Files\\SQL Anywhere 11\\java\\JComponents1100.jar;
    C:\\Program Files\\SQL Anywhere 11\\java\\jlogon.jar;
    C:\\Program Files\\SQL Anywhere 11\\java\\debugger.jar;
    C:\\Program Files\\SQL Anywhere 11\\java\\jodbc.jar
Providers/sqlanywhere1100/Provider=ianywhere.sa.plugin.SAPlugin
Providers/sqlanywhere1100/ProviderId=sqlanywhere1100
Providers/sqlanywhere1100/InitialLoadOrder=0
#
Notes
  • Your installer should create a file similar to this one using the techniques described above. The only changes required are the fully-qualified paths to the JAR files in the Classpath and AdditionalClasspath lines.
  • The AdditionalClasspath lines shown above have wrapped to take up additional lines. They must be on a single line in the .scRepository600 file.
  • Backslash characters (\) are represented with an escape sequence of \\ in the .scRepository600 file.
  • The first line indicates the version of the .scRepository600 file.
  • The lines beginning with # are comments.