Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
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 .scRepository. It resides in the /opt/sqlanywhere10/sybcentral500 directory. It is a plain text file that contains some basic information about the plug-ins that Sybase Central should load.
The provider information for SQL Anywhere is created in the repository file using the following commands.
scjview -register "/opt/sa10/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 10 PluginId=sqlanywhere1000 PluginClass=com.sybase.asa.plugin.SAPlugin PluginFile=\_opt\_sa10\_java\_saplugin.jar AdditionalClasspath=\_opt\_sa10\_java\_isql.jar: \_opt\_sa10\_java\_salib.jar: \_opt\_sa10\_java\_JComponents1001.jar: \_opt\_sa10\_java\_jlogon.jar: \_opt\_sa10\_java\_debugger.jar: \_opt\_sa10\_java\_jodbc.jar ClassloaderId=SA1000
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 and QAnywhere called mobilink.jpr and qanywhere.jpr respectively. They are also located in the java folder.
Here is a sample .scRepository 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: 18.104.22.16845 # Fri Feb 23 13:09:14 EST 2007 # SCRepositoryInfo/Version=4 # Providers/sqlanywhere1000/Version=10.0.1.3390 Providers/sqlanywhere1000/UseClassloader=true Providers/sqlanywhere1000/ClassloaderId=SA1000 Providers/sqlanywhere1000/Classpath= \_opt\_sa10\_java\_saplugin.jar Providers/sqlanywhere1000/Name=SQL Anywhere 10 Providers/sqlanywhere1000/AdditionalClasspath= \_opt\_sa10\_java\_isql.jar: \_opt\_sa10\_java\_salib.jar: \_opt\_sa10\_java\_JComponents1001.jar: \_opt\_sa10\_java\_jlogon.jar: \_opt\_sa10\_java\_debugger.jar: \_opt\_sa10\_java\_jodbc.jar Providers/sqlanywhere1000/Provider=com.sybase.asa.plugin.SAPlugin Providers/sqlanywhere1000/ProviderId=sqlanywhere1000 Providers/sqlanywhere1000/InitialLoadOrder=0 #
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 .scRepository file.
Forward slash characters (/) are represented with an escape sequence of \_ in the .scRepository file.
The first line indicates the version of the .scRepository file.
The lines beginning with # are comments.
For more information about deploying databases and database applications, see Deploying Databases and Applications.