These Release Notes provides information about DB2 Everyplace Version 8.1.1.
It contains updates that have not been added to the DB2 Everyplace Version 8.1 documentation. The DB2 Everyplace Version 8.1 documentation is included on the DB2 Everyplace Version 8.1.1 CD-ROM or with the evaluation code that you downloaded from the DB2 Everyplace Web site.
This section explains the hardware, software, and operating system requirements for DB2 Everyplace.
To use DB2 Everyplace, your system must meet the following hardware requirements:
To use DB2 Everyplace Sync Server, you must have the following software installed:
DB2 Everyplace runs on the following operating systems:
It is strongly recommended that all synchronization sessions are completed before upgrading an existing DB2 Everyplace installation to DB2 Everyplace Version 8.1.1 A device with an unfinished synchronization risks loosing some or all of the data it has collected since the last synchronization.
The following steps are intended to preserve data from synchronization sessions which have not completed prior to the upgrade of DB2 Everyplace to Version 8.1.1, and to let the synchronization session complete after the upgrade. We still strongly recommend that you do not rely on these steps but rather take all necessary precautions to complete all synchronization sessions prior to the upgrade installation.
To preserve the data of uncompleted synchronization sessions:
To install DB2 Everyplace on a Windows or UNIX server:
If you installing from a CD-ROM:
<platform>/jre/bin/java -jar DB2Everyplace.jarwhere <platform> is either AIX, Linux, or Solaris.
If you are installing from the DB2 Everyplace Web site:
The next series of windows in the DB2 Everyplace Installer provides information about the Release Notes and License Agreement.
For Windows, if DB2 Universal Database is not currently installed on your workstation, an embedded copy with limited functionality will be installed. A new window opens:
The features are assigned by default in a single server environment. Verify that the features that you want to install appear in the install preview window and click Next.
Select the check box next to the features on the features window that you want to install. Click Next. By default, all the features are checked.
Verify that all the features that you want installed appear on the install preview window. To make changes to the features that are displayed in the install preview window, click Back to return to the features window.
The installation begins. The files for the selected setup type and features will be copied into the destination directory that was specified previously. The installation progress bar charts the progress of the installation.
Once the installation is complete, proceed through the next series of windows which are described in step 6.
For Windows, follow the steps in this section for each installation type.
Single Server
Multiple Server
Custom
For UNIX, the steps described in this section apply to all three installation types with one exception. In a multiple server installation, you do not need to specify a port number.
If you did not create a DB2 Everyplace instance during installation or you would like to create additional instances outside of the installation process, use the dsyicreate command. Note: A DB2 Everyplace instance must be a DB2 Universal Database instance as well. Therefore, only userids which are DB2 Instance owners can host a DB2 Everyplace instance.
To create a DB2 Everyplace instance, use the dsyicreate.sh command located in the instance directory of the root installation directory (/opt/DB2Everyplace81 on Linux, and /usr/lpp/DBEveryplace81 on AIX and Solaris). Execute the dsyicreate.sh command as root user.
./dsyicreate.sh userid password locale port where userid is the userid of the DB2 instance,
password is the DB2 instance password, locale is the UNIX locale name (see your UNIX installation manuals), and
port is the port under
which the Sync Server of this instance will run../dsyicreate.sh userid password locale boolean_flagwhere userid is the userid of the DB2 instance, password is the DB2 instance password, and boolean_flag takes the following values:
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 segmentation errors on Solaris, and the inability to create a new connection to the database on Linux and AIX.
For Linux and Solaris, we recommend that the kernel parameters are adjusted. For AIX, the extended shared memeory segments should be enabled. This section provides the instructions for Linux, AIX, and SOlaris. Note: Only 32 bit DB2 Universal Database instances are supported.
For Linux systems running kernel 2.4 or higher, issue the following commands on the command line as the root user:
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 recomendations can be found in the Linux 7.2 Release Notes for the FixPak you are running.
For each DB2 Universal Database instance running DB2 Everyplace, modifiy the login profile (most likely /home/<username>/.bashrc) to include the following if you are experiencing problems with java freezing early in the execution of java processes:
export LD_ASSUME_KERNEL_PATH=2.2.5
Exit the user shell, and login as the user to make the changes effective.
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 recommended kernel settings are listed in the DB2 Universal Database Version 7.2, FixPak 7 Release Notes. You can find these Release Notes @ http://www-3.ibm.com/software/data/db2/udb/ad/db2irfp7/db2ir50.htm.
The format for setting these values is
set parameter_name = value
The suggested parameters in the DB2 Universal Database Version 7.2, FixPak 7 Release Notes should be further adjusted to include the following minimum values:
For each DB2 instance running DB2 Everyplace:
export EXTSHM=ON
db2set DB2ENVLIST=EXTSHM
This section begins with a list of features which is followed by recent fixes for the DB2 Everyplace Database.
Application Development
More JDBC support such as scrollable result sets, SQLGetStmtAttr/SQLSetStmtAttr, SQLPrimaryKeys/SQLForeignKeys, JDBC native encoding and miscellaneous DatabaseMetaData methods.
For Win32, adding support of Scrollable cursors and updating the VB sample. For Win32, adding ODBC driver so that applications can be developed through ODBC manager.
New commands have been added to CLP including "Blastdb" command which removes all user tables from DB2 Everyplace, and "CONNECT TO" command.
JSP tools for using database-driven JSP pages built with WebSphere Studio Java Beans. WebSphere Studio JSP pages are parsed by a small tool that then enables browsing the pages on a mobile device with data supplied from DB2 Everyplace.
Performance
Improve index maintenance time for delete and update statements.
Enable table reorganization without dropping all indexes and locking the table, and better reuse of wasted space.
Improves the SQL parser and improves catalog accesses during SQL parsing.
Enhances LIKE predicate to exploit indexes better
Security and new features
Guards DB2 Everyplace data in case a device is lost or stolen.
DB2 Everyplace will support serialized access to a database connection. One process or thread will connect to DB2 Everyplace; other connections will be held in a queue.
DB2 Everyplace database on WinCE/PocketPC can optionally be stored using the native Object Storage instead of using normal the file system.
This list of fixes include an APAR number (where applicable) which is provided for your convenience.
Problems fixed since DB2 Everyplace Version 8.1 and Version 7.2.1.
Data corruption problem
A data corruption problem may occur when the application executes a prepared SELECT statement which does not create a temporary table (using one statement handle) and the tables referenced in the SELECT statement have been modified via a different statement handle. This is exemplified by the following pseudo-code:
step 1: SQLPrepare(handle1, "SELECT
* FROM T" ..)
step 2: SQLExecute(handle1)
step 3: SQLFetch(handle1)
step 4: SQLExecDirect(handle2, "INSERT
INTO T VALUES (10)" ..)
step 5: SQLExecute(handle1)
In step 1, the application prepares a simple
SELECT statement against table T. In step
2, the application executes the prepared
statement using statement handle "handle1".
In step 3, the application fetches a row.
In step 4, the application inserts a row
into the SAME table via a different statement
handle.
In step 5, the application re-executes
the
prepared statement using "handle1".
In this situation, unfortunately, the table T becomes corrupted. This data corruption problem has been fixed in this release.
This section begins with a description of the new Version 8.1 features which is followed by a section for important fixes.
A customizable mechanism which enables you to map non-standard data types of DB2 Universal database which include Informix, Oracle, SQL Server to the data types available on DB2 Everyplace database.
Java application developers can now use the Sync Client Java API(isync4j package) to perform data synchronization. There are two native synchronization providers available. One synchronization provider uses JNI to invoke the native Sync Client libraries to perform the synchronization. The other provider is used for J9 VM for PalmOS only. See the DB2 Everyplace Application Development Guide and the isync4j Javadoc for additional information. Note: We have updated the ConflictReader interface in the listener, so that the column information and data can be accessed easily. Please refer to the isync4j Javadoc for the update.
The sync client application (C or Java) can now specify the target directory with the new Sync Client API. This feature is supported for all platforms except PalmOS (for which it will be available in the upcoming fixpack release).
The IBM Sync Client API has changed, which will provide better clarity, more flexibility, new functionality. The IBM Sync Client API v.7.2.1 is still supported with an API wrapper, but new features are only accessible using the new API.
With the DB2 Everyplace Update Tool, you can upgrade DB2 Everyplace software on the mobile devices (DB2 Everyplace engine, Sync Client and Libraries) without user intervention and then perform synchronization using the updated software.
The Sync Server now assigns the device ID to those device types which do not have a hardware device ID. The assigned device ID will appear in the 'About IBM Sync' panel after the first time the Sync Client synchronizes successfully.
This feature adds support for controlling data encryption of device tables from the Mobile Device Adminstration Center.
Adds the ability on the Sync Client to specify a server for each subscription. Allows the customer to use multiple servers at multiple locations for multiple subscriptions. Note: The same data cannot be synchronized with different servers.
Creates a new J2ME MIDP Sync client to support building applications for J2ME MIDP that can sync subscriptions to the MIDP filesystem for use by the application. Exploits the J2ME MIDP record management system instead of DB2 Everyplace (which cannot run on J2ME MIDP).
Operational features
Enables the Mobile Device Administration Center to run remotely from the server or servers that it is supporting. This supports multipule server configurations by allowing the administration of all server to be done from a separate physical machine and location.
Dynamic control of some server configuration variables, detailed real-time status, and server availability without restarting the Sync Server. This supports High Availability and Load Balancing configurations and increases Administrator control over the Sync Server without requiring timely restarts. Additional details such as USERID will also be added to the logging. Note: This will not allow all configurations and settings to be changed online, only some.
Installing Sync Server Version 8.1 will automatically migrate earlier version configurations to Version 8.1. Migration includes Control tables. In addition,the envaluation version will now support being enabled to a Full Licensed Install without reinstallation.
Adds an XML based scripting tool for managing Sync Server objects and configurations automatically using command line tools and scripts. Also enables easy duplication of one server configuration to several other servers.
If the data on the device is lost or corrupted, a mobile user can automatically request a complete refresh without administrator intervention. Includes an API interface. The feature is also available through the Sync Client API.
Enables safe updating of subscriptions, etc. by quiescing processing of messages related to that item before doing an online update. See Online Server Status and Control.
Exploiting WebSphere Application Server Server Groups, you can enable a server to dynamically manage user load across servers and support failover to another server if the an active server goes down.
Performance features
The Sync Server and the Sync Client will not exchange messages regarding those subscription sets unless it is necessary (for example, new data changes on the server and/or clients, and conflicts). This feature will reduce the turnaround time of synchronization.
Reduces the amount of data sent during initial configuration and config changes by only communicating the differences, not complete configurations.
Reliability Line items
HTTP 1.1 Persistent connection renders better communication efficiency, especially in the wireless environment
This list of fixes include an APAR number (where applicable) which is provided for your convenience.
Problems fixed since DB2 Everyplace 8.1:
The DB2 Everyplace Installation and User's Guide is available in HTML
and PDF format in the following languages:
o Czech
o English
o German
o Korean
o Simplified Chinese
o Traditional Chinese
o Spanish
o Japanese
o Arabic
The DB2 Everyplace Application Development Guide is available in HTML
and PDF format in the following languages:
o English
o Korean
o Simplified Chinese
o Spanish
o Japanese
The DB2 Everyplace Sync Server Administration Guide is available in
HTML and PDF format in the following languages:
o English
o German
o Japanese
o Korean
o Simplified Chinese
The online help within the Mobile Devices Administration Center (MDAC) is available in the national language that you select during installation. English is provided with Arabic, Hebrew, and Czech versions.
This information may contain sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows:
(C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. _enter the year or years_. All rights reserved.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A.For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, JapanThe following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Canada Limited
Office of the Lab Director 1150 Eglinton Ave. East North York, Ontario M3C 1H7 CANADASuch information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
This information may contain examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
The following terms, which may be denoted by an asterisk(*), are trademarks of International Business Machines Corporation in the United States, other countries, or both.
ACF/VTAM IBM AISPO IMS AIX IMS/ESA AIX/6000 LAN DistanceMVS AIXwindows MVS/ESA AnyNet MVS/XA APPN Net.Data AS/400 OS/2 BookManager OS/390 CICS OS/400 C Set++ PowerPC C/370 QBIC DATABASE 2 QMF DataHub RACF DataJoiner DataPropagator RISC System/6000 DataRefresher RS/6000 DB2 S/370 DB2 Connect SP DB2 Extenders SQL/DS DB2 OLAP Server SQL/400 DB2 Universal Database System/370 Distributed Relational System/390 Database Architecture SystemView DRDA VisualAge eNetwork VM/ESA Extended Services VSE/ESA FFST VTAM First Failure Support Technology WebExplorer WIN-OS/2The following terms are trademarks or registered trademarks of other companies:
Microsoft, Windows, and Windows NT are trademarks or registered trademarks of Microsoft Corporation.
Java or all Java-based trademarks and logos, are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Tivoli and NetView are trademarks of Tivoli Systems Inc. in the United States, other countries, or both.
UNIX is a registered trademark in the United States, other countries or both and is licensed exclusively through X/Open Company Limited.
Other company, product, or service names, which may be denoted by a double asterisk(**) may be trademarks or service marks of others.