Lotus Notes Traveler 8.5.

3 Upgrade Pack 1 Beta Drop 2

V ersion 8 Release 5

ii

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Contents
Chapter 1. Overview . . . . . . . . . 1 Chapter 2. New features . . . . . . . . 3 Chapter 3. Downloading the Upgrade Pack Beta . . . . . . . . . . . . . . 9 Chapter 4. Software prerequisites . . . 11 Chapter 5. Upgrading existing Lotus Notes Traveler environments . . . . . 13 Chapter 6. Upgrading the Lotus Domino Server . . . . . . . . . . . 15 Chapter 7. Setting up the Lotus Notes Traveler High Availability Pool . . . . 17
Install Lotus Notes Traveler . . . . . . . . Deploying and configuring the enterprise database Configure Lotus Notes Traveler for enterprise database . . . . . . . . . . . . . . Deploy an IP sprayer or load balancer . . . . Tuning the Lotus Notes Traveler database . . . Enable server to server secure communications (optional) . . . . . . . . . . . . . . . 17 18 . 23 . 25 . 26 . 26

Chapter 8. Upgrading the Lotus Notes Traveler servers in a High Availability pool . . . . . . . . . . . . . . . . 29
Upgrading Lotus Notes Traveler . . . . . . Upgrading the Lotus Notes Traveler database . . Restarting the Lotus Notes Traveler servers in the pool . . . . . . . . . . . . . . . . . 29 . 29 . 30

Chapter 9. Administering Lotus Notes Traveler servers . . . . . . . . . . . 31

Lotus Notes Traveler Client Manager . . . . . . 33

Chapter 10. Managing the Lotus Notes Traveler High Availability pool. . . . . 37 Chapter 11. Installing the Lotus Notes Traveler clients . . . . . . . . . . . 39 Chapter 12. Known restrictions . . . . 41 Chapter 13. Providing feedback or reporting problems . . . . . . . . . 43 Chapter 14. More information . . . . . 45

iii

iv

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 1. Overview
This document highlights the new features and changes that have been made to Lotus Notes Traveler since version 8.5.3.2. IBM Lotus Notes Traveler provides automatic, two-way, over-the-air synchronization capability between Lotus Domino servers and wireless handheld devices, including Android, Apple, Windows Mobile, Nokia S60 Third and Fifth Edition devices and Nokia Symbian ^3 devices. For more information about Lotus Notes Traveler and existing features, see the following 8.5.3 wiki documentation: v Administering v Using v Latest maintenance release notes (8.5.3.2)

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 2. New features

The following new features are included in Lotus Notes Traveler 8.5.3 Upgrade Pack Beta Code Drop 1 and Beta Code Drop 2.

New features for Beta Code Drop 1

The following new features were included in Lotus Notes Traveler 8.5.3 Upgrade Pack Beta Code Drop 1. Android - month view for calendar In addition to the list, day and week views in Lotus Notes Traveler calendar, there is now a month view. Android - Mail and Calendar user interface enhancements for Android Tablets For Android tablet devices running OS 3.x or higher, the user interface for the Lotus Notes Traveler mail and calendar applications have been enhanced. These applications now make use of the larger screen layout sizes to display multiple pieces of data simultaneously. Additional relational database support Support has been introduced for Enterprise Database Servers, DB2 and Microsoft SQL Server, for storing Lotus Notes Traveler Notes Administration data and Device Synchronization data. Support for Enterprise Database Servers has been introduced to enable Lotus Notes Traveler High Availability. It is not required when running Lotus Notes Traveler on a single server. Server High Availability The ability to run multiple Lotus Notes Traveler servers in a service pool has been added, allowing devices to connect to any server in the pool. The following diagram depicts a Highly Available Lotus Notes Traveler configuration:

Requests are received at any Lotus Notes Traveler server and a determination is made whether to service the request locally or to route the

request to another server in the pool. This decision is based on which server is currently monitoring mail for the user and server loads. Lotus Notes Traveler Administration data and Device Synchronization data can be stored in IBM DB2 or Microsoft SQL Server. An enterprise database is not required when running Lotus Notes Traveler on a single server. Web based Administration interface for the Lotus Notes Traveler server You can now administer a stand alone Lotus Notes Traveler server or a Lotus Notes Traveler server HA pool from a browser using the new Lotus Notes Traveler Web-based Administration interface. Access is restricted to users in the Lotus Notes Traveler administrator group. This new web based administration can be used to perform all of the activities previously supported by the Lotus Notes Traveler administration application, including remote wipe, setting up security policies and comprehensive search capabilities. Lotus Notes Traveler client manager New for this release is a subsystem that manages Lotus Notes Traveler clients that are available for download using the Lotus Notes Traveler server. An administrator can now access views in the web based administration application which display exactly which client levels are installed on the Lotus Notes Traveler server and also allows the administrator to assign specific client levels to individual users or groups of users. See Lotus Notes Traveler Client Manager on page 33 for more information. Lotus Notes Traveler configuration settings have been moved to Notes.ini Lotus Notes Traveler configuration settings are now read from the notes.ini. Lotus Notes Traveler specific properties and XML files have been eliminated. When upgrading an existing server, the settings will be migrated. Trace and log settings are now stored in the Lotus Notes Traveler database. In an HA pool, trace settings are shared. Activating tracing on one server affects all servers. High Availability Pool-aware console commands In a Lotus Notes Traveler HA pool, a user/device request may be serviced by any server in the pool. The association of a device to a server can be very transient. To avoid requiring an administrator to understand where a particular device or user is being processed, the management commands have been updated to communicate across servers and execute the request on the appropriate server. In addition, console commands have been added to ease the management and serviceability of a Lotus Notes Traveler HA pool. More information on this is available in Chapter 10, Managing the Lotus Notes Traveler High Availability pool, on page 37. Improved Notes link handling Notes links that are contained in mail messages and viewed on Lotus Notes Traveler clients will now include an additional URL hotspot which points to the web address of the application server. It may be possible to open the linked application using a browser on the mobile device, similar to how applications can be opened using an iNotes application. However, there are a number of restrictions to consider with this functionality: v The link can only be accessed if a connection can be made from the mobile device to the user's Domino mail server and the Domino application server specified in the link. Generally, this requires that the

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

mobile device is using a virtual private network connection (VPN) to tunnel into the company intranet, or the device is connected to a WiFi system which has access to these systems. v The application must be web enabled. This means that the Domino HTTP service must be running on the Domino application server and the application design must have enabled access from web clients. Some applications will look better than others when using a web browser. In particular, Domino applications designed to use Domino xPages design elements will be optimized for web viewing and for viewing from mobile devices. Additional contributors to status condition (red/yellow/green) Additional factors in determining the status condition of a server have been added. New conditions include: v Low disk capacity of the server v Expiration pending of the SSL certificate used to secure Lotus Notes Traveler server to server communication Connection URI The connection URI for Lotus Notes Traveler has been changed from /servlet/traveler to /traveler so as to make it easier for users to enter the link into their mobile devices. In addition, For iOS devices, the "/traveler" is not required. The old connection URI, /servlet/traveler, is still supported for backward compatibility.

New features for Beta Code Drop 2

The following new features are included in Lotus Notes Traveler 8.5.3 Upgrade Pack Beta Code Drop 2. Settings to control sent mail behavior New to the Lotus Notes Traveler 8.5.3 beta is the support for controlling whether or not mail sent using a Lotus Notes Traveler device is saved in the user's Sent mail folder on their Domino mail database. There is now both Administrator and user control for this option. The administrator controls these options by setting NTS_SENDMAIL_SAVE_OPTIONS in notes.ini on the Lotus Notes Traveler servers. The following values for NTS_SENDMAIL_SAVE_OPTIONS are supported: v NTS_SENDMAIL_SAVE_OPTIONS=user Mail sent from a Lotus Notes Traveler client will be saved in the Sent folder based on their Notes and iNotes client mail save preferences. This is the default setting. If NTS_SENDMAIL_SAVE_OPTIONS is not present in notes.ini, this will be the default behavior. v NTS_SENDMAIL_SAVE_OPTIONS=never Mail sent from a Lotus Notes Traveler client is never saved in the Sent folder. v NTS_SENDMAIL_SAVE_OPTIONS=always Mail sent from a Lotus Notes Traveler client is always saved in the Sent folder. v NTS_SENDMAIL_SAVE_OPTIONS=noatt If noatt is specified, then any attachments that are present in the outgoing mail will not be saved in the Sent folder. This option can be specified along with either the option user or always. For example, if you want to specify that sent mail is always saved, but exclude the saving of attachments, then the setting value would be:
Chapter 2. New features

NTS_SENDMAIL_SAVE_OPTIONS=always,noatt

Lotus Domino 8.5.3 Upgrade Pack 1 bundling This version of the Lotus Notes Traveler 8.5.3 beta includes the Lotus Domino 8.5.3 Upgrade Pack 1 installation package. You no longer have to download and install this separately. The Lotus Domino 8.5.3 Upgrade Pack 1 will be automatically installed, if not already installed, during the Lotus Notes Traveler 8.5.3 upgrade pack 1 install. Filter limits In Lotus Notes Traveler 8.5.2.3, administrative settings were added that would enforce a maximum filter window for all users. These were configured using the notes.ini file. The Lotus Notes Traveler administration application now includes the ability to configure these options as part of its default settings. A separate filter limit setting is provided for mail, past events, future events, and notes. Scheduled Sync Settings The Lotus Notes Traveler administration application now includes the ability to configure the scheduled sync settings as part of its default settings. Previously these were configured using the Lotus Notes Traveler clients. The SMS part of the scheduled sync settings continue to be a client only configuration option. Locking of individual default settings The Lotus Notes Traveler administration application default settings configuration now includes the ability to 'Lock' individual settings. This support previously was only available by using Lotus Domino policies. Locking a setting prevents the user from modifying that setting from their device. Enhancements to Server Managed Android Security Settings v Password Type option replaces require alphanumeric Password Type dictates the type of password character enforcement to use. Options are unrestricted, numeric only, alphabetic only, alphanumeric, or complex. Complex password type allows enforcing additional password characteristics, such as the minimum number of letters, minimum number of numerics, and so on. Note: Complex password type requires Android OS 3.0 or higher. v Disable local password storage If this option is selected, the user will be required to enter the domino HTTP password after the phone restarts and whenever the Lotus Notes Traveler service is stopped by the Android OS. Choose this option only if you require the tightest security on the phone, as it will cause the user to enter the password more frequently. v Prohibit copy to clipboard If this option is selected, users will not be allowed to copy data to their device clipboard. v Prohibit export of attachments to file system If this option is selected, users will not be allowed to export attachments. v Prohibit camera If this option is selected, the use of the device's camera will not be allowed. Note: Requires Android OS 4.0 or higher.

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

v Require Application password Require Application password option will cause the Traveler Android client to prompt the user for their domino http password after the specified amount of time not accessing the Traveler Application. Viewing mail and calendar counts as activity. View and scrolling widgets and contacts does not. Support for Lotus Domino 8.5.3, fixpack 1 This beta release of the Lotus Notes Traveler 8.5.3 Upgrade Pack 1 supports being installed on Lotus Domino 8.5.3, fixpack 1. Web based administration look and feel The Lotus Notes Traveler Web Administration interface has been updated to support the OneUI 2.1 theme. Note: Lotus Notes Traveler 8.5.3 Upgrade Pack beta drivers will include all APARs that have been reported on previous releases.

Chapter 2. New features

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 3. Downloading the Upgrade Pack Beta

To download the Upgrade Pack Beta, following the procedure in this section. 1. Go to the download site and login with your IBM ID. Note: If you don't have an IBM user ID, then click the Register here link to create one. You will receive an e-mail informing you that your new IBM user ID has been created. You can then return to the beta download site and sign in. Please answer a few questions about your company and yourself, and whether you would like to be contacted by IBM. Enter the new 10-character access key, provided to you by Jan Kenney (jank@us.ibm.com). Review the beta license agreement. If you agree with its terms, check I agree. Click I confirm at the bottom of the page to display the download page. Select and download the Beta files of interest to you. v For Windows installations: traveler853UP1_HA_win_cd1.zip. v For Linux installations: traveler853UP1_HA_linux_cd1.tar. Scroll down and once again check I agree to the license terms.

2. 3. 4. 5. 6.

7.

8. Please let us know what you think of this beta release by providing feedback in the Design Partner Forum. Contact Jan Kenney (jank@us.ibm.com) if you have forum access issues.

10

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 4. Software prerequisites

The Lotus Notes Traveler 8.5.3 Upgrade Pack Beta has the following the software requirements for use.

Lotus Domino 8.5.3 Server with Upgrade Pack 1

Lotus Notes Traveler 8.5.3 Upgrade Pack Beta Code Drop 2 must be installed on a Domino 8.5.3 server with Upgrade Pack 1 deployed. If the Domino Upgrade Pack 1 is not found on the system it will be installed by Lotus Notes Traveler. Running on Domino 8.5.4 Beta Server is not supported. Only 64-bit Operating Systems will be officially supported by Lotus Notes Traveler running in High Availability configurations. Windows 32-bit OS and Linux 32-bit OS will continue to be supported in stand-alone configurations only. Currently, there is only a 32-bit version of Domino for Lotus Notes Traveler supported Linux versions, which means even though Domino will be 32-bit, the Linux Operating System must be 64-bit. See the IBM Lotus Notes Traveler 8.5.3 System requirements document for a list of operating systems supported by the Lotus Notes Traveler server and for additional device and server requirements. Lotus Notes Traveler supports remote Domino mail servers back to version 7.0.2, running on any operating system supported by the Domino server. The Lotus Notes Traveler 8.5.3 Upgrade Pack Beta Code Drop 1 is English-only.

Enterprise database server

Lotus Notes Traveler does not require an additional database server for standalone mode. However, to enable a highly available configuration, Lotus Notes Traveler 8.5.3 Upgrade Pack requires an enterprise database server. One of the following database server software packages is required: v v v v DB2 Enterprise Server Edition v9.7.0.5 and higher DB2 Workgroup Server Edition v9.7.0.5 and higher Microsoft SQL Server Enterprise Edition 2008 and higher fixpacks Microsoft SQL Server Enterprise Edition 2008 R2 and higher fixpacks

Note: The target platform should be a 64-bit platform. It is not required that the DB server platform match the Lotus Notes Traveler server platform. Note: A 90 day trial version of DB2 9.7 is available from IBM at this location. Select DB2 Multiplatform and then select which version of DB2 you desire (Enterprise or Workgroup). The Workgroup edition should be sufficient for the Lotus Notes Traveler 8.5.3 Upgrade Pack Beta.

11

12

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 5. Upgrading existing Lotus Notes Traveler environments

Beta code drop 2 of the Lotus Notes Traveler High Availability release does not support upgrading from prior releases. Beta code drop 2 supports being installed on a previous Lotus Notes Traveler 8.5.3 Upgrade Pack beta release. If you are installing on a server with a previous release of Lotus Notes Traveler, you should uninstall that version first. It is recommended that the code only be installed on test servers that do not have a production role in your organization. Later code drop releases of this Beta will support transformation from previous Lotus Notes Traveler releases. Transformation will be supported for stand-alone instances of Lotus Notes Traveler. In addition, the capability will be included to upgrade one or more stand-alone Lotus Notes Traveler servers to an HA environment using a remote database connection. At product delivery, Lotus Notes Traveler 8.5.3 Upgrade Pack will support upgrading from previous Lotus Notes Traveler releases. In addition, the capability will be included to transform one or more stand-alone Lotus Notes Traveler servers into a high availability pool.

13

14

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 6. Upgrading the Lotus Domino Server

The Lotus Notes Traveler 8.5.3 Upgrade Pack 1 server runs on Lotus Domino 8.5.3 with Upgrade Pack 1. If the Domino Upgrade pack is not detected on the system it will be installed by Lotus Notes Traveler. Use the following instructions if you prefer to install the Domino Upgrade Pack manually: v Getting the upgrade pack from Passport Advantage v Installing the upgrade pack on a Domino server

Notes
v When searching on Passport Advantage, use the following part number: CI5HUEN. v The OpenNTF version of the XPages Extension Library is not supported and should be uninstalled before installing Lotus Domino 8.5.3 Upgrade Pack 1. v For additional information on the Domino 8.5.3 Upgrade Pack 1, please see the product documentation.

15

16

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 7. Setting up the Lotus Notes Traveler High Availability Pool

This section contains information, procedures and requirements for setting up the Lotus Notes Traveler High Availability (HA) Pool. If you have already set up a Lotus Notes Traveler High Availability pool using a previous beta release, refer to Chapter 8, Upgrading the Lotus Notes Traveler servers in a High Availability pool, on page 29. The recommended minimum configuration for a Lotus Notes Traveler HA Pool is as follows: v Two Domino 8.5.3 Upgrade Pack 1 Servers running Lotus Notes Traveler v One DB2 Server or Microsoft SQL Server (two database servers, if you want high availability of the Lotus Notes Traveler data) v One server running the IP sprayer/load balancer Condensing the setup to fewer servers increases the amount of functionality that is a single point of failure as well as possibly creating performance bottlenecks. Setting up a Lotus Notes Traveler High availability pool will consist of the following steps: 1. Deploying the enterprise database server and creating the Lotus Notes Traveler database (on a separate server from the Lotus Notes Traveler servers). 2. Installing Lotus Notes Traveler. 3. Configuring and validating the functionality of Lotus Notes Traveler with the enterprise database server. 4. Deploying and validating the functionality of a load balancer (you may already have one that can be used). 5. Tuning the DB2 database. 6. Preparing for common configuration (optional). 7. Enabling server to server secure communications (optional). Note: Repeat steps two and three for each additional Lotus Notes Traveler Server to be deployed in the pool.

Install Lotus Notes Traveler

The Lotus Notes Traveler High Availability service is installed on a Lotus Domino 8.5.3 server with Upgrade Pack 1. If Upgrade Pack 1 is not detected on the system it will be installed by Lotus Notes Traveler. The initial installation and configuration choices are similar to those asked for version 8.5.3. For additional server installation details, see Installing the Lotus Notes Traveler Server. You should upgrade the server to Lotus Domino 8.5.3 Upgrade Pack 1 prior to deploying Lotus Notes Traveler.

17

You will not be prompted for any database configuration information during the installation process. Configuring the database is a post-installation step. If you already know the external URL of the sprayer, you can set this value at installation time. Each Domino Server running Lotus Notes Traveler should be registered for the same domain. Once the Lotus Notes Traveler installation is complete, restart the Domino server and verify that the Domino 8.5.3 Upgrade Pack is also installed and working with Lotus Notes Traveler. On the Domino Console, enter the following command:
tell http osgi diag com.lotus.sync.traveler.admin Look for "No unresolved constraints." message.

Example:
> tell http osgi diag com.lotus.sync.traveler.admin [0F24:0002-0F60] 03/13/2012 09:23:28 AM update@../../../data/domino/workspace/ applications/eclipse/plugins/com.lotus.sync.traveler.admin.jar [114] [0F24:0002-0F60] 03/13/2012 09:23:28 AM No unresolved constraints.

Deploying and configuring the enterprise database

This section contains instructions for deploying and configuring both DB2 and SQL enterprise databases for Lotus Notes Traveler.

Install the Server

Although it is possible to deploy the server together with Domino and Lotus Notes Traveler, it is not recommended. DB2 or SQL should be deployed on its own server, and the server should be a 64-bit system. Note: Recommendations on specifications for the server (memory, raid configuration, and so on) are currently being developed. Note: After deploying a DB2 server, you should apply the latest DB2 fixpack (minimally fixpack 5). There are two options for configuring your enterprise database. The first option is the 'autoschema' method. For this option you will create a Database and a User, and then Lotus Notes Traveler will create, alter, and manage the Enterprise Database Schema. This can be considered the 'hands-off' approach. The second option is to manually create and handle the Database Schema using the supplied DDLs. This second option allows you to specifically customize the database to your needs or requirements. v Configure DB2 for Lotus Notes Traveler using the DB2 Configuration Wizard on page 19 v Configure DB2 for Lotus Notes Traveler using DDL on page 20 v Configure SQL for Lotus Notes Traveler using the SQL Server Management Studio on page 21 v Configure SQL for Lotus Notes Traveler using DDL on page 23

18

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Configure DB2 for Lotus Notes Traveler using the DB2 Configuration Wizard
To configure DB2 using the DB2 Configuration Wizard, perform the following procedure: 1. Launch the DB2 Control Center by selecting Create Database > Standard.

2. In the Create Database Wizard, select the defaults for each attribute unless otherwise noted. Fill in the Database name. The example used here is for reference only, any name can be used.

3. Set the code page to UTF-8.

Chapter 7. Setting up the Lotus Notes Traveler High Availability Pool

19

4. Click through the rest of the wizard and select Finish to create the Lotus Notes Traveler database. Note: After Lotus Notes Traveler is configured for DB2, it will automatically create the required database schema, tables, and so on.

Configure DB2 for Lotus Notes Traveler using DDL

To configure DB2 using DDL, perform the following procedure: 1. Unzip the Lotus Notes Traveler DDL in <domino install data dir>\traveler\cfg\db\TravelerSQL.zip or TravelerSQL.tar.gz to the directory <sqldir> cd <sqldir>/DB2. 2. Make any updates necessary, for example the location of files, sizes of the database, schema names, and so on. 3. For Windows, create the DB Login user, Lotus Notes Traveler DB and DB objects, using the following command:
db2cmd -c -w -i db2 -tvf createDb.sql -o -r createDb.out

For Linux:
su - db2inst1 db2 -tvf createDb.sql -o -r createDb.out

4. For Windows, grant the necessary permissions to the DB Login user to the Lotus Notes Traveler DB, using the following command.
db2cmd -c -w -i db2 -tvf appGrants.sql -o -r appGrant.out

For Linux:
db2 -tvf appGrants.sql -o -r appGrant.out

5. Create an Operating System User that matches the DB2 user specified in the appGrants.sql file. 6. Update the notes.ini to add the following property to tell the system the Lotus Notes Traveler DB and its objects were created:

20

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

NTS_AUTO_DBSCHEMA=false

If you changed the schema name in the DDL files, you must set the following property in the notes.ini, where <schemaname> is the schema name used in the DDL files:
NTS_DB2_SCHEMA=<schemaname>

Configure SQL for Lotus Notes Traveler using the SQL Server Management Studio
To configure SQL for Lotus Notes Traveler using the SQL Server Management Studio, perform the following procedure: 1. Launch the SQL Server Management Studio and log in as an Admin user. 2. Create a database user by right clicking Login under Security. Then select New Login.

3. Enter a name and password for the user, set the password policies to your company's requirements, and keep the remaining settings as defaults. 4. Click OK to create the profile. 5. Create the database using the database wizard. Right click Database, then select New Database.

Chapter 7. Setting up the Lotus Notes Traveler High Availability Pool

21

6. Fill in the information in the wizard, selecting the defaults unless otherwise instructed. Enter a database name, then enter the new user name you created above as the owner of the database.

22

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

7. Click OK to create the database with these settings.

Configure SQL for Lotus Notes Traveler using DDL

To configure SQL using DDL, perform the following procedure: 1. Unzip the Lotus Notes Traveler DDL in <domino install data dir>\traveler\cfg\db\TravelerSQL.zip or TravelerSQL.tar.gz to the directory <sqldir> cd <sqldir>/SQLSERVER. 2. Make any updates necessary, for example the location of files, sizes of the database, schema names, and so on. 3. Create the DB Login user, Lotus Notes Traveler DB and DB objects.
sqlcmd -U <admin_user> -P <admin_password> -i "createDb.sql" -v filepath=<path_to_db> password=<password to use for traveler d db user>

4. Grant the necessary permissions to the DB Login user to the Lotus Notes Traveler DB.
sqlcmd -U <admin_user> -P <admin_password> -i "appGrant.sql"

5. Update the notes.ini to add the following property to tell the system the Lotus Notes Traveler DB and its objects were created:
NTS_AUTO_DBSCHEMA=false

Configure Lotus Notes Traveler for enterprise database

This section describes how to configure the Lotus Notes Traveler server to use the database created in the previous steps.

Chapter 7. Setting up the Lotus Notes Traveler High Availability Pool

23

Perform the following procedure for each Lotus Notes Traveler server that is part of the pool: 1. Ensure that the Lotus Notes Traveler DB is created and available. 2. For DB2 servers only: Locate the db2jcc4.jar on the DB2 Server (<db2_install_dir>\sqllib\java\). Copy the db2jcc4.jar from the DB2 server to the <domino>\traveler\lib directory. 3. For SQL servers only: Copy sqljdbc4.jar to the <domino>\traveler\lib directory. Download the Microsoft SQL Server JDBC Driver 3.0 from this site. 4. Open a command prompt. 5. Change directory to <domino data>\traveler\util. 6. For DB2 servers only: Run travelerutil to configure Lotus Notes Traveler in the following format:
travelerutil db set url=jdbc:db2://<db2server hostname>:<db port>/ <traveler db name> user=<db2 admin id> pw=<db2 password>

For example:
travelerutil db set url=jdbc:db2://dbserver.yourco.com:50000/traveler user=db2admin pw=passw0rd

Upon execution, the utility validates the DB2 information and configures Lotus Notes Traveler to use the DB2 instance instead of the default derby database. The credentials are encrypted and stored in the LotusTraveler.nsf. If you do not specify any parameters for travelerutil db set, it will prompt you for all required parameters (the DB2 URL, the database admin id, and the database admin password). To validate what you just configured, use the travelerutil db show command (this will not show the password) or the travelerutil db check command to verify that the configuration allows database connections to be made. You will use the same utility to update the password in the event that becomes necessary. 7. For SQL servers running Windows: Run travelerutil to configure Lotus Notes Traveler in the following format:
travelerUtil db set url=jdbc:sqlserver://<sqlserver hostname>:<db port>; databasename=<traveler db name> user=<sqlserver user id> pw=<sqlserver user password>

For example:
travelerUtil db set url=jdbc:sqlserver://dbserver.yourco.com:1433;databasename=TRAVELER user=LNTUSER pw=passw0rd

8. For SQL servers running Linux: Run ./travelerUtil in the following format:
travelerUtil db set user=<sqlserver user id> pw=<sqlserver user password>

For example:
./travelerUtil db set user=LNTUSER pw=passw0rd

You will be prompted for your database URL. The following example shows a sample database URL for an SQL server:
jdbc:sqlserver://dbserver.yourco.com:1433;databasename=TRAVELER

Upon execution of steps 7 or 8, the utility validates the SQL Server DB information and configures Lotus Notes Traveler to use the SQL Server DB instance instead of the default derby database. The credentials are encrypted and stored in the LotusTraveler.nsf. If you do not specify any parameters for travelerutil db set, it will prompt you for all required parameters (the database URL, the database admin id, and the database admin password).

24

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

To validate what you just configured, use the travelerutil db show command (this will not show the password) or the travelerutil db check command to verify that the configuration allows database connections to be made. You will use the same utility to update the password in the event it becomes necessary. 9. Configure Lotus Notes Traveler to skip creating the database schema (optional). If you created the Lotus Notes Traveler database using the database wizard, you can skip this step. If you configured the Lotus Notes Traveler database using the DDL, the schema and database objects are already created. Add the following entry to the notes.ini to tell Lotus Notes Traveler to skip the schema creation on startup:
NTS_AUTO_SCHEMA=false

10. Start Lotus Notes Traveler. Unless configured otherwise, Lotus Notes Traveler will detect that no schema has been created and will automatically create it. At this point, Lotus Notes Traveler is ready to use with the server. Note: In this initial startup process, Lotus Notes Traveler will migrate existing data. For beta code drop 1, the migration functionality is not supported. Migration will be supported in a future code drop.

Deploy an IP sprayer or load balancer

To support a pool of Lotus Notes Traveler Servers, you will need to provide a single URL entry point for the devices. This can be accomplished by employing an IP sprayer or load balancer, allowing a device to connect to one URL and have the request routed to any of the Lotus Notes Traveler servers in the pool. Lotus Notes Traveler has minimal requirements for an IP sprayer: v Provides a single URL entry point and supports the proxying of device requests to two or more Lotus Notes Traveler servers v Round robin load balancing. This will spread the load evenly across the Domino HTTP tasks as desired. Lotus Notes Traveler provides its own load balancing based on server load characteristics after it has received the requests from Domino HTTP . v Ability to detect when a Lotus Notes Traveler server is no longer responding (to allow for failover). Initial testing has used the IP sprayer capabilities of the WebSphere Edge Server. It is not required that you utilize the WebSphere Edge Server in your configuration. After configuring an IP Sprayer, you must update the Lotus Notes Traveler external URL to point the devices to the URL of the sprayer. Setting the external URL for Lotus Notes Traveler is documented in the Lotus Notes Traveler 8.5.3 wiki, in the section Setting the external server URL. The external URL setting must be updated on each Lotus Notes Traveler server in the high availability pool. Note: For this Beta release, the primary link for Lotus Notes Traveler has been changed from /servlet/traveler (in the documentation linked above) to /traveler, so as to make it easier for users to enter the link into their mobile devices.
Chapter 7. Setting up the Lotus Notes Traveler High Availability Pool

25

Tuning the Lotus Notes Traveler database

Work is ongoing to determine guidance for sizings and tuning of Lotus Notes Traveler and the enterprise database.

Tuning the DB2 database

If either the Auto-Schema method or the DDL Method is used to create the database, the default settings for the MaxAppls and BufferPool sizes are set to Automatically Tune. This allows the settings to increase as required by the Lotus Notes Traveler System. Additionally, AUTO_RUNSTAT and AUTO_REORG are enabled by default. All of these automatic settings should handle any type of tuning/maintenance required on the database systems during the Beta timeframe. If, however, you choose not to use these automatic settings, keep the aforementioned properties in mind as values you may need to check and manually tune.

Tuning the Microsoft SQL Server database

Tuning information is not available with this Beta release.

Enable server to server secure communications (optional)

By default, Lotus Notes Traveler uses regular TCP sockets for communication between the Lotus Notes Traveler server and the HTTP server, as well as for communications between the Lotus Notes Traveler servers within an HA pool. It may be desirable to use secure sockets for this communication if the networking between the Lotus Notes Traveler servers is not isolated or secure. To enable the use of SSL sockets between the Lotus Notes Traveler servers, the following steps can be used: 1. To generate a self-signed certificate with an expiration date far in the future, use the following example:
<domino>\jvm\bin\keytool -genkey -v -alias "Traveler" -validity 9999 -keystore traveler.jks -storepass <password> -keypass <password>

It is recommended you use the same password for the storepass and the keypass. If the password parameters are omitted, the keytool will prompt for them. 2. Copy the traveler.jks that was just created to each server. A suggested location is <domino data>\traveler\cfg. It is important for the servers to use the same certificate file, so the keytool command should not be run on each server. 3. Open a command prompt. 4. Change the directory to <domino data>\traveler\util. 5. Run travelerutil to configure Lotus Notes Traveler to use SSL:
travelerutil ssl set keystore=<domino data>\traveler\cfg\traveler.jks key=<password>

Specify the same password that was used for the storepass and keypass parameters with the keytool command. The next time the Lotus Notes Traveler server starts, it will use SSL sockets to communicate with other Lotus Notes Traveler servers.

26

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Repeat these steps for each Lotus Notes Traveler server in the pool. All the Lotus Notes Traveler servers in the pool must be configured the same way; otherwise, they will not be able to communicate with each other.

Chapter 7. Setting up the Lotus Notes Traveler High Availability Pool

27

28

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 8. Upgrading the Lotus Notes Traveler servers in a High Availability pool
You will need to upgrade Lotus Notes Traveler and the Lotus Notes Traveler database. If you have already set up a Lotus Notes Traveler High Availability pool with a prior beta release, you can choose to upgrade your existing servers with this beta release. Refer to the following topics for information on how to upgrade your servers and the database. If you are setting up a new pool, see Chapter 7, Setting up the Lotus Notes Traveler High Availability Pool, on page 17.

Upgrading Lotus Notes Traveler

You must first upgrade existing Lotus Notes Traveler 8.5.3 Upgrade Pack 1 servers in a high availability pool to the current beta release. To do so, perform the following steps: 1. Stop all Lotus Notes Traveler servers in the pool. For this beta release, it is necessary to stop all servers in the pool before starting the upgrade. For future upgrades, a rolling upgrade will be supported where each server can be shutdown and upgraded in turn. 2. Run the Lotus Notes Traveler server installation program on each server in the pool. It is not necessary to uninstall the existing server version or to drop the database tables. Existing data will be preserved.

Upgrading the Lotus Notes Traveler database

Since the Beta 1 release of Lotus Notes Traveler 8.5.3 Upgrade Pack 1, there have been data schema changes. When deploying the Beta 2 release, it is not necessary to re-create the database. The existing database can be upgraded, preserving the existing data. There are two methodologies for upgrading the database: v Allow Lotus Notes Traveler server to automatically upgrade the schema. This is the default method. When the first upgraded server starts, it will detect that the database schema is downlevel and will perform the upgrade automatically. Do not use this method if used the DDL method to create the initial database. The auto upgrade process will not run if the property NTS_AUTO_DBSCHEMA=false is set in the notes.ini. If using this methodology, proceed to the next section (Restarting the Lotus Notes Traveler servers in the pool ). v Use the supplied DDL to upgrade the Lotus Notes Traveler database. You will need to use this method if you originally used the DDL to create the Lotus Notes Traveler Database. NTS_AUTO_DBSCHEMA=false must be set in the notes.ini if using the DDL method.

29

Upgrade DB2 database for Lotus Notes Traveler using DDL

To upgrade the Lotus Notes Traveler database on DB2 using DDL, perform the following procedure: 1. Unzip the Lotus Notes Traveler DDL in <domino install data dir>\traveler\cfg\db\TravelerSQL.zip or TravelerSQL.tar.gz to the directory <sqldir>. 2. Locate the file fixup853UP1Beta2.sql in <sqldir>/DB2. 3. Make any necessary updates, such as the database name or the schema names. Any changes should match what was used when the original database was created. 4. For Windows, update the schema, using the following command:
db2cmd -c -w -i db2 -tvf fixup853UP1Beta2.sql -o -r updateDb.out

For Linux:
su - db2inst1 db2 -tvf fixup853UP1Beta2.sql -o -r updateDb.out

Upgrade Microsoft SQL Server database for Lotus Notes Traveler using DDL
To upgrade the Lotus Notes Traveler database on Microsof SQL Server using DDL, perform the following procedure: 1. Unzip the Lotus Notes Traveler DDL in <domino install data dir>\traveler\cfg\db\TravelerSQL.zip or TravelerSQL.tar.gz to the directory <sqldir>. 2. Locate the file fixup853UP1Beta2.sql in <sqldir>\SQLSERVER. 3. Make any necessary updates, such as the database name or the schema names. Any changes should match what was used when the original database was created. 4. Update the schema using the following command:
sqlcmd -U <admin_user> -P <admin_password> -i "createDb.sql" -v password=<password to use for traveler d db user> filepath=<path_to_db>

Restarting the Lotus Notes Traveler servers in the pool

Finally, restart all Lotus Notes Traveler servers in the HA pool. To do so, perform the following procedure: 1. Start one of the Lotus Notes Traveler servers in the pool. Unless you manually upgraded the schema previously, the first server started will handle the updating of the Lotus Notes Traveler Database. In addition, the first server started will push any updated Lotus Notes Traveler client packages to the database. On an upgrade, Lotus Notes Traveler client install packages are auto-promoted. Once the initial server has started, it can then receive device requests. 2. Start the remaining servers in the pool.

30

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 9. Administering Lotus Notes Traveler servers

In this Beta release of the IBM Lotus Notes Traveler 8.5.3 Upgrade Pack, there are several changes in the Lotus Notes Traveler administration database application, accessed using the Domino Administrator client 8.5.x. A significant change from prior releases is that the administration data for Lotus Notes Traveler, when configured for High Availability, is no longer stored in the LotusTraveler.nsf. Instead, this data is now stored in the enterprise database for Lotus Notes Traveler. This change allows the administrator to administer the entire pool of Lotus Notes Traveler servers, devices, and users from one administration interface. In previous releases, you were able to perform the following tasks using the Lotus Notes Traveler database application: v Assigning device preferences and security settings to devices v Device Security actions, such as remote wipe of devices (full and application data) v Controlling access to Lotus Notes Traveler v Viewing user and device Information With this beta release, you can perform some of the following tasks using the new Web-based Admin interface in both stand alone mode and in HA-mode: v Viewing server (pool) information v Administering Lotus Notes Traveler Client Installation Packages When configured for HA, the Domino Administrator client cannot be used to administer the Lotus Notes Traveler Servers. In this release, in order to issue any actions (such as Deny or Wipe) or edit the DefaultSettings, the user must be in the ACL of the LotusTraveler.nsf and have the Administrator role enabled. Any user in the ACL without this role will not be able to issue actions or edit the device DefaultSettings. When using the Web-based administration (XPages) version of LotusTraveler.nsf, the user does not need to be a Domino administrator or have the ability to issue remote console commands. The ACL for the user should be at least READER, and the Administrator role either enabled or not enabled.

Lotus Notes Traveler administration database client view

In an HA configuration, when you open the Lotus Notes Traveler administration database views (Devices, Users, and Device Security) from the Domino Administration Client, you will be notified that the selected view is obsolete, and that the Lotus Notes Traveler administration XPages application can be accessed from your browser using a link. Deleting admin records directly from the enterprise database (HA mode) or LotusTraveler.nsf (standalone mode) is not supported. The Lotus Notes Traveler console commands should be used when removing records. In stand-alone mode, the Lotus Notes Traveler administration database client can still be used to administer the Lotus Notes Traveler Server. However, new

31

administration functions, like Administering Lotus Notes Traveler Client Installation Packages, can only be accessed using the Lotus Notes Traveler Web-based administration. A new requirement for this release is that the administrator must have the Administrator role in the ACL enabled. The requirement still exists that when using the database client view to perform actions and edit default settings, the administrator should have Manager access. For viewing information only, Reader access is sufficient.

Lotus Notes Traveler Web-based administration

As mentioned in the introduction section, the new Web-based administration interface has been introduced with this release. You can access the new administration interface from your browser using the following link:
http(s)://<traveler_server>/LotusTraveler.nsf

You will be required to authenticate before allowing access to the administration site. There are two primary areas of the administration site: v Administration v Product Documentation.

Browser support
The following browsers are supported: v Firefox 3.6.x or higher v Safari 4/Safari 5 v Chrome 5 or higher v Microsoft Internet Explorer 7 or higher Note: Internet Explorer 6 is not supported. Note: Mobile device browsers are not supported. Note: For Internet Explorer, Active Scripting must be enabled.

Administration tab
Administration has two main panels: v Navigation bar v Main content area The navigation bar allows you switch between views, and the main content area displays content for the selected resource in the navigation bar. There are six views (five in stand-alone) an administrator can access. Use the steps below to access user and device information: 1. Device Security - displays device information specific to device wipe support and Lotus Notes Traveler security policy settings. At the top of the list there is a tool bar that allows an administrator to take action on the selected devices. Also, double clicking the selected row displays detailed information about that device. The action tool bar has the following buttons: v Deny Access: The user can select a device from the list to deny access by selecting the row of the desired device (the row is highlighted). Pressing the

32

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

2.

3. 4. 5.

6.

Deny Access button from the action bar displays a dialog to confirm whether the user wants to deny access to the selected device or not. Clicking Yes executes the requested action to deny access for that device. The page will auto refresh with the updates. The Access field for the corresponding device gets updated with the value "Deny." v Wipe Device: The user can select a device to wipe by selecting the row of the desired device (the row is highlighted). Pressing the Wipe Device button displays a dialog from which you can select the wipe options. More than one option can be selected at a time. You can cancel from this dialog, and selecting OK will cause the application to execute the action with the requested wipe options. The page will be auto refreshed with the updates. v Clear Wipe/Allow Access: Works in the same manner as the Wipe Device/Deny Access buttons above except no additional input is required from the user. This action clears any previous wipe and deny request. v Change Approval: This action allows the Domino admin to change device access permission. Pressing the Change Approval button displays a dialog from which you can select Approve or Deny options. Selecting Allow and pressing OK displays a confirm request message that allows the administrator to select Yes to continue or No to cancel. Selecting Yes causes the page to execute the request to approve or deny access for that device and user. v Update SMS Address: This action allows the Domino administrator to configure an SMS Address specifically for use on a Wipe Request. Selecting this action button displays a message box in which the user can enter an SMS address. Leaving the SMS address value empty in the message box clears any existing SMS address. Device Settings - a built-in set of default device preferences and security settings that an administrator can modify for use when a device initially registers with Lotus Notes Traveler. Device preferences control how and what data is synced with devices, and security settings define the security policy for devices. Devices - displays a list of all devices on the server(s). Double clicking on the selected row displays detailed information about that device. Users Displays a list of all registered users on all servers. Servers - Displays a list of servers in the HA environment. HA only, not available in Standalone install. For more information, refer to Chapter 10, Managing the Lotus Notes Traveler High Availability pool, on page 37. Client Software - Manages Lotus Notes Traveler Client Installation packages.

Product Documentation tab

It provides brief information about the content on the page and points to the product related site where you can get more information. For this beta release, the product information is for the Lotus Notes Traveler 8.5.3 release.

Lotus Notes Traveler Client Manager

New for this release is a subsystem that manages Lotus Notes Traveler clients that are available for download using the Lotus Notes Traveler server. This feature is available in either the stand-alone Lotus Notes Traveler server scenario or in a high availability configuration using a remote database. Note: The Domino Administration Client cannot be used to manage Lotus Notes Traveler Client Installation packages.
Chapter 9. Administering Lotus Notes Traveler servers

33

Lotus Notes Traveler client images are now stored in the central Lotus Notes Traveler database. In a high availability configuration, where multiple Lotus Notes Traveler servers are connected to a remote database, this allows all of the Lotus Notes Traveler servers connected to the database to immediately become aware of any new Lotus Notes Traveler clients that have been installed on any of the servers. When a Lotus Notes Traveler server is installed using the normal full package installation program, it automatically lays down a copy of all Lotus Notes Traveler clients that ship with the release. This includes Android .apk files, Windows Mobile .cab files, and Nokia .sisx files. While the client files are stored in the database, they are stored locally on each machine under <domino data>/domino/html/travelerclients/ so that they can be downloaded using regular HTTP file requests. If a change is made in the database, the local file system will be updated with that same change. In most cases, the client version installed by the full package installer is made the default client version when the server restarts. However, if this is an upgrade scenario for a server in a Lotus Notes Traveler service pool, then the client will only become the default once all servers in the Lotus Notes Traveler pool have the same three digit version. This rule is in place so that new feature clients do not inadvertently start communicating with an older server that does not support the new features. For example, if a pool of Lotus Notes Traveler servers all running version 8.5.3.100 is installed, and a new server fixpack is made available with version number 8.5.3.101, then this version is installed on any server within the Lotus Notes Traveler pool, and the clients that were shipped, such as 8.5.3.101 version clients, will automatically be made available to all users that are currently receiving the latest default client. This is because the client version (8.5.3) matches the server version to the first 3 digits. However, if a new feature release ships and one of the servers in the Lotus Notes Traveler pool is installed with version 8.5.4, the client will not automatically be pushed down to devices using the latest default version because there are other Lotus Notes Traveler servers in the Lotus Notes Traveler pool that cannot support this level yet. In this case, once the remaining Lotus Notes Traveler servers are upgraded to version 8.5.4, the Lotus Notes Traveler 8.5.4 clients will automatically be promoted to the default level. An administrator can use the new, web-based administration client to view which client levels have been installed on the Lotus Notes Traveler server or server pool. To view the client levels, open the administration web page and select the Clients view.
Table 1. Client Manager view descriptions Column Client Description Description of the client type. This will always include the OS type, such as Windows Mobile, Android, or Nokia. All clients will have a Sync type, which represents the main client program that contains the synchronization capability and security enforcement code. Some clients will have an "Installer" option which is the Lotus Installer client used to facilitate installation of the sync client and keep the client up to date.

34

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Table 1. Client Manager view descriptions (continued) Column Build Level Description The four digit version string and a build level which represents the build date for this version. A list of users or groups that have been explicitly assigned to use this specific client version. Values include Yes, No or Pending. Yes - this client is the default for its type and is automatically assigned to any user requesting it that does not already have an explicit client assignment. No - this is not the default client, though it may still be assigned explicitly to individual users or groups of users. It could also be deleted if needed. Pending - this client will become the default client level once all servers in the Lotus Notes Traveler pool are upgraded to a level that can support this client version.

Users

Default

In a later release, it will be possible for IBM support to deliver an updated version of a specific Lotus Notes Traveler client that contains either new features or bug fixes. The administrator will use an update installation program to apply the new client to any server in the Lotus Notes Traveler server pool. All servers in the Lotus Notes Traveler server pool will be aware of the new client, and the administrator can use the new web based administration program to assign the updated client level to either specific users or groups of users, or they could make this the default client of its type and assign it to all users that do not already have an explicit client assignment.
Table 2. Client Manager actions Action Change Assignments Description Add or remove explicit user assignments for this client level. This action allows the assignment of individual users or groups of users. Promote this client level to be the default level for this client type. Note that this will only succeed if all servers in the Lotus Notes Traveler pool can support this client level. Remove this client level. If any users were explicitly assigned to this level, then those users are assigned to the default client version once this client is deleted. This action is not allowed if this level is currently the default for its client type.

Make Default

Delete Client Level

Chapter 9. Administering Lotus Notes Traveler servers

35

36

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 10. Managing the Lotus Notes Traveler High Availability pool
Managing a Lotus Notes Traveler HA pool, in many ways, is very similar to managing a set of stand alone Lotus Notes Traveler servers. Lotus Notes Traveler servers are started and stopped individually. There is no command to start or shutdown all servers. When any server is shutdown in a pool, the other Lotus Notes Traveler servers detect this outage and handle the device requests. The Lotus Notes Traveler tell commands have been updated to be HA pool-aware. Where necessary, commands automatically route a request to another server or broadcast a request to all the servers in the pool without the administrator explicitly requesting that action. For example, tell traveler user <userName> can be used to show the details for a user. This command will automatically be forwarded to the appropriate server for the user. Another example is setting the log levels. The log levels are managed across the pool of servers, so to set log levels to fine, you would issue tell traveler log level fine and all servers will be notified that the log levels have been changed. Command helps have been updated, where applicable, to provide any new parameters that relate to working with a pool of servers. There are new commands added specifically for the HA environment: tell traveler bind There are scenarios in which it is useful to ensure that all of a user's device requests are handled on a specific server. In this case, the administrator can "bind" a user to a server. There are options to enable the bind, disable the bind, and show all users that are bound to a server. When a user is bound to a server and that server becomes unavailable, that user will not failover to another server in the pool. tell traveler HADR show Shows the status of all Lotus Notes Traveler servers in the pool. tell traveler users Displays the users allocated on the server. This is useful in an HA environment for understanding how users are spread over the various HA servers. This is not a specific HA command. tell traveler available <on/off> Allows an administrator to make a server unavailable from servicing requests. Issuing tell traveler available off sets the availability index to a negative value (for more information on the availability index, see below). The effect is that the server will not serve new device requests, causing any existing user processing to move to other servers until only the users explicitly bound to the server remain. This can be useful when trying to troubleshoot a server or in preparation for taking a server offline for maintenance or other purposes. Some commands can be issued to a specific server or broadcast to all servers. The tell commands have an optional command line parameter to send the command to a specific server or to broadcast a command. The parameter is -s <serverName |

37

* | *->. When this parameter is not specified, the default is to process the command locally. Specifying -s <serverName> will send the command to the specified server. Specifying -s * will broadcast the command to all servers, while -s *- will broadcast the command to all servers except the local. For example, to check the status of all the Lotus Notes Traveler servers in the HA pool, issue tell traveler -s * status. The status command will be forwarded to each server in the pool and the response will be displayed on the local console where the command was originally issued. The Lotus Notes Traveler Web Administration, in an HA environment, provides a view of all servers in the pool. The output is similar to the tell traveler HADR show command. This information is useful in gauging the health of the HA pool as well as diagnosing setup and communications issues. The Information provided for each server in the pool is: Domino Name The canonical name of the Lotus Notes Traveler Server. Host Name The fully qualified hostname of the Lotus Notes Traveler Server. Port The TCP/IP port on which the Lotus Notes Traveler server is listening for server to server communication. This must be the same for all servers.

IP Address This is the IP address that Lotus Notes Traveler Server has derived. Ensure that this IP address is correct for each server. Server Status This indicates whether or not the server is available. Available means that the server providing the status information to the Web Administration can communicate with the server listed. Heart Beat Gives the date and time that the server last updated the database, indicating that the server is running. Availability Index A computed value indicating load on the server. The availability index decreases as load increases on the server. A value of less than 0 means that the server is not available for processing device requests. Number of Users Number of Lotus Notes Traveler users (regardless of the number of devices) actively being monitored on this server. Build Level Build Level of the Lotus Notes Traveler Server. Except when maintenance or an upgrade is being performed, all servers should be at the same level. For more administration information, refer to Chapter 9, Administering Lotus Notes Traveler servers, on page 31.

38

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 11. Installing the Lotus Notes Traveler clients

The Lotus Notes Traveler 8.5.3 Upgrade Pack Beta Code Drop 1 server comes pre-loaded with the Lotus Notes Traveler 8.5.3.2 Windows Mobile and Nokia clients and Lotus Notes Traveler 8.5.3 Upgrade Pack Beta Android Client. The clients are accessible from the Lotus Notes Traveler user home page. With this release level, for the home page, you no longer have to specify /servlet/traveler. Instead, you can access the home page using http(s)://<hostname>/traveler. See the Lotus Notes and Domino wiki for existing information about installing the Lotus Notes Traveler 8.5.3 client: v For installing the client on Android devices v For configuring an Apple device v For installing the client on Windows Mobile devices v For installing the client on Nokia devices

39

40

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 12. Known restrictions

This section provides information on known restrictions for Lotus Notes Traveler Beta Upgrade Pack 1. Lotus Notes Traveler 8.5.3.1 known issues and limitations: v See the known limitations section of the Lotus Notes Traveler 8.5.3 documentation for more information. v The support site contains additional information as well. The following are restrictions and limitations specifically for Lotus Notes Traveler 8.5.3 Upgrade Pack Beta Code Drop 1. Note that these are point in time restrictions and should be lifted in later code drops. v Migration from prior versions is not supported. v (166246) Search results from the Lotus Notes Traveler Web Administration are case sensitive. For example, searching for user "joe" will not match with "Joe". v (166320) With some browsers, if you do not use a fully qualified name in the URL of the Web Administration interface, the data may not display. For example, use http(s)://yourco.com/LotusTraveler.nsf instead of http(s)://yourco/ LotusTraveler.nsf. v Server log settings are no longer set using the Domino server document. These settings will still be present on the Lotus Notes Traveler tab of the Domino server document, but will not have any effect. All Lotus Notes Traveler logging should be set using the tell traveler log command using the Domino server console. v Web Administration Interface browser support. The Lotus Notes Traveler Web Administration interface may not display or format correctly on all browsers and versions. Work is ongoing to support all the browsers identified in the Chapter 4, Software prerequisites, on page 11 section. If you experience issues with a particular browser, please try a different one v (166213) Name picker within Web Administration interface may not display directory entries. There are some administration functions in which you need to assign users and/or groups. A name picker function is provided to assist you with looking up and selecting users and groups. On some browsers, the name picker may not function correctly. Either switch to a different browser or enter manually the person name or group name. v (166143) In this beta release, the Lotus Notes Traveler Client Manager does not provide a method for an administrator to eliminate clients types from being downloaded and installed. v Uninstalling Lotus Notes Traveler 8.5.3 Upgrade Pack Beta. The installation of Lotus Notes Traveler 8.5.3 Upgrade Pack updates the HTTP servlet redirect rules. These updates are not removed during an uninstall. If you install an earlier version of Lotus Notes Traveler on the same server, this could affect the functionality. The administrator should manually update the redirection rules as follows: 1. Open Server configuration in the Domino Admin client. 2. Select Web > WebServer Configurations. 3. Select the rows under your server and delete:

41

v v

v v

URL->URL for (Microsoft-Server-ActiveSync*->/traveler/Microsoft-ServerActiveSync* URL-> URL for (/servlet/traveler*->/traveler* 4. Validate the Traveler external URL is correct in the Lotus Notes Traveler tab. (166652) The security setting for Prohibit Encrypted Devices is not available in this beta release. (166544) Android security settings for password History count enforcement and expiration requires Android 3.0 or higher. Connecting an Android device with an older OS level may have unpredictable results with these security settings turned on. (166484) Require external mail domain validation setting cannot be enabled using the Web Administration interface. (33225) HTC devices that are upgraded to Ice Cream Sandwich (4.x) cause widgets to stop working. The workaround is to not use the widgets.

v The names of many Lotus Notes Traveler configuration parameters have changed since the beta 1 drop. An attempt is made to migrate existing settings. For any settings in the form NTS_ that are not recognized, a warning will be logged to the Domino Console as well as the Lotus Notes Traveler activity log.

42

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 13. Providing feedback or reporting problems

IBM encourages you to report any problems or suggestions you have while working with the Beta. Please add your feedback to the forum so that we can continue to make adjustments and improve the solution. If you encounter any problems or have suggestions for improvement, please use the Design Partner forum. You will need to provide your developerWorks Lotus (LDD/Notes.net) user name at the prompt. Contact Jan Kenney (jank@us.ibm.com) if you have forum access issues. If Lotus Notes Traveler support staff responds and requests data from the Lotus Notes Traveler server(s), please use one of the following methods for collecting and uploading the information. Be sure to notify Lotus Notes Traveler support once the upload is complete.

Automatic method
The easiest way to collect and upload data is to use the Lotus Notes Traveler PMR tell command. This will automatically collect and upload all data required for Lotus Support. For a single server use this command:
> tell traveler pmr 99999,999,000

For all servers in a Traveler Pool use this command:

> tell traveler -s * pmr 99999,999,000

For a particular server in a Lotus Notes Traveler Pool use this command:
> tell traveler -s "servername/company" pmr 99999,999,000

Note: Use invalid PMR number 99999,999,000 for the Beta, since official PMRs are not accepted for Beta customers. In an official release, substitute the appropriate PMR number.

Manual method
From each Lotus Notes Traveler server you are collecting data, run the following two commands:
> tell traveler systemdump > tell traveler log collect

The log collect will generate a single dated zip file. Upload the dated zip file(s) to IBM using FTP or HTTP.

FTP upload
To upload your report using FTP, open a command prompt and perform the following actions:
ftp 192.109.81.7 User: anonymous Password: your-e-mail-address

43

ftp> ftp> ftp> ftp>

cd toibm/lotus bin put filename.zip bye

HTTP upload
To upload your report using HTTP, point your web browser to http://www.ecurep.ibm.com/app/upload, and enter the following information: v PMR Number: 99999,999,000 v Upload is for: Lotus v Email address: Your mail address Select Continue and choose the files for upload. Note: Use invalid PMR number 99999,999,000 for this Beta since official PMRs are not accepted for Beta customers. In an official release, substitute the appropriate PMR number.

44

Lotus Notes Traveler 8.5.3 Upgrade Pack 1 Beta Drop 2

Chapter 14. More information

There are a few additional sources of information for the Beta Upgrade Pack. For more information about Lotus Notes Traveler, see the Lotus Notes Traveler 8.5.3 product documentation. For more information about integrating the Apple iPad, iPhone, and iPod Touch with your enterprise systems, see the Enterprise Deployment Guide.

45