WECM Client Installation and Configuration Instructions

Install WECM Client
Setting Up A Connection
Turning On Client Logs
IBM Mobility Client Readme
   


Install WECM Client
    
1) Obtain the software. Go to URL  "http://www6.software.ibm.com/dl/websphere43/wecm-h?S_PKG=dlwecm50_ww&S_TACT=&S_CMP=". Then in the "Mobility Clients", download "WC5001Win32.exe".

2) Double click on the "WC5001Win32.exe", and in the choice of language panel select "English", then click "Next".

3) In the "Mobility Client" panel, click "Next".

4) Review the IBM Mobility Client readme, then click "Next".

5) Accept the default "Destination Folder", then click "Next".

6) In the "Setup Type" panel, choose "Typical", which will immediately take you to the "Program Folders" panel.

7) In the "Program Folders" panel, accept the default (probably "Access IBM"), then click "Next".

8) In the "Current Settings" panel, review your choices, modify if desired/required, then click "Next".

9) In the "InstallShield Wizard Complete" panel, click "Finish". (if you leave this panel with the default, the "Mobility Connections" panel will be displayed, close if desired or proceed with the following steps.



Setting Up A Connection
(This section uses an example stereotypical connection to a customer's environment)

1) From the Windows "Start" select "Programs", "IBM Mobility Client", and click on "Connections".

2) In the "Mobility Connections" panel double click on "Create Connection".

3) In the "Create a Connection" panel, enter a name for this connection (i.e. "Metlife Connection"), then click "Next".

4) In the "Select a Backup Connection", choose "No" and click "Next".

5) In the "Select a Network" panel, accept the default "IP,WiFi,GPRS, 1XRTT,Broadband", then click "Next".

6) In the "IP Based" panel, for the "What is the Connection Manager address", enter the IP address of the WECM you wish to connect to (i.e. "65.202.19.75"). (you can optionally specifiy a port number, "8889" being the default (i.e. "65.202.19.75:8889")).

7) In the "Select an interface..." panel, select "Defaultl Local IP Interface", then click "Next".

8) In the "Presss "Next" to complete....", click "Next".

9) In the "Start Dialer" panel, click "No".

10) Double click on the "Metlife Connection", and when prompted enter the username/password (i.e.  lv2pvc/password) (see note below). A connection progress display will reflect the status of your connection. If an "Integrity Person Policy Alert" panel appears, click "Yes".

(Note, for some types of connections, additional configuration is necessary. The following is an example of instructions for this configuration)

a) Right click the "Metlife Connection" and select "Properties".
b) In the "Attributes" tab, select "Prompt for user ID and password" a and "Create default route".
c) In the "Security" tab, for the "Preferred encryption" select "AES128".
d) In the "Networks" tab, in the "Configured networks" section, select the "Default Local IP Interface", and click "Properties".
e) In the "Default Local IP Interface" panel, in the "Optimization" tab, select "Compress data", then click "OK", and in the"Metlife Connection" panel click "OK" also.
f) Back in the "Mobility Connections" panel, double click on the "Metlife Connection" icon.

10) To terminate this connection, from the "Mobility Connections" panel, right mouse click on the "Metlife Connection" icon and select "Disconnect".



(Steve, info about Metlife's WEA Server)

at-linyweasvr01.metlife.com/wps/portal
Admin ID wpsadmin/wpsadmin
Domino Test user Weauser/Crc26w
Domino Server  sisciwa1.metlife.com




Turning On Client Logs

1) Execute the program "arttrace.exe" (normally located in "C:\Program Files\IBM\Mobility Client").

2) In the "Trace" dialog box, the "Trace level" section, select the level you desire ("Off", "Performance", "IP", "Low", or "High").

3) In the "Buffering " section, select "Enable buffering".

4) In the "Maximum file size (kB)" section enter an appropriate value (i.e. "10000"). Note this should be set relative to the trace level set in step 2, the higher the trace level, the more data will be collected).



IBM Mobility Client Readme

Welcome to Mobility Client Version 5.0 for Windows and Windows CE,
a component of IBM(R) WebSphere(R) Everyplace(TM) Connection Manager

This README file contains information you need for installing and
running the Mobility Client.  It also contains information   
that was not available for our publications.

This product contains RSA encryption code.

___________________________________________________________________________
Table of contents

1.0  Software requirements
2.0  Hardware requirements
3.0  Getting help
4.0  Installing from CD
5.0  Installing from diskettes
6.0  New features
7.0  Product information
8.0  Fixed Authorized Problem Analysis Reports (APARs)
9.0  Late-breaking information
10.0  Trademarks and Copyright     

___________________________________________________________________________
1.0  Software requirements

  One of the following operating systems is required:
 
   -  Microsoft(R) Windows(R) 98 (SE recommended)
   -  Microsoft Windows Millenium
   -  Microsoft Windows NT(R) Version 4.0 - Service Pack 4 or later
   -  Microsoft Windows 2000
   -  Microsoft Windows XP
   -  Microsoft Windows CE V3.0
  
  Also required is Microsoft ActiveSync Version 3.1 or later (for
  Mobility Client for Windows CE only)

___________________________________________________________________________
2.0  Hardware requirements

  The Mobility Client for Windows CE provides support for the
  following devices: Handheld PC 2000, Pocket PC 2000, and Pocket PC 2002. 
 
___________________________________________________________________________
3.0  Getting help

  Online help is available in the Mobility Client product. 

  See the IBM WebSphere Everyplace Mobility Client User's
  Guide for more information about the types of help that are
  available and instructions on how to access help.

  The guide is in portable document format (PDF) and you will need
  Adobe Acrobat Reader Version 3.0 or greater to display or print it. 
  This guide is located on the web at
  http://www-1.ibm.com/support/search.wss?rs=804&tc=SSZQDW&dc=DA400    

___________________________________________________________________________
4.0  Installing from CD

  If your workstation has a CD drive, you can install the Mobility
  Client directly from CD. Follow the instructions in "Installing
  and configuring the Mobility Client on Windows and Windows CE" in the
  WebSphere Everyplace Mobility Client User's Guide to
  install from CD.
 
  If you have previously installed, see the IBM WebSphere Everyplace
  Connection Manager Administrator's Guide for information about
  applying maintenance.  

  The guide is in portable document format (PDF) and you will need
  Adobe Acrobat Reader Version 3.0 or greater to display or print it. 
  This guide is located on the web at
  http://www-1.ibm.com/support/search.wss?rs=804&tc=SSZQDW&dc=DA400 
 
  When upgrading from a version prior to 2.1.1.11, you must stop the
  client prior to upgrading.  If you do not, you may leave the client
  in a corrupted state.  Should this happen, contact IBM support for
  recovery directions.
 
___________________________________________________________________________
5.0  Installing from diskettes

  From any workstation that has a CD drive, you can create diskettes of
  the Mobility Client for Windows to install on a client
  system. You will need three high-density, formatted diskettes.

  Use a utility that can split a large file into smaller files that fit
  onto multiple diskettes, such as the IBM-created utility CHOPPER.  Follow
  the instructions for CHOPPER at
  http://www.pc.ibm.com/qtechinfo/DSHY-44QSCB.html
  These diskettes can then be taken to a target system and using the same
  CHOPPER utility, recombined into the original single file. When CHOPPER
  splits a file into smaller files, it will copy itself onto the first
  diskette as UNCHOP.EXE. The filename_to_be_transferred is the package-for-
  the-web file in the Win32 or WinCE directories on the installation CD.

  To install Mobility Client from diskettes:
 
  Recombine the single package file onto the client system or a desktop
  system, then click Start --> Run and specify the package file to extract
  the files and install the Mobility Client.

__________________________________________________________________________
6.0  New features for version 5.0

   Enhancements for the Mobility Client on the Windows operating systems that
   include seamless cross-network roaming.

   Windows 95 support withdrawn for the Mobility Client
  
   FIPS 140-2 certification for the Mobility Client for Windows

  
__________________________________________________________________________
7.0  Product information

  Windows Platforms
  ----------------- 
 
   --  IBM's testing has found that the Mobility Client works better
       on Windows 98 SE than on earlier versions of Windows 98. 
       If your computer supports advanced power management, Windows 98 SE
       makes it possible to suspend your computer without breaking the
       network TCP/IP connections.          
      
   --  For IBM PCMCIA DataTAC and IBM PCMCIA CDPD modem users:

       If you are using Microsoft Windows 98, power management on the
       PCMCIA modem slot can interfere with the correct operation of
       these modems.  You must disable power management on the PC card
       slots by installing a registry patch.

       To install the patch, run the program regedit.exe from the Start menu,
       Run... prompt.  Select the menu item Registry, Import registry file.
       When prompted, select the file name
       <your cd-rom drive:>\clients\Win32\en\misc\fixes\power.reg.
       You should see an indication that the registry information was
       successfully entered into the registry.  Restart your computer.

   --  If you are installing a modem driver for the first time on
       Windows 98, Windows NT, Windows 2000, Windows XP, or
       Windows Me, you may be prompted to enter a country code and area code
       for your computer.  This is normal, even if the modem is a
       wireless modem that does not make use of this information. 
       Enter the information when prompted.  
  
   --  When installing the Mobility Client on Windows XP, an "IKernel.exe
       - Application Error" may be encountered. This error is associated
       with InstallShield's kernel engine. Try re-installing the Mobility
       Client. If the error persists, please refer to InstallShield's
       Consumer Central web-site:
         http://consumer.installshield.com/kb.asp?id=Q108190
       for further instructions. The Document ID associated with this
       problem is Q108190.

   -- When upgrading from a version prior to 2.1.1.11, you must stop the
      client prior to upgrading.  If you do not, you may leave the client
      in a corrupted state.  Should this happen, contact IBM support for
      recovery directions.
 
         
  Windows CE Platforms
  --------------------
  
   --  If you are using any of the Socket Communications Serial I/O Cards
       (Serial I/O, Dual Serial I/O) on Windows CE to connect to a Mobitex,
       DataTAC, or Dataradio serial modem, the Mobility Client cannot
       accurately detect when the modem is not responding or is
       disconnected, because the I/O card does not always report write
       failures.  As a result, the client may display timeout error
       messages, but might not shut down as it would normally do when
       unable to write to a modem.
      
   --  If you are using the built-in ActiveSync serial port on a Windows CE
       device to connect to a modem, be sure to choose the modem named
       "Hayes Compatible on COM1:" when setting up your Mobility Client
       connection.  Do not choose "Serial Cable on COM1:" since the Mobility
       Client will not work in this case.  Also, be aware that when
       using the built-in serial port, you will need to use a NULL modem
       adapter or cable to connect to your external modem.
      
   --  DHCP is not supported for the IBM Mobility Interface for Windows on
       Pocket PC devices.  It is supported on Handheld PC 2000 and
       Pocket PC 2002 devices. The IBM Mobility Interface must be configured
       with a static IP address.  This address must match the IP address
       configured for the user at the Connection Manager.  See "Limitations
       of Mobility Client on Windows CE" in the WebSphere Everyplace
       Mobility Client User's Guide for more information on
       DHCP support.
      
   --  On all Windows CE devices except Pocket PC 2002 devices,
       a default gateway is not supported for CDPD and other IP-based
       networks.  If you run the Mobility Client over CDPD or other
       IP-based networks, do not configure the IBM Mobility Interface
       as the default interface.  See "Limitations of Mobility Client
       on Windows CE" in the WebSphere Everyplace Mobility Client User's
       Guide for more information on default gateway support.
                                                                          
_________________________________________________________________________
8.0 Fixed Authorized Problem Analysis Reports (APARs)

Problems resolved with version 5.0 - None at this time


_________________________________________________________________________
9.0 Late-breaking information

In the Mobility Client for Windows User's Guide Chapter 3, Table 6:
Parameters that describe an interface, an additional row should be
included:
Parameter name - RoamSuspendInactive
Description - When an interface supports suspend/resume (short-hold mode),
then this value determines whether or not to suspend the connection when
when it is not the active interface. A value of 0=do not suspend and a
value of 1=suspend. The default value is 0.


_________________________________________________________________________
10.0  Trademarks and Copyright
                  
Everyplace, IBM, and WebSphere, are trademarks or registered trademarks
of the IBM Corporation in the United States or other countries or both.

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

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

Copyright International Business Machines and others, 1994, 2003.
All rights reserved.