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 193 contains the DB2 Everyplace library files. The files
are located in \DB2Everyplace\Clients:
Table 193. 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 195. 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 197. 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