IBM DB2 Everyplace Enterprise Edition
Installation Notes
Version 8.2
Copyright International Business Machines Corporation 1998, 2004. All rights reserved.
US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
DB2 Everyplace Enterprise Edition installation notes for version 8.2
Welcome to the DB2 Everyplace Enterprise Edition installation notes for
version 8.2. These notes provide information about:
- Migration considerations
- System requirements
- Installing DB2 Everyplace files on a server
- Installing DB2 Everyplace files on one or more mobile devices (or emulators)
- Configuring DB2 Everyplace
- Starting the First Steps launchpad
- Troubleshooting installation and configuration problems
- Removing DB2 Everyplace
Migrating
If you are migrating
from an earlier version of DB2 Everyplace, refer to the migration
instructions in the
DB2 Everyplace installation and user's guide
for version 8.2, available for download at the following location:
http://www.ibm.com/software/data/db2/everyplace/library.html
Installing
Before
installing DB2 Everyplace
Adjusting
system parameters for Linux
In order for DB2 Everyplace to
operate with the highest degree of efficiency, system parameters need to
be adjusted. Failure to do so can result in the inability to create a
new connection to the database on Linux. It is recommended that the
kernel parameters are adjusted.
Note:
Only
32-bit DB2 Universal Database instances are
supported.
Modify the login profile to include
the following: export
DISPLAY=hostname:0.0
Where
hostname
is the workstation where you want to use the Mobile Devices
Administration Center.
- For Linux systems running kernel
2.4 or higher, issue the following commands on the command line as the
root user:
- sysctl -w kernel.msgmni=2048
- sysctl -w kernel.shmmax=1073741824
- sysctl -w fs.file-max=32768
- sysctl -w kernel.sem="512 32000 32 1024"
- sysctl -w kernel.threads-max=20480
- To
execute the commands automatically, edit the file
/etc/rc.d/rc.local,
and place the above commands at the end of the file. On every
subsequent system boot, the values will be set automatically. Additional
setting recommendations can be found in the Linux 7.2 Release Notes for
the fix pack you are running.
Adjusting
system parameters for Solaris
In order for DB2 Everyplace to
operate with the highest degree of efficiency, system parameters in DB2
Universal Database need to be adjusted. Failure to do so can result in
unexpected interruptions. It is recommended that the kernel parameters
are adjusted.
Note:
Only
32-bit DB2 Universal Database instances are
supported.
Prerequisites
Modify the login profile to include
the following:
export DISPLAY=hostname:0.0
Where
hostname
is the workstation where you want to use the Mobile Device
Administration Center.
- For Solaris systems, the default
system kernel parameters are insufficient to run DB2 Universal Database
and DB2 Everyplace. These values can be added or edited in the file,
/etc/system.
- The
format for setting these values is: set parameter_name =
value
- The
suggested parameters in the DB2 Universal Database should be adjusted to
include the following minimum values:
set shmsys:shminfo_shmseg = 256
set semsys:seminfo_semume = 256
- After
modification of any kernel parameters, reboot the system to make the
kernel settings effective.
Installing
DB2 Everyplace Enterprise Edition
You need to install the DB2
Everyplace Sync Server on a server, and install the DB2 Everyplace
mobile database and Sync Client software on each mobile device or
emulator that connects to the server. Requirements vary depending on the
hardware, software, and operating system of the target server, device,
or emulator.
After you install and configure
DB2 Everyplace, you can start the First Steps launchpad, which provides links to sample
applications and other resources that will help you get started using
DB2 Everyplace.
DB2
Everyplace Enterprise Edition installation requirements
Hardware requirements
The exact configuration you need to
support your environment with satisfactory response time will vary
depending on the size of the objects you are working with and other
factors. Individual display response times vary depending on workstation
speed, memory, size of objects, and network and server workload. Minimum
recommended configurations must be evaluated and adjusted according to
your unique requirements. Disk space recommendations are for the product
installation and working space only. The actual hard disk space required
varies depending upon your configuration choices.
To use DB2 Everyplace Enterprise Edition, your
system must meet the following hardware requirements:
- Intel Pentium III, AMD Athlon,
AMD64, SPARC (for Solaris), POWER (for AIX and SUSE Linux Version 8.1),
or comparable processor
- 1 GB of memory (2 GB
recommended)
- 1 GB of free disk space to
install DB2 Everyplace Enterprise Edition. Configuration requires
additional space; the amount of space required depends on the kind of
configuration. The DB2 Everyplace Configuration wizard returns an error
if the target computer does not have enough disk space for a specified
configuration.
Table 1. Disk space requirements for configuration types
| Configuration type |
(Windows) Disk space required on the target hard drive |
(Linux and UNIX) Disk space required in the user's home
directory for each DB2 Everyplace Sync Server instance |
| Basic |
400 MB (if using Database message
store)
350 MB (if using File system
message store) |
520 MB (if using Database message
store)
470 MB (if using File system
message store) |
| Distributed
database |
300 MB (if using Database message
store)
250 MB (if using File system
message store) |
420 MB (if using Database message
store)
370 MB (if using File system
message store) |
| Distributed
Server |
200 MB |
320
MB |
| Cluster
configuration (local databases) |
300 MB |
420
MB |
| Cluster
configuration (remote databases) |
100
MB |
220
MB |
| Remote
administration |
100
MB |
220
MB |
Software requirements
The DB2 Everyplace Sync Server requires the
following software:
- Workstation to mobile device
connection software, such as Palm HotSync, that enables the server and a
mobile device to communicate. This software is not provided with DB2
Everyplace. You must obtain it from another source such as the device
manufacturer's web site.
- Optional: DB2 Universal Database
Version 8.1 or 8.2. Do not upgrade the UDB level while DB2 Everyplace is
installed. Instead, remove DB2 Everyplace, upgrade UDB, and then install
DB2 Everyplace again. If the DB2 Everyplace installer does not find DB2
Universal Database, it installs an embedded version of DB2 Universal
Database Enterprise Server Edition with limited functionality.
- The DB2 Everyplace Sync Server
also uses an embedded version of WebSphere Application Server - Express.
The DB2 Everyplace Sync Server can run with the embedded Application
Server-Express or with IBM WebSphere Application Server Version 5 FixPak
2 or later.
Operating system requirements
DB2 Everyplace Enterprise Edition runs on the
following operating systems:
- For the DB2 Everyplace Sync Server:
-
- AIX (Korn shell or compatible
environment required)
- 5.1 Maintenance Level 5100-04 and
above
- 5.2 Maintenance Level 5200-01 +
APAR IY44183
- 5.2 Maintenance Level 5200-02
and above
- Mandrake Linux Version 8.2 and
9.2 (Intel and AMD x86 processors)
- Red Hat Linux Version 7.3 and
8.0 (Intel and AMD x86 processors)
- Red Hat Enterprise Linux 2.1 and
3 (Intel and AMD x86 processors)
- SUSE Linux Version 8.1 (Linux
for iSeries and POWER processors)
- Sun Solaris Version 8 and 9
(Korn shell or compatible environment required)
- Microsoft Windows 2000 Server
SP3 and SP4
- Microsoft Windows XP
Professional SP1
- Microsoft Windows 2003 Server,
Enterprise
- For the DB2 Everyplace Database and Sync Client:
-
- Java 2 Micro Edition Mobile
Information Device Profile Virtual Machine (Express Edition and
Enterprise Edition synchronization client only)
- Linux and embedded Linux Kernel
2.4
- Microsoft Pocket PC, Pocket PC
2000, Pocket PC 2002, Handheld PC 2000, Windows Mobile 2003 for Pocket
PC, and Windows CE .NET
- Microsoft Windows 2000, Windows
XP, and Windows 2003 Server (for the DB2 Everyplace and IBM Cloudscape
Version 10 mobile databases)
- Palm OS 4.1, 5.0, and 5.2
- QNX Neutrino 6.2
- Symbian OS Version 7
Operating system requirements vary
depending on the target device's processor. See Table 4 for more information.
- Device considerations and limitations
-
- The design of some devices may
limit the DB2 Everyplace capabilities that can be used by the device.
Not all devices can support all of the functions offered by DB2
Everyplace.
- IBM cannot guarantee that all
devices will work correctly due to differences in manufacturing,
configuration and pre-loaded device software.
- Some DB2 Everyplace clients for
the supported devices are available as downloads rather than being
included on the DB2 Everyplace media.
- Availability of devices and the
level of device support may change over time based on the device
manufacturers' actions. Some devices may go out of support, or new
devices may be added.
Supported source databases
- DB2 Universal Database Version
8.1 and 8.2 for Windows, Linux, AIX, HP-UX, and Solaris
- DB2 Universal Database Version
7.1 and 8.1 for IBM z/OS
- DB2 Universal Database V5R1 and
V5R2 for IBM iSeries
- IBM Cloudscape Version 10
- Informix Dynamic Server 9.4
(with Informix JDBC driver)
- Lotus Domino Server 6.0.2
- Microsoft SQL Server 2000 with
Service Pack 3a (V8.00.760 with SQL Server Driver for JDBC)
- Oracle 9i and 10g
- Sybase Adaptive Server
Enterprise 11.93 (with Sybase J-Connect 5.5 for JDBC)
Installing
DB2 Everyplace Enterprise Edition on a server
Setting up DB2 Everyplace
Enterprise Edition on a server is a two-step process: copy DB2
Everyplace files from a source to the server, then configure the
environment.
Prerequisites:
- Windows
- Log in as an
administrator.
- Linux and UNIX
-
For all supported operating
systems, the server must meet or exceed the requirements specified in
DB2
Everyplace Enterprise Edition installation requirements.
To install DB2 Everyplace Enterprise Edition on a server:
Choose one of the following
methods:
After installing DB2 Everyplace files, you must configure the runtime environment.
Installing
DB2 Everyplace Enterprise Edition by using the Installation
wizard
The DB2 Everyplace Installation
wizard copies files from a source (such as a CD or compressed archive)
to a server. You can choose one of the following installation types:
- Typical
- Copies a predefined set of
files to default locations relative to a directory you specify.
- Custom
- You specify the files to copy
(for example, to support specific mobile devices). A custom installation
also allows you to save your specifications in a response file that you
can use to automate the installation process on other computers at a
later time.
To install DB2 Everyplace Enterprise Edition by using the
Installation wizard:
- Start the DB2 Everyplace
Launchpad
The procedure for starting the
Launchpad varies depending on your operating system and whether you are
installing from a CD or a downloaded archive.
Table 2. Starting the DB2 Everyplace Launchpad from a CD
| Operating system |
Procedure |
| Windows |
The
Launchpad starts automatically when you insert the CD. |
| Linux |
- Mount the CD.
- Run
dsysetup as the root
user.
|
| AIX and
Solaris |
- Mount the CD labeled Disc
1
- Copy Disc 1 to a temporary
directory, hereafter referred to as $TMPDIR.
- Mount the CD labeled Disc
2.
- Copy Disc 2 to $TMPDIR.
- Run
dsysetup as the root
user.
|
Table 3. Starting the DB2 Everyplace Launchpad from an archive
| Operating system |
Procedure |
| Windows |
- Unzip the archive file.
- Run the
DB2EveryplaceEnterprise82Windows\
dsysetup.exe file.
|
| Linux |
- Untar the archive file.
- Change the working directory
to
DB2EveryplaceEnterprise82Linux
- Run the
./dsysetup command as
root.
|
| Linux for
iSeries |
- Untar the archive file.
- Change the working directory
to
DB2EveryplaceEnterprise82iLinux
- Run the
./dsysetup command as
root.
|
| AIX |
- Untar the archive file.
- Change the working directory
to
DB2EveryplaceEnterprise82AIX
- Run the
./dsysetup command as
root.
|
| Solaris |
- Untar the archive file.
- Change the working directory
to
DB2EveryplaceEnterprise82Solaris
- Run the
./dsysetup command as
root.
|
- Click
Install to
start the Install wizard. You can also read release notes and
installation instructions from the launchpad.
- Proceed
by following the wizard's prompts. DB2 Everyplace files are not
copied to your system until you click
Next in the
Pre-installation Summary page.
After copying the files to the server, you must configure the installation before you use the DB2 Everyplace Sync Server or the DB2 Everyplace Mobile Devices Administration Center. You can start the Configuration wizard from the Installation wizard by clicking Configure in the Post-Install Summary panel, or you
can start the wizard manually later. You can also configure the
installation by using the command line configuration tool.
Installing
DB2 Everyplace Enterprise Edition by using a response file and the
command line installation tool
The command line installer reads
input from a file called a response file, and can automatically install DB2
Everyplace on multiple systems. A response file is an ASCII text file
that contains setup data. The response file can be generated either by
performing a custom installation with the DB2 Everyplace Installation
wizard or by manual editing.
To install DB2 Everyplace by using a response file and the
command line installation tool:
- Open a command window and
navigate to the top level directory of the CD or archive.
The command line installer,
installSilent, is in
the top level directory of the CD or archive.
- Run
the installSilent
command.
- Windows
- installSilent.bat
full_path_to_response_file
- Linux and UNIX
- ./installSilent.sh
full_path_to_response_file
A sample response file is
provided in the lib
directory of the CD or archive.
The following example starts the
command line installation tool on Windows and specifies
C:\lib\db2eSilent.rsp
as the response file.
C:\>installSilent.bat
C:\lib\db2eSilent.rsp
On a mobile
device
Supported
mobile device processors and operating systems
In the following table, supported
combinations of mobile device processors and operating systems are
marked with an X. Availability of devices and the level of device
support may change over time based on device manufacturer's actions.
Some devices may go out of support; new devices may be added.
Table 4. Supported mobile device processors and operating systems
| Processor / OS |
ARM |
ARM
v4T |
Strong ARM |
x86 |
XScale |
WINS |
MIPS |
| Palm OS
4.1 |
X |
|
|
|
|
|
|
| Palm OS
5.0 |
X |
|
|
|
|
|
|
| Palm OS
5.2.1 |
X |
|
|
|
X |
|
|
| Windows(R) CE v3 |
X |
|
|
|
|
|
X |
| Windows CE v4 |
X |
X |
|
X |
X |
|
X |
| Symbian OS
7 |
X |
|
|
|
|
X |
|
| Linux(TM) |
|
|
X |
X |
X |
|
|
| QNX
Neutrino |
|
|
X |
X |
|
|
|
| Windows 2000 / XP / 2003 Server |
|
|
|
X |
|
|
|
The design of some devices may limit
the DB2(R)
Everyplace(R) capabilities
that can be used by the device. Not all devices can support all of the
functions offered by DB2
Everyplace.
IBM(R) cannot guarantee that
all devices will work correctly due to differences in manufacturing,
configuration and preloaded device software. Some
DB2
Everyplace clients for the
supported devices are available as downloads rather than being included
on the DB2
Everyplace media.
Installing
DB2 Everyplace files on a Linux mobile device
Prerequisites:
Prerequisites for installing DB2
Everyplace files on a Linux mobile device vary depending on the
device.
Linux mobile devices take various
forms. Depending on the type of mobile device that you have, there are
several installation options. For example, you could transfer files to
your mobile device by using one of the following methods, depending on
the type of mobile device and how that mobile device is configured:
- Serial connection between the
mobile device and your workstation using XModem or Kermit protocols
- Ethernet connection between the
mobile device and your workstation using FTP software
- Floppy disk, if supported by your
mobile device
The following table lists required
run-time libraries for various processors.
Table 5. Required run-time libraries
| Processor |
Library |
| x86 |
glibc-2.2.4-13 |
| StrongARM |
glibc-2.2.5 |
| XScale |
glibc-2.2.5 |
To install DB2 Everyplace files on a Linux mobile
device:
- Install the DB2 Everyplace
mobile database files.
DB2 Everyplace mobile database
files for Linux mobile devices are in the
%DSYINSTDIR%\Clients\linux\database\
directory, where proc is a processor type, for example, strongarm or
x86, and lang represents the language.
The file names are:
- proc\libcryptoplugin.so
- proc\libdb2e.so
- proc\libdb2ejdbc.so
- proc\libvcpkcs11.so
- jdbc\db2ejdbc.jar
- jdbc\DB2eAppl.class
- lang\DB2eCLP\proc\DB2eCLP
- Install
the DB2 Everyplace Sync Client files.
The files are located in
%DSYINSTDIR%\clients\linux\sync\proc, where
proc is
a processor type, for example, strongarm or x86.
Copy the following library files
for the appropriate processor into
usr/lib/DB2e/:
- libimsaconfig.so
- libimsadb2e.so
- libimsafile.so
- libisync4j.so
- libisyncconf.so
- libisyncore.so
- libisyncstat.so
- libisyncxpt.so
- libwbxml.so
- isync4j.jar
DB2 Sync console is located at
%DSYINSTDIR%\Clients\linux\sync\lang\proc\db2sync_console where
proc
represents a processor type and
lang
represents the
language.
Note:
The
SSL libraries for Linux are no longer packaged with the sync client in
DB2 Everyplace 8.2. Obtain the OpenSSL libraries (libcrypto.so,
libssl.so) separately from http://www.openssl.org. DB2 Everyplace 8.2
currently only supports version 0.9.7. Optionally, for Sharp Zaurus
devices, install the .ipk file that contains both the database and sync
client libraries.
- Set
the environment variable LD_LIBRARY_PATH
to the path where the DB2 Everyplace CLI shared library
(libdb2e.so) is
installed.
For example, if the DB2 Everyplace
CLI shared library is in the
%DSYINSTDIR%\database\x86
directory, append
%DSYINSTDIR%\database\x86
to the existing LD_LIBRARY_PATH by using the following statement:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/DB2e/database/x86
DB2 Everyplace also includes a development database library for Linux devices. The development library generates trace data in addition to the diagnostic data that release libraries generate. This data helps you troubleshoot problems as you develop and test DB2 Everyplace applications. The development library is located in the directories that end in "Dev". For example, the development library for Linux devices with x86 processors are located in %DSYINSTDIR%\Clients\linux\database\x86Dev. To install this library, follow the procedure described in this topic, but copy the file from the appropriate Dev directory.
Installing
DB2 Everyplace files on a Palm OS device
Prerequisites:
- On a Windows workstation, install
and configure the HotSync connection software that came with the Palm OS
device.
- Connect the Palm OS mobile device
to the Windows workstation. Use the mobile device's documentation to
ensure that the mobile device is connected correctly.
Install DB2 Everyplace by
transferring files onto your device using one of the following methods,
depending on whether you are using a mobile device or an emulator.
- Mobile device
- On the workstation, use the
Install Tool of the HotSync connection software that is included with
the Palm OS mobile device to install the files. After you install the
files, perform a HotSync function to complete the installation of the
DB2 Everyplace files to the Palm OS mobile device.
- Emulator
- Drag and drop the files into
the emulator window. After you install all the files, reset the
emulator.
To install DB2 Everyplace files on a Palm OS
device:
- Install the database engine and
supporting files listed in the following table.
These files are in the
%DSYINSTDIR%\Clients
directory.
In the following table,
lang is
a language code, for example, en_US.
Table 6. Palm OS database files
| File name |
Description |
| palmos\database\
CryptoPlugin.prc |
Encryption
library |
| 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\
DB2eDMS.prc |
DB2
Everyplace database engine |
| palmos\database\
DB2eRunTime.prc |
DB2
Everyplace database engine |
| palmos\database\
PBSPkcs11.prc |
Encryption
library. Encryption support is available only on Palm OS 4.1 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. |
|
|
| palmos\database\
lang
\DB2eCLP\DB2eCLP.prc |
DB2
Everyplace command line processor |
|
|
| utilities\
lang
\DB2eImport |
DB2
Everyplace Import tool |
- Optional:
Install the Sync Client files listed in the following table.
These files are required if you
plan to use the DB2 Everyplace sync server. They are in the
%DSYINSTDIR%\Clients\palmos\sync\
directory.
In the following table,
lang is
a language code, for example, en_US.
Table 7. Palm OS sync client files
| File name |
Description |
| 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 |
| isyncstat.prc |
IBM Sync
statistics |
| isyncxpt.prc |
IBM Sync
transport library |
| SSLlib.prc |
IBM Sync
SSL library |
| wbxmllib.prc |
IBM Sync
WBXML library |
| \lang\ db2sync.prc |
DB2 Sync
client GUI |
| \lang\ dsyagent.prc |
IBM Sync
Remote Stored Procedure adapter |
| \lang\ upgrade\ iUpgrade.prc |
IBM Sync
Auto Deploy |
Installing
files on a QNX Neutrino mobile device
Prerequisites:
Installation procedures for QNX
Neutrino mobile devices vary depending on the device. Options include:
- Serial connection between the
device and your workstation using XModem or Kermit protocols.
- Ethernet connection between the
device and your workstation using FTP software.
- Floppy disk, if supported by your
device.
For additional information on
transferring files to your device, see the documentation provided with
that device. You can also consult the QNX Neutrino Software Developer's
Kit (SDK).
- Install the DB2 Everyplace
mobile database files.
DB2 Everyplace database files for
QNX Neutrino mobile devices are located in the
%DSYINSTDIR%\Clients\neutrino\database\
directory.
In the following list,
proc
represents a processor type, for example, strongarm or x86. :
- proc\libcryptoplugin.so
- proc\libdb2e.so
- proc\libdb2ejdbc.so
- proc\libvcpkcs11.so
- jdbc\db2ejdbc.jar
- jdbc\DB2eAppl.class
- DB2eCLP\proc\DB2eCLP
Note:
This
library cannot be used with the J9 JVM.
- Install
the DB2 Everyplace Sync Client files.
The files are located in
%DSYINSTDIR%\clients\neutrino\sync\proc, where
proc
represents a processor type, for example, strongarm or x86.
Copy the following library files
for the appropriate processor into
usr/lib/DB2e/:
- libimsaconfig.so
- libimsadb2e.so
- libimsafile.so
- libisync4j.so
- libisyncconf.so
- libisyncore.so
- libisyncstat.so
- libisyncxpt.so
- libwbxml.so
- isync4j.jar
- lang\db2sync_console
Note:
Only
QNX Neutrino 6.2 and above support Sync client
libraries.
- Set
the environment variable LD_LIBRARY_PATH
to the path where the DB2 Everyplace CLI shared library
(libdb2e.so) is
installed. For example, if the DB2 Everyplace CLI shared library
is stored in
%DSYINSTDIR%/database/x86,
append
%DSYINSTDIR%/database/x86
to your existing LD_LIBRARY_PATH
using the following statement:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/DB2e/database/x86
- Start
the mqueue process to enable encryption.
- To
ensure the mqueue process is running, run the
ps
command. A list of active processes is displayed on the
device.
- Verify
that mqueue is listed. If not, use the
mqueue command to start
the process.
Note:
If
the application terminates unexpectedly after you initialize the
encryption library, the library could be
corrupted.
DB2 Everyplace also includes a development database library for QNX Neutrino devices. The development library generates trace data in addition to the diagnostic data that release libraries generate. This data helps you troubleshoot problems as you develop and test DB2 Everyplace applications. The development library is located in the directories that end in "Dev". For example, the development library for QNX Neutrino devices with x86 processors are located in %DSYINSTDIR%\Clients\neutrino\database\x86Dev. To install this library, follow the procedure described in this topic, but copy the file from the appropriate Dev directory.
Installing
files on a Symbian OS Version 7 device
Prerequisites:
- On a Windows workstation, install
and configure the connection software that came with the Symbian OS
Version 7 mobile device.
- Connect the Symbian OS Version 7
mobile device to the workstation. Use the mobile device's documentation
to ensure that the mobile device is correctly
connected.
To install DB2 Everyplace files on a Symbian OS Version 7
device:
- Use the Install Tool from the
connection software that is included with the Symbian OS Version 7
mobile device to install the DB2 Everyplace mobile database files listed
in the following table. The files are in the
%DSYINSTDIR%\Clients\symbian7\database
directory.
In the following table,
lang is
a language code, for example, en_US.
Table 8. Symbian OS Version 7 database files
| File name |
Description |
| armi\DB2e.sis |
DB2
Everyplace database engine |
| armi\db2ejdbc.sis |
DB2
Everyplace JDBC driver |
| lang\DB2eCLP\UIQ\DB2eCLP.sis |
DB2
Everyplace Command Line Processor |
| lang\install\UIQ\DB2e_Symbian7.sis |
DB2
Everyplace package (all the above in a single
package) |
- Install
the sync client files. The files are in the
%DSYINSTDIR%\Clients\symbian7\sync\lang\proc\ directory, where
lang is
a language code, for example, en_US and
proc is
a processor type, for example, wins or arm.
Table 9. IBM Sync Client files
| File name |
Description |
| DB2Sync.sis |
DB2 Sync
Client |
| upgrade\IUpgrade.app |
IBM Update
Tool |
| upgrade\IUpgrade.rsc |
IBM Update
Tool |
Installing
files on a Windows CE device
Prerequisites:
- On a Windows workstation, install
and configure the Windows CE Services software (also known as
ActiveSync) that came with the Windows CE mobile device.
- Connect the Windows CE mobile
device to the Windows workstation. Use the mobile device's documentation
to ensure that the mobile device is connected correctly.
- Encryption support for Pocket PC
2000 is available only with the Microsoft High Encryption Pack for
Pocket PC V1.0 available fromMicrosoft. High (128-bit) 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. High encryption support comes built-in for Pocket PC 2003
devices.
To install the DB2 Everyplace files on a Windows CE
device:
- Use the Install Tool from the
Windows CE Services connection software (or ActiveSync) that is included
with the Windows CE device to install the files listed in the following
table. These files are in the
%DSYINSTDIR%\Clients\wince\database
directory.
In the following table,
ver is
the Windows CE version, for example, v3 for version 3, or v4 for version
4; and proc is the processor type, for example, ARMRel or
X86Rel.
Table 10. Windows CE database files
| File Name |
Description |
| jdbc\db2ejdbc.jar |
DB2
Everyplace JDBC driver |
| ver\proc\CryptoPlugin.dll |
DB2
Everyplace database engine for data encryption |
| ver\proc\DB2e.dll |
DB2
Everyplace database engine |
| ver\proc\DB2eJDBC.dll |
DB2
Everyplace JDBC driver |
- Use
the Install Tool from the Windows CE Services connection software (or
ActiveSync) that is included with the Windows CE device to install the
files listed in the following table.
- Optional:
If you plan to use the DB2 Everyplace Sync Server, install the files
listed in the following table These files are in the
%DSYINSTDIR%\Clients\wince\sync\lang\ver\proc directory,
where
ver is
the Windows CE version, for example, v3 for version 3, or v4 for version
4;proc
is the processor type, for example, ARMRel or X86Rel; and
lang is
the language code, for example, en_US.
Sync Client XScale libraries are
available only for devices that run Windows CE 4.x. For Windows CE 3.0
(most Pocket PC 2000 and 2002 devices), use Sync Client libraries from
ARM. For the DB2 Everyplace mobile database, XScale libraries are
available for Windows CE 3 and 4.
Table 11. Windows CE Sync Client files
| File Name |
Description |
| db2sync.exe |
IBM Sync
Client GUI |
| 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 |
| isync4j.dll |
IBM Sync
Java interface |
| isync4j.jar |
IBM Sync
Java interface |
| isyncconf.dll |
IBM Sync
engine |
| isyncore.dll |
IBM Sync
engine |
| isyncstat.dll |
IBM Sync
client statistics |
| isyncxpt.dll |
IBM Sync
transport library |
| wbxmllib.dll |
IBM Sync
WBXML library |
| upgrade\iUpgrade.exe |
IBM Sync
Auto Deploy |
As an alternative, you
can install a CAB file for your processor and software version under,
stored in %DSYINSTDIR%\Clients\wince\sync\lang\install that contains the Sync Client
libraries listed above.
- Perform
a sync function to complete the installation of the DB2 Everyplace
libraries and application files to the Windows CE mobile device.
The following table shows where to
obtain Sync Client libraries for various emulators:
Table 12. Sync Client libraries for emulators
| File Name |
Description |
| \Clients\WinCE\sync\lang\v3\X86EMRel |
Pocket PC 2000 emulator |
| \Clients\WinCE\sync\lang\v3\X86Rel |
Pocket PC
2002/2003 emulator |
| \Clients\WinCE\sync\lang\v4\emulatorRel |
WinCE .NET
emulator |
Note:
Sync
client libraries are not supported on the STANDARD SDK emulator that
comes with Embedded Visual C++ 4.0. Use the Pocket PC 2003 emulator
instead.
DB2 Everyplace also includes a
development database library for Windows CE version 3 devices. The
development library generates trace data in addition to the diagnostic
data that release libraries generate. This data helps you troubleshoot
problems as you develop and test DB2 Everyplace applications. The
development library is located in the directories that end in "Dev". For
example, the development library for Windows CE version 3 devices with
x86 processors are located in \Clients\wince\database\wce300\x86Dev. To
install this library, follow the procedure described in this topic, but
copy the file from the appropriate Dev directory.
Installing
files on a Windows client
Prerequisites:
The Microsoft Strong Encryption
download (available from Microsoft) for your operating system must be
installed to use encryption between Windows clients and the DB2
Everyplace Sync Server.
To install DB2 Everyplace files on a Windows
client:
- Copy DB2 Everyplace files from
your Windows server to a folder on your Windows client.
DB2 Everyplace files are in the
%DSYINSTDIR%\Clients\win32\database
directory.
In the following table,
lang
represents a language code, for example, en_US.
Table 13. DB2 Everyplace files
| File name |
Description |
| x86\CryptoPlugin.dll |
DB2
Everyplace database engine for data encryption |
| x86\DB2e.dll |
DB2
Everyplace database engine |
| x86\DB2eJDBC.dll |
DB2
Everyplace JDBC driver |
| x86\DB2eODBC.dll |
DB2
Everyplace ODBC driver |
| jdbc\db2ejdbc.jar |
DB2
Everyplace JDBC driver |
| jdbc\DB2eAppl.class |
Sample Java
application |
| jdbc\DB2eJavaCLP.class |
Command
Line Processor written in Java |
| lang\DB2eCLP\uicode\DB2eCLP.exe |
Command
Line Processor executable |
| x86\ODBCInst.exe |
Registers
the DB2 Everyplace ODBC driver |
- Optional:
If you plan to use the DB2 Everyplace Sync Server, copy the Sync Client
files to the same folder as in the previous step.
The Sync Client files are in the
%DSYINSTDIR%\Clients\win32\sync\lang\ directory, where
lang is
a language code, for example, en_US.
Table 14. Sync Client files
| File Name |
Description |
| db2sync_console.exe |
DB2 Sync
interface |
| dsyagent.dll |
IBM Remote
Stored Procedure adapter |
| imsaconfig.dll |
IBM Sync
Configuration adapter |
| imsadb2e.dll |
IBM Sync
DB2 Everyplace adapter |
| imsafile.dll |
IBM Sync
File adapter |
| isync4j.dll |
IBM Sync
Java interface |
| isync4j.jar |
IBM Sync
Java interface |
| isyncconf.dll |
IBM Sync
engine |
| isyncore.dll |
IBM Sync
engine |
| isyncstat.dll |
IBM Sync
Client statistics |
| isyncxpt.dll |
IBM
Transport library |
| wbxmllib.dll |
IBM Sync
WBXML library |
- Optional:
install your own DB2 Everyplace applications in the same folder as in
the previous step.
DB2 Everyplace also includes a development database library for Windows devices. The development library generates trace data in addition to the diagnostic data that release libraries generate. This data helps you troubleshoot problems as you develop and test DB2 Everyplace applications. The development library is located in the directories that end in "Dev". For example, the development library for Windows devices with x86 processors are located in %DSYINSTDIR%\Clients\win32\database\x86Dev.
After you
install
Adjusting
system parameters for AIX
In order for DB2 Everyplace to
operate with the highest degree of efficiency, system parameters need to
be adjusted. Failure to do so can result in the inability to create a
new connection to the database. The extended shared memory segments
should be enabled.
Note:
Only
32-bit DB2 Universal Database instances are
supported.
Prerequisites
Modify the login profile to include
the following:
export DISPLAY=hostname:0.0
Where
hostname
is the workstation where you want to use the Mobile Devices
Administration Center.
For each DB2 UDB instance running DB2 Everyplace:
- Modify the login profile (most
likely
/home/<username>/.profile),
to include the following:
export EXTSHM=ON
- Exit
the user shell.
- Login
as the user (to make the changes effective) and open a new
shell.
- From
the shell prompt, execute the following command:
db2set DB2ENVLIST=EXTSHM
- Restart
the DB2 Universal Database instance.
Configuring
Configuring
DB2 Everyplace Enterprise Edition
DB2 Everyplace Enterprise Edition
is installed and configured in two separate processes, so you can change
your server setup as needed without reinstalling the files each time.
You can configure and re-configure DB2 Everyplace using either a wizard
or a command line utility. On Linux and UNIX computers, configuring DB2
Everyplace creates a Sync Server instance, also called a DSY
instance.
The topic Troubleshooting
configuration errors provides information about errors
that might arise when you configure DB2 Everyplace.
After you install and configure DB2
Everyplace, you can start the First Steps launchpad, which provides links to sample
applications and other resources that will help you get started using
DB2 Everyplace.
Using
the Configuration wizard
DB2 Everyplace provides a
Configuration wizard to help you set up the DB2 Everyplace Enterprise
Edition Sync Server and control databases.
Prerequisites:
Install DB2 Everyplace files on
the server before you configure DB2 Everyplace.
- (Windows)
- Log in as an
administrator.
- (Linux and UNIX)
- Log in as the root
user.
To use the Configuration wizard:
Choose from the following
configuration options:
- Basic
- Configures DB2 Everyplace
on a single local server.
- Distributed
- Configures the DB2
Everyplace Sync Server control database (Distributed Database) and the
DB2 Everyplace Sync Server (Distributed Server) on two separate servers
(instances on UNIX platforms). The DB2 Everyplace Sync Server can be
administered using the Mobile Devices Administration Center on the
server (instance) configured as a Distributed Server.
- Clustered
- Configures multiple DB2
Everyplace installations (instances) in a clustered environment. You
must install IBM WebSphere Application Server to configure the cluster
of DB2 Everyplace Application servers.
- Remote administration
- Configures the current DB2
Everyplace install (instance) for remote administration of DB2
Everyplace Sync Server configured on a remote server (instance). This
option configures only the DB2 Everyplace Mobile Devices Administration
Center.
DB2
Everyplace Enterprise Edition basic configuration
Prerequisites
Install DB2 Everyplace files
on the server before you configure DB2 Everyplace.
After DB2 Everyplace files
are installed, you can use the Configuration wizard to set up the
runtime environment. A basic configuration configures DB2 Everyplace on
a single local server. When you choose a basic configuration, the
Configuration wizard prompts you for the following data:
- (Windows) DB2 UDB user ID and password
- Provide an existing DB2
UDB user ID and password. This data is required.
- (Linux and UNIX) Sync Server instance name, password, and locale
- Specify a Sync Server
instance name, password, and locale. This data is required. Databases
and samples are created or copied using the specified locale.
- Location for storing messages to and from clients
- DB2 Everyplace can store
messages from client devices in the server's file system or in a DB2 UDB
database. The database option is recommended for most
installations.
- Class path for non-DB2 JDBC drivers
- Enter the full path
(including drive letter) to JDBC drivers from third parties such as
Oracle or Sybase. Use Java CLASSPATH syntax: no spaces, single quotes,
or double quotes are allowed. Use the separator character for your
operating system (semicolon for Windows, colon for Linux and UNIX). This
data is not required. If no such drivers are installed on the server,
you can leave the field blank.
- Configuration information for the DB2 Everyplace Sync Server
- The Configuration wizard
installs and configures an embedded application server used by the DB2
Everyplace Sync Server. Provide the server name, server IP address, HTTP
port number, and SSL port number.
- (Windows) Start the Windows service for the DB2 Everyplace Sync Server
- Specify whether you want
to start the windows service for DB2 Everyplace Sync Server at the end
of the configuration. Starting the Windows service can take a few
minutes.
- (Linux and UNIX) Start the daemon for DB2 Everyplace Sync Server
- Specify whether you want
to start the daemon for DB2 Everyplace Sync Server at the end of the
configuration. Starting the daemon can take a few minutes.
To perform a basic configuration:
- Start the DB2 Everyplace
Configuration wizard.
- Windows
-
Run the
DSYconfig.exe
file, installed by default in the
%DSYINSTDIR%\config\bin
directory.
You can also use a Start
menu shortcut:
Start -> Programs -> IBM DB2 Everyplace
Enterprise -> Setup
Tools -> DB2 Everyplace Configuration Wizard.
- Linux and UNIX
- As the root user, run the
DSYconfig.bin
file, installed by default in the
$DSYPATH/config/bin
directory.
- Linux for iSeries
- As the root user, run
the DSYconfig.sh
file, installed by default in the
$DSYPATH/config/bin
directory.
- Click
Next.
- Choose
Configure (on a Windows computer) or
Create (on a Linux or UNIX computer).
- Choose
Basic
configuration.
- Proceed
by following the wizard's prompts.
DB2 Everyplace is not
configured until you click
Next in the Pre-configuration Summary
panel.
DB2
Everyplace distributed configuration
A distributed configuration
sets up the DB2 Everyplace Enterprise Edition Sync Server control
database and the DB2 Everyplace Sync Server installed on two separate
servers. There are two distributed configuration actions:
- Database configuration
- Sets up the DB2
Everyplace Sync Server control database.
- Server configuration
- Sets up the DB2
Everyplace Mobile Devices Administration Center and the DB2 Everyplace
Sync Server.
When performing a
distributed configuration, you must complete the database configuration
successfully before you begin the server configuration.
DB2
Everyplace distributed database configuration
A distributed database
configuration sets up the DB2 Everyplace Sync Server control
database.
Prerequisites:
Install DB2 Everyplace
files on the servers before you configure DB2 Everyplace.
When you choose a
distributed database configuration, the Configuration wizard prompts you
for the following data:
- (Windows) DB2 UDB user ID and password
- Provide an existing
DB2 UDB user ID and password. This data is required.
- (Linux and UNIX) Sync Server instance name, password, and locale
- Specify a Sync
Server instance name, password, and locale. This data is required.
Databases and samples are created or copied using the specified
locale.
- Location for storing messages to and from clients
- DB2 Everyplace can
store messages from client devices in the server's file system or in a
DB2 UDB database. A database message store is recommended for most
distributed installations. A file system message store is allowed only
for a single-server environment.
To perform a distributed database
configuration:
- Start the DB2
Everyplace Configuration wizard.
- Windows
-
Run the
DSYconfig.exe
file, installed by default in the
%DSYINSTDIR%\config\bin
directory.
You can also use a
Start menu shortcut:
Start -> Programs -> IBM DB2 Everyplace
Enterprise -> Setup
Tools -> DB2 Everyplace Configuration Wizard.
- Linux and UNIX
- As the root user,
run the
DSYconfig.bin
file, installed by default in the
$DSYPATH/config/bin
directory.
- Linux for iSeries
- As the root user,
run the
DSYconfig.sh
file, installed by default in the
$DSYPATH/config/bin
directory.
- Click
Next.
- Choose
Configure (on a Windows computer) or
Create (on a Linux or UNIX computer).
- Choose
Distributed configuration.
- Choose
Database configuration.
- Proceed
by following the wizard's prompts.
DB2 Everyplace is not
configured until you click
Next
in the Pre-configuration Summary panel.
DB2
Everyplace distributed server configuration
Prerequisites:
- Install DB2
Everyplace files on the server before you configure DB2 Everyplace.
- Configure the DB2
Everyplace Sync Server control database before configuring the
distributed server.
- The control database
and the distributed server must use the same locale.
- The DB2 Everyplace
Sync Server instance you configure will use databases on another DB2
Everyplace instance. That other instance must be already installed and
configured.
A distributed server
configuration sets up the DB2 Everyplace Mobile Devices Administration
Center and the DB2 Everyplace Sync Server. When you choose a distributed
server configuration, the Configuration wizard prompts you for the
following data:
- (Linux and UNIX) Sync Server instance name
- Specify the name of
the Sync Server instance to configure.
- (Linux and UNIX) Remote control database locale
- Specify the locale
of the remote UDB instance that holds the DB2 Everyplace control
database.
- Connection parameters for a remote DB2 UDB instance
- Host name, TCP/IP
connection port, user ID, user password.
- Location for storing messages to and from clients
- DB2 Everyplace can
store messages from client devices in the server's file system or in a
DB2 UDB database. The database option is recommended for most
installations.
- Class path for non-DB2 JDBC drivers
- Enter the full path
(including drive letter) to JDBC drivers from third parties such as
Oracle or Sybase. Use Java CLASSPATH syntax: no spaces, single quotes,
or double quotes are allowed. Use the separator character appropriate
for your operating system (semicolon for Windows, colon for Linux). This
data is not required. If no such drivers are installed on the server,
you can leave the field blank.
- Configuration information for the DB2 Everyplace Sync Server
- The Configuration
wizard installs and configures an embedded application server used by
the DB2 Everyplace Sync Server. Provide the server name, server IP
address, HTTP port number, and SSL port number.
- (Windows) Administrator user ID and password
- The Configuration
wizard uses the administrator user ID and password to start the DB2
Everyplace Sync Server as a Windows service.
- (Windows) Start the DB2 Everyplace Sync Server as a service
- Specify whether you
want to start the DB2 Everyplace Sync Server as a service at the end of
configuration. Starting the service can take a few minutes.
- (Linux and UNIX) Start the daemon for DB2 Everyplace Sync Server
- Specify whether
you want to start the daemon for DB2 Everyplace Sync Server at the end
of the configuration. Starting the daemon can take a few minutes.
To perform a distributed server
configuration:
- Start the DB2
Everyplace Configuration wizard.
- Windows
-
Run the
DSYconfig.exe
file, installed by default in the
%DSYINSTDIR%\config\bin
directory.
You can also use a
Start menu shortcut:
Start -> Programs -> IBM DB2 Everyplace
Enterprise -> Setup
Tools -> DB2 Everyplace Configuration Wizard.
- Linux and UNIX
- As the root user,
run the
DSYconfig.bin
file, installed by default in the
$DSYPATH/config/bin
directory.
- Linux for iSeries
- As the root user,
run the
DSYconfig.sh
file, installed by default in the
$DSYPATH/config/bin
directory.
- Click
Next.
- Choose
Configure (on a Windows computer) or
Create (on a Linux or UNIX computer).
- Choose
Distributed configuration.
- Choose
Server configuration.
- Proceed
by following the wizard's prompts.
DB2 Everyplace is not
configured until you click
Next
in the Pre-configuration Summary panel.
Troubleshooting
If the Configuration
wizard or the command line configuration tool fails to catalog the
remote control database in the local database catalog, make sure you
have specified correct values for the following properties:
- Remote host
- Specify the fully
qualified host name.
- TCP/IP connection port
- Use the TCP/IP
connection port specified in the services file for the remote DB2
instance. On Windows, the location is
%SystemRoot%\system32\drivers\etc\services;
on Linux and UNIX, the location is
/etc/services..
- User ID
-
- Password
- Provide a valid
user name to connect to the remote control database
DB2
Everyplace clustered configuration
A clustered configuration configures multiple instances of the DB2 Everyplace Sync Server installed on multiple computers. When you choose a clustered configuration, the Configuration wizard prompts you for the following data:
- Location for the control database and message store
- Specify whether to
create the DB2 Everyplace Sync Server control database and the message
store database on the local server or catalog remote databases in the
local database directory.
- If you choose to create
the databases on the local server, provide the following:
- (Windows) A DB2 UDB user
ID and password.
- (Linux and UNIX) A DB2
UDB instance name, password, and locale.
- If you choose to catalog
remote databases in the local database directory, provide the following:
- (Windows) A remote
database host name, TCP/IP connection port number, user ID, and
password.
- (Linux and UNIX) A remote
database host name, TCP/IP connection port number, user ID, and
password, locale, and instance name.
- Class path for non-DB2 JDBC drivers
- Enter the full path
(including drive letter) to JDBC drivers from third parties such as
Oracle or Sybase. Use Java CLASSPATH syntax: no spaces, single quotes,
or double quotes are allowed. Use the separator character appropriate
for your platform (semicolon for Windows, colon for Linux and UNIX).
This data is not required. If no such drivers are installed on the
server, you can leave the field blank.
To perform a clustered configuration:
- Start the DB2 Everyplace
Configuration wizard.
- Windows
-
Run the
DSYconfig.exe
file, installed by default in the
%DSYINSTDIR%\config\bin
directory.
You can also use a Start
menu shortcut:
Start -> Programs -> IBM DB2 Everyplace
Enterprise -> Setup
Tools -> DB2 Everyplace Configuration Wizard.
- Linux and UNIX
- As the root user, run
the
DSYconfig.bin
file, installed by default in the
$DSYPATH/config/bin
directory.
- Linux for iSeries
- As the root user, run
the
DSYconfig.sh
file, installed by default in the
$DSYPATH/config/bin
directory.
- Click
Next.
- Choose
Configure (on a Windows computer) or
Create (on a Linux or UNIX computer).
- Choose
Clustered configuration.
- Proceed
by following the wizard's prompts. You can stop the wizard by
clicking Cancel. DB2 Everyplace is not configured until you
click Next in the Pre-configuration Summary panel.
DB2
Everyplace remote administration configuration
Prerequisites:
- Install DB2 Everyplace
files on the server before you configure DB2 Everyplace.
- Configure the remote DB2
Everyplace Sync Server before performing remote administration
configuration.
- The local and remote
computers must use the same locale.
- Catalog all source and
mirror databases used by the DB2 Everyplace Sync
Server.
The remote administration
configuration enables you to run the Mobile Devices Administration
Center on a local machine to administer a remote DB2 Everyplace Sync
server. When you choose a remote administration configuration, the
Configuration wizard prompts you for the following data:
- (Linux and UNIX) Sync Server instance name
- Specify the name of the
Sync Server instance to configure.
- (Linux and UNIX) Remote control database locale
- Specify the locale of
the remote UDB instance that holds the DB2 Everyplace control
database.
- Connection parameters for a remote DB2 UDB instance
- Host name, TCP/IP
connection port, user ID, user password.
- Location for storing messages to and from clients
- DB2 Everyplace can
store messages from client devices in the server's file system or in an
existing remote DB2 UDB database.
- Class path for non-DB2 JDBC drivers
- Enter the full path
(including drive letter) to JDBC drivers from third parties such as
Oracle or Sybase. Use Java CLASSPATH syntax: no spaces, single quotes,
or double quotes are allowed. Use the separator character appropriate
for your operating system (semicolon for Windows, colon for Linux). This
data is not required. If no such drivers are installed on the server,
you can leave the field blank.
To perform a remote administration
configuration:
- Start the DB2 Everyplace
Configuration wizard.
- Windows
-
Run the
DSYconfig.exe
file, installed by default in the
%DSYINSTDIR%\config\bin
directory.
You can also use a Start
menu shortcut:
Start -> Programs -> IBM DB2 Everyplace
Enterprise -> Setup
Tools -> DB2 Everyplace Configuration Wizard.
- Linux and UNIX
- As the root user, run
the
DSYconfig.bin
file, installed by default in the
$DSYPATH/config/bin
directory.
- Linux for iSeries
- As the root user, run
the
DSYconfig.sh
file, installed by default in the
$DSYPATH/config/bin
directory.
- Click
Next.
- Choose
Configure (on a Windows computer) or
Create (on a Linux or UNIX computer).
- Choose
Remote
administration.
- Proceed
by following the wizard's prompts.
DB2 Everyplace is not
configured until you click Next in the Pre-configuration Summary
panel.
Troubleshooting
If the Configuration wizard
or the command line configuration tool fails to catalog the remote
control database in the local database catalog, make sure you have
specified correct values for the following properties:
- Remote host
- Specify the fully
qualified host name.
- TCP/IP connection port
- Use the TCP/IP
connection port specified in the services file for the remote DB2
instance. On Windows, the location is
%SystemRoot%\system32\drivers\etc\services;
on Linux and UNIX, the location is
/etc/services..
- User ID
-
- Password
- Provide a valid user
name to connect to the remote control database
Unconfiguring
DB2 Everyplace Enterprise Edition
You must unconfigure DB2
Everyplace before you uninstall it. However, when you re-configure DB2
Everyplace, the configuration tools unconfigure DB2 Everyplace for
you.
Prerequisites:
- Windows
-
- Log in as an
administrator.
- Back up all user
data.
- Linux and UNIX
-
- Log in as the root
user.
- Back up all user data.
Unconfiguring DB2 Everyplace drops all Sync Server instances. Dropping a
DB2 Everyplace Sync Server instance also deletes the
db2everyplace82
directory from the instance user's home directory.
Use the Configuration wizard to unconfigure a DB2 Everyplace installation. The Configuration wizard detects the type of DB2 Everyplace installation (basic, remote, distributed, or clustered), then stops services, uncatalogs databases, and removes features as appropriate. On Linux and UNIX computers, unconfiguring DB2 Everyplace drops Sync Server instances (also called DSY instances) and deletes the db2everyplace82
directory from the user's home directory.
To unconfigure DB2 Everyplace Enterprise
Edition:
- Start the DB2 Everyplace
Configuration wizard.
- Windows
-
Run the
DSYconfig.exe
file, installed by default in the
%DSYINSTDIR%\config\bin
directory.
You can also use a Start
menu shortcut:
Start -> Programs -> IBM DB2 Everyplace
Enterprise -> Setup
Tools -> DB2 Everyplace Configuration Wizard.
- Linux and UNIX
- As the root user, run the
DSYconfig.bin
file, installed by default in the
$DSYPATH/config/bin
directory.
- Linux for iSeries
- As the root user, run the
DSYconfig.sh
file, installed by default in the
$DSYPATH/config/bin
directory.
- Click
Next.
- Choose
Unconfigure (on a Windows computer) or
Drop (on a Linux or UNIX computer).
- Proceed
by following the wizard's prompts.
Now, you can uninstall DB2 Everyplace.
Prerequisites:
- Install WebSphere
Application Server (WAS) Network Deployment on a dedicated server.
- Make sure the WebSphere
installations on each node are at the same level as the deployment
manager, and each node is added to the deployment manager. The WAS
Network Deployment Documentation describes how to setup the node
configuration. Start the deployment manager before configuring the
cluster.
- Install and configure DB2
Everyplace on each node with the cluster configuration option.
- When you configure DB2
Everyplace, select a DB2 UDB database for the message store,
DSYMSGDB.
- Make sure all DB2
Everyplace installations that are part of the clustered configuration
share the DB2 Everyplace Sync Server databases, DSYCTLDB and DSYMSGDB.
The DB2 Everyplace configuration catalogs these databases.
- Catalog the source and
mirror databases that are used for DB2 Everyplace subscriptions on each
of the nodes in the cluster. Catalog these databases with the same
name.
Host the DB2 Everyplace
databases on a dedicated database server. This database server can also
host the source and mirror databases that DB2 Everyplace uses.
If security is enabled in
WAS, provide a WAS security ID user name and password as parameters to
each WebSphere command.
To configure DB2 Everyplace in a clustered
environment:
- Create the first server:
Table 15. Create the first server
| Windows |
Change to the
%DSYINSTDIR%\config\work
directory. |
|
Run
wasdmin.bat.
<WAS_HOME>\bin\wsadmin.bat -f
dsyInstallDB2e.jacl WAS_node_name
WAS_virtual_host
existing_server_name
IP_address
DSYINSTDIR
DSYSQLIBINSTDIR
UDB_version
- WAS_node_name is the existing WebSphere node name
for DB2 Everyplace installation
- WAS_virtual_host is the existing WebSphere virtual
host name
- existing_server_name is the DB2 Everyplace server
name
- IP_address is a valid IP address or host name for
the server
- DSYINSTDIR is the DB2 Everyplace instance
installation directory. Do not use spaces in the directory name. If the
directory name contains a space, use the short name. For example, use
c:\PROGR~1\
instead of
c:\Program
Files\.
- DSYSQLIBINSTDIR is the DB2 UDB installation
directory. Do not use spaces for the directory name. If the directory
name contains a space, use the short name. For example, use
c:\PROGR~1\
instead of
c:\Program
Files\.
- UDB_version is the DB2 UDB version. Use 7 or
8.
|
| Linux and UNIX |
Change to the
$DSYINSTDIR/config/work
directory. |
|
Run
wasdmin.sh.
<WAS_HOME>/bin/wsadmin.sh -f
dsyInstallDB2e.jacl WAS_node_name
WAS_virtual_host
existing_server_name
IP_address
DSYINSTDIR
DSYSQLIBINSTDIR
UDB_version
- WAS_node_name is the existing WebSphere node name
for DB2 Everyplace installation
- WAS_virtual_host is the existing WebSphere virtual
host name
- existing_server_name is the DB2 Everyplace server
name
- IP_address is a valid IP address or host name for
the server
- DSYINSTDIR is the DB2 Everyplace instance
installation directory. Do not use spaces in the directory name. If the
directory name contains a space, use the short name. For example, use
c:\PROGR~1\
instead of
c:\Program
Files\.
- DSYSQLIBINSTDIR is the DB2 UDB installation
directory. Do not use spaces for the directory name. If the directory
name contains a space, use the short name. For example, use
c:\PROGR~1\
instead of
c:\Program
Files\.
- UDB_version is the DB2 UDB version. Use 7 or
8.
|
- Convert
the first server to a cluster:
Table 16. Convert the first server to a cluster
| Windows |
Make
sure the
%DSYINSTDIR%
\config\work\was\ dsySetupEnv.jacl file has the cluster name and
operating system specified correctly. |
|
Run
wasdmin.bat.
<WAS_HOME> \bin\wsadmin.bat -f
dsyCreateCluster.jacl
WAS_node_name
WAS_virtual_host
existing_server_name
IP_address
DSYINSTDIR
DSYSQLIBINSTDIR
UDB_version |
| Linux and UNIX |
Make
sure the
$DSYINSTDIR
/config/work/was/ dsySetupEnv.jacl file has the cluster name and
operating system specified correctly. |
|
Run
wasdmin.sh as
the root user.
<WAS_HOME> /bin/wsadmin.sh -f
dsyCreateCluster.jacl
WAS_node_name
WAS_virtual_host
existing_server_name
IP_address
DSYINSTDIR
DSYSQLIBINSTDIR
UDB_version
DSY_instance_name
DSY_instance_group_name |
- Synchronize
all the nodes in the DB2 Everyplace cluster with the new
configuration:
- If the node agent is
running on the node, synchronize the node from the WebSphere
Administrative Console. Click
System
Administration -> Nodes, select the nodes that you want to
synchronize, and click
Synchronize.
- If the node agent is not
running on the node, you have two options:
- Start the node by using
the startNode
command, and then synchronize the node from the WebSphere Administrative
Console.
Table 17. Start the node by using the startNode command
| Windows |
<WAS_HOME> \bin\
startNode.bat |
| Linux and UNIX (as root user) |
. ~ <userinstance> /.profile
<WAS_HOME> /bin/ startNode.sh |
- Synchronize the node
using the
syncNode
command. However, if you use the
syncNode
command, you must start the node agent later to use the cluster.
Table 18. Synchronize the node using the syncNode command
| Windows |
<WAS_HOME> \syncNode.bat
dmgr_host
dmgr_port |
| Linux and UNIX (as root user) |
<WAS_HOME> /syncNode.sh
dmgr_host
dmgr_port |
- Regenerate
the WebSphere plug-in configuration file.
You may need to copy the
generated file to the directory where the HTTP server is configured to
load the file. Refer to the WAS Network Deployment documentation for
more information.
Table 19. Regenerate the WebSphere plug-in configuration file
| Windows |
<WAS_ND_HOME> \bin\
GenPluginCfg.bat |
| Linux and UNIX (as root user) |
<WAS_ND_HOME> /bin/
GenPluginCfg.sh |
- Start
the DB2 Everyplace cluster.
- Use
a Web browser to log in to the Network Deployment Manager.
- Go
to
Servers -> Clusters -> DB2Everyplace_Cluster.
- Select
the DB2Everyplace_Cluster check box, then click
Start.
- Test
DB2 Everyplace in the clustered environment:
- On
the database server node, open a DB2 command window and change to the
SAMPLE
directory.
Table 20. Change to the SAMPLE directory
| Windows |
Change to the
%DSYINSTDIR%
\Server\sample\ directory. |
| Linux and UNIX |
Change to the
$DSYINSTDIR
/Server/sample/
directory. |
- Create
a sample database.
db2 -vtf Vnurse.ddl
- Catalog
the sample databases on each node in the cluster running DB2 Everyplace.
The sample databases must
be cataloged with the same name on each node.
For the VNurse sample,
catalog the databases VNURSE and M_VN2.
Refer to the DB2
documentation for information on how to catalog the remote
databases.
- On
one of the server nodes in the cluster, change to the
CONFIG
directory.
Table 21. Change to the CONFIG directory
| Windows |
%DSYINSTDIR% \config\ |
| Linux and UNIX |
$DSYPATH
/config/ |
- Run
the
create-sample
command.
Table 22. Run the create-sample command
| Windows |
dsyconfig.bat create-sample |
|
Linux and UNIX
(as the DB2 Everyplace instance) |
./dsyconfig.sh
create-sample |
- On
a test client device, install the DB2 Everyplace client, configure the
device to point to the DB2 everyplace cluster HTTP server, and
synchronize.
Configuring
mobile devices
Topics in this section
provide information that will help you configure
DB2
Everyplace on
mobile devices.
Secure Sockets Layer (SSL) provides added security when synchronizing by encrypting data. To use SSL, you must install a certificate on the client device so that it can verify that it is in communication with the appropriate server. The certificate must be obtained from the public SSL certificate of the HTTP server with which the clients will synchronize data. Refer to the documentation for the server that is providing the SSL service for information about how to obtain and export the certificate in a format that the client can install and use. If you are using the IBM HTTP Server that is installed with the WebSphere Application Server, use the ikeyman tool in the <IHS>\bin directory to export the SSL certificate. If you are using the embedded version of the WebSphere Application server, ikeyman is in the <DSYINSTDIR>\WAS\bin directory. Be sure to export the public certificate.
Windows CE and Symbian devices do not need manual installation of certificates. When synchronizing with these client devices, you only need to specify the address of the SSL server. For example, https://www.syncsample:9558/
To configure SSL for DB2 Everyplace client
devices:
Prerequisites:
Linux device clients
require the OpenSSL libraries. Download these libraries from
http://www.openssl.org and install the libraries before configuring SSL
on Linux client devices.
To configure SSL for Linux client devices:
- Obtain the certificate
file that you want to install on the DB2 Everyplace Sync Client. Use
base-64 encoded X.509
format. Tip: You can obtain the certificate by using a web
browser and then export it to the needed format. The web site will send
it to the client on the first connection.
- Copy
this file to
/usr/share/ss/certs
as the root user.
- Find
out the hash value of the certificate by entering the following
command:
openssl x509 -noout -hash -in
ca_certificate file
where
ca_certificate file is the name of the base-64
encoded X.509 certificate file.
- Create
a symbolic link to the certificate file. The name of the link must be
the hash value appended with a ".0". For example:
ln -s
ca_certificate file
9c975d97.0
where
ca_certificate file is the name of the certificate
file and 9c975d97 is the hash value obtained from the
previous step.
- Verify
the installation of the certificate by entering the following
command:
openssl verify -CApath /usr/share/ssl/certs
/usr/share/ssl/certs/ca_certificate_file
You will see a message
similar to the following if the installation succeeded:
/usr/share/ssl/certs/ca_certificate_file: OK
If you receive an error
message, go to http://www.openssl.org/docs/apps/verify.html to look up
the error message.
Prerequisites:
Download the certificate
conversion utility, palmdb.exe, from
http://www.ibm.com/support/.
To configure SSL for Palm OS client devices:
- Start IBM Key Management
(ikeyman), which is included with the IBM HTTP server.
- Open
a key database file that includes an appropriate certificate.
- Select
a certificate to extract.
For a self-signed
certificate:
- Select
Personal Certificates from the drop-down list
- Select an appropriate
self-signed certificate from the list of personal certificates.
- Click
Extract Certificate.
For a real certificate that
is obtained from CA:
- Select
Signer Certificates from the drop-down list.
- Select an appropriate
certificate from the list of signer certificates.
- Click extract at the
upper right.
- Select
Binary DER data as the Data type.
- Enter
cacerts.bin as
the certificate file name and save it.
- Put
the palmdb.exe
file in the same directory as cacerts.bin.
- Enter
palmdb.exe at the command prompt with no
arguments. Make sure a file named
SSLCaCerts.pdb
was created in the same directory as
palmdb.exe and
cacerts.bin
after running the command.
- Install
SSLCaCerts.pdb
on the Palm OS client device using the Palm Desktop
- Check
SSL enable on the Palm OS client device.
To configure SSL for Windows client devices:
- Connect to the SSL
server using a web browser using the following address:
https://server:port/db2e/db2erdb/.
Note:
If
a window displays telling you that you are viewing pages over a secure
connection, click
OK. The Security Alert window opens.
- Click
View Certificate. The Certificate window
opens
- Click
on Install Certificate. The Certificate Import Wizard
opens.
- Click
Next.
- Select
Automatically select the certificate store based on the
type of certificate and click
Next.
- Click
Finish. The Security Warning window opens.
- Click
Yes. The Certificate Import Wizard window opens
confirming a successful import.
- Click
OK. The Certificate window opens.
- Click
OK. The Security Alert window opens.
- Click
Yes to connect to the SSL server. You should see
the DB2 Everyplace Sync Server message:
DB2e SyncServer (date and time).
Configuring
the DB2 Everyplace ODBC driver
Prerequisites:
- The DB2 Everyplace ODBC driver
is supported only on Windows 32-bit operating systems.
- ODBC Manager is required. These
Windows system files are not packaged with DB2 Everyplace. You can
download the Microsoft Data Access Components from the Microsoft
Universal Data Access Web site. If ODBC Manager is missing, ODBCInst.exe
returns the following error message
The
ODBC installer DLL is not installed on this
system.
Open Database Connectivity (ODBC)
is an application programming interface for developing programs that are
database independent or that access multiple data sources
simultaneously. To reduce DB2 Everyplace's footprint, DB2 Everyplace
ODBC driver and setup functions are provided in a separate file,
DB2eODBC.dll.
The DB2 Everyplace ODBC driver
supports the same functions as the DB2 Everyplace CLI interface, and
faces the same limitations. It might not meet the requirements of most
ODBC GUI tools. One good use of this driver is to write
database-independent code without compiling or linking with DB2
Everyplace files. You can also access multiple data sources from
different vendors simultaneously.
When you install DB2 Everyplace,
the following files are copied to the same directory as DB2e.dll
(default location:
C:\Program
Files\IBM\DB2Everyplace\Clients\win32\database\x86).
- DB2eODBC.dll : DB2 Everyplace
ODBC driver and setup utility.
- ODBCInst.exe : Program for
registering the ODBC driver.
To configure the DB2 Everyplace ODBC
driver:
- Register the DB2 Everyplace
ODBC driver with the desktop ODBC manager. From command line,
enter odbcinst.exe -i
- Add
a user data source.
- Start
the "ODBC Data Sources" program from the Control Panel
Choose
Start -> Settings -> Control
Panel -> Administrative
Tools -> Data Sources (ODBC)
- Click
Add in
the User DSN panel.
- Choose
IBM DB2
Everyplace ODBC Driver from the list of drivers in the Create New
Data Source window.
- Click
Finish.
- Enter
the following in the IBM DB2 Everyplace ODBC Driver configuration panel:
- Data Source Name: ODBC data source name.
- Description: A description of the data source.
- DB2 Everyplace Database Directory: DB2 Everyplace data
source name. Example: C:\data\employee\
After you configure the DB2
Everyplace ODBC driver, you can use it to execute the functions provided
in the DB2 Everyplace CLI interface, plus the following additional C/C++
function.
SQLGetFunctions()
This function reports whether a
specific function is supported, allowing applications to adapt to
varying levels of support when connecting to different database
servers.
Syntax
SQLRETURN SQLGetFunctions(
SQLHDBC ConnectionHandle,
SQLUSMALLINT FunctionId,
SQLUSMALLINT * SupportedPtr);
Arguments
ConnectionHandle
[Input]
Connection handle.
FunctionId
[Input]
A #define
value that identifies the ODBC function of interest:
- SQL_API_ODBC3_ALL_FUNCTIONS is
used by an ODBC 3.x application to determine support of ODBC 3.x and
earlier functions.
- SQL_API_ALL_FUNCTIONS is used by
an ODBC 2.x application to determine support of ODBC 2.x and earlier
functions.
SupportedPtr
[Output]
SupportedPtr can point to a single value or an array of values, depending on the value of FunctionId, as shown in the following table. Arrays returned in SupportedPtr use zero-based indexing
| FunctionId |
SupportedPtr |
| identifies
a single ODBC function |
Points to a
single SQLUSMALLINT value. The value is SQL_TRUE if the specified
function is supported by the driver; otherwise, the value is
SQL_FALSE. |
| SQL_API_ODBC3_ALL_FUNCTIONS |
Points to a
SQLSMALLINT array with a number of elements equal to
SQL_API_ODBC3_ALL_FUNCTIONS_SIZE. The Driver Manager treats this array
as a 4,000-bit bitmap that can be used to determine whether an ODBC 3.x
or earlier function is supported. |
| SQL_API_ALL_FUNCTIONS |
Points to
an SQLUSMALLINT array of 100 elements. The array is indexed by
#define values used
by FunctionId to identify each ODBC function; some elements of the array
are unused and reserved for future use.
An array element's value is
SQL_TRUE if it identifies an ODBC 2.x or earlier function supported by
the driver. It is SQL_FALSE if it does not identify an ODBC function, or
if it identifies an ODBC function that the driver does not support. |
Starting
the First Steps launchpad
The First Steps launchpad provides
links to sample applications and other resources that will help you get
started using DB2 Everyplace.
Prerequisites:
Install and configure DB2
Everyplace.
To start the First Steps launchpad:
Run the First Steps
command.
- (Windows)
- There are two ways to run the
First Steps command:
- Use the Start menu shortcut,
replacing [EditionName] with the name of your DB2 Everyplace edition
(for example, Express):
Start -> Programs -> IBM DB2 Everyplace
[EditionName] -> Setup
Tools -> First Steps
- Run the
dsyfs file in the
%DSYINSTDIR%\Server\bin
directory.
- (Linux and UNIX)
- As the Sync Server instance
user, run the
dsyfs.sh file in the
$DSYPATH/Server/bin
directory.
The First Steps launchpad provides buttons linked to resources that will help you get started with DB2 Everyplace. The number of buttons and associated resources varies depending on your operating system and DB2 Everyplace configuration.
Troubleshooting
Troubleshooting
configuration errors
This topic provides information that will help you troubleshoot errors that may arise while using the Configuration wizard or the command line configuration tool.
Stop the Sync Server
If you receive an error message
due to an incorrect or invalid value for a property in the Configuration
wizard or the
dsyconfig.properties
file, stop the servlet or process for the DB2 Everyplace Sync Server
(the default name is IBMDB2eServer) before you run the Configuration
wizard or command line configuration tool again.
To stop the Sync Server, open a
command window and issue the following command:
- Windows
- %DSYINSTDIR%\server\bin\dsysyncstop
You can also use a Start menu
shortcut:
- Enterprise Edition
- Start -> Programs -> IBM DB2 Everyplace
Enterprise -> Admin
tools -> Stop Servlet for Sync Server
- Express Edition
- Start -> Programs -> IBM DB2 Everyplace
Express -> Admin
tools -> Stop Servlet for Sync Server
.
- Linux
-
- Log in to the desired Sync
Server instance (also called a DSY instance).
- Run the
$DSYINSTDIR\server\bin\dsysyncstop
command.
Unconfiguration of embedded Application Server - Express fails
When a Windows service is
stopped, files that are locked by that service are not always released
immediately. As a result, the DB2 Everyplace configuration tools might
be unable to delete certain files and directories, and the
unconfiguration process will fail. If this happens, start the
unconfiguration process again.
Testing
the Sync Server servlet
To ensure that the Sync Server can successfully
communicate with clients, make sure that the servlet is running. You do
not need to have any clients installed in order to perform a
check.
- To test the servlet on Windows:
- Start
the DB2 Everyplace Sync Server.
- In
a Web browser, go to http://yourhostname.yourdomain:8080/db2e/db2erdb.
8080 is the default HTTP port number. Substitute port 8080 with the
correct port number of the DB2 Everyplace Sync Server which is listed in
the Post-install summary panel which is displayed at the end of the DB2
Everyplace installation.
- To test the servlet on Linux:
- Login
as the DB2 Everyplace Sync Server instance owner
- Open
a shell window and change the directory to
$DSYINSTDIR/Server/bin
- Run
dsysync.sh.
- In a Web browser, go to
http://yourhostname.yourdomain:8080/db2e/db2erdb. 8080 is the default
HTTP port number. Substitute port 8080 with the correct port number of
the DB2 Everyplace Sync Server which is listed in the Post-install
summary panel which is displayed at the end of the DB2 Everyplace
installation.
- If
the servlet is running correctly, it will display the following message: DB2e
SyncServer <datetime string>
- For
the Application Server - Express that ships with DB2 Everyplace, the
server log files located in
$DSYINSTDIR/Server/logs/servername might contain a message saying that
the port is already taken by another program. If you receive this
message, change the port number. The default value during
installation for the server name is IBMDB2eServer. The default value
during installation for the server IP address is 127.0.0.1.
- Optional:
To change the port number:
- Windows:
cd
[DSYINSTDIR]\Server\installableApps\common
[DSYINSTDIR]\WAS\bin\stopServer.bat IBMDB2eServer
[DSYINSTDIR]\WAS\bin\wsadmin.bat -conntype NONE -f
dsyConfigEmbedded.jacl DefaultNode default_host DB2eServer 127.0.0.1
[DSYINSTDIR] [new http port] [new https port]
- Linux or UNIX:
cd
[DSYINSTDIR]/Server/installableApps/common
[DSYINSTDIR]/WAS/bin/stopServer.sh IBMDB2eServer
[DSYINSTDIR]/WAS/bin/wsadmin.sh -conntype NONE -f dsyConfigEmbedded.jacl
DefaultNode default_host DB2eServer 127.0.0.1 [DSYINSTDIR] [new http
port] [new https port]
Tracing
and diagnostics
DB2 Everyplace provides basic error logging facilities
for devices that use Linux, QNX Neutrino, or
Windows 32-bit operating systems.
DB2
Everyplace
also provides development libraries that you can install on these
devices to generate trace data. This data can help you troubleshoot
problems as you develop and test
DB2
Everyplace
applications.
Tracing
To enable tracing, install
development libraries on the mobile device. These libraries are in
directories that end in "Dev". For example, the development libraries
for Linux
devices with x86 processors are located in
\Clients\linux\database\x86Dev.
When you use the
development libraries to run an application,
DB2
Everyplace
writes data to a trace file in the database directory, using a file name
listed in the following table. If a trace file exists in the database
directory, CLI trace information is appended to that file.
Table 23. Tracing and diagnostics file names
|
Long file name |
Short file name (8.3 format) |
| Trace file |
DSY_DB2eTRACE |
_trc.DBs |
| Log file |
db2ediag.log |
_diag.DBs |
| Dump files |
DB2e_cxxxxx * |
_cxxxxx.DBs
* |
* xxxxx is the process identifier (PID) number of the
affected process.
Diagnostic data
DB2 Everyplace generates diagnostic data for applications
running either release or development libraries. When an application
encounters a severe system error (SQLState 58005),
DB2
Everyplace
logs the error in a log file and captures the system state in a dump
file. The previous table lists the file names for log files and dump
files. All files are located in the same directory as the database.
Data in the following log
files can also help you diagnose problems:
- %DSYINSTDIR%\Server\logs\IBMDB2eServer\syncadapterinit.log
- %DSYINSTDIR%\Server\logs\IBMDB2eServer\dsynnnn.trace
- %DSYINSTDIR%\Server\logs\dsyadminnnnn.trace
The data integrity check
tool reports whether tables and indexes are corrupted. To run this tool,
execute the
DBCHECK
command in the sample CLP application. The command syntax
is:
DBCHECK outputfile
The
outputfile parameter specifies a text file in the
database directory where the tool will write the
results.
Note:
This
tool is supported on Linux and
Windows 32-bit operating systems only.
DB2 Everyplace Update Tool error messages
The table below lists all of the error messages
that can be generated by the DB2 Everyplace Update Tool. Table 24 displays the error message and a possible remedy for the problem.
Table 24. 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. |
Removing
DB2 Everyplace Enterprise Edition
Use the Uninstall wizard to
remove DB2 Everyplace Enterprise Edition from a server.
Prerequisites:
- Windows
-
- Log in as an
administrator.
- Back up all user data.
- Unconfigure DB2 Everyplace
before you remove it. You can unconfigure DB2 Everyplace by using the
Configuration wizard or the command
line configuration tool.
- (If using the embedded DB2
UDB) Drop all DB2 Everyplace databases.
- Linux and UNIX
-
- Log in as the root user.
- Back up all user data.
- Drop all DB2 Everyplace Sync
Server instances. Dropping a DB2 Everyplace Sync Server instance
unconfigures the instance and deletes the
db2everyplace82
directory from the instance user's home directory.
- (If using the embedded DB2
UDB) Drop all DB2 UDB instances
- (If using the embedded DB2
UDB) Drop the DB2 DAS instance.
To remove DB2 Everyplace Enterprise Edition:
- Start the DB2 Everyplace
Uninstall wizard
- Windows
- You have two choices:
- Run the
DB2EveryplaceUninstall.exe
file, installed by default in the
%DSYINSTDIR%\Uninstaller
directory.
- Use the Windows Add/Remove
Programs control panel.
- Linux and UNIX
- As root user, run the
DB2EveryplaceUninstall.bin
file, installed by default in the
$DSYPATH/Uninstaller
directory.
- Linux for iSeries
- Execute the command
java -jar $DSYPATH/Uninstaller/uninstall.jar as
the root user. Use IBM JDK 1.3.1 or later to start the Uninstall Wizard.
- Proceed
by following the wizard's prompts.
- When
you click Finish, the DB2 Everyplace files are deleted from the
server.
If an embedded version of DB2
Universal Database was installed by the DB2 Everyplace Installation
Wizard, it will be removed by the Uninstall Wizard.