Everyplace® Client for Windows Mobile™ 2003

This is the Everyplace Client v5.0.1.1 for Windows Mobile 2003 devices that have passed the Resource Checker. (For more information about the Resource Checker, please refer to the Resource Checker Readme)

  • In order for the Device Manager Server (DMS) to properly support Windows Mobile 2003 Second Edition devices, a manual update to the Server is required and a refresh of the Device Agent for the Everyplace Client for Windows Mobile 2003 is required (instructions below).
  • The updated Everyplace Client for Windows Mobile 2003 is now at version 5.0.1.1.  Note that this version of the Windows Mobile 2003 Everyplace Client is only needed for customers who have deployed both Windows Mobile 2003 and Windows      Mobile 2003 Second Edition devices using DMS.  Customers using only Windows Mobile 2003 devices do not need this update. Furthermore, this version can only be deployed via DMS.  Installation via ActiveSync is NOT supported in this version.
  • Finally, the Everyplace Client for Pocket PC 2002 remains at version 5.0.1.

 

APARs included in this release

PQ96485    Device generates assert exceptions and hangs if calendar has an overlapping reoccurring entry

PQ97426    Cancel sync returns improper response and leads to client crash

PQ99199    SyncML client does not parse session ID URI correctly

PK00190    Device agent does not check registry key correctly

PK01507   Unique code for transportation industry customer

 

                                                                      

Server prerequisites

You can use the Device Management portlets to deploy the Windows Mobile 2003, Second Edition .zip files to your Windows Mobile 2003, Second Edition devices.

 

Before you complete the steps in this section, install WebSphere® Everyplace Access 5.0 Fixpack 1, IF1, and IF4.

 

Complete the following steps on the Everyplace Access Services server to complete the prerequisites for this release.

 

1.      Create a backup copy of the platforms.xml file located in the  \Program Files\WebSphere\EAS\config\ templates\wps\ent.portlets\dms\ directory.

2.      Open the platforms.xml file and add a devices definition and associated wm2003se_only platform definition AFTER the current ppc2003 definition by copying the following:

    <device id="Sprint_PPC6601_Harrier"  displayName="Sprint 6601 Harrier"/>

    <device id="HP_iPAQ_hx4700"   displayName="HP iPaq 4700"/>

   <!--

Windows Mobile 2003 Second Edition Only

    -->

    <platform

        deviceClass="Wince"

        displayName="Windows Mobile 2003 Second Edition Only"  

        id="wm2003se_only"

        swType="WINCE_PACKAGE"

     >

        <query>

            <queryExpression condition="AND">

                <queryClause attribute="computer.OS_MAJOR_VERS" operator="=" value="4" />

                <queryClause attribute="computer.OS_MINOR_VERS" operator="=" value="21" />

            </queryExpression>

        </query>

        <agent>*MSIE 4.01; Windows CE*</agent>

        <device id="HP_iPAQ_hx4700"/>

        <device id="Sprint_PPC6601_Harrier"/>

     </platform> 

 

Note: This code does not need to be modified for your specific WM2003 Second Edition device; it will work for all Second Edition devices as is.

 

3.      Apply the updated definitions by running the following script:

\Program Files\WebSphere\EAS\config\EASWASconfig.bat eas-wps-dm-portlets-updatePlatforms

 

3.1  Restart WebSphere_Portal by running the following script:

\Program Files\WebSphere\AppServer\bin\stopServer WebSphere_Portal -user <was security userid> -password <was security password> \Program Files\WebSphere\AppServer\bin\startServer WebSphere_Portal

 

4. Complete the following updates on the Device Manager Server:

3.1.   Increase the field size for File Legal Trademarks column by completing the following steps

3.1.1.      Open a DB2® command session and do a connect to the dms database For example, if you are on a Windows machine, type:

connect to dms user db2admin using <passwd>

 

alter table FILE_DESC alter column FILE_LEGAL_TRADEMARKS set data type varchar(512) 

 

3.1.2.      commit

3.1.3.      (optional) To ensure that your change is successful, complete the following to verify that the column size is set to 512.             

                                                                       

select typename, length from syscat.columns where tabname='FILE_DESC' and

colname='FILE_LEGAL_TRADEMARKS'                    

 

3.2.   Delete the Pocket PC 2003 and Pocket PC 2002 5.0.1 Device Manager Server packages using the WEA DMS Portlets.  Because of a change to Device Manager Server (DMS) for Windows Mobile 2003 Second Edition, a refresh of the Device Agent is required for Pocket PC 2003.

3.3.   Upload the new 5.0.1.1 Device Manager Server packages to the WebSphere Everyplace Access server using the WEA DMS Portlets. The WEA5011_ppc2003.zip package resides in the \Client\WM2003\dms\ directory.

 

Installing Everyplace Client for Windows Mobile 2003

For installation from the WebSphere Everyplace Access portal, follow these steps:

  1. Open the browser on your device.
  2. Log in to the Portal with the Web address provided by your administrator.
  3. Select the Mobile Setup.
  4. Select the Everyplace Client Installer.
  5. Click on the Everyplace Client Installer icon to start the installation.
  6. Click Install.
  7. Follow the instructions on the screen.

 

Once the installation has completed, verify the build level of the Everyplace Client by following these steps:

  1. Launch Everyplace Client on your device by selecting Start->Programs->Everyplace Client.
  2. On the Welcome screen, tap About to display the build information.

Note: You can also find the build information at the bottom of the My Settings panel.

  1. Verify that the build version is IBM® Everyplace Client V5.0.1.1 – Build 200504291347.

           

 

Known limitations

Invalid pop up message appears when the Everyplace Client starts the WebSphere Everyplace Connection Manager connection

When the Everyplace Client starts the WebSphere Everyplace Connection Manager connection, an invalid pop up message might appear. The popup message requests the user to make a choice between some connection alternatives. Users should NOT select any of the choices presented. Instead, they should dismiss the pop up by either tapping on the Hide link or by tapping elsewhere on the screen. Users can also run the Connection Manager from the Start menu rather than from within the Everyplace Client. The invalid popup message only appears when WebSphere Everyplace Connection Manager is activated from within the Everyplace Client.

 

Everyplace Client Installer Incorrect Message

The Device Management Agent used for Windows Mobile 2003 Second Edition is the same as that used for Windows Mobile 2003.  So when you use the WebSphere Everyplace Access Portal to install the Everyplace Client, you might see the following message on a Windows Mobile 2003 device: “Everyplace Client V5.0.2.0 Base for WM2003SE”.  Alternately, you might see the following message when installing on a Windows Mobile 2003 Second Edition device: “Everyplace Client V5.0.1.1 Base for WM2003”.  In either case, the correct version will be installed to the device.  This is only a documentation problem.

 

Trademarks

(c) Copyright International Business Machines Corporation 1994, 2005. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

 

IBM, WebSphere, Everyplace, and DB2 are trademarks or registered trademarks of the IBM Corporation in the United States, other countries, or both.

 

Windows and Windows Mobile are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both.

 

Other company, product, and service names might be trademarks or service marks of others.