This section provides information about installing DB2 Everyplace. The topics covered are:
There are several ways to transfer files to the client device. You can:
Related tasks
The Install on Mobile Devices tool is available only in the SDK version of DB2 Everyplace.
The Install on Mobile Devices tool for Windows workstations supports mobile devices that use the following operating systems:
Prerequisites
Before you install the DB2 Everyplace libraries and sample applications, you need to perform the following steps:
If you use the JDBC DB2 interface or ISync4J API, you need to install a Java Virtual Machine on your mobile device prior to installing DB2 Everyplace. This process applies to all client platforms.
Procedure
To install the DB2 Everyplace libraries and sample applications using the install tool:
For a Windows CE mobile device, perform a sync function to transfer the files to the mobile device.
More information on working with the sample application is available in Overview of the Visiting Nurse sample application.
Related tasks
Related reference
This section provides information about manually installing DB2 Everyplace on a mobile device. The topics covered are:
You can manually install the DB2 Everyplace libraries and sample applications on a mobile device. The operating systems that support this type of installation are:
Related tasks
This section describes how to manually install DB2 Everyplace libraries and sample applications on a Palm OS mobile device.
Prerequisites
Before you install the libraries and sample applications, you need to perform the following steps:
Procedure
To install the DB2 Everyplace libraries and sample application files manually:
Table 2. Palm OS database and sample files
File Name | Description |
---|---|
PalmOS\database\DB2eCat.prc | DB2 Everyplace database engine |
PalmOS\database\DB2eCLI.prc | DB2 Everyplace database engine |
PalmOS\database\DB2eComp.prc | DB2 Everyplace database engine |
PalmOS\database\DB2eRunTime.prc | DB2 Everyplace database engine |
PalmOS\database\DB2eDMS.prc | DB2 Everyplace database engine |
PalmOS\database\PBSPkcs11.prc | Encryption library |
utilities\lang\DB2eImport | DB2 Everyplace Import tool |
PalmOS\database\Samples\lang\SampleCLP\ DB2eCLP.prc | DB2 Everyplace Command Line Processor |
PalmOS\database\Samples\lang\Phone\Phone.prc | Phonebook sample program |
PalmOS\database\Samples\lang\Nurse\Nurse.prc | Visiting Nurse sample program |
PalmOS\database\Samples\lang\NurseInit\ NurseInit.prc | Visiting Nurse initialization program |
PalmOS\database\JDBC\cldc\sample\DB2eAppl.prc | Sample JDBC app for use with J9 CLDC |
PalmOS\database\JDBC\xtr\sample\DB2eAppl.prc | Sample JDBC app for use with J9 XTREME |
See Overview of DB2 Everyplace sample applications for information on the location of the sample applications.
Table 3. Palm OS SyncClient files
File Name | Description |
---|---|
dsyagent.prc | IBM Sync Remote Stored Procedure adapter |
imsaconfig.prc | IBM Sync Configuration adapter |
imsadb2e.prc | IBM Sync DB2 Everyplace adapter |
imsafile.prc | IBM Sync File adapter |
isyncconf.prc | IBM Sync engine |
isyncore.prc | IBM Sync engine |
isyncui.prc | IBM Sync interface |
wbxmllib.prc | IBM Sync WBXML library |
iUpgrade.prc | IBM Sync Auto Deploy |
isyncxpt.prc | IBM Sync transport library |
SSLlib.prc | IBM Sync SSL library |
Encryption support is available only on Palm OS 3.5 devices or later. The PBSPkcs11.prc file must be installed to use encryption between a Palm OS mobile device and the DB2 Everyplace Sync Server.
Related tasks
Related reference
This section describes how to install the DB2 Everyplace libraries and sample applications on a Windows CE mobile device.
Prerequisites
Before you install the files, you need to perform the following steps:
Procedure
To install the DB2 Everyplace libraries and sample application files manually:
Table 4. Windows CE device files
File Name | Description |
---|---|
wce300\proc\db2e.dll | DB2 Everyplace database engine |
wce300\proc\CryptoPlugin.dll | DB2 Everyplace database engine for data encryption |
wce300\proc\db2ejdbc.dll | DB2 Everyplace JDBC driver |
jdbc\db2ejdbc.jar | DB2 Everyplace JDBC driver |
See Overview of DB2 Everyplace sample applications for information on the location of the sample files.
where lang is the language code, ver is the WinCE
version, and proc is the processor type.
Table 5. Windows CE SyncClient files
File Name | Description |
---|---|
dsyagent.dll | IBM Sync Remote Stored Procedure adapter |
imsaconfig.dll | IBM Sync Configuration adapter |
imsadb2e.dll | IBM Sync DB2 Everyplace adapter |
imsafile.dll | IBM Sync File adapter |
isyncconf.dll | IBM Sync engine |
isyncore.dll | IBM Sync engine |
isyncxpt.dll | IBM Sync transport library |
isync4j.dll | IBM Sync Java adapter |
isync4j.jar | IBM Sync Java |
isyncui.exe | IBM Sync interface |
wbxmllib.dll | IBM Sync WBXML library |
upgrade\iupgrade.exe | IBM Sync Auto Deploy |
Table 6. Sync Client libraries for emulators
File Name | Description |
---|---|
\Clients\WinCE\sync\lang\wce300\X86EMRel | Pocket PC emulator |
\Clients\WinCE\sync\lang\wce300\X86Rel | Pocket PC 2002 emulator |
\Clients\WinCE\sync\lang\wce400\emulatorRel | WinCE .NET emulator |
Encryption support for Pocket PC 2000 is available only with the Microsoft High Encryption Pack for Pocket PC V1.0 available from www.microsoft.com/mobile/pocketpc/downloads/ssl128.asp. Encryption support for Pocket PC 2002 is available with the Pocket PC 2002 SDK under \Windows CE Tools\wce300\Pocket PC 2002\support\EnhancedCrypto. The Microsoft High Encryption Pack for Pocket PC must be installed to use encryption between Windows CE or Pocket PC mobile devices and the DB2 Everyplace Sync Server.
Related tasks
Related reference
This section describes how to install the DB2 Everyplace libraries and sample applications on a Symbian OS Version 6 mobile device.
Prerequisites
Before you install, you need to perform the following steps:
Procedure
To install the DB2 Everyplace libraries and sample application files
manually, use the Install Tool from the connection software that is included
with the Symbian OS Version 6 mobile device. Install the following
files. Table 7 contains the DB2 Everyplace libraries and sample application
files. They are located in
\DB2Everyplace\Clients\Symbian6\database. In the following
table, lang is a language code.
Table 7. DB2 Everyplace libraries and sample application files
File Name | Description |
---|---|
armi\DB2e.sis | DB2 Everyplace database engine |
armi\DB2eJDBC.sis | DB2 Everyplace JDBC driver |
install\lang\Crystal\armi\DB2e_Symbian6.sis | DB2 Everyplace package (all the above in a single package) |
The IBM Sync Client ISync.sis is located in
%DSYINSTDIR%\Clients\Symbian6\Sync\lang\proc\ | IBM Sync Client |
See Overview of DB2 Everyplace sample applications for information on the location of the sample applications.
Related tasks
Related reference
This section describes how to install the DB2 Everyplace libraries and sample applications on a Symbian OS Version 7 mobile device.
Prerequisites
Before you install you need to perform the following steps:
Procedure
To install the DB2 Everyplace libraries and the sample application files
manually, use the Install Tool from the connection software that is included
with the Symbian OS Version 7 mobile device. The files that you need to
install are listed in "DB2 Everyplace libraries and sample application files
for the database" and "IBM Sync Client libraries". The DB2
Everyplace libraries and sample application files are located in
\DB2Everyplace\Clients\Symbian7\database. In the following
table, lang is a language code.
Table 8. DB2 Everyplace libraries and sample application files for the database
File Name | Description |
---|---|
armi\DB2e.sis | DB2 Everyplace database engine |
armi\DB2eJDBC.sis | DB2 Everyplace JDBC driver |
samples\lang\SampleCLP\UIQ\armi\SampleCLP.sis | Command Line Processor (for the device) |
samples\lang\SampleCLP\UIQ\wins\SampleCLP.sis | Command Line Processor (for the emulator) |
samples\lang\PersonList\UIQ\armi\PersonList.sis | Sample application (for the device) |
samples\lang\PersonList\UIQ\wins\PersonList.sis | Sample application (for the emulator) |
install\lang\NurseInit\UIQ\wins\NurseInit.sis | Sample application (for the device) |
install\lang\UIQ\armi\DB2e_Symbian7.sis |
DB2 Everyplace package] This package includes:
|
The IBM Sync Client libraries are located in
\DB2Everyplace\Clients\Symbian7\sync\lang\proc\.
Table 9. IBM Sync Client libraries
File Name | Description |
---|---|
ISync.sis | IBM Sync Client |
| IBM Update Tool |
Related tasks
To test the synchronization on the device, make sure that the device is connected to the workstation using its connectivity software.
Procedure
Related tasks
Related reference
This section describes how to install DB2 Everyplace on a QNX Neutrino or embedded Linux mobile device. These mobile devices take various forms. Depending on the type of mobile device that you have, there are several installation options:
For additional information on transferring files to your mobile device, see the documentation provided with the mobile device. QNX Neutrino users can also consult the QNX Neutrino Software Developer's Kit (SDK).
Procedure
%DSYINSTDIR%/Clients/Linux/database/procwhere proc is your processor type.
libisyncxpt.so libimsaconfig.so libimsadb2e.so libimsafile.so libisyncore.so libisyncconf.so libwbxml.so goISync
Setting the environment variable
Set the environment variable, LD_LIBRARY_PATH, to the path where the DB2 Everyplace CLI shared library (libdb2e.so) was installed. For example, if the DB2 Everyplace CLI shared library is stored in /DB2e/database/x86, append /DB2e/database/x86 to your existing LD_LIBRARY_PATH using the following statement:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/DB2e/database/x86
Setting up encryption support
This section applies only to QNX Neutrino mobile devices. To enable encryption on a QNX Neutrino device, the mqueue process must be started.
If the application terminates unexpectedly after you initialized the encryption library, the library could be corrupted.
Running sample applications
Sample applications are included with the DB2 Everyplace database and the DB2 Everyplace Sync Server packages.
See Overview of DB2 Everyplace sample applications for more information on DB2 Everyplace sample applications for QNX Neutrino and Linux.
You can run the DB2 Everyplace Sync Server sample, goISync, from the directory where it is installed. After the first run, a subdirectory /data is created in this directory.
When you launch goISync for the first time, configure the settings for synchronization. To configure the settings:
You are now ready to synchronize.
Related tasks
Related reference
This section describes how to install the DB2 Everyplace library and sample files on a Sharp Zaurus device.
Procedure
The installation package db2e-libs_8.1.4_arm.ipk can be found in the %DSYINSTDIR%\Clients\linux\install directory. The db2e-libs_8.1.4_arm.ipk file contains the DB2 Everyplace and Sync Client libraries.
Use the Zaurus Manager software to install db2e-libs_8.1.4_arm.ipk onto the device. All *.so and *.jar will be installed under /usr/lib. The applications (goISync and SampleCLP) will be installed under /usr/bin.
You can also copy the DB2 Everyplace engine files and Sync Client files onto the device. For ARM the files are located:
%DSYINSTDIR%/Clients/linux/database/proc
%DSYINSTDIR%/Clients/linux/sync
Related tasks
This section describes how to install the DB2 Everyplace library and sample files on a MIDP supported device.
Prerequisites
You need to install a Web application server on your workstation before installing the DB2 Everyplace libraries and sample files. WebSphere Application Server 5.x, the embedded version of the IBM WebSphere(R) Application Server - Express V5.0, or Apache Tomcat can be configured to run with DB2 Everyplace You must install one of these application servers before continuing.
MIDP for DB2 Everyplace has been tested on several different devices including RIM, Nokia, and Motorola. The following section describes how to install if your carrier is Nextel. Some devices load their applications over a data cable, some using infrared ports. Refer to the manufacturer's documentation for details. Before you install the DB2 Everyplace libraries and sample files on one of these devices, you must download an update application, which enables you to transfer files to your phone. To download this application:
Both the VNurse.jad and VNurse.jar files are sent to the device during installation. The names of these files must match. If the file names are different, the installation will not succeed.
Procedure
To install the DB2 Everyplace libraries and sample application files:
Install the following files on the MIDP supported device. Table 10 contains the DB2 Everyplace library files. The files
are located in \DB2Everyplace\Clients:
Table 10. DB2 Everyplace library files
File Name | Description |
---|---|
Midp\lib\VNurse.jad | Visiting Nurse jad file |
Midp\lib\VNurse.jar | Visiting Nurse non-debug jar file |
You can use these files to develop your own MIDP applications or work with the sample application:
File Name | Description |
---|---|
ISyncMidp.jar | MIDP ISync/Java API non-debug archive |
ISyncMidpDebug.jar | MIDP ISync/Java API debug archive |
Table 12. Sample JAD and JAR files
File Name | Description |
---|---|
Dump.jad | Dump utility jad file |
Dump.jar | Dump utility jar file for Dump.jad file |
Dump1.jad | Dump utility jad file |
DumpDebug.jar | Debug version of Dump utility |
VNurseDebug.jad | Vistiting Nurse jad file |
VNurseDebug.jar | Vistiting Nurse non-debug jar |
VNurseDebug1.jad | jad file for user1/user1/221 device id |
VNurseDebug2.jad | jad file for user2/user2/222 device id |
VNurseDebug3.jad | jad file for user3/user3/223 device id |
VNurseDebug4.jad | jad file for user4/user4/224 device id |
VNurseDebugt5.jad | jad file for user5/user5/225 device id |
File Name | Description |
---|---|
com\ibm\mobileservices\demo\Dump.java | Sample Source |
com\ibm\mobileservices\demo\ NursesAid.java | Aid to VNurse |
com\ibm\mobileservices\demo\VNurse.java | Sample Source |
ISyncSample.java | Simple MIDP Synchronization examples |
ISyncWorker.java | Simple MIDP Synchronization examples |
Table 14. Filter servlet setup files
File Name | Description |
---|---|
lib\FilterServlet.jar | MIDP Servlet non-debug jar file |
lib\FilterServletDebug.jar | MIDP Servlet debug jar file |
bin\dsytomcat.bat | Tomcat startup file |
The Debug files are too large to fit on most devices, and display lots of trace output. They are intended for debugging your application during development in your IDE of choice. The numbered VNurse.jad files define various user, and password combinations that can run from the Sun Wireless Toolkit emulator (Midp/bin/run.bat). If you want to use one of these files on a phone, the root file name must match the JAR file. For example, VNurse3.jad must be renamed to VNurse.jad before you load it on a phone.
If you want to develop your own applications using the MidpISync.jar and the enclosed build.bat (ANT script) file, you can download and install the following software programs:
Related tasks
Related reference
You can install the DB2 Everyplace client on a Win32 client where you will write application programs for DB2 Everyplace.
Procedure
Table 15. Application program files
File Name | Description |
---|---|
x86\DB2e.dll | DB2 Everyplace database engine |
x86\CryptoPlugin.dll | DB2 Everyplace database engine for data encryption |
x86\DB2eJDBC.dll | DB2 Everyplace JDBC driver |
jdbc\DB2eJDBC.jar | DB2 Everyplace JDBC driver |
jdbc\DB2eAppl.class | Sample Java application |
jdbc\DB2eJavaCLP.class | Command Line Processor written in Java |
samples\lang\sampleCLP\Release\ SampleCLP.exe | Command Line Processor (ANSI version) |
samples\lang\sampleCLP\ReleaseU\ SampleCLPU.exe | Command Line Processor (UNICODE version) |
samples\VisualBasic\DB2eSample.exe | Sample application written in Visual Basic |
File Name | Description |
---|---|
dsyagent.dll | IBM Remote Stored Procedure adapter |
testisync.exe | IBM Sync interface |
imsaconfig.dll | IBM Sync Configuration adapter |
imsadb2e.dll | IBM Sync DB2 Everyplace adapter |
imsafile.dll | IBM Sync File adapter |
isyncconf.dll | IBM Sync Configuration adapter |
isyncore.dll | IBM Sync DB2 Everyplace adapter |
isync4j.dll | IBM Sync Java adapter |
isync4j.jar | IBM Sync Java |
wbxmllib.dll | IBM Sync WBXML library |
isyncxpt.dll | IBM Transport library |
Encryption support is available only with the Microsoft Strong Encryption download available from www.microsoft.com/TechNet/security/crypload.asp. The Microsoft Strong Encryption download for your operating system must be installed to use encryption between Win32 clients and the DB2 Everyplace Sync Server.
Related tasks
Related reference
This section provides information about how to update your Sync Client software using the Update tool. The topics covered are:
The DB2 Everyplace Update Tool provides a user-friendly solution for Sync Client users who want to upgrade their client software. Instead of physically bringing your mobile device into a service station to retrieve files, you can launch the DB2 Everyplace Update Tool to download new IBM Sync files for you. This tool is available on the following platforms:
Prerequisites
Before you update Sync Client software using the DB2 Everyplace Update Tool, you must complete the following steps:
Procedure
To run the update tool from your mobile device:
On Symbian operating systems, the update tool places all IBM Sync Client DLLs into C:\System\Libs and the sample application into C:\System\Apps\ISync by default. These paths can be changed in the Advanced panel. If the files are downloaded from the server successfully, a dialog window prompts you to specify the new target directory as part of the final update process. The target directory is where configuration and data files will be stored in the version 8 client, which by default is C:\System\Data\ISync. Configuration files from IBM Sync Client version 7 will be copied over to this new target directory for version 8. The update tool does not update the versions of DB2 Everyplace and Sync Server applications in the Install/Remove programs on the Control Panel. Instead of downloading individual DLLs, you may choose to download only ISync.sis and DB2e.sis by modifying the DSYDeploy.properties file on your server. Once these two files are received and placed into C:\System\Libs, you can manually install them on the device, and the proper versions will be reflected.
On WinCE operating systems, the update tool places all IBM Sync Client DLLs into \Windows and the sample application into \Windows\Start by default. These paths can be changed in the Advanced panel. If the files are downloaded from the server successfully, a dialog window prompts you to specify the new target directory as part of the final update process. The target directory is where configuration and data files will be stored in the version 8 client, which by default is the root directory (\). Configuration files from IBM Sync Client version 7 will be copied over to this new target directory for version 8.
Related tasks
Related reference
Before you install and run the DB2 Everyplace Update Tool, you need to modify the DSYDeploy.properties file on your server. This properties file tells the server where to locate the updates that are being sent to a client device.
This task is part of the main task of Updating Sync Client software using the DB2 Everyplace Update Tool. After you complete these steps, return to Updating Sync Client software using the DB2 Everyplace Update Tool.
Restrictions
You must have the DB2 Everyplace Synchronization Server Version 8.1 or later to use the update tool.
Procedure
Palm.M68.prc.syncserver=
Palm.M68.prc.syncserver=c:\db2everyplace\Clients\PalmOS\Sync\upgrade\
iUpdate will send all the files with the .prc extension in this directory to the device.
Related tasks
Related reference
You must install the DB2 Everyplace Update Tool after you install DB2 Everyplace on a server and mobile device. The DB2 Everyplace Update Tool can be installed manually or by creating a file subscription that is synchronized to one or more mobile devices.
This task is part of the main task of Updating Sync Client software using the DB2 Everyplace Update Tool. After you complete these steps, return to Updating Sync Client software using the DB2 Everyplace Update Tool.
Procedure
To install the DB2 Everyplace Update Tool manually:
For information about installing DB2 Everyplace files manually on Palm OS, WinCE, and Symbian6 platforms, see Installing DB2 Everyplace files manually.
To install the update tool using a file subscription:
Before you close the Mobile Devices Administration Center, make sure that the correct groups and users are assigned to the subscription set that contains the new file subscription.
Related tasks
Related reference
Table 2 below lists all of the error messages that can be generated by the DB2
Everyplace Update Tool. Table 17 displays the error message and a possible remedy for the
problem.
Table 17. Troubleshooting Guide
Error message | Possible remedy |
---|---|
Authentication failed (invalid encryption key) - update aborted | Verify that the client settings match the user's settings defined in the Mobile Device Administration Center. |
File size exceeds available memory | Delete any applications or files that are no longer needed on the device and try again. |
Internal server error | This is an internal error that you need to report to IBM Software Support with the trace file. |
Failed to open connection | Check your network connection and the SyncServer. Make sure that the host is connected and the server is running. |
Failed to establish connection | Check your network connection and the SyncServer. Make sure that the host is connected and the server is running. |
Failed to send request | Try to synchronize again when there is less traffic on the network or try to synchronize from a faster network. |
Failed to receive reply | Try to synchronize again when there is less traffic on the network or try to synchronize from a faster network. |
Timeout while receiving reply | Specify a larger timeout value or try to synchronize when there is less traffic on the network. |
Failed to receive acknowledge | Try to synchronize again when there is less traffic on the network or try to synchronize from a faster network. |
Failed to open Net library | Verify that the network library exists on the device. Try to reinstall the library. |
Failed to resolve hostname | Verify that the hostname and the DNS addresses are correct. |
Failed to allocate working buffer for transport | Delete any applications or files that are no longer needed on the device and try again. |
Unknown network error | This is an internal error that you need to report to IBM Software Support with the trace file. |
Failed to create target file | Verify that the target file is not being used by another application. If the target file is being used, unlock it and synchronize again. |
No files received for update | This is an informational message stating that the server does not have an update for the mobile device. |
Related tasks