Mobility Client User's Guide - IBM - United States · v Install and configure the Mobility Client for Nokia devices v Manage accounts ... When this parameter is set to Yes UDP will

Lotus® Mobility Client for Nokia devicesVersion 6.1.4

User's Guide

��

Lotus® Mobility Client for Nokia devicesVersion 6.1.4

User's Guide

��

Note

Before using this information and the product it supports, read the information in Notices.

This edition applies to version 6, release 1 modification 4 of IBM Lotus Mobile Connect (product number 5724-R20)and to all subsequent releases and modifications until otherwise indicated in new editions.

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in anyway it believes appropriate without incurring any obligation to you.

©Copyright International Business Machines Corporation and others 1994, 2010. All rights reserved.

Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure issubject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

Contents

Chapter 1. About the Mobility Clientguide for Nokia devices . . . . . . . . 1Who should read this information . . . . . . . 1What's new in this release . . . . . . . . . . 1

Chapter 2. Getting started . . . . . . . 3Understanding network access . . . . . . . . 3Prerequisites . . . . . . . . . . . . . . 3Installing and launching the Mobility Client . . . . 3Creating a new account. . . . . . . . . . . 3Establishing a connection to the Connection Manager 8Removing the Mobility Client . . . . . . . . 8

Chapter 3. Managing accounts . . . . . 9Editing an account . . . . . . . . . . . . 9Deleting an account . . . . . . . . . . . . 9Duplicating an account . . . . . . . . . . . 9Setting a default account . . . . . . . . . . 9Changing the password . . . . . . . . . . 10Hiding and showing the active connection . . . . 10Disconnecting the active connection . . . . . . 11

Chapter 4. Using the Mobility Client . . 13Viewing the connection information . . . . . . 13

Using advanced settings . . . . . . . . . . 14Using trace . . . . . . . . . . . . . . 15

Enabling logging . . . . . . . . . . . 15Clearing the log file . . . . . . . . . . 16Moving files between the device and the desktop 16

Exporting and importing configuration files . . . 17Checking that applications are running beforeconnecting. . . . . . . . . . . . . . . 18Automatically starting applications after connecting 19Using cross-network roaming . . . . . . . . 20

Changing Internet access point priority . . . . 21Applying maintenance. . . . . . . . . . . 21

Chapter 5. Configuring clients withconfiguration files . . . . . . . . . . 23

Chapter 6. Accessibility . . . . . . . 33

Chapter 7. Notices . . . . . . . . . . 35Trademarks . . . . . . . . . . . . . . 37

Index . . . . . . . . . . . . . . . 39

iii

iv Mobility Client User's Guide

Chapter 1. About the Mobility Client guide for Nokia devices

This document provides information about using the Mobility Client for Nokiadevices, a component of IBM® Lotus® Mobile Connect. The Mobility Client enablessecure access to enterprise networks from these devices:v Nokia 9300 Communicatorv Nokia 9300i Communicatorv Nokia 9500 Communicatorv Nokia E50v Nokia E51v Nokia E52v Nokia E55v Nokia E60v Nokia E61v Nokia E61iv Nokia E66v Nokia E70v Nokia E71v Nokia E71xv Nokia E72v Nokia E75v Nokia E90

Note: The steps to complete tasks differ depending on which device you are using.For the Nokia 9300, 9300I, or 9500 Communicator devices, use theinstructions labelled On Nokia Communicator. For the Nokia Exx devices,use the instructions labelled On Nokia E series.

Who should read this informationThis information describes how to use the Mobility Client for Nokia devices. Youshould read this information if you want to complete the following tasks:v Install and configure the Mobility Client for Nokia devicesv Manage accountsv Complete Mobility Client tasks, such as using trace, exporting and importing

configuration files, or using cross-network roaming

You should already be familiar with how to navigate applications using the Nokiadevices.

What's new in this releaseNew in version 6.1.4 of the Mobility Client:v Added support for the Nokia E52, E55, E71x and E72 devices.v Support for connection oriented protocols (HTTP and HTTPS). This support will

allow the client to communicate on networks where UDP traffic is not permitted.

1

2 Mobility Client User's Guide

Chapter 2. Getting started

To get started using the Mobility Client, it helps to first understand network accessusing Nokia devices. Then, review and verify that you have met the prerequisitesand complete the tasks described in the following sections.

Understanding network accessEach network connection on Nokia devices is represented by a named Internetaccess point (IAP). There are several types of IAPs: WiFi, general packet radioservice (GPRS), global system for mobile communications (GSM), IP pass-through,and virtual private network (VPN). You create separate IAPs for each specificconnection within these types. For example, you would have separate IAPs (withnames you define) for each network type that you use: GPRS access point name(APN), GSM phone number, and WiFi service set identifier (SSID).

Note: WiFi is not supported on the Nokia 9300.

PrerequisitesThe list of detailed system requirements is available online. See:v Detailed system requirementsv Hardware requirementsv Supported operating systemsv List of supported software

Installing and launching the Mobility ClientInstall the Mobility Client on your Nokia device using a SIS or SISX file. A SIS fileis used on Nokia Communicator devices. A SISX file is used on Nokia E seriesdevices. Use the SIS or SISX file to install the software from a computer or it canalso be downloaded using e-mail or the phone's browser, then installed. It can alsobe installed to a memory card. Refer to the documentation that came with yourNokia device.

After you complete the installation, the Mobility Client is displayed in your list ofapplications.

When you launch the Mobility Client by selecting the Mobility Client applicationfrom the list of applications, a window opens.On Nokia E series devices, thewindow is named Mobility Client and on the Nokia Communicator devices, thewindow is named Mobility Client Accounts.

Creating a new accountThe settings in your account determine the Connection Manager to which youconnect and how data is transmitted, such as whether it is encrypted orcompressed.

Notes:

3

http://www.ibm.com/support/docview.wss?&uid=swg27008473




1. If you are using Mobility Client for the first time, you only have theoption to create a new account. After you create an initial account, youcan create, edit, connect, and delete Mobility Client accounts.

2. The Nokia Communicator account settings are separated in the userinterface using tabs. On the Nokia E series devices, all account settingsare listed together.

To create a new account:1. Specify the values you want to use for account, user ID, password, password

prompt, and organizational unit:

On Nokia E seriesPress the button next to Options on the Mobility Client window. SelectAccount → New.

On Nokia CommunicatorPress the button next to New on the Mobility Client Accounts window.Select the Logon tab.

Use these descriptions to complete these fields:

AccountThis field indicates the name of your account. The account name isdisplayed in the account list on the main screen. By default, theMobility Client names the first account you create, Account-1. You canchange the account name by specifying a unique name in the field. Thisis a required field.

If you choose not to rename the new connection and leave theconnection name as Account-1, each subsequent account you create isnamed Account followed by a hyphen and a number. For example, thenext connection is named Account-2.

User IDThis field indicates the name by which a user is defined on theConnection Manager. This field is required.

PasswordThis field indicates the password that corresponds to the account's userID.

Password promptThis field indicates whether the user should be prompted for thepassword on every login. If the password field is empty, thenprompting will occur regardless of the password prompt setting.

Org. unitThis field provides a way to define and group resources, such as users.Org. Unit might be an optional field in your environment. Completethis field only if instructed to do so by your administrator.

2. Specify these fields to further define the account.

On Nokia E seriesSelect Connections, then press the button next to Options on theMobility Client window. Select Add connection.

Note: The Connections setting is only available on devices runningSymbian OS 9.2 or older. Devices running Symbian OS 9.3 andnewer, will use the device system settings to configure the accesspoints that the Mobility client will use. These access points


should be added to the Internet Network destination which isfound under Destinations in the Connection section of thedevice settings.

On Nokia CommunicatorUse the Menu key to select the Connections tab.

This list specifies the Internet access points (IAP) that the Mobility Client usesto communicate with the Connection Manager. IAPs can be added, deleted andprioritized. The Mobility Client uses the highest priority IAP, which appears atthe top of the list. Select the IAPs that you want associated with this account.

Notes:

a. Connections must be added as access points before they appear inthe list.

b. When adding a Wi-Fi connection on the Nokia 9300 or 9500Communicator devices, be sure to set Hidden Network? to Yes ifthe Wi-Fi network has its SSID hidden. Otherwise, the MobilityClient cannot use this connection.

3. Specify these fields to further define the account.

On Nokia E seriesScroll down to display the fields.

On Nokia CommunicatorUse the Menu key to select the Settings tab.

Use these descriptions to complete these fields:

Server IP addressThis field indicates the IP address of the Connection Manager you wantto use for this account. Specify this field using the host name or usingdotted-decimal format.

TX port (only on Nokia Communicator)This field indicates the port number that the Mobility Client uses tosend data to the Connection Manager. This value must match thecorresponding entry on the Connection Manager and should not bechanged unless requested by your administrator. The valid range ofvalues is 1-65535. The default value for this port is 8889.

Protocol (only on Nokia E Series)Introduced in version 6.1.4, this setting allows the user to configure thesettings for UDP, HTTP and HTTPS connections. Select Protocol todisplay the following settings:

Enable UDPWhen this parameter is set to Yes UDP will always be the firstprotocol used when the Mobility Client attempts a connectionto the Connection Manager. This is true for both initialconnections and connections that are being re-establishing afterroaming from one physical access point to another. Setting thisparameter to No will cause the Mobility Client to never attemptconnections over UDP.

UDP port numberThis field indicates the port number that the Mobility Clientuses to send data to the Connection Manager when using theUDP protocol. This value must match the corresponding entryon the Connection Manager and should not be changed unless

Chapter 2. Getting started 5

requested by your administrator. The valid range of values is1-65535. The default value for this port is 8889.

Enable HTTPWhen this parameter is set to Yes the HTTP protocol will beused for connections to the Connection Manager only if theUDP protocol has not been enabled or if a connection attemptover UDP has failed. This is true for both initial connectionsand connections that are being re-establishing after roamingfrom one physical access point to another. Setting thisparameter to No will cause the Mobility Client to never attemptconnections over HTTP.

HTTP port numberThis field indicates the port number that the Mobility Clientuses to send data to the Connection Manager when using theHTTP protocol. This value must match the corresponding entryon the Connection Manager and should not be changed unlessrequested by your administrator. The valid range of values is1-65535. The default value for this port is 80.

Enable HTTPSWhen this parameter is set to Yes the HTTPS protocol will beused for connections to the Connection Manager only if theUDP and HTTP protocols have not been enabled or if aconnection attempt over UDP and HTTP has failed. This is truefor both initial connections and connections that are beingre-establishing after roaming from one physical access point toanother. Setting this parameter to No will cause the MobilityClient to never attempt connections over HTTPS.

Note: Connections to the Connection Manager gateway usingHTTPS require that a trusted (not self-signed) certificatebe installed on the Connection Manager.

HTTPS port numberThis field indicates the port number that the Mobility Clientuses to send data to the Connection Manager when using theHTTPS protocol. This value must match the correspondingentry on the Connection Manager and should not be changedunless requested by your administrator. The valid range ofvalues is 1-65535. The default value for this port is 443.

Use proxy serverWhen this parameter is set to Yes the Mobility Client willattempt connections to the Connection Manager via a proxywhen the HTTP or HTTPS protocol is being used. Setting thisparameter to No will cause the Mobility Client to attempt directconnections to the Connection manager when using the HTTPor HTTPS protocols.

Note: This setting is ignored when the UDP protocol is beingused.

Proxy addressThis field indicates the IP address of the proxy server you wantto use for HTTP and HTTPS connections. Specify this fieldusing the host name or using dotted-decimal format.


Proxy port numberThis field indicates the port number for the proxy server youwant to use for HTTP and HTTPS connections. This value mustmatch the listening port on the proxy server as specified byyour administrator. The valid range of values is 1-65535. Thedefault value for this port is 8080.

Select Back or Done to return to the main account settings.

EncryptionThis field specifies the level of encryption for your connection.Encryption prevents unauthorized access to data by transforming it intoan unintelligible form, so that the original data can only be obtained byusing a decrypting process. If the Connection Manager requiresencryption, select a level of encryption that is supported by theConnection Manager. Choose from:

None Disables encryption

AES128A 128-bit encryption algorithm using advanced encryptionstandard (AES)

AES192A 192-bit encryption algorithm using AES

AES256A 256-bit encryption algorithm using AES

DES An encryption algorithm using DES (data encryption standard)

Auto roamingSetting this parameter to Yes causes the Mobility Client to periodicallysearch for higher priority IAPs to use in communicating with theConnection Manager. If a higher priority IAP is found, then theMobility Client switches to that connection. The existing virtual privatenetwork (VPN) session is maintained in a seamless way during thisphysical connection transfer.

Notes:

a. Auto roaming is only available when you have more thanone connection defined for the account.

b. Setting Auto roaming to No does not disable roaming. Aslong as your account has more than one connection specifiedfrom the list of IAPs, then you can manually roam byselecting Roam.

c. Auto roaming consumes additional power. To minimizebattery usage, do not enable Auto roaming. Instead,manually initiate roaming on the Mobility Client screen:

On Nokia E seriesPress the Options softkey, then select the Roammenu item.

On Nokia CommunicatorPress the Roam softkey.

Roaming intervalIf you have enabled Auto roaming, then this field specifies how oftenthe Mobility Client checks to see if a higher priority IAP is available.

Chapter 2. Getting started 7

ProxiesProxies can be set for HTTP or HTTPS. If Use proxy server is selectedthen separate proxies can be specified.

Note: The Proxies setting is only available on devices running SymbianOS 9.2 or older. Devices running Symbian OS 9.3 and newer, willuse the device system settings to configure the proxy used byapplications that use HTTP and/or HTTPS stack via the VPNsession. This proxy should be configured in the Mobility Clientaccess point in the Intranet Network destination which is foundunder Destinations in the Connection section of the devicesettings.

4. See “Automatically starting applications after connecting” on page 19 for moreinformation about the Autostart options.

5. On Nokia E series devices, select Back. On Nokia Communicator, select Done.

Establishing a connection to the Connection ManagerAfter you create a new user account, you can use that account to establish aconnection with the Connection Manager.

On Nokia E seriesSelect the account that you want to use. Press the button next to Optionson the Mobility Client window, then select Connect.

On Nokia CommunicatorSelect an account then select Connect on the Mobility Client Accountswindow.

Note: If you do not select an account, the Default account is connected.

Removing the Mobility ClientTo remove the Mobility Client:

On Nokia E series

1. From the Main menu, select Tools → App mgr.2. Select Mobility Client.3. Select Options → Remove.

On Nokia Communicator

1. From the Main menu, select Tools → Control panel → Datamanagement → Application Manager.

2. Select Mobility Client.3. Press the button next to Remove.


Chapter 3. Managing accounts

After you have installed and configured the Mobility Client, you can manageaccounts.

Editing an accountTo edit an account:

On Nokia E seriesSelect the account that you want to edit, then press the button next toOptions on the Mobility Client window. Select Account → Edit. Modify thefields you want to edit, then select Back.

On Nokia CommunicatorUse the arrow keys to select the account you want to edit from the list ofaccounts and select Edit. Modify the fields you want to edit, then selectDone.

Deleting an accountTo delete an account:

On Nokia E seriesPress the button next to Options on the Mobility Client window. SelectAccount –> Delete. Press OK on theConfirm window to confirm theaccount you want to delete.

On Nokia CommunicatorPress the Menu key and use the arrow keys to select Account -> Delete,then press the button next to Select. Press OK on the Confirm window toconfirm the account you want to delete.

Duplicating an accountTo duplicate an account:

On Nokia E seriesSelect the account you want to duplicate, then press the button next toOptions on the Mobility Client window. Select Account → Duplicate.

On Nokia CommunicatorPress the Menu key and use the arrow keys to select Account → Duplicate,then press the button next to Select.

The Mobility Client appends a hyphen (-) and a number to the account name youduplicated and opens the duplicated account for editing.

Setting a default accountIt is not required that you initially log on using the Connect selection from theMobility Client Accounts window (on Nokia Communicator devices) or theMobility Client window (on Nokia E series devices). You can select the MobilityClient Internet access point (IAP) as your connection from an application, and it

9

will log you in automatically if you are not already logged in. The account withwhich it connects automatically is known as the default account.

To set the default account:

On Nokia E seriesSelect the account you want to set as default, then press the button next toOptions on the Mobility Client window. Select Account → Set as default.

On Nokia CommunicatorPress the Menu button to view the Mobility Client Accounts window.Select the account you want to set as default, then select Account → Set asdefault.

The word (default) is displayed next to the account name.

Changing the password

To change the password:1. Make sure you have successfully established a connection.

On Nokia E seriesPress the button next to Option on the Mobility Client window. SelectAccount → Password change.

On Nokia CommunicatorPress the Menu key. Select Account → Password change.

2. Type in the existing password in the Old Password field.3. Type in the new password twice, once in the New Password field and once in

the Confirm field.4. Select Done on Nokia E series or OK on Nokia Communicator.

Hiding and showing the active connectionAfter you are successfully connected, you can hide the Mobility Client so that it isoperating in the background. The Mobility Client must remain active while you arelogged on, but it does not need to be in the foreground. The action of hiding theapplication is not the same as disconnecting from the Connection Manager.

To hide the active connection:1. Establish a connection with the Connection Manager.2.

On Nokia E seriesPress the Back softkey.

On Nokia CommunicatorFrom the Mobility Client Accounts window, select Hide.

To show the active connection when it is in the background:1.

On Nokia E seriesPress the Menu key, to the left of the joy stick.

On Nokia CommunicatorPress the Desk button at the upper left-hand corner of the keyboard.


2. Use the arrow keys to select the Mobility Client icon.

Disconnecting the active connectionTo disconnect from the Connection Manager:

On Nokia E seriesPress the button next to Options on the Mobility Client window. SelectDisconnect.

On Nokia CommunicatorFirst make sure that the Mobility Client is operating in the foreground andis not hidden. From the Mobility Client Accounts window, selectDisconnect.

Chapter 3. Managing accounts 11


Chapter 4. Using the Mobility Client

After you have installed and configured the Mobility Client, you can use otherMobility Client features.

Viewing the connection informationThe Connection Status window displays information about your networkconnection.

To view the general information, statistics, and settings for your connection:1. Establish a connection with the Connection Manager.2. To view the general information for your connection:

On Nokia E seriesPress the button next to Options on the Mobility Client window. SelectConnection → Connection status.

On Nokia CommunicatorPress the Menu key. Use the arrow keys to select Connection →Connection Status and press the button next to Select. Then, select theGeneral tab.

The descriptions of each field include:

Network connection (E Series only)Specifies the physical internet access point (IAP) currently being usedfor the connection to the Connection Manager.

Protocol (E Series only)Specifies the protocol currently being used for the connection to theConnection Manager.

Local AddressSpecifies the Internet Protocol (IP) address that the network uses toaccess your mobile device.

Gwy AddressSpecifies the dotted-decimal IP address that the network uses to accessthe Connection Manager.

Primary DNSSpecifies the address of the primary domain name system (DNS) serverused by your device.

Secondary DNSSpecifies the address of the secondary DNS used by your device.

3. To view the statistics for your connection:

On Nokia E seriesScroll down to see the statistics fields.

On Nokia CommunicatorSelect the Statistics tab.


13

Pkt SentSpecifies the number of packets sent by the Mobility Client since youconnected to the Connection Manager.

Pkt ReceivedSpecifies the number of packets received by the Mobility Client sinceyou connected to the Connection Manager.

Bytes SentSpecifies the number of bytes sent by the Mobility Client since youconnected to the Connection Manager.

Bytes ReceivedSpecifies the number of bytes received by the Mobility Client since youconnected to the Connection Manager.

Conn. TimeSpecifies the total time that your Mobility Client has been connected tothe Connection Manager. When roaming is enabled, this value specifiesis the time you last roamed from one network to another.

Note: Statistics are not dynamically updated but are a record of the currentstate when you invoke the view.

4. To view the connection settings:

On Nokia E seriesScroll down to see the connection setting fields.

On Nokia CommunicatorSelect the Settings tab.


CompressionSpecifies whether compression is enabled.

EncryptionSpecifies the level of encryption for your connection.

Header reductionSpecifies whether header reduction is enabled

Keep alive intervalSpecifies how often an echo packet is sent to the Connection Managerserver for the purpose of keeping a constant network path open.

After you are finished reviewing the fields, select OK.

Using advanced settings

The Advanced settings window displays information about your networkconnection. You should modify these settings only when you are instructed to byyour administrator.

To view or modify these settings:

On Nokia E seriesPress the button next to Options on the Mobility Client window. SelectConnection → Advanced settings.


On Nokia CommunicatorPress the Menu key. Use the arrow keys to select Connection → Advancedsettings and press the button next to Select.


Disconnect if idle forIf no data is sent in the time specified, then Mobility Client automaticallydisconnects from the Connection Manager. This timeout has these possiblevalues: unlimited, 2 minutes, 5 minutes, 10 minutes, 1 hour, 2 hours, or 4hours.

Stop roaming/keep alive if idle forIf no data is sent in the time specified, then the Mobility Clientautomatically stops the keep alive feature. When data transfer resumes, theMobility Client attempts to find the fastest connection. This timeout hasthe following possible values: unlimited, 2 minutes, 5 minutes, 10 minutes,1 hour, 2 hours, or 4 hours.

After you are finished reviewing the advanced settings, select Save on Nokia Eseries or Done on Nokia Communicator.

Using traceAfter you have installed and configured the Mobility Client, you can work withtrace logs. By default, the Mobility Client traces information during the logonprocess. After logon completes, the log settings that you define are used.

The trace log is stored on the device in the file:

On Nokia E seriesData\Mobility Client\Log\wecmlog.txt

On Nokia CommunicatorCommunicator\My Files\Mobility Client\Log\wecmlog.txt

When directed by an administrator, you should enable tracing or transfer the logfile from the device to your desktop computer.

Enabling loggingYou can enable the Mobility Client to log messages that are used for problemresolution.

Note: Do not enable logging unless instructed by your administrator.1. To enable logging:

On Nokia E seriesPress the button next to Options on the Mobility Client window. SelectTools → Log settings.You can modify each setting individually or pressthe button next to Options choose from Log All or Default logging.

On Nokia CommunicatorFrom the Mobility Client Accounts window, press the Menu key. Usethe arrow keys to select Tools → Log Settings and press the button nextto Select.

Use these descriptions to complete the log settings:

Chapter 4. Using the Mobility Client 15

Max SizeSpecifies the number of Kilobytes of data that the log will grow tobefore writing over the data in the log. You can specify the log size tobe as large as the amount of file space you have available.

Logon traceSpecifies that logging is automatically turned on during the logonprocess. The default value is that logging is automatically turned on.After logon completes, the settings on System and Level fields areused. When only Logon trace is on, the log file is reset each time theaccount is successfully connects.

SystemSpecifies which Mobility Client components will monitor and recordinformation in the log. Select the parameters for each system you wantlogged. On Nokia Communicator devices, select Yes. On Nokia E seriesdevices, select System.

Level Specifies the level of messages that the Mobility Client will store in thelog. On Nokia Communicator devices, select Yes for the level you wantenabled. On Nokia E series devices, select the levels you want enabled.

2. After you finish changing the log settings, press the button next to Back onNokia E series or OK Nokia Communicator.

Clearing the log fileTo delete the contents of the log file:

On Nokia E SeriesPress the button next to Options on the Mobility Client window. SelectTools → Clear log file.

On Nokia CommunicatorPress the Menu key. Use the arrow keys to select Tools → Clear log fileand press the button next to Select.

Moving files between the device and the desktopThere are several ways you can move files to or retrieve files from Nokia devices.You can use e-mail, the phone's browser, a multimedia card (MMC), or an infraredconnection.

These instructions assume that you are using a Microsoft® Windows® desktopmachine and an infrared (IR) connection.

To move a file from the device to the desktop1. Activate the infrared connection.

On Nokia E series

a. From the main menu, select Connect → Infrared → Activate.b. Place the device next to the IR port on the desktop computer. The

desktop machine recognizes the device and opens a wireless linkicon in the system tray of the desktop machine.

c. On the device, select the Main Menu → Office → File mgr, thenselect the file to be transferred.


a. On the device, activate the IR port by pressing the Chr key and theright arrow key.


b. Place the device next to the IR port on the desktop computer. Thedesktop machine recognizes the device and opens a wireless linkicon in the system tray of the desktop machine.

c. On the device, select the File manager, then select the file to betransferred.

2. Send the file.

On Nokia E seriesPress the button next to Options. Select Send → Via infrared.

On Nokia CommunicatorPress the Menu button, then select Send → Via infrared, then pressSelect.

3. On the desktop machine, accept the transfer and the file is stored in yourDesktop folder.

To move a file from the desktop to the device:1. Activate the infrared connection.

On Nokia E seriesFrom the main menu, select Connect → Infrared → Activate.

On Nokia CommunicatorOn the device, activate the IR port by pressing the Chr key and theright arrow key.

2. Place the device next to the IR port on the desktop computer. The desktopmachine recognizes the device and opens a wireless link icon in the system trayof the desktop machine.

3. Double-click the icon to open a dialog to transfer files to the device. Select thefile and press Send in the Wireless Link dialog to transfer the file to the device.

Exporting and importing configuration filesYou can export and import configuration files as directed by an administrator toset or change Mobility Client configuration options. There are several ways youcan move files to or retrieve files from Nokia devices.

To export a configuration file:1. On the device from the Mobility Client Accounts window, press the Menu key.2. Use the arrow keys to select Tools → Export configuration.3. Determine if you want to export the file as a platform-independent

configuration or whether you want to export the complete configuration. SelectExport as platform-independent → Yes when you want to export aconfiguration that can be used by any installed Mobility Clients. Select Exportas platform-independent → No when you want to export a configuration thatcan be used only by Mobility Clients using Nokia devices.

4. When Export as platform-independent is set to No, determine if you want toExport advanced settings for the account. When exporting a configuration asplatform-independent, this field is ignored.

5. Select Export to export the file.6. By default, you are prompted to save the file in this directory:

On Nokia E seriesMobility Client\Export


On Nokia CommunicatorCommunicator\My Files\Mobility Client\Export

Enter the file name, then select OK.When Export as platform-independent is set to No, the default file name isconfig.wecm. When Export as platform-independent is set to Yes, the defaultfile name is config.pdb.

7. Transfer the exported file from the device to the desktop machine.

To import a configuration file:1. Transfer the file to import from the desktop machine to the directory My

Files\Mobility Client\Import.2. On the device from the Mobility Client Accounts windows, press the Menu

key.3. Use the arrow keys to select Tools → Import configuration.4. Select the file you want to import, then select Open or select Browse to find

the file from another directory. Select OK to import the file.

The Mobility Client automatically determines if the imported file isplatform-dependent or platform-independent and handles the format accordingly.If the advanced settings were specified in the export that created the import file,then the advanced settings replace the current advanced settings in the devicewithout any prompting.

The accounts in the import file are all added to the phone. If an account name inthe import file already exists, a message displays indicating that the account existsand will merge the two accounts. When an account is merged, the user ID andpassword of the account originally on the device is maintained. Then, eachconfiguration item for that account that is defined in the import file replaces thevalue in the account currently on the device. If a configuration item in the importfile is omitted, then the original value in the account is retained.

Checking that applications are running before connectingThe Mobility Client can check that certain programs are running, like antivirus orpersonal firewall software, before allowing the connection to start.

You can modify the configuration file to add parameters that let the MobilityClient check for up to 16 applications before starting a connection. If theapplications listed are not running, the Mobility Client starts them for you. Toconfigure these settings, manually edit the configuration file.See Chapter 5,“Configuring clients with configuration files,” on page 23.

Note: If an application cannot be started, an error message is displayed. You willnot be able to log on until all necessary applications are running.

Application configuration parameters are stored in the account configuration fileand stored in c:\system\data\Mobility Client\accounts directory. To create newconfiguration or change existing application check parameters, enter them in the<account_name>.conf file:

PrereqAppName1 ... PrereqAppName16One PrereqAppName for each application that must be executing before aconnection attempt can proceed. The application name is a descriptivename that is displayed to the user in informational and error messages.


PrereqAppProcess1 ... PrereqAppProcess16Where PrereqAppProcess1 is the name of the first process that must berunning before the Mobility Client attempts to connect, andPrereqAppProcessn is the last process that must be running before theMobility Client attempts to connect.

PrerequisiteDisabledIf PrerequisiteDisabled is set to 1, then the applications are ignored and nochecking is done.

Automatically starting applications after connectingYou can configure the Mobility Client to launch up to 16 applications automaticallyafter a connection has been established. In addition to specifying the applicationname, you can also configure any parameters with which you want the applicationstarted.

After a successful logon, the applications are started in the order in which they arelisted on the Autostart tab. Note that when the applications are started, they mightopen on the screen in a different order, depending on how much time it takes untilthey display on the screen.

To view or modify which applications are automatically started and their priority :1. Edit the account for which you want to automatically start applications.

On Nokia E series

a. Select the account that you want to edit, then press the button nextto Options on the Mobility Client window. Select Account → Edit.

b. Scroll down to Autostart and select Options → Change.c. To add applications, select Options → Add application → Select

App → OK


a. Use the arrow keys to select Account and press the button next toEdit on the Mobility Client Accounts window.

b. Press the Menu key to select the Autostart tab.c. Select Add to add an application to the list of applications

automatically launched after a connection has been established.Note that only one instance of an application can be added to thelist.

d. Use the arrow keys to select the application from the list.e. Optionally, in the Parameters field, type the parameters that you

want used when the application starts. For example, if you wantedto specify when the browser starts and automatically connects to aURL other than your home page, specify that URL in this field.Select OK when complete.

2. Add as many as 16 applications to the list. Then, prioritize the list so that theapplications are automatically started in the order in which they are displayedfrom the top to the bottom of the list. Select Priority then select Move up orMove down.

3. Select Done when complete.

To delete an application from the list, select the application then select Delete.


Using cross-network roamingUsing seamless cross-network roaming, the Mobility Client connection andapplications persist when switching networks in a multi-network environment.Persistence allows switching physical networks, while preserving both theconnection and application session. At configurable intervals, the Mobility Clientchecks to see if there is a connection available that is of higher priority than theconnection currently being used.

The candidate connections available for roaming are those Internet access points(IAP) displayed:

On Nokia E seriesin the list as seen on the Select IAP window

On Nokia Communicatorin the list as seen on the Connections tab of the logged in account.

The priority of these IAPs are determined by their relative priority positions set inlist. An exception to the roaming priority occurs on WiFi IAPs. When the MobilityClient is currently connected to a WiFi IAP and a higher priority WiFi IAPbecomes available, it will not switch to it. To set the priority of IAPs, see“Changing Internet access point priority” on page 21.

Roaming is enabled or disabled for each account.1. To modify or view roaming configuration:

On Nokia E series

a. Press the button next to Options on the Mobility Client window.Select Account → Edit.

b. Scroll down until you see Auto roaming.


a. Use the arrow keys to select Account and press the button next toEdit on the Mobility Client Accounts window.

b. Press the Menu key to select the Settings tab.c. Use the arrow keys to select Auto roaming.

2. Select Yes if you want Mobility Client to periodically check for the availabilityof Internet Access Points (IAPs) assigned to the network ID you choose foryour account. If an IAP with a higher priority becomes available, MobilityClient roams to take advantage of that IAP. Select No if you do not want toroam while you are logged in to Mobility Client. If you select No, MobilityClient uses the highest priority IAP available at the time you log in. It uses thisIAP throughout the duration of your session.

3. If Auto roaming is set to Yes, then use the arrow keys to select Roaminginterval. This field specifies in seconds how often the Mobility Client checks tosee if a higher priority IAP is available for roaming. The default value is 30seconds.

4. On Nokia Communicator devices only, use the arrow keys to select theConnections tab. If you access any WiFi networks whose service set identifier(SSID) names are hidden, select any applicable networks and select Edit, thenselect Hidden network? and choose Yes.If you do select to use hidden WiFi networks, you might want to set theRoaming interval higher than the default value.

5. Select Done when complete.


Note: WiFi is not supported on the Nokia 9300.

Changing Internet access point priorityTo change the priority of an Internet access point (IAP), edit the account for whichyou want to automatically start applications.

On Nokia E series

1. Select the account that you want to edit, then press the button next toOptions on the Mobility Client window. Select Account → Edit.

2. Scroll down and select Connections.3. After selecting an IAP, select Options → Move up or Options → Move

down to change the priority of the selected IAP.4. Select Back when complete.


1. Use the arrow keys to select the account you want to edit from the listof accounts and select Edit.

2. Select the Connections tab.3. After selecting an IAP, select Move up or Move down to change the

priority of the selected IAP.4. Select Done when complete.

Note: The IAP at the top of the list has the highest priority. The IAP at the bottomof the list has the lowest priority.

Applying maintenanceLinks to code fixes, for entitled customers, are available from the Lotus MobileConnect Product Support web site (http://www-01.ibm.com/support/docview.wss?rs=3183&uid=swg27009682). The Lotus Mobile Connect updates arelocated on IBM Fix Central product Support web site (http://www.ibm.com/support/fixcentral/). Lotus Mobile Connect customers can register at the web sitefor an IBM ID if they do not already have one. A list of authorized ID's wascreated at the time which Lotus Mobile Connect was purchased from IBM. If theIBM ID being used to access IBM Lotus Mobile Connect is not on this list anentitlement failure message will be received. Please contact your IBM Marketingand Sales representative for assistance with the authorized users list.

For the Mobility Client for Nokia devices, there is one file which is approximately600 KB and contains all supported languages.

Where version is the version number of the code, the files are dependent on thedevice type:

Nokia E seriesMCversionESeries.sisx

Nokia 9500 Communicatorwcversion9500.zip

Nokia 9300 and 9300i Communicatorwcversion9300.zip

After downloading the file, unzip it, then make sure that the device is connected tothe desktop computer. Double-click the sis or sisx file to begin installation.


http://www-01.ibm.com/support/docview.wss?rs=3183&uid=swg27009682

http://www-01.ibm.com/support/docview.wss?rs=3183&uid=swg27009682

http://www.ibm.com/support/fixcentral/


Chapter 5. Configuring clients with configuration files

To configure a Mobility Client to use a specific configuration, first export aconfiguration file that is not platform-independent. Then, edit the file to containthe parameters you want to use and import the configuration file. See “Exportingand importing configuration files” on page 17 for more detail.

The configuration file consists of lines of the form: parameter-name =parameter-value. Parameter names are alphanumeric strings. Parameter values canbe textual or numerical. Note that parameters that take boolean values use 1 fortrue and 0 for false.

The configuration file is stored in the c:\system\data\Mobility Client\accountsdirectory and is named account_name.conf, where account_name is the name of theaccount. The first line of the file is WECM EXPORT. If this line is missing, the filedoes not import correctly.

The file is divided into sections. Each section is preceded by a period (.) and asection name. The first section, .account account_name, contains global informationabout the configuration of this Mobility Client. Subsequent sections containinformation about the connections and their interfaces and are preceded by.interface . Global configuration settings are preceded by the .global tag. The endof the .interface and .global sections are specified by .end.

If no value is specified for a parameter, the Mobility Client will either use a defaultvalue, attempt to negotiate a value for the parameter at connect time, or promptthe user.

Note: Do not attempt to change these values when the Mobility Client account isconnected to the Connection Manager.

Table 1. Account parameters configuration

Parameter name Description

ALPRetries The number of times to reattempt a failed logon negotiationwith the Connection Manager. The default value is 3. Usedonly if UseSpeedForWLPSettings is set to 0. WhenRequestTransportProfile = 1, this parameter is ignored.

ALPTimeout The number of seconds to wait for a logon attempt tocomplete before timing out and closing the connection. Thedefault value is 30. Used only if UseSpeedForWLPSettings isset to 0. When RequestTransportProfile = 1, this parameter isignored.

AuthMethod Method that the Connection Manager uses to validate theMobility Client. This value should not be changed from thedefault value of 1 unless instructed by your administrator.Allowable values are:

0 Reserved

1 The Connection Manager requires user ID andpassword authentication.

2 Reserved

23

Table 1. Account parameters configuration (continued)


Autostart1...Autostartn One Autostart for each application to be automatically startedafter a successful logon to the Connection Manager. Theapplication name includes the complete path, withoutparameters. The order of which application is started first isdetermined by the numeric order in the configuration file.

AutostartParams1 ...AutostartParamsn

One AutostartParams for each parameter required for thecorresponding Autostartn application. Must be present, butblank, if no parameters are required for a given application.The order of which parameters are checked first isdetermined by the numeric order in the configuration file.

BlackHoleDecrement The value used to decrement padded configure requestswhen performing black hole detection. The default value is100 bytes.

BroadcastPgmName This parameter is ignored by the Mobility Client for theNokia 9300/9500 Communicator.

BroadcastPort This parameter is ignored by the Mobility Client for theNokia 9300/9500 Communicator.

Compression When this boolean parameter is set to 1, the Mobility Clientattempts to negotiate a compressed connection with theConnection Manager. The only form of compression that iscurrently supported is BSD LZW compression as provided bythe zlib library. This parameter is useful for low-bandwidthconnections, but is not recommended in cases where thetransmission speed is largely CPU bound (for example, anencrypted broadband connection). The default value is 1.When RequestTransportProfile=1, this parameter is ignored.

ConnectionCount Indicates how many IAPs are associated with the account.

DetectBlackHoles 1 = an advertised speed of network connection is 10 Mbps orgreater, client will pad configuration requests sent to thegateway to the maximum network MTU size in an effort todetect black holes. If the configuration request times out, thenthe retry will be decremented using BlackHoleDecrementbefore being retransmitted. This should be set to 0 in the casewhere the client is using a high speed adapter, but there is avery slow or inefficient intermediate link between the clientand the gateway.

The default value is 1.

DeviceLib This parameter is ignored by the Mobility Client for theNokia 9300/9500 Communicator.

EnablePktJoining This parameter is ignored by the Mobility Client for theNokia 9300/9500 Communicator. WhenRequestTransportProfile = 1, this parameter is ignored.




Encryption This parameter determines the type of encryption that theMobility Client attempts to negotiate with the ConnectionManager. The value should be one of the ConnectionManager encryption minor type numbers. The available typenumbers are:

14 AES 256-bit CBC (cipher block chaining) mode

12 AES 192-bit CBC mode

10 AES 128-bit CBC mode

1 DES CBC

0 No encryptionThe default value is 14.

GatewayIapId This entry is deprecated with Mobility Client version 5.1.1.Applicable only when GatewayNetId is set to Use fixedaccess point, this parameter defines the fixed Internet accesspoint (IAP) to use to connect to the Connection Manager.

GatewayNetId This entry is deprecated with Mobility Client version 5.1.1.Previous versions of the Mobility Client will still have thisentry in the configuration table. Specifies the ConnectionManager network ID as set in Server tab of account settings.If set to Use fixed access point then, GatewayIapId is valid.

GatewaySuppliesDNS When this boolean option is set to 1, DNS informationnegotiated with the Connection Manager is set in the systemenvironment at connect time. The DNS information typicallyincludes primary and secondary DNS servers and the localdomain name. This results in the /etc/resolv.conf file beingbacked up and edited. When the Mobility Client is not shutdown cleanly, /etc/resolv.conf may not be restored properly.If this happens, the original DNS configuration can berestored by entering the /etc directory and renamingresolv.conf.ibmwc<pid> backup to resolv.conf. The defaultvalue is 1.

HeaderReduction When this boolean parameter is set to 1, the Mobility Clientattempts to negotiate IP header reduction with theConnection Manager. IP header reduction can reduce theamount of traffic sent over the network interface, but isgenerally only really useful for low-bandwidth connections.The default value is 0. When RequestTransportProfile = 1,this parameter is ignored.

IAP<number> Indicates the IAPs associated with the account. For exampleif you have two IAPs, one named T-Mobile and the othernamed IBMLeap, you'll have the keys: IAP1=T-Mobile andIAP2=IBMLeap

IAParm<number> Indicates a parameter that corresponds to the IAP named inthe IAP<number> key (IAP1 goes with IAPParm1 etc). IfIAParm<number> is set to hidden, then it indicates that thecorresponding IAP is a WiFi one with a hidden SSID. Anyother value means its SSID is public. This key is ignored fornon-WiFi IAPs.

InterfaceList Reserved. Value is accountname_device.conf.

Chapter 5. Configuring clients with configuration files 25



IPStackMTU The maximum transmission unit for the IP stack interface.The only valid value is 1400 bytes. WhenRequestTransportProfile = 1, this parameter is ignored.

Mod Modification level number of the configuration file.

NetworkAverageBPS Connection throughput in bits per second. If greater than33600, header reduction and other TCP optimizations aredisabled. The default value is 10000000.

OneButtonConnect This parameter is ignored by the Mobility Client for theNokia 9300/9500 Communicator.

OrgUnit The LDAP organizational unit corresponding to theConnection Manager user ID specified by the AccountIdparameter.

Password Port The Connection Manager port that the Mobility Clientconnects to for password changes. The default value is 8888.

PasswordRequired When this boolean parameter is set to 1, a password isrequired by the Connection Manager, if the account does nothave one, then you are prompted for one at logon. When theparameter set to 0, no prompt occurs even if password isblank. Same as Password required field in Logon tab ofaccount settings.

PreferredInterface Reserved. Value is accountname_device.conf.

PrereqAppName1 ...PrereqApplicationName16

Where PrereqAppName1 is the name of the first process thatmust be running before the Mobility Client attempts toconnect, and PrereqAppProcessn is the last process that mustbe running before the Mobility Client attempts to connect.The application name includes the complete path. The orderof which application is checked first is determined by thenumeric order in the configuration file.

PrereqAppProcess1 ...PrereqAppProcess16

One PrereqAppProcess for the process name of eachapplication to check before logon. When a process is running,t values are found by typing ps -e from a shell prompt. Theorder of which process is checked first is determined by thenumeric order in the configuration file.

PrerequisiteDisabled If PrerequisiteDisabled is set to 1, then the applications areignored and no checking is done.

ProxyHttpEnable 1 indicates if an Http proxy is enabled for the Mobility ClientIAP. Default is 0.

ProxyHttpException A comma limited list of IP addresses that should not gothrough the proxy.

ProxyHttpPort Indicates the Http proxy port to use.

ProxyHttpServer Indicates the Http proxy server IP address.

ProxyHttpsEnable 1 indicates if an Https proxy is enabled for the MobilityClient IAP. Default is 0.

ProxyHttpsException A comma limited list of IP addresses that should not gothrough the proxy.

ProxyHttpsPort Indicates the Https proxy port to use.

ProxyHttpsServer Indicates the Https proxy server IP address.




RadiusRetryAttempts This parameter indicates how many times the client will retryRADIUS authentication attempts after timeout failures.Default value is set to 2.

RadiusTimeout This parameter indicates the time in seconds that the clientwaits for a response from a radius authentication request.Default value is set to 15.

Release Release number of the configuration file.

RoamEnable When this boolean option is set to 1, roaming is enabled.When this boolean option is set to 0, roaming is disabled.

RoamInterval Specifies in seconds how often the Mobility Client checks tosee if a higher priority Internet access point is available forroaming.

SecAuthTimeout Indicates how long a secondary authentication dialog isdisplayed without the user entering. If user does not enterwithout this time, the dialog goes away and the connection iscancelled. Default is 60 seconds.

SetDefaultRoute When this boolean option is set to 1, the Mobility Client setsthe default route for IP traffic to flow through the MobilityClient with the exception of any individual routes that arepreviously set in the routing table. The default value is 1.This parameter is ignored by the Nokia 9300/9500.

TcpOptEnable When this boolean option is set to 1, TCP optimization isenabled. The default value is 1. WhenRequestTransportProfile = 1, this parameter is ignored.

TcpOptMaxBurst Maximum number of unacknowledged TCP packetstransmitted. The optimization engine withholds packets tokeep from overloading a directional channel of a wirelessnetwork. The range of values is 5-16, inclusive. The defaultvalue is 50. When RequestTransportProfile = 1, this parameteris ignored.

TcpOptMaxWindowSize Maximum size of the TCP sliding window in bytes. Theoptimization engine adjusts the TCP window on-the-fly as ameans of performing network latency-specific flow control.The range of values is 2048-65535, inclusive. A value of zerodisables this function. The default value is 920. WhenRequestTransportProfile = 1, this parameter is ignored.

TcpOptRetransmitTTL Length of time in milliseconds to suppress TCP retransmitpackets. A value of 0 disables TCP retransmit suppression.The default value is 5000. When RequestTransportProfile = 1,this parameter is ignored.

UseHiddenSSID This entry is deprecated with Mobility Client version 5.1.1.When this boolean option iss set to 0, the Mobility Clientuses the operating system's connection monitor to attempt aconnection. When this boolean option is set to 1, the MobilityClient does not use the operating system's connectionmonitor but instead manually attempts the connection bothat initial logon and at every roaming interval poll.

Version Version number of the configuration file.

VpnNetId This entry is deprecated with Mobility Client version 5.1.1.Previous versions of the Mobility Client will still have thisentry in the configuration table. This entry specifies the VPNnetwork ID as set in VPN tab of account settings.




VpnTimeout Indicates the length of time the connection will bemaintained in an idle state. Values are stored in minutes with0 meaning unlimited.

Table 2. Interface parameters configuration


BindPort Specifies the port number on which theMobility Client listens for data sent from theConnection Manager. This value must matchthe corresponding entry on the ConnectionManager. The default value is 8889.

EncryptedProxyPassword When a connection is established using aproxy server the Mobility Client mustsupply credentials for the proxy server toauthenticate. This field is the password.

GatewayAddress The physical IP address of the ConnectionManager.

GatewayAddressDec The IP address of the Connection Managerin dotted-decimal format. This entry is forinternal use and any value entered isignored.

HttpProxyAddr Specifies either the IP address or the hostname of the authentication proxy server.This parameter is used only if you haveenabled proxy authentication on theConnection Manager.

HttpProxyPort Specifies the port number used tocommunicate with the authentication proxyserver. This parameter is used only if youhave enabled proxy authentication on theConnection Manager.

HttpSendPort Specifies the port number used to send datato the Connection Manager for an HTTPconnection. The default value is 80.

HttpsSendPort Specifies the port number used to send datato the Connection Manager for a secureHTTP connection. The default value is 443.

NetworkMTU This parameter is ignored by the MobilityClient for the Nokia 9300/9500Communicator. WhenRequestTransportProfile = 1, this parameteris ignored.

ProxyUsername When a connection is established using aproxy server the Mobility Client mustsupply credentials for the proxy server toauthenticate. This field is the user name.

SaveProxyPassword When a connection is established using aproxy server the Mobility Client mustsupply credentials for the proxy server toauthenticate. When this boolean option is setto 1, the Mobility Client stores the password.


Table 2. Interface parameters configuration (continued)


SendPort The port used to send data to theConnection Manager. The default value is8889.

SupportedProtocols Specifies the protocols that can be supportedon the Mobility Client. The value for thisparameter can be one or more of thefollowing, in a comma-separated list:

ConnectionlessUse UDP as a protocol to connectto the Connection Manager.

ConnectionOrientedUse HTTP as a protocol to connectto the Connection Manager.

ConnectionOrientedSecureUse HTTPS as a protocol to connectto the Connection Manager.

UseBindPort Specifies whether the Mobility Client listenson a specific port number for data sent fromthe Connection Manager.

UseHttpProxy This parameter is used to enable or disableproxy authentication on the Mobility Clientfor connection-oriented (HTTP or HTTPS)connections. The default value of 0 disablesproxy authentication. If you enter 1 toenable proxy authentication, you must alsoprovide the proxy server address and portnumber. Use the HttpProxyAddr parameterto specify the address and HttpProxyPort forthe port number, as provided by the systemadministrator.

UseUDPEcho This boolean parameter determines whetherthe UDP echo function for the MobilityClient and Connection Manager is usedduring the logon sequence when connectingover UDP. If UseUDPEcho=1, the UDP echofunction uses a test packet to check whetherthe Mobility Client can reach the gatewayand what the Maximum Transmission Unit(MTU) should be. If UseUDPEcho=0, thenthe UDP echo function is not used. Thisparameter is updated after each logon, basedon whether the Connection Manager towhich the Mobility Client is connectedsupports the function.

For migrated connections, the default valueis 0. For new connections, the default valueis 0 if only the UDP protocol is enabled or 1if http, https, or both are selected in additionto the UDP protocol.


Table 3. Global parameters configuration


CableProfileName The transport profile name that is requestedby the client when Mobility Client uses IPpassthrough cable as the physicalconnection. The default name is "NokiaCable".

DefaultAccount The name of the account to be set as thedefault--i.e., the account that is logged intowhen Mobility Client is started from anotherapplication via the IAP (as opposed tologging on via the Mobility Client graphicaluser interface).

GPRSProfileName Transport profile name that is requested bythe client when Mobility Client uses GPRSas the physical connection. The default nameis "Nokia GPRS".

GSMProfileName Transport profile name that is requested bythe client when Mobility Client uses dialupGSM as the physical connection. The defaultname is "Nokia GSM".

LogLevel This text parameter determines the verbosityof the Mobility Client's logging. The higherlogging levels can cause a dramatic decreasein performance and are only useful fordebugging purposes. Most users should usethe default level of error. Multiple valuescan be specified separated by commas.Allowable values are:

error Messages about unexpected eventson which you need to take action

warn Messages about events on whichyou may or may not need to takeaction

log General information messages

debug Data used for problem analysis

all All statements and messages.

none Turns all logging off.

LogMaxSize Specifies the maximum size of the trace filestored in /My Files/MobilityClient/Log/wecmlog.txt. The default valueis 1400 KB.


Table 3. Global parameters configuration (continued)


LogSubSystems This text parameter is used to suppressmessages from some Mobility Clientsubsystems. Generally, the default value ofall should be used. Multiple values can bespecified separated by commas. Allowablevalues are:

main Messages logged in the main clientcode

commonMessages logged in libwgcmn.soand do not have a specific category

ip_stackMessages logged in libipstack.so

compressMessages logged inlibwgcompress.so

hdr_reductMessages logged in libipreduct.so

port Messages logged by the portsubsystem (for example, UDP orTCP)

timer Messages logged from the timesubsystem.

alp Messages logged by the LinkControl Protocol.

all Everything

none Turns all logging off.

PowerTimeout Indicates the length of time theroaming/keep alive feature will bemaintained in an idle state. Values are storedin minutes with 0 meaning unlimited.

VpnTimeout Indicates the length of time the connectionwill be maintained in an idle state. Valuesare stored in minutes with 0 meaningunlimited.

WiFiProfileName The transport profile name that is requestedby the client when Mobility Client uses WiFias the physical connection. The default nameis "Nokia WLAN".



Chapter 6. Accessibility

Keyboard shortcuts are used to trigger an action directly. Keyboard shortcuts areuseful for actions that are performed frequently. There are four keyboard shortcutsin the Mobility Client for the Nokia 9300, 9300i, and 9500 Communicator devices:v To create a new account, use keyboard shortcut Ctrl and N

v To delete an account, use keyboard shortcut Ctrl and D

v To edit an account, use keyboard shortcut Ctrl and E

v To set an account as default, use keyboard shortcut Ctrl and S

33


Chapter 7. Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504–1785USA

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct 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 itbelieves appropriate without incurring any obligation to you.

35

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:v IBM Corporationv P.O. Box 12195v 3039 Cornwallis Roadv Research Triangle Park, NC 27709-2195v USA

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE: This information contains sample application programs insource language, which illustrates programming techniques on various operatingplatforms. You may copy, modify, and distribute these sample programs in anyform without payment to IBM, for the purposes of developing, using, marketing ordistributing application programs conforming to the application programminginterface 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 theseprograms. You may copy, modify, and distribute these sample programs in anyform without payment to IBM for the purposes of developing, using, marketing, ordistributing application programs conforming to IBM's application programminginterfaces.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

The software included herein contains PPP Magic Number routines licensed byCarnegie Mellon University.


The software included herein contains derivatives of the RSA Data Security, Inc.MD5 Message-Digest Algorithm. This technology is licensed from RSA DataSecurity, Inc.

SNMP++ Toolkit aided in the development of the Connection Manager's NetworkManagement Support. SNMP++ Toolkit is copyright© 1999 Hewlett-PackardCompany.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. If these and other IBM trademarked terms are marked on their firstoccurrence in this information with a trademark symbol (&regtm; or &tm;), thesesymbols indicate U.S. registered or common law trademarks owned by IBM at thetime this information was published. Such trademarks may also be registered orcommon law trademarks in other countries. A current list of IBM trademarks isavailable on the Web at Copyright and trademark information(www.ibm.com/legal/copytrade.shtml).

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

Other company, product, or service names might be trademarks or service marksof others.

Chapter 7. Notices 37

http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml


Index

Aabout the guide 1access

understanding network 3account 4, 23

changing password 10creating 3deleting 9disconnecting connection 11duplicating 9editing 9hiding 10setting default account 9showing 10tracing 15working with 9

advanced settings 14applications

check for before connecting 18starting after connection 19

applying maintenance 21auto roaming 7automatically starting applications after

connecting 19

Bbytes received 14bytes sent 14

Cchanging

advanced settings 14IAP priority 21password of account 10

checking that applications are runningbefore connecting 18

clearing logs 16code fixes 21compression 14configuration

exporting 17file 23importing 17using configuration file 23

conn time 14connection

automatically starting applicationsafter 19

checking that applications are runningbefore establishing 18

disconnecting active 11establishing 8information 13parameters 23

Connection Manager, establishing aconnection to 8

connections 5creating accounts 3

cross-network roaming 20

Ddefault account 9deleting accounts 9disconnect if idle for 15disconnecting 11disk space requirements 3download code 21duplicating accounts 9

Eediting an account 9enable HTTP 6enable HTTPS 6enable UDP 5enabling trace logging 15encryption 7, 14exporting configuration 17

Ffiles, moving 16

Ggateway address 13getting help 33getting started 3

Hheader reduction 14help, getting 33hiding the active connection 10HTTP port number 6HTTPS port number 6

Iimporting configuration 17information

connection, viewing 13who should read 1

installing 3Internet access point

changing priority of 21description of 3

Kkeep alive interval 14

Llaunching the Mobility Client 3legal notices 35local address 13logs

clearing 16enabling 15

Mmaintenance, applying 21managing accounts 9modifying advanced settings 14moving files 16

Nnetwork

understanding access 3network connection 13new account 3notices 35

Oonline help 33org. unit 4

Ppassword prompt 4password required 4password, changing 10pkt received 14pkt sent 14prerequisites, software and disk space 3primary DNS 13prioritizing IAPs 21protocol 5, 13proxies 8proxy address 6proxy port number 7

Rremoving the Mobility Client 8requirements, software and disk space 3roaming 20roaming interval 7

Ssecondary DNS 13server IP address 5setting a default account 9settings, advanced 14showing the active connection 10

39

softwaredownload 21requirements 3

stop roaming/keep alive if idle for 15

Ttrace

clearing log file 16enabling 15moving the log file 16using 15

trademarks 37transferring files 16tx port 5

UUDP port number 5uninstalling the Mobility Client 8use proxy server 6user ID 4using advanced settings 14using the Mobility Client 13

Vviewing

advanced settings 14connection information 13

Wwho should read this information 1working with

accounts 9logs 15


��

Printed in USA

Mobility Client User's Guide - IBM - United States · v Install and configure the Mobility Client for Nokia devices v Manage accounts ... When this parameter is set to Yes UDP will

Documents