The following hardware is required for DB2 Everyplace:
You must have installed one of the following operating systems:
Download the IBM JDK from www.ibm.com/developerworks/java/jdk/.
For UNIX you must install a ksh shell before you install DB2 Universal Database (most UNIX systems have the ksh shell by default).
To use DB2 Everyplace, you must install the following software:
To install DB2 Everyplace on a Windows workstation:
If the DB2 Everyplace installation program does not open, begin installation by double-clicking the Setup.exe file located on the DB2 Everyplace CD-ROM.
If you have downloaded the installation program from the Web, run DB2Everyplacexxx.exe, where xxx is the 3-letter language code. When you execute this file, the installation files are extracted to your temporary directory and the setup program runs automatically.
If you selected to install DB2 Everyplace Sync Server, the installation program checks to ensure that you have installed DB2 Universal Database. If the installation program cannot detect DB2 Universal Database, you will be prompted to install it. The Sync Server installation will abort if it finds an incorrect version of DB2 Universal Database and if the edition of DB2 Everyplace that you are installing does not include the latest version of DB2 Universal Database.
Two new environment variables are included with the Sync Server:
After you complete the installation, select View additional setup tasks information and Create Sync Server sample databases for a brief tutorial on how to use the DB2 Everyplace Sync Server. The Create Sync Server sample databases program creates sample data and mirror tables for use with the tutorials. See the DB2 Everyplace Sync Server Administration Guide for information about how to get started using the Sync Server to replicate enterprise data to the mobile device and synchronize this data as changes are made.
Note: | DB2 Everyplace Sync Server is included only with DB2 Everyplace Enterprise Edition. |
After installing DB2 Everyplace to the Windows workstation, see Chapter 3, Installing DB2 Everyplace on a client for instructions on how to install the DB2 Everyplace libraries and sample files to a mobile, embedded, or emulated device.
Before you can use your mobile device to access DB2 databases, you must create a mid-tier server and set up replication for your databases. The mid-tier server, which is also referred to as a mirroring server, is used to cache data that is received when you synchronize from a mobile device. One mirroring server is used by many mobile devices to synchronize data. The data or updates that are destined for a DB2 database are held on the mirroring server until replication is performed between the database and the mirroring server. Replication can be set up to occur at regular intervals or done on demand. More detailed information about propagating data can be found in the DB2 Universal Database Replication Guide and Reference : .
The following sections tell you how to set up a mid-tier server, how to set up a sample database, how to enable replication, and what to do to test the servlet
If your source database exists on a different machine than the mid-tier server, you need to link to it from the DB2 Universal Database (UDB) Control Center. In the Control Center, you add the host system, create an instance for the host system, and then add the database to the host system using an alias for the name of the mid-tier database if necessary. You can create the mid-tier database from a DB2 command line (use the command: db2 create db), or use the Database Create wizard in the DB2 UDB Control Center. To create a mid-tier database on your local machine on the Sync Server instance, both the mid-tier database and the Sync Server control database (DSYCTLDB) must use the same code page.
On Windows operating systems, if you did not specify that you want to create the sample databases when you installed DB2 Everyplace, you can create the samples later by navigating to %DSYINSTDIR\Sample and executing the dsysample.exe file. The DB2 Everyplace Sync Server samples include
To replicate between the mirroring server and DB2 databases, you must create a table subscription for your databases. Replication is set up automatically when you install the Sync Server. If you want more information, see the DB2 Everyplace Sync Server Administration Guide :
To ensure that the Sync Server servlet to ensure that it can successfully communicate with clients. It is not necessary to have any clients installed to check the servlet. Use the following steps:
com.ibm.mobileservices.adapter.rdb.RDb <date> <time> DB2 Everyplace SyncServer 7.2.1 <build date>
If you receive a message that port 8080 is already taken by another program, change the port number. To change the port number go to $DSYINSTDIR/WebSphere/AppSrver/bin/servletengine.bat. Near the bottom of the file, change the port number in the following entry to any free port:
-Dcontrolserver.websphere.websphere.port=xxxx ...
This section describes how to install and configure the DB2 Everyplace engine and DB2 Sync Server on a UNIX operating system.
Ensure that you have installed all the required prerequisites. See Prerequisites. For UNIX operating systems, you must set some DB2 Universal Database parameters before using DB2 Everyplace.
export DISPLAY=nnn:0.0
where nnn is the name of the machine on which the Sync Server starts.
set shmsys:shminfo_shmseg = 256 set semsys:seminfo_semume = 256
To install DB2 Everyplace Sync Server on UNIX:
tar xvf DB2Everyplace_SyncServerInstall_[platform].tar
If you are using Solaris Operating Environment, execute this command before you un-tar the files:
gunzip DB2Everyplace_SyncServerInstall_solaris,tar.gz
su root
./setup
Running setup will install DB2 Everyplace Sync Server into the following directory:
The installation program lists the users that currently have DB2 instances on the system.
To install the client code:
Before you can use your mobile device to access DB2 databases, you must create a mid-tier server and set up replication for your databases. The mid-tier server, which is also referred to as a mirroring server, is used to cache data that is received when you synchronize from a mobile device. One mirroring server is used by many mobile devices to synchronize data. The data or updates that are destined for a DB2 database are held on the mirroring server until replication is performed between the database and the mirroring server. Replication can be set up to occur at regular intervals or done on demand. More detailed information about propagating data can be found in the DB2 Universal Database Replication Guide and Reference : .
The following sections tell you how to set up a mid-tier server, setting up a sample database, how to get started with replicating data, and what to do to test the servlet
If your source database exists on a different machine than the mid-tier server, you need to link to it from the DB2 Universal Database Control (UDB) Center. In the Control Center, you add the host system, create an instance for the host system, then add the database to the host system using an alias for the name of the mid-tier database if necessary. You can create the mid-tier database from a DB2 command line (use the command: db2 create db), or use the Database Create wizard in the DB2 UDB Control Center. To create a mid-tier database on your local machine on the Sync Server instance, both the mid-tier database and the Sync Server control database (DSYCTLDB) must use the same code page.
On Linux and Solaris operating systems, DB2 Everyplace Sync Server for UNIX includes a sample database configuration in the $DSYINSTDIR/Sample directory. You can install the sample database manually by entering ./ dsysample.sh on a DB2 command line. This script requires that the instance user ID and password be entered on the command line.
This sample database configuration includes the following components:
In order to replicate between the mirroring server and DB2 databases, you must create a table subscription for your databases. Replication is set up automatically when you install the Sync Server. If you want more information, refer to the DB2 Everyplace Sync Server Administration Guide : for information on how to define subscriptions and start replicating data.
To ensure that the Sync Server can successfully communicate with clients, check the servlet. It is not necessary to have any clients installed to check the servlet. Use the following steps:
com.ibm.mobileservices.adapter.rdb.RDb <date> <time> DB2 Everyplace SyncServer 7.2.1 <build date>
For AIX: If you are using WebSphere Application Server, do not preload the servlet by testing it from a Web browser.
For the Web application server that ships with DB2 Everyplace, you might receive a message that port 8080 is already taken by another program. If you receive this message, change the port number. To change the port number go to $DSYINSTDIR/WebSphere/AppSrver/bin/servletengine.sh. Near the bottom of the file, change the port number in the following entry to any free port:
-Dcontrolserver.websphere.websphere.port=xxxx ...
Where xxxx is any available port number.