QAnywhere provides C++, Java, and .NET API support for SQL Anywhere message stores. The Java and .NET APIs also support UltraLite message stores. The files required for deploying QAnywhere applications are based on your Windows environment, message store type, and API selection. Additional files are required if you are developing Mobile Web Service applications.
In addition to the files listed below, a QAnywhere application requires:
All files listed in the MobiLink synchronization client, Listener, and optionally the Security option sections for Deploying SQL Anywhere MobiLink clients. See SQL Anywhere MobiLink client deployment.
The MobiLink Listener files are required only if you are using push notifications, which is the default.
dbeng12 or dbsrv12 files. See Database server deployment.
To deploy Sybase Central, see Administration tool deployment.
Windows applicationsAll directories are relative to %SQLANY12%.
For more details on the file structure of a Windows Mobile environment, see Windows Mobile applications.
The following is a list of files required to set up a SQL Anywhere message store.
| Client API | Windows files |
|---|---|
| C++ |
|
| Java |
For Mobile Web Service applications, you also need the following:
|
| .NET |
For Mobile Web Service applications, you also need the following:
|
The following is a list of files required to set up an UltraLite message store with deployments using QAnywhere Agent.
| Client API | Windows files |
|---|---|
| Java |
For Mobile Web Service applications, you also need the following:
|
| .NET |
For Mobile Web Service applications, you also need the following:
|
When creating an UltraLite message store, you must create a udb database file using the UltraLite Create Database utility, then initialize the database using the QAnywhere UltraLite Agent's -si option. See UltraLite Initialize Database utility (ulinit) and qauagent utility.
The following is a list of files required to set up a deployment with the QAnywhere standalone client.
| Client API | Windows files |
|---|---|
| Java |
|
| .NET |
|
Windows Mobile applicationsAll directories are relative to %SQLANY12%.
For more details on the file structure of a Windows environment, see Windows applications.
The following is a list of files required to set up a SQL Anywhere message store.
| Client API | Windows Mobile files |
|---|---|
| C++ |
|
| Java |
For Mobile Web Service applications, you also need the following:
|
| .NET |
For Mobile Web Service applications, you also need the following:
|
The following is a list of files required to set up an UltraLite message store with deployments using QAnywhere Agent.
| Client API | Windows Mobile files |
|---|---|
| Java |
For Mobile Web Service applications, you also need the following:
|
| .NET |
For Mobile Web Service applications, you also need the following:
|
When creating an UltraLite message store, you must create a database file using the UltraLite Create Database utility, then initialize the database using the -si option for the QAnywhere UltraLite Agent. See UltraLite Initialize Database utility (ulinit) and qauagent utility.
The following is a list of files required to set up a deployment with the QAnywhere standalone client.
| Client API | Windows Mobile files |
|---|---|
| Java |
|
| .NET |
|
Registering the QAnywhere .NET API DLLThe QAnywhere .NET API DLL (Assembly\V2\iAnywhere.QAnywhere.Client.dll) needs to be registered in the Global Assembly Cache on Windows (except on Windows Mobile). The Global Assembly Cache lists all the registered programs on your computer. When you install SQL Anywhere, the installation program registers it. In Windows Mobile you do not need to register the DLL.
If you are deploying QAnywhere, you must register the QAnywhere .NET API DLL (Assembly\V2\iAnywhere.QAnywhere.Client.dll) using the gacutil utility that is included with the .NET Framework.
 |
Discuss this page in DocCommentXchange.
|
Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1 |