|
You can deploy a database server by making the SQL Anywhere installer available to your end users. By selecting the proper option, each end user is guaranteed of getting the files they need.
The simplest way to deploy a personal database server or a network database server is to use the Deployment wizard. For more information, see Using the Deployment wizard.
To run a database server, you need to install a set of files. The files are listed in the following table. All redistribution of these files is governed by the terms of your license agreement. You must confirm whether you have the right to redistribute the database server files before doing so.
| Windows | Linux/Unix | Mac OS X | NetWare |
|---|---|---|---|
| dbeng10.exe | dbeng10 | dbeng10 | N/A |
| dbeng10.lic | dbeng10.lic | dbeng10.lic | N/A |
| dbsrv10.exe | dbsrv10 | dbsrv10 | dbsrv10.nlm |
| dbsrv10.lic | dbsrv10.lic | dbsrv10.lic | dbsrv10.lic |
| dbserv10.dll | libdbserv10_r.so, libdbtasks10_r.so | libdbserv10_r.dylib, libdbtasks10_r.dylib | N/A |
| dblg[en]10.dll | dblg[en]10.res | dblg[en]10.res | dblg[en]10.res |
| dbctrs10.dll | N/A | N/A | N/A |
| dbextf.dll 1 | libdbextf.so 1 | libdbextf.dylib 1 | dbextf.nlm 1 |
| dbicu10.dll2 | libdbicu10_r.so2 | libdbicu10_r.dylib2 | dbicu10.nlm2 |
| dbicudt10.dll2 | libdbicudt10.so2 | libdbicudt10.dylib2 | dbicud10.nlm2 |
| sqlany.cvf | sqlany.cvf | sqlany.cvf | sqlany.cvf |
| dbodbc10.dll 3 | libdbodbc10.so 3 | libdbodbc10.dylib 3 | N/A |
| N/A | libdbodbc10_n.so 3 | libdbodbc10_n.dylib 3 | N/A |
| N/A | libdbodbc10_r.so 3 | libdbodbc10_r.dylib 3 | N/A |
| dbjodbc10.dll 3 | libdbjodbc10.so 3 | libdbjodbc10.dylib 3 | N/A |
| java\jconn2.jar 3 | java/jconn2.jar 3 | java/jconn2.jar 3 | java\jconn2.jar 3 |
| java\jodbc.jar 3 | java/jodbc.jar 3 | java/jodbc.jar 3 | java\jdbcdrv.zip 3 |
| java\sajvm.jar 3 | java/sajvm.jar 3 | java/sajvm.jar 3 | java\sajvm.jar 3 |
| java\cis.zip 4 | java/cis.zip 4 | java/cis.zip 4 | java\cis.zip 4 |
1 Required only if using system extended stored procedures and functions (xp_).
2 Required only if the database character set is multi-byte or if the UCA collation sequence is used.
3 Required only if using Java in the database.
4 Required only if using Java in the database and remote data access.
Depending on your situation, you should choose whether to deploy the personal database server (dbeng10) or the network database server (dbsrv10).
You must include the separate corresponding license file (dbeng10.lic or dbsrv10.lic) when deploying a database server. The license files are located in the same directory as the server executables.
The Java VM jar file (sajvm.jar) is required only if the database server is to use the Java in the Database functionality.
The table does not include files needed to run utilities such as dbbackup.
For information about deploying utilities, see Deploying administration tools.
To ensure that messages written by the server to the Event Log on Windows are formatted correctly, create the following registry key.
HKEY_LOCAL_MACHINE\
SYSTEM\
CurrentControlSet\
Services\
Eventlog\
application\
SQLANY 10.0
Within this key, add a REG_SZ value named EventMessageFile and assign it the data value of the fully qualified location of dblgen10.dll, for example, C:\Program Files\SQL Anywhere 10\win32\dblgen10.dll. The English language DLL, dblgen10.dll, can be specified regardless of the deployment language. Here is a sample registry change file.
REGEDIT4 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SQLANY 10.0] "EventMessageFile"="c:\\sa10\\win32\\dblgen10.dll"
To ensure that messages written by MESSAGE ... TO EVENT LOG statements to the Event Log on Windows are formatted correctly, create the following registry key.
HKEY_LOCAL_MACHINE\
SYSTEM\
CurrentControlSet\
Services\
Eventlog\
application\
SQLANY 10.0 Admin
Within this key, add a REG_SZ value named EventMessageFile and assign it the data value of the fully qualified location of dblgen10.dll, for example, C:\Program Files\SQL Anywhere 10\win32\dblgen10.dll. The English language DLL, dblgen10.dll, can be specified regardless of the deployment language. Here is a sample registry change file.
REGEDIT4 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\SQLANY 10.0 Admin] "EventMessageFile"="c:\\sa10\\win32\\dblgen10.dll"
You can suppress Windows event log entries by setting up a registry key. The registry key is
Software\Sybase\SQL Anywhere\10.0\EventLogMask
and it can be placed in either the HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE hive. To control event log entries, create a REG_DWORD value named EventLogMask and assign it a bit mask containing the internal bit values for the different Windows event types. The three types supported by the SQL Anywhere database server are:
EVENTLOG_ERROR_TYPE 0x0001 EVENTLOG_WARNING_TYPE 0x0002 EVENTLOG_INFORMATION_TYPE 0x0004
For example, if the EventLogMask key is set to zero, no messages appear at all. A better setting would be 1, so that informational and warning messages don't appear, but errors do. The default setting (no entry present) is for all message types to appear. Here is a sample registry change file.
REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\SQL Anywhere\10.0] "EventLogMask"=dword:00000007