The simplest way to deploy a MobiLink server into a production environment is to install a licensed copy of SQL Anywhere onto the production computer.
However, if you are redistributing a MobiLink server in a separate installation program, you may want to include only a subset of the files. In this case, you need to include the following files in your installation.
NotesTest on a clean computer before redistributing.
Files must be installed to the SQL Anywhere installation directory, with the exception of samples.
The files should be in the same directory unless otherwise noted.
When a location is given, the files must be copied into a directory of the same name.
On Unix, environment variables must be set for the system to locate SQL Anywhere applications and libraries. It is recommended that you use the appropriate file for your shell, either sa_config.sh or sa_config.csh (located in the directory install-dir/bin32 for 32-bit environments and install-dir/bin64 for 64-bit environments) as a template for setting the required environment variables. Some of the environment variables set by the sa_config files include PATH, LD_LIBRARY_PATH, SQLANY12, and SQLANYSAMP12.
On Windows, the PATH environment variable must be set for the system to locate SQL Anywhere applications and libraries. Check the PATH variable to ensure that it includes install-dir\bin32 for 32-bit environments or install-dir\bin64 for 64-bit environments. If both entries exist, remove the path that does not apply to your environment.
To use Java synchronization logic, and to use the graphical administration tools (Sybase Central and the MobiLink Monitor), you must have JRE 1.6.0 installed.
To deploy Sybase Central, see Deploying administration tools.
There is a deployment wizard for Windows. See Using the Deployment Wizard.
Windows 32-bit applicationsAll directories are relative to install-dir. For more details on the file structure of a 64-bit Windows environment, see Windows 64-bit applications.
| Description | Windows files |
|---|---|
| MobiLink server |
|
| Language library |
|
| Synchronization stream libraries (to support version 8 and 9 clients) |
|
| Java synchronization logic |
|
| .NET synchronization logic |
|
| Security option for version 10 and later clients (mlsrv12 -x)3 |
|
| Setup scripts (deploy the ones for your consolidated database) |
|
| mluser utility |
|
| mlstop utility |
|
| mlreplay utility |
|
| MobiLink arbiter |
|
| MobiLink Monitor |
For security with the MobiLink Monitor:3
|
| Online help for the MobiLink 12 plug-in and MobiLink Monitor |
|
| Notifier |
|
| MobiLink server files required by QAnywhere |
|
| Relay Server Outbound Enabler |
For security with the Outbound Enabler:
|
| Integrated Outbound Enabler |
|
1 For German, Japanese, and Chinese editions, substitute en with de, ja, and zh, respectively.
2 If you are redistributing an application, you must obtain these files directly from Sun.
3 ECC and FIPS require that you obtain the separately-licensed SQL Anywhere security option and is subject to export regulations. RSA security is included with SQL Anywhere for version 10 and later. To order this component, see Separately licensed components.
4 If you are redistributing an application, you must obtain this file directly from Apache.
5 You must also create a registry key called HKEY_LOCAL_MACHINE\SOFTWARE\Certicom\libsb and add a REG_BINARY value named expected tag with the data 5B0F4FA6E24AEF3B4407052EB04902711FD991B6.
Windows 64-bit applicationsAll directories are relative to install-dir. For more details on the file structure of a 32-bit Windows environment, see Windows 32-bit applications.
| Description | Windows files |
|---|---|
| MobiLink server |
|
| Language library |
|
| Synchronization stream libraries (to support version 8 and 9 clients) |
|
| Java synchronization logic |
|
| .NET synchronization logic |
|
| Security option for version 10 and later clients (mlsrv12 -x)3 |
|
| Setup scripts (deploy the ones for your consolidated database) |
|
| mluser utility |
|
| mlstop utility |
|
| mlreplay utility |
|
| MobiLink arbiter |
|
| MobiLink Monitor |
For security with the MobiLink Monitor:3
|
| Online help for the MobiLink 12 plug-in and MobiLink Monitor |
|
| Notifier |
|
| MobiLink server files required by QAnywhere |
|
| Relay Server Outbound Enabler |
For security with the Outbound Enabler:
|
| Integrated Outbound Enabler |
|
1 For German, Japanese, and Chinese editions, substitute en with de, ja, and zh, respectively.
2 If you are redistributing an application, you must obtain these files directly from Sun.
3 ECC and FIPS require that you obtain the separately-licensed SQL Anywhere security option and is subject to export regulations. RSA security is included with SQL Anywhere for version 10 and later. To order this component, see Separately licensed components.
4 If you are redistributing an application, you must obtain this file directly from Apache.
5 You must also create a registry key called HKEY_LOCAL_MACHINE\SOFTWARE\Certicom\libsb and add a REG_BINARY value named expected tag with the data 5B0F4FA6E24AEF3B4407052EB04902711FD991B6.
Unix 32-bit applications on Unix, Linux, and Mac OS XAll directories are relative to install-dir. For more details on the file structure of a 64-bit Unix environment, see Unix 64-bit applications on Unix and Linux.
| Description | Unix files |
|---|---|
| MobiLink server |
|
| Language library |
|
| Synchronization stream libraries for version 8 and 9 clients (deploy the ones you use) |
|
| Java synchronization logic |
|
| .NET synchronization logic |
|
| Security option for version 10 and later clients (mlsrv12 -x)4 |
|
| Setup scripts (deploy the ones for your consolidated database) |
|
| mluser utility |
|
| mlstop utility |
|
| mlreplay utility |
|
| MobiLink arbiter |
|
| MobiLink Monitor |
|
| Notifier |
|
| MobiLink server files required by QAnywhere |
|
| Relay Server Outbound Enabler |
For security with the Outbound Enabler:
|
| Integrated Outbound Enabler |
|
1 For German, Japanese, and Chinese editions, substitute en with de, ja, and zh, respectively.
2 If you are redistributing an application, you must obtain these files directly from Sun.
3 For Linux, the file extension is .so. For Mac OS X, the file extension is .dylib.
4 Transport-layer security requires that you obtain the separately-licensed SQL Anywhere security option and is subject to export regulations. To order this component, see Separately licensed components.
5 If you are redistributing an application, you must obtain these files directly from Apache.
Unix 64-bit applications on Unix and LinuxAll directories are relative to install-dir. For more details on the file structure of a 32-bit Unix environment, see Unix 32-bit applications on Unix, Linux, and Mac OS X.
| Description | Unix files |
|---|---|
| MobiLink server |
|
| Language library |
|
| Synchronization stream libraries for version 8 and 9 clients (deploy the ones you use) |
|
| Java synchronization logic |
|
| .NET synchronization logic |
|
| Security option for version 10 and later clients (mlsrv12 -x)4 |
|
| Setup scripts (deploy the ones for your consolidated database) |
|
| mluser utility |
|
| mlstop utility |
|
| mlreplay utility |
|
| MobiLink arbiter |
|
| MobiLink Monitor |
|
| Notifier |
|
| MobiLink server files required by QAnywhere |
|
| Relay Server Outbound Enabler |
For security with the Outbound Enabler:
|
| Integrated Outbound Enabler |
|
1 For German, Japanese, and Chinese editions, substitute en with de, ja, and zh, respectively.
2 If you are redistributing an application, you must obtain these files directly from Sun.
3 For Solaris SPARC and Linux, the file extension is .so. For IBM AIX, the file extension is .a.
4 Transport-layer security requires that you obtain the separately-licensed SQL Anywhere security option and is subject to export regulations. To order this component, see Separately licensed components.
5 If you are redistributing an application, you must obtain these files directly from Apache.
 |
Discuss this page in DocCommentXchange.
|
Copyright © 2010, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.0 |