You are on page 1of 492

IBM Redbooks: IBM Notes Traveler

Hints and Tips for a Successful


Deployment



















Note: This PDF document is the original text from the IBM Notes Traveler Hints and Tips for a
Successful Deployment guide hosted in the online wiki. Always refer to the online wiki version for
the latest updates.
Copyright IBM Corp. 2013. All rights reserved. 1
Contents
Chapter 1. IBM Lotus Notes Traveler overview . . . . . . . . . . . . . . . . . . . . . 13
1.1 Lotus Notes Traveler architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2 Introducing Lotus Notes Traveler 8.5.3 Upgrade Pack 1 . . . . . . . . . . . . . 15
1.2.1 Web administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2.2 Administration features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2.3 Client manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.2.4 Traveler high availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.2.5 Android enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.2.6 Miscellaneous new features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 2. Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.1 Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.1.1 Domino Server support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.1.2 Mail database support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.1.3 Domino directory template support (names.nsf) . . . . . . . . . . . . . . . . 23
2.1.4 Server hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.1.5 Enterprise database requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.1.6 Server operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.1.7 Web browsers for administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.1.8 IP sprayer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.1.9 Device hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.1.10 Devices and operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.2 Choosing a stand-alone or high availability configuration for Lotus Notes
Traveler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.2.1 Number of devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.2.2 System availability consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.2.3 Other considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.2.4 What does IBM do internally? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2.3 Planning your server and network topology . . . . . . . . . . . . . . . . . . . . . . . 33
2.3.1 Choosing a Lotus Domino server . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.3.2 High availability or stand-alone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.3.3 Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.4 Capacity planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.5 Catering for user with multiple devices . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.5.1 What does IBM do internally? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.6 Domino domain configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.6.1 What does IBM do internally? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.6.2 Further reading on supporting multiple Lotus Domino . . . . . . . . . . . 46
2 IBM Notes Traveler Hints and Tips for a Successful Deployment
2.7 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.7.1 Device security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.7.2 Server security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.7.3 Encrypting Lotus Notes Traveler network traffic . . . . . . . . . . . . . . . . 53
2.7.4 Internet password lockout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.8 Language support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.9 Anti-virus recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.10 Upgrading versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.10.1 Upgrading Lotus Domino version . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.10.2 Upgrading Lotus Traveler upgrading. . . . . . . . . . . . . . . . . . . . . . . . 59
2.11 Integrating Lotus Notes Traveler into a high availability pool . . . . . . . . . 60
2.12 Enterprise database server clustering. . . . . . . . . . . . . . . . . . . . . . . . . . . 61
2.13 Load balancer considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.14 Mobile device management integration. . . . . . . . . . . . . . . . . . . . . . . . . . 63
2.14.1 What is mobile device management? . . . . . . . . . . . . . . . . . . . . . . . 63
2.14.2 Why use a mobile device management solution in conjunction with
Lotus Notes Traveler? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
2.14.3 Further reading on mobile device management . . . . . . . . . . . . . . . 64
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment . 65
3.1 Scenario description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.1.1 Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.2 Lotus Notes Traveler installation on Linux . . . . . . . . . . . . . . . . . . . . . . . . 67
3.2.1 Installing Lotus Notes Traveler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.2.2 Domino startup and installation validation. . . . . . . . . . . . . . . . . . . . . 78
3.3 Lotus Notes Traveler installation on Windows . . . . . . . . . . . . . . . . . . . . . 79
3.3.1 Installing Lotus Notes Traveler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
3.3.2 Domino startup and installation validation. . . . . . . . . . . . . . . . . . . . . 88
3.4 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
3.4.1 Lotus Domino configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
3.4.2 Lotus Notes Traveler configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 91
3.4.3 Additional configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Chapter 4. Deploying a high availability Lotus Notes Traveler environment
131
4.1 Scenario description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
4.1.1 Planning considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
4.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
4.2.1 Lotus Notes Traveler installation. . . . . . . . . . . . . . . . . . . . . . . . . . . 134
4.2.2 Database installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
4.2.3 Load balancer installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
4.3 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
4.3.1 Lotus Domino configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Contents 3
4.3.2 Database configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
4.3.3 Lotus Notes Traveler configuration for high availability. . . . . . . . . . 163
4.3.4 Configuring the selected load balancer . . . . . . . . . . . . . . . . . . . . . . 168
Chapter 5. User deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.1 User provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.1.1 Access to the Lotus Notes Traveler server . . . . . . . . . . . . . . . . . . . 172
5.1.2 Access control list configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
5.1.3 User authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5.2 Installation and configuration on an Apple device. . . . . . . . . . . . . . . . . . 177
5.2.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
5.2.2 Installing Lotus Notes Traveler profile on an Apple mobile device . 178
5.2.3 Customize Sync data and schedule . . . . . . . . . . . . . . . . . . . . . . . . 186
5.2.4 Managing mail on Apple devices . . . . . . . . . . . . . . . . . . . . . . . . . . 188
5.3 Installation on an Android device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
5.3.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
5.4 Installation on a Windows mobile device. . . . . . . . . . . . . . . . . . . . . . . . . 223
5.4.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
5.4.2 Installing the Lotus Notes Traveler application on a Windows mobile
device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
5.4.3 Customize data sychronization and schedule. . . . . . . . . . . . . . . . . 239
5.4.4 Managing mail on Windows devices . . . . . . . . . . . . . . . . . . . . . . . . 240
5.5 Installation on a Sybian or Nokia device . . . . . . . . . . . . . . . . . . . . . . . . . 250
5.5.1 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
5.5.2 Beginning installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
5.5.3 Customize Sync data and schedule . . . . . . . . . . . . . . . . . . . . . . . . 255
5.6 Unconventional deployment options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
5.6.1 Apple device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
5.6.2 Android device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Chapter 6. Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
6.1 Moving to a 64-bit architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
6.1.1 How to move . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
6.1.2 Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
6.2 Upgrading to 8.5.3 Upgrade Pack 1 from a previous version of Lotus Notes
Traveler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
6.2.1 Announcing the upgrade schedule . . . . . . . . . . . . . . . . . . . . . . . . . 264
6.2.2 Stopping Lotus Domino server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
6.2.3 Backing up files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
6.2.4 Updating Lotus Domino. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
6.2.5 Upgrading Lotus Notes Traveler . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
6.2.6 Starting Lotus Domino and Lotus Notes Traveler . . . . . . . . . . . . . . 272
6.2.7 Validating the upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
4 IBM Notes Traveler Hints and Tips for a Successful Deployment
6.2.8 Additional configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
6.3 Moving from Lotus Notes Traveler 8.5.3 Upgrade Pack 1 stand-alone to a
high availability environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
6.3.1 Integrating an existing Lotus Notes Traveler 8.5.3 Upgrade Pack 1
stand-alone servers into a Lotus Notes Traveler High Availability pool
285
6.3.2 Integration strategies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
6.3.3 Setting up a new HA pool and integrating an existing servers into the
pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
6.4 Moving from a single pool to a multi-pool high availability environment . 288
6.4.1 Moving from a single pool to a multi-pool high availability environment
288
6.4.2 Further reading on creating Lotus Notes Traveler high availability pools
290
Chapter 7. Enterprise integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
7.1 LDAP integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
7.1.1 Configuring Directory Assistance to enable LDAP authentication . 294
7.1.2 Further reading on LDAP integration . . . . . . . . . . . . . . . . . . . . . . . 297
7.2 Configuring single sign-on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Chapter 8. Administration and management . . . . . . . . . . . . . . . . . . . . . . 299
8.1 Server console commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
8.1.1 Tell command reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
8.1.2 High availability commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
8.2 Web-based administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
8.2.1 Device security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
8.2.2 Device settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
8.2.3 Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
8.2.4 Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
8.2.5 Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
8.2.6 Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
8.3 Policy-based management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
8.4 Server document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
8.4.1 Traveler tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
8.4.2 Basic tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
8.4.3 Security tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
8.4.4 Port tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
8.4.5 Internet protocols tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
8.5 Customizing the Lotus Notes Traveler home page . . . . . . . . . . . . . . . . . 339
8.5.1 Notes.ini servlet display parameters . . . . . . . . . . . . . . . . . . . . . . . . 339
8.6 Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
8.6.1 Log setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Contents 5
8.6.2 Log considerations in a stand-alone environment. . . . . . . . . . . . . . 349
8.6.3 Log considerations in a high availability environment . . . . . . . . . . . 350
8.7 The travelerutil command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
8.7.1 travelerutil db set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
8.7.2 travelerutil ssl set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
8.8 Monitoring Lotus Notes Traveler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
8.8.1 Monitoring device and server synchronization . . . . . . . . . . . . . . . . 354
8.8.2 Monitoring server resource usage. . . . . . . . . . . . . . . . . . . . . . . . . . 357
8.8.3 Logging Lotus Notes Traveler status information to log files on an
administrator defined interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
8.8.4 Monitoring Traveler with Watchit . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
8.9 Backup and recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
8.9.1 All deployments of Lotus Notes Traveler . . . . . . . . . . . . . . . . . . . . 370
8.9.2 Stand-alone deployments of Lotus Notes Traveler . . . . . . . . . . . . . 370
8.9.3 High Availability deployments of Lotus Notes Traveler . . . . . . . . . . 371
8.10 Recommended maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
8.10.1 All environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
8.10.2 Stand-alone environment only . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
8.10.3 High availability environment only. . . . . . . . . . . . . . . . . . . . . . . . . 373
Chapter 9. Tuning and troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . 375
9.1 Performance tuning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
9.1.1 Lotus Notes Traveler high availability considerations . . . . . . . . . . . 376
9.1.2 Latest software version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
9.1.3 Data filter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
9.1.4 Log level options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
9.1.5 Enterprise database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
9.1.6 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
9.1.7 User authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
9.1.8 Transactional logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
9.2 Problem determination guides. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
9.3 Troubleshooting techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
9.3.1 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
9.3.2 Common user problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Chapter 10. Appendix A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
6 IBM Notes Traveler Hints and Tips for a Successful Deployment
Copyright IBM Corp. 2013. All rights reserved. 7
Preface
Meet the authors
This wiki was produced by a team of technical specialists from around the world.
Sreehari (Sree) Haridevara is a Field Support Engineer
based in Poughkeepsie, New York. He joined the Accelerated
Value team in April of 2008, and brings over 19 years of
industry experience. In this role, Sree has delivered numerous
successful engagements on various Lotus products including
Domino servers, Notes clients, Sametime, Websphere Portal,
Quickr, and NotesTraveler. He is well versed with multiple
Operating systems including Windows, AIX, Linux, zSeries (Linux and z/OS).
Currently, Sree delivers FSS offerings including Domino performance and
capacity planning workshop, NSD workshop, UNIX administration for Domino
administrators, and customized training for various IBM collaboration solutions
products. Previously, Sree worked as a Domino Architect for 12 years
responsible for IBM internal Domino deployment and infrastructure for Mail and
Application domains for over 100,000 users.
Martin Hill is an IBM accredited Senior IT specialist working in
the IBM UK Mobile Enterprise Services (MES) team. He joined
IBM in 1994 and spent over 12 years working with Lotus
Notes/Domino and associated products as an Email
Messaging and Collaboration specialist, before moving into his
current MES role. He now works with IBM's clients helping
them to implement a wide range of mobility related products &
services, of which Lotus Notes Traveler is one. He was also one of the technical
leads for the IBM internal deployment of Lotus Notes Traveler in EMEA, which
now serves 17,000+ IBMers in over forty different countries.
Abhishek Jain is working with IBM India Software Labs since
2004 and has been in the industry for 10 years. He is currently
working as an IT Specialist with IBM Collaboration Services
and is skilled on various Lotus products. He is a Certified Lotus
Professional, Certified Lotus Administrator, and a Certified
Lotus Instructor on both Lotus Domino Administration and
Development. Abhishek has been a part of earlier RedWikis
Customizing Quickr 8.1 and Best Practices for Building Web Applications for
8 IBM Notes Traveler Hints and Tips for a Successful Deployment
Domino 8.5.1. He has also published developerWorks articles Integrating IBM
Lotus Forms with IBM Lotus Domino and Auto-zipping Lotus Notes Attachments.
John J Johnson is a Field Support Engineer, specializing in
Lotus Notes Traveler and IBM Sametime, along with Domino.
He has been involved extensively with Lotus Notes Traveler for
the last two years, traveling to customers all across North
America to assist them with their Traveler deployments. John
started with IBM in 1999, working as a developer on internal
IBM Lotus Domino Applications. He joined the Field Support
Services (FSS) team in January of 2006.
Maiko Miwa is working for IBM Japan Systems Engineering
Co., Ltd. which provides advanced technical support as well as
technology transfer to IBM organizations and clients in Asia
Pacific region. Being with Collaboration and Mobile team for 4
years, she has served as technical and consulting roles in
some Lotus products (especially in WebSphere Portal, IBM
Connections and Lotus Notes Traveler) and general mobile
solutions. As an expert in Lotus Notes Traveler, she has involved in areas such
as installation and configuration of Lotus Notes Traveler and writing technical
articles about it. She also has advised many customers about designing and
administering Lotus Notes Traveler.
Matt S Munse is the technical lead for Lotus Notes Traveler
level 2 support. He has been supporting the Lotus Notes
Traveler product since version 8.5.2.1 of the product was
released. Prior to this, he spent 8 years supporting
WebSphere portal. He has been involved in both the support of
IBM technologies as well as development of the products that
he has supported. Matt has written a number of IBM published
documents including developerWorks articles for WebSphere Portal and pages
for the Official Info Center documentation for Lotus Notes Traveler.
Jenny Tsai is a Software Engineer working in the IBM Taiwan
Mobility Team. Her area of expertises include Lotus Domino,
Lotus Notes Traveler architecture and other mobile solutions
across various platforms. She has worked with Lotus Notes
Traveler product since version 8.5.2.2 and specialising in
reliability and performance analysis. Jenny holds a master
degree in Computer Science from the University of Oxford.
Preface 9
Peter Volkmar is a level 2 support engineer for Lotus Notes
Traveler and IBM Mobile Connect. He started his career as an
IBM customer before being seduced by the dark side 28 years
ago. He has been involved with IBM Mobile Connect as a
developer, a services provider, and a support engineer. When
a scientific experiment from the IBM lab in Heidelberg, ARTour,
was first shown in Research Triangle Park, he was involved in
setting up its demonstration in 1994; it took root in its new home and grew to
become IBM Mobile Connect.
Whei-Jen Chen is a Project Leader at the International Technical Support
Organization, San Jose Center. She has extensive experience in application
development, database design and modeling, and DB2 system administration.
Whei-Jen is an IBM Certified Solutions Expert in Data Management, and an IBM
Certified IT Specialist
Acknowledgements
The authors express their deep gratitude for the content contributed from the
following members:
Jim Dewan is an Advanced Value Leader in IBM for the last seven years. Jim
has developed a series of tools to assist customers in better managing their
deployments. He has in-depth experiences in Domino Administration
development, Sametime and Domino Integration, and Domino Linux
development. Jim shares his work in the Lotus Greenhouse "Watchit
Community" to provide customers a place to access code, collaborate with
the larger Watchit community, and review documentation.
Vladislav Tatarincev is the Technical Director and co-owner of CYONE.
www.cyone.eu. He has a Master of Computer Science from Latvian
University. He has been working with Domino from release 4.5, for more than
10 years. He is also an IBM Certified Security Professional. Vladislav is the
author of many freeware tools for Domino. His key areas of focus for Lotus
Domino are: Performance, Traveler, Security. His hobbies include: diving,
shark diving, wreck diving, underwater archeology, and motorbikes.
We wish to acknowledge a special thank you to the following sponsors and key
stakeholders from the Lotus Development, Product Management, and Lotus IDC
Teams:
Amanada Bauman - Everyone Writes and IDC Wikis Program Manager
Bill Wimer - Lotus Notes Traveler Chief Programmer
10 IBM Notes Traveler Hints and Tips for a Successful Deployment
Additionally, we wish to thank the following members for their technical help and
contributions to this wiki:
J Smith Doss
Curtis Ebbs
Bob Sielken
Raji Akella
Danny Levenson
Corey quinn
Yuhsuke Murakami
Zin Nyein Oo
Mieko Kudoh
Masaki Nakabayashi
David Kline
Become an author
Join us for a two- to six-week residency program! Share your knowledge with
peers in the industry and learn from others. Help create content about specific
products or solutions, while getting hands-on experience with leading-edge
technologies. You will have the opportunity to team with IBM technical
professionals, Business Partners, and Clients. Your efforts will help increase
product acceptance and customer satisfaction. As a bonus, you will develop a
network of contacts in IBM development labs, and increase your productivity and
marketability.
Find out more about the residency program, browse the residency index, and
apply online at:
http://www.ibm.com/redbooks/residencies.html
Comments welcome
Your comments are important to us!
We want the content in this wiki and all our wikis to be as helpful as possible.
Provide us your comments in one of the following ways:
Use the commenting feature with in the wiki. Login and add comments,
located at the bottom of each page.
Provide feedback in the Web form located at:
http://www-12.lotus.com/ldd/doc/cct/nextgen.nsf/feedback?OpenForm
Preface 11
Stay connected to IBM Redbooks
Find us on Facebook:
http://www.facebook.com/IBMRedbooks
Follow us on Twitter:
http://twitter.com/ibmredbooks
Look for us on LinkedIn:
http://www.linkedin.com/groups?home=&gid=2130806
Explore new Redbooks publications, residencies, and workshops with the
IBM Redbooks weekly newsletter:
https://www.redbooks.ibm.com/Redbooks.nsf/subscribe?OpenForm
Stay current on recent Redbooks publications with RSS Feeds:
http://www.redbooks.ibm.com/rss.html
12 IBM Notes Traveler Hints and Tips for a Successful Deployment
Copyright IBM Corp. 2013. All rights reserved. 13
Chapter 1. IBM Lotus Notes Traveler
overview
IBM Lotus Notes Traveler software is a push email product that provides a full featured e-mail
access for Lotus Notes users using supported mobile devices which includes both smart
phones and tablets.
Lotus Notes Traveler wirelessly synchronizes email, calendar, contacts, journal and to-do
data with an IBM Lotus Domino server without compromise the security aspects of an
organization.
The eligible Lotus Domino customers can download the software free of charge using their
respective PartnerWorld and Passport Advantage accounts or through IBM Sales
representative.
Lotus Notes Traveler software provides following features:
Provides a full, cross-platform release that includes capabilities for these supported
mobile device platforms: Apple iOS, Google Android, Nokia Symbian, and Microsoft
Windows Mobile.
Supports Lotus Notes mobile users, both through on-premises IBM Lotus Domino or Lotus
Domino Express deployments, and in the IBM cloud with IBM SmartCloud Notes.
Reads and composes Lotus Domino encrypted email.
Searches your corporate directory to find individuals and groups by name that you want to
email.
Single point of control to monitor the Lotus Notes Traveler user community.
Scheduled synchronization and data filtering policies, including the ability to wipe only the
Lotus Notes Traveler data.
Supports for remote wipe for lost or stolen devices.
Enforceable Security policies to remotely secure mobile devices.
Automated client updates.
Data in transit is synchronized over secure HTTPS and SSL connection.
1
14 IBM Notes Traveler Hints and Tips for a Successful Deployment
Supports both Linux and Microsoft Windows servers.
Works over all wired and wireless connections (GPRS, GSM, WiFi, USB, and ActiveSync)
Starting with the version 8.5.3 Upgrade Pack 1, the Lotus Traveler server can also be
optionally configured as a server pool to work in high availability mode.
1.1 Lotus Notes Traveler architecture
Lotus Notes Traveler is installed on a Lotus Domino server and runs as a separate add-in
task. Having a dedicated Lotus Notes Traveler infrastructure is preferable, so nothing else
should be deployed on the Lotus Notes Traveler servers to ensure adequate system
resources are available.
Each mobile device has a either Lotus Notes Traveler client (Google Android, Symbian Nokia
and Windows Mobile) or profile (Apple iOS) installed which communicates with the Lotus
Notes Traveler server over http or https. All mobile devices have to download the Lotus
Traveler client, except for Apple devices which download a configuration a profile to the device
and use the native iOS email client.
The following components are involved when a user accesses the Lotus Notes Traveler
server;
User mail file
Mobile device
Domino directory
The following figure shows the main components of a simple Lotus Notes Traveler
configuration and how they interact:
Figure 1-1 The main component of Lotus Notes Traveler
Chapter 1. IBM Lotus Notes Traveler overview 15
New mail messages arriving in your Inbox on the Domino server arrive on the device without
you needing to do anything (that is, are automatically pushed) and can trigger a notification
event, such as a tone or a device vibration. Updates made on the device such as sending a
new mail message or changing a calendar entry are synchronized with the server as soon as
a network connection is available, and are reflected in the user's mail file and Notes client.
The Lotus Notes Traveler client provides a simple, easy-to-use interface with a minimal
number of configuration settings. You can customize how much data is synchronized with the
device to optimize the use of device memory and server resources.
The Lotus Traveler server checks the Domino Directory for the user home server and mail file
information and subsequently connects to it. The Lotus Traveler server does not store any
data, only the user's designated mail server has the user mail file. The figure below shows
how the three components work together:
In a stand-alone implementation (that is non high availability) of Lotus NotesTraveler server,
there is a local Derby database where information about the user's subscribed folders,
devices, and sync status is stored. This derby database also stores any security information
about the devices on the system if the administrator of the server has implemented specific
settings in regards to devices security. In a high availability implementation of the Lotus Notes
Traveler server, this information is kept in a central database on a separate enterprise
database server (IBM DB2 for Linux, UNIX, and Windows or Microsoft SQL Sever) and
shared amongst all the Lotus Notes Traveler servers in the same high availability pool.
There is a friendly way to see the majority of information stored in the Lotus Notes Traveler
database referenced above. This is the LotusTraveler.nsf file which is located in the root folder
of the Lotus Traveler server for stand-alone implementations or a web interface found at
http(s)://server_name.domain.com/LotusTraveler.nsf for a high availability implementation. In
this view, you can see all devices, and users. You can use this interface to administer these
devices and users. In essence, this is the graphical user interface the administrator can use to
view and administer the Lotus Notes Traveler's database information.
1.2 Introducing Lotus Notes Traveler 8.5.3 Upgrade Pack 1
The Lotus Notes Traveler 8.5.3 Upgrade Pack 1 introduces the much desired high availability
(HA) feature as an option for the Lotus Notes Traveler deployments.
It is still possible to use Lotus Notes Traveler on a single server without high availability
(referred to as 'stand alone' in Upgrade Pack 1 terminology) and this is supported by the IBM,
but many enterprise customers are expected to move to the HA version of the Lotus Notes
Traveler.
The Lotus Notes Traveler in HA mode includes the following components:
16 IBM Notes Traveler Hints and Tips for a Successful Deployment
The IP Sprayer (a load balancer) that directs the incoming the Lotus Traveler client
connection to one of the available configured servers.
The Lotus Notes Traveler server pool that receives a connection from the load balancer.
In HA mode, a shared relational database replaces the locally stored 'Derby' database that
is used in stand alone mode. Lotus Notes Traveler 8.5.3 Upgrade Pack 1 supports using
both IBM DB2 for Linux, UNIX, and Windows and Microsoft SQL Server to host the
relation database. You can use the high availability features provided in both relational
database servers in your Lotus Notes Traveler environment to make the end to end Lotus
Notes Traveler highly available. IBM provides a free DB2 entitlement with the Louts Notes
Traveler.
All other components of mail servers, mail files, the Domino Directory are the same.
Apart from the new high availability mode, there are other new feature introduced in Lotus
Notes Traveler 8.5.3 Upgrade Pack 1 including:
Web administration
Administration features
Client manager
Android enhancements
Miscellaneous new features
1.2.1 Web administration
Lotus Notes Traveler 8.5.3 Upgrade Pack 1 provides a new web administration tool that is
based on XPages and uses the IBM oneUI framework. You can use this web interface to
perform all the activities previously supported by the Lotus Notes Traveler administration
application, including remote wipe, setting up security policies, and comprehensive search
capabilities. The following figure shows the new administration interface which is available in
both stand alone and HA mode:
Chapter 1. IBM Lotus Notes Traveler overview 17
1.2.2 Administration features
The Lotus Notes Traveler server provides an administrator with different options to manage
the server:
Administration
Lotus Domino server console
Administration application (LotusTraveler.nsf)
Lotus Domino server policies
Lotus Domino server security settings
Filter limits
In Lotus Notes Traveler 8.5.2.3, administrative settings could be added to NTSConfig.xml
that would enforce a maximum filter window for all users. The Lotus Notes Traveler
administration application now includes the ability to configure the maximum filter window
settings as part of the default settings. A separate filter limit setting is provided for mail,
past events, future events, and notes.
Scheduled synchronization settings
The Lotus Notes Traveler administration application now includes the ability to configure
the scheduled synchronization settings as part of the default settings which were earlier
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 server policies. Locking a setting prevents the user from modifying
that setting from their device. The following figure shows how you can lock a particular
setting:
18 IBM Notes Traveler Hints and Tips for a Successful Deployment
1.2.3 Client manager
This newly released subsystem 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 that display exactly which client levels are installed
on the Lotus Notes Traveler server. The Client manager allows the administrator to assign
specific client levels to individual users or groups of users.
1.2.4 Traveler high availability
The ability to run multiple Lotus Notes Traveler servers in a high availability service pool is
provided in Lotus Notes 8.3.5 Upgrade Pack 1. This feature allows devices to connect to any
server in the pool at any given time. Requests are received at any Lotus Notes Traveler server
and a decision is made whether to service the request locally or to route the request to
another server in the pool based on which server is currently monitoring mail for the user and
server loads. If a server in the pool is stopped or unavailable, device requests can be handled
by the other servers in the pool without requiring a recovery synchronization.
Support for Enterprise Database Servers has been introduced to enable Lotus Notes Traveler
high availability. In this release, DB2 for Linux, UNIX, and Windows and Microsoft SQL Server
are supported for storing Lotus Notes Traveler Notes administration data and device
synchronization data. An enterprise database is not required when running Lotus Notes
Traveler on a single server (i.e. in stand alone mode).
Lotus Notes Traveler also supports the transfer of existing administration and user
synchronization data from the stand-alone Derby database to the enterprise database. This
allows the migration and/or consolidation of existing Lotus Notes Traveler servers into a Lotus
Notes Traveler HA pool.
Chapter 1. IBM Lotus Notes Traveler overview 19
High availability pool-aware console commands
The association of a device to a server is easy and 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 run the
request on the appropriate server. New console commands are also added to ease the
management and serviceability of the pool.
Additional contributors to status condition
Additional factors in determining the status condition (red/yellow/green) of a server are
added. The new conditions include:
Low disk space on server
Expiration pending of the SSL certificate used to secure Lotus Notes Traveler server to
server communication
1.2.5 Android enhancements
The enhancements for Android mobile devices include both client and server areas:
Enhancements for Android Client
Monthly view for Calendar
Mail and Calendar UI now use larger screen size in tablets
Enhancements for Server managed security policy
Enforce the complex password type (OS 3.0 or higher)
Disable local password storage
Prohibit copy to clipboard
Prohibit export attachments to file system
Prohibit camera (OS 4.0 or higher)
Application password support
Password expiration period (OS 3.0 or higher)
Password history count (OS 3.0 or higher)
Prohibit unencrypted devices (OS 3.0 or higher)
1.2.6 Miscellaneous new features
Some general enhancements that are applicable for all mobile devices are as listed below.
Improved handling of Lotus Notes documents
Notes links that are contained in mail messages and viewed on Lotus Notes Traveler clients
now include an additional URL hotspot which points to the web address of the application
server. You can open the linked application using a browser on the mobile device, similar to
how applications can be opened using iNotes. However, there are a number of restrictions to
consider with this functionality:
The link can only be accessed if a connection can be made from the mobile device to the
user's Domino mail server and/or the Domino application server specified in the link.
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.
20 IBM Notes Traveler Hints and Tips for a Successful Deployment
Sent folder save options
Lotus Notes Traveler now synchronizes with the user preference for handling the saving of
mail in the Sent Mail folder. In the previous releases, sent mail was always saved in the Sent
Mail folder. Additionally, the Lotus Notes Traveler Administrator can override this behavior
using the NTS_SENDMAIL_SAVE_OPTIONS notes.ini parameter. Supported values are:
user - Honor the user's Notes and iNotes client mail save preferences (default).
never - Lotus Notes Traveler never saves sent mail in the Sent Mail folder.
always - Mail sent from a Lotus Notes Traveler client is always saved in the Sent folder,
regardless of the user's Notes and iNotes client mail save preferences.
noatt - Attachments in the outgoing mail will not be saved in the Sent Mail folder.
Draft mail attachment options
Lotus Notes Traveler now gives administrators the option for all users who do not to save
attachments when creating a draft document on the device. When the administrator sets the
notes.ini parameter NTS_DRAFT_DO_NOT_SAVE_ATTACHMENTS=true, all attachments
are stripped from the document being saved on a Domino server.
Copyright IBM Corp. 2013. All rights reserved. 21
Chapter 2. Planning
In this chapter, we describe the tasks and the areas you need to consider when planning an
IBM Lotus Notes Traveler deployment.
2
22 IBM Notes Traveler Hints and Tips for a Successful Deployment
2.1 Supported hardware and software
In this section, we provide the base supported hardware and software for IBM Lotus Notes
Traveler. For the complete and the most current Lotus Notes Traveler 8.5.3 Upgrade Pack 1
system requirements, see the following website:
http://www.ibm.com/support/docview.wss?uid=swg27027499
2.1.1 Domino Server support
All versions of IBM Lotus Notes Traveler must be installed and run on a base Lotus Domino
server. You can use either of these two versions of Lotus Domino for a stand-alone Lotus
Notes Traveler server:
Lotus Domino 8.5.3 Enterprise Server
Lotus Domino 8.5.3 Messaging Server
To implement a high availability Lotus Notes Traveler server, you must use Domino 8.5.3
Enterprise Server.
The code version of both Lotus Domino and Lotus Notes Traveler must be matched to the first
three digits of the version number. For example, version 8.5.3.x of Lotus Notes Traveler has to
be installed with version 8.5.3.x of Lotus Domino. It is not possible to install a lower version of
Lotus Notes Traveler on a higher version of Domino (for example, Lotus Notes Traveler
version 8.5.2.x on Domino version 8.5.3.x). This is because the libraries that are used by the
Lotus Notes Traveler task are associated with the libraries that the Lotus Domino server
implements and the Libraries that the Lotus Domino server uses can change in different
releases of the product. This is why the only supported environments are the environments
that match the base versions.
Note that during the installation process of Lotus Notes Traveler 8.5.3 Upgrade Pack 1,
Domino will automatically be upgraded to the Upgrade Pack 1 of Lotus Domino version 8.5.3
if this is not already in place. This upgrade to Lotus Domino is included in the Lotus Notes
Traveler installation package of 8.5.3 Upgrade Pack 1. This is because there are certain
aspects that are included in this Lotus Domino upgrade pack that are needed for Lotus Notes
Traveler new functionality such as XPages for the web administration of the server.
For optimal performance, Lotus Notes Traveler should be installed on a dedicated server,
including using a dedicated Lotus Domino server that doesn't perform any other Lotus
Domino functions (for example, mail server or replication hub). In a small scale proof of
concept or pilot, you could consider installing Lotus Domino mail server, Lotus Notes Traveler,
and even other tasks such as Sametime on the same host machine, however the production
system should be designed with the capacity carefully planned and have a dedicated server
just for Lotus Notes Traveler. We describe the capacity planning in 2.4, Capacity planning on
page 43.
2.1.2 Mail database support
Lotus Notes Traveler can use and synchronize with remote mail databases hosted on Lotus
Domino version 7.0.2 and later, running on any operating system that Lotus Domino supports.
Lotus Notes Traveler supports Lotus Notes standard and iNotes mail file templates based on
version 6.5 and higher. So this means that although the Lotus Notes Traveler server itself has
to be at a very specific version, it can synchronize email from any Lotus Domino server
running on any platform as long as it is at version 7.0.2 or greater, and using mail file
Chapter 2. Planning 23
templates of version 6.5 and above. It is possible to have your Lotus Notes Traveler server
running at a newer version of Lotus Domino than the rest of the Lotus Domino servers in your
domain. However if doing so, you need to give careful consideration to preventing the newer
database design elements replicating out from your Lotus Notes Traveler server to the rest of
the older Lotus Domino servers in your Lotus Domino domain. More details on Lotus Domino
domain planning can be found in 2.6, Domino domain configuration on page 44.
2.1.3 Domino directory template support (names.nsf)
You must ensure that you use the same Domino directory template for the names.nsf
database (pubnames.ntf) version for the Lotus Domino server that you run Lotus Notes
Traveler on. Ensure the Domino directory template that is supplied with the version of Lotus
Domino that matches your Lotus Notes Traveler version. So for example, if using Lotus Notes
Traveler 8.5.3 Upgrade Pack 1, the Domino directory template used on the Lotus Domino
server running Lotus Notes Traveler must also be at version 8.5.3 Upgrade Pack 1. This is
because there are new fields introduced in each version of Lotus Notes Traveler and only the
matching version of Domino directory mail template includes the new fields. If the Domino
directory template on the Lotus Domino server and Lotus Notes Traveler server do not match,
certain fields won't show all of the data. For example, there was no "External Server URL"
field in the 8.5.1.x version of Lotus Notes Traveler. If you upgraded the Lotus Notes Traveler
server to 8.5.2.x or later and did not upgrade the Domino directory template, the field for the
"External Server URL" would not appear even though this was a valid data field according to
the server.
You can check the version of the Domino directory template on any Lotus Domino server
using the following steps:
1. Open the Domino administration console and navigating to the "Files" tab.
2. Right-click the Domino directory for the server (names.nsf filename). Select Properties.
3. From the pop-up window, select the design tab. The template version is shown in the
Inheritance section.
The template version should be 8.5.3 for a Lotus Domino Server running version 8.5.3, and
that is the required version for Lotus Notes Traveler 8.5.3 upgrade pack 1.
When planning your Lotus Notes Traveler infrastructure if you opt to place your Lotus Notes
Traveler servers in the same Lotus Domino domain as the rest of your Lotus Domino servers,
you need to decide how to manage the Domino directory template. You have three options:
Upgrade all your Lotus Domino servers in the Domino domain to use the same version of
Lotus Domino as used on your Lotus Notes Traveler Server. This means all your Lotus
Domino servers will be at the same level and will use the same version the Domino
directory template, but this may be difficult to achieve if you have a large Lotus Domino
environment.
Just upgrade your Lotus Notes Traveler servers to use the latest version of Lotus Domino
and allow the updated Domino directory template replicate to the other, older, Lotus
Domino servers in your Lotus Domino domain. This should work and is supported as the
updated versions of the Domino directory template are designed to be backwards
compatible with previous versions of Lotus Domino (albeit only to a certain number of
previous versions) but it would be good practice to test this first in your own environment.
Especially to ensure that the latest version of the Domino directory template is backwards
compatible with all the older versions of Lotus Domino you have.
Just upgrade your Lotus Notes Traveler servers to use the latest version of Lotus Domino
and prevent the new design elements of updated Domino directory template replicating
out to the other, older, Lotus Domino servers in your Lotus Domino domain.
24 IBM Notes Traveler Hints and Tips for a Successful Deployment
If you place your Lotus Notes Traveler servers in their own dedicated Lotus Domino domain
instead then you can upgrade them to the latest version of Lotus Domino without having to
worry about the design of the Domino directory replicating to any other/older Lotus Domino
servers. More details on Lotus Domino domain planning can be found in 2.6, Domino domain
configuration on page 44.
2.1.4 Server hardware requirements
The operating system that is used for the Lotus Notes Traveler server should be a 64-bit
version. The Lotus Notes Traveler server does not copy the user mail files from the Lotus
Domino mail server to the Lotus Notes Traveler server, but moves the data through the server
as required during synchronization. The Lotus Notes Traveler server must maintain the
memory needs for the data transferring from the Lotus Domino mail server to all the end user
devices, and this can be thought of as a "pipeline" from the mail server to the device through
the memory of the Lotus Notes Traveler server. The number of data connections that are in
use can also be extensive. To better manage the connections, Lotus Notes Traveler requires
resources from the operating system to maintain the amount of information needed to
oversee the connections. Therefore, it is recommended to run Notes Traveler on a 64-bit
operating system. Capacity will be severely limited if running Notes Traveler on a 32 bit OS.
The following table shows the hardware requirements for Lotus Notes Traveler:
Feature Requirement
Disk space Although you can run Notes Traveler with as little as 500MB of free
disk space, for production environments it is recommended to
maintain at least 5 GB of free disk space. Certain log actions can
suddenly use a lot of disk space, such as a memory dump. Running
low on disk space will cause file fragmentation and performance
issues. Running out of disk space will cause a server crash and
possibly loss of data.
A stand-alone server implementation of Lotus Notes Traveler
requires database space. Running a defragmentation on the
database on a regular interval might keep the size of this database
small. In 8.5.3 Upgrade Pack 1, the database management code is
improved and defragmentation should not be as necessary as it
was in the previous versions of the product.
To help with managing the space that if used by logging, you can
put in plan to use the command tell traveler log clear to clear the
logs on the server and reinitialize the logging. Note that running the
tell traveler log clear command will remove all previous runtime
logs on the server in regards to Lotus Notes Traveler directory
/traveler/logs (NTSUsage*, NTSActivity*, and NTSError* logs). If
you decide to do this as part of your maintenance you can plan
appropriately for your needed disk space.
Memory The minimum amount of free memory required to run Lotus Notes
Traveler is 512 MB. This is in addition to the memory needed for the
operating system, and Lotus Domino itself.
For production systems a minimum of 8 GB of system memory is
recommended. More may be required depending on how many
concurrent users / devices you wish to host. See 2.4, Capacity
planning on page 43 for more detail on memory concerns.
Chapter 2. Planning 25
2.1.5 Enterprise database requirements
Lotus Notes Traveler High Availability mode requires an enterprise database that is accessed
by all Lotus Notes Traveler servers in a common service pool. The following table shows the
enterprise databases that are supported. See the database product documentation for
information on their hardware and software requirements:
2.1.6 Server operating systems
The following table shows the supported operating systems (OS) for Lotus Notes Traveler:
Network protocols Lotus Notes Traveler supports any network supported by a device
that provides an HTTP/TCP or HTTPS/TCP connection between
the device and the Lotus Notes Traveler server. Examples include
GSM, GPRS, 802.11x, and WiFi. In addition, Lotus Notes Traveler
can utilize Short Messaging Service (SMS) for push notifications
instead of HTTP/HTTPS (for selected mobile device platforms).
The SMS is only used for notifications and HTTP/HTTPS is still
required for data transfer. For communication between the Lotus
Notes Traveler server and the Louts Domino mail servers, Notes
RPC is used (port 1352 by default).
Feature Requirement
Product Notes
DB2 for Linux, UNIX, and
Windows Enterprise Server
Edition 9.7, Fixpack 5 or higher
64-bit version recommended.
DB2 for Linux, UNIX, and
Windows Workgroup Server
Edition 9.7, Fixpack 5 or higher
64-bit version recommended.
A limited use license to IBM DB2 for Linux, UNIX, and Windows
9.7.0.4 Server Edition is included with the Lotus Notes Traveler
8.5.3 Upgrade Pack 1 release. This limited use license is provided
for customers who want to deploy a Lotus Notes Traveler High
Availability server and elect to use this entitled DB2 version as their
RDBMS solution. The DB2 license should not be used for any
purpose other than the support of Lotus Notes Traveler.
Microsoft SQL Server
Enterprise Edition 2008 SP1
CU1 or higher
64-bit version recommended.
Microsoft SQL Server
Enterprise Edition 2008 R2 SP1
CU1 or higher
64-bit version recommended.
Operating system Notes
Red Hat Enterprise Linux
(RHEL) 5 Server for x86 (32-bit)
32-bit operating systems are supported, but 64-bit operating
systems are strongly recommended for all deployments with a
significant number of users. This OS is supported for Lotus Notes
Traveler Standalone mode only.
Red Hat Enterprise Linux
(RHEL) 5 Server for x86 (64-bit)
Supports Domino server running in 32-bit application mode. This
operating system is supported for Lotus Notes Traveler Standalone
mode and High Availability mode.
26 IBM Notes Traveler Hints and Tips for a Successful Deployment
Red Hat Enterprise Linux
(RHEL) 5 Advanced Platform
for x86 (32-bit)
32-bit operating systems are supported, but 64-bit operating
systems are strongly recommended for all deployments with a
significant number of users. This OS is supported for Lotus Notes
Traveler Standalone mode only.
Red Hat Enterprise Linux
(RHEL) 5 Advanced Platform
for x86 (64-bit)
Supports Domino server running in 32-bit application mode. This
OS is supported for Lotus Notes Traveler Standalone mode and
High Availability mode.
Red Hat Enterprise Linux
(RHEL) 6 Server for x86 (32-bit)
32-bit operating systems are supported, but 64-bit operating
systems are strongly recommended for all deployments with a
significant number of users. This OS is supported for Lotus Notes
Traveler Standalone mode only.
Red Hat Enterprise Linux
(RHEL) 6 Server for x86 (64-bit)
Supports Domino server running in 32-bit application mode. This
OS is supported for Lotus Notes Traveler Standalone mode and
High Availability mode.
SUSE Linux Enterprise Server
(SLES) 10 for x86 (32-bit)
32-bit operating systems are supported, but 64-bit operating
systems are strongly recommended for all deployments with a
significant number of users. This OS is supported for Lotus Notes
Traveler Standalone mode only.
SUSE Linux Enterprise Server
(SLES) 10 for x86 (64-bit)
Supports Domino server running in 32-bit application mode. This
OS is supported for Lotus Notes Traveler Standalone mode and
High Availability mode.
SUSE Linux Enterprise Server
(SLES) 11 for x86 (32-bit)
32-bit operating systems are supported, but 64-bit operating
systems are strongly recommended for all deployments with a
significant number of users. This OS is supported for Lotus Notes
Traveler Standalone mode only.
SUSE Linux Enterprise Server
(SLES) 11 for x86 (64-bit)
Supports Domino server running in 32-bit application mode. This
OS is supported for Lotus Notes Traveler Standalone mode and
High Availability mode.
Windows Server 2003
Enterprise Edition x86 (32-bit)
32-bit operating systems are supported, but 64-bit operating
systems are strongly recommended for all deployments with a
significant number of users. This OS is supported for Lotus Notes
Traveler Standalone mode only.
Windows Server 2003 R2
Enterprise Edition x86 (32-bit)
32-bit operating systems are supported, but 64-bit operating
systems are strongly recommended for all deployments with a
significant number of users. This OS is supported for Lotus Notes
Traveler Standalone mode only.
Windows Server 2003
Enterprise Edition x86 (64-bit)
This OS is supported for Lotus Notes Traveler Standalone mode
and High Availability mode.
Windows Server 2003 R2
Enterprise Edition x86 (64-bit)
This OS is supported for Lotus Notes Traveler Standalone mode
and High Availability mode.
Windows Server 2003
Standard Edition x86 (32-bit)
32-bit operating systems are supported, but 64-bit operating
systems are strongly recommended for all deployments with a
significant number of users. This OS is supported for Lotus Notes
Traveler Standalone mode only.
Windows Server 2003 R2
Standard Edition x86 (32-bit)
32-bit operating systems are supported but, 64-bit operating
systems are strongly recommended for all deployments with a
significant number of users. This OS is supported for Lotus Notes
Traveler Standalone mode only.
Operating system Notes
Chapter 2. Planning 27
2.1.7 Web browsers for administration
Lotus Notes Traveler supports web based administration through XPages. You can use this
administration tool in place of the lotustraveler.nsf that was previously used in the Lotus Notes
Traveler servers. For the high availability implementation of the server, the web administration
is required as it is no longer possible to administrate the Lotus Notes Traveler environment
using the lotustraveler.nsf database after the move to HA mode has been completed. The
following web browsers are supported in this capacity:
Apple Safari 5.0 and higher
Mozilla Firefox 3.6 and higher
Microsoft Internet Explorer 7 and higher
Google Chrome 5 and higher
2.1.8 IP sprayer
Lotus Notes Traveler, running in High Availability mode, requires an IP sprayer located in front
of the Lotus Notes Traveler server pool to provide a single URL entry point and to route
requests evenly among the members of the pool. IP sprayer support has been tested with, but
not limited to, the following:
Apache HTTP Server v2.2.22
WebSphere Edge Server v7.0.0.18
Windows Server 2003
Standard Edition x86 (64-bit)
This OS is supported for Lotus Notes Traveler Standalone mode
and High Availability mode.
Windows Server 2003 R2
Standard Edition x86 (64-bit)
This OS is supported for Lotus Notes Traveler Standalone mode
and High Availability mode.
Windows Server 2008
Enterprise Edition x86 (32-bit)
32-bit operating systems are supported, but 64-bit operating
systems are strongly recommended for all deployments with a
significant number of users. This OS is supported for Lotus Notes
Traveler Standalone mode only.
Windows Server 2008
Enterprise Edition x86 (64-bit)
This OS is supported for Lotus Notes Traveler Standalone mode
and High Availability mode.
Windows Server 2008 R2
Enterprise Edition x86 (64-bit)
This OS is supported for Lotus Notes Traveler Standalone mode
and High Availability mode.
Windows Server 2008
Standard Edition x86 (32-bit)
32-bit operating systems are supported, but 64-bit operating
systems are strongly recommended for all deployments with a
significant number of users. This OS is supported for Lotus Notes
Traveler Standalone mode only.
Windows Server 2008
Standard Edition x86 (64-bit)
This OS is supported for Lotus Notes Traveler Standalone mode
and High Availability mode.
Windows Server 2008 R2
Standard Edition x86 (64-bit)
This OS is supported for Lotus Notes Traveler Standalone mode
and High Availability mode.
Operating system Notes
Important: JavaScript and cookie support must be enabled in the web browser for the
Lotus Notes Traveler web administration application to function properly.
28 IBM Notes Traveler Hints and Tips for a Successful Deployment
Lotus Mobile Connect (LMC) v6.1.5
2.1.9 Device hardware requirements
The following table shows the hardware requirements for the mobile devices that are
supported by Lotus Notes Traveler:
Feature Applicable OS Notes
Device memory Nokia Series 60 3rd and 5th
edition
Nokia Symbian^3
Lotus Notes Traveler for Nokia S60 client requires approximately 4
MB of free program file storage on the device to install Lotus Notes
Traveler.
File storage required for PIM and mail is not included in these
estimates, varies widely, and depends on how much data is
synchronized to the device.
If it is necessary to collect traces or logs, up to 2 MB of additional
program file storage may be needed.
If the installation file (SISX file) is manually downloaded to program
file storage, it requires an additional 1 MB. This file can be deleted
after installation.
If mobile device security policies are in place or support for remote
device wipe is needed, and you are using a Nokia S60 device, it may
be necessary to install the Nokia security enablement library on the
device. This library can be obtained from
download.fds-ncom.nokia.com/supportFiles/phones/files/pdf_guides
/services/IBM_TTPA_Allow_New_App/IBMTTPAAllowNewApp.SIS
Device memory Windows Mobile 6.0, 6.1,
and 6.5
Lotus Notes Traveler for Windows Mobile client requires
approximately 4 MB of free program file storage on the device to
install Lotus Notes Traveler.
File storage required for PIM and mail is not included in these
estimates, varies widely, and depends on how much data is
synchronized to the device.
If it is necessary to collect traces or logs, up to 2 MB of additional
program file storage may be needed.
If the cabinet install file (CAB file) is manually downloaded to program
file storage, it requires an additional 2 MB. This CAB file can be
deleted after installation.
Device memory Android Lotus Notes Traveler for Android client requires approximately 2 MB
of free storage on the device to install Lotus Notes Traveler.
File storage required for PIM and mail is not included in these
estimates, varies widely, and depends on how much data is
synchronized to the device. Note that during initial setup, you can
choose to have some of the data stored on external storage.
Trace and log storage required is dependent upon the configuration
setting. The default value is 2 MB.
Chapter 2. Planning 29
2.1.10 Devices and operating systems
The following table shows the mobile device operating systems that are supported by Lotus
Notes Traveler:
Device/Operating
System
Notes
Apple iPhone OS 2 Not supported. For reliable operation with Lotus Notes Traveler, upgrading to
version 3.1 firmware or higher is required.
Apple iPhone OS 3 IBM strongly encourages upgrading to version 3.1 firmware or higher for use
with Lotus Notes Traveler.
Apple iOS 4 IBM strongly encourages upgrading to version 4.0.1 firmware or higher for
use with Lotus Notes Traveler.
Apple iOS 5 IBM Lotus Notes Traveler supports the same mail, calendar and contact
features in iOS5 that are supported in iOS4. New capabilities in iOS5 (e.g.
Reminders) are not supported by Lotus Notes Traveler, but will be
considered for utilization and support in a future release.
Apple iOS 6 IBM Lotus Notes Traveler supports the same mail, calendar and contact
features in iOS6 that are supported in iOS5.
iPhone, iPhone 3G,
iPod Touch (2nd
generation)
Supported. Note that these devices do not include on-device encryption.
iPhone 3GS, iPhone
4, iPhone 4S, iPad,
iPad2, iPad3, iPod
Touch (3rd
generation and
higher)
Supported.
Nokia Series 60 3rd
Edition
Lotus Notes Traveler supports all Nokia Series 60 3rd and 5th edition
devices.
For a list of Nokia devices that support the Nokia security enablement library
for remote security features see
download.fds-ncom.nokia.com/supportFiles/phones/files/pdf_guides/servic
es/IBM_TTPA_Allow_New_App/IBMTTPAAllowNewApp.SIS
Nokia Series 60 3rd
Edition Feature Pack
1
Nokia Series 60 3rd
Edition Feature Pack
2
Nokia Series 60 5th
Edition
Nokia Symbian^3
Edition
Device encryption is only supported by Symbian^3 devices and they must be
running an operating system level of Symbian Anna release or higher.
Nokia Symbian^3 devices do not require a separate download of the Nokia
security library required for S60 devices. This support is built into the device.
30 IBM Notes Traveler Hints and Tips for a Successful Deployment
What does IBM do internally?
The IBM internal implementation of Lotus Notes Traveler is currently based on a mixture of
Windows and Linux based servers, but a project is underway to migrate to using Linux only.
All of servers are run as virtual 'guests' on a VMware 4.5.1 Enterprise environment. The
specifications of the virtual guests are as follows:
Windows VMware guest specifications:
4 vCPUs
8GB - 12GB of memory (the most heavily utilized servers were upgraded from 8 GB to 12
GB)
Windows 2008 R2 64-bit
Windows Mobile 6.0
Classic
Lotus Notes Traveler supports all Windows Mobile 6.0, 6.1, and 6.5 devices.
Windows Mobile 6.0
Professional
Windows Mobile 6.0
Standard
Windows Mobile 6.1
Classic
Windows Mobile 6.1
Professional
Windows Mobile 6.1
Standard
Windows Mobile 6.5
Professional
Windows Mobile 6.5
Standard
Android OS 2.0.1+ Lotus Notes Traveler supports all devices, including tablets, running Android
OS 2.0.1 to 2.x. Note that if you wish to use enterprise security features, such
as complete device wipe or device password policies, you must be running
Android OS 2.2 or higher.
Android OS 3.0+ Lotus Notes Traveler supports all devices, including tablets, running Android
OS 3.0 or higher. This version is required for enablement of some Android
security features, including: Complex character device password support,
device password expiration, device password history count and whole device
encryption.
Android OS 4.0+ Lotus Notes Traveler supports all devices, including tablets, running Android
OS 4.0 or higher. This version supports all Android security features from
previous Android releases and adds support for Prohibit Camera.
Important: IBM recommends upgrading the firmware of all Android, Apple, Nokia, and
Windows Mobile devices to the latest levels. The specific delivery technique varies widely
and depends on the device, the carrier, and many other factors.
Device/Operating
System
Notes
Chapter 2. Planning 31
SAN hosted disks with separate volumes for the operating system (C:), program binaries
(D:) and log files (E:).
Linux VMware Guest Specifications:
4 vCPUs
8GB memory
Redhat 6 Enterprise Server
SAN hosted disks with separate file systems and mount points for the operating system,
program binaries and log files.
For details of how many users IBM host on Lotus Notes Traveler servers of this specification,
see 2.4, Capacity planning on page 43.
2.2 Choosing a stand-alone or high availability configuration
for Lotus Notes Traveler
When deciding to deploy IBM Lotus Notes Traveler version 8.5.3 Upgrade Pack 1, a number
of questions should be asked in regards to using the high availability (HA) option or the
stand-alone option. By default, the installation of 8.5.3 Upgrade Pack 1 is a stand-alone
server. It is not until you want to configure Lotus Notes Traveler for HA that an enterprise
database and a 'front-end' IP sprayer are required.
The two main influencing factors to choosing a stand-alone server versus an HA Lotus Notes
Traveler implementation are:
The number of devices Lotus Notes Traveler is to service
The need for continuous availability or fail-over capability if a Lotus Notes Traveler server
instance becomes unavailable.
Other factors are also discussed after we address these main two concerns.
2.2.1 Number of devices
Lotus Notes Traveler 8.5.3 Upgrade Pack 1 has improved the server capability to manage
memory and data in the servers. With this improvement, the server performs faster and
maintains better data organization in the Lotus Notes Traveler databases. These are either
the local derby databases that are used by Lotus Notes Traveler in stand-alone mode, or the
enterprise databases that are used in the HA mode. The improvement was largely due to the
improvement, and refactoring of many of the SQL queries that are used, and adjustments to
the tables that are contained in the Lotus Notes Traveler databases. Because of these
important factors, if your current implementation of Lotus Notes Traveler is providing service
for 2,000 devices or less, then a stand-alone server with 8.5.3 Upgrade Pack 1 (of the correct
specification) would be sufficient if you do not need your Lotus Notes Traveler server to be
highly available.
Important: If using a Virtual System environment, a dedicated storage such as SAN
hosted disks used by IBM is important. Running Notes Traveler in stand alone mode is very
disk IO heavy. Often times Virtual Machines are not given sufficient disk priority to perform
at maximum capacity. In HA mode much of the disk processing is moved to the database
server, and it is this server that disk IO speed will be critical.
32 IBM Notes Traveler Hints and Tips for a Successful Deployment
If you plan to support more than 2,000 devices, using the HA environment is your best option.
A single Lotus Notes Traveler 8.5.3 Upgrade Pack 1 server in an HA configuration can service
up to approximately 2,500 devices on a single server. For any additional devices above this
number, another server is required to handle the load. A single HA server pool (consisting of
multiple Lotus Notes Traveler servers, all configured in HA mode) can support approximately
10,000 devices. The basic rule of thumb is that the number of servers required in a Lotus
Notes Traveler HA server pool is 1 + the number of servers needed to serve the load. For
example, if you were to implement an environment that was intended to serve 5,000 users,
you would need 3 Lotus Notes Traveler servers. The additional server is required so that if
one of the servers in the pool failed, all of the devices can still be serviced by the remaining
servers in the pool without degrading the quality of the service. Note that all of the servers in
a HA pool are always used in normal circumstances so the additional server is utilized all of
the time.
2.2.2 System availability consideration
If you wish to ensure that the Lotus Notes Traveler solution has continuous availability, then
the HA option is the solution that must be used.
If you are implementing a HA solution you need to ensure that all of the components that
make up the end to end Lotus Notes Traveler server are also high availably. As such the other
aspects of the solution that need to be considered and have a high availability solution of their
own include:
A HTTP/IP Sprayer or load balancer server
A Lotus Domino mail server (for example, use Lotus Domino clustering)
A high availability solution for the enterprise database
2.2.3 Other considerations
The other considerations of using an HA solution include:
Server resource constraint:
If your servers has a maximum of 8 GB memory only, the HA solution allows you to have
multiple severs. With multiple servers you can handle a higher load with fewer devices on
each server. Thus, you are able to service more devices with more machines when the
machines are restricted on the resources they are allotted. This is more common in a VM
environment.
Network constraint:
If the internal network speed is not fast, or bandwidth is a limitation, consider the
stand-alone solution if you do not need a HA solution according to the first two points
described in this section. In a stand-alone configuration, all the resources are local and
there is no traffic from the HTTP/IP Sprayer to the Lotus Notes Traveler server to the
enterprise database server and back within the network.
2.2.4 What does IBM do internally?
At the time of writing, the IBM internal implementation of Lotus Notes Traveler is comprised
entirely of stand alone Lotus Notes Traveler servers.
Chapter 2. Planning 33
2.3 Planning your server and network topology
When planning the server and network topology for a Lotus Notes Traveler environment, there
are a number of key points that you should consider:
On which Lotus Domino servers should you install Lotus Notes Traveler?
Does your Lotus Notes Traveler environment need to be highly available?
How will the user mobile devices, which are typically on an external mobile data network,
connect to your Lotus Notes Traveler server?
How will your Lotus Notes Traveler server connect to the Lotus Domino servers hosting
the users mail files?
2.3.1 Choosing a Lotus Domino server
It is advisable to use a dedicated Lotus Domino server for hosting Lotus Notes Traveler that is
not used for performing any other role (for example, mail server, routing hub, and so on). This
configuration not only maximizes the number of users that the Lotus Notes Traveler server
can host, but also has other advantages such as being able to apply Lotus Notes Traveler
specific configuration and tuning settings, enabling the server to be upgraded easier, and
giving you more flexibility as to where you place your Lotus Notes Traveler servers in your
network topology.
2.3.2 High availability or stand-alone
Implementing high availability for your Lotus Notes Traveler environment is a decision you
have to make based on how critical the service is to your business. A high availability solution
means that your users can continue to use the Lotus Notes Traveler service even in the event
of an outage. However, it does increase the complexity of the overall Lotus Notes Traveler
environment, so, if the availability of the Lotus Traveler service is not considered to be
business critical, you have the choice of implementing a simpler stand-alone solution
instead.
2.3.3 Connectivity
There are three different approaches to providing the necessary connectivity between Lotus
Notes Traveler, the users, and their respective mail servers. However, the implementation of
each varies slightly depending on if you also want to enable High Availability (HA). All three
variants work in a HA configuration, so the decision on whether to use HA does not restrict
which of the three approaches you can use. The three approaches are described in more
detail in the following sections, including details of the pros and cons of each to help you
choose which is best suited to your own environment.
Option one: A direct connection solution
In a direct connection topology, the Lotus Notes Traveler server is placed in a network
de-militarized zone (DMZ) that enables the Notes Traveler to connect directly to internet using
the "front" firewall of the DMZ. The Lotus Notes Traveler is able to access to the Lotus Domino
mail server through the "back" firewall of the DMZ.
This topology is shown in the following figure:
34 IBM Notes Traveler Hints and Tips for a Successful Deployment
Why use a direct connect solution?
As a direct connect based solution is the quickest and easiest to implement, it is often used in
an initial pilot or proof of concept of Lotus Notes Traveler. However, even in these
circumstances, you still have to ensure the servers are sufficiently secured before exposing
them to internet, especially if they will be synchronizing data from your production
environment.
Implementing High Availability in a direct connect solution
When implementing high availability (HA) in a direct connect solution, the pool of HA Lotus
Notes Traveler servers is placed in the DMZ so that all of the servers in that pool can be
accessed from the internet. This pool of servers is then addressed using either a simple
round robin DNS entry that contains an entry for all the servers in the pool or using a
separate IP sprayer server, depending on how you implement the load balancing part of the
HA solution (2.14, Mobile device management integration on page 63 for more details on
load balancer considerations). Because the HA solution for Lotus Notes Traveler also requires
an enterprise database server (either IBM DB2 for Linux, UNIX, or Windows or Microsoft SQL
Server) that is hosted on the internal network, an additional rule on the "back" firewall of the
DMZ is required to enable connectivity between the Lotus Notes Traveler server and the
database server.
The following figures show the topology for a direct connect solution with HA using both round
robin DNS and an IP sprayer:
Chapter 2. Planning 35
Lotus Notes Traveler direct connection with high availability via round robin DNS:
36 IBM Notes Traveler Hints and Tips for a Successful Deployment
Lotus Notes Traveler direct connection with high availability using an IP sprayer:
Advantages of a direct connect solution
The main advantage of the direct connection solution is that it is the simplest and quickest to
implement. All that is required is a network DMZ and a new server upon which to host Lotus
Notes Traveler.
Disadvantages of a direct connect solution
The main disadvantage of the direct connection solution is that it is the least secure because
it exposes the Lotus Notes Traveler server (and the Lotus Domino server hosting it) to the
internet.
The front firewall of the DMZ only requires the HTTPS port to be opened (443) but this allows
all external web browser traffic to connect to the Lotus Notes Traveler server. This means the
operating system, the Lotus Domino server, and the Lotus Notes Traveler server all must be
properly hardened to make sure they are secure. These servers also must be patched
regularly to ensure they remain secure.
If using a direct connect solution, consider deploying your Lotus Notes Traveler server in a
separate Lotus Domino domain to the Lotus Domino mail servers to increase the level of
security at the Domino layer. This implementation prevents the servers on your main Domino
domain (and the data they host, such as the Domino directory etc) from being exposed
directly to the internet. For more details on implementing Lotus Notes Traveler in a separate
Lotus Domino domain, see 2.6, Domino domain configuration on page 44.
Another disadvantage of the direct connect solution is that Lotus Notes document links will
not work in Lotus Notes Traveler unless additional configuration is implemented to support it
(e.g. opening more firewall rules between the Lotus Notes Traveler servers and the Lotus
Chapter 2. Planning 37
Domino Mail servers). So if a user receives an email that contains a link to another document
hosted somewhere in the Lotus Notes environment, they cannot use that link. This is
because, although Lotus Notes Traveler does support Lotus Notes document links, the Lotus
Domino server hosting the document that the link points to must be both HTTP enabled and
accessible on the network to the user device through HTTP. In a direct connection solution, by
default only the Lotus Notes Traveler server itself is accessible to the user device. So if being
able to use Lotus Notes document links via Lotus Notes Traveler is required, it would also be
necessary to implement the network layer configuration changes to provide the connectivity
between the Lotus Notes Traveler server and the Lotus Domino mail servers for it to work.
Option two: A reverse proxy solution
In a reverse proxy based solution, the Lotus Notes Traveler server is placed in your internal
network and a reverse proxy server is placed in a network de-militarized zone (DMZ). The
connectivity between the user device and the Lotus Notes Traveler server is handled by proxy
server, so the device only ever connects directly to the proxy server and then the proxy server
(transparently) provides the connectivity to the Lotus Notes Traveler server. As the Lotus
Notes Traveler server is on the internal network, there are no connectivity restrictions
between it and the Lotus Domino mail servers.
The following figure shows this topology:
Why use a reverse proxy solution?
A reverse proxy based solution negates some of the security risks associated with the direct
connect solution, but is generally easier and cheaper to implement than a Virtual Private
Network (VPN) based solution. As such, it is a good choice if you want to implement a
solution with strong security but do not want the complexity and cost associated with
38 IBM Notes Traveler Hints and Tips for a Successful Deployment
implementing a separate VPN infrastructure. If implementing a HA solution, you also have the
option to use a combined proxy and IP sprayer server to provide the required functionality
with the minimum number of servers.
Implementing high availability in a reverse proxy solution
When implementing high availability (HA) in a reverse proxy solution, rather than connecting
to the Lotus Notes Traveler server, the proxy server connects to an IP Sprayer located on the
internal network instead. That IP Sprayer then passes the connection from the user device on
to one of the Lotus Notes Traveler servers in the HA pool. Alternatively, if you use a proxy
server that supports a load balancing/IP spraying capability (such as IBM Mobile Connect), it
is also possible to combine the IP spraying function with the reverse proxy meaning that the
reverse proxy performs both of these roles, reducing the number of server instances required
to provide the Lotus Notes Traveler infrastructure.
As the Lotus Notes Traveler servers are located on the internal network, they can connect
directly to the enterprise database server that is also required in a HA configuration.
The following figures are examples of reverse proxy topology using both a separate IP
sprayer and a combined IP sprayer and proxy:
Lotus Notes Traveler reverse proxy connection with high availability using a separate IP
sprayer:
Chapter 2. Planning 39
Lotus Notes Traveler reverse proxy connection with high availability using combined proxy
and IP sprayer:
Advantages of a reverse proxy solution
The main advantage of the reverse proxy solution is that the Lotus Domino server running
Lotus Notes Traveler is no longer directly connected to the external internet, reducing the
security risks associated of exposing the data hosted on these servers and thus making the
overall solution more secure.
Another advantage of this solution is that if you configure Single Sign On (SSO)
authentication between the proxy server and the Lotus Notes Traveler server, you can off load
much of the user authentication processing to the proxy server. This can potentially improve
the performance of your Lotus Traveler server as it will only process users who have already
authenticated successfully with the proxy server. Configuring SSO is described in more detail
in 7.2, Configuring single sign-on on page 297.
Disadvantages of a reverse proxy solution
The main disadvantage of the reverse proxy solution is that it increases the number of server
instances that make up the Lotus Notes Traveler environment. This topology also increases
the complexity as a separate proxy server is required, requiring additional skills to support the
reverse proxy server and additional configuration to integrate the reverse proxy server with
Lotus Notes Traveler. However, the benefit of the additional security a reverse proxy solution
offers will generally outweigh this disadvantage in the majority of circumstances.
Another disadvantage is that the reverse proxy solution only provides connectivity to the
Lotus Notes Traveler servers themselves and not to anything else on the internal network.
40 IBM Notes Traveler Hints and Tips for a Successful Deployment
This means that the users cannot access other applications or data on the internal network,
such a browsing intranet web pages or using Sametime.
A further disadvantage is that, just like the direct connect solution, Lotus Notes document
links will not work in Lotus Notes Traveler unless additional configuration is implemented to
support it (e.g. opening more firewall rules between the Lotus Notes Traveler servers and the
Lotus Domino Mail servers). This is because, although Lotus Notes Traveler does support
Lotus Notes document links, the Lotus Domino server hosting the document that the link
points to must be both HTTP enabled and accessible on the network to the users device via
HTTP. In a reverse proxy solution typically only the Lotus Notes Traveler server itself is
accessible to the users device, via the connectivity provided by the proxy server. So if being
able to use Lotus Notes document links via Lotus Notes Traveler is required, it would also be
necessary to implement the network layer configuration changes to provide the connectivity
between the Lotus Notes Traveler server and the Lotus Domino mail servers for it to work.
Option three: A virtual private network solution
In a virtual private network (VPN) based solution, a VPN connection (tunnel) is established
between the users mobile device and the internal network, through a VPN server located in
the network de-militarized zone (DMZ). Once this VPN connection is established, the users
mobile device is effectively connected the internal network and has direct connectivity to all of
the servers located on it. All of the network traffic between the mobile device and the internal
network is sent through the VPN connection, which is normally encrypted as well. This means
that all of the Lotus Notes Servers can be located on the internal network and, once a VPN
connection is established, the user mobile devices can connect directly to them.
The following figure shows the topology of the virtual private network solution:
Chapter 2. Planning 41
Why use a Virtual Private Network solution?
A VPN based solution not only negates the security risks associated with the direct
connection solution, but also has the advantage over a reverse proxy solution of connecting
the mobile device to more of the internal network rather than just the Lotus Notes Traveler
server. This makes the VPN based solution a better solution if you want to have mobile
devices to connect securely to more than just Lotus Notes Traveler. It is also a good solution if
you want to be able to use Lotus Notes document links in Lotus Notes Traveler.
Implementing high availability in a virtual private network solution
When implementing high availability (HA) in a virtual private network, the pool of HA Lotus
Notes Traveler servers are located on the internal work along with a separate IP sprayer. The
users devices are then able to connect directly to the IP sprayer through the VPN connection
(once it has been established).
The following figure shows the topology of virtual private network with HA:
Advantages of a virtual private network solution
The main advantage of the virtual private network solution is that the VPN connection
between the user mobile device and the internal network can be used for more than just
accessing Lotus Notes Traveler. So it can also be used to access your internal intranet or
other internal applications (for example, Sametime). Because the VPN connection is normally
encrypted, all of these accesses can be done securely well.
Another advantage of a VPN based solution is that, just as with the reverse proxy solution, the
Lotus Domino and Lotus Notes Traveler servers are no longer directly connected to the
external internet. Therefore, the security risks associated with exposing the data hosted on
these servers is reduced, thus making the overall solution more secure.
A VPN solution is also a good solution for Lotus Notes document links to be usable in Lotus
Notes Traveler. This is because the user mobile device will be able to use the VPN to connect
42 IBM Notes Traveler Hints and Tips for a Successful Deployment
to the Lotus Domino server hosting the document that the link points to, although that Lotus
Domino server will still need to be HTTP enabled for the link to be accessible through Lotus
Notes Traveler.
Disadvantages of a virtual private network solution
There are three main disadvantages of using a virtual private network solution. The first is the
complexity and potential cost of implementing and supporting the additional VPN
infrastructure itself, which of three different connectivity solutions for Lotus Notes Traveler is
probably the highest.
The second is that in order for Lotus Notes Traveler to sync, the user device must first have a
VPN connection established. Although many modern mobile devices now support VPN
connections natively, some might still require a separate VPN client to be installed.
Regardless of the device type and VPN client used, Lotus Notes Traveler cannot
automatically establish the VPN connection itself when Notes Traveler needs the connection.
Therefore, if the VPN connection is not already established, Lotus Notes Traveler cannot
synchronize data to the device. This is a significant drawback compared to a reverse proxy
based solution because in that, Lotus Notes Traveler is always able to connect to the proxy
server (assuming there is a data network connection available) so synchronization always
occur automatically without the need for the user to ensure a separate network connection is
enabled.
The third disadvantage is that Apple does not send the push messages over a VPN
connection. This means that all iOS devices will not receive any push notifications from Apple.
Email synchronisation does work (so users can still get their email) but it will not be possible
to automatically push anything to the user's devices. Note that this limitation only applies to
Apple and iOS devices in a VPN implementation.
What does IBM do internally?
The IBM internal implementation of Lotus Notes Traveler uses a reverse proxy based solution
based on IBM Mobile Connect (IMC). The IMC and Lotus Notes Traveler servers are
configured to use Single Sign On (SSO), so the users only authenticate with the IMC servers.
Further reading on planning your server and network topology
The following articles provide more information on planning your server and network
topology:
Planning your server topology -
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Planning_your_server_topology_A85
3UP1
Planning your network topology -
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Planning_your_network_topology_A8
53UP1
Direct connection -
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Direct_connection_A853UP1
Using a reverse proxy -
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Using_a_reverse_proxy_A853UP1
Using a virtual private network -
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Using_a_virtual_private_network_A
853UP1
Chapter 2. Planning 43
2.4 Capacity planning
Sizing the servers for a Lotus Notes Traveler implementation can be challenging because
there are a number of different factors that must be considered. When considering the
capacity of a Lotus Notes Traveler server system, you need to consider the processor,
memory, disk space, and network requirements of the software that will be hosted on the
system. A Lotus Notes Traveler server system must have Lotus Notes Traveler itself installed,
and a Lotus Domino Server with the HTTP task enabled regardless the topology you are
using for your Lotus Notes Traveler environment. When planning the over all server capacity,
you also need to consider any future expansion of service to new users.
For the capacity planning guidelines, see
http://www-10.lotus.com/ldd/dominowiki.nsf/xpDocViewer.xsp?lookupName=Administerin
g+Lotus+Notes+Traveler+8.5.3+Upgrade+Pack+2#action=openDocument&res_title=Capacity
_planning_guidelines_for_Lotus_Notes_Traveler_A853UP2&content=pdcontent
The best is to open a case with IBM TechLine and have a team come on-site or preform
remote analysis to evaluate your business requirements and provide you the system
requirements. For details on how to request this service work with your IBM sales
representatives for further information, this service is not always a paid engagement.
2.5 Catering for user with multiple devices
By default, Lotus Notes Traveler allows an unlimited number of devices per user to connect to
the Lotus Notes Traveler server. Many users will have multiple devices, a mobile phone and a
tablet for example. In addition, you may want to allow users to "Bring Your Own Device"
(BYOD), and therefore users may also get their Personal Information Management (PIM) data
on additional devices, such as their personal mobile phone, personal tablet, or devices owned
by their spouse. Unregulated, this can present a multitude of problems for the Lotus Notes
Traveler administrator and management. It will also have an impact on your server sizing and
capacity planning, because the performance of a Lotus Notes Traveler server is affected by
the number of active devices with which it has to synchronize, rather than the number of
registered users. To help manage this, It is possible to optionally configure Lotus Notes
Traveler to restrict the number of devices each user is permitted. As such, a decision should
be made on the number of mobile devices you wish to allow per user.
If you want to maximize the number of users a single Lotus Notes Traveler server can support
then set this number to one. If you are willing to provide additional server capacity to allow
users to have multiple devices then you can set this number higher. A value of two would
allow users to have both a smart phone and a tablet device. However be aware that in setting
a device limit, there will be some overhead on your Lotus Notes Traveler administrators to
manage requests from users who are changing or swapping devices as they won't be able to
register their new device until their old one is either removed by an Administrator or
automatically deleted after a period of inactivity to free up one of their permitted device quota.
As such you may wish to consider setting the limit to 3 devices (or higher) so that a user can
have 2 active devices at any one time plus a spare quota to allow the migration to a new
device without having to request any administrator support. You also have the option of not
setting any device limit at all, but be aware that in doing so you are allowing users to register
as many devices as they wish which could cause issues with server performance and
capacity planning as previously stated.
Administrators also must consider the amount of resources on the Lotus Notes Traveler
server that will be consumed by each additional device. The addition of each device will
44 IBM Notes Traveler Hints and Tips for a Successful Deployment
require the use of more memory, processor cycles, and storage. A Lotus Notes Traveler
server is limited to a finite number of devices it can handle, depending on the processors and
memory on the server, and the amount of mail the users maintain on the device. Remember
that this is a per mobile device resource, not per user and each device's state information is
maintained separately by the Lotus Notes Traveler server from all the other devices owned by
a user.
Each mobile device will also create a demand for services on the Lotus Domino Mail servers.
When a mobile device connects to a Lotus Notes Traveler server, it will prompt the Note
Traveler server to poll the Mail server every three seconds, by default settings, for any
changes that needs to be synched with the mobile device. This is approximately the same
amount of demand on the mail server as when a user connects directly to the mail server for
their PIM data. Each time a new device is registered, there is no additional polling required,
but there will be additional load on the mail servers as these devices perform synchronization.
So be aware that allowing users to have multiple devices will increase the load on your Lotus
Domino Mail server as well.
Lotus Notes Traveler provides a setting that can be utilized to allow a device to connect only
after approval from an administrator, or set to allow a certain number of devices for a user
before approval is required for additional devices to connect. You can use these settings to
help you manage how many devices a user can have configured for use with Lotus Notes
Traveler. See 8.2.2, Device settings on page 309 for information on how to set up a limit on
the number of devices.
2.5.1 What does IBM do internally?
In the IBM internal implementation of Lotus Notes Traveler, users are not restricted on the
number of devices they are allowed to use (i.e. users are permitted multiple devices). To
accommodate this, the number of registered users each Lotus Notes Traveler server supports
is less than its maximum so that there is spare capacity for users with multiple devices. On
average, we see approximately 15% - 20% more devices on each server than we have
registered users.
2.6 Domino domain configuration
You can install the IBM Lotus Notes Traveler server in the same Domino domain as your
mail servers or install in it's own isolated Domino Domain. Installing in the same domain as
mail servers simplifies the setup but can complicate upgrade process as many customers
upgrade their Traveler servers more frequently than their mail servers. If installing the Notes
Traveler server in the DMZ then you should always install in an isolated Domino domain to
improve security and limit the information stored in the local names.nsf in the DMZ. For more
on network setups see 2.3, Planning your server and network topology on page 33.
The following checklist covers all Notes Traveler setups, however when installing in the same
domain as the mail servers, many of these items come for free. If installing in an isolated
Domino Domain or your company has multiple Domino Domains, be sure to ensure all of
these items are satisfied.
The Lotus Notes Traveler server must be able to physically connect to mail servers in the
other domains.
The server ID file used by the Lotus Notes Traveler server must be cross-certified with any
other Domino domains that the Lotus Notes Traveler server needs a connection to.
Chapter 2. Planning 45
The remote mail servers must grant server access to the Lotus Notes Traveler server.
Generally this is best accomplished by putting the Traveler server in the
LocalDomainServers group.
The user's mail file must grant manager plus delete access to the Lotus Notes Traveler
server. Generally this is best accomplished by putting the Traveler server in the
LocalDomainServers group.
The Notes Traveler server must have access to the Domino directory or LDAP server
being used for User information storage and authentication. If not the local names.nsf then
Directory assistance must be used to point to this directory or directories.
The Domino directory or LDAP server must be capable of returning the home mail server
and the mail file path name for each user that registers with the Lotus Notes Traveler
server. If using an LDAP server that does not contain the mail server information, it must
return a unique distinguished name or internet address that can be used to find the mail
server when performing a lookup against the local names.nsf or Domino directory
specified by Directory Assistance.
If you are using multiple Domino domains and plan on implementing mobile security
policies, it is easier to use Lotus Notes Traveler default settings to define security policies
rather than use Lotus Notes Traveler policy settings documents that are part of the
Domino administration policy setup. If using Lotus Notes Traveler policy documents, you
have to define the policy settings separately in every different Domino domain for them to
work properly. If you are using Lotus Notes Traveler default settings, then these settings
and security policies apply to any user that connects to the Lotus Notes Traveler server
regardless of the Domino domain the user belongs to. For more information, see 8.2.2,
Device settings on page 309.
It is possible to have a Lotus Notes Traveler server or a Traveler High Availability pool
supporting mobile users in multiple Domino domains. The configuration changes required are
same as above: cross-certification of the domains, update security access in server
document, and configure Directory Assistance on Traveler server to authenticate with all the
domains or make available the person records locally.
Considerations when choosing single or multiple domain configuration:
Lotus Traveler and Domino mail servers in same domain:
Generally for smaller companies, who only have one mail domain.
Simpler Administration and Maintenance of the Domain, with replication and mail routing.
Common Server configuration documents and program documents in the same domain
keep the configuration easy to maintain.
No special Authentication configuration needed for users within same domain where all
mail users exist in the primary Domino directory (names.nsf)
Lotus Traveler and Domino mail servers in separate domain:
Required for larger environments running multiple mail domains.
Recommended if running the Notes Traveler server in the DMZ.
Better Security, since no mail users in Lotus Traveler Domino directory.
Both Traveler domain and Domino mail server domain(s) need to be cross-certified
Directory assistance needs to be configured on Lotus Traveler server for user lookup and
authentication of users in other mail domains
46 IBM Notes Traveler Hints and Tips for a Successful Deployment
2.6.1 What does IBM do internally?
In the IBM internal implementation of Lotus Notes Traveler, multiple Traveler servers are
deployed in each Domino mail domain. Users are assigned to a Notes Traveler server that is
a part of their mail domain. The Traveler servers are inside the corporate firewall and uses the
IBM Mobile Connect reverse proxy to provide external network access and improve security.
There are a few smaller mail domains which do not have Traveler servers deployed. These
users are assigned to a Notes Traveler server in a different domain and Directory Assistance
is used to provide proper user lookup.
2.6.2 Further reading on supporting multiple Lotus Domino
http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=%2Fcom.ibm.h
elp.lnt851.doc%2FPlan_Domino_domains.html
2.7 Security
In this section we describe various aspects of security that you should consider when
implementing a Lotus Notes Traveler environment, both from a client and server perspective.
We cover the following topics:
2.7.1, Device security
2.7.2, Server security on page 52 2.7.2
2.7.3, Encrypting Lotus Notes Traveler network traffic on page 53
2.7.4, Internet password lockout on page 53
2.7.1 Device security
When planning the security of the devices that will be using Lotus Notes Traveler, you should
consider the following areas:
Company owned devices versus employee Bring Your Own Device:
You must consider whether to limit the mobile devices to only company purchased devices
or to allow employee purchased devices, which is commonly referenced as "bring your
own device" (BYOD). This is a business decision and should adhere to the company's
security policy. The security policies you can apply to a device may have to vary
depending on who owns the device.
Ownership of the data on the mobile device
The company owns all the corporate related data that resides on the mobile device via
Lotus Notes Traveler, but what about all the rest of the data, personal photos, contact lists,
and so on? Your company should have business conduct guideline that clear define the
data ownership and employee should follow the guidelines.
Company rights if the device is lost, misplaced, or stolen.
You must understand your company's policy about how to handle the data of a lost,
misplaced, or stolen device and how this may vary depending on who owns the device.
Lotus Notes Traveler has several security features that can help a company to protect their
data.
Required version of OS on Mobile Devices
Earlier mobile device Operating Systems (OS) do not support many of the security
features that are now standard requirements for many companies. For example, Android
devices must be at level 2.2 or higher to support the Remote Wipe options. If an installed
Chapter 2. Planning 47
version OS does not support a companies security requirements you may wish to consider
not allowing them to connect to your Lotus Notes Traveler environment.
The following table lists the device security options, at a high level, available in Lotus Notes
Traveler at the time this wiki is written. You should check the current security options for
mobile operating system to ensure they meet your companies requirements before allowing
devices based on that OS version to connect to your environment. Note: if you are using a
Mobile Device Management (MDM) solution in addition to Lotus Notes Traveler, the security
options from that may override the options listed in this table:
Device security
Consideration should be given to the control of the Lotus Notes Traveler data on the mobile
device, who owns it and how to protect it. Especially in the context as to how in the event that
a mobile device is lost, or worse, stolen, how you can protect the data stored on the device.
You also need to consider what happens to the data when a user leaves the company. Having
some kind of legal agreement that users must agree to before using the Lotus Notes Traveler
service can help with. This agreement can then specify that the company can, at its
discretion, take any and all steps that are deemed appropriate to protect the data. Options
can include deny access to the device which prevents the synching of data, or wiping the
device of just Lotus Notes Traveler data or completely wiping all data and settings from a
device and returning it to its factory default settings.
Lotus Notes Traveler has the ability to apply certain security settings on the end user mobile
devices. Applying security settings to these devices can be used to help protect the enterprise
data that Lotus Notes Traveler synchronizes to them from unauthorized access, if the device
is lost or stolen.
As an administrator, you can either have a single default policy that applies to all users or use
multiple policies and apply them to different groups of users, allowing different security
settings to be applied to different users.
48 IBM Notes Traveler Hints and Tips for a Successful Deployment
The settings that can be applied vary between the different mobile device platforms that Lotus
Notes Traveler supports (Windows Mobile, Nokia, Apple iOS and Android), but all include the
ability to require a password be enabled on the device. The following figures show the
security settings that are available on each of the different platforms, each of these individual
settings is described in more detail of 8.2.2, Device settings on page 309.
Windows Mobile Device Security Settings
Nokia (Symbian) Device Security Settings
Apple (iOS) Device Security Settings
Chapter 2. Planning 49
Android Device Security Settings
50 IBM Notes Traveler Hints and Tips for a Successful Deployment
Although the exact security settings vary between the different device platforms, they
generally all provide some capability in the following areas:
Enabling a device password - This turns on a password on the mobile device, and defines
rules regarding the length and strength of that password.
Enabling encryption of storage cards - This encrypts the contents of any plug-in storage
media cards inserted into the device.
Prohibiting devices incapable of security enablement - This prevents devices that do not
support the ability for security settings to be automatically enforced from being used.
The latest Android devices (running Android version 3.x and 4.x) also provide the
capability to disable certain functions, such a copying data from Lotus Notes Traveler to
the clipboard or saving attachments to the device operating system.
What device security settings should you use?
Applying any of the available device security settings is entirely optional, but using them will
help protect the data that Lotus Notes Traveler synchronizes to the devices. Therefore, if you
want to increase the security of the data on the device, you should consider using them.
If you do chose to use them, the security settings should be as per your companys own IT
security standards, but following options are suggested as good practice:
Enforce a device password with an automatic lockup after an elapsed time of inactivity.
Without it, anyone who picks up the device has immediate access to the Lotus Notes
Traveler data. Also, some devices do not enable their native encryption capabilities without
a device password being set. The device password should be a minimum of four
characters, but for optimal protection, a password of at least eight characters, using a mix
of alpha, numeric and special characters should be considered. Enforcing a regular
password change and preventing the re-use of the same password will further increase
the security offered by the device password.
Chapter 2. Planning 51
Enable the option to prohibit devices that dont support security enablement.
Doing so blocks all devices that do not allow Lotus Notes Traveler to apply security
settings or support the ability to perform a remote wipe. Enabling this will limit what
devices are able to use your Lotus Notes Traveler service, however most modern devices
now support security enablement so it will typically be older or less functional devices that
would be blocked. If you do chose not to enable this option you should be aware that you
may allow some devices bypass your security settings because Lotus Notes Traveler can
not enforce them on devices that do not support security enablement.
Limitations of device security settings
There are two key limitations regarding the device security settings that you can apply in
Lotus Notes Traveler:
Nearly all of the settings apply to the entire device, not just Lotus Notes Traveler.
For example, if you chose to enforce a 10 digit password, the user would have to enter that
password every time they wanted to do anything on the device, not just use Lotus Notes
Traveler itself. This might have a negative impact on the overall user experience on the
device, especially for performing common tasks such as making a call or sending a text
message. This can be especially significant if you are using Lotus Notes Traveler in a
Bring Your Own Device implementation because the security settings you apply will
affect the user even when they are using the device for personal use.
The security settings that you are able to enforce using Lotus Notes Traveler are limited
and do not necessarily provide complete protection against data leakage.
Preventing data leakage goes beyond just controlling access to the mobile device itself
(through enforcing a password) to actually restricting what the user can do with the data
after it is on the device to ensure that the device never goes outside of your control.
Examples include preventing the user from saving email attachments locally to the device
(where they can then subsequently be copied anywhere), controlling the ability to copy
and paste the content of emails to another app and preventing email data being backed up
to cloud services where the content might not be encrypted.
Remote device security
In addition to being able to apply security settings to the mobile devices, you can also use
Lotus Notes Traveler to perform the following management functions that can help you
manage the security of the user devices remotely:
Deny access:
An administrator can block individual devices from being able to access the Lotus Notes
Traveler server. Once this is applied, the device no longer can connect and synchronize
new data with the server. However, any existing Lotus Notes Traveler data remains on the
device. As such, this option is only useful for temporarily disabling users for whom it is
acceptable for them to still have access to any data they have previously synchronized.
Wipe device:
An administrator can initiate a remote wipe of the user device, which will delete the Lotus
Notes Traveler data from the device and prevent it from being able to connect to server
again. You can use this feature to remotely remove your enterprise data from devices that
are lost or stolen, or if an employee leaves the company. There are actually three different
types of wipe that can be performed:
Hard wipe:
This resets the device back to factory defaults and delete all data (for example photos,
music, and so on), not just the Lotus Notes Traveler data. Although this is the most secure
option, you should only use it for devices where you are legally entitled to be able to delete
all the data on the device. This is not normally an issue for corporately owned devices,
52 IBM Notes Traveler Hints and Tips for a Successful Deployment
however, it might not be the case if the device is the users personal property (for example,
if you are using Lotus Notes Traveler in a "Bring Your Own Device" implementation).
Lotus Traveler application and data:
This deletes just the Lotus Notes Traveler data from the device and does not delete
anything else. This wipe method makes is more suited for use with devices that are
personally owned by the user because it gives you the ability to delete your enterprise
data from the device without affecting any of the users own data or settings.
Storage card:
This option deletes all data from the storage card in the device (if there is one present). It
does not actually delete any of the Lotus Notes Traveler data though, so it is only useful if
you want to ensure the contents of any storage cards is also deleted, which you could do
in conjunction with issuing a "hard wipe" to ensure both the device and any storage card
inserted into are wiped of any corporate data. Just as with the hard wipe option though, be
sure that you are legally entitled to delete the data from the storage card.
A limitation of all of the wipe features is that the wipe is sent to the device to action the next
time the device synchronizes with the server, so for the device to receive and action the wipe
command the device must actually connect to the Lotus Notes Traveler server. This might not
necessarily occur in all circumstances, for example, if the device is lost whilst powered off.
What does IBM do internally?
The IBM internal implementation of Lotus Notes Traveler applies a security policy that
enforces a strong alpha numeric password on all devices regardless of them being corporate
issued or personally owned. Users are also forced to change their password on a regular
basis. Devices that do not support security enablement are prohibited. IBM also uses an
additional MDM solution (IBM Endpoint Manger for Mobile Devices) to apply further security
settings and controls on the mobile devices.
Further reading on device security
The following article provides more information on device security:
Device Preference and Security Settings -
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Default_device_preference_and_sec
urity_setting_values_LNT853
2.7.2 Server security
Lotus Notes Traveler Server security
Lotus Notes Traveler server might be deployed in DMZ for direct internet access or in intranet
accessed through a proxy server. Securing a Lotus NotesTraveler server in these
environments is important to ensure both the integrity and the availability of data.
Server access includes:
Network access
The network access is controlled by a firewall. If the Lotus Notes Traveler server is
configured to connect through a Load Balancer or a Proxy server, HTTP and HTTPS Port
are enabled on Load Balancer. Enforce HTTPS with a HTTP redirect to HTTPS.
If Lotus Notes Traveler server is configured for direct access from mobile devices by
placing it in network de-militarized zone (DMZ), enable only the HTTPS port (443) for
external access and disable all other ports.
Chapter 2. Planning 53
User authentication:
Lotus Notes Traveler server provides access to Lotus Notes mail and calendar data using
HTTP or HTTPS ports and it is necessary to configure HTTP security to enforce
authentication. HTTP authentication can be configured for Domino authentication or an
LDAP server. It is also important to plan for single-sign on for establishing trust between
Load Balancer or Proxy server and Lotus Notes Traveler server. We describe this topic in
detail in 7.2, Configuring single sign-on on page 297.
Lotus Notes Traveler server access:
Secure the Lotus Notes Traveler server access by restricting anonymous access, disabling
databases browsing, and limiting the administration access to Administrators only. The
server access is defined in the Server document as described in 8.4.3, Security tab on
page 335.
Lotus Domino application and mail access:
Use access control list (ACL) for restricting unauthorized access to Mail files and
Applications on Domino servers. Displaying of Notes Document links in email messages
depends on ACL restrictions.
What does IBM do internally?
In the IBM internal implementation of Lotus Notes Traveler, all servers are configured to use
SSL so that the communication between the end user devices and the Lotus Notes Traveler
servers is encrypted over a HTTPS connection. As the IBM internal Lotus Notes Traveler
servers also use an external LDAP directory to authenticate user log in details (rather than
the native Lotus Domino directory) the LDAP connection is also secured using SSL to ensure
that the user's credentials are also always encrypted.
2.7.3 Encrypting Lotus Notes Traveler network traffic
It is suggested to secure all communications traffic between devices and the Lotus Notes
Traveler server to avoid any over the air security breaches. Depending on your environment,
this can be achieved by enabling SSL encryption for the Lotus Domino HTTP server or
reverse proxy, or by using a VPN. If you are using a Lotus Notes Traveler High Availability
(HA) configuration then all servers in the HA pool must be configured in the same way (either
all should use SSL or none).
Once the SSL is enabled, you can use https://hostname to access the server instead of
http://hostname. You can either use Domino self-signed SSL certificates or third-party SSL
certificates to configure SSL on the Domino HTTP server. Third party trusted SSL certificates
are recommended as some devices will not tolerate an untrusted certificate and will not be
able to connect to a server using a self-signed untrusted certificate.
For steps to enable SSL on Lotus Domino server, see the server documentation
http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=%2Fcom.ibm.h
elp.domino.admin85.doc%2FH_ABOUT_SETTING_UP_SSL_ON_A_SERVER.html
2.7.4 Internet password lockout
The benefits of using Internet Password Lockout
You can configure the Lotus Domino Internet Password Lockout (IPL) feature to help protect
your Lotus Notes Traveler environment against brute force and dictionary attacks on the user
passwords used to authenticate with the Lotus Notes Traveler server. If mobile devices are
connecting directly to the Lotus Notes Traveler server, or if there is no lockout capability
present on a front-end authentication proxy, then it is recommended to enable this capability.
54 IBM Notes Traveler Hints and Tips for a Successful Deployment
Because email addresses are relatively easy to ascertain, there is a definite security value in
protecting the passwords used by Lotus Notes Traveler against multiple incorrect password
attempts. This is especially true if you have deployed your Lotus Notes Traveler server in an
"internet facing" configuration (that is, your Lotus Notes Traveler server is directly accessible
through the internet). However, even if the Lotus Notes Traveler server is only available
internally, using IPL can help protect against the actions of a rogue employee attempting to
maliciously access another employees email.
How Internet Password Lockout works
IPL is actually a feature of the Lotus Domino web engine, but can be used in a Lotus Notes
Traveler environment as well, even if the users Lotus Notes Traveler passwords are stored in
an external LDAP directory rather than native Domino directory. This is because all
connectivity to Lotus Notes Traveler server is handled by the Domino HTTP task, which
utilizes the IPL feature.
IPL works on the simple concept of defining how many failed user authentication attempts are
allowed. Once this number is exceeded, a record for the user is created in an IPL database
stored on the Domino server. The HTTP task queries the contents of this database every time
it receives a new authentication request and automatically fails any attempt for a user name
that has a matching record.
A user is unable to authenticate with the Lotus Notes Traveler server all the time that they
have a record present in the IPL database (even if he subsequently try and authenticate with
the correct credentials). There are two options on how user records can be removed from the
IPL database to re-enable the user access:
They can be configured to delete automatically, after an administrator definable period of
time has elapsed (for example, after 24 hours).
They can be deleted manually by a Domino or Lotus Notes Traveler Administrator who has
the necessary access permission to the IPL database.
The following figure shows how the IPL integrates into a simple Lotus Notes Traveler
architecture:
Chapter 2. Planning 55
Things to be aware of when using Internet Password Lockout
If you do choose to enable IPL in your environment there are three main things to be aware
of:
It will inconvenience users who accidentally enter the password incorrectly enough times
to be locked out. It is important to have a well defined and communicated process that
users can follow to re-enable their access to Lotus Notes Traveler.
Depending how IPL is configured, it can be an additional overhead on your Lotus Notes
Traveler administrators as they have to process requests from locked out users.
IPL can be used as a potential denial of service attack, because anyone can attempt
multiple incorrect password attempts on any Lotus Notes Traveler account if they have
network connectivity to the server and know the email address. This is more of a potential
issue if the Lotus Notes Traveler server is connected directly to the internet. Remember
that once a user is added to the IPL database, they are locked out until that record is
explicitly deleted by an administrator or the record is removed because it expires.
Using Internet Password Lockout with Single Sign On
If you configure your Lotus Notes Traveler environment to use Single Sign On (SSO)
authentication with another authentication source (for example, an alternative LDAP server),
then it is not necessary to use the IPL feature on your Lotus Notes Traveler servers. This is
because when SSO is enabled, all of the authentication work actually is done by the external
SSO server and therefore the Lotus Notes Traveler server will receive only an SSO token for a
user who has already been successfully authenticated. In these circumstances, there is no
need to use IPL on the Lotus Notes Traveler servers anymore because users will no longer be
authenticating with them directly.
What does IBM do internally?
In the IBM internal implementation of Lotus Notes Traveler, IPL was originally configured to
block a user after three failed password attempts. The block is maintained for 24 hours after
which, it is configured to automatically delete, enabling the user to try again. IBM also
deployed a custom "self service" application that allows users to delete any IPL lock out that
matches their own Lotus Notes ID. This enables users to unlock themselves on a 24/7 basis,
as long as they have access to their Lotus Notes client and ID. Otherwise, they must wait for
the 24 hour period to expire, or they can submit a help desk request for a Lotus Notes Traveler
Administrator to unlock them.
Further reading on the Internet Password Lockout feature
The following articles describe the IPL feature in more detail, including a step by step of how
to enable it:
Securing an IBM Lotus Domino Web server: Using the new Internet lockout feature -
http://www.ibm.com/developerworks/lotus/library/domino8-lockout/
Securing Internet passwords -
http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=%2Fcom.ib
m.help.domino.admin85.doc%2FH_SECURING_THE_INTERNET_PASSWORD_IN_THE_PERSON_DOCU
MENT_7640_STEPS.html
2.8 Language support
Lotus Notes Traveler has multiple language support and you can select the language at the
beginning of the installation. Once you decide the language, you cannot change it unless you
re-install the Lotus Notes Traveler server. Once you have decided what language support
56 IBM Notes Traveler Hints and Tips for a Successful Deployment
your company needs, you can begin installing and setting up your Lotus Notes Traveler
server. This following table shows the information on all supported language for Lotus Notes
Traveler. English is used when the device or browser locale is unsupported.
Language Server Servlet Client for
Windows
Mobile
Client for Nokia Client for
Android
Arabic No Yes No Yes No
Catalan Yes Yes Yes Yes Yes
Chinese
(Simplified)
Yes Yes Yes Yes Yes
Chinese
(Traditional)
Yes Yes Yes Yes Yes
Czech Yes Yes Yes Yes No
Danish Yes Yes Yes Yes Yes
Dutch Yes Yes Yes Yes Yes
English Yes Yes Yes Yes Yes
Finnish Yes Yes Yes Yes Yes
French Yes Yes Yes Yes Yes
German Yes Yes Yes Yes Yes
Greek Yes Yes Yes Yes Yes
Hebrew No Yes No Yes No
Italian Yes Yes Yes Yes Yes
Japanese Yes Yes Yes No Yes
Korean Yes Yes Yes No Yes
Norweigan-Bok
mal
No Yes Yes Yes Yes
Polish Yes Yes Yes Yes Yes
Portuguese Yes Yes Yes Yes Yes
Portuguese
(Brazilian)
Yes Yes Yes Yes Yes
Russian Yes Yes Yes Yes Yes
Slovak Yes Yes Yes Yes No
Slovenian Yes Yes No Yes No
Spanish Yes Yes Yes Yes Yes
Swedish Yes Yes Yes Yes Yes
Thai Yes Yes No Yes No
Turkish Yes Yes Yes Yes Yes
Chapter 2. Planning 57
What does IBM do internally
In the IBM internal implementation of Lotus Notes Traveler, we typically choose English
servers. One benefit of running English servers is that administrators from any location can
manage and troubleshoot servers quickly and efficiently, as the server console and log
messages are all in English. This means that error and log messages are more easily
located.
2.9 Anti-virus recommendations
It not recommended to scan Domino data Directories with a standard OS level Anti-Virus
program, this also applies to the Notes Traveler server. It is recommended to use a
specialized scanner designed to scan mail and protect the Domino directories. Lotus
Protector is one such product and there are many other third party mail security applications.
That said, unless the Notes Traveler also hosts mail files, no user data is ever stored on the
Notes Traveler server, so it is not necessary to deploy a mail scanner on this system. All the
emails sent from Lotus Notes Traveler mobile devices are delivered using the user's home
Lotus Domino mail server. If that Lotus Domino mail server is unavailable, the Lotus Notes
Traveler server will attempt to find an alternative if one is available as part of a Lotus Domino
cluster. As such the anti-virus solution configured for Lotus Domino home mail server is used
for scanning all the emails sent by Lotus Notes Traveler.
It is also advisable to have an anti-virus installed on the user mobile devices as an additional
layer of protection to prevent any malware infecting the device itself.
2.10 Upgrading versions
New releases of Lotus Notes Traveler provides new features that keep your users connected
and productive with full-featured e-mail for smartphones and tablets. Lotus Notes Traveler Fix
Packs are also released when necessary which contains small enhancement or fixes for
current defects. Upgrading to the latest version is ensure your Lotus Notes Traveler
environment run with full benefits of Lotus Notes Traveler.
For latest Notes Traveler versions see this technote: Recommended Maintenance -
http://www.ibm.com/support/docview.wss?uid=swg24019529
Important: When Lotus Notes Traveler is installed on a system with a Thai locale, you
must add the following line to the Notes.ini of the Lotus Notes Traveler server or servers (in
an HA pool). This addition is because the Java for Lotus Notes Traveler uses the
Gregorian calendar (and not the Buddhist calendar).
NTS_Java_Parms=-Duser.language=th.US
Although it is possible, it is not recommended installing Lotus Notes Traveler servers in
different languages in one High availability pool, as not much benefit. Doing so could cause
the an end user who is not using a support language to see different languages depending
on what server they are connecting too.
58 IBM Notes Traveler Hints and Tips for a Successful Deployment
2.10.1 Upgrading Lotus Domino version
Lotus Notes Traveler 8.5.3 Upgrade Pack 1 server must be installed on a Domino 8.5.3.x
server and supports two modes of operation:
Stand alone mode
High Availability mode.
Ensure the upgraded version of Lotus Domino on your Lotus Notes Traveler server is the
most recent version that matches the version of Lotus Notes Traveler you intend to install. So
for example if you are planning on installing Lotus Notes Traveler 8.5.3 Upgrade Pack 1, the
most recent version of Lotus Domino should be 8.5.3.3. If the most recent version of Lotus
Domino on your Lotus Notes Traveler server is a higher version than what is installed on your
Lotus Domino domain Administration server then you will need to do one of the following to
avoid potential problems with having different versions of the Lotus Domino system
databases replicating between servers in the same Lotus Domino domain:
1. Install the Traveler server in its own Domain.
2. Upgrade all of the Lotus Domino servers in your Lotus Domino domain to use the latest
version as well.
3. Consider upgrading just your Lotus Domino Administration server to the latest version,
although be aware this will upgrade the design of the Lotus Domino system databases so
you need to be sure that all Lotus Domino servers in your Lotus Domino domain will work
correctly with this configuration.
4. Upgrade just the design of the Lotus Domino system database templates (e.g. Public
Address book, Admin4 etc) to use the latest version (so that they can replicate freely with
latest version as used on your Lotus Notes Traveler server). Again be aware this will
upgrade the design of the Lotus Domino system databases so you need to be sure that all
Lotus Domino servers in your Lotus Domino domain will work correctly with this
configuration - especially your Lotus Domino administration server(s).
5. Take steps to prevent the replication of the upgraded design of the Lotus Domino system
database templates from your Lotus Notes Traveler servers to the rest of the Lotus
Domino servers in your Lotus Domino domain. In this configuration the Lotus Notes
Traveler servers use the latest design version of the Lotus Domino system databases but
the rest of the Lotus Domino servers in the Lotus Domino domain continue to use their
existing (older) version. This can be achieved using a combination of selective replication
rules (e.g., disabling the option to replicate design elements of the system databases to
and from the Lotus Notes Traveler servers) and reduced Access Control List (ACL)
permissions (e.g., only granting the Lotus Notes Traveler servers lower than Designer
access on the system databases). However care does need to be taken when using this
configuration to ensure the newer design of the system databases on the Lotus Notes
Traveler servers is not accidentally propagated to the older servers in the Lotus Domino
domain.
Upgrading all of your Lotus Domino servers in your Lotus Domino domain is the ideal solution
because then all of your servers are at the same version. However this can be a challenge if
you have a large Lotus Domino domain so in these circumstances you may want to consider
just upgrading your Lotus Notes Traveler servers and then managing the interaction between
them and the other servers in the Lotus Domino domain using either option two, three or four
in the list above. Of course if you have your Lotus Notes Traveler servers in their own
dedicated Lotus Domino domain, as is discussed in 2.6, Domino domain configuration on
Important: When upgrading version, always upgrade the Domino server first, the perform
the Notes Traveler upgrade.
Chapter 2. Planning 59
page 44, then upgrading to the latest version is less of a challenge in this respect because all
of the servers in that Lotus Domino domain will be at the same level so there are no concerns
about having different versions of the Louts Domino system databases.
2.10.2 Upgrading Lotus Traveler upgrading
For maintenance, install Lotus Notes Traveler 853 Upgrade Pack 1:
Recommended Level Component Build Levels
8.5.3.100 Server
WM LMI
WM Client
Nokia LMI
Nokia Client
Android Client
20120613_2102
20120528_2100
20120528_2100
20120525_1525
20120525_1525
20120611_0951
Important: Lotus Notes Traveler 8.5.3 Upgrade Pack 1 requires Domino 8.5.3 Upgrade
Pack 1. If this software has not been previously installed, it will automatically be installed
during the installation of Lotus Notes Traveler. Please ensure you check on Install Domino
8.5.3 Upgrade Pack 1 when you install Lotus Notes Traveler 8.5.3 Upgrade Pack 1.
60 IBM Notes Traveler Hints and Tips for a Successful Deployment
2.11 Integrating Lotus Notes Traveler into a high availability
pool
Integrating a Lotus Notes Traveler server into a High Availability pool (HA) is a simple
process, but requires careful planning to ensure a successful implementation. Consider the
following before installing an HA instance of Lotus Notes Traveler:
Location of the Lotus Notes Traveler servers:
Where to place the Lotus Notes Traveler servers depends on the topology chosen. Each
topology has its advantages and disadvantage. For example, placing the Lotus Notes
Traveler servers in the same location as the Mail servers can prevent long running http
threads caused by network latency. However, if mail servers are scattered amongst
several geographical locations, it might be advantageous to place separate pools of Lotus
Notes Traveler servers in each location. 2.3, Planning your server and network topology
on page 33 provides the considerations for various topology for Lotus Notes Traveler
deployment.
Installation of the enterprise database
Lotus Notes Traveler supports DB2 for Linux, UNIX, and Windows or Microsoft SQL Sever.
Lotus Notes Traveler provides a no charge entitlement of DB2 for Linux, UNIX, and
Windows. Consider the in-house expertise you already have with either DB2 or Microsoft
SQL Server when deciding which to use. If you have no experience in either, it may be
advantageous to use DB2 as then you can get support for both Lotus Notes Traveler and
DB2 from IBM.
The enterprise database hosts your Lotus Notes Traveler data so you also want to
consider the high availability for the database environment to provide the accessibility and
protection of the Lotus Notes Traveler data on your enterprise database server. This is
because any outage to the enterprise database server will also cause an outage to your
Lotus Notes Traveler environment. For more details, see 2.13, Load balancer
considerations on page 62 2.13.
Broadcasting a single URL for client access
The Lotus Notes Traveler HA pool requires the use of a single URL for all the servers in
the pool. In the server document, on the Traveler tab, a field is designated for this use.
See 3.4.2, Lotus Notes Traveler configuration on page 91 on how to set this value. If
multiple Lotus Notes Traveler servers have already been deployed, some planning is
necessary on how to consolidate to a single URL.
If a Lotus Notes Traveler server has already been deployed with the desired address for a
single URL, this should be the first Lotus Notes Traveler server to be converted to the High
Availability pool in order to maintain the use of that URL. The remaining Lotus Notes
Traveler servers can then be added to the pool. The internal DNS will need to be changed
at the time of conversion to resolve the old Lotus Notes Traveler server address to the
single address for the HA pool. In this way the Lotus Notes Traveler clients can continue to
access the existing configured URL which will now resolve to the new HA pool.
If the environment is using an additional Mobile Device Management solution (MDM), the
desired address may already be in place with one of the MDM's. In that case only the
internal network DNS will need to be updated to point the existing addresses to the HA
pool.
Using load balancers
A proxy, load balancer, or IP sprayer capable of basic round-robin balancing function with
no or limited session affinity is required in front of the HA pool to direct the incoming the
Chapter 2. Planning 61
single URL traffic to the pool of servers. The Lotus Notes Traveler servers within the HA
pool do their own load balancing, so a true Load Balancer/IP Sprayer is not necessary.
However, care should be taken the Load Balancer selected can handle the expected
number of Mobile Devices. It is also important to ensure that the Load Balancer or IP
Sprayer infrastructure has its own High Availability solution. Otherwise any outage to the
Load Balancer/IP Sprayer would prevent the end user devices from being able to connect
to the Lotus Notes Traveler server pool. For additional information on the requirements of
the Load Balancer, see 2.13, Load balancer considerations on page 62.
Supporting large number of mobile devices
Given the required hardware, software, and network configuration, a single Lotus Notes
Traveler server in an HA configuration can service up to a maximum of 2500 devices and a
single HA pool can service up to 10,000 devices. If your environment needs to support
more a large number of devices, in some cases in excess of 10,000 devices there are
several options, depending on your environment and needs:
It is best to keep the Lotus Notes Traveler servers in the same data center as the Lotus
Domino mail servers. If this is the case it would be best to set up several Lotus Notes
Traveler HA pools, one at each of the mail data centers, even if each individual pool is
less than 10,000 devices. Each pool will require it's own URL address.
If your environment needs to support more than 10,000 devices at a single data center
and a single URL is desired, consider using Lotus Mobile Connect (LMC) or a similar
type of software. One of the new features of LMC is Lotus Notes Traveler HA pool
awareness. The LMC servers will track the affinity to which pool a user has been
connected previously and connect the user to the same pool each time they connect.
New users will be balanced to one of the available pools, with affinity then stored in a
database. The LMC database is separate from the Lotus Notes Traveler Enterprise
database.
If you need to support in excess of 10,000 devices at a single data center, and a single
URL is not required, you may set up multiple pools using the same address, but with a
different port number in the URL to connect for each pool. For example you would
advertise the address as 'https://travelerservers.yourcompany.com:15001'. The Load
Balancer would direct the users to the proper pool based on the port number.
For the capacity considerations, see 2.4, Capacity planning on page 43.
2.12 Enterprise database server clustering
In a high availability (HA) environment, all systems, including the enterprise database, must
be duplicated to prevent a single point of failure.
When moving to an HA environment, the database that tracks the Lotus Notes Traveler device
state information and metadata is moved from a local database on the Lotus Notes Traveler to
an enterprise database that resides on a separate server. If only a single enterprise database
server is installed, it would become a single point of failure. When the enterprise database is
unavailable, Lotus Notes Traveler is not functional until the enterprise database is recovered
or a new instance of the database is created. Recovering takes time and will impact the
serviceability and productivity of your company.
To avoid these possibilities, you should ensure the enterprise database infrastructure has its
own High Availability capability as well.
62 IBM Notes Traveler Hints and Tips for a Successful Deployment
Lotus Notes Traveler supports IBM DB2 for Linux, UNIX, and Windows and Microsoft SQL
Server. The following table lists the specific versions currently supported. Before installing
Lotus Notes Traveler and an associated enterprise database, check the current requirements.
For more information about DB2 installation, configuration, and high availability setup, see the
IBM Redbooks publications:
Up and Running with DB2 on Linux, SG24-6899
DB2 Deployment Guide, SG24-7653
High Availability and Disaster Recovery Options for DB2 for Linux, UNIX, and Windows,
SG24-7363
There are various methods to create an HA instance of Microsoft SQL server depending on
version of SQL Server installed and the underlying OS. See the Microsoft documentation that
best suits your installation on specific instructions.
2.13 Load balancer considerations
To support a pool of Lotus Notes Traveler servers, a single connection URL for the end user
devices is required. 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.
The minimal requirements for an IP sprayer or load balancer in a Lotus Notes Traveler
implementation include:
Provides a single URL and supports the proxy of device requests to two or more Lotus
Notes Traveler servers.
Round robin load balancing to spread the load evenly across the Lotus Domino HTTP
tasks as desired. Lotus Notes Traveler provides its own load balancing (within the HA
pool) based on server load characteristics after it has received the requests from the Lotus
Domino HTTP task.
The ability to detect when a Lotus Notes Traveler server is no longer responding (to allow
for failover).
Product Notes
DB2 for Linux, UNIX, and Windows
Enterprise Server Edition Version 9.7,
Fixpack 5 or higher
64-bit version recommended.
DB2 for Linux, UNIX, and Windows
Workgroup Server Edition Version 9.7,
Fixpack 5 or higher
64-bit version recommended. A limited entitlement to IBM
DB2 9.7.0.4 Workgroup Server Edition is included with the
Lotus Notes Traveler 8.5.3 Upgrade Pack 1 release. This
limited entitlement is provided for customers who want to
deploy a Lotus Traveler High Availability server and elect to
use this entitled DB2 version as their RDBMS solution. The
DB2 entitlement may be used for no purpose other than the
support of Lotus Notes Traveler.
Microsoft SQL Server Enterprise
Edition 2008 SP1 CU1 or higher
64-bit version recommended.
Microsoft SQL Server Enterprise
Edition 2008 R2 SP1 CU1 or higher
64-bit version recommended.
Chapter 2. Planning 63
Session affinity for a device session is not required but is recommended for efficiency. A
short timeout of less than 2 hours is recommended.
When configuring the HA pool, you need to set the Lotus Notes Traveler external URL to point
the devices to the URL of the IP sprayer/load balancer through the Traveler tab of the Lotus
Notes Traveler server document. All Lotus Notes Traveler servers within the same HA pool
must use the same URL value.
When considering the function of load balancing, it is important to keep in mind that the Lotus
Notes Traveler servers will be providing their own load balancing, independent of what the
front end server does. After the front end server passes a request to a specific Lotus Notes
Traveler server, that server will then determine which of the pool of servers should handle the
request and forward it as appropriate. For further information on this process, see
[http://www-10.lotus.com/ldd/dominowiki.nsf/xpDocViewer.xsp?lookupName=Administeri
ng+Lotus+Notes+Traveler+8.5.3+Upgrade+Pack+2#action=openDocument&res_title=Load_ba
lancing_considerations_A853UP2&content=pdcontent.
2.14 Mobile device management integration
2.14.1 What is mobile device management?
Mobile device management (MDM) software is designed to help manage and administrate
large scale deployments of mobile devices. This can include being able to perform tasks such
as device configuration, enforce device security policies, monitor the device, install
applications on the device, and perform other general tasks such as auditing and reporting.
There are many different mobile device management software vendors in the market, all
offering a variety of solutions and capabilities.
2.14.2 Why use a mobile device management solution in conjunction with
Lotus Notes Traveler?
Lotus Notes Traveler is not a mobile device management server. It does offer some basic
mobile device management capabilities, mainly in the context of being able to apply security
related settings on the device. The fully fledged MDM software provides a much greater
breadth and depth of capabilities. It is however important to note that it is not necessary to
use any mobile device management software in order to install and use Lotus Notes Traveler.
There are advantages to using mobile device management software in conjunction with Lotus
Notes Traveler though, such as:
Automate the install and configuration of Lotus Notes Traveler for the users.
Self service portal for end users.
Jailbreak and root detection.
Automatic detection and blocking of non compliant or compromised device.
Application management, including enterprise apps store and automatic push of device
policies.
Easy implementation of a wider range of configuration policies, including the ability to
control device settings that cannot be managed using just Lotus Notes Traveler (for
example, WiFi and VPN).
Additional controls for email access.
64 IBM Notes Traveler Hints and Tips for a Successful Deployment
If you want to be able to perform management tasks of your user's mobile devices beyond the
capabilities offered natively by Lotus Notes Traveler, you should consider using additional
mobile device management software in conjunction with Lotus Notes Traveler.
2.14.3 Further reading on mobile device management
The following articles provides more information on choosing and using a mobile device
management solution with Lotus Notes Traveler:
An integrated approach to managing and securing your mobile environment -
ftp://submit.boulder.ibm.com/sales/ssi/ecm/en/tis14115usen/TIS14115USEN.PDF
Select the right solution for end point management -
http://public.dhe.ibm.com/common/ssi/ecm/en/tio14008usen/TIO14008USEN.PDF
Copyright IBM Corp. 2013. All rights reserved. 65
Chapter 3. Deploying a stand-alone Lotus
Notes Traveler environment
In this chapter, we walk through a scenario where the goal is to deploy a smaller, stand-alone
IBM Lotus Notes Traveler server that can be used in the case of most smaller businesses. We
briefly discuss certain planning steps that are detailed in 2.0 Planning, and go over our
topology considerations. One thing to note is that given our requirements for this deployment,
the version of Lotus Notes Traveler 8.5.3 Upgrade Pack 1 is a scalable version of the
software. Meaning, if the environment is to grow, and there is a need to add another server
(either for high availability or an increase of devices), this can be done without a problem to
the environment. This is further discussed in Chapter 6, Migration on page 259 where we
discuss "migrating" to a high availability environment.
Installation, configuration, and user deployment are three major milestones in deploying an
IBM Lotus Notes Traveler environment. After the Lotus Notes Server is configured and ready
to serve the users, users can configure their devices to connect to Lotus Notes Traveler to
access their mails. User deployment to devices is covered in full detail in 5.0 User
deployment. This chapter includes the following sections:
3.1, Scenario description on page 66
3.2, Lotus Notes Traveler installation on Linux on page 67
3.3, Lotus Notes Traveler installation on Windows on page 79
3.4, Configuration on page 89
3
66 IBM Notes Traveler Hints and Tips for a Successful Deployment
3.1 Scenario description
In this scenario, we deploy an IBM Lotus Notes Traveler server with the same mentality that a
small business would use. This solution encapsulates introducing a Lotus Notes Traveler
server into an existing Lotus Domino environment. The Lotus Notes Traveler Server uses
internet through a DMZ (or firewall) and allows devices and browsers to connect directly to
the Lotus Notes Traveler server through HTTP/HTTPS. Lotus Notes Traveler then is
communicating with the mail servers via the internal network.
This following figure depicts the topology of the scenario.
In this section we walk through both the the Linux and Windows installation procedures.
Important: Although this is a common scenario it is preferred to use an authenticating
proxy server in the DMZ and move the Notes Traveler server inside the firewall. For more
information on using a proxy server in this configuration see 3.4.3 Additional
configurations.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 67
3.1.1 Planning considerations
When making the considerations as to what type of server to deploy, we take into account the
size of the user base that is going to be catering to, the necessity for the server to be available
100% of the time, and the cost of the hardware be required.
First, we choose to go with a stand-alone server to cater to the 25 devices that we will be
servicing in this scenario. This being a small number and less than 2,000 devices, we knew
that we do not need to have more than one server in the environment to service these
devices.
Second, in this operation we understand that if the Lotus Notes Traveler server is to become
unavailable for one reason or another, all of the employees could simply use their Lotus Notes
Client or iNotes to retrieve email, and manage their calendars and contacts. This being said,
we did not need to add additional servers for high availability.
Based on these two reasons, there is no need to have more than one server purchased to
give us the mobile functionality.
See 2.2, Choosing a stand-alone or high availability configuration for Lotus Notes Traveler
on page 31 for further information about the decision of choosing stand-alone versus high
availability topology.
3.2 Lotus Notes Traveler installation on Linux
In this section, we walk through the installation procedures that are documented in the official
Lotus Notes Traveler product wiki to install the Lotus Notes Traveler 8.5.3 Upgrade Pack 1 on
a Linux server in our lab. You can find the official Lotus Notes Traveler product wiki here
(http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Installing_the_Lotus_Notes_Traveler
_server_A853UP1).
In our lab environment, the Domino server was set up according to the recommendations on
the "Before you install" link on the above hyperlink. Any of the user specific setup is
addressed in Chapter 5, User deployment on page 171.
Bookmark and reference to the regularly updated FAQ page
(http://www-01.ibm.com/support/docview.wss?uid=swg21450615) for the most current and
common issues being seen with the Lotus Notes Traveler software.
It is advisable to stay at the latest fix level of 8.5.3.100+. You can keep track of the current
level of code by referencing the recommended maintenance page
(http://www-01.ibm.com/support/docview.wss?uid=swg24019529).
3.2.1 Installing Lotus Notes Traveler
Use these steps to install the Lotus Notes Traveler on a Linux system:
1. Stop Domino:
Ensure that you stop the Domino server before installing Lotus Notes Traveler. To stop the
Domino server, run quit on the Domino console. If you have just installed Domino for the
use of Lotus Notes Traveler, start the Domino server once before you install Lotus Notes
Traveler to enure that the Domino server is able to initialize successfully. Then ensure the
Domino server is stopped before you install Lotus Notes Traveler.
68 IBM Notes Traveler Hints and Tips for a Successful Deployment
2. Launch the installer:
If installing from a DVD, insert the DVD into the DVD-ROM drive of the target system.
Navigate to the DVD content and run launchpad.sh.
If installing from an installation application, extract the tar file to a temporary location
then run TravelerSetup.
The following figure shows the initial panel after start the installer.
3. Stop Domino double check.
Ensure that Domino server is stopped before you continue.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 69
4. Licence agreement:
Review and accept the license agreement.
5. Choose if partitions are used:
70 IBM Notes Traveler Hints and Tips for a Successful Deployment
Select Install multiple partitions to install Lotus Notes Traveler on multiple Domino
partitions. Leave cleared if the Domino server is not partitioned or if you want to install on
only one Domino partition.
It is possible to have multiple Domino instances running on the same Linux server in
different partitions on the same machine. We do not do this in our scenario.
6. Software install directories:
Specify the directories in which the Domino program files and data files are located. The
installer prompts asking you to enter the directory for the notes.ini file if it is not present in
the Domino program files directory.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 71
7. Domino credentials:
Enter the values for the Domino user name and group name. These are existing users and
groups on the Linux server used to run the Domino server, which are set up before
installing and running the Domino server.
Important: When installing on a partitioned Domino server, you can install Lotus Notes
Traveler on one or more of the Domino partitions. The installation panel pre-fills with all
partitions detected by the installer. Add or remove partitions from the panel as required.
The same installation options are used for all partitions indicated. In addition, you can
add or remove partitions at a later time by either using the installer again or running the
uninstaller.
72 IBM Notes Traveler Hints and Tips for a Successful Deployment
8. User home page:
The user home page is a useful starting place for users. It provides status information,
links to client software, and user management options. If the user home page is set as the
default website for this server, you can view the home page by pointing any browser to
http(s)://hostname. When the default website is set to the user homepage, a mapping is
made that automatically forwards the request from http(s)://hostname to
http(s)://hostname/traveler. If the user home page is not set as the default, you can view
the home page by pointing the browser to http(s)://hostname/traveler. This setting takes
effect the first time Lotus Notes Traveler is started and can be manually changed at a later
time.
Select Set user home page as default website for this server.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 73
9. Client connection URL:
This is the value that you will have the users use to connect to the server. If you chose to
not set the home page as the default website for this server you have to notify users of
URL specifying /traveler on the end of the URL. You also have to specify the protocol
either HTTP or HTTPS. It is good practice for the connecting devices to always configure
their device to use the URL http(s)://hostname/traveler even if the default homepage is set
to the Lotus Notes Traveler user home page. If you have decided to use a different port
than the default port of 80 or 443 for SSL, you will need to add that to the URL as well. For
example http(s)://hostname:port_number/traveler
Configure the client connection URL by indicating whether clients connect directly to the
Lotus Notes Traveler server or connect through a proxy. If the URL is not currently known,
select Configure later. In our scenario, we select Clients connect to this server
directly.
74 IBM Notes Traveler Hints and Tips for a Successful Deployment
10.Setting external server URL:
Specify the external server URL in the field. The URL is validated. Note any warning
dialogs and continue.
In our case, we decided not to use SSL, and went with a HTTP URL. Because of this, we
were presented with a warning which we noted, and continued:
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 75
11.Domino upgrade notification:
The Domino Upgrade Pack 1 is required for the XPages web administration and other
Lotus Notes Traveler functionality. If this is not done, then Lotus Notes Traveler Version
8.5.3 Upgrade Pack 1 will not run properly.
If Domino 8.5.3 Upgrade Pack 1 is not detected on this system, indicate whether you
would like Lotus Notes Traveler to install the prerequisites. This option is checked by
default.
When Domino 8.5.3 Upgrade Pack 1 is not installed, select this option and install it. This
option is checked by default.
76 IBM Notes Traveler Hints and Tips for a Successful Deployment
12.Review:
Review your selections. If any changes are required, select Previous to update the
selections, otherwise, select Install to continue.
13.Finishing the installation:
The installation commences and you can see the progress.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 77
Select Done when the installation is completed. If any errors or warnings are reported, review
the installation log and contact IBM Support to resolve any problems.
78 IBM Notes Traveler Hints and Tips for a Successful Deployment
3.2.2 Domino startup and installation validation
On the next start up of Domino, you see that the Lotus Notes Traveler server also starts when
the server is started.
You can validate the install is working correctly by accessing the server in a browser from a
laptop, a desktop machine, or a device.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 79
3.3 Lotus Notes Traveler installation on Windows
In this section, we walk through the installation procedures that are documented in the official
Lotus Notes Traveler product wiki to install the Lotus Notes Traveler 8.5.3 Upgrade Pack 1 on
a Windows server in our lab. You can find the official Lotus Notes Traveler product wiki here.
In our lab environment, the Domino server was set up according to the recommendations on
the "Before you install" link on the above hyperlink. Any of the user specific setup is
addressed in Chapter 5, User deployment on page 171.
Bookmark and reference to the regularly updated FAQ page
(http://www-01.ibm.com/support/docview.wss?uid=swg21450615) for the most current and
common issues being seen with the Lotus Notes Traveler software.
It is advisable to stay at the latest fix level of 8.5.3.100+. You can keep track of the current
level of code by referencing the recommended maintenance page.
3.3.1 Installing Lotus Notes Traveler
Use these steps to install the Lotus Notes Traveler on a Windows system:
1. Stop Domino:
80 IBM Notes Traveler Hints and Tips for a Successful Deployment
Ensure that you stop the Domino server before installing Lotus Notes Traveler. To stop the
Domino server, run quit on the Domino console. If you have just installed Domino for the
use of Lotus Notes Traveler, start the Domino server once before you install Lotus Notes
Traveler to enure that the Domino server is able to initialize successfully. Then ensure the
Domino server is stopped before you install Lotus Notes Traveler.
2. Launch the installer:
If installing from a DVD, insert the DVD into the DVD-ROM drive of the target system. If
autorun is enabled for the system, the Common Launchpad starts automatically. If
autorun is disabled, navigate to the DVD content and double-click launchpad.exe.
If installing from an installation application, run the downloaded file, usually
TravelerSetup.exe.
The following figure shows the initial panel after start the installer.
3. Stop Domino, double check:
Ensure that you first stop the Domino server before installing Lotus Notes Traveler.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 81
4. Licence agreement:
Review and accept the license agreement.
5. Software install directories:
Specify the directories in which the Domino program files and data files are located.
82 IBM Notes Traveler Hints and Tips for a Successful Deployment
6. User home page:
The user home page is a useful starting place for users. It provides status information,
links to client software, and user management options. If the user home page is set as the
default website for this server, you can view the home page by pointing any browser to
http(s)://hostname. When the default website is set to the user homepage, a mapping is
made that automatically forwards the request from http(s)://hostname to
http(s)://hostname/traveler. If the user home page is not set as the default, you can view
the home page by pointing the browser to http(s)://hostname/traveler. This setting takes
effect the first time Lotus Notes Traveler is started and can be manually changed at a later
time.
Select Set user home page as default website for this server.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 83
7. Client connection URL:
This is the value that you will have the users use to connect to the server. If you chose to
not set the home page as the default website for this server you have to notify users of
URL specifying /traveler on the end of the URL. You also have to specify the protocol
either HTTP or HTTPS. It is good practice for the connecting devices to always configure
their device to use the URL http(s)://hostname/traveler even if the default homepage is set
to the Lotus Notes Traveler user home page. If you have decided to use a different port
than the default port of 80 or 443 for SSL, you will need to add that to the URL as well. For
example http(s)://hostname:port_number/traveler
Configure the client connection URL by indicating whether clients connect directly to the
Lotus Notes Traveler server or connect through a proxy. If the URL is not currently known,
select Configure later. In our scenario, we select Clients connect to this server
directly.
84 IBM Notes Traveler Hints and Tips for a Successful Deployment
8. Setting the external server URL value:
Specify the external server URL in the field. The URL is validated. Note any warning
dialogs and continue.
In our case, we decided not to use SSL, and went with a HTTP URL. Because of this we
were presented with a warning which we noted, and continued:
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 85
9. Domino upgrade notification:
The Domino Upgrade Pack 1 is required for the XPages web administration and other
functionality. If this is not done, the Lotus Notes Traveler Version 8.5.3 Upgrade Pack 1 will
not run properly.
If Domino 8.5.3 Upgrade Pack 1 is not detected on this system, indicate whether you want
Lotus Notes Traveler to install the prerequisites. This option is checked by default.
When Domino 8.5.3 Upgrade Pack 1 is not installed, select this option and install it. This
option is checked by default.
86 IBM Notes Traveler Hints and Tips for a Successful Deployment
10.Review:
Review your selections. If any changes are required, select Previous to update the
selections, otherwise, select Install to continue.
11.Finishing the installation:
The installation commences and you can see the progress.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 87
Select Done when the installation is completed. If any errors or warnings are reported, review
the installation log and contact IBM Support to resolve any problems.
88 IBM Notes Traveler Hints and Tips for a Successful Deployment
3.3.2 Domino startup and installation validation
On the next startup of Domino, you see that the Lotus Notes Traveler server also starts when
the server is started.
You can validate whether the installation is working correctly by accessing the server in a
browser from a laptop, a desktop machine, or a device.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 89
3.4 Configuration
After the Lotus Notes Traveler is installed, the next step is to configure server. The server
should work correctly without the need for any further configuration out-of-the-box, but there
are sometimes needs to make some configuration changes to the server. We cover the
following topics:
3.4.1, Lotus Domino configuration
3.4.2, Lotus Notes Traveler configuration on page 91
3.4.3, Additional configurations on page 97
3.4.1 Lotus Domino configuration
The Domino server for Lotus Notes Traveler should not also function as your mail server. Note
that Domino Enterprise version is required for Lotus Notes Traveler HA servers. Although you
should follow your normal setup procedures, there are a few items that you should be aware
of on the setup.
Ensure replication is working
When a mobile device connects to the Lotus Notes Traveler server for the first time, a look up
is performed to the Address book to locate the user's mail server. To ensure this information is
correct, the replication must be working. You can verify this from the Lotus Notes Traveler
server console by running rplicate , where FQDN is the fully qualified Domain name of the
90 IBM Notes Traveler Hints and Tips for a Successful Deployment
server from which the Lotus Notes Traveler server is to receive updates, usually the
Administration or a Hub server. If replication does not complete successfully, try running
replicate, where ipaddress is the IP Address of the Administration or Hub server. When the
replication works correctly, open the server console on the Administration or Hub server and
perform the same steps to ensure the replication is working correctly in both directions.
Considerations for the Domino installation
Ensure the installed version of Domino is the most recent version that matches the version
of Lotus Notes Traveler you intend to install. For example, if you plan to install Lotus Notes
Traveler 8.5.3 Upgrade Pack 1, the installed version of Domino must be 8.5.3 Upgrade
Pack
When installing the Upgrade Pack 1 for Lotus Notes Traveler, the installer automatically
upgrades the Domino to 8.5.3 Upgrade Pack 1. Check if there are any fix packs that
must be installed as well through Fix Central
(http://www-933.ibm.com/support/fixcentral).
If the version of Domino about to be installed on the Lotus Notes Traveler server is a
higher version than what is installed on your Administration server, consider one of the
following:
Upgrade Domino or the Address book template on your Administration server to the
same level as to what will be installed on the Lotus Notes Traveler server.
Take steps to not allow the proliferation of the address book on the Lotus Notes
Traveler server to other servers in your domain.
The Domino server that hosts Lotus Notes Traveler must have access to the users mail
servers with Manager and Delete privileges to mail files. When a user deletes an email on
their mobile device, the deletion is carried out by the Lotus Notes Traveler server. This
access might be granted by adding the Lotus Notes Traveler server to the
LocalDomainServers group in many cases, but check your environment for the best
method.
Each user must have an entry in the Lotus Notes Travelers address book, names.nsf, or
the directory assistance must be configured so the users can be found.
Each user must have an HTTP password in their person document, or directory
assistance must be configured so that the user ID and password can be validated.
Each user should have an internet address specified in their person document. In general,
mobile devices work better with Internet addresses than with Domino style addresses.
For example, internet address: username@yourcompany.com
If you are using Internet Site documents and plan on synchronizing the Apple devices,
ensure that the Options command is enabled on the Configuration tab of the Internet Site
document. This is required to register and synchronize Apple devices.
Set 'More name variations with lower security' in the Internet authentication parameter on
the Security tab of the server document. This action resolves many login issues.
Lotus Notes Traveler requires the following notes.ini parameters during startup. Ensure
they have the correct values, or Lotus Notes Traveler can fail to start.
NotesProgram=<pathtoDominoInstallation>
Directory=<pathtoDominoInstallation>\data
Domain=yourcompanyDomainname
ServerName=travelerservername/yourcompanyDomainname
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 91
The Lotus Domino server that is hosting each Lotus Notes Traveler service must have the
HTTP web server component installed.
Note that the HTTP task should not be in the notes.ini ServerTasks line because the
Lotus Notes Traveler service will start HTTP automatically.
Lotus Notes Traveler does not support Roaming Users or Roaming Profiles. All user data
must exist in the mail file on the mail server.
Considerations for the Domino installation on Linux
The Lotus Notes Traveler installation must be done as the root user for proper access, or
the server might not be able to start after installation because of the incorrect file
permission.
This includes running the Lotus Notes Traveler utility (travelerUtil) when setting up the
HA environment.
Running the installer as a user other than root user might cause the install application
to hang and not complete successfully.
If you log in to a Linux system as a non root user and switch to root with the su
command, you might see an error about trying to start the Lotus Notes Traveler
installer in the UI mode, similar to the java.lang.noclassdeffounderror sun awt x1
graphics environment.
This cause of this problem depends on the system configuration, but you can work
around this issue by either logging in to the system using the root user or simply
running the installer in silent mode.
For more information, see Installing in silent mode on Linux operating systems
(http://www-10.lotus.com/ldd/dominowiki.nsf/xpDocViewer.xsp?lookupName=Ad
ministering+Lotus+Notes+Traveler+8.5.3+Upgrade+Pack+1#action=openDocument
&res_title=Installing_in_silent_mode_on_Linux_operating_systems_A853UP1&c
ontent=pdcontent) in the Domino wiki.
Ensure the password of the Domino user is not expired or it might cause the Lotus Notes
Traveler installation application to hang. This is because the operating system will prompt
the installer to change the password.
3.4.2 Lotus Notes Traveler configuration
After the Lotus Notes Traveler server is installed, follow the steps below to configure the
Notes Traveler and verify the installation:
1. Opening the the Server document using the Domino Administrator client.
2. On the Basics tab, ensure the "Server name" and "Fully qualified Internet host name" are
set correctly.
92 IBM Notes Traveler Hints and Tips for a Successful Deployment
3. On the Internet Protocols, HTTP tab, review the value of "Number of active threads". By
default, this value is set to 400 on a 64-bit server and this value can be a good starting
point. However, review this value regularly and update the value as necessary. If the
number of active threads is too low, HTTP 503 (Service not available) errors are
generated. If the value is too high, an excess amount of memory is used. For information
about how to set this value, see 8.4.5 Internet protocols tab. A good rule of thumb for the
proper settings of the "Number of active threads" is 1.2 * the number of devices serviced
by the system, or are planned to be serviced by the system.
4. Go to the Internet Protocols, Domino Web Engine tab.
Review the Memory Caches section.
The Maximum cached users field is used to store a users name, password, and a list of
groups that the user belongs to. A user is added to this cache after they successfully
authenticate with the Lotus Notes Traveler server. The default setting for this field is 64. If
the number of current authenticated users logged in exceeds this value, some
performance improvements may be gained by increasing the number of the Maximum
cached users. To review the current values, look at the statistics from a recent NSD file. As
a general guideline, when adjusting any of the "Domino.Cache.*.Count" statistics, they
should be slightly less than their "Domino.Cache.*.MaxSize" counterpart. In this case, the
"Domino.Cache.User Cache.Count" should be slightly less than the "Domino.Cache.User
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 93
Cache.MaxSize". If the value listed in the Domino.Cache.User Cache.Count is larger than
the Domino.Cache.User Cache.MaxSize, then try slowly incrementing the maximum value
for the "Maximum cached users", as shown in the Memory Cache section screen capture
above, until the Count no longer reaches the Maximum.
5. Go to the Transactional Logging tab.
Disable Transactional Logging. The Lotus Notes Traveler server is not a typical server, as
there is very little writing to Domino databases. With the small number of writes necessary,
it is not necessary to enable Transactional Logging.
Go to the Lotus Traveler tab.
Review the Basics section.
Maximum Memory Size
This is the amount of Java Memory allocated. By default on a 64-bit Domino server,
this is set to 1024 MB (1GB). The Lotus Notes Traveler process is written in Java, so
Java memory must be allocated. The Java memory required also depends on the
number of the devices connected to the Notes Traveler server. Evaluate the system
load and adjust the memory size as necessary. See 9.1 Performance tuning about
the tips to increase this value as necessary.
IPC Socket Ports
These are the TCP ports that are used for the communications between the Lotus
Notes Traveler HTTP servlet and the Lotus Notes Traveler server task and also the
communications among the Lotus Notes Traveler servers. These communications
are only on the local system so no external firewalls ever see this traffic. Rarely, if
ever, will this need to be changed.
External Server URL
This value should be set to the DNS name or IP address that is used to route traffic
to the Lotus Notes Traveler server from the internet or the intranet. This URL
ensures that the server sends a link that the devices can use and should not
change. Include the following in the URL:
Scheme, HTTP or HTTPS
Server host name
Port number (if not a default port)
Path, such as /traveler
94 IBM Notes Traveler Hints and Tips for a Successful Deployment
If the server allows both HTTP and HTTPS, and HTTP is redirected to HTTPS, then
the External URL should be the HTTPS version and not the HTTP version.
In an HA pool, all servers must be configured with the same value for this
parameter. The servers are part of a service pool that is accessed through the
same front end sprayer, and must be configured with the external URL that will send
traffic through that sprayer.
In the Lotus Traveler Access section, the Administrators can select whom to allow
access to the server and what controls the users may have.
When in edit mode the section looks like this:
Access server
If this field is left to the default value of blank, all users are able to access the server,
unless they are excluded in the "Not access sever" field. Optionally, the administrator can
enter individual names of users, servers, and groups to allow access to the Lotus Notes
Traveler server. Separate multiple names with commas or semicolons. To specify all
members of a branch of a hierarchical name tree, enter an asterisk followed by a forward
slash and certifier name, for example, */Sales/Acme. Only users with Person documents in
either the primary directory of this server or any secondary directories that are trusted for
credentials using Domino directory assistance can be added. These values must be
consistent on all Lotus Notes Traveler servers in the pool.
Remote user commands
Enabling this field allows users to issue commands from the Lotus Notes Traveler servlet,
such as displaying all the information about their mobile device. For example, the users
can open the web page http(s):/travelerservername.com/traveler and the following will be
displayed on the web page. The user can select their device and perform any of the
displayed commands.
Administrator tip: It may be simpler to create and use a Configuration
document for all the Traveler servers to ensure that the NTS_EXTERNAL_URL
parameter is pushed down to the notes.ini file on each server.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 95
User managed security
If this field is enabled, users can issue a remote wipe command if their device is lost or
stolen. For example, the users will be able to open the web page
http(s)://travelerservername.com/traveler and the following will be displayed on the web
page. The user will be able to select their device and perform any of the displayed
commands.
Review the Log Settings section
You can set the logging levels here. Do not change the default values unless debugging is
enabled on the server.
Review the Auto Sync Settings section
The last section of the Lotus Traveler tab is Auto Sync settings. These should rarely need
to be changed, if ever. So this will be for informational purposes only.
Administrator tip: Any changes done here for debugging purposes requires a restart
of the Traveler process to enable the changes. An alternative is to change the logging
levels using the server console commands, which will go into effect immediately without
a restart. See 8.1 Server console commands for a full listing of the console commands
on changing logging levels.
96 IBM Notes Traveler Hints and Tips for a Successful Deployment
Polling interval
This set how often the Lotus Notes Traveler server polls the Mail server for any changes,
such as a new email, change in contacts, etc. If changes are found, a prime sync is
created and the mobile device is notified changes have been found.
Port for TCP Connections
This is the TCP Port used by the push engine for communications.
Heartbeat
Normally, it is not necessary to modify the heart beat interval. The heartbeat interval for
each connected client is automatically adjusted by Lotus Notes Traveler to be optimal.
However, the configuration parameters can be tweaked to slightly improve operation. By
default, the Heartbeat Algorithm Maximum Interval is set to 15 minutes in the Lotus Notes
Traveler server configuration document.
If you have devices earlier than Lotus Notes Traveler 8.5.2 that use TCP push, leave the
maximum at 15 minutes. But, if you are running all devices on Lotus Notes Traveler 8.5.2
or later using HTTP push, there are advantages to increasing the maximum setting to 30,
45, or 60 minutes. If you do modify the heartbeat algorithm maximum interval, set it to a
number slightly less than the timeout of the underlying network connection for all users, if
known. For example, if all Lotus Notes Traveler clients are connecting over a VPN that has
an idle timeout of 30 minutes, then set the maximum heartbeat interval to 28 or 29
minutes.
Apple devices use a different heartbeat algorithm (the ActiveSync algorithm). The
ActiveSync algorithm uses the Lotus Notes Traveler minimum and maximum intervals, so
these apply to all devices. The other Lotus Notes Traveler heartbeat algorithm settings
apply only to other devices.
Device Offline Timeout
The Lotus Notes Traveler server will continue to poll the Mail server every 3 seconds (see
Polling Interval above) until the device is considered to be offline. The administrator can
set the amount of timeout period here.
User Cleanup Timeout
This is the number of days a device must be offline before the Lotus Notes Traveler server
will cleanup information in the Lotus Notes Traveler derby database. Note that this does
not remove the entry from the lotustraveler.nsf database, only from the Lotus Notes
Traveler derby database.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 97
3.4.3 Additional configurations
In the simple configuration, IBM Mobile Connect can fill the role of either a reverse proxy or a
VPN server. In this section, we walk through the installation and configuration procedures that
are documented in the official IBM Mobile Connect product Information Center to install IBM
Mobile Connect 6.1.5 on a Windows server in our lab. You can find the official IBM Mobile
Connect product Information Center
(http://publib.boulder.ibm.com/infocenter/lmc/v6r1/index.jsp?topic=/com.ibm.lmc_6.
1.4.doc/home.html).
Installing IBM Mobile Connect
Use these steps to install IBM Mobile Connect on a Windows system:
1. Launch the installer:
Upon running ConnMgr_615_X86.exe, you see:
2. Accept the license agreement:
Accept the license agreement and click Next.
98 IBM Notes Traveler Hints and Tips for a Successful Deployment
3. Destination Folder:
Accept or change the destination folder to where the Lotus Mobile Connect will be
installed.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 99
4. Ready to Install the Program:
Click Install to begin the installation:
5. Acknowledge the virtual adapter device driver:
100 IBM Notes Traveler Hints and Tips for a Successful Deployment
During the installation, you are informed that the virtual adapter device driver is going to
be installed:
6. Continue (Allow the Virtual Adapter installation):
Windows then asks if you want to allow the installation of the virtual adapter. Click
Continue Anyway.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 101
7. Finish:
Click Finish to complete the installation of IBM Mobile Connect and launch the First Steps
screen to begin the process of configuration.
If you want to defer the configuration, you can deselect the Launch option. First Steps can
be launched anytime from the Start menu.
102 IBM Notes Traveler Hints and Tips for a Successful Deployment
Configuring IBM Mobile Connect
After installing IBM Mobile Connect, use the FirstStep utility to configure the resources used
by the server to provide clientless access to Traveler.
The First Steps panel provides links to three utilities which are used to configure IBM Mobile
Connect:
Database Configuration Wizard
Gatekeeper
Key Management utility
These utilities can also be accessed from the Start menu. First Steps is included as a
convenient guide and reminder.
Configuring database
When running IBM Mobile Connect on a Windows system, it is necessary to specify the
storage mechanism.
1. Run First Steps, either selecting at the end of the installation or from the Start menu:
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 103
2. Select Database Configuration:
104 IBM Notes Traveler Hints and Tips for a Successful Deployment
IBM Mobile Connect requires a storage mechanism for its configuration and active session
table. If desired, this can also be used for storing its accounting and billing information.
The options are to use the Local file System, IBM DB2, or Microsoft SQL Server. For a
production system, use either DB2 for Linux, UNIX, and Windows or Microsoft SQL
Server. To simplify this lab exercise, the Local File System was selected. On Windows, this
uses DB2 (a single user version of DB2), which is only available on 32 bit Windows.
Click Database Configuration Wizard.
3. In this panel, Select the desired storage mechanism. We select Local File System. Click
Next:
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 105
4. Database configuration is complete. Click Done.
5. The wizard returns to First Steps initial screen.
6. Select the Gatekeeper from the menu and click the Gatekeeper link to run the
Gatekeeper:
As seen on the figure, Lotus Mobile Connect Gatekeeper comes pre-configured with a
profile and administrator, which can be used to perform the initial configuration. Because
the administrator password is the same for each new installation, change the passwords.
106 IBM Notes Traveler Hints and Tips for a Successful Deployment
Initial configuration of IBM Mobile Connect resources
The Gatekeeper is used to configure and administer IBM Mobile Connect. It is a stand-alone
utility which can be run on a variety of Operating Systems (Windows, Linux, and AIX) and
does not have to run on the same system as the IBM Mobile Connect server component,
which is known as the Connection Manager. If run the Gatekeeper on a different system, it
requires TCP connectivity with the Connection Manager system and a new profile to identify
that system.
The first time you run Gatekeeper, it detects that it is the first time and automatically walk you
through your initial configuration. It does this by detecting the absence of the file wgated.conf
in the Mobile Connect directory. If you ever want to run the initial configuration again, rename
or delete that file.
Initial configuration
Follow these step to perform the initial configuration.
1. Run the Gatekeeper to start the configuration. The Login screen opens. You can either log
in or edit profile. Click Edit profile.
Important: The Gatekeeper includes an excellent set of tips. Whenever you have a
question about what to input, put the focus on that field and click Tips.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 107
2. Select Add Profile to add a new profile.
3. Enter the Login profile name and either a Host name or IP address, then click OK.
4. Log in to the new profile.
108 IBM Notes Traveler Hints and Tips for a Successful Deployment
5. For the first login, you are presented with an informational window. After reading and
closing it, you must configure the Access Manager. This is a server component which acts
as the go between for the Gatekeeper and the Connection Manager.
Click Next to start the configuration.
6. Take the defaults or change as desired and click Next.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 109
7. Choose All for the logging level so that you have complete setup logs. Click Next.
8. Select Finish to configure the Access Manager.
110 IBM Notes Traveler Hints and Tips for a Successful Deployment
9. The next prompt is change the administrator password. It is advisable to do so.
10.After dealing with the administrator password, you are prompted to create a Connection
Manager. This is the primary server component that provides communications between
the user devices and Lotus Notes Traveler.
Click Next to begin to add the Connection Manager.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 111
11.Enter the values desired and click Next:.
12.Configuration OUs provide a means of organizing the configuration display but do not
change behavior of the system.
Most installations take the default here and click Next.
112 IBM Notes Traveler Hints and Tips for a Successful Deployment
13.Click Finish to complete the Connection Manager.
14.Click Yes to begin the configuration of the HTTP Access service.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 113
15.The Service URL defines the address that an user device uses to access IBM Mobile
Connect. It starts with https which means that an SSL connection will be established. To
use SSL, IBM Mobile Connect needs a security certificate. This certificate is provided by
using the Key Management utility as described later.
16.The Application server URL points to Lotus Notes Traveler. Note that the Authentication
Profile is listed as System because that is the only one available. Click Next to proceed
with the configuration.
114 IBM Notes Traveler Hints and Tips for a Successful Deployment
17.Accept or change the defaults and click Finish to complete the configuration.
18.Mobile access service is not used by Apple and Android devices, so click No.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 115
19.The Connection Manager can manage its own user accounts or use an external
authentication server. We chose the latter, so click No.
20.Further configuration is needed, so click No.
This completes the initial configuration of IBM Mobile Connect. Further configuration is
required to simplify authentication.
Authentication configuration
To enable the IBM Mobile Connect Connection Manager to use the Domino credentials for
user authentication, you have to create a Directory Services Server (DSS) that will access the
LDAP function of Domino. The DSS is referenced by a new Authentication Profile (AP).
Finally, the HTTP Access Service previously defined is modified to make use of the new AP.
1. Create a Directory Services Server:
a. In Gatekeeper on the Resource tab, right-click Mobile Connect Add Resource
Director server .
116 IBM Notes Traveler Hints and Tips for a Successful Deployment
b. Provide a Common name, the name or address of the server, and Base distinguished
name, then click Next.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 117
c. If the Domino LDAP function is configured for anonymous bind, Administrator's
credentials are not needed.
Enter the values needed and click Next.
d. Accept or change the OU configuration and click Finish.
118 IBM Notes Traveler Hints and Tips for a Successful Deployment
2. Create an Authentication Profile.
a. In Gatekeeper on the Resource tab, right-click Mobile Connect Add Resource
Authentication Profile LDAP-bind Authentication.
b. Provide a Common name and Description, then click Next.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 119
c. Select the Directory Server and User key field, then click Next.
d. Configure LTPA to enable Single Sign-On (SSO), then click Next.
120 IBM Notes Traveler Hints and Tips for a Successful Deployment
For a complete discussion about SSO, see SSO
(http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Lotus_Mobile_Connect_Providin
g_secure_remote_access_to_Traveler_servers).
e. Accept or change the organization OU and click Finish.
3. Modify the HTTP Access Service to use the new Authentication Profile.
a. In Gatekeeper on the Resource tab, right-click http-service0 Properties.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 121
b. On the Mode tab, change Credential challenge type to HTTP 401 basic authorization
challenge and change Authentication Profile to the one just created.
122 IBM Notes Traveler Hints and Tips for a Successful Deployment
c. On the Lotus Mobility tab, select Enable Lotus Traveler integration and click OK.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 123
d. On the General tab, set the maximum number of processing threads.
Important: The number of simultaneous sessions and number of processors are
considerations for setting this value. The recommended value for a two-processor
system with 1000 simultaneous sessions is 5 .
124 IBM Notes Traveler Hints and Tips for a Successful Deployment
Key Management
The Key Management utility is used to provide IBM Mobile Connect with a security certificate
so that it can establish an SSL connection. Either a self-signed certificate or one acquired
from a Certificate Authority can be used. It should be noted that Android devices are known to
have problems with self-signed certificates; see Lotus Mobile Installer for Android
(http://www-01.ibm.com/support/docview.wss?uid=swg21457494).
You can run the Key Management utility from either the First Steps window or the Start menu.
1. Run the Key Management utility and open your key database.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 125
The key database needs to be of type CMS. The default provided is http.trusted.kdb which
is found in the Connection Manager directory.
2. When you open the key database, you are prompted for its password. The default is
trusted.
3. To create a self-signed certificate, go to the Personal Certificates section and click New
Self-Signed.
126 IBM Notes Traveler Hints and Tips for a Successful Deployment
4. Enter a label and click OK to complete the process.
5. In order to get a certificate from a Certificate Authority, go to Personal Certificate
Requests and click New.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 127
6. Fill in the label and click OK.
128 IBM Notes Traveler Hints and Tips for a Successful Deployment
7. Click OK and include the created file in the request to the Certificate Authority.
8. When the certificate is received, navigate to the Personal Certificates section and click
Receive.
Chapter 3. Deploying a stand-alone Lotus Notes Traveler environment 129
For some certificates, you need to receive and import intermediate and signer certificates
from the Certificate Authority.
Ready To Run
Your Connection Manager is now ready to run. In Gatekeeper on the Resources tab,
right-click the Connection Manager resource and select Startup.
130 IBM Notes Traveler Hints and Tips for a Successful Deployment
Copyright IBM Corp. 2013. All rights reserved. 131
Chapter 4. Deploying a high availability
Lotus Notes Traveler
environment
In this chapter, we go over the end-to-end deployment of a high availability (HA) IBM Lotus
Notes Traveler server.
There are two main influencing factors to choose a stand-alone server versus an HA Lotus
Notes Traveler implementation. These include:
The number of devices that the Lotus Notes Traveler is to service.
The requirement about the up-time or availability if the a server instance becomes
unavailable.
In our scenario, we have a medium sized company that implements the Lotus Notes Traveler
solution. This company must service about 2,000 devices and must have their sales staff able
to access their email from the road 24x7.
Given the number of devices, a stand-alone server can provide the services required.
However, 2,000 devices is the limit for a stand-alone server and leaves no room for growth.
The need for the sales team to have reliable constant access to their email requires the
solution to be implemented in a high availability environment. To provide 24x7 availability, we
must provide backup servers to service the client devices if one of the servers, including the
Lotus Notes Traveler server, becomes unavailable for some reason (server patch, upgrade,
crash, operating system issue, and so on).
Installation, configuration, and user deployment are three major milestones in deploying an
IBM Lotus Notes Traveler environment. We cover the installation and configuration in this
chapter. User deployment to devices is covered in full detail in Chapter 5, User deployment
on page 171.
4
132 IBM Notes Traveler Hints and Tips for a Successful Deployment
4.1 Scenario description
In this scenario, we deploy an IBM Lotus Notes Traveler server with the same methodology
that a medium to large business would use. This solution introduces a high availability (HA)
Lotus Notes Traveler server into an existing Lotus Domino environment. We will need to install
a new Domino server(s) into this environment to host the additional Lotus Notes Traveler
server(s) in the internal network and communicate with the devices and the web
administration for Lotus Notes Traveler by using an internet facing HTTP server/IP Sprayer in
the DMZ.
The following diagram shows the architecture of this scenario:
In this chapter, we walk through both the Linux and Windows installation procedures for Lotus
Notes Traveler, and cover the integration with an IBM DB2 database for Linux, and Windows
operating systems and a Microsoft SQL Server database.
4.1.1 Planning considerations
In this scenario, we build a server for a medium size business that has to serve approximately
2,000 devices. The need to have the mobile devices continuously available is great because
many of the sales teams are mobile and must have access to their calendars, contacts, and
email while on the road.
We implement a high availability Lotus Notes Traveler solution with the following
considerations:
2,000 devices to be serviced:
A single Lotus Notes Traveler 8.5.3 Upgrade Pack 1 server can services up to 2000
devices. Though a single Lotus Notes Traveler server can satisfy the current requirement,
we want to provide room for the future growth.
Continuous availability
An HA Lotus Notes Traveler solution provides both pooled and redundant systems for
Lotus Notes Traveler, the IP Sprayer, the enterprise database server, and Domino mail
servers. The redundant systems will provides the services in case the primary system has
an outage or requires maintenance.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 133
In this scenario, we focus on the implementation of a highly available Lotus Notes Traveler
system.
Reference 2.2, Choosing a stand-alone or high availability configuration for Lotus Notes
Traveler on page 31 for further information about the decision process of choosing
stand-alone versus high availability architecture.
In this architecture, a "gateway" or HTTP access into the internal network is required. We
choose to use Lotus Mobile Connect v6.1.5 as a reverse proxy combined with the new IP
Sprayer functionality. The IP Sprayer distributes incoming request in a round-robin pattern so
that if one Lotus Notes Traveler server in the pool becomes unavailable then the second
server can receive the request.
With our scenario, we create a single server pool containing two Lotus Notes Traveler
servers.
The binaries for Lotus Notes Traveler can be downloaded from the IBM Passport Advantage
website. The binaries include both the 64-bit and 32-bit version in the same package. Upon
installation, the installer detects the bit architecture version of Domino that it is being installed
upon and uses that version of the Lotus Notes Traveler code.
For the enterprise database, we demonstrate two different scenarios:
Integrate the Lotus Notes Traveler servers with an IBM DB2 for Linux, UNIX, and
Windows.
Integrate the Lotus Notes Traveler servers with a Microsoft SQL Server enterprise
database.
Lotus Notes Traveler supports both relational database management systems. The Lotus
Notes Traveler server includes a limited entitlement to IBM DB2 for Linux, UNIX, and
Windows.
To support Blackberry Enterprise servers (BES), Microsoft SQL Server is a required back-end
database and so if you want to support BES with the database server which is used by the
Lotus Notes Traveler server, select Microsoft SQL Server.
You can use a Domino mail server of any version after 7.0.2 on any Domino supported
platform. In our lab environment, we built the mail server on a Linux machine.
4.2 Installation
In this section, we cover the installation of the high availability (HA) Lotus Notes Traveler
server.
After walking through the steps for installing the Lotus Notes Traveler servers, we show the
installation of the IBM DB2 Workgroup Server for Linux, UNIX, and Windows. A limited
license to IBM DB2 Workgroup Server for Linux, UNIX, and Windows is provided with the
license to the Lotus Notes Traveler 8.5.3 Upgrade Pack 1 software. We then discuss the
database server configuration and the database creation for the conversion of a stand-alone
traveler server into a HA traveler server pool.
Finally, we run the commands that insert the Lotus Notes Traveler server into the HA pool to
create the pool of Lotus Notes Traveler servers.
134 IBM Notes Traveler Hints and Tips for a Successful Deployment
These are addressed in the following subsections:
4.2.1, Lotus Notes Traveler installation
4.2.2, Database installation
4.2.3, Load balancer installation
4.2.1 Lotus Notes Traveler installation
The base Domino servers are all part of the same domain and can be managed from one
central Domino admin client. The names.nsf (Domino directory) is replicated amongst all the
Domino servers in the environment to allow for each server to maintain the users and their
access to the system.
These are the steps that we captured when installing the Domino servers to be used as the
hosts for the Lotus Notes Traveler servers. If you already have Domino servers in the
environment that you can dedicate to Lotus Notes Traveler, then you can continue to the
Lotus Notes Traveler installation segment of this section. The installation of Domino is
documented here because it is important that the Domino servers are configured to be aware
of the other servers in the environment.
Domino installation
Use these steps to install the Domino server:
1. Start the installer:
If installing from eAssembly, start the eAssembly and follow the installation steps.
If installing from DVD, simply insert the DVD into the target system's DVD ROM drive. If
autorun is enabled for the system, the Common Launchpad starts automatically. If
autorun is disabled, navigate to the DVD content and double-click Launchpad.exe.
2. Accept the licence for the product:
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 135
3. Choose the installation directory:
4. Choose the installation data directory:
136 IBM Notes Traveler Hints and Tips for a Successful Deployment
5. Select which server type to use:
For high availability, you must use the enterprise version of the software. Select Domino
Enterprise Server.
6. The installation begins and provides status:
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 137
7. Installation complete:
After you select Finish, do not attempt to start and configure the server until you have first
registered this in the Domino environment. This is covered in 4.3.2, Database
configuration on page 156.
Traveler installation
After you have properly configured the Domino server into the environment, the next task is to
install the Lotus Notes Traveler server. All Lotus Notes Traveler installations begin as
stand-alone versions of the product. It is not until you add these servers into the central
138 IBM Notes Traveler Hints and Tips for a Successful Deployment
enterprise database that the servers go from being a stand-alone server to a member of the
Lotus Notes Traveler pool.
For Lotus Notes Traveler installation on Linux, see 3.2, Lotus Notes Traveler installation on
Linux on page 67.
For Lotus Notes Traveler installation on Windows, see 3.3, Lotus Notes Traveler installation
on Windows on page 79.
After the server is installed as a stand-alone server and initialized, you can add this sever to
the Lotus Notes Traveler pool, and achieve high availability. We discuss the Notes Traveler
configuration for high availability in 4.3.3, Lotus Notes Traveler configuration for high
availability on page 163.
4.2.2 Database installation
The Lotus Notes Traveler High Availability (HA) mode requires an enterprise database to
store Lotus Notes Traveler data that is accessed by all Lotus Notes Traveler servers in a
common service pool. Lotus Notes Traveler 8.5.3 Upgrade Pack 1 release included a limited
entitlement to IBM DB2 Workgroup for Linux, UNIX, and Windows. This limited entitlement is
provided for customers who want to deploy a Lotus Notes Traveler High Availability server but
do not already have a relational database management system. The DB2 entitlement is to be
used to support Lotus Notes Traveler and not for any other purpose.
In a HA Lotus Notes Traveler solution, the enterprise database holds the user data and
security data. This enterprise database system should also be enabled for high availability to
avoid the database server from being a single point of failure. In this section, we show a
simple DB2 installation on a Windows platform. For more information about DB2 installation,
configuration, and high availability setup, see the IBM Redbooks publications:
Up and Running with DB2 on Linux, SG24-6899
DB2 Deployment Guide, SG24-7653
High Availability and Disaster Recovery Options for DB2 for Linux, UNIX, and Windows,
SG24-7363
DB2 version
The Lotus Notes Traveler High availability support requires:
DB2 Enterprise Server Edition Version 9.7, Fixpack 5 or higher
DB2 Workgroup Server Edition Version 9.7, Fixpack 5 or higher
64-bit version platform is suggested. It is not required that the DB server platform match the
Notes Traveler server platform. Although it is possible to deploy DB2 together with Domino
and Traveler, it is not advisable. DB2 should be deployed on its own server.
Installing DB2
We perform the following steps to install the DB2 included in Notes Traveler 8.5.3 on a
Windows server:
1. Begin with DB2 setup Launch pad. Click Install a Product and click Install New.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 139
2. Accept software licence agreement:
In the Software Licence Agreement panel, accept the licence for the product and click
Next.
140 IBM Notes Traveler Hints and Tips for a Successful Deployment
3. Select the installation type:
The typical setup includes basic database server function, database administration tools,
and most product features and functionality. This is sufficient for Lotus Notes Traveler.
4. Select the installation, response file creation, or both:
You are presented with the option of saving the installation choices in a response file,
performing the installation, or both. You can also specify the location (path) and file name
for the response file. The response file allows you to save this installation options selected
for deploying to other server. Select Install DB2 Workgroup Server Edition on this
computer and save my settings in a response file.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 141
5. Select the installation folder:
The default installation folder is set for you. However, you can change the installation path.
142 IBM Notes Traveler Hints and Tips for a Successful Deployment
6. Select user information for the DB2 Administration Server:
In this panel, provide domain user information for the DB2 administration. For Local
System account, the default user name is db2admin. Assign a password for Lotus Traveler
High Availability configuration.
7. Configure DB2 instances:
The default DB2 instance name on Windows is DB2. To change the name, click
Configure.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 143
8. Prepare the DB2 tools catalog:
The DB2 tools catalog is required for using the Task Center and scheduler. This step is
optional.
144 IBM Notes Traveler Hints and Tips for a Successful Deployment
9. Set up notifications:
Set up notifications here if you want to receive e-mail or pager notification when a
database needs attention. This step is optional.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 145
10.Enable operating system security for DB2 objects:
Specify if you want to enable operation system security for DB2 files, folders, registry keys,
and other objects on your computer. This step is optional.
146 IBM Notes Traveler Hints and Tips for a Successful Deployment
11.Start copying files and create response file:
When you click Finish, all your selections are saved in the response file that you specified
and the installation process starts.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 147
12.Complete installation:
DB2 installation is now completed. You can start to create a database for Lotus Notes
Traveler. This is covered in 4.3.2, Database configuration on page 156.
4.2.3 Load balancer installation
The procedure to install and configure IBM Mobile Connect 6.1.5 to function as a Reverse
Proxy is documented in 3.4.3, Additional configurations on page 97. You can use the same
procedure to install IBM Mobile Connect to serve as a load balancer.
4.3 Configuration
The configuration is broken down into two sections. The first section is about Lotus Domino
configuration and which settings should be considered. The second section is about settings
specific to Lotus Notes Traveler.
4.3.1, Lotus Domino configuration on page 147
4.3.2, Database configuration on page 156
4.3.3, Lotus Notes Traveler configuration for high availability on page 163
4.3.4, Configuring the selected load balancer on page 168
4.3.1 Lotus Domino configuration
The Domino server for Lotus Notes Traveler should be set up as you would your mail servers.
Note that Domino Enterprise version is required for Lotus Notes Traveler HA. Although you
148 IBM Notes Traveler Hints and Tips for a Successful Deployment
should follow your normal setup procedures, there are a few items you should be aware of on
the setup.
Considerations for the Domino installation:
Ensure the installed version of Domino is the most recent version that matches the version
of Lotus Notes Traveler you intend to install. For example, if you are planning to install
Lotus Notes Traveler 8.5.3 Upgrade Pack 1, the installed version of Domino should be
8.5.3 as well. Domino will automatically be updated to 8.5.3.3 when the Upgrade Pack 1
for Lotus Notes Traveler is installed. As a further caveat, always check to see if there are
any fix packs that should be installed. That can be found at Fix Central. If the most recent
version of Domino is a higher version than what is installed on you Administration server,
you will need to consider upgrading the installed version on your Administration server, or
upgrade to the same template for the Public Address book as what will be used on the
Lotus Notes Traveler server, or take steps to not allow the proliferation of the address book
on the Traveler server to other servers in your domain.
The Domino server that hosts Lotus Notes Traveler must have access to the users mail
servers with Manager and delete privileges to mail files. When a user deletes an email on
their mobile device, the deletion is carried out by the Lotus Notes Traveler server. This
access may granted by adding the Lotus Notes Traveler server to the LocalDomainServers
group in many cases, but check your environment on the best method.
Each user must have an HTTP password in their person document, or directory
assistance must be configured so that the user ID and password can be validated.
Each user should have an Internet address specified in their person document. In general,
mobile devices work better with Internet addresses than with Domino style addresses.
for example - Internet address: username@yourcompany.com
Each user must have an entry in the Lotus Notes Travelers address book, names.nsf, or
directory assistance must be configured so the users can be found.
If you are using Internet Site documents and plan to sync Apple devices, ensure that the
Options command is enabled on the Configuration tab of the Internet Site document. This
is required to register and sync Apple devices.
Set 'More name variations with lower security' in the Internet authentication parameter on
the Security tab of the server document. This action resolves many login issues.
Lotus Notes Traveler requires the following notes.ini parameters during startup. Ensure
they have the correct values, or Lotus Notes Traveler may fail to start.
NotesProgram=
Directory=
Domain=yourcompanyDomainname
ServerName=travelerservername/yourcompanyDomainname
Each Lotus Domino server that is hosting the Lotus Notes Traveler service must have the
HTTP web server component installed. Note the HTTP task should not be in the notes.ini
ServerTasks line. Traveler will start this task automatically when it has launched.
Note that Lotus Notes Traveler does not support Roaming Users or Roaming Profiles. All
of the user's data must exist in the mail file on the mail server.
Considerations for the Domino installation on Linux
The Lotus Notes Traveler installation must be done as the root user for proper access;
otherwise, the server may not be able to start after installation due to incorrect file
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 149
permissions. The Lotus Notes Traveler utility (travelerUtil) when setting up the HA
environment must also be run as the root user. Running the installer as a user other than
root user may cause the install application to hang and not complete successfully.
If you login to a Linux system as a non-root user and SU to root, you may see an error
trying to launch the Lotus Notes Traveler installer in UI mode, similar to
java.lang.noclassdeffounderror sun awt x11graphicsenvironment. This depends on the
system configuration, but you can work around by either logging in to the system using
the root user or by simply running the installer in silent mode (for more information, see
Installing in silent mode on Linux operating systems in the Domino wiki).
Ensure the Domino user's password is not expired or it may cause the Lotus Notes
Traveler installation application to hang because the OS will prompt the installer to change
the password.
In this scenario we set up a new Traveler pool, consisting of two new Lotus Notes Traveler
servers. Creating the new Domino Servers is the first step in setting up the Lotus Notes
Traveler pool. When setting up the Traveler servers, ensure to follow your corporate standards
when setting up Domino servers. The configuration tasks include:
Registering the Domino Server to create the server.id
Setting up the Domino Server to ensure the values are correct for the Traveler server
We illustrate the Domino Server configuration on a Windows system.
Registering a new Domino Server
From the Domino administration client tool bar menu, click the Configuration tab, select
Registration Server.
Enter the information for the new server that you are registering with the Domino
environment.
150 IBM Notes Traveler Hints and Tips for a Successful Deployment
Setting up the new Domino server
Follow the steps below to setup the Domino server:
1. Start the server setup by launching the Lotus Domino Server. On Windows system, click
the Lotus Domino Server icon. On a Linux system, open a command prompt to the
notesdata directory and run /opt/ibm/lotus/bin/server from the command line. When
starting Domino Server for the first time, Domino server launches the configuration steps
automatically.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 151
2. Select Set up an additional server to add this new Domino Server to the existing Domino
domain.
3. If you have an Administrator ID registered, select The server ID file is stored in the
Domino Directory and provide a password. Optionally, if you did not use a password for
the server.id created, you must copy the ID file to the server or network drive and select
Browse to locate the ID.
152 IBM Notes Traveler Hints and Tips for a Successful Deployment
4. Enter the server name.
Enter the same server name that you have registered with the Domino administration
client. This field is automatically filled in for you after you have selected the ID in the
previous step.
5. Select the internet services.
The Lotus Notes Traveler requires the HTTP services, so select Web Browser (HTTP
Servers).
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 153
6. Verify the network settings and click on Next.
7. Enter the server name and, optionally, the network address for the Administration or Hub
server from which the Lotus Notes Traveler server will receive updates.
154 IBM Notes Traveler Hints and Tips for a Successful Deployment
8. Select Set up as a primary Domino Directory to set the directory type to be used for this
Domino server. Also select Create a replica of the Directory Assistance database to
create a replica if one is in use in your environment and is to be used on the Lotus Notes
Traveler sever.
9. Secure the server by selecting Prohibit Anonymous access to all databases and
templates. Select Add LocalDomainAdmins group to all databases and templates to
include LocalDomainAdmins to all access control lists (ACL).
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 155
10.Verify the installation option selected. If you are satisfied with all of the selections, Click
Setup to start the Domino Server setup.
11.It will take several minutes to compete the Setup. Progress can be monitored as shown
below. When complete click Done.
156 IBM Notes Traveler Hints and Tips for a Successful Deployment
12.This completes the configuration. Reboot the operating system to ensure the Domino
server launches automatically.
4.3.2 Database configuration
In this section, we show how to use DB2 Control Center to create a database for Lotus Notes
Traveler. You can also use create database statement using command line.
When using DB2 for Linux, UNIX, and Windows as the enterprise database server for Lotus
Notes Traveler, Lotus Notes Traveler is a DB2 application. If the database server is dedicated
to Lotus Notes Traveler, the tuning consideration can just focus on Lotus Notes Traveler.
When Lotus Notes Traveler is sharing the database server with other applications, the
database administrator will have to balance the resources among the applications. We
introduce the initial DB2 server configuration using DB2 Configuration Advisor.
To configure the DB2 HADR to provide the high availability, see High Availability and Disaster
Recovery Options for DB2 for Linux, UNIX, and Windows, SG24-7363.
Creating a DB2 database
To create a DB2 database through Control Center, use these steps:
1. Launch the DB2 Control Center and select Create Database Standard.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 157
2. Follow the Create Database Wizard. Fill in the Database name, In this example, it is called
traveler.
3. Specify the locale Code set as UTF-8.
158 IBM Notes Traveler Hints and Tips for a Successful Deployment
4. Click through and click Finish. This will create the traveler database. Note: You do not
need to create tables at this point. Lotus Notes Traveler server will automatically create
tables during configuration. Go to section 4.3.3, Lotus Notes Traveler configuration for
high availability on page 163 to configure Lotus Notes Traveler server to use DB2.
Locating the DB2 connection port number
To locate the DB2 server name and port number:
1. Open the DB2 Control Center on the Windows server.
2. Right-click one of the available instances for the local machine.
3. Click Setup Communications.
4. Click Properties. The port number is listed in the Properties window.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 159
Tuning the DB2 database
Follow this steps to configure database.
1. From the Control Center, right-click your database and select Configuration Advisor.
2. Select Server to specify how much of this server's memory can be used. Assuming the
database server is dedicated to Lotus Notes Traveler, you can select 80% target memory
to allow system to use almost all of the memory for this database.
160 IBM Notes Traveler Hints and Tips for a Successful Deployment
3. For the type of workload, select Mixed.
4. Specify a typical database transaction. Select More than 10 (long transactions) and set
the Transaction per minute (estimate) to 120.
5. Specify a database administration priority. Select faster performance.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 161
6. Select No data populated.
7. Estimate the number of applications connected. For example, if your DBMaxPoolSize is
set as 2000, then you have to set Average number of connected remote applications to
2010.
8. Select default Cursor stability as the isolation level.
162 IBM Notes Traveler Hints and Tips for a Successful Deployment
9. Review your selection and click Finish to perform the changes.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 163
4.3.3 Lotus Notes Traveler configuration for high availability
To add a Lotus Notes Server into the High Availability (HA) pool, you use the travelerUtil
command to associate the Lotus Notes Traveler server with the enterprise database.
When the Lotus Notes Traveler server is set to use the enterprise database, all of the local
Derby database information is copied to the central enterprise database. Along with this
information, the server is listed in the database tables so that the other Lotus Notes Traveler
servers are aware of each of the servers that are available in the HA pool.
Starting with Notes Traveler 8.5.3 Upgrade Pack 1 release, pooled Notes Traveler servers
share the load by balancing the users across the server pool. The load balancing algorithm is
based on Notes Traveler Availability Index (AI where 100 is 100% available) plus biases.
Each active user is assigned to one Notes Traveler server in the pool. The user stays active in
the pool for 24 hours from last time the user device contacted the pool. This assigned server
monitors the user's mail file for changes so that when the devices comes back in the server
will be up to date on changes that need to be sent to the device.
On each request from the device, the load balancing algorithm in the Traveler server
determines which server in the pool is the best to handle the request. The best server is
defined by comparing all of the servers relative AIs with each other, and the server with the
best relative AI becomes the assigned server and handles the request for that user. If a new
server has a better AI including biases than the current monitoring server, then the user is
routed to the new server and that new server will become the new monitoring server.
The biases are determine by adding NTS_ROUTE_CURRENT_BIAS (default value of 20) to
the AI for the server that is current assigned to monitor the user and adding
NTS_ROUTE_LOCAL_BIAS (default value 10) to the server that has the current request from
the device. This bias is built into the algorithm so users do not keep getting bounced from
server to server. So, once a user is being monitored by a server, that user will typically stay on
the same server unless the loads between the servers in the pool becomes significantly
unbalanced.
The following table shows examples of different AIs and how the message was routed. In
each example, Server 1 is where the request was received and Server 3 is the current
monitoring server.
Configuring Lotus Notes Traveler with DB2
Lotus Notes Traveler on a Windows system
On Windows, you must run the Lotus Notes Traveler configuration commands on the server
as a user with administrator permission.
1. Ensure that the Lotus Notes Traveler database is created on the DB2 server and is
available. No tables need to be created in this database. All of the tables will be created by
the first Lotus Notes Traveler server to be added to the database.
2. Locate the db2jcc4.jar under the directory \sqllib\java\ on the DB2 server. Copy the
db2jcc4.jar from the DB2 server to the \Traveler\lib directory.
164 IBM Notes Traveler Hints and Tips for a Successful Deployment
3. Open a Windows command prompt and change the directory to \traveler\util.
4. 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>
The travelerUtil.cmd is created on each server during installation of Lotus Notes
Traveler. If there is a problem with this command, see Chapter 9, Tuning and
troubleshooting on page 375.
The URL for DB2 consists of the fully qualified host name of the database server, the port
for the database instance (the default value is 50000), and the database name. For
example:
travelerUtil db set url=jdbc:db2://dbserver.yourco.com:50000/traveler
user=db2admin pw=passw0rd
The utility validates the DB2 information by verifying that it can connect to the database.
Upon successfully connecting to the database, Lotus Notes Traveler is configured to use
the DB2 database 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, the command prompts you for all required parameters (the DB2 URL, the database
administration ID, and the database administration password).
To validate the configuration, use the travelerUtil db show command (this command does
not show the password) or the travelerUtil db check command to verify that the
configuration allows database connections to be made. You can use the same utility to update
the password in the event that becomes necessary.
Lotus Notes Traveler on a Linux system
On Linux, you must run the configuration commands on the server as a user with root
permission.
1. Ensure that the Lotus Notes Traveler database is created and available.
Tip: Go to 4.3.2, Database configuration on page 156 for instruction on locating the
DB2 connection port number.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 165
Locate the db2jcc4.jar under the \sqllib\java\ on the DB2 server. Copy the db2jcc4.jar
from the DB2 server to the lib directory. By default, the lib directory is under the following
path:
{code}/opt/ibm/lotus/notes//linux/Traveler/lib{:code}
2. From a command prompt, change the directory to \traveler\util.
3. 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>
The travelerUtil is created on each server during installation of Lotus Notes Traveler. If
there is a problem with this command, see Chapter 9, Tuning and troubleshooting on
page 375.
The URL for DB2 consists of the fully qualified host name of the database server, the port
for the database instance (the default value is 50000), and the database name. For
example:
travelerUtil db set url=jdbc:db2://dbserver.yourco.com:50000/traveler
user=db2admin pw=passw0rd
The utility validates the DB2 information by verifying that it can connect to the database.
Upon successfully connecting to the database, Lotus Notes Traveler is configured to use
the DB2 database 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, the command prompts you for all required parameters (the DB2 URL, the database
administration ID, and the database administration password).
Tip: Go to 4.3.2, Database configuration on page 156 for instruction on locating the
DB2 connection port number.
166 IBM Notes Traveler Hints and Tips for a Successful Deployment
To validate the configuration, use the travelerUtil db show command (this command does
not show the password) or the travelerUtil db check command to verify that the
configuration allows database connections to be made. You can use the same utility to update
the password in the event that becomes necessary.
Configuring Lotus Notes Traveler with Microsoft SQL Server
Lotus Notes Traveler on a Windows system
On Windows, you must run the Lotus Notes Traveler configuration commands on the server
as a user with administrator permission.
1. Ensure that the Lotus Notes Traveler database is created and available.
2. Copy sqljdbc4.jar to the \Traveler\lib directory.
Download the Microsoft SQL Server JDBC Driver 3.0 from
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=21599
The jar file is located in the *.tar.gz file located on that download page. You have to
download the *.tar.gz file and expand the file to obtain the current version of the driver.
3. Open a command prompt and change the directory to \traveler\util.
4. 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
The utility validates the SQL Server DB information by verifying that it can connect to the
database. Upon successfully connecting to the database, Lotus Notes Traveler is
configured to use the SQL Server database 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, the command prompts you for all required parameters
(the database URL, the database administration ID and password).
Tip: Go to 4.3.2, Database configuration on page 156 for instruction on locating the
DB2 connection port number.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 167
To validate the configuration, use the travelerUtil db show command (this command does
not show the password) or the travelerUtil db check command to verify that the
configuration allows database connections to be made.
Lotus Notes Traveler on a Linux machine
On Linux, you must run the configuration commands on the server as a user with root
permission.
1. Ensure that the Lotus Notes Traveler DB is created and available.
2. Copy sqljdbc4.jar to the Lotus Notes Traveler lib directory.
Download the Microsoft SQL Server JDBC Driver 3.0 from
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=21599
The jar file is located in the *.tar.gz file located on that download page. You have to
download the *tar.gz file and expand this to obtain the current version of the driver.
By default, the lib directory is located at /opt/ibm/lotus/notes//linux/Traveler/lib.
3. From a command prompt and change the directory to \traveler\util.
4. 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
jdbc:sqlserver://dbserver.yourco.com:1433;databasename=TRAVELER
Important: There are many URL formats allowed for SQL server. See the SQL
documentation for all possible variations. One common variation is using a database
mirror. If using a mirror, you add ;failoverPartner=hostname to the end of the URL.
Tip: The URL parameter for SQL Server on Linux will not work because of the required
semicolon. You will be prompted for your database URL. The following example shows
a sample database URL for an SQL server:
168 IBM Notes Traveler Hints and Tips for a Successful Deployment
The utility validates the SQL Server DB information by verifying that it can connect to the
database. Upon successfully connecting to the database, Lotus Notes Traveler is
configured to use the SQL Server database 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, the command prompts you for all required parameters
(the database URL, the database administration ID and password).
To validate the configuration, use the travelerUtil db show command (this command does
not show the password) or the travelerUtil db check command to verify that the
configuration allows database connections to be made.
4.3.4 Configuring the selected load balancer
The procedure to install and configure IBM Mobile Connect 6.1.5 to function as a reverse
proxy is documented in Additional Configurations. To modify IBM Mobile Connect to function
as a load balancer, change two fields in the HTTP Access service resource:
1. In Gatekeeper on the Resources tab, right-click http-service0, then select Properties.
Tip: Go to 4.3.2, Database configuration on page 156 for instruction on locating the
DB2 connection port number.
Important: There are many different URL formats allowed for SQL server. See the SQL
documentation for all possible variations. One common variation is using a database
mirror. If using a mirror you would add ;failoverPartner=hostname to the end of the URL.
Chapter 4. Deploying a high availability Lotus Notes Traveler environment 169
2. Go to the Server tab, add the additional Lotus Notes Traveler servers to the Application
server URL in a comma separated list. Select Balanced in the Scheduling algorithm.
Click OK.
170 IBM Notes Traveler Hints and Tips for a Successful Deployment
Copyright IBM Corp. 2013. All rights reserved. 171
Chapter 5. User deployment
After the IBM Lotus Notes Traveler is installed, next step is to deploy the Lotus Notes Traveler
application to the devices. We describe both the conventional and unconventional deployment
options and cover the following topics:
5.1, User provisioning on page 172
5.2, Installation and configuration on an Apple device on page 177
5.3, Installation on an Android device on page 199
5.4, Installation on a Windows mobile device on page 223
5.5, Installation on a Sybian or Nokia device on page 250
5.6, Unconventional deployment options on page 256
5
172 IBM Notes Traveler Hints and Tips for a Successful Deployment
5.1 User provisioning
As an administrator, you can determine which users will have access to the Lotus Traveler
server. You can allow or block a set of users from your directory for the server access.
We cover the configuration details in the following sections:
5.1.1, Access to the Lotus Notes Traveler server
5.1.2, Access control list configuration
5.1.3, User authentication
5.1.1 Access to the Lotus Notes Traveler server
The Lotus Notes Traveler administrator can control the access to the Lotus Notes Traveler
server by using the Lotus Traveler tab in the server document.
The following figure shows the section of the Lotus Traveler tab where you can control the
access to the Lotus Notes Traveler server:
In edit mode of the server document, the above figure appears like this:
Access server
Chapter 5. User deployment 173
This option controls access to the Lotus Notes Traveler server for users with person
documents in all the configured directories of the server whether primary or secondary.
You have the option of selecting individual names of users and groups to allow access to
the Lotus Notes Traveler server.
The default blank value means that all certified users can access the Lotus Notes Traveler
server except any listed in the Not access server field.
To specify all members of a branch of a hierarchical name tree, you can enter an asterisk
followed by a forward slash and certifier name, for example, */OU/O.
Not access server
You can use this option to select names of users or groups who should not have access to
the Lotus Notes Traveler server.
The default blank value means that no users are denied access.`
To specify all members of a branch of a hierarchical name tree, you can enter an asterisk
followed by a forward slash and certifier name, for example, */OU/O.
You can also use the Access server field in the Security tab of server document to deny
access, entering names in the Access server field automatically denies access to those
not listed in the field. The figure below shows the section in the server document:
Remote user commands
If this option is enabled, it will allow Lotus Notes Traveler users to issue remote user
commands from the Lotus Notes Traveler user home page from a browser.
These remote commands include:
Delete - Delete the Lotus Traveler data for the device
Reset - Force a sync reset for the device
Stop Sync - Stops any active syncs for the device
User managed security
This option controls whether the user has access to user managed security commands
from the Lotus Notes Traveler user home page from a browser.
From the browser the user cab run these commands if this option is enabled:
Wipe Device - Resets the device to the factory default state by erasing everything on
the device and prevents the device from synchronizing with the server.
Wipe Application - Erases all Lotus Notes Traveler client software and data on the
device and prevents the device from synchronizing with the server.
Deny Access - Prevents the device from synchronizing with the server.
Tip: If users are added to the access server field, then all other users on the server that
are not included in the users entered in the "Access server" field are by default not able
to access the server.
174 IBM Notes Traveler Hints and Tips for a Successful Deployment
5.1.2 Access control list configuration
Access control level for Lotus Notes Traveler
The Lotus Notes Traveler server must be added to the access control list (ACL) and granted
Manager and Delete documents access to any mail database that you wish to synchronize
with the Lotus Notes Traveler client on the mobile devices. This can be accomplished using
the following methods:
Manual ACL addition
Using LocalDomainServers group
Manual ACL addition
1. Open the mail database you wish to synchronize in a Lotus Notes client.
2. Select File Application -- Access Control...
3. Click Add...
4. Browse for or type in the exact name of the Lotus Notes Traveler server (for example,
Traveler/YourDomain).
5. Change User Type to Server.
6. Change Access to Manager.
7. Select Delete documents.
8. Click OK to close.
Chapter 5. User deployment 175
LocalDomainServers group
If the LocalDomainServers group is a part of the mail file ACL of the user mail database and
possesses the necessary Manager access and delete documents attributes, you can simply
add the Lotus Notes Traveler server to the LocalDomainServers group.
5.1.3 User authentication
Lotus Notes Traveler uses the HTTP protocol for the devices to communicate with the server.
Whatever you have chosen for the Domino authentication is what will be used by Lotus Notes
Traveler to authenticate the user. The default for this is Domino Directory authentication, but
you can use external mean such as an external LDAP for this as well.
If using Domino Directory authentication, it is mandatory for the users to have their internet
passwords set. This is the same user ID and password that would be used when logging into
iNotes (if this is configured on the client) or any other browser based application running on a
Lotus Domino server using the same Domino Directory.
The internet password can be defined by the administrator on user registration by checking
the "Set internet password" checkbox upon the user's registration:
176 IBM Notes Traveler Hints and Tips for a Successful Deployment
You can also set the internet password by opening up the user's person document in the
Domino administrator and setting this value:
When using Lotus Domino Session Authentication, users might have problems connecting to
Lotus Notes Traveler because many devices do not support HTML form based authentication.
Form based authentication is enabled on the Lotus Domino server if you have Session
Authentication enabled and have not allowed Anonymous authentication using TCP or SSL.
Chapter 5. User deployment 177
To see if form-based authentication is enabled for the Lotus Notes Traveler URLs, use a
browser to navigate to the following URLs on your server:
http://servername/servlet/traveler
http://servername/traveler
If SSL is enabled, use the following links:
https://servername/servlet/traveler
https://servername/traveler
If form based authentication is enabled, you will see an HTML form for authentication instead
of a pop up window.
There are two ways to disable HTML form based authentication and enable basic
authentication on the Lotus Notes Traveler server:
Enable Anonymous as part of the authentication options for the HTTP Server:
This is the easiest method. If you use Internet Site documents, you can disable HTML
form based authentication on the Security tab of the Internet Site document. If you use
Web Configurations, disable HTML form based authentication on the Ports Internet
Ports tab of the server document.
Use the Override Session Authentication rules:
To enable basic authentication for the Lotus Notes Traveler URLs by using the Override
Session Authentication rules, you must use the Internet Site documents. Open the Internet
Site document for the web protocol that applies to the Lotus Notes Traveler server and
create an Override Session Authentication rule for each of the Lotus Traveler URL paths.
5.2 Installation and configuration on an Apple device
In this section, we walk through the installation and configuration of the Apple profile for the
Lotus Notes Traveler Apple devices configuration. We also go through some of the steps on
how to use the client after this has been configured.
5.2.1 Preparation
Check iOS version
It is suggested to upgrade the devices to the latest iOS version. Check the iOS version from
Settings About Version. Upgrade the device software version can be done by
connecting it to iTunes on the user's computer.
For supported devices and operating systems, refer to 2.1, Supported hardware and
software on page 22.
Remove previously installed Lotus Notes Traveler profile
If the device has previously installed and configured Lotus Notes Traveler profile for use with a
different Lotus Notes Traveler environment, remove the existing profile by go to Settings
General Profile Tap Remove. The user may have to enter device passcode to remove
the profile if a device passcode was required based on Lotus Notes Server's security
requirements.
178 IBM Notes Traveler Hints and Tips for a Successful Deployment
Multiple accounts support
Configuring multiple accounts on the same device is possible only on Apple iOS 4.0+ devices.
If the user wishes to configure multiple accounts with the same server, upgrade the device to
iOS 4.0+.
5.2.2 Installing Lotus Notes Traveler profile on an Apple mobile device
Before the user begins, make sure your Apple device is connected to a WiFi or 3G network.
Use these steps to install Lotus Notes Traveler profile on the iOS device:
1. Go to the Lotus Notes Traveler user home page:
Open the Safari browser on your device, and go to the Lotus Notes Traveler user home
page URL provided to the user by your the system administrator. The Lotus Notes user
home page URL are:
For a stand-alone Lotus Notes Traveler environment, use http(s)://traveler_server/traveler,
for example, http(s)://9.12.5.133/traveler
For a highly available Lotus Notes Traveler environment, use
http(s)://IP_sprayer_address/traveler,for example, http(s)://9.12.5.144/traveler
Enter the user's HTTP User ID and Password.
Tap Log In.
Chapter 5. User deployment 179
2. Start configuration:
Select Configure your Apple iPhone/iPod Touch/iPad to begin download.
Tip: The user status section at the top of the home page shows the status as well as
the status of the device. If there are any user errors (for example, ACL not setup
correctly), there will be an error message shown at the top of the page and the install
section will NOT be shown (it is hidden until they fix the problem).
180 IBM Notes Traveler Hints and Tips for a Successful Deployment
3. Verify configuration:
Verify that the logon name and mail address is correct. The logon name is the user name
that was used to log in to the Lotus Notes Traveler user home page.
Select Generate to produce a customized profile for the device.
Chapter 5. User deployment 181
4. Install profile:
Select Install to begin the installation page.
182 IBM Notes Traveler Hints and Tips for a Successful Deployment
If the installer does not go to this screen, reboot your device and re-try again.
5. Accept authenticity of the profile:
When prompted about the authenticity of the profile, select Install Now to continue.
6. If you have a passcode already configured on the device, you will be prompted for it before
the installation will be allowed to continue.
7. Input Exchange password:
Because Lotus Notes Traveler uses the Exchange ActiveSync protocol, the installer
prompts for an "Exchange" password. Enter the password that was used to log in to the
Lotus Notes Traveler user home page and select Next.
Chapter 5. User deployment 183
8. (Optional) Input device security passcode:
If a security passcode has not been configured for the device and the passcode is required
as part of the security policy for the Lotus Notes Traveler server, set a security passcode
and click Next. If your passcode does not conform to the passcode requirements, you will
be asked to choose another passcode.
184 IBM Notes Traveler Hints and Tips for a Successful Deployment
9. (Optional) Re-enter device security passcode:
Re-enter the chosen passcode and click Next.
Tip: The phone data might be wiped off if the wrong passcode is entered too many
times depending on the security policy of the company.
Chapter 5. User deployment 185
10.Complete configuration:
Select Done to complete the installation. The new Exchange ActiveSync account is
created in the Mail, Contacts, and Calendars sections of the Settings application of the
Apple device.
186 IBM Notes Traveler Hints and Tips for a Successful Deployment
11.Initial synchronization
Allow some time to pass for the initial synchronization with the server to complete before
opening the Inbox of your mail. Opening the mailbox too soon can prolong the initial
synchronization.
5.2.3 Customize Sync data and schedule
User can customize sync data and schedule options to reduce data power usage.
To change the settings of your IBM Lotus Notes Traveler mail, calendars, and contacts, go to
Settings Mail, Contacts, Calendars and choose IBM Lotus Notes Traveler.
Chapter 5. User deployment 187
All options are ON by default, switch OFF if you do not want to synchronize particular
applications. You can also select how many days of mail to keep and change Fetch New Data
to Push to obtain email immediately when it is received on the mail server, otherwise, you can
synchronize on a schedule or manually.
You can change specific mail, calendars, or contacts settings, such as the number of mail
message lines to preview, the contacts sort order, or how much calendar data to keep. To do
so, select Settings Mail, Contacts, Calendars, and then scroll to Mail, Contacts, or
Calendars and change the settings that you want.
188 IBM Notes Traveler Hints and Tips for a Successful Deployment
5.2.4 Managing mail on Apple devices
Your mails are in the Mail application of your device. Opening it reveals a new Inbox labeled
with the mail address associated with your Lotus Notes account. You can use IBM Lotus
Notes Traveler to communicate with co-workers, friends, and family electronically by creating,
sending, replying to, and forwarding mail messages.
Tip: The mail setting Show x Recent Messages does not apply to Lotus Notes Traveler.
If you change how much calendar data to keep, you can select only how far back in the
past to synchronize calendar events. This limitation is due to the fact that all future
calendar events always synchronize to the device.
After modifications, you might have to go to the main Settings screen to allow the settings
take effect.
Chapter 5. User deployment 189
Compose a new message
You can create and send mail messages with your mobile device. When composing a new
mail message, you can select recipients' names from your contacts list.
1. Open the Mail application.
2. Select the Compose icon Compose icon.
3. Address the message by entering at least one email address in one of the address fields,
To, Cc (carbon copy), and Bcc (blind carbon copy). To select addresses from your contact
list for a field, select the Add contact icon in that field.
4. Enter a subject in the Subject field.
5. Enter the body of your message.
6. Do one of the following:
To send the message, click Send.
To save the message as a draft, click Cancel, and then click Save.
To discard the message, click Cancel, and then click Don't Save.
Tip: After you type three characters (or a different number set by your administrator) in
any of the recipient fields, the Lotus Notes Traveler server searches for the recipient
name and address in the corporate directory.
190 IBM Notes Traveler Hints and Tips for a Successful Deployment
Create a message with a photo or video attachment
You can send photos and videos with your mobile device.
1. Open the Photos or Videos application.
2. Select a photo or video.
3. Select Send icon
4. Select Email Photo or Email Video.
5. Address the message by entering at least one email address in one of the address fields,
To, Cc (carbon copy), and Bcc (blind carbon copy). To select addresses from your contact
list for a field, select Add contact icon in that field.
6. Enter a subject in the Subject field.
7. Add text to the message body.
8. Do one of the following:
To send the message, click Send.
To save the message as a draft, click Cancel, and then click Save.
Tip: After you type four characters (or a different number set by your administrator) in
any of the recipient fields, the Lotus Notes Traveler server searches for the recipient
name and address in the corporate directory.
Chapter 5. User deployment 191
To discard the message, click Cancel, and then click Don't Save.
Forward and reply messages
1. Open the message.
2. Select the Reply or forward Reply/forward icon.
3. Address the message by entering at least one email address in one of the address fields,
To, Cc (carbon copy), and Bcc (blind carbon copy). To select addresses from your contact
list for a field, select Add contact in that field.
Optional: Add comments to the message.
Do one of the following:
To send the message, click Send.
To save the message as a draft, click Cancel, and then click Save.
To discard the message, click Cancel, and then click Don't Save.
192 IBM Notes Traveler Hints and Tips for a Successful Deployment
Mail folder management
You can keep the mail messages on your mobile device and mail server synchronized when
you are connected to the Lotus Notes Traveler server.
Inbox mail is automatically pushed to the Inbox on your mobile device. Other folders on your
mobile device are synchronized when you open the folders. To synchronize a mail folder
manually, open the folder or select the Sync icon in the already displayed folder.
If your device is version 3.0 or later, you can select mail folders to push automatically using
Settings Mail, Contacts, Calendars account name Mail Folders to Push. The
selected folders are automatically pushed to your device.
Create new folder
Mobile devices running Apple iOS 5+ have the ability to create, rename, move, and delete
mail folders from their devices.
Chapter 5. User deployment 193
Move mails to folder
You can organize your mail messages by moving them to folders.
1. Do one of the following:
To move one message, open the message and select the Folder icon.
To move multiple messages, select Edit, select the messages to move, and select
Move.
2. Scroll to the folder to move the messages to, and then select the folder.
Tip: You cannot move a message to a folder when you are not connected to the Lotus
Notes Traveler server.
194 IBM Notes Traveler Hints and Tips for a Successful Deployment
Compose and receive encrypted messages
Lotus Notes Traveler Companion allows Traveler users to view and send encrypted mail
directly on their Apple device. Traveler Companion is available from the Apple App Store. The
simplest way to install it is to open the App Store on your device to search for Traveler
Companion. Then install Traveler Companion from its store entry. Lotus Notes Traveler
Companion is provided by IBM at no cost.
Configuring Traveler Companion
If you launch Traveler Companion by tapping the Traveler Companion link in an encrypted
mail and have not yet configured the settings, your server automatically configures based on
information in the link. You can then supply the password and the encrypted mail downloads
for viewing.
To manually configure the Traveler Companion settings, start the Traveler Companion
application. In the settings menu, there are options for server, user name, password, and
SSL. These options generally match the settings for your Lotus Notes Traveler account in the
mail settings on your device. Contact your Domino administrator if you are unsure of which
values to use.
Option Description
Server This field contains the address of your Lotus Notes Traveler
server, for example yourserver/traveler. Do not include http:// or
any other prefix.
Chapter 5. User deployment 195
For digital signing, encrypting, or decrypting to work, the Notes ID file must be uploaded to
the mail file or the ID vault. See "Upload my Notes ID file" below.
User name The user name you use to connect to your Lotus Notes Traveler
server.
Password The password for your user name.
Require SSL If this setting is configured to "ON", Traveler Companion does not
download encrypted mail over an unencrypted connection. Do
not change this setting unless you are instructed to do so by your
Lotus Notes Traveler administrator.
How do I... Action
Upload my Notes ID file? 1. From a computer where you use a Lotus Notes client, open
a web browser to
http://your_Lotus_Notes_Traveler_server/traveler.
Note: If your server is using SSL then open a web browser to
https://your_Lotus_Notes_Traveler_server/traveler.
2. Select Manage the Notes ID.
3. Select Upload the Notes ID.
4. In the Notes ID File field, type the path of your Notes ID file,
or browse for it.
5. In the Password field, enter your Notes ID password.
6. Select Upload Notes ID.
Read/Send encrypted mail? Once successfully configured, you can use Traveler Companion
to view and send encrypted mail in the mail application for your
device. When you receive an encrypted mail from the Lotus
Notes Traveler server, it contains a message with a Traveler
Companion link. Tapping on this link launches Traveler
Companion to download and display the actual message
content. Traveler Companion prompts you for the password for
the Notes ID file unless you have recently entered it, in which
case it is stored by the Apple password caching feature
(configurable from the administrator settings). This password
may be different from your Lotus Notes Traveler password. Once
the message has been successfully downloaded, Traveler
Companion displays the mail. Press Home to close the mail. You
can then go back to the mail application to resume your mail
session.
Note: If you do not see a link for Traveler Companion in your
encrypted mail, ask your Domino administrator to upgrade the
Notes Traveler server to version 8.5.1.1 or later.
You can use Traveler Companion to compose a new encrypted
mail, or to reply to or forward an encrypted mail message from
your device. To compose a new message, launch Traveler
Companion and tap the New message icon on the top left of the
screen. To reply to or forward an encrypted mail message, view
the encrypted message in Traveler Companion, then tap the
Respond icon at the bottom right of the screen. The original
message will be appended to your new message when you touch
the Send button.
Option Description
196 IBM Notes Traveler Hints and Tips for a Successful Deployment
For more detailed information, see
http://www-10.lotus.com/ldd/dominowiki.nsf/xpDocViewer.xsp?lookupName=Using+Lotus+
Notes+Traveler+8.5.3+Upgrade+Pack+1#action=openDocument&res_title=How_do_I_view_an
d_send_encrypted_mail_U853UP1&content=pdcontent
Managing the calendar on your Apple device
Meetings and appointments from your Lotus Notes Calendar are also automatically added to
your Apple device. Open your Calendar application to view them. From here, you can also
respond to new meeting invitations, just as you would from Lotus Notes.
Create new calendar event
1. Select Add event icon above the calendar.
2. Select the Title & Location panel, specify these details, and select Done.
3. Select the Starts & Ends panel and do one of the following:
To create an appointment, specify a start time and date, select Ends, specify an end
time and date, and select Done.
To create an all-day event, set the All-day field to ON, and select Done.
4. Specify date and time information as necessary in the Starts field and, if necessary, in the
Ends field.
Do any of the following:
To repeat the entry, select the Repeat panel, select a repeat interval, and select Save.
To set an alarm for the entry, select the Alert panel, select an alarm time relative to the
event, and select Save.
To add more details about the entry, select the Notes panel, enter the details, and
select Save.
5. Select Done to save the entry.
Tip: Only Domino-encrypted mail is supported on the Lotus Notes Traveler client.
Encrypted calendar, to-do, and notebook entries are not supported. SMIME encryption is
unavailable.
Tip: Use either a secure socket layer (SSL) connection or a virtual private network (VPN)
solution when encryption is enabled on the Lotus Notes Traveler server." This is a server
statement, applies to all devices, and belongs in some other section. It probably belongs in
the topology section(s).
Chapter 5. User deployment 197
Accept or reject invitations
You can respond to meeting invitations with basic options, such as Accept, Decline or Maybe,
using Lotus Notes Traveler. To perform advanced invitation features, such as invitation
delegation and proposing a new meeting time, you must use the Lotus Notes client on your
desktop.
To respond to a meeting invitation using Lotus Notes Traveler, perform the following
procedure:
1. In your Inbox, open the meeting invitation. Select the Invitation Icon within the Body of the
email. Optionally, select Add Comments to include remarks in the reply.
2. Select one of the following:
Accept: Creates an email response to the meeting chair notifying them that you are
accepting the meeting invitation. A calendar entry is added to your calendar. The next
time that the synchronization takes place, busy time is updated with your new calendar
entry.
Maybe: Creates an email response to the meeting chair notifying them that you are
tentatively accepting the meeting invitation. Busy time is not updated.
Decline: Creates an email response to the meeting chair notifying them that you are
declining the meeting invitation.
198 IBM Notes Traveler Hints and Tips for a Successful Deployment
Managing contacts on your Apple device
Lotus Notes Traveler can help you organize your business and personal contacts. Use contact
entries to store information such as names, addresses, phone numbers, and email
addresses.
Create new contacts
1. Select Contacts from the home page.
2. Select the add contact icon above the contact list.
3. Specify information in any of the fields and select Save.
4. Select Done to save the contact.
Chapter 5. User deployment 199
5.3 Installation on an Android device
In this section, we walk through the installation and configuration of Lotus Notes Traveler on
Android devices. We also go through basic steps on how to use the client once this has been
configured.
5.3.1 Preparation
Here are some preparatory items for Lotus Notes Traveler installation.
Check device OS version
Depending on your company security policy, previous versions (for example, Android OS
version 2.1 and prior) do not honor the required security settings may not be permitted access
to Lotus Notes Traveler.
For supported devices and operating systems, refer to 2.1, Supported hardware and
software on page 22.
200 IBM Notes Traveler Hints and Tips for a Successful Deployment
Remove previously installed Notes Traveler profile
Lotus Notes Traveler Android Client does not support multiple accounts. If you have Lotus
Notes Traveler installed previously, it is required to uninstall your existing Lotus Installer and
Lotus Notes Traveler.
For Version 8.5.3 and later of Lotus Notes Traveler: Uninstall Lotus Notes Traveler by
launching the "Lotus Traveler" application on the Android device, then select Menu
Tools -> Uninstall application. If the uninstall process is initiated in this manner, you are
not required to disable the device administrator manually.
For prior Version 8.5.3 of Lotus Notes Traveler: Uninstall Lotus Notes Traveler by
launching the Lotus mobile installer application, then selecting the Lotus Notes Traveler
application and choosing Uninstall.
Chapter 5. User deployment 201
If you choose to uninstall manually and your device is running Android 2.2 or higher, you
must first disable the device administrator.
To disable the device administrator, select Menu Settings Location & Security
Select device Administrators. After you have disabled the Lotus Notes Traveler device
administrator, you can use the operating system to remove Lotus Notes Traveler, by
navigating to Menu Settings -- Applications Manage Applications.
You can uninstall Lotus Mobile Installer using the normal method for uninstalling applications
on your Android device.
Installing Lotus Notes Traveler on an Android mobile device
The following screen shots were taken from the HTC One X user interface. Screen images
might be different depending on the model of Android device that you have.
Use these steps to install Lotus Notes Traveler:
1. Allow installation of non-market applications:
Go to Settings Security and check Unknown Sources. This action allows you to
install applications that are not from Android market.
202 IBM Notes Traveler Hints and Tips for a Successful Deployment
2. Go to the Lotus Notes Traveler user home page:
Before you begin, make sure that your Android device is connected to a WiFi or 3G
network
Open the browser on your device, and go to the Lotus Notes Traveler user home page
URL provided to you by your system administrator.
The Lotus Notes Traveler user home page URL are:
For a stand-alone Lotus Notes Traveler environment, use
http(s)://traveler_server/traveler, for example, http://9.12.5.133/traveler
For a highly available Lotus Notes Traveler environment, use
http(s)://IP_sprayer_address/traveler, for example, https://9.12.5.144/traveler
3. Enter ID and password:
When prompted for your user name and password, enter your HTTP User ID and
Password.
Chapter 5. User deployment 203
4. Download Lotus Notes Traveler application:
Select Configure your Android to begin download.
Tip: The user status section at the top of the home page shows the status as well as
the status of the device. If there are any user errors (for example, ACL not setup
correctly), there will be an error message shown at the top of the page and the install
section will NOT be shown (it is hidden until they fix the problem).
204 IBM Notes Traveler Hints and Tips for a Successful Deployment
5. Start installation:
Click the Home button to exit the web browser and drag down the status window from the
top of the screen.
Open LotusTravler.apk.
Tap Install to start the installation.
Tip: The warning message below must be accepted. This alerts the user that the
application will have access to perform the needed processes that is necessary for
Lotus Notes Traveler client.
Chapter 5. User deployment 205
The Lotus Traveler installation starts and a progress bar appears while installation. When
the application installation is complete, tap Open.
206 IBM Notes Traveler Hints and Tips for a Successful Deployment
6. Accept the license agreement:
Read the License Agreement carefully and click Accept to continue.
7. Start configuration:
Chapter 5. User deployment 207
Confirm server address and user ID, and input the password used for connecting to your
Lotus Notes Traveler server. Click Next to continue.
8. Activate security policy:
If your company has security policies in place, you might be asked to activate a security
policy before continuing.
Select Activate, the configuration wizard shows.
Tip: This is the same user ID and password used to access the Lotus Notes Traveler
homepage.
208 IBM Notes Traveler Hints and Tips for a Successful Deployment
9. Select the applications you want to synchronize, and whether you would like to store the
data using internal device storage or the SD card. Typically, if you plan on synchronizing
only a small set of data, you should choose internal phone storage. Select Finish when
you have made your choices.
Chapter 5. User deployment 209
10.Complete configuration:
The configuration of Lotus Notes Traveler on your Android device is now complete. You
can now start using Louts Notes Traveler from your Android device.
11.Security policy compliance:
(Optional) If a security passcode has not been configured for the device, and this is set as
the security policy for the Lotus Notes Traveler server, set a security passcode and click by
tap Update Password. Tap Password and Re-enter the passcode to confirm and then tap
OK.
Tip: While the removable storage card generally has much more space available, the
internal phone memory is much faster. If you do choose a removable card, we
recommend investing in fast flash memory such as a Class 10 card.
210 IBM Notes Traveler Hints and Tips for a Successful Deployment
12.Initial synchronization:
Allow some time to pass for the initial synchronization with the server to complete before
opening your mail Inbox. Opening the mailbox too soon can prolong the initial
synchronization.
Customize Sync data and schedule
Users can set and update device configurations and settings on the device by using the
following procedure:
1. Select the Lotus Traveler icon.
2. Select Menu.
3. Select Settings.
4. Select Applications.
5. You can select mail and calendar or other applications for syncing on Android devices.
6. Select from the following filters:
Tip: There is no new Contact app installed for Lotus Traveler, it uses the native Contact
application on the device.
Filters Description Options
Remove mail older than Mail messages are kept on your
mobile device based on interval
specified. After an email
message is older than the
specified interval, the message
is automatically removed from
the device. The email message
is not deleted from the Lotus
Notes mailbox on the server.
This setting applies to all folders
on the device.
1 day
3 days
5 days (default)
1 week
1 month
Show all
Chapter 5. User deployment 211
Managing mail on Android devices
You can use IBM Lotus Notes Traveler to communicate with co-workers, friends, and family
electronically. You can create, send, reply, and forward email. You can send attachments,
such as files and pictures, and organize messages in folders. You can save information about
people in your contact list.
Create a message on an Android device
Use the following steps to create a message:
Importance Sync only urgent or all email. All messages (default)
Urgent messages
Truncate mail to This filter controls the number
of characters that are included
in each email that is synced to
the device. Setting it to off
disables the truncation feature.
If an email is truncated, you can
retrieve the entire email
message including all
attachments by using the
Download Message feature.
Off
1 K
2 K
5 K (default)
10 K
50 K
100 K
Auto download inline images up
to
Inline images up to this
configured size are downloaded
automatically. As with the
truncation setting, the rest of
the inline images can be
downloaded using the
Download Message feature.
Off (default)
5K
25K
100K
500K
Auto download attachments up
to
By default, no attachments are
synchronized with mobile
device. To allow attachments,
you must set a size value. You
can retrieve the entire email
message including all
attachments by using the
Download Message feature.
Off (default)
25K
100K
500K
2MB
10MB
Show past events Events older than the interval
specified are removed from the
mobile device. These events
are not removed from you Lotus
Notes calendar on the server.
1 day
3 days
1 week (default)
2 weeks
1 month
3 months
6 months
Show all
Show upcoming events Upcoming events are synced to
your device based upon the
interval specified.
1 day
3 days
1 week
2 weeks
1 month
3 months (default)
6 months
1 year
Show all
Filters Description Options
212 IBM Notes Traveler Hints and Tips for a Successful Deployment
1. Choose the Mail icon from you application drawer.
2. Press the menu button and select Compose. If you are using a tablet, select the Compose
icon.
3. Address the message by entering at least one mail address in the address fields. To
enable the Cc: and Bcc: fields, select Menu Show Cc/Bcc.
On tablets, select the Overflow Menu button, the last icon in the Action Bar, to select
additional fields.
You can type a contact name in the Recipient field, and Lotus Notes Traveler will attempt
to fill in the name automatically based on what you type. Auto completion for local contacts
starts after two chars are typed. Auto completion for remote contacts starts after three
chars are typed (or a different number set by your administrator). The number of
characters for auto completion to begin can be configurable by the administrator on the
server. Remote contacts are designated by an orange bar on the left side of the contact,
while groups and mail-in DBs are designated by special thumbnail images.
Chapter 5. User deployment 213
You can also access your corporate directory by selecting Menu Look Up Recipient.
When using the lookup application, only the server is searched. Local contacts do not
appear. In the application, lookup starts after four characters are typed. This can also be
configured on server.
Tip: If you want to start a lookup with fewer characters, press the Android search button
at any time.
Tip: A message displays in the auto complete list if there are more results available
than can display on the device. To display the best results, you must refine your search
string.
214 IBM Notes Traveler Hints and Tips for a Successful Deployment
4. In the Subject field, enter a subject.
5. Enter the body of your message.
6. Optional: Do either of the following:
To attach one or more files on Android phones, select Menu Attach. On tablets,
select the Attachment link, between the subject and the message body.
To mark the mail as Urgent, select Menu Message Options High Importance.
To sign the mail, select Menu Message Options Sign.
7. Perform one of the following:
Select the on-screen Send button.
Select Menu Send to send the message to the specified recipients.
Select Menu Save as Draft to save a copy of this draft mail on both the client and
server.
Select Menu Discard to discard the draft email from both the client and server.
Delete a message on an Android device
You can delete a message from your Android device in one of four ways:
From the inbox or other folder view, select and hold the message, then press Delete.
Select the checkbox for the message or messages you wish to delete, then select
Menu Delete on Android phones. On tablets, select the Delete icon.
On Android phones, open the message and select the Trash icon located near the bottom.
This option is not available on tablets.
Open the message and select Menu Delete on Android phones. On tablets, select the
Delete icon Delete.
Reply or forward a message on an Android device
You can reply or forward a message to another recipient.
1. Open the message.
2. Select Menu.
3. Reply or forward a message:
Reply:
For Android phones, select one of the following options: Reply / Reply to All.
For Android tablets, select the Reply icon Reply. A sub-menu displays with options for
Reply and Reply to All.
Forward:
For Android phones, select Forward.
For Android tablets, select the forward icon
Tip: On tablets, the Message Options menu is available by selecting the Overflow Menu
button, the last icon in the Action Bar.
Tip: On Android tablets, the Send, Save as Draft, and Discard options reside in the
action bar.
Chapter 5. User deployment 215
4. To view the Cc:, Bcc:, press Menu Add Cc/Bcc.
5. Optional: Type additional comments.
6. Optional: Do either of the following:
To attach one or more files on Android phones, select Menu Attach.
On tablets, select the Attachment link, between the subject and the message body.
To specify delivery options on Android phones, such as priority, select Menu
Message Options.
On tablets, the Message Options menu is available by selecting the Overflow Menu
button, the last icon in the Action Bar.
7. On an Android phone, select Send to send the message. On tablets, the Send, Save as
Draft, and Discard options reside in the action bar.
Folder management on an Android device
Tip: Only attachments already downloaded to the device are included in the new
mail.
216 IBM Notes Traveler Hints and Tips for a Successful Deployment
Sync folders on an Android device
Keep your mobile device and server mail file folders synchronized (or subscribed).
When viewing your Inbox on an Android phone, choose Menu Show Folders Personal
Folders. On tablets, the personal folders are already visible in the main view. To perform
operations, press a folder and hold. A menu with additional options displays, including the
option to subscribe or unsubscribe a folder. From this menu you can also:
Delete the folder
Rename the folder
Create a new folder
Search for mail within the folder
Move a message to a folder on an Android device
Organize the data on your device by moving messages to folders to make finding them easier
and save disk space.
You can move a message to a folder on your Android device in one of several ways:
In the mail list view, select the checkbox of the e-mails you wish to move. On Android
phones, select Menu Move to Folder. On tablets, select the Move to Folder icon.
In the mail list view, select and hold a single e-mail. Then select Move to Folder.
Open the e-mail, then select Menu Move to Folder on an Android phone. On tablets,
select the Move to Folder icon Move to Folder.
Chapter 5. User deployment 217
Send/Read encrypted mail on an Android device
Reading and sending IBM Lotus Domino encrypted and signed mail messages can be
performed from an Android device. IBM Lotus Notes Traveler implements an encryption and
decryption strategy that requires server-side access to the user Notes ID file. The ID file
contains the private and public keys necessary to digitally sign, encrypt, and decrypt mail
messages.
218 IBM Notes Traveler Hints and Tips for a Successful Deployment
For digital signing, encrypting, or decrypting to work, the Notes ID file must be uploaded to
the mail file or the ID vault. See "Upload my Notes ID file" below.
Managing calendar on Android devices
Use the calendar to schedule and manage meetings, appointments, all day events,
anniversaries, reminders, and event announcements.
To view your calendar, select the Calendar icon from the application drawer.
How do I... Action
Upload my Notes ID file? 1. From a computer where you use a Lotus Notes client, open a
web browser to
http://your_Lotus_Notes_Traveler_server/traveler.
Note: If your server is using SSL then open a web browser to
https://your_Lotus_Notes_Traveler_server/traveler.
2. Select Manage the Notes ID.
3. Select Upload the Notes ID.
4. In the Notes ID File field, type the path of your Notes ID file, or
browse for it.
5. In the Password field, enter your Notes ID password.
6. Select Upload Notes ID.
Read encrypted mail? 1. Select the encrypted mail message to read.
2. Select Menu Download Message or select Get the rest of
the message from within the mail message.
3. If prompted, enter your Notes ID password.
Tip: Only Domino-encrypted mail is supported on the Lotus Notes Traveler client.
Encrypted calendar, to-do, and notebook entries are not supported. SMIME encryption is
unavailable.
Tip: Use either a secure socket layer (SSL) connection or a virtual private network (VPN)
solution when encryption is enabled on the Lotus Notes Traveler server.
Chapter 5. User deployment 219
Create and manage calendar entries on an Android device
You can create and manage calendar entries on your Android device in various ways.
How do I... Action
Change the calendar display? 1. On an Android phone, select Menu.
2. Select one of the following:
Day: List daily calendar entry descriptions with the time slot
display.
Week: Visual display of booked time slots for the week.
Month: Visual display of booked time slots for the month.
Agenda: List daily calendar entry descriptions without the time
slot display.
Note: On tablets, the calendar views are accessible as tabs on the
left of the calendar screen. You can choose Agenda, Day, Week,
or Month.
Items in your calendar can be color coded to represent specific
types of events. The following color coding scheme is used by your
device's calendar:
Meeting
Appointment
All day event
Anniversary
Reminder
Create a calendar entry? 1. On an Android phone, select Menu from a calendar event.
Then select New Event.
On a tablet, select the New Even icon New Event from the
calendar screen.
2. Type a subject in the Subject field.
3. Select Event type: choices are "Meeting", "Appointment", "All
Day Event", "Anniversary", and "Reminder".
4. To change start or end time, select the link. This displays a
date and time selection dialog.
5. Do any of the following:
Select the Repeats field to display the Repeats dialog. Then
specify the repeat options.
Select the Alarm field to display the Alarm dialog. Then set the
time interval for the alarm to sound before an event.
Use the Description field to add any additional information
about the entry.
Enter a category name in the Category field.
You can make the event private by selecting Private.
You can designate the time slot as available by selecting
Availability.
6. If the calendar event you are creating is a meeting, you can
add names to the invitation using the Required, Optional, or
FYI fields.
7. Select Save or Menu Save to save and close.
Reschedule or update a
meeting?
1. Select the calendar entry.
2. On Android phones, select Menu Edit to open the entry for
editing. On tablets select the editing icon.
220 IBM Notes Traveler Hints and Tips for a Successful Deployment
Respond to a meeting invitation on an Android device
If a meeting invitation contains Accept and Decline options, then the meeting chair expects
you to respond to the invitation. To perform advanced invitation features such as invitation
delegation and proposing a new meeting time, use either the desktop Lotus Notes client or
iNotes.
Set an alarm? 1. In a calendar entry, select Alarm to display the Alarm editor.
2. Specify in either minutes, hours, or days the amount of time
before or after the start of the calendar entry to trigger the
alarm.
3. Press OK to apply the changes or Cancel to back out.
Pressing the Back button also cancels the alarm.
Edit a calendar entry? 1. On Android phones, open the calendar entry and select Edit.
On tablets, select the Edit icon Calendar Edit from the calendar
screen.
2. Make the edits to calendar entry.
3. Select Save to save and close.
4. For repeat calendar entries, a window displays. Select Just
this instance to save only this occurrence or select All
instances to save all occurrences. Then select either Save or
Cancel.
Delete a calendar entry? 1. Select the calendar entry.
2. On Android phones, select Menu Delete to permanently
delete the calendar entry. On tablets, select the Delete icon.
Note: If the entry is a recurring event, the confirmation dialog
contains choices to delete this instance or all instances.
Add tap-to-dial coding for a new
calendar entry?
You can add special characters to customize the tap-to-dial
functionality of telephone numbers within a calendar entry.
You can use the characters "p" and "," (comma) as "pause"
characters. In addition, the characters ";" (semicolon) and "x"
cause a user to be prompted before the characters which follow it
are sent.
Some examples of conference call number formats are shown
below. The first examples pause between dialing the phone
number and sending the access code:
(800)555-1234p123456#
1-800-555-1234p123456#
(800)555-1234,123456#
1-800-555-1234,123456#
The next examples cause an Android device to prompt the user
before sending the access code:
(800)555-1234;123456#
1-800-555-1234;123456#
(800)555-1234x123456#
1-800-555-1234x123456#
How do I... Action
Chapter 5. User deployment 221
The following table describes meeting invitation icons.
Tip: On tablets, the Accept and Decline menu options are also available directly from the
action bar.
Icon Description
Signifies a new invitation to which your response is requested.
Indicates an information update to an existing meeting that has not yet
been applied to your calendar.
An existing meeting has been rescheduled to a new time and day and your
response is requested.
An existing meeting has been canceled and your response is requested.
Indicates an invitation that you have accepted and to which the client is
currently propagating the response to the chair.
Indicates an invitation that you have declined and to which the client is
currently propagating the response to the chair.
Indicates an information update to an existing meeting, that has already
been applied to your calendar.
Indicates an attendee accepted your invitation to a meeting.
Indicates an attendee declined your invitation to a meeting.
Indicates an attendee tentatively accepted your invitation to a meeting.
222 IBM Notes Traveler Hints and Tips for a Successful Deployment
Use the following steps to respond to a meeting invitation:
1. In your Inbox, open the meeting invitation.
2. Select Menu.
3. Select one of the following:
Managing contacts on Android devices
IBM Lotus Notes Traveler helps you organize your business and personal contacts. Use
contact entries to store information such as name, address, phone number, and email.
To open your contact list from your home page, select Contacts.
Store information about your business and personal contacts such as name, address, phone
number, and email.
Indicates that a cancelation notice has been applied to your calendar.
Option Description
Accept Creates an email response addressed to the meeting chair notifying that
you have accepted. A calendar entry is added to your calendar. The next
time syncing takes place, busy time is updated with your new calendar
entry.
Decline Creates an email response addressed to the meeting chair notifying that
you have declined.
Tentative Creates an email response addressed to the meeting chair. Busy time is not
updated.
Tip: In some devices, the native Contacts application might be named People instead of
Contacts.
How do I... Action
Create a contact? 1. Select Contacts from the home page.
2. Select Menu New contact.
3. Complete the action using "Lotus Traveler".
4. Specify information in any or all of the fields.
5. Select Menu Done to save the contact.
Edit a contact? 1. Open the specific contact you want to edit.
2. Select Menu Edit contact.
3. Complete the action using "Lotus Traveler".
4. Update the contact information.
5. Select Menu Done.
Delete a contact? 1. Select Contacts from the home page.
2. Open the contact you want to delete.
3. Select Menu Delete contact.
4. Select OK to permanently delete the contact
Icon Description
Chapter 5. User deployment 223
5.4 Installation on a Windows mobile device
In this section we walk through the installation of the Lotus Notes Traveler on Windows Mobile
devices. We also go through basic steps on how to use the client after the client application is
configured.
5.4.1 Preparation
Ensure your device is connected to a stable WiFi network or to a 3G or 4G network. Using
any slower network will increase the time it takes to perform the initial synchronization.
Software version
For supported devices and operating systems, refer to 2.1, Supported hardware and
software on page 22.
To check your software level on a Windows Mobile device, follow these steps:
1. Access the start menu of your phone, either by tapping the corresponding button from your
launch page or by using your touch screen (if equipped).
2. Find and access Settings. On most Windows Mobile equipped phones, this is illustrated
by a folder with a gear icon.
3. Scroll down until you find "About." You might have to scan through several pages. When
you reach the end of a page, click More to move on to the next page.
4. Click About. This window provides you with the necessary information. The version of
Windows Mobile is usually listed at the top. It should read "Windows Mobile 6" or
"Windows Mobile 6.5," depending on what version you have.
Multiple accounts support
Configuring multiple accounts on the same device is not possible on Windows devices.
5.4.2 Installing the Lotus Notes Traveler application on a Windows mobile
device
1. Go to the Lotus Notes Traveler user home page from the device:
Open the browser on your device, and go to the Lotus Notes Traveler user home page
URL provided to you by your system administrator.
The Lotus Notes Traveler user home page URL are:
Search for a contact using
corporate look up?
1. Select Lookup from the applications list.
2. Enter the first few characters of the first or last name of the contact.
The Results window populates a list of names with similar
characters.
Note: You can also search for Lotus Notes group names as well as
mail-in databases.
3. Select the appropriate name from the list.
4. From here you can call, email or add the contact to your local
contacts list.
How do I... Action
224 IBM Notes Traveler Hints and Tips for a Successful Deployment
For a stand-alone Notes Traveler environment, use https://traveler_server/traveler or
http://traveler_server/traveler, for example, http://9.12.5.133/traveler
For a highly available Notes Traveler environment, use
https://IP_sprayer_address/traveler or http://IP_sprayer_address/traveler, for example,
https://9.12.5.144/traveler
2. Enter HTTP User ID and Password:
When prompted for your user name and password, enter your HTTP User ID and
Password.
3. Download Lotus Notes Traveler application:
Select "Configure your Windows Mobile" to begin download.
Tip: The user status section at the top of the home page shows the status as well as
the status of the device. If there are any user errors (for example, ACL not setup
correctly), there will be an error message shown at the top of the page and the install
section will NOT be shown (it is hidden until they fix the problem).
Chapter 5. User deployment 225
4. Start installation:
You can either launch the file right now or later.
226 IBM Notes Traveler Hints and Tips for a Successful Deployment
The Lotus Traveler installation starts and a progress bar appears while installation.
Chapter 5. User deployment 227
228 IBM Notes Traveler Hints and Tips for a Successful Deployment
5. Accept the license agreement:
Read the License Agreement carefully and click Accept to continue.
Chapter 5. User deployment 229
6. Download the client:
Click on Next to download the Lotus Traveler client.
230 IBM Notes Traveler Hints and Tips for a Successful Deployment
7. Confirm server address, user ID, and input password used for connecting to your Lotus
Notes Traveler server. Click Next to continue.
Chapter 5. User deployment 231
232 IBM Notes Traveler Hints and Tips for a Successful Deployment
Chapter 5. User deployment 233
234 IBM Notes Traveler Hints and Tips for a Successful Deployment
Chapter 5. User deployment 235
8. Wait for download to finish.
236 IBM Notes Traveler Hints and Tips for a Successful Deployment
9. Select the features on your device that you want to synchronize with the server.
Chapter 5. User deployment 237
10.Complete configuration.
238 IBM Notes Traveler Hints and Tips for a Successful Deployment
Chapter 5. User deployment 239
5.4.3 Customize data sychronization and schedule
Users can set and update device configurations and settings on the device.
1. Select the Lotus Traveler icon.
2. Select Menu.
3. Select Settings.
4. You have the option for configuring your Account, Mail, Calendar and Tasks, Other
Applications, Auto Sync, and Server Settings.
240 IBM Notes Traveler Hints and Tips for a Successful Deployment
5.4.4 Managing mail on Windows devices
You can use IBM Lotus Notes Traveler to communicate with co-workers, friends, and family
electronically. You can create, send, reply, and forward email. You can send attachments,
such as files and pictures, and organize messages in folders. You can save information about
people in your contact list.
Create a message on a Windows device
Use the following steps to create a message:
1. Go to Messaging.
Chapter 5. User deployment 241
2. Select Lotus Traveler Mail.
242 IBM Notes Traveler Hints and Tips for a Successful Deployment
3. You are taken to your Inbox.
Chapter 5. User deployment 243
4. To create a new message, you can use Menu options or you can open any existing
message and select Reply to reply the mail.
244 IBM Notes Traveler Hints and Tips for a Successful Deployment
Chapter 5. User deployment 245
5. You can add or look up recipient as required.
246 IBM Notes Traveler Hints and Tips for a Successful Deployment
Chapter 5. User deployment 247
6. You can also select the Delivery options by using Menu Message Options.
248 IBM Notes Traveler Hints and Tips for a Successful Deployment
Options on a Windows device
1. You can sort your view on different criteria.
Chapter 5. User deployment 249
2. You can also manage folders and choose which ones to subscribe.
250 IBM Notes Traveler Hints and Tips for a Successful Deployment
5.5 Installation on a Sybian or Nokia device
In this section we walk through the installation of Lotus Notes Traveler on Symbian Series 60
3rd Edition, Series 60 5th Edition, and Symbian ^3 devices. We also go through basic steps
on how to use the client once this has been configured.
5.5.1 Preparation
Ensure your device is connected to a stable WiFi network or to a 3G or 4G network. Using
any slower network will increase the amount of time it takes to perform the initial
synchronization.
Software Version
For supported devices and operating systems, refer to 2.1 supported hardware and software.
Remove previously installed Traveler profile
If you have previously installed and configured the Lotus Notes Traveler for use with a
different Traveler environment, uninstall your existing profile.
Chapter 5. User deployment 251
Multiple accounts support
Configuring multiple accounts on the same device is not possible.
5.5.2 Beginning installation
1. Go to the Lotus Notes Traveler user home page:
Open the browser on your device, and go to the Lotus Notes Traveler user home page
URL provided to you by your system administrator.
The Lotus Notes Traveler user home page URL are:
For a stand-alone Lotus Traveler environment, use https://traveler_server/traveler or
http://traveler_server/traveler, for example, http://9.12.5.133/traveler
For a highly available Lotus Traveler environment, use
https://IP_sprayer_address/traveler or http://IP_sprayer_address/traveler, for example,
https://9.12.5.144/traveler
2. Enter Internet user ID and password:
When prompted for your user name and password, enter your Domino internet ID and
password.
3. Download Lotus Notes Traveler application:
If you log in with correct user ID and password, you should be directed to the Lotus
Traveler user home page. The user status section at the top of the home page shows your
status as well as the status of your device. Select Configure your Nokia Symbian to
begin download.
4. The installer downloads the Lotus Notes Traveler application to your device.
252 IBM Notes Traveler Hints and Tips for a Successful Deployment
5. Start Installation: The installer is also available in the downloaded files section of the
device.
6. Accept the License Agreement;
Read the License Agreement carefully and click OK to continue.
Chapter 5. User deployment 253
Click Start to download and install Lotus Notes Traveler client application.
7. Start Configuration:
Enter the server details
254 IBM Notes Traveler Hints and Tips for a Successful Deployment
8. Choose OK to install Lotus Notes Traveler.
9. You must allow Lotus Notes Traveler administrator access to manage the device for
security reasons (if the device is lost or stolen, the users Notes data can be secured).
Chapter 5. User deployment 255
10.Select the features on device you want to synchronize with your server.
11.Complete configuration.
5.5.3 Customize Sync data and schedule
Users can set and update device configurations and settings on the device by using the
following steps:
1. Select the Lotus Traveler icon.
2. Select Options.
256 IBM Notes Traveler Hints and Tips for a Successful Deployment
3. Select Settings.
You have the option for configuring your Account, Mail, Calendar and Tasks, Other
Applications, Auto Sync, and Server Settings.
Managing mail on Symbian devices
You can use IBM Lotus Notes Traveler to communicate with co-workers, friends, and family
electronically. You can create, send, reply, and forward email. You can send attachments,
such as files and pictures, and organize messages in folders. You can save information about
people in your contact list.
Add Lotus Traveler Mail widget and shortcut on your Symbian device
You can use the adding widget methods of your device to add Notes Traveler Mail widget on
your Symbian devices. For example, on E75 device, you can go to Menu Control Panel
Modes Email Notifications select Lotus Traveler Mail on the Mailbox field.
On Symbian ^3 device, you can add a shortcut by doing a long press on the homescreen,
selecting Add, and then selecting Lotus Traveler Mail from the list.
Create a message on a Symbian device
Use the following steps to create a message:
1. Select Options Create Message.
2. Type the content in relevant fields for Subject, Recipient, and Body.
3. You can use the Options button to: Add recipient, Look up recipient, Insert
attachment, Address fields.
4. You can also perform Forward, Reply, Reply to All, Delete from your device by using
Options button for any mail you have in your Inbox.
5.6 Unconventional deployment options
In some cases, users may not be able to download and configure Lotus Notes Traveler from
the Traveler servlet page. This may caused by the 3rd party applications, certificate validation
or other issues. Follow the steps provided here for the appropriate device to attempt to setup
Lotus Notes Traveler on the device.
5.6.1 Apple device
On the apple devices, the profile might fail to launch the "Install Profile" action and the
browser might display an icon similar to the following:
This indicates that an application on the Apple device has become associated with the
standard Apple configuration profile format when downloaded through the browser and has
stopped the "Install Profile" action from occurring. Known 3rd Party Applications that can
cause this include (but are not limited to): QuickOffice, WebProjector, Air Sharing,
Downloader, File App, DocumentsToGo, ActivePrint and other PDF applications. If this is the
case, there are certain steps that you can take to configure the client and profile manually on
the device.
Use these steps to manually create the profile on an Apple device:
1. Press the device home button to return to the home screen.
Chapter 5. User deployment 257
2. Select Settings Mail, Contacts, Calendars Add Account Microsoft Exchange.
3. Complete the following fields, and select Next.
Email Specify your mail address (for example, yourname@yourcompany.com).
Domain Leave this field blank.
Username Specify your HTTP user ID.
Password Specify your HTTP password.
Description Specify a description, or leave the default (the Email field value).
4. Specify your Lotus Notes Server address in the Server field in the format
yourserver.com/traveler, and select Next.
5. Select the applications that you want to synchronize, and select Done.
5.6.2 Android device
There is a problem with SSL certificates within the Android operating system browser which
can prevent the browser from downloading files. On the Android devices, users might not be
able to download and install the IBM Lotus Mobile Installer (LotusTraveler.apk package), the
device "hangs" on the download and does not complete when using SSL. This is caused by
an Android defect. For details on this Android defect, see:
http://code.google.com/p/android/issues/detail?id=5851
There are several possible workarounds for this issue (including but not limited to):
Configure Gmail or other email account on the device and then email the
LotusTraveler.apk as an attachment. Install the LotusTraveler.apk on the device. To save
this file to be emailed, log into the Traveler servlet (http:///traveler) on the desktop browser,
select Select an IBM Lotus Mobile Installer and then Android. Save the file
LotusTraveler.apk and email it to the user's Gmail or other account.
Download and install another browser (for example Opera or Firefox) on the device and
retry the installation with one of these browsers instead of using the Google browser.
Find some other mechanism to place the LotusTraveler.apk on the device. For Example:
Download the LotusTraveler.apk package to your desktop, and sync this to the device's SD
card. Install the LotusTravler.apk from the SD card.
Contact your device manufacturer or carrier if additional details are needed on this Android
browser defect.
Tip: SSL is enabled by default (and recommended). If SSL is not used, you must
disable SSL for the account. To do so, select Settings Mail, Contacts,
Calendars account name Account Info, and then change Use SSL to OFF.
Tip: If you use a proxy, use the format yourproxyserver.com:port/traveler. For
example, for a IBM Mobile Connect connection, specify
yourIMCserver.com:port/traveler.
Tip: A file manager program may need to be installed on the device and can be found in
the Android Market.
258 IBM Notes Traveler Hints and Tips for a Successful Deployment
Copyright IBM Corp. 2013. All rights reserved. 259
Chapter 6. Migration
In this section, we look at what you need to consider if you already have an existing IBM Lotus
Notes Traveler environment that you want to upgrade to the new 8.5.3 Upgrade Pack 1
version or moving from a stand-alone Lotus Notes Traveler environment to a high availability
configuration. We cover the following topics:
6.1, Moving to a 64-bit architecture on page 260
6.2, Upgrading to 8.5.3 Upgrade Pack 1 from a previous version of Lotus Notes Traveler
on page 263
6.3, Moving from Lotus Notes Traveler 8.5.3 Upgrade Pack 1 stand-alone to a high
availability environment on page 285
6.4, Moving from a single pool to a multi-pool high availability environment on page 288
6
260 IBM Notes Traveler Hints and Tips for a Successful Deployment
6.1 Moving to a 64-bit architecture
IBM Lotus Notes Traveler 8.5.3 Upgrade Pack 1 supports 32-bit operating system (OS) when
running in stand alone mode, however, if you have more than a hundred users or so a 64-bit
OS is recommended.
When running Lotus Notes Traveler in a High Availability mode, only a 64-bit OS is supported.
For more information about the system requirements, see
Lotus Notes Traveler 8.5.3 Upgrade Pack 1 System Requirements -
http://www-01.ibm.com/support/docview.wss?uid=swg27027499&myns=swglotus&mynp=OCSSY
RPW&mync=R
This section describes how to migrate a Lotus Notes Traveler server from a 32-bit system to a
64-bit system and the considerations about this system change.
6.1.1 How to move
The general procedure of moving Lotus Notes Traveler from a 32-bit system to a 64-bit
system is as follows:
1. Preparing the 64 bit OS.
2. Installing the Lotus Domino Server and Lotus Notes Traveler on the 64-bit system.
3. Copy data from the 32-bit system to the 64-bit system.
4. Starting Lotus Domino and Lotus Notes Traveler on the 64-bit system.
You should not change versions of Lotus Domino and Lotus Notes Traveler when you migrate
the server. If you want to upgrade Lotus Domino and Lotus Notes Traveler, upgrade after you
complete the server migration.
When considering how the Lotus Notes Traveler is migrated, there are two methods from
which to choose.
Full data copy method
In Full data copy, you copy all of the contents of Domino data directory from the 32-bit server
to the 64-bit server when migrating the Lotus Notes Traveler server.
The benefit of this method is that the steps involved in the installation and configuration of
Lotus Domino and Lotus Notes Traveler are less than the minimal data copy method. Also,
since the directory structure is copied from the 32-bit system and the entire data directory is
copied, the chance to introduce an error is less. The limitation of this method is that the
operating system file systems and directory structure of the target 64-bit system must be
identical to the source 32-bit system. In addition, you will need more time to copy the data, so
the system downtime is longer than the minimal data copy method.
The migration steps are as follows:
1. Install the new operating system, Lotus Domino server, and Lotus Notes Traveler server
on the 64-bit system. Do not start Lotus Domino yet.
Tip: In the Full data copy method you can NOT change operating systems. For example
you can not go from a Windows 32 bit system to a Linux 64 bit system using this method.
You can do this using the Minimal data copy method.
Chapter 6. Migration 261
For information on how to install Lotus Domino and Lotus Notes Traveler, see 3.0
Deploying a stand-alone Lotus Notes Traveler environment.
For example, if Lotus Domino is installed in the path C:\Lotus\Domino on the 32-bit
system, install Lotus Domino in C:\Lotus\Domino on the 64-bit system also.
2. Shut down Lotus Notes Traveler and the Lotus Domino on the 32-bit system.
3. Copy the notes.ini file and all contents of the Lotus Domino data directory from the 32-bit
system to the 64-bit system. If your system is not Windows, ensure that the permission
setting on the copied contents is the same as those on the 32-bit system.
4. Power off the 32-bit system. Do not scrap the 32-bit system before you confirm the
success of moving to the 64-bit system.
5. Change the host name and IP address of the 64-bit system to match those of the 32-bit
system.
6. Run the following three offline maintenance commands on the 64-bit system. These
commands correct database corruptions if there is any.
Fixup
/nfixup names.nsf -F
/nfixup admin4.nsf -F
Compact
/ncompact names.nsf -c
/ncompact admin4.nsf -c
Updall
/nupdall names.nsf -R
/nupdall admin4.nsf -R
/nupdall LotusTraveler.nsf -R
(If your Lotus Notes Traveler's version is earlier than 8.5.3 Upgrade Pack1)/nupdall
ntsclcache.nsf -R
For more information about the options, refer Administrator Guide for Domino Server
maintenance (http://www-01.ibm.com/support/docview.wss?uid=swg27006573).
7. Start Lotus Domino and Lotus Notes Traveler on the 64-bit system. Users can access the
new 64-bit server using the same URL which they used to access the 32-bit server
because the host name and IP address are same.
Tip: When you install Lotus Domino and Lotus Notes Traveler, you must create and use
the same directory structure as you have on the 32-bit system.
Tip: If you are using transaction logging, use the option "-J" instead of "-F".
Tip: If you are using transaction logging, use the option "-c -i" instead of "-c".
Tip: If you are using transaction logging, use the option "-R -X" instead of "-R".
262 IBM Notes Traveler Hints and Tips for a Successful Deployment
Minimal data copy method
When using the minimal data copy method, you copy only the minimum required files from the
32-bit server to the 64-bit server when migrating the Lotus Notes Traveler server.
The benefit of this method is that the file system and the directory structure of the operating
system on the target 64-bit system is not required to be same as the source 32-bit system. In
addition, the system downtime is shorter than the full data copy method because the data
copy time is shorter. The limitation of this method is that more steps are required to complete
the migration.
The migration steps are as follows:
1. Install the new operating system, Lotus Domino Server, and Lotus Notes Traveler Server
on the 64-bit system.
For information on how to install Lotus Domino and Lotus Notes Traveler, see Chapter 3,
Deploying a stand-alone Lotus Notes Traveler environment on page 65.
2. Start Lotus Domino on the 64-bit system and perform any necessary configuration steps
to have it running identically as the 32-bit system, except for the host name.
3. Shut down Lotus Notes Traveler and Lotus Domino on the 32-bit system and 64-bit
system.
4. Copy the following files and contents of the directory from the 32-bit system to the 64-bit
system:
<Lotus Domino data>/traveler/ntsdb
<Lotus Domino data>/LotusTraveler.nsf
<Lotus Domino data>/ntsclcache.nsf: Copy this file only if your Lotus Notes Traveler
version is earlier than 8.5.3 Upgrade Pack1.
5. Power off the 32-bit system. Do not scrap the 32-bit system before you confirm the
success of moving to the 64-bit system.
6. Change the host name and IP address of the 64-bit system to match those of the 32-bit
system.
7. Remove the TRAVELER and HTTP parameters from the ServerTasks list in the notes.ini
and start Lotus Domino on the 64-bit system.
8. Change the host name in the Domino server document.
Go to the Basic tab, change the host name in Fully qualified internet host name field
to match the values from the 32 bit system.
Go to the Internet Protocols tab HTTP tab and change the host name in Host
name field to match the values from the 32 bit system.
If the users use an external server URL to access the 32-bit Lotus Notes Traveler
server through a proxy server or load balancer, set the external server URL on the
64-bit system. Go to the Lotus Traveler tab, set the URL in the External server URL
field to match the values from the 32 bit system.
9. If you have the internet site documents in your environment, change the host name in
these documents.
10.Shut down Lotus Domino on the 64-bit system.
Tip: Lotus Notes Traveler 8.5.3 Upgrade Pack 1 does not have the HTTP parameters in
the notes.ini.
Chapter 6. Migration 263
11.Add the TRAVELER parameters to the ServerTasks in the notes.ini.
12.Run the Updall offline maintenance on the 64-bit system:
/nupdall LotusTraveler.nsf -R
If your Lotus Notes Traveler version is under 8.5.3 Upgrade Pack1, use /nupdall
ntsclcache.nsf -R
13.Start Lotus Domino on the 64-bit system.
6.1.2 Tuning
After migrating the Lotus Notes Traveler to a 64-bit architecture, check the following two
settings and adjust the values as required to improve the performance of Lotus Notes
Traveler.
Maximum cached users
You can set the value of Maximum cached users on the Domino server document:
Go to the Internet Protocols tab Domino Web Engine tab and change the value in
the Maximum cached users field. See section 3.4.2, Lotus Notes Traveler configuration
on page 91 for more information on this setting.
Maximum memory size
You can allocate more memory to a Lotus Notes Traveler Java heap on a 64-bit system.
See 9.1, Performance tuning on page 376 for more information on this setting.
By default, the value of the maximum memory size is 1024 MB. Use the tell traveler
mem or tell traveler status command to determine if Java heap is sufficient on your
system. If it is not sufficient, you can change this value in the Domino server document:
Go to the Lotus Traveler tab and change the value in the Maximum Memory Size field.
6.2 Upgrading to 8.5.3 Upgrade Pack 1 from a previous version
of Lotus Notes Traveler
This section provides the procedure to upgrade Lotus Notes Traveler server from a previous
version to 8.5.3 Upgrade Pack 1.
If you plan to convert your Lotus Notes Traveler environment to an HA configuration, Lotus
Notes Traveler 8.5.3 Upgrade Pack 1 is required. You must first bring your Lotus Notes
Traveler to the 8.5.3 Upgrade Pack 1 level then use the procedure described in 6.3, Moving
from Lotus Notes Traveler 8.5.3 Upgrade Pack 1 stand-alone to a high availability
environment on page 285 to convert the stand-alone Lotus Notes Traveler server to a high
availability environment.
The general procedure of upgrading Lotus Notes Traveler to 8.5.3 Upgrade Pack 1 is as
follows:
1. Plan the upgrade and announce the upgrade schedule.
2. Stop Lotus Domino and Lotus Notes Traveler.
Tip: If the Lotus Notes Traveler server is earlier than 8.5.3 upgrade pack 1 then also
add HTTP to the ServerTasks list.
264 IBM Notes Traveler Hints and Tips for a Successful Deployment
3. Backup the necessary files.
4. Upgrade/migrate Lotus Domino.
5. Upgrade/migrate Lotus Notes Traveler.
6. Start Lotus Domino and Lotus Notes Traveler.
7. Validate upgrade.
8. (Optional) Modify parameters in notes.ini and settings in LotusTraveler.nsf.
6.2.1 Announcing the upgrade schedule
Before upgrading, you should announce the upgrade plan of Lotus Notes Traveler to users.
The upgrade process implements a migration of the Lotus Notes Traveler's database to the
new version. This database migration process generally will take 30-45 minutes to complete,
but we have seen cases of it taking up to 90 minutes on larger deployments.
Users cannot access Lotus Notes Traveler during upgrade. If current Lotus Notes Traveler
users, except for iOS device users, wish to use the new features in the clients on their
devices, they will have to update their Lotus Notes Traveler application on mobile devices
after upgrading the servers.
You should give users notice about the upgrade schedule and application upgrade procedure
to avoid confusion caused by upgrading. After the upgrade when the devices first access the
newly upgraded servers they will be prompted that there is a new version available for them to
use. The user can choose to use this new version with the new features if they wish. The user
can choose to check for an upgrade at a later time if they do not wish to upgrade at that time
from the device.
6.2.2 Stopping Lotus Domino server
On the day of upgrading, first, run quit on the Domino console to shutdown Lotus Domino
server.
6.2.3 Backing up files
Backup any files that are needed to restore your environment.
For Lotus Notes Traveler, backup the /LotusTraveler.nsf and <Lotus Domino data>/traveler
directories.
6.2.4 Updating Lotus Domino
If your Lotus Domino version is lower than 8.5.3, you must migrate Lotus Domino server to
8.5.3.
If your Lotus Domino version is 8.5.3, skip this step and go to the Upgrade Lotus Notes
Traveler section.
Complete these steps to migrate the Lotus Domino from Version 8.0.X or 8.5.X to 8.5.3.
1. Remove the TRAVELER parameter from the ServerTasks list in notes.ini.
2. Install Lotus Domino 8.5.3.
Chapter 6. Migration 265
For the installation detail, see Chapter 3, Deploying a stand-alone Lotus Notes Traveler
environment on page 65.
3. Start the Domino server and confirm that migration has succeeded.
During startup, you will be asked if you want to upgrade the design of the Domino
directory. Consider which is acceptable for your environment and input Y(Yes) or N(No). If
the Domino directory is customized, you might not want to upgrade it at this step.
4. After validating the migration by checking there are not any errors, shutdown Lotus
Domino.
6.2.5 Upgrading Lotus Notes Traveler
1. Launch the installer:
Windows:
If installing from a DVD, insert the DVD into the DVD-ROM drive of the target
system. If autorun is enabled for the system, the Common Launchpad starts
automatically. If autorun is disabled, navigate to the DVD content and double-click
launchpad.exe.
If installing from an installation application, run the downloaded file, usually
TravelerSetup.exe.
The following figure shows the first screen.
Linux
266 IBM Notes Traveler Hints and Tips for a Successful Deployment
If installing from a DVD, insert the DVD into the DVD-ROM drive of the target
system. Navigate to the DVD content and run launchpad.sh.
If installing from an installation application, extract the tar file to a temporary
location then run TravelerSetup.
2. Welcome page:
Ensure that Lotus Domino server is stopped and click Next.
Chapter 6. Migration 267
3. Licence agreement:
Review and accept the license agreement.
4. (Linux only) Choose if partitions are used:
If you want to install multiple partitions, check the box. We do not do this in our scenario.
268 IBM Notes Traveler Hints and Tips for a Successful Deployment
5. Software install directories:
Specify the directories in which the Domino program files and data files are located.
Windows
Chapter 6. Migration 269
Linux
6. (Linux only) Domino credentials:
Enter the values for the Lotus Domino user name and group name. These are existing
users and groups on the Linux server that are used to run the Domino server.
270 IBM Notes Traveler Hints and Tips for a Successful Deployment
7. Domino upgrade notification:
The Domino Upgrade Pack 1 is required for the XPages web administration. If this is not
done, then Lotus Notes Traveler 8.5.3 Upgrade Pack 1 will not run properly.
When Domino 8.5.3 Upgrade Pack 1 is not installed, select this option and install it. This
option is checked by default.
8. Review:
Review your selections. If any changes are required, select Previous to update the
selections, otherwise, select Install to continue.
Windows
Chapter 6. Migration 271
Linux
9. Finish:
Select Done when the installation is completed. If any errors or warnings are reported,
review the installation log and contact IBM Support to resolve any problems.
272 IBM Notes Traveler Hints and Tips for a Successful Deployment
6.2.6 Starting Lotus Domino and Lotus Notes Traveler
When you start Lotus Domino, Lotus Notes Traveler is started automatically and its
configuration will be updated. The first time this is done, the database will be migrated to the
8.5.3 upgrade pack 1 level. This will take some time, so be patient and do not think that the
process has hung and kill the process. You will know that this is complete when you see
"Lotus Traveler: Server started"
If Lotus Notes Traveler does not start, run load traveler on the Domino console. If you
encounter the Java VM can't be created error as show in the following figure, run load http on
the Domino console.
If you loading HTTP failed as shown in the following figure, reinstall Lotus Domino 8.5.3 and
Lotus Notes Traveler 8.5.3 Upgrade Pack 1.
You do not need to uninstall Lotus Domino and Lotus Notes Traveler before reinstallation.
Chapter 6. Migration 273
If you see the message of "Lotus Traveler: SEVERE *systemException caught during Lotus
Traveler configuration. Exception was NotesException: Role name [Administrator] not found",
you must give the Administrator role to an user of LotusTraveler.nsf. From 8.5.3 Upgrade
Pack 1, the LotusTraveler.nsf has Administrator role and at least one user must be assigned
to this role to be the administrator. After updating, if no user has this role, the error message is
given.
For details, see Lotus Notes Traveler will not start after upgrade to version 8.5.3 Upgrade
Pack 1 - http://www-01.ibm.com/support/docview.wss?uid=swg21600233
6.2.7 Validating the upgrade
After the server starts, access Lotus Notes Traveler from your desktop Web browser and
mobile devices, and confirm that upgrading Lotus Notes Traveler is successful.
1. Access the web-based administration page:
After upgrading, you can open LotusTraveler.nsf on the Lotus Domino Administrator client.
You can also access it from a web browser.
274 IBM Notes Traveler Hints and Tips for a Successful Deployment
Access http://LotusTraveler.nsf and log in as an administrator of Lotus Notes Traveler.
2. Access the user homepage:
You can access the user homepage from a web browser on both desktop client and mobile
device.
Access http://traveler and log in as a user.
Tip: If you have configured Lotus Notes Traveler for an enterprise database (DB2 or
SQL Server) the LotusTraveler.nsf is only available via the web browser.
Chapter 6. Migration 275
When running the previous version Lotus Notes Traveler 8.3.5 Upgrade Pack 1, you can
access the Notes Traveler using http://servlet/traveler.
After upgrading, you can still use this old link. The server redirects automatically. This is
done so that users do not have to reconfigure their devices after the upgrade to the new
URL.
3. Accessing Lotus Notes Traveler from mobile devices:
All devices excepted the iOS devices are required to upgrade the Lotus Notes Traveler
application after the server is updated to version 8.3 5 Upgrade Pack1 to have the new
features that were introduced in the 8.5.3 upgrade pack 1 version.
The following are the upgrading steps for the Android devices:
For the users who access Lotus Notes Traveler server 8.5.3:
The users will receive notification to download and install the new version of Lotus
Notes Traveler application Lotus Notes Traveler the first time when they try to
synchronize their device the first time after the server is updated.
Download and install the application for Lotus Notes Traveler application for 8.3.5
Upgrade Pack 1 by completing the steps described in 5.3, Installation on an Android
device on page 199.
The user can also select to check for an upgrade from the "Lotus Traveler"
application on their device at a later time.
For the devices that access Lotus Notes Traveler 8.5.2:
These users must update the Lotus Installer.
276 IBM Notes Traveler Hints and Tips for a Successful Deployment
a. When the device accesses the Lotus Notes Traveler the first time after the server is
upgraded to Lotus Notes Traveler 8.5.3 Upgrade Pack 1, user will receive upgrade
notification.
Tap the notification and select Install.
Chapter 6. Migration 277
b. Replace application:
Tap OK.
278 IBM Notes Traveler Hints and Tips for a Successful Deployment
c. Review:
Review what can be accessed by Lotus Installer and select Install.
Chapter 6. Migration 279
d. Open Lotus Installer:
When installation finish, tap Open.
280 IBM Notes Traveler Hints and Tips for a Successful Deployment
e. Start to update Lotus Traveler:
The new Lotus Installer notify you that you can update Lotus Traveler. Select Install.
Chapter 6. Migration 281
f. Uninstall the old application:
Before installing the new version, you have to uninstall the old application. Select OK.
282 IBM Notes Traveler Hints and Tips for a Successful Deployment
g. Finish uninstallation:
When uninstallation finishes, tap OK.
Chapter 6. Migration 283
h. Install the new Lotus Notes Traveler application:
After uninstallation, installation of the new Lotus Notes Traveler application starts.
284 IBM Notes Traveler Hints and Tips for a Successful Deployment
i. Install Lotus Notes Traveler application for 8.3.5 Upgrade Pack 1 by completing the
steps described in 5.3, Installation on an Android device on page 199.
For the installation procedure of other devices, see the following sections.
5.4, Installation on a Windows mobile device on page 223
5.5, Installation on a Sybian or Nokia device on page 250
4. Using Lotus Notes Traveler from mobile devices:
After upgrading the server, you can use Lotus Notes Traveler immediately.
Resynchronization between the server and devices does not occur. Check that each
component runs correctly.
Chapter 6. Migration 285
6.2.8 Additional configuration
There are new notes.ini parameters and security settings for Lotus Notes Traveler 8.5.3
Upgrade Pack 1. You can manage the security settings in LotusTraveler.nsf (either by the
conventional access through the Domino Administrator interface or the new web interface).
If necessary, change the settings and test these before you release the Lotus Notes Traveler
system to users.
6.3 Moving from Lotus Notes Traveler 8.5.3 Upgrade Pack 1
stand-alone to a high availability environment
6.3.1 Integrating an existing Lotus Notes Traveler 8.5.3 Upgrade Pack 1
stand-alone servers into a Lotus Notes Traveler High Availability pool
After this process is complete, all synchronization and administration data is automatically
transferred to the HA pool database. This process is useful for consolidating an existing set of
servers into a single HA pool. This is useful to move off existing servers or transitioning to a
different operating system (OS). For example, Windows 32-bit servers are not supported in
a High Availability pool. However, it is possible to configure a Lotus Notes Traveler server
running on a Windows 32-bit server to join an HA pool, regardless of the OS of the servers in
the pool. The server data is automatically transferred to the HA pool database and then the
Windows 32-bit server can be removed from the configuration.
Integration considerations
When integrating an existing Lotus Notes Traveler 8.5.3 Upgrade Pack 1 stand-alone server
into a Lotus Notes Traveler High Availability pool, consider the following:
During the transfer of data from the internal database to the enterprise database, the
server is unable to serve devices requests. This transfer process can take several hours,
depending on the amount of data.
Lotus Notes Traveler clients do not support changing the server address after
provisioning. This means that to support the integration of existing servers with existing
clients, the existing server address must be aliased to the front end address (external
URL) for the HA pool. Please note: SSL certificate(s) may need to be revoked and
installed on the Load balancer supporting the server addresses.
The new server URL is /traveler. However, for backwards compatibility with existing Lotus
Notes Traveler clients, /servlet/traveler is still supported.
Once a server has been configured for an HA pool, the original internal database data is
removed. It is possible to reconfigure an HA server as a stand-alone server, however, any
synchronization state data will have to be recreated as devices synchronize with the
server after this is done.
6.3.2 Integration strategies
There are two strategies for integrating existing servers into an HA pool:
Building up the HA pool only from existing servers:
286 IBM Notes Traveler Hints and Tips for a Successful Deployment
The advantage of this strategy is that no additional servers are required for the Lotus
Notes Traveler servers. The disadvantage is that you cannot validate the configuration
until at least one of the servers has been reconfigured for HA.
Setting up a new HA pool and then integrate the existing servers into the pool:
The advantage of this strategy is that the initial HA configuration can be validated without
impacting the existing users. Then the integration of the existing servers can be staged. At
the end of the integration, excess servers can be removed from the configuration. The
disadvantage of this strategy is the requirement for additional hardware, at least until the
integration is complete.
The following integration checklist assumes the second strategy:
1. Set up and validate the initial Lotus Notes Traveler High Availability pool.
Note that after the new environment is set up and validated, new users can be provisioned
for the HA pool.
2. Upgrade all of the existing Lotus Notes Traveler servers to the same version/release
utilized by the HA pool.
During the upgrade process, existing data and configuration is migrated as necessary.
Depending upon the size of the database this process can take a while. Note that during
this upgrade process, the server will not be available for device requests.
3. Configure the server for secure communication (optional).
If the HA pools is configured for secure server to server communication, enable this on the
existing servers that will join the HA pool. See step 3 in the below section for assistance
with this.
4. Configure an existing Lotus Notes Traveler server for the HA pool database.
This configuration change will not take affect until the server is restarted.
5. Restart the server.
Upon start, the server detects that it is now configured for an HA environment and starts
transferring all of the user and administration data to the HA pool database. The server is
not available for requests until the data transfer is complete.
6. Validate the configuration.
After the transfer is complete, the server is registered as part of the HA pool. This can be
validated from the web administration interface or from any server in the pool.
7. Update the network configuration such that the server address is aliased by the front end
sprayer, this is published URL that users access from their devices, for the HA pool. See
your documentation for your IP sprayer for assistance with configuring this.
Update the front end sprayer to service this server
8. Update the external server URL setting for the server to coincide with the front end sprayer
for the pool.
9. Repeat steps 3 through 8 for each server to be integrated into the HA pool.
6.3.3 Setting up a new HA pool and integrating an existing servers into the
pool
Follow these instructions to install Lotus Notes Traveler server based on the platform as
described in 3.2, Lotus Notes Traveler installation on Linux on page 67. To set up and
configure for High Availability pool, follow instructions described in 4.3.3, Lotus Notes
Traveler configuration for high availability on page 163.
Chapter 6. Migration 287
Compete these steps to setting up a new HA pool and then integrate the existing servers into
the pool:
1. Set up and validate the initial Lotus Notes Traveler High Availability pool.
The installation considerations for a server that is to be part of an HA pool are as follows:
Each Domino Server running Lotus Notes Traveler should be registered for the same
domain
Each Domino Server running Lotus Notes Traveler should be co-located in the same
data center to reduce latency for inter-server communication
The external URL setting for Lotus Notes Traveler must be the same for each Lotus
Notes Traveler in the pool, and can be setup after installation. This should be the front
end IP sprayer's address.
2. Upgrade all of the existing Lotus Notes Traveler servers to the same version/release
utilized by the HA pool.
Follow instructions as described in 6.2, Upgrading to 8.5.3 Upgrade Pack 1 from a
previous version of Lotus Notes Traveler on page 263.
3. Configure the server for secure communication (optional).
By default, Lotus Notes Traveler uses regular TCP sockets for communication between the
Lotus Notes Traveler server and the HTTP server, and for communications between the
Lotus Notes Traveler servers within an HA pool.
It might be desirable to use secure sockets for this communication if the networking
between the Lotus Notes Traveler servers is not isolated or secure. Note that requiring
secure server to server communications will impact overall performance.
To enable the use of SSL sockets between the Lotus Notes Traveler servers, use the
following steps:
a. 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>
Use the same password for the storepass and the keypass. If the password parameters
are omitted, the keytool will prompt for them.
b. Copy the traveler.jks that was just created to each server. A suggested location is
\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.
c. Open a command prompt and change the directory to \traveler\util.
d. 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.
After making these changes, both the Traveler task and the HTTP task must be
restarted on the Lotus Notes Traveler Server. When the Lotus Notes Traveler server
288 IBM Notes Traveler Hints and Tips for a Successful Deployment
restarts, it will use SSL sockets to communicate with other Lotus Notes Traveler
servers.
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.
4. Configure an existing Lotus Notes Traveler server for the HA pool.
You can add an exiting Lotus Notes Traveler server to an HA pool by configuring this Lotus
Notes Traveler server to use the enterprise database that the servers on the pool shared.
When you configure a stand alone server to use an enterprise database, the server
migrates existing user and security information to the enterprise database. However, if you
are moving from an enterprise database to another database, enterprise or stand-alone,
no user or security data is migrated.
To configuring the Lotus Notes Traveler server to use the enterprise database, follow the
steps outlined in section 4.3.3, Lotus Notes Traveler configuration for high availability on
page 163.
6.4 Moving from a single pool to a multi-pool high availability
environment
6.4.1 Moving from a single pool to a multi-pool high availability environment
A Lotus Notes Traveler High Availability (HA) pool is defined by a group of servers all sharing
the same enterprise database. The first server added to a database effectively creates the
pool (by creating the tables and schema in the common database) and all other servers
added to the same database become members of it. So creating another Lotus Notes
Traveler pool only requires a server to be added to a new database on the enterprise
database server. This second enterprise database server should be on a second machine to
combat the overhead of I/O that the database will execute while servicing Lotus Notes
Traveler servers.
As discussed in 2.12, Enterprise database server clustering on page 61, there are three
main reasons to consider implementing a multi-pool High Availability Lotus Notes Traveler
environment:
You have Lotus Notes Traveler servers in multiple geographical locations.
For performance reasons, it is best to have all members of the Lotus Notes Traveler HA
pool, including the enterprise database servers, be connected though a high speed Local
Area Network (LAN) and be local to each other. Therefore, if you have Lotus Notes
Traveler servers in multiple geographical locations, it is better to create a HA pool in each
of the locations. Note that this arrangement also applies to the enterprise database server
that hosts each pool, so each pool should also have a local database server.
The number of active devices in an existing Lotus Notes Traveler pool has reached
approximately 10,000.
With this number of devices, the inter-communication between the member servers in the
pool and with the enterprise database server becomes significant. Better performance can
be achieved by hosting any further devices over 10,000 in a separate pool rather than
increasing the size of a pool above the 10,000 devices being serviced.
You have multiple Lotus Domino domains that do not share Domino directory information.
Chapter 6. Migration 289
Lotus Notes Traveler supports having users in multiple Domino domains. However, to work
correctly, the Lotus Notes Traveler server must have access to all the Domino directories
of the different domains, normally by using Domino Directory Assistance. If you have
multiple Domino domains that do not share Domino directory information and are using
Lotus Notes Traveler High Availability, you must have a separate HA pool for each Domino
domain, or for each group of domains that do share directory information.
Each Lotus Notes Traveler pool (of up to 10,000 devices) should have its own enterprise
database and database server instance. If hosting multiple Lotus Notes Traveler pool
enterprise databases and database server instances on the same underlying operating
system and hardware, ensure that the system has sufficient capacity to host the additional
load (both in terms of disk space and processing capability). The enterprise database and
database server instance should also be located on the same LAN as the Lotus Notes
Traveler servers in the pool.
The process for actually creating additional Lotus Notes Traveler pools is very similar to those
used for creating a single pool environment as described in 6.3, Moving from Lotus Notes
Traveler 8.5.3 Upgrade Pack 1 stand-alone to a high availability environment on page 285,
but specifying a different database server and database name in the travelerUtil db set
command used to add a Lotus Notes Traveler server into the pool. The exact syntax of this
command differs depending if you are using DB2 for Linux, UNIX, and Windows or Microsoft
SQL Server as your enterprise database server.
Creating a new HA server pool using DB2
To create a new HA server pool using DB2, complete these steps:
1. Create a new database on the DB2 server for Lotus Notes Traveler to use. To create a
separate pool, this database must be different to that used by any existing pools.
2. Copy the db2jcc4.jar file from the DB2 server (normally located in \sqllib\java\) and place
it in the \domino\traveler\lib directory (not the Domino data directory) on your Lotus Notes
Traveler server.
3. Run travelerUtil db set on the Lotus Notes Traveler server to create the pool, but specify
a different database server instance and database name to create a new pool.
For example, the command syntax to create two HA pools is as follow:
To create the first DB2 HA pool, and add any subsequent servers to this pool:
To create the second DB2 HA pool, and add any subsequent servers to this pool:
290 IBM Notes Traveler Hints and Tips for a Successful Deployment
Creating a new HA server pool using Microsoft SQL Server
To create a new HA server pool using Microsoft SQL server, use the following steps:
1. Create a new database on the SQL server for Lotus Notes Traveler to use. To create a
separate pool, this database must different to that used by any existing pools.
2. Create a user on the Microsoft SQL server that has access to the database you created in
the previous step.
3. Download the JDBC Driver 3.0 file, sqljdbc4.jar, from the Microsoft Download Centre and
copy it to the \domino\traveler\lib directory (not the Domino data directory) on your Lotus
Notes Traveler server.
4. Run travelerUtil db set on the Lotus Notes Traveler server to create the pool, but specify
a different database server instance and database name to create a new pool.
For example, to create two HA pools, the command syntax is as follows:
To create the first SQL Server HA pool, and add any subsequent servers to this pool:
To create the second SQL HA pool, and add any subsequent servers to this pool:
6.4.2 Further reading on creating Lotus Notes Traveler high availability pools
The following articles provide more information on how to create Lotus Notes Traveler high
availability pools:
Configuring IBM Lotus Notes Traveler High Availability with an enterprise Microsoft SQL
database -
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Configuring_IBM_Lotus_Notes_Traveler
_High_Availability_with_enterprise_Microsoft_SQL_database
Configuring IBM Lotus Notes Traveler High Availability with an enterprise IBM DB2 database -
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Configuring_IBM_Lotus_Notes_Traveler
_High_Availability__with_an_enterprise_IBM_DB2_database
Copyright IBM Corp. 2013. All rights reserved. 291
Chapter 7. Enterprise integration
In this chapter, we describe the tasks and the areas you may want to consider when
integrating IBM Lotus Notes Traveler into a existing enterprise infrastructure. This chapter
includes the following topics:
7.1, LDAP integration on page 292
7.2, Configuring single sign-on on page 297
7
292 IBM Notes Traveler Hints and Tips for a Successful Deployment
7.1 LDAP integration
By default, Lotus Notes Traveler uses the Domino directory as the authentication source,
therefore, users must authenticate using their Lotus Notes name and internet password as
stored in their person document within the Domino directory. It is also possible to configure
Lotus Notes Traveler to use an alternative Lightweight Directory Access Protocol (LDAP)
directory as the authentication source. The LDAP authentication approach has the advantage
of enabling you to use a directory other than the Domino directory for authentication
purposes. For example, if you have another LDAP directory in your organization that you
already use for user authentications, you can configure Lotus Notes Traveler to use that rather
than the default Domino directory. The difference between the two types of authenticating are
shown in the following figures:
Lotus Notes Traveler using default Domino Directory authentication
Chapter 7. Enterprise integration 293
Lotus Notes Traveler using LDAP authentication
To configure Lotus Notes Traveler to use an alternative LDAP directory for authentication, it is
necessary to set up the under lying Lotus Domino server to use a feature called Directory
Assistance (DA). DA is a standard Lotus Domino feature that is used to extend a Lotus
Domino server to connect to other directories beyond the local Domino directory. This can
include using other directories for user addressing purposes (for example, the ability to look
up the email address of user who is not in the local Domino directory) and/or to authenticate
the credentials of HTTP users against an alternative directory. It is this alternative
authentication capability that Lotus Notes Traveler can utilize.
The LDAP directory that you want to authenticate with must contain the users internet email
address, in the same format as it is stored in the Domino directory. This is because it is this
address that the Domino server will retrieve from the LDAP directory if the user completes the
authentication process correctly (that is, enters a valid user ID and password). It will then
match that address to the users person document in the Domino directory to establish their
native Lotus Notes name. Lotus Notes Traveler then uses their "fully qualified" Lotus Notes
name (for example, Joe Bloggs/ITSO/IBM) to validate that they have access to Lotus Notes
Traveler and establish the location of their mail server.
Directory Assistance optionally supports the use of secure sockets layer (SSL) to encrypt the
connection to the LDAP server, if the LDAP server also supports it. All of the communication
between the Lotus Notes Traveler server and the LDAP server is encrypted if SSL is enable in
DA. This is a useful security measure to consider using because it helps protect the user ID
and password credentials submitted by the users as part of the authentication process. It is
especially important to consider using this feature if your Lotus Notes Traveler server is
deployed in a "direct connection" network topology (as discussed in 2.3, Planning your
server and network topology on page 33.
294 IBM Notes Traveler Hints and Tips for a Successful Deployment
7.1.1 Configuring Directory Assistance to enable LDAP authentication
Use the following steps to configure Directory Assistance and enable Lotus Notes Traveler to
authenticate users against an LDAP directory:
1. Using a Lotus Notes client, open the New Application dialogue window.
2. In the "Specify New Application Name and Location" section, set the "Server Name field to
be your Lotus Notes Traveler server. Set the Title field to be Directory Assistance and set
the File name field to be da.nsf.
3. In the "Specify Template for New Application" section, set the "Server Name" field to be
your Lotus Notes Traveler server again and select Show Advanced Templates. The
template section should now populate with a list of available templates from your Lotus
Notes Traveler server. Scroll through the list and select Directory Assistance.
4. Now click OK in the New Application dialogue window to create the new Directory
Assistance database.
5. Once the Directory Assistance database finishes creating, it should automatically open
and display the "About" window. Press Escape to exit this and display the main DA
database content.
6. Click Add Directory Assistance.
7. Click the Naming Contexts (Rules) tab and change the "Trusted for Credentials" setting for
the first row to Yes. Everything else on this tab can be left as per their defaults.
8. Click the Basics tab.
Change the Domain Type to be LDAP.
Set the Domain name to be that of your LDAP directory.
Set the Company name to an appropriate value, but it can actually be any value.
Set the search order to 1, assuming this is the only entry in the DA database. If you
have other entries in the DA database then set the order number to an appropriate
value for your environment.
In the "Make this domain available to" field, make sure only Notes Clients & Internet
Authentication is selected.
Set the "Group authorization" field to No.
Set the "Use exclusively for group authorization or credential authentication" field to
Yes.
Set the "Enabled" field to Yes.
Leave the two fields in the SSO configuration field blank.
Chapter 7. Enterprise integration 295
You can add some explanatory text in the "Comments" field. The completed Basics tab
should look similar to the following example:
9. Now click the LDAP tab. The exact settings you use on this tab depend on the type of
LDAP server you have in your environment so the following examples are for illustrative
purposes only.
Set the "hostname" field to be the address of the LDAP server you wish to connect to.
You can use the Verify button to check the connection.
In the "LDAP vendor" field, choose the type of LDAP server that best matches your
environment from the drop down list.
If necessary for your environment, specify the user name and password that should be
used to connect to your LDAP server. Click Verify to check the connection works.
If necessary for your environment, specify the appropriate value in the "Base DN for
search" field that should be used to connect to your LDAP server. Use Suggest or
check with the administrator of your LDAP server to see if this is necessary. Click Verify
to check the connection works.
In the "Connection Configuration" section, set the "Channel encryption" field to SSL if
you are going to enable encryption or None if not. Note that if you enable SSL, the
Domino server must have a SSL certificate installed and configured for use.
Set the "Port" field to use the correct port number for your LDAP server.
In the "Advanced Options" section, set the values that are appropriate for your LDAP
server if required, otherwise, accept the defaults. Ensure that the "Preferred mail
format" field is set to the Internet Mail Address, and the "Type of search filter to use"
field is set to the correct value that best matches your LDAP server.
296 IBM Notes Traveler Hints and Tips for a Successful Deployment
The completed LDAP tab should look similar to the following example, but with the
correct settings where appropriate for your environment:
10.Click Save and Close to save your new DA configuration.
11.Open the Domino directory (NAMES.NSF) on your Lotus Notes Traveler server, go to
Configuration Servers All Server Documents and then edit the server document
for your Lotus Notes Traveler server.
12.On the Basics tab of the server document, set the "Directory assistance database name"
field to da.nsf and then save and close the document.
Chapter 7. Enterprise integration 297
13.Restart your Lotus Domino server to pick up the changes and have DA enabled.
14.Once the Lotus Domino server completes its restart, run show xdir on the Domino server
console to verify that DA is enabled (it should list the LDAP server in the output).
7.1.2 Further reading on LDAP integration
The following article provides more information about how to configure Directory Assistance
to enable Lotus Notes Traveler to use an alternative LDAP directory for authentication:
Creating a Directory Assistance document for a remote LDAP directory -
http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=/com.ibm.hel
p.domino.admin85.doc/H_EXTENDING_YOUR_DIRECTORY_SERVICE_TO_AN_LDAP_DIRECTORY_7491_
STEPS.html
7.2 Configuring single sign-on
In order for a device from the internet to establish a communication session with an IBM Lotus
Notes Traveler server on the internal network, user authentication is required. This function is
normally provided by the entry-point server, which is either the reverse proxy or load balancer.
Rather than having to maintain multiple or duplicate credentials, it is preferable to have the
entry-point server validate the offered credentials by submitting them to the primary
credentials server.
When the primary credentials server is Domino, you can use the LDAP function of Domino to
perform an LDAP-bind with the credentials. After the entry-point server authenticates the
device, that device is trusted by the internal network. Establishing that trust relationship is
how single sign-on (SSO) is accomplished.
298 IBM Notes Traveler Hints and Tips for a Successful Deployment
If the entry-point server is IBM Mobile Connect, the steps for using Domino as the primary
credentials server are described in 3.4.3, Additional configurations on page 97, which also
references configuring IBM Mobile Connect to generate a lightweight third party
authentication (LTPA) token. By following the configuration procedure, IBM Mobile Connect
can generate an LTPA token which the device inserts in the HTTP header of its messages to
the Lotus Notes Traveler server. This token allows the server to trust the device, which
eliminates the need to perform its own authentication of the device.
Copyright IBM Corp. 2013. All rights reserved. 299
Chapter 8. Administration and management
This chapter deals with the administration and management of the IBM Lotus Notes Traveler
server. We go over the various commands that can be used through the console, as well as
the Lotus Notes Traveler web administration interface (formerly the LotusTraveler.nsf) and the
Domino Administration console.
This chapter covers the following administrative features:
8.1, Server console commands on page 300
8.2, Web-based administration on page 306
8.3, Policy-based management on page 327
8.4, Server document on page 330
8.5, Customizing the Lotus Notes Traveler home page on page 339
8.6, Logging on page 340
8.7, The travelerutil command on page 351
8.8, Monitoring Lotus Notes Traveler on page 354
8.9, Backup and recovery on page 370
8.10, Recommended maintenance on page 371
8
300 IBM Notes Traveler Hints and Tips for a Successful Deployment
8.1 Server console commands
This topic provides a detailed description of the IBM Lotus Notes Traveler console
commands. You can perform the following tasks on the Domino console to start, stop, and
restart Lotus Traveler server.
Start: load traveler
Stop: tell traveler quit
Restart: restart task traveler
8.1.1 Tell command reference
The Lotus Notes Traveler console Tell command allows the administrator to access and
display information about Lotus Note Traveler server. You can run the tell command on the
Domino console.
tell traveler command
For example, to check the status of local Lotus Notes Traveler server, run tell traveler status.
When you have multiple Lotus Notes Traveler in your environment, you can run the tell
command with the -s parameter to send the command to a specific server or to broadcast a
command. When this parameter is not specified, the default is to process the command
locally. Specifying -s sends the command to the specified server. Specifying -s * broadcasts
the command to all servers, while -s *- broadcasts the command to all servers except the
local.
The syntax is as follows:
tell traveler [-s (<serverName> | * | *-)] command
Where:
-s is an optional parameter to send the tell command remotely when the servers are
configured for a High Availability pool.
Use to send the command to a specifically named server.
Use * to send the command to all servers in the High Availability pool.
Use *- to send the command to all servers in the High Availability pool except the local
server.
For example, to check the status of all the Lotus Notes Traveler servers in the HA pool, run
tell traveler -s * status. The status command is forwarded to each server in the pool and the
response is displayed on the local console where the command was originally issued.
The following table lists the tell commands:
Command Result
Active Displays the users who are currently synchronizing with the
server.
Chapter 8. Administration and management 301
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. The effect is that the
server will not service 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.
BannedDoc show DocID UserID Shows the specified banned document. DocID is the UNID or
a noteID of a document.
BannedDoc show * UserID Lists all of the banned documents for the specified user.
BannedDoc show * Lists all of the banned documents on the system.
BannedDoc Remove DocID UserID Removes the ban for a particular document. DocID is the
UNID or a noteID of a document.
BannedDoc Remove * UserID Removes the ban for all banned documents for the specified
user.
BannedDoc Remove * Removes the ban for all banned documents on the server.
BannedDoc Add DocID UserID Bans a particular document from syncing. DocID is the UNID
or a noteID of a document.
BannedDoc dump Attempts to dump all of the banned documents to
DumpDoc.nsf. This should only be used if providing IBM
support the documents in question for troubleshooting
purposes.
Bind show Shows which users have been explicitly bound to a server. By
default this list will be empty.
Bind showall Shows all of the registered users in the High Availability pool,
along with which server they are running on.
Bind enable UserID Removes the binding for the user.
Client show type Displays the available client builds and assignments. If type is
omitted, all types are displayed.
type can be any of the following:
Android_Installer
Android_Sync
Nokia_Installer
Nokia_Sync_S60_3
Nokia_Sync_S60_5
Nokia_Sync_S63
Nokia_Sync
WM_Installer
WM_Sync
WM_Sync_6_PPC
WM_Sync_6_SP
WM_Sync_6_PPC_
WM_Sync_6_SP_
Where is CA, CS, DA, DE, EL, EN, ES, FI, FR, HU, IT, JA,
KO,NB_NO, NL, PL, PT, PT_BR, RU, SK, SV, TR, ZH_CN or
ZH_TW
Command Result
302 IBM Notes Traveler Hints and Tips for a Successful Deployment
Client refresh Checks for new clients.
Client promote type level Makes the specified build the default for clients of the given
type.
Client delete type level Deletes the specific build of the given type.
Client addassignment type level
user|group
Assigns user or group to the specified build of the given type.
user or group can be a comma separated list.
Client removeassignment type level
user|group
Removes the specific assignment for user|group from the
specified build of the given type. user|group can be a comma
separated list. user|group of * means "all".
Client setassignment type level
user|group
Combination of removeassignment * and addassignment
user|group. user|group can be a comma separated list.
Config regex Displays any or all configuration parameters. If regex is not
specified, all configuration parameters will be shown. The
regular expression pattern can be a full name or a regex like
NTS_SSL.*
Delete device user Deletes all data associated with the specified user, including
all device profiles.
Dump user Dumps the information about the specified user to a file.
HADR show Shows the status of all Lotus Notes Traveler servers in the
pool.
HADR ping server This command sends an internal ping request to the specified
server. The response will indicate success if the server is
active or a failure if the server cannot be contacted.
HADR delete server Removes the server from the High Availability pool. You must
take the server offline before executing this action.
Help Displays help topics.
Log AddHandler handler Add a handler to the list of handlers.
handler choices: activity, error, usage, logNsf, console,
errorConsole.
Log AddPackage pkg Adds a package to the log filter. Only packages in the filter list
are logged. * can be used after the package name. Use Log
AddPackage * to log all packages.
Log AddUser level user Logs records for this user at the specified log level. This level
overrides the system log level until this user is removed from
the list.
Log Clear Deletes the logs.
Log Collect Moves the logs and debug data to a subdirectory.
Log Count # Sets maximum number of activity files to keep
Log Export file Exports the log settings to the fully qualified file name.
Command Result
Chapter 8. Administration and management 303
Log Fields fields Controls which fields are logged in the activity file: S=Subject,
B=Body, L=Location, A=Address, P=Phone, *=show all fields,
blank=hide all fields. For example, "Log Fields SB" shows
Subject and Body fields only.
Log Handler handler propname
propvalue
Set a handler property.
handler choices: activity, error, usage, logNsf, console,
errorConsole.
propname choices: level, formatter, filter, limit, count, pattern,
append.
If no parameters are specified, the possible settings for each
handler will be listed.
Log Help Displays help about Log command options.
Log Level level Sets the logging capture level to FINEST, FINER, FINE,
INFO, WARNING, or SEVERE.
Log MaxEntrySize # Maximum size for a single log entry (minimum is 500 bytes)
Log RemoveHandler handler Remove a handler from the list of handlers. Same handler
choices as AddHandler.
Log RemovePackage pkg Removes a package from the log filter.
Log RemoveUser user Removes a user from the list of users that are logging.
Remove all users by specifying *.
Log Show Displays current log settings.
Log Size # Maximum size in megabytes before the activity file overwrites
itself.
Log Usage on/off Enables or disables usage logging.
Log XML propname propvalue Set a property for the XML handler.
propname choices: limit, count, pattern, append.
If no parameters are specified, the current XML handler
settings will be listed.
Mailreplicas show user Shows current mail replica information being used by Lotus
Notes Traveler for the user.
Mailreplicas update user server Search for the user's mail replica information using the
cldbdir.nsf located on server. If found, use this information as
the user's mail replica data.
Memory Displays the amount of memory that Lotus Notes Traveler is
using and how much memory is free for use.
Command Result
304 IBM Notes Traveler Hints and Tips for a Successful Deployment
pmr log file list Performs a systemdump of log files, creates a log file
collection, and automatically uploads it to IBM Support.
Where pmr_number is a properly formatted PMR number.
The syntax must be "5 numeric, 3 alphanumeric, 3 numeric".
Separators can be commas or periods.
Where log file list is a list of files to upload. If log file list is not
present, the server performs a systemdump, log collection
and uploads the resulting Lotus Notes Traveler log archive. If
log file list is present, a new log collection is not performed,
but instead each log file is uploaded for this PMR. log file list
can be one or more file names, separated by spaces with \"
surrounding the file name if it contains spaces itself. A
quotation mark (") by itself is not sufficient, the tell command
processor in Domino will strip it off; it must be \" and included
in the command usage details. You would typically only ever
use the command to upload a specific zip file if a previous
FTP attempt had failed. The file names can be relative files
names (in the Traveler logs directory) or fully qualified file
names including path information.
Policy Help Displays help about Policy command options.
Policy Update user Pushes updates to Lotus Notes Traveler policy settings to
users now. This command only affects Lotus Notes Traveler
users on Domino mail servers before Domino 8.0.1. Specify *
to indicate all users.
Reset device user Forces a sync reset for a device.
Security Add device user Adds the device.
Security approval flag device user Sets the approval state for a user's device. flag can be either
Approve or Deny.
Security Delete device user Removes the device.
Security DeleteAll Remove all users and devices.
Security flagsAdd flag device user Sets the flag for the device. The flag options are all,
wipeDevice, wipeApps, wipeStorageCard, and lock.
Security flagsRemove flag device
user
Removes the flag for the device. The flag options are the
same as those for Security flagsAdd.
Security Help Displays help about Security command options.
Security Policy device user Displays device security policy compliance status.
Security Send device user Sends the security message to the device using all available
means.
Security smsAdd sms device user Sets the SMS address for the device.
Security smsRemove device user Removes the SMS address for the device.
Security Status user Displays status of user and devices owned.
Show user Displays all the information associated with the specified user
and all the devices. This command also validates whether the
user is correctly configured for Lotus Notes Traveler server.
Command Result
Chapter 8. Administration and management 305
8.1.2 High availability commands
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. There are
several tell commands specifically for the HA environment. Where necessary, commands
automatically route a request to another server or broadcast a request to all the servers in the
pool without the administrator requesting that action explicitly. For example, you can use tell
traveler user to show the details for a user. This command is forwarded to the appropriate
server for the user automatically. 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 run tell traveler log level
fine and all servers are notified that the log levels is changed. Command helps is updated,
where applicable, to provide any new parameters that relate to working with a pool of servers.
The following commands are used for the HA environment:
tell traveler HADR
The HADR command is used for managing servers in the High Availability pool. The
following commands are supported:
tell traveler HADR Show
Shutdown Stops the server from accepting new work requests, allows
current work to complete, and then quits.
Stat Clear Clears the Lotus Notes Traveler server statistics.
Stat Help Displays help about Stat command options.
Stat Show Displays the Lotus Notes Traveler server statistics.
Status Performs checks to determine if Lotus Notes Traveler Server
is operating normally, and reports the results of the check to
the administrator.
StopSync device user Saves the current Lotus Notes Traveler Server system state
to a file.
SystemDump Help Displays help about SystemDump command options.
Threads Display server thread pools and thread information.
User user Displays all the information and devices associated with the
specified user. This command also validates whether the user
is correctly configured for Lotus Notes Traveler server.
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.
Version Displays the version information for the Lotus Notes Traveler
server.
Command Result
306 IBM Notes Traveler Hints and Tips for a Successful Deployment
This command shows all servers in the High Availability pool along with the same
information that is available in the Servers view from the web based administration
client.
tell traveler HADR Ping
This command sends an internal ping request to the specified server. The response
will indicate success if the server is active or a failure if the server cannot be contacted.
tell traveler HADR Delete
Removes the server from the High Availability pool. You must take the server offline
before executing this action.
tell traveler available
Specify on or off to enable or disable this server in the High Availability pool. If a server is
available, then it will be considered for load balancing. Disabling a server means that the
internal Lotus Notes Traveler load balancer will not consider this server for new work. For
example: tell traveler available on
tell traveler bind
The bind command allows you to view all of the registered users in the Traveler pool and to
which servers they are currently bound. It also lets you force a user to always connect to a
specific Lotus Notes Traveler server. This might be useful when debugging a single user
so that all of their traffic is routed to a single server and ignores the availability index. Note:
this command is not recognized on a stand alone system.
tell traveler bind show
Shows which users have been explicitly bound to a server. By default this list will be
empty.
tell traveler bind showall
Shows all of the registered users in the High Availability pool, along with which server
they are running on.
tell traveler bind enable
Binds the user to the local server.
tell traveler bind disable
Removes the binding for the user.
8.2 Web-based administration
Web-based administration is one of the new functions of Lotus Notes Traveler 8.5.3 Upgrade
Pack 1.
You can manage users, devices, security, servers and so on through the web-based
administration interface. This is the main tool to manage Lotus Notes Traveler system. The
web-based administration is browser independent and requires JavaScript support and
Cookies to be enabled.
You can access the web-based administration using this URL: http://LotusTraveler.nsf
If you are running the Lotus Notes Traveler server in stand-alone mode, add a full text index to
LotusTraveler.nsf. This will improve the performance of the application.
Chapter 8. Administration and management 307
The following figure shows the top page of the Notes Traveler web-based administration
function.
8.2.1 Device security
On the Device Security page of the web-based administration tool, you can see security
states of devices that have accessed the Lotus Notes Traveler server.
You can manage the device security from this page. Double-click a device name to show the
detail information of the device.
Deny Access
You can disable selected devices for accessing the Lotus Notes Traveler server.
Select one or some devices and click Deny Access. The access is revoked immediately and
the device cannot access the server.
The data which had been synchronized before access was denied remains in mobile devices.
You can use this function to stop access from devices temporarily. For example, when a user
takes a temporary leave from a job or a user lost the device. However, if you want to wipe off
the data on a device, you should not deny access but instead use the Wipe Device action.
Especially for Apple devices, do not issue a deny access action if the intent is to issue a Wipe
Device action. We describe this point further in the next section.
308 IBM Notes Traveler Hints and Tips for a Successful Deployment
Wipe Device
If a user loses their device or it is stolen, wiping the data off the device is a more secure action
than just denying access to the device.
You can choose to wipe off all data on a device, only Lotus Notes Traveler Application and
data, or data on a storage card.
If you select Hard Reset, the device is restored to the factory default settings.
If you select Lotus Traveler application and data, all mail, calendar and contact data that
has been synchronized with Lotus Notes Traveler will be removed. Applications and profiles
remain but the device will no longer be able to connect to the Lotus Traveler server to
synchronize any data until the Lotus Traveler administrator removes the wipe order. If you use
an Apple device and have multiple profiles for other account types, data in profiles which are
not for Lotus Notes Traveler remains.
When you select Storage Card, all data on the storage card is removed regardless of what
owns it. This option is not provided for Apple devices and only applies to devices that use
storage cards.
After the wipe, whichever option you select, the device cannot access the Lotus Notes
Traveler server until an Administrator gives the access again.
Consider the following about remote wiping:
Apple remote wipe:
Apple devices support only the Hard Reset Device and Lotus Traveler Application and
Data options and do not use SMS for remote wipe. For Apple devices, the Lotus Traveler
Application and Data option occurs during a synchronization. As a result, the device must
be able to connect with the server for the data removal to occur. The mail server must be
accessible and the ACL must still be correct for the sync that is erasing all the data to
work. The Lotus Traveler Application and Data option will remove all data and erase all
calendar and contact information. In addition, all mail folders (and their contents) will be
erased, except for the Inbox which is left with a message stating that the device has been
wiped and provides instructions on how to remove the account. The Lotus Notes Traveler
account is not deleted or modified in any way, but if the device tries to synchronize, it will
get an access denied response.
Nokia remote wipe:
For certain Nokia devices, this feature requires installation of a Nokia security enablement
library. You can obtain the library from Nokia IBM Lotus Notes Traveler site
Chapter 8. Administration and management 309
Nokia N-Series devices support only the Lotus Traveler Application and Data option. Only
supported options display for the selected device.
Windows Mobile remote wipe:
Certain older Windows Mobile devices running Windows Mobile version 5 without the
Microsoft Messaging and Security Feature Pack upgrade do not hard reset when they
receive the reset command from the Lotus Notes Traveler server. Instead, these devices
reboot. If this happens, then the Lotus Notes Traveler client detects that the hard reset
command failed and executes a wipe of the Lotus Notes Traveler application and data.
For more detail, see the following links:
Lotus Notes and Domino wiki -> Administering Lotus Notes Traveler 8.5.3 Upgrade Pack 1
-> Remote wipe -
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Remote_wipe_A853UP1
2.1 supported hardware and software -> 11.Devices and Operating systems -
http://www-10.lotus.com/ldd/rbtravelerwiki.nsf/dx/2.1_supported_hardware_and_so
ftware
The wipe occurs when the device is connected to the Lotus Notes Traveler server. When the
device is not connected but an SMS address is registered with the server, an SMS message
is sent to tell the device to wipe the data. This SMS message is sent through the cellular
network, therefore, if the device is on and connected to a cellular network, the wipe command
can run.
Because the Apple devices cannot use SMS message, the Apple devices must be connected
to the Lotus Notes Traveler server to receive the wipe command. You must not deny access
from Apple devices or from an user who own the device before running the wipe command.
Clear Wipe/Allow Access
If you want to cancel the wipe command or allow access for the device which is prohibited
from connecting to the Lotus Notes Traveler server, select the devices and push Clear
Wipe/Allow Access. This action runs immediately.
Change Approval
When Require approval for device access is enabled on the Device Settings page, you can
change approval status by using the Change Approval button.
Update SMS Address
As describe in the "Wipe Device" section, Lotus Notes Traveler can use the SMS message to
wipe data. To use this function, the SMS mail address must be registered with the Lotus
Notes Traveler server. You can register and update SMS address by selecting the device and
pushing Update SMS Address.
8.2.2 Device settings
On the Device Settings page of the web-based administration tool, an administrator can
change contents that is to be synchronized with user devices and security policies for the
Lotus Notes Traveler system. These settings are applied to all mobile devices that access the
Lotus Notes Traveler server. If you want to change a setting just for certain users, you must
use Domino policy instead of this page. Make policy documents and apply them to a user or a
user group.
The following figure shows the Device Setting page.
310 IBM Notes Traveler Hints and Tips for a Successful Deployment
Basic
The Basics tab shows the name and description of the setting document. Anyone cannot
change it.
Preferences
On the Preferences tab, an administrator can set preferences for mobile devices.
Chapter 8. Administration and management 311
The changes of security settings are applied to all mobile devices immediately as all security
settings are treated as locked settings. For other settings, if the changed value is not locked,
the new setting is applied only to devices that are registered to the Lotus Notes Traveler
server after the change but not to devices that are registered before the change.
To enforce the settings on devices that have already registered with Lotus Notes Traveler,
select Lock value on device.
Sync
On the Sync tab, you can change settings about synchronization. By default, users can
change these settings on their devices. However, an administrator can lock values by
selecting Lock value on device. In the Lotus Notes Traveler prior version 8.5.3 Upgrade
Pack 1, locking value must be done through the Domino policy. In 8.5.3 upgrade pack 1, the
administrator can lock the synchronization setting by using the Lotus Notes Traveler default
device settings.
Synchronization Options
Users can select applications to synchronize their data with mobile devices. In
Synchronization Options section, an administrator can make a default setting about that.
312 IBM Notes Traveler Hints and Tips for a Successful Deployment
For Windows Mobile and Android devices, if you select either Email or Calendar, both of them
are synchronized.
For Nokia devices, if either Calendar or ToDo is selected, both of them are synchronized.
ToDo and Journal are not synchronized with Apple devices even if they are selected.
Note: To force the settings of the already registered devices, select Lock value on device.
AutoSync Options
The administrator can change the default frequency of synchronization using AutoSync
Options.
An administrator can lock the values and if do so users cannot change them. However,
considering the usability, leave these settings unlocked. Users generally want to change
synchronization schedule depending on the battery condition or where they are.
Connect when roaming is disabled by default. Leaving it disabled because roaming might
cause a high charge.
Note: To force the settings of the already registered devices, select Lock value on device.
Chapter 8. Administration and management 313
Filter Settings
On the Filter Settings tab, you can set which contents you want to synchronize with mobile
devices.
Mail Filters
You can limit mails to be synchronized with devices. The smaller mail size and number result
shorter synchronization time and smaller storage space of a mobile device required for Lotus
Notes Traveler. However, if limit is too small, usability becomes low. We describe the impact of
receiving a mail that exceeds size limit in the following sections.
By default, users can change settings on their devices. To prevent users from changing the
settings, select Lock value on device.
Email Body Truncation
If you select Email Body Truncation and set the limiting value, mails with the body size
over the limit value are not downloaded automatically. By default, the value is 5000
characters. When using 2-byte character, the limit is 2000 characters. When receiving a
mail exceeding the limit, the user can see the title of the mail on the device, but they must
download the mail body manually to read it.
Maximum Email Attachment Size Allowed
Only an administrator can change this setting. On devices, this setting is not shown. If this
value is 0KB, users cannot refer to any attachments on the mobile devices. On mobile
devices, it appears as attachments is not exist. However, users can send a mail with
attachments from the mobile devices. Users who receive the mail can see attachments on
a Notes client.
Email Attachment Size
This setting limits the size of individual attachment to be downloaded automatically. If not
locked, uses can change this setting. When users receive an attachment exceeding the
limit, they can see the attachment title only. To see the content, users must download the
attachment manually.
Email Date Filter
This setting limits how long mails remain on mobile devices from the date mails were sent.
By default, it is five days and users can change it. Even if an administrator leave this
setting unlocked, an administrator can set the filter limit by entering a number between
1-9999 or selecting unlimited. When the filter limit is set, users can change the filter in
range of the filter limit defines.
High Importance only
If an administrator wants users to use Lotus Notes Traveler only for important mails, select
High Importance Only. With this setting selected, only the high Importance mails are
synchronized.
314 IBM Notes Traveler Hints and Tips for a Successful Deployment
Note: To force the settings of the already registered devices, select Lock value on device.
Other Filters
In the Other Filters section, you can change settings about Calendar, Journal, and ToDo.
How to set Calendar Date Filter and Journal Date Filter is similar to how to set Email Date
Filter described in the Mail Filters section.
If an administrator select Incomplete Status Only for ToDo Status, only tasks that have not
been marked as complete are synchronized with mobile devices.
Note: To force the settings of the already registered devices, select Lock value on device.
Device Settings
The Device Settings view allows an administrator to set the default logging settings on the
devices.
The default setting for Device Logging is Off and the maximum Device log File Size is 2000
KB.
Note: Select Lock value on device to prevent modification of the setting from a Lotus Notes
Traveler client.
Chapter 8. Administration and management 315
Security Settings
On the Security Settings tab, you can set security restrictions for mobile devices. Users
cannot change these settings. There are tabs for Windows Mobile, Nokia, Apple, and Android
for changing the restrictions for each type of devices.
By default, there are no restrictions. You should set securities for losing a device. The
appropriate security level depends on not only the security policy of the corporation but also
who owns a device. For example, if users use their own devices, prohibiting camera for
security will not be acceptable by users.
The changes on this tab are applied to devices dynamically.
When selecting options, consider both security and usability. For the details of planning
security, see 2.7.1, Device security on page 46.
Windows Mobile
For Windows Mobile, there are three settings for device security. By default, none of the
settings is selected. See the figure below (in the figure, we select a setting to show options
under the setting):
Require device password
If you select this option, users must set a password for their mobile device. You can select
Password type from Simple PIN and Strong Alphanumeric.
Devices is locked after the time set in "Inactivity timeout." If you want a device to wipe off
data when a user mistakes a password many times consecutively, use "Wrong Password
before wiping device."
Storage card encryption
This setting requests devices to encrypt their storage cards.
Prohibit devices incapable of security enablement
If you select this option, the server prohibit devices that do not support remote wipe or
security profile from accessing the server.
The Violation Action set the action the Lotus Notes Traveler server should take when a device
violation occurs.
For Require device password and Storage card encryption, the action options are:
Report
The device can synchronize with the server, but the violation is reported to Domino
Domain Monitor on the Lotus Notes Traveler server.
316 IBM Notes Traveler Hints and Tips for a Successful Deployment
On the device, violation is notified to an user on the Lotus Notes Traveler status panel.
Disable Synchronization
The device cannot synchronize with the server until an user changes device settings to
match the security policy.
The violation is reported to the Lotus Notes Traveler server.
Enforce
Lotus Notes Traveler application prompts an user to change settings. The device cannot
sync with the server until an user obey the prompt.
The violation is reported to Domino Domain Monitor on the Lotus Notes Traveler server.
For "Prohibit devices incapable of security enablement", Enforce is the only option.
Nokia
Nokia has the same three device security settings as Windows Mobile. However, Nokia has
more Require device password options than the Windows Mobile has. See the figure below
(in the figure, we select a setting to show options under the setting):
Apple
Apple has three options, Require device password, Prohibit camera, and Prohibit devices
incapable of security enablement. For Violation Action, Enforce is the only option for Apple
devices. See the figure below (in the figure, we select a setting to show options under the
setting):
Chapter 8. Administration and management 317
Android
There are many settings for Android. Some of them are new features of Lotus Notes Traveler
8.5.3 Upgrade Pack 1. See the figure below (in the figure, we select some settings to show
options under settings):
318 IBM Notes Traveler Hints and Tips for a Successful Deployment
Require application password
This is a new option. When this setting is selected, users must enter the Lotus Notes
internet password to use Lotus Notes Traveler application, however, the user are not
required to enter the password when they use other applications on mobile devices. This
option is different from Required device password that makes password required for all
applications on the device.
If an administrator selects this option and Prohibit export of attachments to file system, an
administrator can keep users usability and protect corporate information that is included in
Lotus Notes application and attachment files of mails. However, note that the address
book on a device is not locked.
Disable local password storage
This is a new feature in Lotus Notes Traveler 8.5.3 Upgrade Pack 1.
By default, Lotus Notes internet password is stored in the Lotus Notes Traveler application
or profile. So users can use Lotus Notes Traveler without entering their password after
completing installation. If you select this option, the password is not stored in the local
storage and users must input their password when a device or Lotus Notes application is
restarted. Selecting this option makes a device more secure than the default condition.
Setting both Require device password and Require application password can further
protect user information and data.
Require external mail domain validation
This is a new feature in Lotus Notes Traveler 8.5.3 Upgrade Pack 1.
Chapter 8. Administration and management 319
If a user addresses a mail to a person who is not in the domain specified in Internal mail
domains, Lotus Notes Traveler shows a warning message. You can custom the warning
message. By default, the message is "This mail contains external recipients. Confirm
these external recipients."
Note that certain settings require Android OS 3+ or OS 4+.
Device Access
From the Device Access view, an administrator can set the approval required before a user
device can synchronize data. In addition, the administrator can specify a certain number of
devices that a user can synchronize data without approval. This function applies to all devices
supported by Lotus Notes Traveler.
Require approval for device access
Selecting this setting allows a new device to be registered but not to be synchronized with
Lotus Notes Traveler. The device is in a locked state until approved by an administrator.
Number of devices to allow per user before approval is required
This setting allows an administrator to approve a given number of devices for a user
automatically. The number refers to registered devices per user and is not time sensitive.
For example if set to 1, the first device a user registered does not require approval, but any
additional device registered requires approval for accessing Lotus Notes Traveler.
Completely deleting a device from the database and security record removes it from being
considered in this calculation.
Optional
This allows an administrator to be notified when an approval action is required. The
notification includes the user ID, device ID, device type, and registration date. The
notification list can include users, groups, and Mail-In databases. The registering user
always receives a notification when a device is registered and an approval is required. The
e-mail copy including a link to LotusTraveler.nsf is sent to an administrator.
Approving or denying a device using the Lotus Notes Traveler administration database
(LotusTraveler.nsf)
320 IBM Notes Traveler Hints and Tips for a Successful Deployment
The Device Security view shows the approval state of all devices. The Approval column
reports the current device approval state. This column is sortable. The Approval button allows
both approve and deny actions for a given device, and can be taken against one or more
selected devices. The reported states in this view are:
Not Required: The setting was not enabled when this device connected.
Approved: Device has been approved for access.
Auto Approved: Device Approval was enabled. When this device was registered, the user
was under the set number of devices limit.
Denied: Device is denied to access.
Pending: Approval for this device is pending (synchronization is not allowed in this state).
These are the devices that require action by the administrator.
Double-clicking a device in the view displays the device information window that shows the
Approval state with an approver ID and the approval time.
Approving or denying a device using the tell commands
Use the following tell commands to manage device approval:
tell traveler security approval approve <device> <user>
tell traveler security approval deny <device> <user>
Assignment
The Assignment view allow the administrator to modify the include and the exclude user lists
when the administrator wants to limit the users to whom the default settings apply. Leave
these lists blank so that the defaults apply to all users.
The primary purpose of the include and the exclude list is to allow the administrators to
exclude users from the device settings set by the administrator from the web-administration
tool. Any users excluded uses the device settings built into the Lotus Notes Traveler server.
These built-in settings are the same as the initial default device settings, which are all set to
Chapter 8. Administration and management 321
off. Adding any entries (names, groups, or organizations) to the exclude list excludes those
users from the default device settings. Adding any entries to the include list means that the
default device settings apply only to the users in the list, and all others are excluded. The
exclude list takes precedence if the users are in both lists.
Ensure that you input the full domino name to allow the policy take effect, or you can search
the users from "Lookup" to avoid typo.
8.2.3 Devices
The Devices view displays information for each mobile device that is currently registered with
the Lotus Notes Traveler server.
The following table explains the columns of the device list:
Devices view details
You can retrieve detailed information about each device by clicking the device name link to
display a modal window about the specific device. The information includes the devices data
and the device security data. See 8.2.1, Device security on page 307 to understand device
security view. In addition to the data displayed in the view, there are action buttons available
that will perform operations on devices selected in the view. The actions include:
Deny Access
Selecting a device and Deny Access from the action bar displays a window to confirm
whether the administrator wants to deny access to the selected device. Clicking Yes runs
the requested action to deny access for that device. The page is refreshed with the
updates automatically. The Access field for the corresponding device is updated with the
value "Deny." When the device is in the "Deny" state, it is not allowed to connect to the
Lotus Notes Traveler server.
Wipe Device
Column Information displayed
User The Domino name of the user.
Device Name The name of the device as reported by the device firmware.
Last Sync Time The most recent date and time the device was synchronized.
OS Type The device platform type. For example, Apple-iPhone3C1 is an
iPhone 4 device, HTC One X is a HTC device.
Build Level The Lotus Notes Traveler client version and build number that is
running on this device. The build level is always blank for Apple
devices.
Note: Devices that use native clients (for example, Apple) will
never display a build level.
322 IBM Notes Traveler Hints and Tips for a Successful Deployment
Selecting a device and Wipe Device displays a window with the wipe options available for
that specific device. More than one option can be selected at a time. Note that after
running a Wipe Device action, the device is also prohibited from connecting to the Lotus
Notes Traveler server until a Clear Wipe/Allow Access action is run.
Clear Wipe/Allow Access
This action clears any previous wipe and deny request.
Change Approval
Selecting Change Approval displays a window from which you can approve or deny an
access request from a mobile device. This action is used when the Device Approval
security policy is enabled.
Update SMS Address
The Lotus Notes Traveler administrator can use this action to configure an SMS Mailbox
Address specifically for use on a wipe request. Selecting this action displays a message
box in which the user can enter the SMS mailbox address. Leaving the SMS address
value empty in the message box clears any existing SMS address. SMS addresses are
only applicable for devices that use a Lotus Notes Traveler client (such as Android,
Windows Mobile and Nokia).
OK
Clicking OK dismisses the dialog.
The following figure shows a device view of an Apple mobile devices.
Devices view user interface
The user interface of the Device view include the following:
Column name: All the columns in the view that are sortable by selecting column name.
Show: 10 | 20 | 50 | 100 items: You can change the number of rows that a pager will
display on a single page. The default is 10.
Chapter 8. Administration and management 323
Auto Refresh: Select auto refresh on the right top corner of the page allows web
administration page to refresh the data automatically. The option includes 5 sec, 30 sec, 1
min, 2 min, 5 min, and off. The default value is off.
Search: A search bar is located at the top right corner of the page and you can search by
device name, user, OS type, and build level.
8.2.4 Users
The Users view displays information for each user that have devices registered on the Lotus
Notes Traveler server.
The following table explains the columns of the user list:
The following table explains the columns of the device list:
Users view user interface
The user interface of the User view include the following:
Column name: All the columns in the view that are sortable by selecting column name.
Show: 10 | 20 | 50 | 100 items: You can change the number of rows that a pager will
display on a single page. The default is 10.
Auto Refresh: Select auto refresh on the right top corner of the page allows web
administration page to refresh the data automatically. The option includes 5 sec, 30 sec, 1
min, 2 min, 5 min, and off. The default value is off.
Search: A search bar is located at the top right corner of the page and you can search by
user, mail server, mail file.
Column Information displayed
User The Domino name of the user.
User State Either Online or Offline.
Online means that at least one mobile device has connected to
the server within the last 24 hours. Once 24 hours expires without
any activity, the user moves to the Offline state. When offline, the
mail file of the user is no longer monitored for changes. If the user
stays in the Offline state for longer than the user cleanup interval
(default is 30 days), the user and all devices are automatically
cleaned and removed from the Lotus Notes Traveler server.
Mail Server The mail server currently being monitored for server side data
changes. This server may be different than the home mail server
of the user if a Domino mail server failover has been detected.
Mail File The mail file name of the user.
324 IBM Notes Traveler Hints and Tips for a Successful Deployment
8.2.5 Servers
The Servers view is only available in the web-based administration application when the
Lotus Notes Traveler server is configured for High Availability. This view shows the overview
of each server in the pool.
The following table explains the columns of the Servers view:
Servers view user interface
The user interface of the Servers view include the following:
Column name: All the columns in the view that are sortable by selecting column name.
Show: 10 | 20 | 50 | 100 items: You can change the number of rows that a pager will
display on a single page. The default is 10.
Column Description
Domino Name The Domino server name of the Lotus Traveler server
Server Status Available - the server is running
Unavailable - the server task is not running or the server is
unreachable
Availability Index 0 to 100: The server is available. 100 means 100% available, 0 is
0% available.
-100 to -1: The server is constrained due to load or resource
availability. It will continue to process existing syncs but new syncs
will not start. -100 is most constrained where -1 is least
constrained.
-200: The server is running but it is not available for work from
the load balancer. It will continue to handle users that have been
explicitly bound to run on this server.
Number of Users Number of users currently running on this server
Heartbeat Timestamp of the last time this server recorded that it was still
alive. If the server is shutdown normally, then this value will be
empty. Under normal operation, each Lotus Notes Traveler server
updates the heartbeat every 60 seconds.
Build Level The version and build number of the Lotus Traveler server.
Host Fully qualified internet host name.
Port TCP Port number used in server to server communication for load
balancing and session routing.
IP Address IP address of the server that is used for server to server
communication and session routing.
Chapter 8. Administration and management 325
Auto Refresh: Select auto refresh on the right top corner of the page allows web
administration page to refresh the data automatically. The option includes 5 sec, 30 sec, 1
min, 2 min, 5 min, and off. The default value is off.
Using console commands
There are several Domino console commands that are useful for administering a Lotus Notes
Traveler server pool. See 8.1 Server console commands for more details about commands
specific to a server pool.
8.2.6 Client Software
The Client Software view allows administrator to view and manages Lotus Notes Traveler
clients on the Lotus Notes Traveler server or server pool.
The table below explains the columns of the Client Software view:
Column Description
Client 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.
Build Level The four digit version string and a build level which represents the
build date for this version.
326 IBM Notes Traveler Hints and Tips for a Successful Deployment
Client software view detail
An administrator can use the new, web-based administration client to manage client levels on
the Lotus Notes Traveler server or server pool. The following table explains the actions that
the administrator can take from the Client Software view to managed.
For example, the administrator can use the web based administration program to assign the
updated client level to either specific users or groups of users by Change assignments, or
they could make this the default client of its type by Make Default and delete an specific client
level.
Client software view user interface
The user interface of the Client software view include the following:
Column name: All the columns in the view that are sortable by selecting column name.
Show: 10 | 20 | 50 | 100 items: You can change the number of rows that a pager will
display on a single page. The default is 10.
Auto Refresh: Select auto refresh on the right top corner of the page allows web
administration page to refresh the data automatically. The option includes 5 sec, 30 sec, 1
min, 2 min, 5 min, and off. The default value is off.
Default 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.
Assignments A list of users or groups that have been explicitly assigned to use
this specific client version.
Action Description
Change Assignments Add or remove explicit user assignments for this client level. This
action allows the assignment of individual users or groups of
users.
Make Default 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.
Delete 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.
Note: You can also manually delete client level at
\domino\html\travelerclients\
Column Description
Chapter 8. Administration and management 327
Search: A search bar is located at the top right corner of the page and you can search by
user and build level.
Using console commands
There are several Domino console commands that are useful for administering a Lotus Notes
Traveler client software. See 8.1 Server console commands for more details on commands
specific to a server pool.
8.3 Policy-based management
Domino policy is a powerful mechanism that allow administrators remotely push settings to
users and standardize various parts of Lotus Notes. With the help of Domino policies, you can
define rules for new user registration, mail file settings, security and roaming settings, and
push Lotus Notes settings that can be enabled by default. Administrator can also lock certain
settings if they do not want users to modify them.
You can apply policies to the entire organization, a particular organization unit, or even
specific users or group of users. You can also use policy to set initial values of certain user
settings but allows user to change them, or set and lock certain setting values. If policies are
deployed in an organization and setting documents are properly filled, you will have a
standardized environment. A standardized environment can result in less help desk calls.
There is a difference in managing the setting for the devices through a Lotus Domino policy
document as opposed to the Device Settings in LotusTraveler.nsf interface. The settings
made in LotusTraveler.nsf will take effect quicker (on the next device synchronization with the
Lotus Notes Traveler server) than the Lotus Domino policies. The reason is that the Lotus
Domino policies are maintained in the user's individual mail database file on the Lotus
Domino mail server. To apply these settings to the mail database for the user, the entire
Domino domain tree must be traversed to apply the policy to the selected group. This is then
applied to the users that are included in the policy.
For debugging and troubleshooting purposes, it is important to know that policies are in place
so that there is no confusion between was is being done based on the policy as opposed to
what is being done in the Device Settings in LotusTraveler.nsf. The Lotus Domino policy
settings have priority over the settings made in the Device Settings on LotusTraveler.nsf.
If you implement locking setting, it will work for new phones that installed Lotus Notes Traveler
client after setting is implemented. If you want to force locking setting for new phone, you must
reset Lotus Traveler device status, but deleting Lotus Traveler device entry with console
command on Lotus Traveler server. These commands are:
tell traveler security delete <device ID or * for all devices> <user ID>
tell traveler delete <device ID or * for all devices> <user ID>
You can have default policy document that has Lotus Traveler Settings document for all users.
If you have complicated environment, you can have explicit policy for certain group of users. It
is better when there is organization policy, and user is affected at least by one policy
document. If all the settings are the same for all users, it is advantageous to use the Device
Settings in LotusTraveler.nsf as opposed to a Lotus Domino policy.
This is an example of how to add a Lotus Domino policy:
1. From the Domino administrator navigate to the Dynamic Policies and select Add Policy.
328 IBM Notes Traveler Hints and Tips for a Successful Deployment
2. Select a new Lotus Traveler policy.
Chapter 8. Administration and management 329
3. Enter a policy name.
4. Apply any settings that you want for this policy to implement in the remaining tabs.
330 IBM Notes Traveler Hints and Tips for a Successful Deployment
5. Finally, select Save and Close.
If the Lotus Domino or Lotus Traveler environment is split in several domains you might be
required to deploy and maintain setting of Lotus Traveler policies in every domain.
For more information about the policy and setting documents, such as locking and inheritance
of settings from parent or to child, see
Lotus Domino policy FAQ -
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/domino-policies-faq
Lotus Domino policies -
http://www-10.lotus.com/ldd/dominowiki.nsf/xpViewCategories.xsp?lookupName=Domi
no%20policies
Default device preferences and security settings -
http://www-10.lotus.com/ldd/dominowiki.nsf/xpDocViewer.xsp?lookupName=Administe
ring+Lotus+Notes+Traveler+8.5.3#action=openDocument&res_title=Default_device_pr
eferences_and_security_settings_LNT853&content=pdcontent
8.4 Server document
The server document for the Lotus Notes Traveler server is used for all the configuration and
administration of the various aspects of the Domino server. There are a number of factors that
can be administered with this document for the server and should be used on the server
document if there is a choice to put a parameter change in the server document or the
notes.ini. In this section we will walk through the different factors on the server document that
influence the Lotus Notes Traveler server.
This section covers the following topics:
8.4.1, Traveler tab
Chapter 8. Administration and management 331
8.4.2, Basic tab
8.4.3, Security tab
8.4.4, Port tab
8.4.5, Internet protocols tab
8.4.1 Traveler tab
The Lotus Traveler tab of the server document allows for the administrator of the Lotus Notes
Traveler tab to control certain aspects of the server, and implement settings for the server.
This section goes over all the parts of the Lotus Traveler tab in the server document.
If there is a value that can be defined in both the server document and the notes.ini, the
preferred method for definition is to set this in the server document. If this is defined in both
places, the notes.ini definition takes precedence in almost every case.
Basics
The following figure shows the Basics section.
Maximum memory size
This is the maximum memory size that the Lotus Notes Traveler process can use. For a
64-bit server, set this value to 2048 MB (this is 2 GB) is preferable. When setting this
value, ensure that enough physical memory is available on the machine. Remember that a
single HTTP thread requires about 4 MB of RAM, and the OS needs about 1 GB. The
HTTP server usually takes 256 MB as does the Domino server. If there is not enough
memory on the machine, the Lotus Notes Traveler task will fail to start.
IPC Socket Ports
TCP ports that are used for communications between the Lotus Notes Traveler HTTP
servlet and the Lotus Notes Traveler server task. This communication is only on the local
system so no external firewalls ever see this traffic.
External Server URL
The complete URL used by devices to connect to the server to perform all Lotus Notes
Traveler transactions and data synchronization. This URL ensures that the server sends a
link that the devices can use and should be a URL that Lotus Notes Traveler users can
always access, whether on an internal network or the internet, and should not change.
The URL should include the scheme (HTTP or HTTPS), the server host name, the port
number (if not a default port), and the path, such as /traveler. If the server allows both
HTTP and HTTPS, and HTTP is redirected to HTTPS, then the External URL should be
the HTTPS version and not the HTTP version. If there is a reverse proxy in use, the URL
should be set using this reverse proxy name. If there is a DNS name or IP that is used to
route external traffic to the Lotus Notes Traveler server from the internet, the URL should
be set using this DNS name or IP address.
In an HA pool, all servers must be configured with the same value for this parameter. The
servers are part of a service pool that is accessed through the same front end sprayer,
332 IBM Notes Traveler Hints and Tips for a Successful Deployment
and must be configured with the external URL that will send traffic through that sprayer.
There are two ways this can be accomplished:
The administrator can configure the value to be the same in the Lotus Traveler tab in
the server document of each server in the pool.
The administrator can use the common configuration. See Setup for common
configuration (optional -
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Setup_for_common_configuration
_optional_A853UP1) to ensure that the NTS_EXTERNAL_URL parameter is pushed
down to the notes.ini file on each server.
Lotus Traveler Access
The following figure shows the Lotus Traveler Access section:
Access server
Controls access to the Lotus Notes Traveler server for users with Person documents in
either the primary directory of this server or any secondary directories that are trusted for
credentials using Domino directory assistance. You can also select individual names of
users, servers, and groups to allow access to the Lotus Notes Traveler server.
The default blank value means that all certified users and servers can access the Lotus
Notes Traveler server except any listed in the Not access server field.
Separate multiple names with commas or semicolons.
To specify all members of a branch of a hierarchical name tree, enter an asterisk followed
by a forward slash and certifier name, for example, */Sales/Acme.
Not access server
Select names of users, servers, or groups who should not have access to the Lotus Notes
Traveler server. The default blank value means that no users are denied access.
You can also use the Access server field to deny access; entering names in the Access
server field automatically denies access to those not listed in the field.
Separate multiple names with commas or semicolons.
To specify all members of a branch of a hierarchical name tree, enter an asterisk followed
by a forward slash and certifier name, for example, */Sales/Acme.
Remote user commands
Allows Lotus Notes Traveler users to issue remote user commands from the Lotus Notes
Traveler user home page.
User managed security
This controls whether the user has access to user managed security commands. With
user managed security, users can remotely wipe or lock their own devices without the help
of an administrator using the Manage Security section of the Lotus Notes Traveler User
Home Page.
They can also "clear" their own actions (for example, canceling a wipe request or
unlocking a device).
Chapter 8. Administration and management 333
Users can only perform their own security actions if User Managed Security has been set
to Enabled on the Traveler tab of the Server document by the Administrator. In addition,
users cannot undo any changes requested by the administrator. For example, if the
administrator requests a "Lotus Traveler Application and Data", the user could not "clear"
that request. The only thing the user could do would be to upgrade the request to a "hard
reset device". Similarly, if the administrator does a "hard reset device", the user could do
nothing.
Log settings
All diagnostic logging levels should now be set using the Lotus Notes Traveler console
command "tell traveler log". See the console command reference for more information.
Auto Sync Settings
The following figure shows the Auto Sync Settings section:
Monitor Polling Interval
This value is set in seconds. How frequently a user mail database is checked for changes
when it is actively being monitored for Auto Sync. This check is made between the Lotus
Notes Traveler server and the user mail database.
Port for TCP Connections
If this server is configured for High Availability, the Auto Sync TCP port should be disabled
as this is not a supported option in this mode. To disable the Auto Sync TCP port, set the
port value to 0.
Heartbeat Algorithm
The algorithm to use when sending the connection keep alive message. The keep alive
message is sent only if there is no other Auto Sync activity. Indefinite Detection is the only
supported option. Do not change this value.
Heartbeat initial interval
The initial interval to use for keepalive polling. This value should not be shorter than
any network timeout values and not shorter than the minimum interval specified in
Heartbeat algorithm minimum interval.
Heartbeat algorithm minimum interval
The minimum interval allowed for keepalive polling. The heartbeat algorithm is not
allowed to calculate a value smaller than this value.
Heartbeat Algorithm Maximum Interval
The maximum interval allowed for keepalive polling. The heartbeat algorithm is not
allowed to calculate a value greater than this value.
334 IBM Notes Traveler Hints and Tips for a Successful Deployment
If you use a Windows Mobile or Nokia client version 8.5.2 or later, you might want to
increase the maximum, but keep it still less than your network and VPN timeout.
Heartbeat Retry Interval
How long to use the optimal keepalive interval before calculating a new optimal value.
Device Offline Timeout
If a user is inactive for a time greater than this value, the user mail database is no longer
actively monitored. The user can still access the Lotus Notes Traveler server by activating
the device or starting the Lotus Notes Traveler client. As soon as the device is detected by
the server after this timeout, the server resumes active monitoring of the mail database.
User Cleanup Timeout
If a user is inactive for a time greater than this value, the user is purged from the Lotus
Notes Traveler database. The user can still connect by activating the Lotus Notes Traveler
client, but the client must register again with Lotus Notes Traveler server. The data must
also be synchronized as if it is from a new user.
The user will not have to re-install the application and profile. However, the first
synchronization will be an initial synchronization, and take a longer time to complete the
first synchronization.
8.4.2 Basic tab
In this section, we cover the aspects of the Basic tab that effect the Lotus Notes Traveler
server.
Basics
The following figure shows the Basic section:
Server name
This is the server name for the Domino server that Lotus Notes Traveler is hosted on.
Server title
This is an optional field for informational data that is usually defined on Domino server
setup.
Domain name
Chapter 8. Administration and management 335
This should be the Domino domain name that is used across all the servers in the Lotus
Notes Traveler pool if High Availability is enabled.
Fully qualified Internet host name
This is the fully qualified host name that the server is accessed by via the internet. This
should correspond to the URL that is used to access the server
http(s)://fully_qualified_internet_host_name/traveler.
This URL might be different if internet site documents are being used to access the server
using a different URL.
Directory Information
The following figure shows the Directory Information section:
Directory assistance database name
This is populated with the database that is used for directory assistance if directory
assistance is enabled.
8.4.3 Security tab
In this section, we cover only the aspects that will effect the Lotus Notes Traveler server.
Server Access
The following figure shows the Server Access section of the Security tab:
336 IBM Notes Traveler Hints and Tips for a Successful Deployment
Access server
This field allows all users to access this server by default. If this field has a value then only
those users entered in this field or members of groups in this field will be allowed to access
services on this server. Multiple users or groups can be entered into this field with comma
separated values.
Not access server
If this field is empty then all users can access the server. If there is a value in this field,
then users listed in this field or that are members of groups in this field will not be allowed
to access resources on this server.
Internet Access
The following figure shows the Internet Access section of the Security tab:
The default value for field is "Fewer name variations for higher security." If you would like to
allow for users to log in to the Lotus Notes Traveler with their short name or first and last
name, then you can change this value to "More name variations for lower security."
8.4.4 Port tab
In this section, we cover only the aspects that effect the Lotus Notes Traveler server.
The following figure shows the Web tab under Port tab:
Chapter 8. Administration and management 337
This is where you define the ports that the HTTP or HTTPS communication will take place.
The default value for HTTP is in the field "TCP/IP port number" and is 80. You can set this to a
different port if you wish. The SSL port number is set by default to 443. You can also set this
to a different port if desired. Any changes to these ports also must be reflected on the
"External Server URL" field on the Lotus Traveler tab in the server document.
For example, if you change the TCP/IP port number to port "8080" and are not using SSL,
then you have to define this in the external server URL as:
http://server_name:8080/traveler
If you change the SSL port number to port "4433" and are using SSL, then you will need to
define this in the external server URL as:
https://server_name:4433/traveler
A restart of the HTTP server and Traveler should be done for this to effectively take place.
8.4.5 Internet protocols tab
In this section, we cover the HTTP tab under Internet protocols tab. We explain the sections
that effect the Lotus Notes Traveler server.
Basics
The following figure shows the Basics section:
338 IBM Notes Traveler Hints and Tips for a Successful Deployment
The Number active threads field is important to Lotus Notes Traveler based on the number of
devices that you have configured on the server. This number should be roughly 1.2 times the
number of devices on the system.
For example, if there are 100 devices registered to the system, then this setting should be
120.
This is an approximation, and should be correct in most cases. If there are more connections
made than HTTP threads available, these requests are queued up and put in a wait state on
the server and may lead to a high CPU situation. To determine the number of devices on the
system execute this command on the server console:
tell traveler stat show
To find the number of devices that have registered on the server, search for this entry:
Push.Devices.Total=
When setting the HTTP Active Threads, ensure that your system has sufficient resource to
handle the increased threads. On a 64-bit machine, a single HTTP thread will occupy about 4
MB of memory and on a 32-bit machine, this will be about 1 MB of memory. For example, the
memory required to handle a load of 1000 devices on a 664-bit can be calculated as follows:
Lotus Notes Traveler: 1024MB
HTTP server: 1024MB
Domino: 512MB
Operating system: 1024MB
HTTP Threads set to 1000*1.2 = 1200: 4800MB
Total memory required would be: 8384MB or about 8 GB for the server to run optimally.
You must restart the HTTP server for these changes to take effect: restart task http
Mapping
The following figure shows the Mapping section of the HTTP tab:
Chapter 8. Administration and management 339
If you decide at installation time to set the home URL to go automatically to Lotus Notes
Traveler (http://server_name take you to http://server_name/traveler automatically), set
to the Home URL field to /traveler.
If you want the home URL pointing to be the default HTTP home page, set this field to
/homepage.nsf?Open.
If you want the home URL pointing to the Lotus Notes Traveler, then set this field to /traveler.
You must restart the HTTP server for the change to take effect: restart task http
8.5 Customizing the Lotus Notes Traveler home page
The Lotus Notes Traveler user home page is not customizable. However, you can set certain
options which control which features are displayed on the user home page and control which
Lotus Notes Traveler clients can be downloaded from the user home page.
8.5.1 Notes.ini servlet display parameters
You can change the following Notes.ini parameters to modify what is displayed on the Lotus
Notes Traveler user home page:
NTS_SERVLET_ALLOW_CLIENT_INSTALL
Set to true during installation. Default value is true.
Controls whether the client installation and configuration parts of the user home page are
shown. This parameter is similar to a master switch for enabling or disabling these
portions of the user home page for all device types. If this parameter is set to false, all
client portions of the web page will be disabled. If it is set to true, all client potions of the
web page will be enabled unless any of the following device specific parameters are set to
false. It may be desirable to set this parameter or any of the following
NTS_SERVLET_ALLOW_CLIENT_INSTALL_* parameters to false if an MDM solution is
in use to deploy clients to devices.
NTS_SERVLET_ALLOW_CLIENT_INSTALL_ANDROID
Default value is true.
If NTS_SERVLET_ALLOW_CLIENT_INSTALL is set to true (which is a global parameter
allowing any downloads to be available), the download link for Android clients will be
disabled by setting this parameter to false.
NTS_SERVLET_ALLOW_CLIENT_INSTALL_APPLE
Default value is true.
340 IBM Notes Traveler Hints and Tips for a Successful Deployment
If NTS_SERVLET_ALLOW_CLIENT_INSTALL is set to true (which is a global parameter
allowing any downloads to be available), the download link for Apple profiles will be
disabled by setting this parameter to false.
NTS_SERVLET_ALLOW_CLIENT_INSTALL_NOKIA
Default value is true.
If NTS_SERVLET_ALLOW_CLIENT_INSTALL is set to true (which is a global parameter
allowing any downloads to be available), the download link for Nokia profiles will be
disabled by setting this parameter to false.
NTS_SERVLET_ALLOW_CLIENT_INSTALL_WM
Default value is true.
If NTS_SERVLET_ALLOW_CLIENT_INSTALL is set to true (which is a global parameter
allowing any downloads to be available), the download link for Windows Mobile profiles
will be disabled by setting this parameter to false.
NTS_SERVLET_ALLOW_DELETE_IDFILE
Default value is false.
If enabled, users are able to delete their Lotus Notes ID from their mail database using the
Lotus Notes Traveler Notes ID management web page.
NTS_SERVLET_ALLOW_MANAGE_NOTES_ID
Default value is true.
Controls whether the Manage the Notes ID section of the servlet page is shown.
NTS_SERVLET_ALLOW_USER_COMMANDS
Default value is false.
Controls whether the Execute Commands section of the servlet page is shown for Notes
users that do not have administrative access rights.
NTS_SERVLET_ALLOW_USER_MANAGE_SECURITY
Default value is true.
Controls whether the Manage Security part of the servlet page is shown. If enabled, users
can manage their own devices for wipe requests and other related security actions. A
system administrator can always perform these operations on the server. This controls
whether the users can do the actions themselves.
NTS_SERVLET_ALLOW_REPORT_PROBLEM
Default value is true.
Controls whether the problem report part of the servlet page is shown.
NTS_SERVLET_WEB_FOOTER_INCLUDES_SERVER_INFO
Default value is true.
Controls whether the server information is included in the footer of the servlet page.
8.6 Logging
There are two main places where the logging might be needed in a Lotus Notes Traveler
environment. The first is on the server side of the environment. The second is the on the
device side of the environment. In this section, we go over how to set these different logging
Chapter 8. Administration and management 341
levels and what these different settings correspond to. We also describe the considerations
for a stand-alone environment and a HA environment.
This section covers the following topics:
8.6.1, Log setting
8.6.2, Log considerations in a stand-alone environment
8.6.3, Log considerations in a high availability environment
8.6.1 Log setting
The following table shows the location of log files that are present on the Domino server in
relation to Lotus Notes Traveler.
Logging tell command reference
The tell command for logging has the following syntax:
tell traveler log <command>
The table below shows the variables that the <command> include:
File type Location
Java core dump files <DominoDataDir>/IBM_TECHNICAL_SUPPORT/javacore.traveler.*.l
og
Heap dump files <DominoDataDir>/IBM_TECHNICAL_SUPPORT/heapdump.traveler.
*.log
Traveler logs <DominoDataDir>/IBM_TECHNICAL_SUPPORT/traveler/logs/
directory
NSD files <DominoDataDir>/IBM_TECHNICAL_SUPPORT/NSD*.log
Domino console <DominoDataDir>/IBM_TECHNICAL_SUPPORT/console*.log
HTTP thread logs <DominoDataDir>/IBM_TECHNICAL_SUPPORT/htthr*.log
Servlet logs <Domino data>/domino/workspace/logs/trace-log-*.xml
<Domino data>/domino/workspace/logs/error-log-*.xml
Variables Description
Level <level> Set the logging capture level to: FINEST, FINER, FINE, INFO,
WARNING, or SEVERE.
AddUser <level> <user> Logs records for this user at the specified log level. This level
overrides the system log level until this user is removed from the
list.
RemoveUser <user> Removes a user from the list of users that are logging. You can
remove all users by specifying '*'.
AddPackage <pkg> Adds a package to the log filter. Only packages in the filter list
will be logged. Use AddPackage * to log all packages.
RemovePackage <pkg> Removes a package from the log filter.
ListPackage Displays all possible log packages.
Usage <on|off> Enables or disables usage logging.
342 IBM Notes Traveler Hints and Tips for a Successful Deployment
MaxEntrySize <#> Sets the maximum size for a single log entry.
Size <#> Sets the maximum size (in MB) before the activity file wraps.
Count <#> Sets the maximum number of activity files to keep.
Fields <fields> Controls which fields are logged in the activity file. Options
include:
S = Subject
B = Body
L = Location
A = Address
P = Phone
O = Other
* = Show all fields
Blank = hide all fields
For example, Log Fields SB would show Subject and Body fields
only.
Show Displays current log settings.
Clear Deletes the logs.
Collect Copies the logs to a zip file.
Import <file> Imports the log settings from the fully qualified file name.
Export <file> Exports the log settings to the fully qualified file name.
AddHandler <hlr> Adds a handler to the list of handlers. Options include:
activity
error
usage
logNsf
console
errorConsole
RemoveHandler <hlr> Remove a handler from the list of handlers. Options for <hlr>
include:
activity
error
usage
logNsf
console
errorConsole
Handler Sets a handler property. Choices for <hlr> include:
activity
error
usage
logNsf
console
errorConsole
Variables Description
Chapter 8. Administration and management 343
Server logs
There are two basic types of problems to consider when gathering logs:
User problems: Include device connectivity and synchronization related issues.
Server problems. Include server reliability and configuration issues.
You can run the tell traveler commands through the Domino console to obtain Lotus Notes
Traveler server information. The syntax of the tell command is as follows:
tell traveler [-s (<serverName> | * | *-)] command
Where:
-s is an optional parameter to send the tell command remotely when the servers are
configured for a High Availability pool.
Use <serverName> to send the command to a specifically named server.
Use * to send the command to all servers in the High Availability pool.
Use *- to send the command to all servers in the High Availability pool except the local
server.
Checkpoints before submitting the logs for review
To better aid the Lotus Support staff in troubleshooting the problem, review this checklist
before submitting logs for a problem report.
If the issue is a user problem, verify that the user is running a client that matches the level
of Lotus Traveler Server. The version number of the server is the first line of the log.html
file in the TPR submitted from the device. To get the version of the user's client, look in the
administration User Interface (UI) or use tell traveler client show. If the versions do not
match, ask the user to upgrade to the latest client and see if the problem can be
reproduced.
Check if the NTSActivity* log files contain data that match the date and time of the TPR. If
the logging level is set too high, these files can wrap quickly. There are settings on the
Choices for <prop name> for the
Handeler directly above.
level
formatter
filter
limit
count
pattern
append
If no parameters are specified, the settings for each handler will
be listed.
XML Sets a property for the XML handler. Choices for <prop name>
include:
limit
count
pattern
append
If no parameters are specified, the current XML handler settings
will be listed.
Variables Description
344 IBM Notes Traveler Hints and Tips for a Successful Deployment
Lotus Traveler tab that can be changed to increase the number and size of the NTSActivity
logs. Although in most cases, increasing the logging level for the users effected is
sufficient.
If you are reporting a user problem, always include the user name, the device type and
model being used, and the time the error occurred.
If you are reporting a connectivity problem, then also report the connection type (for
example, WiFi or 3G) and the device carrier.
Log collection for user-based problems
You can use the tell command to gather information and set logging for a particular server in
the cluster and bind a user to that server when you are trouble shooting. In a High Availability
(HA) environment, log settings are shared across servers in the pool. For instance, if you use
the tell traveler log command to change a log setting, that setting is applied to all servers in
the HA pool.
To bind a user to the local server, run the following command on that server:
tell traveler bind enable <userid>
When you finish troubleshooting, unbind the user from that server with the following
command:
tell traveler bind disable <userid>
Perform the following procedure to generate a set of logs for troubleshooting a user-based
problem:
1. Increase the log level for a specific user that is has problem by running the following
command:
tell traveler log adduser finest <username>
2. Include the field data in your log report by running the following command:
tell traveler log fields *
3. Collect HTTP thread logs.
If users are experiencing connectivity or authentication errors, it is helpful to have HTTP
thread logs. Before enabling it, consider backing up the existing HTTP thread log files then
deleting them so that the resulting HTTP thread log files cover only the time of the problem
recreation. This should keep the size of the files collected to a minimum, and can be done
while HTTP is running. These log files are located in the <domino
data>\IBM_TECHINICAL_SUPPORT directory and are called htthr*.log files.
Run the following command to collect HTTP tread log:
tell http debug thread on
This command logs only the HTTP threaders and is usually sufficient. If you want to return
the HTTP threaders and the HTTP body (though it will result in much larger files), use:
tell http debug thread all
4. Ask the user to reproduce the problem and submit a Traveler Problem Report (TPR). For
more information about gathering device logs, see the "Device logs" section below.
5. After the user submits the TPR, run the following command to generate a userdump for
the user.
tell traveler dump <username>
6. Send the collected information to IBM Support:
Chapter 8. Administration and management 345
Run the command:
tell traveler pmr <pmr_number>
Where <pmr_number> is a formatted PMR number (nnnnn,bbb,ccc). This command
performs a system dump of all log files, collect them in one zipped file, and upload (FTP)
the output from the log collection to ECuRep under the designated PMR number
When performing a long running task, such as a user dump, system dump, log collection,
or PMR upload, a console message displays every 30 seconds to indicate that the task is
still running.
If you have already performed a system dump and have a list of file logs to send to IBM
support, add [log file list] to the command:
tell traveler pmr <pmr_number> [log file list]
Where [log file list] is a list of your log files to upload. In this case, the command does not
perform a systemdump of log files and collect them, rather it just uploads the files defined
by [log file list] to ECuRep under the designated PMR number. For more than one file, you
must separate them with a space and place the "\" character on either side of each file
name.
To collect the logs into a log file for use in [log file list], use tell traveler log collect. This
command no longer deletes the NTS*.log files after they are collected. To delete the files,
use tell traveler log clear.
Note: In cases where the Lotus Notes Traveler service does not start at all, you can still
generate, gather, and transmit log files offline by running commands from the file system.
You must run the command from the directory <Domino data root>/traveler/util.
For Windows operating systems: travelerUtil.cmd PMR <pmr_number> [log file list]
For Linux operating systems: ./travelerUtil PMR <pmr_number> [log file list]
If the Lotus Notes Traveler server does not have the ability to FTP files, you can upload the
files to your open PMR by uploading them using this URL:
http://www.ecurep.ibm.com/app/upload
7. Run the following commands to undo the system settings you configured in steps 1, 2 and
3, if necessary:
tell traveler log removeuser <username>
tell traveler log fields <previous setting> (You can run this command to reset the
flags to the default position "tell traveler log fields SLAP").
tell http debug thread off
Log collection for server-based problems
Perform the following procedure to generate a set of logs for troubleshooting a server-based
problem.
1. Increase the logging for the system by running the following command:
tell traveler log level fine
2. Include the field data in your log report by running the following command:
tell traveler log fields *
3. Reproduce the problem.
4. Sent log files to IBM Support:
Run the command:
tell traveler pmr <pmr_number>
346 IBM Notes Traveler Hints and Tips for a Successful Deployment
Where <pmr_number> is a properly formatted PMR number (nnnnn,bbb,ccc). This
command performs a system dump of all log files, collects them in one zipped file, uploads
(FTP) the output from the log collect to ECuRep under the designated PMR number.
When performing a long running task, such as a user dump, system dump, log collect, or
PMR upload, a console message displays every 30 seconds to indicate that the task is still
running.
If you have already performed a system dump and have a list of file logs to send to IBM
support, add [log file list] to the command:
tell traveler pmr <pmr_number> [log file list]
Where [log file list] is a list of your log files to upload. In this case, the command does not
perform a system dump of log files and collect them, rather it just uploads the files defined
by [log file list] to ECuRep under the designated PMR number. For more than one file, you
must separate them with a space and place the "\" character on either side of each file
name.
If the Lotus Notes Traveler service does not start at all, you can still generate, gather, and
transmit log files offline by executing commands from the file system. You must run the
command from the directory <Domino data root>/traveler/util.
For Windows operating systems: travelerUtil.cmd PMR <pmr_number> [log file list].
For Linux operating systems: ./travelerUtil PMR <pmr_number> [log file list].
If the Lotus Notes Traveler server does not have the ability to FTP files, you can upload the
files to your open PMR by uploading them using this URL:
http://www.ecurep.ibm.com/app/upload
5. Run the following commands to undo the system settings you configured in steps 1 and 2,
if necessary:
tell traveler log level <previous setting> (You can run this command to reset the log
lever to the default position "tell traveler log level info").
tell traveler log fields <previous setting> (You can run this command to reset the flags
to the default position "tell traveler log fields SLAP").
Domino logging considerations
If messages related to the problem display on the Domino console, then enable console
logging by running the following command:
start consolelog
Device logs
This section provides information about reporting a problem to the system administrator from
an user device. A Traveler Problem Report (TPR) is invaluable to the system administrator
when working with product support to resolve problems. Problem resolutions can be delayed
by weeks if Lotus support staff have difficulty obtaining a TPR from the System
Administrator.
Submitted TPRs are stored in the <data>\traveler\logs\tprs directory and are named
(UserName)_tpr_(Date).zip. The Date is in GMT and the format is YYYYMMDDHHmmss,
where:
YYYY - 4 digit year (ex: 2010)
MM - 2 digit month, (ex: 03 for March)
DD - 2 digit day of month (ex: 26 for the 26th of the month)
HH - 2 digit hour in a 24 hour clock (ex: 17 for 5PM)
mm - 2 digit minute
Chapter 8. Administration and management 347
ss - 2 digit second
For example, JoeSmith_tpr_20100326173533.zip is a TPR from mobile user JoeSmith that
was reported on March 26th, 2010 at 5:35:33 PM GMT.
Note the .zip extension of TPR files. The logs\tprs directory can also contain files ending with
.stmp and .tmp. These files are partially uploaded TPRs and are not useful in problem
determination.
Android devices
To submit a problem report to your system administrator from an Android device, perform the
following procedure:
1. When you encounter a problem, turn logging on by clicking the Lotus Traveler icon and
selecting Menu Settings Logging Enable Logging.
2. Reproduce the problem if possible. It is important to demonstrate the problem with logging
turned on.
3. Submit a TPR by clicking the Lotus Notes Traveler icon and selecting Menu Tools
Report Problem.
4. The device collects the logs and sends them to the server. Logs are typically stored in the
traveler/logs/tprs folder.
5. If the problem is connectivity-related, the log files might not be sent to the server. In this
case, return to the Report Problem screen by selecting Menu Tools Report
Problem and select Export. The TPR is placed on your SDcard. Use the Problem Report
feature of the Lotus Notes Traveler servlet to upload the compressed file. The servlet can
be accessed at http://hostname/traveler. For SSL, use HTTPS instead of HTTP in the
browser URL.
6. Notify the System Administrator of the problem. Be sure to include as much detail as
possible and the steps to reproduce the problem.
Apple devices
Unfortunately, Apple devices do not have a Lotus Notes Traveler client and therefore have no
logs to submit. The users of the Apple device can submit a TPR from the Lotus Traveler
servlet pages using any connected web browser. The servlet can be accessed at
http://hostname/traveler. For SSL, use HTTPS instead of HTTP in the browser URL.
Additional files can be uploaded as needed. For example, the user can upload a particular
email that does not synchronize, or upload screen captures or text documents of error
messages. Be sure to also notify the System Administrator of the problem and include as
much detail as possible. Typically, the resulting TPR is written to the sever in the
traveler/logs/tprs folder.
Windows Mobile devices
To submit a problem report to your system administrator from a Windows Mobile device,
perform the following procedure:
1. When a problem is encountered, turn logging on by clicking the Lotus Traveler icon and
selecting Menu Settings Logging Logging -> On.
2. Reproduce the problem if possible. It is important to demonstrate the problem with logging
turned on.
3. Submit a TPR by clicking the Lotus Traveler icon and selecting Menu Tools Report
Problem.
4. The device collects the logs and sends them to the server. Logs are typically stored in the
traveler/logs/tprs folder.
348 IBM Notes Traveler Hints and Tips for a Successful Deployment
5. If the problem is connectivity-related, the log files might not be sent to the server. In this
case, copy the TPR compressed file from the Program Files/Lotus Traveler/logs directory
of the device to a connected notebook. Use the Problem Report feature of the Lotus
Traveler servlet to upload the compressed file. The servlet can be accessed at
http://hostname/traveler. For SSL, use HTTPS instead of HTTP in the browser URL.
6. Notify the System Administrator of the problem. Be sure to include as much detail as
possible and the steps to reproduce the problem.
Note: Logging is always enabled. Select Lotus Notes Traveler Tools Report Problem.
Logs are collected in \LotusInstaller\Logs.
Nokia devices
To submit a problem report to your system administrator from a Nokia device, perform the
following procedure
1. When a problem is encountered turn logging on by opening Lotus Traveler and selecting
Options Settings Logging Logging > On.
2. Reproduce the problem if possible. It is important to demonstrate the problem with logging
turned on.
3. Submit a TPR by opening Lotus Traveler and selecting Options Tools Report
Problem.
4. The device collects and sends the logs to the server. Logs are typically stored in the
traveler/logs/tprs folder.
5. If the problem is connectivity-related, the log files may not be sent to the server. In this
case, copy the TPR compressed file from the C:/data/LotusTraveler/ directory of the
device to a connected notebook. Use the Problem Report feature of the Lotus Traveler
servlet to upload the compressed file. The servlet can be accessed at
http://hostname/traveler. For SSL, use HTTPS instead of HTTP in the browser URL.
6. Notify the System Administrator of the problem. Be sure to include as much detail as
possible and the steps to reproduce the problem.
Note: The user can enable logging by entering # then 1 while in the Lotus Mobile Installer.
Select Lotus Notes Traveler Tools Report Problem. Go back to the LMI and enter #
then 1 again, to disable logging and to flush the collected log to
C:\data\LotusInstaller\lmi_log.txt.
PMR command details
For help on the command, run tell the command traveler pmr help.
Usage:
tell traveler [-s ] PMR
Where -s is an optional flag to specify the server you wish to run the command against. Use
-s * to run on all Lotus Notes Traveler servers in the HA environment.
Where is the PMR number. This number is five numeric characters, followed by three
alphanumeric, followed by three more numeric, where the separators can be commas or
periods.
Where [files] is an optional space separated list of files to be uploaded. If [files] is omitted, a
systemdump and log collect will be performed to create a new file that will then be uploaded.
Files can be base file names in the logs directory or fully qualified file names in any directory.
If the name includes a space, you must use \" (not just ") around the name.
Chapter 8. Administration and management 349
Examples:
tell traveler pmr 12345,ABC,000
tell traveler -s "server/domain" pmr 12345,ABC,000
tell traveler -s * pmr 12345,ABC,000
tell traveler pmr 12345,ABC,000 C:\temp\out.txt "C:\Program
Files\Domino\notes.ini"
If the Lotus Notes Traveler server will not start, run the PMR command from a command utility
window from the directory /traveler/util.
For Windows operating systems: travelerUtil.cmd pmr
For Linux operating systems (must be root user): ./travelerUtil pmr
Note: The -s parameter is not available when running from the command line.
If your environment does not allow outgoing FTP, you should still run the PMR command, but
you will have to manually upload the zip file(s) created by the PMR command. One zip file will
be created on each server the command is run on. The file will be created in the
/IBM_TECHNICAL_SUPPORT/traveler/logs directory and will be named something like
datetime_traveler_serverx2Fdomain.zip. For example:
20121106_214056_traveler_myserverx2Fmydomain.zip. Use this URL for uploading
documentation to IBM:
http://www.ecurep.ibm.com/app/upload|http://www.ecurep.ibm.com/app/upload">http://
www.ecurep.ibm.com/app/upload">http://www.ecurep.ibm.com/app/upload|http://www.ecu
rep.ibm.com/app/upload
8.6.2 Log considerations in a stand-alone environment
All the log files for Lotus Notes Traveler are located in the <Domino
data>\IBM_TECHNICAL_SUPPORT\traveler\logs directory on the server. Within this
directory location, there are the NTSActivity*, NTSUsage*, and NTSErrors logs. All data is
filed to the NTSActivity log. All the tracing done on a user or the server is written to the
NTSActivity log files.
All log settings are logged and reflected in the NTSActivity*.log.
Starting in 8.5.3 UP1, the Lotus Traveler tab settings aren't used except for the privacy fields.
"Maximum File Size" is the size of the log file to maintain. When a log file is rolled over, a
timestamp is added to the file name where the "*" is (NTSActivity*.log). The server will keep
350 IBM Notes Traveler Hints and Tips for a Successful Deployment
the amount of historical files as defined by the "Maximum Number of Activity Logs Files"
parameter on the same tab in the server document.
You can change the location of the logging files by defining the "NTS_LOG_ROOT_DIR"
parameter in the notes.ini to point to a different logging directory. The default value for this
parameter is "/IBM_TECHNICAL_SUPPORT/traveler/logs."
You also can use the tell command to manage the logs. On a stand-alone environment,
because setting log settings effect only on that specific environment, there is no need to
specify the "-s" option in the tell command. To run the log setting commands, precede the
command with tell traveler log.
For example, to set the log level to "finer" for the server, run tell traveler log level finer.
If you increase the logging to "finest" using tell traveler log level finest, the both server
logging and users are set to "finest". If you want to log the finest level for only one particular
user, then maintain the server logging on "info" and set the logging for the single user to
"finest.". The method captures the logging that is needed without the log files rolling over.
When the logging is set to finest there will be an /xml directory generated in the logs
directory. These xml files contain the to and from information that is sent to and from the
devices.
When a systemdump or userdump are created they are placed in the /dumps directory
contained in the logs directory.
8.6.3 Log considerations in a high availability environment
In a high availability (HA) environment, Lotus Notes Traveler servers that are in the same HA
pool use the same log settings, except for the location setting of log files.
The location of log files is defined by the "NTS_LOG_ROOT_DIR" parameter in the notes.ini
on each server and so is not shared across the HA pool.
If an administrator changes the other setting on one server, this change will be applied to
other servers because they refer to the identical setting in the enterprise database.
The method of changing the logging setting for a Lotus Notes Traveler server in an HA pool is
the same as the server in a stand-alone environment. For details, see 8.6.1 Log setting and
8.6.2 Log considerations in a stand-alone environment.
Information for HA
The failover information of Lotus Notes Traveler servers and connection to the enterprise
database are particular to a high availability environment. These information is included in
NTSActivity*.log like other Lotus Notes Traveler information. So an administrator can use
NTSActivity*.log to detect problems which occur in a high availability environment.
For example, there are two Lotus Notes Traveler servers, server A and B. If server A goes
down when accessed by users, server B will recognize that A is failed and users will be
registered to B. This event is recorded in NTSActivity*.log similar to the following:
Heartbeat information
[Server A IP address] [Server B IP address] "Server A hostname" Dead XXX 0 "XX"
Heartbeat 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
User registration information
Chapter 8. Administration and management 351
INFO Alarm-0960 [User DN] [Device ID] StateController.processSymbol#XXX User
[User DN] has been registered.
INFO Alarm-0960 [User DN] [Device ID] StateController.processSymbol#XXX
Device [Device ID] for user [User DN] has been registered.
When the enterprise database is down, Lotus Notes Traveler server cannot synchronize with
devices. This event is recorded in NTSActivity*.log like below:
Lotus Traveler: SEVERE *system Error rollingback Transaction id=XXX Exception
Thrown: com.ibm.db2.jcc.am.SqlNonTransientConnectionException:
[jcc][t4][10335][10366][4.13.80] invalid operation: Connection is closed.
ERRORCODE=-4470, SQLSTATE=08003
HTTP JVM: Error rollingback Transaction id=34. For more detailed information,
please consult error-log-0.xml located in
C:/IBM/Lotus/Domino/data/domino/workspace/logs
Lotus Traveler: WARNING *system Status change from Green to Red: Unable to connect
to database via jdbc:db2://[database server hostname:port number].
Lotus Traveler: SEVERE *system Error starting a Transaction Exception Thrown:
com.ibm.db2.jcc.am.DisconnectNonTransientConnectionException:
[jcc][t4][2043][11550][4.13.80] Exception java.net.ConnectException: Error opening
socket to server [database server hostname]/[database server IP address] on port
[port number] with message: Connection refused: connect ERRORCODE=-4499,
SQLSTATE=08001
Note that these are only example. Log contents are different according to differences of
environments.
Logs of other components
In a high availability environment, in addition to the Lotus Notes Traveler servers, there are
Domino mail servers, load balancers, and enterprise database servers. An administrator must
manage logs on all these servers. About how to manage them, see the product documents of
load balancer and database. The following are
IBM Mobile Connect document and IBM DB2 document:
IBM Mobile Connect documentation -
http://publib.boulder.ibm.com/infocenter/lmc/v6r1/index.jsp?topic=/com.ibm.lmc_6.1
.4.doc/home.html
IBM DB2 Database for Linux, UNIX, and Windows Information Center -
http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp
8.7 The travelerutil command
The travelerutil command is added in Lotus Notes Traveler 8.5.3.0 to enable log collection
when the process could not start. It was enhanced to perform new configuration functions in
the Lotus Notes Traveler 8.5.3 Upgrade Pack 1. This command is built during product
installation and contains the server information of the system on which the Lotus Notes
Traveler is installed. Therefore, this command is specific to the system and the data that is in
place at installation time.
To use the travelerutil command, you must run the this on the operating system level of the
server:
352 IBM Notes Traveler Hints and Tips for a Successful Deployment
1. Open a command prompt.
2. Change directory to \traveler\util.
8.7.1 travelerutil db set
The travelerutil db set command configures the Lotus Notes Traveler server to the High
Availability mode.
The basis for high availability for all the Lotus Notes Traveler servers in the pool to share
common data via a remote enterprise database. Thus, if one server is to go down, another
server can access the same data and "pick up" where that server left off. With that said, you
can see that this command changes the Lotus Notes Traveler server from using the internal
local Derby file system database to a central database that can be shared among additional
servers.
IBM DB2 Server usage
To set a Lotus Notes Traveler to use DB2 for Linux, UNIX, and Windows database, use the
following command
travelerUtil db set url=jdbc:db2://<db2server hostname>:<db port>/<traveler db
name> user=<db2 admin id> pw=<db2 password>
Example of this usage:
travelerUtil db set url=jdbc:db2://dbserver.yourco.com:50000/traveler
user=db2admin pw=passw0rd
On Linux the usage would be slightly different:
./travelerUtil db set url=jdbc:db2://dbserver.yourco.com:50000/traveler
user=db2admin pw=passw0rd
Note: "50000" is the default DB2 port.
Micorsoft SQL Server usage
To set a Lotus Notes Traveler to use Microsoft SQL Server database, use the following
commands;
Windows:
travelerUtil db set url=jdbc:sqlserver://<sqlserver hostname>:<db
port>;databasename=<traveler db name> user=<sqlserver user id> pw=<sqlserver
user password>
Example of this usage:
./travelerUtil db set
url=jdbc:sqlserver://dbserver.yourco.com:1433;databasename=TRAVELER
user=LNTUSER pw=passw0rd
Linux:
In a Linux environment, you cannot run the command with the JDBC URL because the
database name is delimited from the server name by a required semicolon and the Linux
shell interprets this semicolon as a command separator. To avoid this problem, run the
command without specifying the
url
Chapter 8. Administration and management 353
parameter:
travelerUtil db set user=<sqlserver user id> pw=<sqlserver user password>
When the system prompts for the JDBC URL, enter:
jdbc:sqlserver://<dbserver.yourco.com>:1433;databasename=<database>
Example of this usage:
./travelerUtil db set user=LNTUSER pw=passw0rd
jdbc:sqlserver://dbserver.yourco.com:1433;databasename=TRAVELER
8.7.2 travelerutil ssl set
By default, Lotus Notes Traveler uses regular TCP sockets for communication between the
Lotus Notes Traveler server and the HTTP server, and for communications between the Lotus
Notes Traveler servers within an HA pool. You might want to use secure sockets for this
communication if the networking between the Lotus Notes Traveler servers is not isolated or
secure. Note that requiring secure server to server communications might impact overall
performance.
To enable the use of SSL sockets between the Lotus Notes Traveler servers, complete the
following steps:
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>
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 created to each server in the HA pool. A suggested location
is \traveler\cfg. It is important for each of the servers to use the same certificate file, so the
keytool command should not be run on each server.
3. Open a command prompt and change the directory to \traveler\util.
4. Run travelerUtil ssl set 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.
After making these changes, both the Lotus NotesTraveler task and the HTTP task must be
restarted on the Lotus Notes Traveler Server. When the Lotus Notes Traveler server restarts,
it will use SSL sockets to communicate with other Lotus Notes Traveler servers.
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.
354 IBM Notes Traveler Hints and Tips for a Successful Deployment
8.8 Monitoring Lotus Notes Traveler
You can monitor the Lotus Notes Traveler server for client connectivity to the server with the
server console or with the NTSUsage logs. You can also monitor the server resources with
specific commands and the logging output. There are also tools available such as Watchit
that are described in this section.
8.8.1 Monitoring device and server synchronization
The users synchronize their device with Lotus Notes Server to update their mail, contacts and
calendar information. This activity is logged in the NTSUsage log. The administrator can
monitor the log for issues such as when the device last connected, what was synchronized
between the device, the return codes (if successful or not), and the time this synchronization
took to complete. This information can be useful to the administrator to determine if devices
are synchronizing with the server and how long this process is taking.
Monitoring with server console
To monitor the client usage, in version 8.5.3 Upgrade Pack 1, Lotus Notes Traveler provides
the ability to add specific handlers to handle the logging objects that are used in Lotus Notes
Traveler. These handlers handle the logging events and "handle" how Lotus Notes Traveler
deals with these logging events. The handler can be configured to contain different
information depending on what information the administrator whish to capture in logging
output.
Lotus Notes Traveler provides commands for adding and removing a handler to the server.
tell traveler log addhandler <handler>
tell traveler log removehandler <handler>
The handlers are:
activity
error
usage
logNsf
console
errorConsole
To add logging to be handled by the console, run this command on the server:
tell traveler Log AddHandler console
The output is similar to this:
[0F20:0022-00D8] 08/13/2012 03:56:33 PM HTTP JVM: Traveler: (CN=<user>/O=<org>,
<device ID>) syncAS D<-S (845b, 3282ms, 200rc, Sync, Email, 4, 11778)
The output shows that there was a synchronization using active sync (syncAS) and this was
done from the server to the device (D<-S). Likewise, you can see a sync that was initiated by
the device to the server (D->S) on the console. This will show you that ere syncs happening
between the server and the device.
Chapter 8. Administration and management 355
Monitoring with logs
You can also monitor the synchronization activities that take place between the device and
the server through the NTSUsage*.log log files.
In this file you can see this type of data:
"07/12 14:58:37.817" 9.27.157.16 9.37.16.125 "CN=John Doe/O=ACME"
http://acme.ibm.com/mail%2Ftest13.nsf sp 200 2390 "Lotus Traveler Android 8.5.3"
Android_26608076e563affa 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 "S2D Mail 2A"
This data is displayed in space delimited columns in the logging line that is entered in the
NTSUsage log. The column names are as follows:
Timestamp: Time stamp of the request.
Device Address: IP address of the device.
If there is a front-end proxy, then this address will be the proxy address instead of the
actual device.
Server Address: IP address of the server.
User ID: User Identification (what the HTTP server normalized the user name to - not
necessarily what the user entered on the device).
Database URL: URL of the database (mail file) to be synced.
Sync Origin: Identifies who requested the sync (ps = prime sync, dm = device manual, dp
= device push, sp = server push).
Status Code: Code indicating the status of the ended sync For example, 200 = success,
408 = timed out, 409 = sync was cancelled because a new sync came in while the old one
was running, 500 = server error, 503 = server too busy.
Duration: Number of milli-seconds that the action took to complete.
User Agent: HTTP User Agent header reported by the device (for a prime sync, there is no
real device, so it is logged as "primesync" for the User Agent).
Device ID: Device Identification.
D->S Mail Adds: Number of mails created on the Device and sent to the Server.
D->S Mail Modifies: Number of mails modified on the Device and sent to the Server.
D->S Mail Deletes: Number of mails deleted on the Device and sent to the Server.
D->S Contacts Adds: Number of address book entries created on the Device and sent to
the erver.
D->S Contacts Modifies: Number of address book entries modified on the Device and sent
to the Server.
D->S Contacts Deletes: Number of address book entries deleted on the Device and sent
to the Server.
D->S Calendar Adds: Number of events created on the Device and sent to the Server.
D->S Calendar Modifies: Number of events modified on the Device and sent to the Server.
D->S Calendar Deletes: Number of events deleted on the Device and sent to the Server.
D->S Todo Adds: Number of todos created on the Device and sent to the Server.
D->S Todo Modifies: Number of todos modified on the Device and sent to the Server.
D->S Todo Deletes: Number of todos deleted on the Device and sent to the Server.
356 IBM Notes Traveler Hints and Tips for a Successful Deployment
D->S Journal Adds: Number of journal entries created on the Device and sent to the
Server.
D->S Journal Modifies: Number of journal entries modified on the Device and sent to the
Server.
D->S Journal Deletes: Number of journal entries deleted on the Device and sent to the
Server.
D->S Folder-Add: Number of mail folders created on the Device and sent to the Server
D->S Folder-Update: Number of mail folders modified on the Device and sent to the
Server
D->S Folder-Delete: Number of mail folders deleted on the Device and sent to the Server
D<-S Mail Adds: Number of mails created on the Server and sent to the Device.
D<-S Mail Modifies: Number of mails modified on the Server and sent to the Device.
D<-S Mail Deletes: Number of mails deleted on the Server and sent to the Device.
D<-S Contacts Adds: Number of address book entries created on the Server and sent to
the Device.
D<-S Contacts Modifies: Number of address book entries modified on the Server and sent
to the Device.
D<-S Contacts Deletes: Number of address book entries deleted on the Server and sent
to the Device.
D<-S Calendar Adds: Number of events created on the Server and sent to the Device.
D<-S Calendar Modifies: Number of events modified on the Server and sent to the Device.
D<-S Calendar Deletes: Number of events deleted on the Server and sent to the Device.
D<-S Todo Adds: Number of todos created on the Server and sent to the Device.
D<-S Todo Modifies: Number of todos modified on the Server and sent to the Device.
D<-S Todo Deletes: Number of todos deleted on the Server and sent to the Device.
D<-S Journal Adds: Number of journal entries created on the Server and sent to the
Device.
D<-S Journal Modifies: Number of journal entries modified on the Server and sent to the
Device.
D<-S Journal Deletes: Number of journal entries deleted on the Server and sent to the
Device.
D<-S Folder-Add: Number of mail folders created on the server and sent to the Device
D<-S Folder-Update: Number of mail folders modified on the server and sent to the Device
D<-S Folder-Delete: Number of mail folders deleted on the server and sent to the Device
Summary: A brief summary showing non-zero counts for device or server updates. For
example, "S2D Mail 2A" means two mail documents were synced from the server to the
device as adds.
Check these two items when monitor the device and server synchronization:
What type of sync is being done.
If the user agent and the device ID are "primesync" primesync, then this was a prime
synchronization that is performed from the Lotus Notes Traveler server to the mail server
to see if there are any updates on the mail file that need to be pushed to the device.
Chapter 8. Administration and management 357
If this is a device synchronization, then the user agent and the device ID shows the Lotus
Notes Traveler client application and device ID, for example:
"Lotus Traveler Android 8.5.3" Android_26608076e563affa
The type of action that was done is the synchronization origin.
The action is shown as the following code:
ps: Prime sync, this was a prime synchronization that is performed from the Lotus
Notes.
dm: Device manual, this was a manual synchronization initiated by the user to
synchronize the device to the server.
dp: Device push, this was a push done from the device to the server, such as a mail
being sent from the device, calendar update on the device, contact change on the on
the device. The device decided to push this to the server without the user selecting the
synchronization option in the UI.
sp: Server push, this is a push initiated by the server to the device, such as a new email
that has arrived on the server, calendar update on the server, contact change on the
server.
The status code next to the synchronization origin field is the code indicating the status of the
ended sync. For example, 200 = success, 408 = timed out, 409 = sync was cancelled
because a new synchronization request came in while the old one was running, 500 = server
error, 503 = server too busy.
8.8.2 Monitoring server resource usage
Server resource usage tide with the system performance. You can use the tell commands to
monitor the usage of the resources on the server.
tell traveler memory
This command gives you an overview of the memory that is being used on the server. If you
suspect a memory problem on the server, or are curious as to the memory that is being
allocated on the server, you can use this command. The following is an output example:
tell traveler memory
[1070:7CE0-0BB8] CPU and Memory (MB) Usage History
[1070:7CE0-0BB8] Date CPU Pct Java Mem C Mem Avl Indx # Users
# Errors
[1070:7CE0-0BB8] 2012-09-02 12:22:05 EDT 0.01 31 2594 100 1
0
[1070:7CE0-0BB8] 2012-09-02 12:37:07 EDT 0.01 32 2594 100 1
0
[1070:7CE0-0BB8] 2012-09-02 12:52:08 EDT 0.01 34 2594 100 1
0
The above shows the memory "polls" of the system. These polls are taken every 15 minutes
and logged in this table to show the memory and CPU usage at the time of the poll.
[1070:7CE0-0BB8] Current Memory Usage
[1070:7CE0-0BB8] Java Memory Usage
[1070:7CE0-0BB8] Max Total 1024 MB
[1070:7CE0-0BB8] Current Total 96 MB
[1070:7CE0-0BB8] Free 985 MB (96 percent of Max Total)
358 IBM Notes Traveler Hints and Tips for a Successful Deployment
[1070:7CE0-0BB8] Allocated 39 MB (4 percent of Max Total)
[1070:7CE0-0BB8] C Memory Usage
[1070:7CE0-0BB8] Total Virtual 8388608 MB
[1070:7CE0-0BB8] Total Physical 4095 MB
[1070:7CE0-0BB8] Allocated 2594 MB (64 percent of Total Physical)
[1070:7CE0-0BB8] Current Usage
[1070:7CE0-0BB8] Java 39 MB
[1070:7CE0-0BB8] C 2594 MB
The "Java Memory Usage" is defined as follows:
Max Total - This is the max memory defined for the server as defined in the max memory
parameter in the Traveler tab of the server document
Current Total - This is the amount of memory that is being used by the server at the
current time
Free - This is the amount of free memory. One thing to note is that the JVM will not run
garbage collection and clean up the memory until about 95% of the total memory is used.
After this threshold is reached the garbage collection will run and clean up the used
memory and free up the segments of memory that are no longer referenced in the process
running (Lotus Note Traveler).
Allocated - This is the current amount of allocated memory to the process. Even though
there is the "Max Total" available, the allocated is the amount of memory that is currently
allocated of that "Max Total."
The "C Memory usage" is the defined as follows:
Total Virtual - This is the total virtual amount of memory that is addressable on the
machine. This will only be the amount of usable memory on the machine. For example, if
there is 10GB of RAM on the machine and the OS is taking 2GB of that memory then only
8GB will be addressable for use on the machine.
Total Physical - This is the total amount of physical memory that is addressable on the
machine. This will only be the amount of usable memory on the machine. For example, if
there is 10GB of RAM on the machine and the OS is taking 2GB of that memory then only
8GB will be addressable for use on the machine.
Allocated - This is the amount of allocated memory on the machine. There is currently
2594 MB of memory allocated and in use by the host machine.
The "Current Usage" is defined as follows:
Java - This shows the amount of memory that Java is currently using.
C - This is the amount of memory that the machine is currently using.
tell traveler threads
The tell traveler threads commend gives you the status of the threads that are in use in the
server. You would use this command if the server is behaving slowly, or there is a question of
how to allocate additional threads for the server.
The following shows an output example:
tell traveler threads
> [1070:7D0A-0B30] ########## Thread Manager (Mon Sep 03 13:23:15 EDT 2012) ##########
Chapter 8. Administration and management 359
[1070:7D0A-0B30] --- Summary (Mon Sep 03 13:23:15 EDT 2012) ---
[1070:7D0A-0B30] Shutdown requested: false
[1070:7D0A-0B30] Threads total: 5
[1070:7D0A-0B30] Threads available: 4
[1070:7D0A-0B30] Threads busy: 1
[1070:7D0A-0B30] Threads deadlocked: 0
[1070:7D0A-0B30] Threads monitor deadlocked: 0
[1070:7D0A-0B30] -- Busy Thread Counts (Name: Current / Peak / Max) --
[1070:7D0A-0B30] DS: 0 / 2 / 5000
[1070:7D0A-0B30] PS: 0 / 1 / 200
[1070:7D0A-0B30] Worker: 0 / 1 / 5000
[1070:7D0A-0B30] TC: 1 / 1 / 50
[1070:7D0A-0B30] Alarm: 0 / 5 / 20
[1070:7D0A-0B30] HTTP: 0 / 11 / 400
[1070:7D0A-0B30] --- Thread Details (5) (Mon Sep 03 13:23:15 EDT 2012) ---
[1070:7D0A-0B30] TC-0b30 [null] [SYSADMIN] [threads] [null] [0 runnables] [Busy? true] [Last
Runnable: Mon Sep 03 13:23:15 EDT 2012] [Running: 15ms] [Idle: 0ms]
[1070:7D0A-0B30] Unassigned-0bb8 [null] [null] [null] [null] [0 runnables] [Busy? false]
[Last Runnable: Never] [Running: 0ms] [Idle: 0ms]
[1070:7D0A-0B30] Unassigned-0d88 [null] [null] [null] [null] [0 runnables] [Busy? false]
[Last Runnable: Never] [Running: 0ms] [Idle: 0ms]
[1070:7D0A-0B30] Unassigned-0ec0 [null] [null] [null] [null] [0 runnables] [Busy? false]
[Last Runnable: Never] [Running: 0ms] [Idle: 0ms]
[1070:7D0A-0B30] Unassigned-0f90 [null] [null] [null] [null] [0 runnables] [Busy? false]
[Last Runnable: Never] [Running: 0ms] [Idle: 0ms]
[1070:7D0A-0B30] --- Per Thread Type Mappings of Tokens to Threads (Mon Sep 03 13:23:15 EDT
2012) ---
[1070:7D0A-0B30] --- Summary (Mon Sep 03 13:23:15 EDT 2012) ---
[1070:7D0A-0B30] Shutdown requested: false
[1070:7D0A-0B30] Threads total: 5
[1070:7D0A-0B30] Threads available: 4
[1070:7D0A-0B30] Threads busy: 1
[1070:7D0A-0B30] Threads deadlocked: 0
[1070:7D0A-0B30] Threads monitor deadlocked: 0
[1070:7D0A-0B30] -- Busy Thread Counts (Name: Current / Peak / Max) --
[1070:7D0A-0B30] DS: 0 / 2 / 5000
[1070:7D0A-0B30] PS: 0 / 1 / 200
[1070:7D0A-0B30] Worker: 0 / 1 / 5000
[1070:7D0A-0B30] TC: 1 / 1 / 50
[1070:7D0A-0B30] Alarm: 0 / 5 / 20
[1070:7D0A-0B30] HTTP: 0 / 11 / 400
The output include the following fields:
Shutdown requested: false - There was not a shutdown requested, this was initiated by the
command "tell traveler threads".
Threads total: 5 - This is the total threads that are allocated and being used in the Lotus
Notes Traveler server.
Threads available: 4 - This is the total amount of threads that are available from the
currently allocated threads.
Threads busy: 1 - The number of threads that are allocated that are doing work.
Threads deadlocked: 0 - If there are threads deadlocked this will be the value of how many
threads are in this state.
360 IBM Notes Traveler Hints and Tips for a Successful Deployment
Threads monitor deadlocked: 0 - If there are monitor threads deadlocked, this is the
number of these threads.
-- Busy Thread Counts (Name: Current / Peak / Max) --
The counts are shown with three values in the following format:
<the current number of threads being used> / <the peak number of threads used in this
instance of Lotus Notes Traveler> / <the max that you have configured>
In the example output, you see
DS: 0 / 2 / 5000 - DS is the number of Device Sync threads.
PS: 0 / 1 / 200 - PS is the number of Prime Sync threads.
Worker: 0 / 1 / 5000 - This is the number of worker threads on the server.
C: 1 / 1 / 50 - This is the number of Timer Clock threads on the server.
Alarm: 0 / 5 / 20 - This is the number of the Alarm threads on the server.
HTTP: 0 / 11 / 400 - This is the number of the HTTP threads on the server.
--- Thread Details (5) (Mon Sep 03 13:23:15 EDT 2012) ---
TC-0b30 [null] [SYSADMIN] [threads] [null] [0 runnables] [Busy? true] [Last Runnable:
Mon Sep 03 13:23:15 EDT 2012] [Running: 15ms] [Idle: 0ms]
This is the thread details that currently active on the Lotus Notes Traveler server. This
shows the type of action that is being done by the thread, and the data associated with
that thread.
8.8.3 Logging Lotus Notes Traveler status information to log files on an
administrator defined interval
A Domino program document can be used to create an administrator defined interval of Lotus
Notes Traveler server statistics and resource usage.
There are three commands that you can run on the Lotus Notes Traveler server to obtain the
server statistics and resource usage:
tell traveler status
tell traveler mem show
tell traveler stat show
The following is an output example of the tell traveler status command. There will be a
numerical value in place of the "X" in the "X successful" output below:
The Lotus Notes Traveler task has been running since Tue Oct 09 10:36:39 EDT 2012.
There have been X successful device syncs since Lotus Notes Traveler was started.
The overall status of Lotus Notes Traveler is Green.
For the status command details, see the product documentation
(http://www-10.lotus.com/ldd/dominowiki.nsf/xpDocViewer.xsp?lookupName=Administeri
ng+Lotus+Notes+Traveler+8.5.3+Upgrade+Pack+1#action=openDocument&res_title=Status_
commands_A853UP1&content=pdcontent).
The tell traveler stat show command gives you all the statistics that Lotus Notes Traveler
maintains. The following is an output example of the tell traveler mem show command:
Chapter 8. Administration and management 361
Memory Usage:
Java Memory Usage <---This is the total memory that is used by the Lotus Notes Traveler
process.
Max Total 512 MB <---This is the max memory as configured on the Lotus Traveler tab of the
server document.
Current Total 96 MB
Free 481 MB (94 percent of Max Total) <---The amount of free memory of the max memory
configured on the server document. This number is taken at the time of the command.
Allocated 31 MB (6 percent of Max Total) <---The used memory of the max memory configured
on the server document. This number is taken at the time of the command.
C Memory Usage <---This is the total amount of allocatable memory on the machine.
Total Virtual 2047 MB
Total Physical 2047 MB
Allocated 961 MB (48 percent of Total Physical)
Current Usage <---This is a summary of the above "Java Memory Usage" and "C Memory Usage"
values
Java 31 MB
C 961 MB
In the above example, you want to monitor this on intervals. In a Java application it should not
be alarming to see that a high percent of the Java Memory is used. It is not until almost all of
this memory is used (95%-98%) that the Java Virtual Machine will perform a Garbage
Collection and free up this memory for further processing.
To configure the above output to be entered to the NTSActivity* log on regular intervals,
create a Domino server program document by following these steps:
1. Navigate to the "Configuration" tab of the server document for Lotus Notes Traveler.
Select Server Programs:
2. Select Add Program:
362 IBM Notes Traveler Hints and Tips for a Successful Deployment
3. Enter the fields in the Basic table:
Program name: nserver
Command line: -c "". This is the command that you wish to generate the output for. Please
note, there is a space before the "-c"
Server to run on: This should be the Lotus NotesTraveler server.
Enabled/disabled: Select if you want program to be Enabled or Disabled.
Run at times: Select a time or leave this blank to run at intervals.
Repeat interval of: The number of minutes to take the command. It must be "0" if you want
the program to be run at a particular time from above screen shot, the command "tell
traveler status" is to be run every 10 minutes.
Days of week: The days of the week to run this command.
Note: A restart of the Domino server is required for the program document to take effect.
When complete, parse the logs for the particular values required and match them with the
time stamps in the log for a historical view of how the server is behaving over time.
8.8.4 Monitoring Traveler with Watchit
The Watchit tool is a framework to test, debug, monitor, and identify performance trends in
your software deployments. It functions as a part of managing and supporting a distributed
software deployment. The goal of using Watchit is to quickly and pro-actively identify
Chapter 8. Administration and management 363
problems, get to the source of the problem faster, and reduce time to resolution of problems.
All these will save cost and time in supporting your deployment and increase user satisfaction
of the service itself.
Watchit functions as the eyes and ears of your distributed environment by testing each piece
independently to help quickly identify the failing component. The tool helps reduce rounds of
debug beginning at the user facing component and moving along the chain until the root
cause is found. By deploying Watchit, anywhere in the environment, administrators can learn
quickly where problems are, whether they be network, software or hardware.
The Watchit tool currently comes with four existing custom monitor plug-ins to assist in
monitoring the function and performance of a Lotus Notes Traveler deployment. Any plug-in
can be used independently or in unison.
Healthcheck is the component that performs the network host and port connection testing
and monitoring. Healthcheck also gives alerts if a service is lost or if network latency is
seen.
Domino_URL is the component that tests the Lotus Notes Traveler server access by using
HTTP/HTTPS and the Domino HTTP/HTTPS connectivity. Domino_URL tests URL
loading capabilities and performance validation.
Domino_DB is the component that validates the NRPC connectivity to the Domino server
and databases. It tests Domino database access and performance validation to any
database
LDAP_Checker validates the LDAP bind and search operations. It tests LDAP bind and
search.
DB2_Checker tests and monitors the DB connect and search operations to ensure your
DB2 data store is functioning and performing within defined thresholds.
Each plugin, when run concurrently, provides status and performance data in one concise log
for each component of the Lotus Notes Traveler solution. Instant message or email alerts can
be delivered if any function or performance threshold is not met. The logging of each
validation provides insightful relationships between the function and performance of each
component and assists both the administrators and IBM support in identifying failing
components faster than taking the serial approach of adding debug to one component only to
learn the debug identified another piece as the next step in the debug process.
Benefits of using Watchit
The benefits to using Watchit are based on how versatile it is to deploy and the information it
provides instantly when potential issues are seen. Overall, the goal is to provide
administrators a quick tool that can be deployed anywhere in the environment within minutes
to better understand the performance and function of any component anywhere in the
network topology. This is critical for understanding problems (failures or performance) related
to network or location. The tool requires minimal resources, adds no load to the server
components and requires only JRE 1.6 as its software prerequisite.
The first and foremost benefit is the basic concept that the faster the failing component is
identified, the faster the problem will be circumvented. While each server component has its
own debug capabilities, there are times where the debug only points to another component
and then multiple rounds of debug and outages have to be performed to identify the failing
component. Watchit, by testing each component individually, quickly allows administrators the
ability to understand each component and better identify the failing one.
Secondly, another benefit of Watchit is the ability to generate performance reports on each
function which allows administrators to track usage and response times of all the
components. This assists with resource planning, measuring changes in the environment,
364 IBM Notes Traveler Hints and Tips for a Successful Deployment
and understanding the relationship of the performance of the components. For example, if a
hotfix is supplied, for performance, how well is it understood the actual benefit to end users.
Or if a server is added to the LDAP cluster, how well does is that reflected in the actual LDAP
service response to the Lotus Notes Traveler.
Lastly, using Watchit for debug has been a valuable capability. Noting when a condition
occurs, other than waiting for end user reports which are slow to come into the help desk, can
provide a more reliable timeline to when issues occur. The logging is easy to provide IBM
when understand the timing of failures between components. Also, understanding the
performance of one component can make administrators more intelligent on where to focus
their attention when problems occur.
What to monitor
The following figure shows a typical Lotus Notes Traveler deployment and how Watchit would
be used to validate every component. Typically, each server and load balancer would be
tested to understand the entire service as well as each server within the cluster. By testing the
cluster load balancer and each component it is possible to understand the performance of
each component and the access point the services use to get their necessary
communications through.
Watchit runs on any personal computer or workstation, does not require a dedicated machine,
and uses minimal resources on both the workstation and the servers it tests. Identified in the
figure are the flows and monitoring from Watchit which are described as follows:
1. All flows listed above are validated for host/port combinations to ensure each service is up
and measure network socket open/close operations for performance considerations. This
will highlight any network latency, service down or DNS issues.
2. Flow #1: Watchit has the ability to issue LDAP search and bind commands to the LDAP
server for any attribute or entry desired. It maps the success and failure of each request
Chapter 8. Administration and management 365
and the response time to each. Performance thresholds can be defined to alert when
performance is not as expected.
3. Flow #2:The Lotus Notes Traveler servers can be validated by a series of URL requests to
the Lotus Notes Traveler server servlets to ensure the service is available and certain
servlet actions to ensure the service can access the necessary resources in Domino.
Each transaction is logged and response time is calculated. Performance thresholds can
be defined to alert when performance is not as expected.
4. Flow #3: Db2 is monitored from a connect and search perspective. Any DB2 table or
search can be executed to ensure necessary information is quickly available to the Lotus
Notes Traveler servers. Each transaction is logged and response time is calculated.
Performance thresholds can be defined to alert when performance is not as expected.
5. Flow #4:Domino NRPC access to Domino databases can also be validated with database
opens to any resource. This ensure the back end databases are available to the Lotus
Notes Traveler servers as necessary. Performance thresholds can be defined to alert
when performance is not as expected.
Logging with Watchit
Logging with Watchit is a powerful way to collect information from each component in one
single location. The logs provide an insightful relationship between components that allows
administrators the chance to see how one failure or performance alert in one component can
reflect in another piece of the architecture. For example a slow LDAP response could also
result in a slow URL page load or a network outage could result in failures to connect to the
back end Domino server farm.
8/23/12 08:04:09 Domino URL monitor: Domino URL Monitor Begin
08/23/12 08:04:09 Domino URL monitor: Connecting to host: https://traveler_LB.company.com
08/23/12 08:04:09 Domino URL monitor: Connecting to url: /traveler
08/23/12 08:04:09 Database Check: DB2 Check Begin
08/23/12 08:04:09 Domino URL monitor: URL = https://traveler_LB.company.com/traveler
08/23/12 08:04:10 Database Check: Connect to Database traveler_db2.company.com took (in ms): 640
08/23/12 08:04:10 Domino URL monitor: Elasped time to open url:
https://traveler_LB.company.com/traveler was 1360
08/23/12 08:04:10 Domino URL monitor: URL = https://traveler_srv1.company.com/traveler
08/23/12 08:04:11 Database Check: DB2 Search to host traveler_db2.company.com took (in ms): 125
08/23/12 08:04:11 Database Check: DB2 Check End
08/23/12 08:04:11 Domino URL monitor: Elasped time to open url:
https://traveler_srv1.company.com/traveler was 125
08/23/12 08:04:11 Domino URL monitor: Error reading https://traveler_srv1.company.com2_url
string in properties file
08/23/12 08:04:11 Domino URL monitor: Connecting to host: https://traveler_srv2.company.com
08/23/12 08:04:11 Domino URL monitor: Connecting to url: /traveler
08/23/12 08:04:11 Domino URL monitor: URL = https://traveler_srv2.company.com/traveler
08/23/12 08:04:11 Domino URL monitor: Elasped time to open url:
https://traveler_srv2.company.com/traveler was 203
08/23/12 08:04:11 Domino URL monitor: Error reading https://traveler_srv2.company.com2_url
string in properties file
08/23/12 08:04:11 Domino URL monitor: Connecting to host: https://traveler_srv3.company.com
08/23/12 08:04:11 Domino URL monitor: Connecting to url: /traveler
08/23/12 08:04:11 Domino URL monitor: URL = https://traveler_srv3.company.com/traveler
08/23/12 08:04:11 Domino URL monitor: Elasped time to open url:
https://traveler_srv3.company.com/traveler was 125
08/23/12 08:04:11 Domino URL monitor: Error reading https://traveler_srv3.company.com2_url
string in properties file
08/23/12 08:04:11 Domino URL monitor: Connecting to host: https://traveler_srv4.company.com
366 IBM Notes Traveler Hints and Tips for a Successful Deployment
08/23/12 08:04:11 Domino URL monitor: Connecting to url: /traveler
08/23/12 08:04:11 Domino URL monitor: URL = https://traveler_srv4.company.com/traveler
08/23/12 08:04:11 Domino URL monitor: Elasped time to open url:
https://traveler_srv4.company.com/traveler was 140
08/23/12 08:04:11 Domino URL monitor: Error reading https://traveler_srv4.company.com2_url
string in properties file
08/23/12 08:04:11 Domino URL monitor: Waiting 5 minutes before rerunning Domino URL tests
08/23/12 08:04:11 Domino Database monitor: Domino Database Monitor Begin
08/23/12 08:04:11 Domino Database monitor: Connecting to host: Domino_Mail/ORG/ORG1
08/23/12 08:04:11 Domino Database monitor: Database successfully opened : Company Address Book
08/23/12 08:04:11 Domino Database monitor: Database: Domino_Mail/ORG/ORG1/names.nsf open took
(in ms): 391
08/23/12 08:04:40 Ldap Lookup Check: Bind to host ldap.company.com took (in ms): 968
08/23/12 08:04:40 Ldap Lookup Check: LDAP Search to host ldap.company.com took (in ms): 15
08/23/12 08:05:09 Network Scan End
08/23/12 08:05:09 Network Scan Begin
08/23/12 08:06:09 Network Scan End
The log shows the various monitors running concurrently:
Domino URL Monitor for Lotus Notes Traveler access
Domino Database Monitor for Domino DB access
Network Scan Monitor for host/port socket open/close validation
LDAP Lookup Check Monitor for LDAP bind and search validation
DB2 connect and search validation
The ability to condense all the application testing in one location and to quickly move Watchit
instances around makes it very powerful to know how the performance and connectivity is
through your network topology and allows administrations the ability to cross reference issues
to understand where issues originate from. These logs provide an excellent timeline of
problems seen with each component that is easy to look through and can be done by the
local administrator rather than by multiple teams within IBM.
Alerts generated by Watchit
While log generation is useful, it does not provide a proactive way to know of problems as
they begin to manifest themselves throughout the environment. There are also times when
hard to reproduce problems require debug be taken when a certain condition occurs and
relying on end users to call the helpdesk can add a unwanted delay to the data collection
process. Watchit provides two methods of alerting your administration staff of any
performance or functional issue. Email and/or instant message alerts (leveraging Sametime)
can be easily configured. Both have benefits with instant message the power of being
"instant". Email alerts are useful for off-shift hours or sending information to a pager for an
administration team to be paged if problems occur. Both have their benefits and can be
enabled at the same time. The alerts contain a specific message about the URL, LDAP
function, DB2 command, network issue that will point the administration staff in the proper
direction to understand the behavior. Slow URL page loads shows the URLs themselves,
while Domino database validation will show the server and DB. The idea is to present the
most amount of information quickly to the administration staff rather than relying on logs to be
uploaded and reviewed before understanding where root cause may be.
The figure below shows an example of an IM alert:
Chapter 8. Administration and management 367
Email alerts contain the same data and can be delivered to a list of users, a defined group or
an individual. The same is true for IM alerts. Alerting provides a quick way to provide useful
information into the hands of the administration staff without the reliance of end user reports.
Consider these proactive alerts your best way to collect end users reports of problems.
Watchit performance reporting
After the logs are created from the runs, there are many options to generating reports. The
logs can be processed by themselves or concatenated to provide a performance picture of
any time period. Most server components contain statistics that show the performance of the
server itself. What often is missing is the measurement and understanding of the entire path
from client to server. Our teams are measured by the user experience; why not measure the
performance of the client experiences?
Obviously, there are times when there is churn within the software environment supporting
both client and server, in which case, it is important to understand any delta that has occurred
as a result of the initiated changes. An example of this are fixes that are applied to deal with a
performance issue or fixes that may negatively impact performance but are necessary. Both
situations require an understanding of what is being gained or lost, so as to best evaluate
whether the changes are complete or need additional focus before considering the issue
closed.
For example, if you run the Watchit tool on a daily basis, you can concatenate the logs for the
five days of the week and run the report generator to yield a weekly view of the data. It is that
easy. It might be useful to know how the solution performed on any given day, so as to
understand capacity needs on a certain day of the week, for example, if trouble is only seen
on Mondays. It can also be useful to look at the weekly view to get a larger sample size.
To generate a report, the scripts are UNIX shell-based parsing tools that can be run on any
UNIX shell or Cygwin Microsoft Windows environment.
To generate the report, only one command is required:
368 IBM Notes Traveler Hints and Tips for a Successful Deployment
./process_bot_output.sh <logfile.log>
The following is a sample performance report:
URL Loading SUMMARY DATA
Max response time on URL https://traveler_LB.company.com/traveler was(ms):
12344
Min response time on URL https://traveler_LB.company.com/traveler was(ms):
94
total number of loads for url:
5710
average response time on load was(ms):
778
Median was: 297
Max response time on URL https://traveler_srv1.company.com/traveler was(ms):
6047
Min response time on URL https://traveler_srv1.company.com/traveler was(ms):
93
total number of loads for url:
5711
average response time on load was(ms):
124
Median was: 110
Max response time on URL https://traveler_srv2.company.com/traveler was(ms):
12078
Min response time on URL https://traveler_srv2.company.com/traveler was(ms):
93
total number of loads for url:
5711
average response time on load was(ms):
581
Median was: 125
Max response time on URL https://traveler_srv3.company.com/traveler was(ms):
7438
Min response time on URL https://traveler_srv3.company.com/traveler was(ms):
93
total number of loads for url:
5711
average response time on load was(ms):
613
Median was: 125
Max response time on URL https://traveler_srv4.company.com/traveler was(ms):
13375
Min response time on URL https://traveler_srv4.company.com/traveler was(ms):
78
total number of loads for url:
5712
average response time on load was(ms):
616
Median was: 125
End URL Loading SUMMARY DATA
Domino Database Open SUMMARY DATA
Max response time on Database Domino_Mail/ORG/ORG1/names.nsf was(ms):
391
Min response time on Database Domino_Mail/ORG/ORG1/names.nsf was(ms):
Chapter 8. Administration and management 369
391
total number of loads for Database:
1
average response time on load was(ms):
391
Median was: 391
End Domino SUMMARY DATA
LDAP SUMMARY DATA
Max response time on Bind was(ms):
968
min response time on Bind was(ms):
968
total number of Binds was
1
average response time on Binds was(ms):
968
Median was: 968
Max response time on LDAP Search was(ms):
15
min response time on LDAP Search was(ms):
15
total number of LDAP Searchs was
1
average response time on LDAP Search was(ms):
15
Median was: 15
END LDAP SUMMARY DATA
The reports show the following:
Max, min, median, mean for each URL tested
Max, min, median, mean for Domino DB validated
Max, min, median,mean for LDAP searches and bind
These text reports are a quick and easy means to evaluate user response times in your
environment. The reports can be even run on a running instance of the Watchit tool, so you
can get real-time data on the acceptability of the system's current state. While these
response-time reports of individual runs are useful for understanding any given user-to-user
interaction, it is often relevant to produce reports that contrast multiple environments, so as to
better illustrate changes in response times or study comparative environments.
Understanding the performance delta and setting appropriate performance goals is often
critical to implementing changes or deploying new environments successfully. From a debug
perspective, it would be useful to know what our simulations are reporting when customers
are reporting slow performance. This allows us to better isolate the problem and thus resolve
it faster.
Debugging with Watchit
Watchit provides some useful capabilities when problems do occur in the environment. First is
the ability to quickly isolate the failing component. By providing a comprehensive view of each
component and server, administrators are able to quickly assess the failing component. It
would then be useful to cross reference the Watchit logs with server logs to understand the
issues from both client and server perspective. Secondly, the ability to use the alerts, instead
of end user reports allows the support staff to collect data immediately at the closest point of
370 IBM Notes Traveler Hints and Tips for a Successful Deployment
failure which lowers the amount of data support has to review. The logging provides an
excellent timeline to issues that can be hard to get from end user reports.
Given that Watchit can be deployed quickly, anywhere in the environment, it is easy to place a
new instance anywhere trouble may be seen. With the small footprint, ability to run on any
platform supporting Java JRE 1.6, and quick install procedures, Watchit can be quickly
dropped anywhere in the environment to help identify any geographic location issues, server
to server communication issues, and various network latency problems.
Conclusion
The Wathit utility is fully documented and available in the Lotus Greenhouse. Subscriptions to
the Greenhouse Watchit community can be requested by contacting jdewan@us.ibm.com.
First register with the Lotus Greenhouse and then email a request for an invite. The
Community contains all the documentation, download and how-to information needed to get
started. The IBM Field Support Team also provides engagements to analyze your
environment and configure Watchit specifically to your needs.
Watchit can provide great value in lowering costs, reducing time to resolution of problems and
allowing administration staffs to act more pro-actively to situations based on the knowledge
that they can now receive at the time of failure. The monitoring, performance reporting, and
debug capabilities within Watchit make it a useful tool in achieving a successful Lotus Notes
Traveler deployment.
8.9 Backup and recovery
Regardless of the environment (standalone or HA using an enterprise DB), restoring the
backup will only be as good as when the backup was taken. Therefore, there may be some
administrative actions lost (ex: wipes) and some set of devices may have to perform a
recovery sync due to the fact that the device has changes more recent than when the server
data backup occurred.
The data that is used by the Lotus Notes Traveler server is either in a central database if the
Lotus Notes Traveler is in a high availability environment, or in a local file system Derby
database if the Lotus Notes Traveler is a stand-alone server. The Lotustraveler.nsf is a view of
the actual data that is populated in the Lotus Notes Traveler database and thus does not
require backup. The backup consideration is on the actual database.
8.9.1 All deployments of Lotus Notes Traveler
In version 8.5.3 Upgrade Pack 1, the server configuration is maintained in the notes.ini file, so
this file is important to back up for the server. notes.ini is a regular file and can be backed up
using the operating system back up function.
8.9.2 Stand-alone deployments of Lotus Notes Traveler
The data that is important in a stand-alone Lotus Notes Traveler server is housed in the local
file system Derby database. This information is all maintained on the file system of the server
in
<Domino data>\traveler\ntsdb.
Back up this file system using the same backup strategy as other file systems on the server.
Chapter 8. Administration and management 371
This database contains two main tables.
User information
Security information.
The user information is the synchronization anchors of the last time that the respective
devices for each user has synchronized to the server.
The security information is the access status and security details on the server for each
respective device. For example, the access status includes if a device has been wiped or
blocked from the server. Security details include, for example, if there are particular security
policies that are in place for the device, such as if a pin has to be configured on the device,
and if the device is compliant.
If for some reason this directory is deleted from the server, the information will be recreated
on restart of the server and all user and device information will be re-populated. The users
are not required to be re-authenticated against the server, but on the first synchronization
when this data is re-populated, the user might see a slight delay as this information is re-built.
It is important to note that all security data will be lost, and any security actions such as wipes
or deny access requests will no longer be in place on the server.
8.9.3 High Availability deployments of Lotus Notes Traveler
In this type of Lotus Notes Traveler deployment, all the data that is used on the server is
maintained in the central database that has been configured for the servers to use (IBM DB2
for Linux, UNIX, and Windows, or Microsoft SQL Server). Follow the database backup
strategy of your company to back up the enterprise database.
Consult the product documentation for the respective database about how to properly back
up these databases.
8.10 Recommended maintenance
In this section, we describe common maintenance tasks for the Lotus Notes Traveler system.
For a list of recommended maintenance releases for Notes Traveler see this technote
(http://www.ibm.com/support/docview.wss?uid=swg24019529).
If the system is a stand-alone implementation, you must care only nsf files and logs related to
Lotus Notes Traveler and Lotus Domino. If there are VPN server or proxy server, their
maintenance is added. When you configure a high availability system, you must maintenance
Lotus Notes Traveler, Lotus Domino, enterprise database, and load balancer or IP sprayer.
This section focus on the maintenance of Lotus Notes Traveler, Lotus Domino, and enterprise
database. For the maintenance of other components, see their product documents.
8.10.1 All environments
The resource that are common for maintenance on both stand-alone and high availability
Lotus Notes Traveler environment includes application(*.nsf), database, log, and server.
372 IBM Notes Traveler Hints and Tips for a Successful Deployment
Application
Lotus Notes Traveler uses LotusTraveler.nsf to store information about server, users, and
devices. Maintain this file same as other applications files. For example, run compact
command weekly and run updall or fixup monthly.
For details about nsf maintenance, see Administrator Guide for Domino Server maintenance
(http://www-01.ibm.com/support/docview.wss?uid=swg27006573).
Database
In a stand-alone environment, Lotus Notes Traveler uses a Derby relational database to store
the device information, device security information, and synchronization information. In a high
availability environment, IBM DB2 or Microsoft SQL database plays this role. You must
maintain the database that is used by your Lotus Notes Traveler servers.
Log
To have the Lotus Notes Traveler server, the log files must have sufficient space for the Lotus
Notes Traveler to log the operation and configuration information. You can define the log size
in the "Lotus Traveler" tab of the server document tab.
"Maximum File Size" is the size of the log file to maintain. Once a log file is rolled over, a time
stamp is added to the file name where the "*" is (NTSActivity*.log). The server keeps the
number of historical files as defined by the "Maximem Number of Activity Logs Files"
parameter on the same tab in the server document.
You can clear all the logs with the tell traveler log clear command, More details about logging,
see 8.6, Logging on page 340.
Server
The administrator should keep track of the number of devices that are accessing the server
and ensure that the proper number of HTTP threads are allocated to the server.
A guideline for estimating of the number of threads that are needed is 1.2 times of the number
of devices. If the number of devices accessing the server increases from 800 devices to 1000
devices, the HTTP threads that are allocated to the server should be updated to reflect this
change:
For 800 devices, set the number of HTTP threads to 960.
For 1000 devices, set the number of HTTP threads to 1200.
Similar to other Lotus Domino servers, the Lotus Notes Traveler server should be restarted
periodically for stable running.
8.10.2 Stand-alone environment only
In the version before the Lotus Notes Traveler 8.3.1 Upgrade Pack1, you must defragment the
internal database that Traveler used regularly. Though the how Lotus Notes Traveler enters
data into this internal database and makes use of the database has changed, however, it is
still beneficiary to defragment this database on a regular basis.
You can judge how often you should run defrag by checking the size of /traveler/ntsdb.
You must restart the Lotus Notes Traveler to defragment the database. To defragment the
Lotus Notes Traveler database, use the following methods:
Manual defragmentation:
Chapter 8. Administration and management 373
You can instruct the server to defragment the database using the defrag option in the load
traveler command:
load traveler -defrag
Automatic defragmentation:
You can set the NTS_DEFRAG_INTERVAL_DAYS parameter in notes.ini to have the
server detects when is the last defragmentation was performed on the server and run the
defragmentation function on restart if the defined threshold is passed.
For example, if you want the Lotus Notes Traveler to defragment the database every 30
days, set the parameter as follows:
NTS_DEFRAG_INTERVAL_DAYS=30
If this parameter is defined and a defragmentation runs, the following parameter is added
to the notes.ini file:
NTS_LAST_DEFRAG
The NTS_LAST_DEFRAG parameter records the last time a defragmentation was run on
the server. You can also force a defragmentation by deleting the NTS_LAST_DEFRAG
parameter if you have set the NTS_DEFRAG_INTERVAL_DAYS parameter.
8.10.3 High availability environment only
For a high availability deployments of the Lotus Notes Traveler environment, maintaining the
enterprise database is essential. Review the product documentation for the required
maintenance of the database that you use for the server.
374 IBM Notes Traveler Hints and Tips for a Successful Deployment
Copyright IBM Corp. 2013. All rights reserved. 375
Chapter 9. Tuning and troubleshooting
In this section we describe the turning techniques to help the administration maintain the
server performance to meet the service level agreement. We also show the log files that an
administrator can review, to troubleshoot and solve IBM Lotus Notes Traveler related issues
that might occur.
9.1, Performance tuning on page 376
9.2, Problem determination guides on page 379
9.3, Troubleshooting techniques on page 380
9
376 IBM Notes Traveler Hints and Tips for a Successful Deployment
9.1 Performance tuning
Performance tuning is an on-going activity and there are many factors that can influence the
performance of a Lotus Notes Traveler server performance. These factors include host
system resources, the number of devices, the network efficiency, the overall server load, the
amount of data transferred to the devices, and the level of code being run. We explain how to
review your server and configure the related parameters so that the server will run efficiently.
9.1.1 Lotus Notes Traveler high availability considerations
When deploying Lotus Notes Traveler on VMware, to avoid having a single point of failure,
place each Traveler server in the Traveler server pool on a separate VMware ESX server.
For each Lotus Notes Traveler server, keep the number of devices under 2,500.
Note the Maximum number of 2500 devices is per server after a failover has occurred.
Have 4 processor cores and 16 GB memory for each Traveler server in the pool.
Use 64-bit operating system for Lotus Notes Traveler and Lotus Domino (where
supported)
Adjust the Java Max Memory as more devices are added
9.1.2 Latest software version
The Lotus Notes Traveler maintenance release contains the latest fix for the code stream. It is
always a good idea to stay on the latest release of the Lotus Notes Traveler software. For the
latest version of the 8.5.3.100+ software, see the Recommended Maintenance - Lotus Notes
Traveler (http://www-01.ibm.com/support/docview.wss?uid=swg24019529). The Lotus Note
Traveler team attempts to stay on top of all the new device operating systems and levels that
are released. Because of this, when a new device code level is released, look to the
Recommended Maintenance - Lotus Notes Traveler
(http://www-01.ibm.com/support/docview.wss?uid=swg24019529) for the latest Lotus Notes
Traveler code to address the new device code levels.
9.1.3 Data filter settings
The data filter settings influences the amount of data that is synchronized between the
devices and the Lotus Notes Traveler server. By setting these parameters, you can avoid a
user tying up the resources when trying to synchronize large amounts of data.
These parameters are defined in the default device settings, and can be overwritten for a
certain user group by a dynamic security policy that can be implemented on the Domino
server. The Lotus Notes Traveler Server first uses a dynamic security policy if this is in place
for the particular user over the default device settings on the Lotus Notes Traveler server. If
there is no dynamic security policy in place for the user in question, the default device settings
is used.
To adjust the parameter value, select the Preferences tab and then the Filter Settings tab.
The default value is Unlimited, meaning that no filter is applied by the server. To set a filter
limit, enter a number in days for one of the following settings. While mobile device users can
set their filter limit lower than the defined maximum, anything higher will not be honored by the
server.
Chapter 9. Tuning and troubleshooting 377
Email filter limit
New mail older than the Email filter limit will not be synchronized with the device.
Past events filter limit
Calendar events older than the past events filter limit will not be synchronized with the
device. Note that recurring events that have an instance within the filter window will be
synchronized, even if they have instances that start earlier that the past events filter limit.
Future events filter limit
Calendar events in the future that occur beyond the future events filter limit will not be
synchronized with the device. Note that recurring events that have an instance within the
filter window will be synchronized, even if they have instances that occur beyond the future
events filter limit.
Journal filter limit
Journal entries modified earlier than the limit will not be synchronized to mobile devices
that support Journal sync. This is currently only supported in Windows Mobile devices.
9.1.4 Log level options
Log information is essential for monitoring server performance and troubleshooting. The more
information is collected, the more disk space is required and the more overhead is seen on
the Lotus Notes Traveler server. The base logging level for the Lotus Notes Traveler INFO. To
set the entire server to the INFO level for logging, run the tell traveler log level info command.
Modify the log level only if there is a reason for increased logging.
It is not recommended to set the logging level to FINEST for the server. Please only use
FINEST logging for a single user. Since this Wiki was created we have released Upgrade
Pack 2, and some additional information for log collection. Please reference this link
(http://www-10.lotus.com/ldd/dominowiki.nsf/xpDocViewer.xsp?lookupName=Administeri
ng+Lotus+Notes+Traveler+8.5.3+Upgrade+Pack+2#action=openDocument&res_title=Gatheri
ng_log_files_for_support_A853UP2&content=pdcontent)for this more current
documentation. The information in Upgrade Pack 2 Gathering log file support section
contents can be applied for Upgrade Pack 1 application.
9.1.5 Enterprise database
This section covers the hardware specifications and configuration parameters that can
influence the enterprise database performance.
Consider the following software and hardware specifications for the Lotus Notes Traveler
database server:
For large enterprise deployment, Use physical servers for the database servers
Place the data and transaction log volumes on separate storage hardware RAID LUNs.
Data and Transaction Log volumes must be able to support the sustained I/O
(Input/Output) operations per second (IOPs) required.
For a database server supporting up to 10,000 devices in a Lotus Notes Traveler Server
pool:
Use 8 processor cores, 32 GB memory, and 1,000 sustained IOPs.
Use a dedicated (not shared with other applications) hardware RAID 5 (or better) LUN
with 8 disks (8,000 to 10,000 devices) for the Lotus Notes Traveler database.
378 IBM Notes Traveler Hints and Tips for a Successful Deployment
Use a dedicated (not shared with other applications) hardware RAID 1 (or better) with 4
disks for transaction log.
The LUNs are dedicated, the storage system can be shared.
For up to 8,000 devices, 6 disks are needed for the LUN that the Lotus Notes Traveler
database uses.
Database servers should use DB2 HADR or Microsoft SQL for full HA (requires 2
database servers).
DB2 for Linux, UNIX, and Windows 9.7 FP5 or later and Microsoft SQL Server Enterprise
2008 R2 SP1 or later are required.
It is important to note that the storage system used for the database servers must be able to
support the SUSTAINED IOPs required. For example, if a high end storage such as the IBM
XIV Storage System is used, then configure the storage LUNs for the required sustained
IOPS.
DB2
The Lotus Notes Traveler DB2 database buffer pool can be set to 1- 2 GB based on available
physical memory on the server and the user load. As an example, for a Lotus Notes Traveler
pool supporting 8,000 devices, use a buffer pool up to 2 GB on a DB2 server running with
8-16 GB memory.
Consider the following DB2 database configuration parameters for a Lotus Notes Traveler
deployment:
LOGBUFSZ: Log buffer size, a good starting point to set this is 8192.
LOGFILSIZ: Log file size, A good starting point to set this is 8192.
MINCOMMIT: Number of commits to group, a good starting point to set this is 1.
LOGPRIMARY: Number of primary log files, a good starting point to set this is 120.
LOGSECOND: Number of secondary log files, a good starting point to set this is 10.
9.1.6 Network
Ideally, the Lotus Notes Traveler servers and the mail servers will all be located at the same
location. If the mail servers are located in a different location the latency may create a
bottleneck on the server.
9.1.7 User authentication
Go to the Internet Protocols, Domino Web Engine tab.
Review the Memory Caches section.
Chapter 9. Tuning and troubleshooting 379
The Maximum cached users field is used to store a users name, password, and a list of
groups that the user belongs to. A user is added to this cache after they successfully
authenticate with the Lotus Notes Traveler server. The default setting for this field is 64. If the
number of current authenticated users logged in exceeds this value, some performance
improvements may be gained by increasing the number of the Maximum cached users. To
review the current values, look at the statistics from a recent NSD file. As a general guideline,
when adjusting any of the "Domino.Cache.*.Count" statistics, they should be slightly less than
their "Domino.Cache.*.MaxSize" counterpart. In this case, the "Domino.Cache.User
Cache.Count" should be slightly less than the "Domino.Cache.User Cache.MaxSize". If the
value listed in the Domino.Cache.User Cache.Count is larger than the Domino.Cache.User
Cache.MaxSize, then try slowly incrementing the maximum value for the "Maximum cached
users", as shown in the Memory Cache section screen capture above, until the Count no
longer reaches the Maximum. Given the resources this value should be roughly 3 times the
number of users.
9.1.8 Transactional logging
Go to the Transactional Logging tab.
Disable Transactional Logging. The Lotus Notes Traveler server is not a typical server, as
there is very little writing to Domino databases. With the small number of writes necessary, it
is not necessary to enable Transactional Logging.
9.2 Problem determination guides
The following problem determination guides are updated regularly and can be helpful for you
if you are troubleshooting an issue with Lotus Notes Traveler:
Lotus Notes Traveler FAQ - http://www-01.ibm.com/support/docview.wss?uid=swg21450615
APAR Listing -
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Lotus_Notes_Traveler_APAR_listing
Performance and Tuning -
http://www.ibm.com/developerworks/lotus/library/notes852-trav-perf/index.html
https://idoc2.swg.usma.ibm.com/domino/index.jsp?topic=/com.ibm.help.lnt8532.doc/co
llecting_logs_for_ibm_support.html
380 IBM Notes Traveler Hints and Tips for a Successful Deployment
9.3 Troubleshooting techniques
IBM Lotus Notes Traveler Support provides the common issues with their solutions on FAQ
page for Lotus Notes Traveler
(http://www-01.ibm.com/support/docview.wss?uid=swg21450615). This site is updated
regularly and you can visit 9.3.2, Common user problems before opening a PMR with IBM
Support.
When you encounter a problem, check your Lotus Notes version and consider updating your
Lotus Notes Traveler to the latest code level for the release that you are running to eliminate
any problems that have already been addressed, and usually can get your server up and
running as quickly as possible. Because any code fixes for new problems that are found are
included on the latest code stream, you will most likely be asked to upgrade to the latest level
of the code to apply any fixes from IBM Support.
For the latest code releases, see Recommended maintenance page
(http://www-01.ibm.com/support/docview.wss?uid=swg24019529).
These sections describes the issues that you might experience with the server and from a
user perspective:
9.3.1 Server
Understanding high availability
Starting with Notes Traveler 8.5.3 Upgrade Pack 1 release, pooled Notes Traveler servers
balance the user load across the server pool. The load balancing algorithm is based on Notes
Traveler Availability Index (AI) plus biases.
Each active user is assigned to one Notes Traveler server in the pool. The user stays active in
the pool for 24 hours from last time the user device contacted the pool. This assigned server
monitors the user mail file for changes so that changes that need to be sent to the device will
be up to date when the devices connect to server next time.
On each request from the device the load balancer determines which is the best server to
handle the request. The best server is defined by comparing all of the servers relative AIs with
each other, and the server with the best relative AI becomes assigned server and handles the
request for that user. If a new server has a better AI including biases than the current
monitoring server, then the user is routed to the new server and that new server becomes the
new monitoring server.
The biases are determine by adding NTS_ROUTE_CURRENT_BIAS (default value of 20) to
the AI for the server that is current assigned to monitor the user and adding
NTS_ROUTE_LOCAL_BIAS (default value 10) to the server that has the current request from
the device.
The following table shows examples of different AIs (where 100 is 100% available) and how
the message was routed. In each example Server 1 is where the request was received and
Server 3 is the current monitoring server.
Chapter 9. Tuning and troubleshooting 381
Crashes
If you are experiencing a Lotus Domino/Traveler server crash, there are three major things
that are needed to assist you to identify the issue:
NSD logs capturing the crash, which can be found at:
\Lotus\Domino\data\IBM_TECHNICAL_SUPPORT\NSD.log
Javacore file is required if the crash / hang is caused by java code which can be found at:
\Lotus\Domino\javacore.txt
The Traveler logs, which can be found at:
\Lotus\Domino\data\IBM_TECHNICAL_SUPPORT\traveler\logs
Here we guide you, by an example, of the process for troubleshooting a server crash problem:
1. When Lotus Notes Traveler Server crashes, search "Panic" in the NSD log file
The following is a crash report example that caused by a bad document.
############################################################
### thread 116/119: [ nserver: 2c74: 2c44] FATAL THREAD (Panic)
### FP=0x300b6168, PC=0x77676eba, SP=0x300b6168
### stkbase=0x300c0000, total stksize=4194304, used stksize=40600
### EAX=0x0000d7ce, EBX=0x00000c4c, ECX=0x300b51b8, EDX=0xFFFFFFFDF80AE50
### ESI=0x00000000, EDI=0x00000000, CS=0x00000033, SS=0xFFFFFFF0000002B
### DS=0x00000000, ES=0x00000000, FS=0x00000000, GS=0xFFFFFFF00000000 Flags=0x00000287
############################################################
[ 1] 0x77676eba ntdll.ZwWaitForSingleObject+10 (4,300b84d8,300bb56a,300bb540)
[ 2] 0x7745c0b0 kernel32.WaitForSingleObjectEx+160 (c4c,0,0,c4c)
@[ 3] 0x00834cdb nnotes.FRSendCommandToService+1943 (300bb800,300bbb18,0,830fc4)
@[ 4] 0x008385c4 nnotes.OSRunExternalScript+5860 (4,0,2aaa084,3)
@[ 5] 0x00831df1 nnotes.FRTerminateWindowsResources+2277 (0,0,90b5a20,0)
@[ 6] 0x0083b58e nnotes.OSFaultCleanupExt+622 (0,83118b,150014,2aae1b0)
@[ 7] 0x0083c005 nnotes.OSFaultCleanup+29
(76F72505C3A4322,56C6946206D6172,F4C5C4D42495C73,96D6F445C737574)
@[ 8] 0x0085597a nnotes.OSNTUnhandledExceptionFilter+626 (300bea90,2a91164,300bfb00,4d)
@[ 9] 0x007c5a6c nnotes.Panic+856 (dc49780,2a93c9b,f8817e8,191c)
@[10] 0x100079df nserverl.ProcessMonitorTask+899 (6f550071,0,2c74,c2e0df4)
@[11] 0x10001b21 nserverl.Scheduler+969 (0,0,0,0)
@[12] 0x007d654e nnotes.ThreadWrapper+330 (0,0,0,0)
[13] 0x7744be3d kernel32.BaseThreadInitThunk+13 (0,0,0,0)
[14] 0x77656861 ntdll.RtlUserThreadStart+33 (0,0,0,0)
...
...
<@@ ------ Notes Data -> OS Data -> MM/OS Structure Information (Time 04:16:32) ------ @@>
Start Time = 09/20/2012 04:11:14 AM
Crash Time = 09/20/2012 04:15:24 AM
Domino Controller Enabled = 1
Domino Controller Current Log = dcntrlr201209200411.log
382 IBM Notes Traveler Hints and Tips for a Successful Deployment
Error Message = PANIC: Process C:\Program Files\IBM\Lotus\Domino\nTraveler.EXE (6428/0x191C)
has terminated abnormally
Note the crash time: Crash Time = 09/20/2012 04:15:24 AM
2. Now look at the javacore log file
1TISIGINFO Dump Event "gpf" (00002000) received
1TIDATETIME Date: 2012/09/20 at 04:14:55
Note the time: 2012/09/20 at 04:14:55
Check the 0section section.
3. Find the section: "0SECTION THREADS subcomponent dump routine". Look at the
current thread that was running when the server crashed (also known as "caused the
crash").
0SECTION THREADS subcomponent dump routine
NULL =================================
NULL 1XMCURTHDINFO Current thread
NULL ----------------------
3XMTHREADINFO "DS-11a4[4r1xGwAA][2][EFE7C8B7D48D83672879533E7664B0DE]"
J9VMThread:0x000000003C70E400, j9thread_t:0x00000000143DE280,
java/lang/Thread:0x000007FFEBC0A860, state:R, prio=5
3XMTHREADINFO1 (native thread ID:0x11A4, native priority:0x5, native policy:UNKNOWN)
3XMTHREADINFO3 Java callstack:
4XESTACKTRACE at
com/lotus/sync/dca/access/NativeAccess.jniConvertBodyToHtml(Native Method)
4XESTACKTRACE at
com/lotus/sync/dca/access/NativeAccess.convertBodyToHtml(NativeAccess.java:2705)
4XESTACKTRACE at
com/lotus/sync/dca/access/ContentStore.readDocument(ContentStore.java:4187)
4XESTACKTRACE at
com/lotus/sync/dca/fieldmap/Converter.exportDocGeneric(Converter.java:928)
4XESTACKTRACE at
com/lotus/sync/dca/fieldmap/Converter.exportDoc(Converter.java:403)
4XESTACKTRACE at
com/lotus/sync/dca/BackEndMonitor.getEntry(BackEndMonitor.java:1240)
4XESTACKTRACE at
com/lotus/sync/dca/BackEndMonitor.getDataItem(BackEndMonitor.java:897)
4XESTACKTRACE at
com/lotus/sync/dca/BackEndMonitor$1.Next(BackEndMonitor.java:837)
4XESTACKTRACE at
com/lotus/sync/caf/filters/OrderedResultsGetFilter.Next(OrderedResultsGetFilter.java:111)
4XESTACKTRACE at
com/lotus/sync/caf/filters/ToLongGUIDFilter.Next(ToLongGUIDFilter.java:102(Compiled Code))
4XESTACKTRACE at
com/lotus/sync/caf/filters/GetDataItemsObjectsFilter.Next(GetDataItemsObjectsFilter.java:56)
4XESTACKTRACE at
com/lotus/sync/caf/filters/GetActiveSyncAttachmentsFilter.Next(GetActiveSyncAttachmentsFilter.ja
va:146)
4XESTACKTRACE at
com/lotus/sync/caf/util/EnumWithCacheIterator.fill(EnumWithCacheIterator.java:86)
4XESTACKTRACE at
com/lotus/sync/caf/util/EnumWithCacheIterator.hasNext(EnumWithCacheIterator.java:99)
Chapter 9. Tuning and troubleshooting 383
4XESTACKTRACE at
com/lotus/sync/TSS/DBInt/CafDB.putResultRowsIntoRetrieveObject(CafDB.java:1652)
4XESTACKTRACE at com/lotus/sync/TSS/DBInt/CafDB.retrieveRecords(CafDB.java:2193)
4XESTACKTRACE at com/lotus/sync/TSS/DBInt/CafDB.retrieveRecords(CafDB.java:1859)
4XESTACKTRACE at
com/lotus/sync/TSS/DBInt/CoreDB.retrieveRecords(CoreDB.java:1442)
4XESTACKTRACE at
com/lotus/sync/TSS/DBInt/CoreDB.retrieveRecords(CoreDB.java:1406)
4XESTACKTRACE at
com/lotus/sync/TSS/CoreEngine/CoreEngine.retrieveRecords(CoreEngine.java:1094)
4XESTACKTRACE at
com/lotus/sync/TSS/CoreEngine/CoreEngine.processAction(CoreEngine.java:257(Compiled Code))
4XESTACKTRACE at
com/lotus/sync/TSS/CoreEngine/CoreEngine.processAction(CoreEngine.java:179(Compiled Code))
4XESTACKTRACE at
com/lotus/sync/TSS/QMgr/QMgrObserver.processAction(QMgrObserver.java:109(Compiled Code))
4XESTACKTRACE at
com/lotus/sync/TSS/QMgr/QMgrObserver.doWork(QMgrObserver.java:96(Compiled Code))
4XESTACKTRACE at
com/lotus/sync/TSS/Action/ActionMgrLocal2$HTTPActionMgrLocal.sendAction(ActionMgrLocal2.java:161
(Compiled Code))
4XESTACKTRACE at
com/lotus/sync/TSS/Action/ActionMgr.add(ActionMgr.java:195(Compiled Code))
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/tss/TSSSession.sendAction(TSSSession.java:3243)
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/tss/TSSSession.sendAction(TSSSession.java:3265)
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/tss/TSSSync.sendAction(TSSSync.java:4959)
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/tss/TSSSync.sendAction(TSSSync.java:4946)
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/tss/TSSSync.doRetrieve(TSSSync.java:2986)
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/tss/TSSSync.doRetrieve(TSSSync.java:3057)
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/tss/TSSSync.sendIterateToNextRecord(TSSSync.java:3149)
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/protocol/syncml/ds/server/RequestHandler.sendCommands(RequestHan
dler.java:1344)
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/protocol/syncml/RequestHandlerCommon.sendSyncBodyCommands(Reques
tHandlerCommon.java:1540)
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/protocol/syncml/RequestHandlerCommon.handleRequest(RequestHandle
rCommon.java:167)
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/protocol/syncml/SyncServletCommon.handleRequestBody(SyncServletC
ommon.java:478)
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/tss/TSSServlet.handleRequestBody(TSSServlet.java:174)
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/protocol/syncml/SyncServletCommon.handleRequest(SyncServletCommo
n.java:456)
384 IBM Notes Traveler Hints and Tips for a Successful Deployment
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/tss/TSSServlet.handleRequest(TSSServlet.java:152)
4XESTACKTRACE at
com/lotus/sync/TSS/SyncMLServer/protocol/syncml/SyncServletCommon.doPost(SyncServletCommon.java:
95)
4XESTACKTRACE at
com/lotus/sync/servlet/WorkManager$WorkerRunnable$1.run(WorkManager.java:1972)
4XESTACKTRACE at
com/lotus/sync/util/ThreadPoolThread.run(ThreadPoolThread.java:391(Compiled Code))
3XMTHREADINFO3 No native callstack available on this platform
We can now identify the crash is caused by the Lotus Notes Traveler thread ID (native
thread): "DS-11a4" from jniConvertBodyToHtml(Native Method) (first line in the stack).
4. Search in the Activity_logs file for the thread ID, DS-11a4 around the time that the crash
happened.
09/20 04:14:55.707] FINE
DS-11a4[4r1xGwAA][2][EFE7C8B7D48D83672879533E7664B0DE] CN=user
name/OU=organization unit/OU=organization unit/O=organization
CNotesDb.cpp.CNotesDb::GetAttachmentData#7035 Skipping this attachment b/c
already included in mime with host type(2304) or size==0, file name = 'mime.htm'
size = 61259 on NoteId=19506
The crash is found when Lotus Notes Traveler server is accessing a document
EFE7C8B7D48D83672879533E7664B0DE.
For more information about the Activity log, see Activity logs
(http://www-10.lotus.com/ldd/rbtravelerwiki.nsf/dx/9.2.4_Activity_logs).
5. Check SystemDump log file for the document information.
The SystemDump log file show that the server has already banned this document and no
further crashes will occur due to this "bad" document:
########## Banned Documents (Thu Sep 20 06:02:58 EDT 2012) ##########
Description: List of documents that have been banned.
EMail EFE7C8B7D48D83672879533E7664B0DE CN=user name/OU=organization
unit/OU=organization unit/O=organization
Some customers have reported an uncommon, but highly disruptive scenario in which a
particular Notes document is corrupted or contains non-standard content that will cause
the Domino Server API to crash the Lotus Traveler server when trying to process the
particular document. The problem is amplified by the fact that Lotus Traveler will detect the
failed sync and retry the document once restarted. The problem generally resolves itself
when the failing document is deleted by the end user, moved to a non-syncing folder, or
simply moves outside the filter window for the particular user. This is addressed by this
APAR for example:
LO70193 Server crash converting to html if document contains certain type of MIME
attachment.
For more information about SystemDump log, see Systemdump log
(http://www-10.lotus.com/ldd/rbtravelerwiki.nsf/dx/9.2.2_SystemDump_logs).
High processor usage
A high processor usage issue with the Lotus Notes Traveler server is usually attributed to a
lack of resources. When this occurs, you will noticed that the work requests are "backed up"
in the queue while other work is trying to be accomplished. The server might also busy in
Chapter 9. Tuning and troubleshooting 385
freeing some resources to allow for the processing to occur. Here we describe common
reasons why high processor usage might occur and ways to help resolve the problem.
HTTP threads are not set correctly
Lotus Notes Traveler devices utilize Lotus Domino web server HTTP threads when
communicating with the server. If the number of active HTTP threads is insufficient, the
following problems might occur:
Apple device users might experience "Cannot connect to server" messages or slow
responsiveness when opening, sending, or synchronizing email, contacts, or calendar
items and when downloading email attachments
Other device users might see error 503 (Server busy) messages in the Lotus Notes
Traveler client interface, experience sync failures, and general slow responsiveness
Server processor and memory utilization might increase to abnormal levels.
How to determine the number of active HTTP threads needed for Lotus Notes
Traveler
The number of active HTTP threads needed for Traveler is calculated with the following
formula:
1.2 x Number of registered devices = Number of needed active HTTP threads
How to determine the number of Notes Traveler devices
At the Domino console on the Lotus Notes Traveler server, run the following command:
tell traveler stat show
In the output displayed by the command, find Push.Devices.Total, which is the total number of
devices registered with the server.
For example:
Push.Devices.Total = 225
This indicates that 225 devices are registered for synchronization with the Notes Traveler
server. This number of devices indicates that at least 270 HTTP threads are needed (1.2 x
225 = 270).
If the console output is scrolling too quickly to find this information, the info can be dumped to
a file by doing the following:
1. Run the console command tell traveler systemdump stat
2. Open \data\IBM_TECHNICAL_SUPPORT\traveler\logs\dumps\systemdump.log
3. Search for Push.Devices.Total
How to determine the current number of active HTTP threads and where to set this
The current number of active HTTP threads allocated by the Domino web server at start time
can be found in the Server document on the Internet Protocols --> HTTP tab in the "Number
active threads" field.
The Lotus Notes Traveler database might be fragmented
While fragmentation should not be much of a problem in 8.5.3 Upgrade Pack 1 and later
versions of the product, it does not hurt to ensure this is running smoothly.
386 IBM Notes Traveler Hints and Tips for a Successful Deployment
How to set the defrag to run on startup intervals
1. Add NTS_DEFRAG_INTERVAL_DAYS to the notes.ini parameter. For example, to set
interval of 30 days add:
NTS_DEFRAG_INTERVAL_DAYS=30
2. Restart the Lotus Traveler server. From that point on, if Lotus Traveler server is restarted
and it has been 30 days since the last defrag, then the defrag operation will run.
3. To force a defrag to run, delete the parameter NTS_LAST_DEFRAG from the notes.ini file
and restart the server. If NTS_DEFRAG_INTERVAL_DAYS is set and there is no last
defrag timestamp, then the server will perform a defrag and reset the timestamp.
How to manually run defrag
1. Shutdown the Lotus Notes Traveler and the Domino HTTP tasks on the server by running
the following commands:
tell traveler quit
tell http quit
2. Be sure that both the HTTP and the Lotus Notes Traveler process are completely stopped.
3. Start the Lotus Notes Traveler using the defrag parameter:
load traveler -defrag
4. The defrag command runs when the Lotus Note Traveler Server starts. The server will
start normally after the defrag operation completes.
Note that the defrag operation might take more than 30 minutes to complete depending on
database size and system capabilities.
5. If the Domino HTTP task is not started automatically by Lotus Notes Traveler, then start
HTTP manually.
Load HTTP.
Memory issues
You can see the memory usage by running tell traveler mem show.
This output similar to this:
Java garbage collection does not take place until about 95% of the memory is used. If the
memory continues to stay high for a sustained period of time, consider the following to
address memory usage issue:
Be sure that you are on the latest level of code for the release that you are on. You can find
the latest levels of code at Recommended maintenance page. The memory leak issue
might have addressed already.
Chapter 9. Tuning and troubleshooting 387
You can increase the memory that the Lotus Notes Traveler process can access. You can
modify the memory size setting on the "Lotus Traveler" tab of the server document.
Note for Linux platform: Do not give more than 2GB memory size for a Linux system. This is
because there is currently only a 32-bit version of Domino code. Thus, the 32-bit Java
libraries are used and they are restricted to 32-bit memory constraints. If you increase is
much larger than 2 GB, the Lotus Notes Traveler server will not start.
Network concerns
You can detect the connection to the servers from Lotus Notes Traveler with the Domino trace
command:
trace
This command allows you to ensure that the servers can connect to each other and give you
an idea of the connection speed.
Even the best configured system can encounter difficulties on a problematic network.
Unfortunately "network problems" can be among the most difficult to diagnose. Because of
their complexity, network conditions are often the last consideration in troubleshooting and
debugging. Some things to take into consideration when designing your Lotus Notes Traveler,
or looking for problems.
Naming Conventions
Naming schemes and problems are often found at the root of "network problems." So audit
your naming and addressing schemes and check the following:
Server configuration documents - server documents, connection documents, and son on.
Host files - If present, check for them, because a host file will override any name servers.
DNS accuracy - does the name resolve to the expected address?
DNS availability - can the system reach its DNS server reliably?
Log files - to see what names were used to reach the systems in question.
Ensure that you use consistent names, for example, fully qualified domain name (FQDN)) for
all servers in your deployment, and that those names are consistently resolved across your
enterprise.
Latency
Latency (that is, delay in transit) is a common problem in wide-area network (WAN)
environments when it comes to Lotus Notes Traveler. For example, if a mail server is not
located in the same network center, but rather in another center across the country or on
another continent, the latency will cause long running HTTP threads. If there are too many of
these, it may slow down the other connections as well. This characteristic of network traffic
can best be measured by packet captures (using a tool such as Sniffer, WireShark, or
Surveyor) taken at either endpoint of the connection. Most network analysis software can
calculate latencies, in terms of both "average" latency and "latency since previous packet."
Some latency is to be expected in wide-area networking. Isolating the point at which the
latency is introduced may require multiple packet capture sessions, in which captures are
taken from different points on the client-to-server network path; you have to engage your
networking team for assistance in this activity.
388 IBM Notes Traveler Hints and Tips for a Successful Deployment
Important note: The timing statistics of ping, traceroute and similar commands, while helpful,
are not a proper measure of network latency. Those commands use a protocol (ICMP/IP)
which is not subject to the same handling and prioritization as TCP/IP packets. In fact, most
network infrastructure equipment, when under congestion, discards any or all ICMP packets
before it discards any TCP packet. Therefore, those commands, in most circumstances,
indicate conditions that are more negative than those experienced by your "real" TCP/IP
connections. Use these commands to indicate overall connectivity (that is "How are my
packets getting to the server?"), but do not use their timing results for latency analysis in a
congested network.
The following are tools that can help troubleshooting network issues:
1. Server diagnostics and statistics
Domino statistics include various network statistics, including per-connection and
by-session information. See your Domino documentation for more information.
The netstat command supports per-protocol statistics (check your OS documentation
for the proper options), which can include packets retransmitted, packets sent and
received, and the like.
2. Network Analysis software
WireShark is a freeware packet capture and analysis package; it is available for
download from http://www.wireshark.org.
The netstat command provides limited statistics on general network traffic issues.
Network conditions can have a significant impact upon your Lotus Notes Traveler
performance. It is essential that you partner with your networking team to understand the
general layout of your enterprise network, identify potential "hot spots", and gain an
understanding of your network's "normal" performance level.
9.3.2 Common user problems
Though most of the issues that a user experiences when using the product are on the server
side, there are a few that can be resolved from the device.
Read and unread marks are not sent
There are two reasons why the read and unread marks are not set:
Unread replication is not enabled
Unread replication is enabled for each user automatically by the Lotus Notes Traveler
server so that unread marks synchronize correctly with the device. To activate unread
replication manually, perform the following procedure:
1. From the Domino Administrator, click the Files tab.
2. Select the databases for which you are enabling the replication of unread marks.
3. From the Tools panel, click Database -- Advanced Properties.
4. Click Select and then Replicate unread marks.
5. To enable replication of unread marks for the selected databases across all servers, click
All servers.
6. To enable replication of unread marks for any cluster containing a replica of the database,
click Clustered server only.
7. Click OK.
Chapter 9. Tuning and troubleshooting 389
This issue is described in Infocenter reference
(http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Enabling_syncing_of_read_or_unre
ad_changes_A853UP1).
The read and unread marks are not synchronized "immediately" from devices when an
email is read.
Whenever an email is read from the device, Lotus Notes Traveler application flags the
email as been read, and keeps track of this from the device perspective. On the next
"significant sync", Lotus Notes Traveler application sends all of these flags to the server.
A "significant sync" means either sending and email, retrieving an email, deleting an
email, or a manual synchronization performed by the user (pushing the "sync now"
button). The reason for this is to keep the amount of data transfer to a minimum and not to
synchronize data that can be batched up and sent as one package at a time and
implement multiple things in the mail file. This is to keep performance high in the server
and limit the bandwidth that is needed for communication.
If a user would like these read and unread marks to come across immediately, just perform
a manual synchronization, or send, receive, and delete an email.
Emails not being sent or received
This is common when the system is taxed for resources. Review the sections for "High CPU"
and "Memory concerns" in the 9.4.1 Server to fix this issue.
Multiple calendar entries are on the device
There can be an issue with the IDs that are assigned to the entries that are maintained within
the device database if there have been issues in the communication with the server that
cause these to be duplicated. The way to fix this on an Android device is to go to the Lotus
Traveler application on the device, and press the menu button. Select Tools from there and
choose Replace the data on the device. Select Replace to replace the calendar data and
re-synchronize the device.
Multiple emails are on the device
There can be an issue with the IDs that are assigned to the entries that are maintained within
the device's database if there have been issues in the communication with the server that
cause these to be duplicated. The fix this problem in an Android device, go to the Lotus
Traveler application on the device, and press the menu button. Select Tools from there and
choose Replace the data on the device. Select Replace to replace the email data and
re-synchronize the device.
Device fails to connect to the server
This is usually due to the server being unresponsive and is usually due to a memory or high
processor situation occurring on the server. Review the sections for "High CPU" and "Memory
concerns" in the 9.4.1 Server section to fix this.
DA Domain error 0 on an Apple device
This happens when a new user is trying to setup Lotus Notes Traveler on a new Apple device.
This is caused usually by the OPTIONS HTTP method being blocked to the Lotus Traveler
Server.
You can detect if the OPTIONS method is getting through to the server by enabling HTTP
debug threads. To do this, run this command on the console:
tell http debug thread on
390 IBM Notes Traveler Hints and Tips for a Successful Deployment
(tell http debug thread off turns this debugging off.)
This command causes htthr* files to be written to the IBM_TECHINCAL_SUPPORT directory.
When looking at these files after an Apple user has tried to log in and set up a device, you will
see something similar to this in the file:
*** New Request -- Parse and Check Request: Session 6069, Thread e30, Clock 1752574875
OPTIONS /Microsoft-Server-ActiveSync HTTP/1.1
Host: 9.37.30.206
User-Agent: Apple-iPad2C1/902.206
Content-Length: 0
Accept: */*
X-MS-PolicyKey: 0
Authorization: ****************
Accept-Language: en-us
Accept-Encoding: gzip, deflate
Connection: keep-alive
*** Process Request: Session 6069, Thread e30, Clock 1752574891
*** Client IP Address [9.27.49.215], Server IP Address [9.37.30.206]: Session 6069, Thread e30,
Clock 1752574891
*** Start Request Step: Session 6069, Thread e30, Clock 1752574906
*** Raw Request Step: Session 6069, Thread e30, Clock 1752574906
*** Create Sub Request: Session 6069, Thread e30, Clock 1752574906
*** End Request Step: Session 6069, Thread e30, Clock 1752574906
*** Process Request: Session 6069, Thread e30, Clock 1752574906
*** Client IP Address [9.27.49.215], Server IP Address [9.37.30.206]: Session 6069, Thread e30,
Clock 1752574906
OPTIONS /traveler/Microsoft-Server-ActiveSync HTTP/1.1
Host: 9.37.30.206
User-Agent: Apple-iPad2C1/902.206
Content-Length: 0
Accept: */*
X-MS-PolicyKey: 0
Authorization: ****************
Accept-Language: en-us
Accept-Encoding: gzip, deflate
Connection: keep-alive
*** Start Request Step: Session 6069, Thread e30, Clock 1752574922
*** Raw Request Step: Session 6069, Thread e30, Clock 1752574922
*** Pre Authenticate Step: Session 6069, Thread e30, Clock 1752574938
*** Authenticate Step: Session 6069, Thread e30, Clock 1752574938
*** Post Authenticate Step: Session 6069, Thread e30, Clock 1752574938
*** Get Group List Step: Session 6069, Thread e30, Clock 1752574938
*** Authorized Server Access Step: Session 6069, Thread e30, Clock 1752574938
*** Translate Step: Session 6069, Thread e30, Clock 1752574938
*** Post Translate Step: Session 6069, Thread e30, Clock 1752574938
*** Authorized Step: Session 6069, Thread e30, Clock 1752574938
*** Process Request for User CN=t u2/O=munse: Session 6069, Thread e30, Clock 1752574938
*** Calling Url Cache Process Request: Session 6069, Thread e30, Clock 1752574953
*** Calling Inotes Process Request: Session 6069, Thread e30, Clock 1752574953
*** Post write Buffer, bytes [679]: Session 6069, Thread e30, Clock 1752574953
Chapter 9. Tuning and troubleshooting 391
HTTP/1.1 200 OK
Date: Tue, 02 Oct 2012 19:38:44 GMT
Set-Cookie: SessionID=DA950FBRD9; path=/
Cache-Control: no-store
Server: Lotus-Domino
Cache-Control: private
Allow: OPTIONS,GET,POST
Public: OPTIONS,GET,POST
Vary: Accept-Encoding
MS-ASProtocolVersions: 2.5,12.0,12.1
MS-ASProtocolCommands:
Sync,SendMail,SmartForward,SmartReply,GetAttachment,GetHierarchy,CreateCollection,DeleteCollecti
on,MoveCollection,FolderSync,FolderCreate,FolderDelete,FolderUpdate,MoveItems,GetItemEstimate,Me
etingResponse,Search,Settings,Ping,ItemOperations,Provision,ResolveRecipients,ValidateCert
MS-Server-ActiveSync: 8.1
Content-Type: application/vnd.ms-sync.wbxml
Content-Length: 0
*** Returned from Process Request, Request Processed: Session 6069, Thread e30, Clock 1752574953
*** End Request Step: Session 6069, Thread e30, Clock 1752574953
*** Log Request: Session 6069, Thread e30, Clock 1752574953
If you do not see this present in the htthr files for your incoming Apple device, OPTIONS is
either blocked or not enabled. To solve this problem, first, ensure that there is not a proxy in
place in front of the server that is not allowing OPTIONS to be passed through to the server.
This is the common problem.
If you are using internet site documents on your server, you must allow for the OPTIONS
method to be passed through to the server. To do this, follow these steps:
1. Open the Internet site document for Web Protocol in edit mode.
2. Click Basic.
3. Either set the "Use this web site" to handle requests which cannot be mapped to this site
to Yes, or set the Host names or addresses mapped to this site with the host name that the
Lotus Notes Traveler client uses to connect to this server.
4. Click Configuration.
5. Optional: Set Home URL to /traveler if you want the Lotus Notes Traveler user home page
to be the default site for this server.
6. For Allowed Methods, select GET, POST, and OPTIONS.
7. Restart the HTTP server.
392 IBM Notes Traveler Hints and Tips for a Successful Deployment
Copyright IBM Corp. 2013. All rights reserved. 393
Chapter 10. Appendix A
In this appendix, we walk through the systemdump log. This can be used to provide an
overview of the system configurations and status of the server. The below is an example of
what you would see in a systemdump from 8.5.3 upgrade pack 1. Depending on the settings
that are in place, some different information will be displayed. Please use the below as an
example and observe some of the annotations that were made within the systemdump.
This example contains the following basic information:
Two users: "t u1" and "t u3"
Server IP address: 9.37.30.206
External server URL: "http://9.37.30.206/traveler"
Organization: "organization"
Domain: "domain."
A 32-bit system is use for testing purposes only.
The comments are in bold.
10
394 IBM Notes Traveler Hints and Tips for a Successful Deployment
IBM Lotus Notes Traveler Server system dump
This section of the systemdump shows the versions of the software that are installed on the
machine. It also denotes the database connection URL, as you see here that this is
configured to DB2 from this entry in the section: Database Connection URL:
jdbc:db2://chevy.rtp.raleigh.ibm.com:50000/trvlrdb
You can see the time the server was started, how long the server has been up, and any
systemdump options that were supplied with the command to generate the systemdump.
############### IBM Lotus Notes Traveler Server system dump (Wed Sep 05 12:29:03 EDT 2012)
###############
Domino Version: Release 8.5.3|September 15, 2011
Domino Platform: Windows/32
Domino Install Type: Domino Enterprise Server License (4)
Domino Server Name: 9.37.30.206/organization
Database Connection URL: jdbc:db2://chevy.rtp.raleigh.ibm.com:50000/trvlrdb
Current Time (Local): Wed Sep 05 12:29:03 EDT 2012
Current Time (GMT): Wed Sep 05 16:29:03 GMT 2012
Lotus Notes Traveler Started: Wed Sep 05 11:28:55 EDT 2012 (running for 0 days, 1 hours, 0
minutes, and 8 seconds)
System Dump options: [status, java, configuration, threads, threaddata, stat, push, security,
sync, banneddoc, mailreplicas, database, dbconfig, ha]
Status (Wed Sep 05 12:29:03 EDT 2012)
This section shows the status of the server (Green, Yellow, or Red), a processor snapshot,
and memory usage of the server. The Status messages are configurable parameters and are
defined at this URL.
If your server is configured for high availability, the Availability Index is also given. The
Availability Index is a number where the value is anywhere from 100 to -200. The value of this
is defined as follows:
The number begins with 100, and then the resources are taken into account. The CPU
usage is subtracted, as well as the memory usage. From a user's perspective when
accessing the server pool, they are given a +10 to the last server they accessed within the
pool. A value of 100 is very available and a value of -200 is very unavailable.
The CPU snapshot is taken every 15 minutes with a cache size of 100 which provides 24
hours of data. This can be configured with adding or changing the following notes.ini
parameters:
NTS_CPU_UTILIZATION_CACHE_SIZE = 100 <- This is the cache size
NTS_CPU_UTILIZATION_INTERVAL = 900 <- This is the interval to take the snapshot in
seconds.
The following message snippets are from the Status section.
Current CPU Utilization: CPU running at 0.00 pct over 3.546 Secs
CPU and Memory (MB) Usage History
Date CPU Pct Java Mem C Mem Avl Indx # Users # Errors
2012-09-05 11:44:00 EDT 0.22 26 858 100 2 0
2012-09-05 11:59:00 EDT 0.01 28 892 100 2 0
Chapter 10. Appendix A 395
2012-09-05 12:14:00 EDT 0.01 29 920 100 2 0
2012-09-05 12:29:00 EDT 0.02 30 960 100 2 0
The CPU and memory usage history shown here are the snapshots used in the average.
These snapshots are taken of the memory and CPU every 15 minutes, as can be seen by the
"Date" column.
Memory Usage:
Java Memory Usage <---- This is the total memory that is used by the Lotus Notes Traveler
process.
Max Total 512 MB <---- This is the maximum memory as configured on the Lotus Traveler tab
of the server document.
Current Total 96 MB
Free 481 MB (94 percent of Max Total) <---- The amount of free memory of the maximum
allocated memory.
Allocated 31 MB (6 percent of Max Total) <---- The used memory of the maximum allocated
memory.
C Memory Usage <---- This is the total amount of allocatable memory on the machine.
Total Virtual 2047 MB
Total Physical 2047 MB
Allocated 961 MB (48 percent of Total Physical)
Current Usage < <---- This is a summary of the above values.
Java 31 MB
C 961 MB
Starting with Notes Traveler 8.5.3 Upgrade Pack 1 release pooled Notes Traveler servers will
load balance users across the server pool. The load balancing algorithm is based on Notes
Traveler Availability Index (AI where 100 is 100% available) The AI is roughly calculated by
this algorithm: 100 - the CPU being used - the percent of memory being used (after a
threshold has been reached).
Avaiability Index:
Availability Index: 100
Status: Green
Initial native memory usage: 757
These are some of the work queues that Lotus Notes Traveler uses for internal processing.
-- WorkMgr-DelQ --
DelayQueue (Name: WorkMgr-DelQ, Size: 0 object(s), Head: null, Current Date: Wed Sep 05 12:29:03
EDT 2012)
obj2DqeMap (Object To DelayQueueElement Map) (0 objects sorted by dequeue time)
-- BusySig --
DelayQueue (Name: BusySig, Size: 0 object(s), Head: { dequeues at 1346859539254 [2012-09-05
11:38:59.254 EDT], enqueued at 1346859309254 [2012-09-05 11:35:09.254 EDT], BusySession:
sess-CN=t u3/O=organizationAppl1B017URA75JsyncASSyncEmail4 slowsync-false key-2 busyCount-0
app-Email collection-4 time-1346859309254(3234381ms ago at Wed Sep 05 11:35:09 EDT 2012) },
Current Date: Wed Sep 05 12:29:03 EDT 2012)
obj2DqeMap (Object To DelayQueueElement Map) (0 objects sorted by dequeue time)
396 IBM Notes Traveler Hints and Tips for a Successful Deployment
Java Dump (Wed Sep 05 12:29:03 EDT 2012)
This section denotes when the last Java dump was made, and where this file is located.
The following are log snippets of the Configuration sections.
########## Configuration (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: List of the current configuration values in use by the Lotus Notes Traveler server
based on the Lotus Traveler server document tab and any notes.ini overrides.
The complete notes.ini file is also included.
All configuration values:
-------------------------
ADMINP_POLL_INTERVAL = 0
DEBUG_OUTFILE = ""
LOGFILE_DIR = ""
NTS_64_BIT = false
NTS_ACCESS_ALLOW = "" <---- These are the users allowed access to the Lotus Notes Traveler
server on the Lotus Traveler tab in the server document.
NTS_ACCESS_DENY = "" <---- These are the users not allowed access to the Lotus Notes Traveler
server on the Lotus Traveler tab in the server document.
NTS_ACCESS_ENABLED = true
NTS_64_BIT = false <---- Indicates that the server is not a 64-bit machine.
NTS_ACCESS_ALLOW = "" <---- Shows the groups and users that are set to allow access to the
Lotus Notes Traveler server on the Lotus Traveler tab of the server document.
NTS_ACCESS_DENY = "" <---- Shows the groups and user that are set to deny access to the
Lotus Notes Traveler server on the Lotus Traveler tab of the server document.
NTS_ACCESS_ENABLED = true" <---- Grants access to the Lotus Notes Traveler server.
The parameters that begin with NTS_ACTION are parameters that should not be touched.
These parameters are used when the servlets interact with the device:
NTS_ACTION_CHECKFORUPDATE = true
NTS_ACTION_COMMAND = true
NTS_ACTION_DELETEIDFILE = true
NTS_ACTION_GETATTACHMENT = true
NTS_ACTION_GETATTACHMENT_AS = true
NTS_ACTION_SETSECURITY = true
NTS_ACTION_SYNC = true
NTS_ACTION_SYNC_AS = true
NTS_ACTION_UPLOAD = true
NTS_ADDRESSCACHE* entries are used to cache objects that are expensive to retrieve or
create and are long lasting. Typically, that is going to be information retrieved from the user's
mail database that stays constant most of the time, for example, the access control list (ACL)
on their database, the device profiles and preferences and their home mail server information.
In this example, NTS_APPLE_ENCRYPT_ENABLED = true indicate that this server allows
for encrypted emails to be sent to Apple devices.
NTS_ADDRESSCACHE_ENABLED_ANDROID_MAIL = true
NTS_ADDRESSCACHE_ENABLED_AS_CALENDAR = true
NTS_ADDRESSCACHE_ENABLED_AS_CONTACTS = true
NTS_ADDRESSCACHE_ENABLED_AS_MAIL = true
Chapter 10. Appendix A 397
NTS_ADDRESSCACHE_ENABLED_SYM_MAIL = true
NTS_ADDRESSCACHE_ENABLED_WM_MAIL = true
NTS_ADDRESSCACHE_ENCODING_ENABLED_AS = true
NTS_ADDRESSCACHE_EXPINTERVAL = 30
NTS_ADDRESSCACHE_LIFETIME = 1440
NTS_ADDRESSCACHE_MAX_ENTRIES = 10000
NTS_ADMIN_DIR_CAT_EXT = "" (ext = "")
NTS_APPLE_ENCRYPT_ENABLED = true
NTS_AS* are parameters that work with Active Sync sessions.
NTS_AUTOSTART_HTTP = true <---- If true, Lotus Notes Traveler will start or restart the HTTP
server as needed at run time to ensure proper functionality. If false, it is up to the Domino
Administrator to ensure HTTP starts correctly, usually done by adding HTTP to the ServerTasks
list in the notes.ini file.
NTS_AUTO_CONFIG = true <---- If set to true, the Lotus Notes Traveler server configures the
HTTP server during startup. This value is assumed to be true unless set to false.
NTS_AUTO_DBSCHEMA = true <---- Tells the system the Lotus Notes Traveler database its objects
were created. This happens after the first Lotus Notes Traveler server is added to the HA
pool's database. If adding another server to the HA pool after the first was added.
NTS_AS_ALLOW_DS_CHANGES = true
NTS_AS_ALLOW_DS_FOLDER_CHANGES = true <---- Allows the device to make folder changes.
NTS_AS_ALLOW_INVITATIONS = true <---- Allows the device to send invitations.
NTS_AS_BDAY_SHIFT = 12
NTS_AS_IGNORE_DS_CONTACT_UPDATES_LIMIT = 50
NTS_AS_MAX_COMPRESSABLE_BODYSIZE_APPLE_2X = 256000
NTS_AS_MAX_RETRIEVE_COUNT = 15
NTS_AS_PROTOCOL_COMMANDS =
"Sync,SendMail,SmartForward,SmartReply,GetAttachment,GetHierarchy,CreateCollection,DeleteCollect
ion,MoveCollection,FolderSync,FolderCreate,FolderDelete,FolderUpdate,MoveItems,GetItemEstimate,M
eetingResponse,Search,Settings,Ping,ItemOperations,Provision,ResolveRecipients,ValidateCert"
NTS_AS_PROTOCOL_VERSIONS = "2.5,12.0,12.1"
NTS_AS_PROVISION_EXEMPT_USER_AGENT_REGEX = ""
NTS_AS_PROVISION_THROTTLE_TIME = 10
NTS_AS_REQUEST_TIME_LIMIT_APPLE_2X = 50
NTS_AS_REQUEST_TIME_LIMIT_APPLE_3X = 230
NTS_AS_REQUEST_TIME_LIMIT_APPLE_4X = 230
NTS_AS_REQUEST_TIME_LIMIT_APPLE_5X = 230
NTS_AS_REQUEST_TIME_LIMIT_DEFAULT = 50
NTS_ATTACHMENT_HOOK = ""
NTS_ATTACHMENT_HOOK_ADMIN_MAX = ""
NTS_AUTHWRAPPER_DEVICEATTACHSIZE = 100
NTS_AUTHWRAPPER_MAXATTACHMENTSIZE = 4000
NTS_AUTHWRAPPER_PREFERENCEACCESSORCLASS = "com.lotus.sync.caf.auth.DominoPreferenceAccessor"
NTS_AUTHWRAPPER_USERACCESSORCLASS = "com.lotus.sync.caf.auth.UserAccessorDomino"
NTS_BANNED_DOC_DUMP = false <---- Indicates that a DumpDoc will not be performed each time a
document is banned.
NTS_BANNED_DOC_LIMIT = 2 <---- Allow up to 3 crashes (one to turn on doc_sync, one to
increment to 1, third crash > 1 ). A value of "0" means disable this.
NTS_BANNED_DOC_SYNCS = 3 <---- Shows the number of synchronization after a crash or take
over to track documents.
NTS_CLIENT_CONFIG_DEFAULT_LOGON_NAME = "ILNT_Address_Internet" <---- Shows the default
logon ID.
NTS_CLIENT_CONFIG_DEFAULT_MAIL_ADDRESS = "ILNT_Address_Internet" <---- Shows the default
email address.
398 IBM Notes Traveler Hints and Tips for a Successful Deployment
NTS_CONSTRAINT_DB_CONNECTION_ENTRY = 280 <---- Shows the constraint entry level for the
number of database connections.
NTS_CONSTRAINT_DB_CONNECTION_EXIT = 224 <---- Shows the constraint exit level for the number
of database connections (80% of entry).
The parameters that begin with NTS_BACKENDMANAGER* define the setup of the
back-end database.
NTS_BACKENDMANAGER_APPL_QUEUE_SIZE = 40000
NTS_BACKENDMANAGER_DEFAULT_TEMPLATE = "StdR6Mail"
NTS_BACKENDMANAGER_ENABLEINVITATIONS = true
NTS_BACKENDMANAGER_MAP_DIR_DB = "C:/IBM/Lotus/Domino/data/traveler\map\MapDir.nsf"
NTS_BACKENDMANAGER_MAP_DIR_DB_CUSTOM =
"C:/IBM/Lotus/Domino/data/traveler\map\custom\MapDir.nsf"
NTS_BACKENDMANAGER_REMOVECONTENTWHENPREVENTCOPYING = true
NTS_BACKENDMANAGER_SET_UNREAD_REPLICATION = false
NTS_BACKENDMANAGER_SUPPORT_DOWNLEVEL_DOMINO_SERVERS = false
NTS_BACKENDMANAGER_URI = "http://"
NTS_BACKENDMONITOR_NUMBER_OF_ITEMS = 5
NTS_BACKENDMONITOR_URI = "http://"
NTS_BVT = false
NTS_CLIENT_CONFIG_INCLUDE_APPLE_COOKIE_DICT = true
NTS_CLIENT_UPDATE = ""
NTS_CMP_USER = false
NTS_CMP_USER_EXEMPT_EXT = "" (ext = "")
NTS_COMPANION_MINIMUM_VERSION = "2.0.5"
NTS_COMPANION_POLICY = ""
NTS_CONFIG_REFRESH_INTERVAL = 60
NTS_CONTENTMANAGER* are used for mappings and should not be modified.
NTS_CPU_UTILIZATION_CACHE_SIZE = 100 <---- Shows the cache of CPU entries that are kept for
determining the CPU utilization.
NTS_CPU_UTILIZATION_INTERVAL = 900 <---- Shows the interval in seconds that the CPU stats
are updated (default 15 minutes).
NTS_CONTENTMANAGER_MAPSOURCE_1 = "UNFILED"
NTS_CONTENTMANAGER_MAPSOURCE_2 = "TASKS"
NTS_CONTENTMANAGER_MAPSOURCE_3 = "EVENTS"
NTS_CONTENTMANAGER_MAPSOURCE_4 = "INBOX"
NTS_CONTENTMANAGER_MAPSOURCE_5 = "OUTBOX"
NTS_CONTENTMANAGER_MAPSOURCE_6 = "DRAFT"
NTS_CONTENTMANAGER_MAPSOURCE_7 = "DRAFTS"
NTS_CONTENTMANAGER_MAPSOURCE_8 = "SENT"
NTS_CONTENTMANAGER_MAPSOURCE_9 = "SENT ITEMS"
NTS_CONTENTMANAGER_MAPTARGET_1 = "@UNFILED"
NTS_CONTENTMANAGER_MAPTARGET_2 = "@UNFILED"
NTS_CONTENTMANAGER_MAPTARGET_3 = "@UNFILED"
NTS_CONTENTMANAGER_MAPTARGET_4 = "Inbox"
NTS_CONTENTMANAGER_MAPTARGET_5 = "Outbox"
NTS_CONTENTMANAGER_MAPTARGET_6 = "Drafts"
NTS_CONTENTMANAGER_MAPTARGET_7 = "Drafts"
NTS_CONTENTMANAGER_MAPTARGET_8 = "Sent Items"
NTS_CONTENTMANAGER_MAPTARGET_9 = "Sent Items"
NTS_CUSTOM_CLASSES = ""
Chapter 10. Appendix A 399
NTS_DB2* are settings that are for DB2 HADR Information.
NTS_DB2_ADMINBUFFERPOOL = "TRAVELERADMINBP"
NTS_DB2_ADMINTABLESPACE = "TRAVELERADMINTS"
NTS_DB2_ALT_PORT = ""
NTS_DB2_ALT_SERVER = ""
NTS_DB2_BUFFERPOOL = "TRAVELERBP"
NTS_DB2_SCHEMA = ""
NTS_DB2_TABLESPACE = "TRAVELERTS"
NTS_DB* are the settings for the database that is being accessed by Lotus Notes Traveler.
NTS_DBCONNECTIONDEATHINTERVAL = 21600
NTS_DBDRIVERCLASS = "com.ibm.db2.jcc.DB2Driver" <---- This is the database
driver being used.
NTS_DBMAXPOOLSIZE = 600 <---- This is the database connection pool size.
NTS_DBPAGECACHESIZE = 1000 <---- This is the database cached size.
NTS_DBPASSWORD_RESET = ""
NTS_DB_FORCE_SNAP_ISO = true
NTS_DB_ITEM_BATCH = 15
NTS_DEBUG* are settings for debugging the Lotus Notes Traveler server and should not be
changed unless instructed by support.
NTS_DEBUG = false
NTS_DEBUG_DOMINO_OBJECTS_STATS = false
NTS_DEBUG_DOMINO_OBJECTS_STATS_TRACE = false
NTS_DEBUG_EMMA_COVERAGE_FILE_HTTP = ""
NTS_DEBUG_EMMA_COVERAGE_FILE_TASK = ""
NTS_DEBUG_FUTURE_VERSION = false
NTS_DEBUG_NATIVE = false
NTS_DEBUG_NATIVE_MEMORY = 2048
NTS_DEBUG_ROUTE_AI_OFFSET = 0
NTS_DEFRAG_INTERVAL_DAYS <--- Shows the threshold of when to defragment the
server. "0" is off.
NTS_DEFRAG_ONCE = 0
NTS_DERBY* are settings used for the Lotus Notes Traveler server in stand-alone mode and
are defined in the cloudscape.properties file.
NTS_DERBY_DERBY_LOCKS_MONITOR = "true"
NTS_DERBY_DRDA_TRACE_ALL = "false"
NTS_DERBY_INFOLOG_APPEND = "false"
NTS_DERBY_LANGUAGE_LOG_QUERY_PLAN = "false"
NTS_DERBY_LANGUAGE_LOG_STATEMENT_TEXT = "false"
NTS_DERBY_LOCKS_DEADLOCK_TIMEOUT = "20"
NTS_DERBY_LOCKS_DEADLOCK_TRACE = "false"
NTS_DERBY_LOCKS_MONITOR = "true"
NTS_DERBY_LOCKS_WAIT_TIMEOUT = "300"
NTS_DERBY_STORAGE_PAGE_CACHE_SIZE = "4000"
400 IBM Notes Traveler Hints and Tips for a Successful Deployment
NTS_DEVICECAPABILITIESWRAPPER are settings that are used in defining settings for the
device server interaction.
NTS_DEVICECAPABILITIESWRAPPER_ALARM_ORDER = 4
NTS_DEVICECAPABILITIESWRAPPER_ALARM_ROUGH_SIZE = 20
NTS_DEVICECAPABILITIESWRAPPER_ATTENDEE_ORDER = 2
NTS_DEVICECAPABILITIESWRAPPER_ATTENDEE_ROUGH_SIZE = 30
NTS_DEVICECAPABILITIESWRAPPER_DESCRIPTION_ORDER = 1
NTS_DEVICECAPABILITIESWRAPPER_DISABLE_EVENT_TRUNCATION = false
NTS_DEVICECAPABILITIESWRAPPER_EVENT_TRUNCATE_MAX_OBJ_OFFSET_FACTOR = 0
NTS_DEVICECAPABILITIESWRAPPER_LOCATION_ORDER = 3
NTS_DEVICECAPABILITIESWRAPPER_SERVER_WINS_TRUNCATION = false
NTS_DEVICECAPABILITIESWRAPPER_SUMMARY_ORDER = 5
NTS_DEVICECAPABILITIESWRAPPER_XMLFILE = "Devices.xml"
NTS_DEVICECAPABILITIESWRAPPER_XMLFILE_ROOT_DIR = "C:/Program
Files/IBM/Lotus/Domino/data/traveler/cfg"
The following are Device Profile base default values. Starting name with NTS_DEVP_
automatically includes them in the base properties.
NTS_DEVP_ALLOWROAMING = "0"
NTS_DEVP_ALLOWSMS = "0"
NTS_DEVP_APPLSTOSYNC = "1:2:3:4:5"
NTS_DEVP_CALFILTERFUTUREDAYS = "90"
NTS_DEVP_CALFILTERPREVDAYS = "7"
NTS_DEVP_DEVICEATTACHSIZE = "100"
NTS_FETCHCACHE_MAX_SIZE = 50
NTS_FONT_CONVERSION = 0
NTS_FORCE_GC_MEMORY_LEVEL = 5
NTS_FORCE_OUTBOX_MAIL_TO_DRAFTS = false <---- Indicates that all outgoing mail will be saved
to drafts rather than being sent.
NTS_FORCE_START = false <---- Indicates that when the Lotus Notes Traveler starts, the start
program will not perform any checks.
NTS_INSTALLATION_TYPE = ON_PREMISE
NTS_INSTALL_INSTANCE = ""
NTS_INTERNAL_BATCH_UPDATES = false
NTS_INTERNAL_CAFDB_GETS_TYPE_AND_FOLDER_FROM_SYNC_OBJ = false
NTS_INTERNAL_RETRY_BATCH = false
NTS_INTERNAL_YEARLY_RECUR_LIMIT = 100
NTS_JAVA_PARMS = "" <---- This would override the max memory in the Lotus Traveler tab of
the server document. This would start the server with a max and min memory of 1024M:
NTS_Java_Parms=-Xms1024m -Xmx1024m
NTS_JAVA_PARMS_DEBUG = ""
NTS_LAST_DEFRAG = 0 <---- This is the last time the server ran a defrag. This will only be
used if you have defined to have a defrag run by setting the NTS_DEFRAG_INTERVAL_DAYS
parameter.
NTS_LINKHTMLALT = 0
NTS_LOG_COLLECT_DATE_RANGE = 14
NTS_LOG_COLLECT_ON_STARTUP = false
NTS_LOG_FINEST_INCLUDES_XML = true
NTS_LOG_LEVEL_SERVLET_REQUEST_RESPONSE = "FINE"
NTS_LOG_PRIVACY = "2;4;8;16"
NTS_LOG_ROOT_DIR = "C:/IBM/Lotus/Domino/data/IBM_TECHNICAL_SUPPORT/traveler/logs/" <----
Shows where the log files are placed on the server.
NTS_LOOKUP_ENFORCE_ACL = 0
Chapter 10. Appendix A 401
NTS_MAINTASK_QUIT_CHECK_THREADS = true <---- Indicates that the unexpected threads will not
be checked at the end of quit.
NTS_MAINTASK_QUIT_WAIT_TIME = 40
NTS_MAINTASK_SHUTDOWN_WAIT_TIME = 300
NTS_MAX_GUID_CACHE = 5000
NTS_MIGRATE_EXTERNAL_URL = false
NTS_MIGRATION_FAIL_THRESHOLD = 0 <---- Prevent starting if more than 50% of the Lotus Notes
Traveler migration failed
NTS_MIME_FORCE_B64 = false
NTS_NAME_LOOKUP_EMAILADDRESSITEMS = "InternetAddress" <---- List of nameLookupItems that are
email addresses. If these values contain characters that are not valid in an internet address,
they will be specially encoded or decoded as needed.
NTS_NAME_LOOKUP_FLAGS = 40 <---- Order of these fields are important for priority of results
returned. First item has highest priority, then second.
NTS_NAME_LOOKUP_ITEMS_EXT =
"LastName,FirstName,MiddleInitial,ListName,FullName,InternetAddress,$$NoteID,Type,Title,Suffix,O
fficeStreetAddress,OfficeCity,OfficeState,OfficeZIP,OfficeCountry,StreetAddress,City,State,Zip,c
ountry,JobTitle,CompanyName,Department,CellPhoneNumber,PhoneNumber,OfficePhoneNumber,WebSite"
(ext =
"LastName,FirstName,MiddleInitial,ListName,FullName,InternetAddress,$$NoteID,Type,Title,Suffix,O
fficeStreetAddress,OfficeCity,OfficeState,OfficeZIP,OfficeCountry,StreetAddress,City,State,Zip,c
ountry,JobTitle,CompanyName,Department,CellPhoneNumber,PhoneNumber,OfficePhoneNumber,WebSite")
NTS_NAME_LOOKUP_MAX_RECORDS = 30
NTS_NAME_LOOKUP_MIN_LENGTH = 3
NTS_NAME_LOOKUP_NAMESPACE = "($Users),($MailGroups),Mail-In Databases"
NTS_NAME_LOOKUP_UNIQUEITEMS = "InternetAddress,$$NoteID" <---- List of items used for
duplicate resolution. If two or more results contain the same value for these items, the first
result will be kept and the others discarded.
NTS_NEW_INSTALL = false
NTS_NOKIA_SECURITY = "1"
NTS_NONCECACHE_EXPINTERVAL = 30
NTS_NONCECACHE_LIFETIME = 300
NTS_OFFERNOTESURLINLINK = 1
NTS_OUTBOX_MAIL_SERVERS = "" <---- Lists the server names to be used for mail routing.
NTS_PMRUPLOAD* Is used for the tell traveler pmr nnnnn,bbb,ccc command.
NTS_PMRUPLOAD_PASSWORD = "********"
NTS_PMRUPLOAD_PASSWORD_RESET = ""
NTS_PMRUPLOAD_PATH = "/toibm/windows"
NTS_PMRUPLOAD_USER = "anonymous"
NTS_PMRUPLOAD_VALIDATION = true
NTS_PMRUPLOAD_HOST = "ftp.ecurep.ibm.com"
NTS_POLICY_DISABLE = false
NTS_POLICY_POLL_INTERVAL = 720 <---- Indicates that the poll for policies will wake up
every 12 hours. The values is in minutes.
NTS_PORT_PUSH_TCP = 8642
NTS_PORT_SERVLET = 50126 <---- This is the port used to communicate with the servlet
internally.
NTS_PORT_TRAVELER = 50125 <---- This is the internal port used to communicate with Domino.
NTS_PREF_ALARM_TYPE = 1
NTS_PREF_DATE_FORMAT = "mdy"
NTS_PREF_LOCALE = "en_US"
NTS_PREPEND_CLASSES = ""
NTS_PRESERVE_PROPS = false
402 IBM Notes Traveler Hints and Tips for a Successful Deployment
NTS_PRIMESYNC_CONSTRAINED_RETRY_TIME = 60 <---- If the Lotus Notes Traveler is in a
constrainted state, this is the interval of when to retry the request in seconds.
NTS_PRIMESYNC_ENABLED = true
NTS_PRIMESYNC_IGNORE_UPDATE_WINDOW_MSEC = 15
NTS_PRIMESYNC_SESSION_EXPIRATION = 2700
NTS_PS_CHANGE_THRESHOLD = 50
NTS_PS_MAX_RETURN_DOCS = 100
NTS_PS_UPDATE_LAST_ACCESS = 20
NTS_PUSH_CHANGEDDB_MINIMUM_BUILDNUMBER = 323
NTS_PUSH_CLEANUP_TIMEOUT = 30
NTS_PUSH_REAPINTERVAL = 300
NTS_PUSH_START_ONLINE = false
NTS_RETURN_RECEIPT_SAVE = false
NTS_RETURN_RECEIPT_SEND = true
NTS_ROUTE are HADR ROUTING configs
NTS_ROUTE_AI_ADD = 3
NTS_ROUTE_AI_SUBTRACT = 3
NTS_ROUTE_AUTO_DELETE = true
NTS_ROUTE_BIND_HOLD_TIME = 600000
NTS_ROUTE_CURRENT_BIAS = 20
NTS_ROUTE_HADR_AVAILABLE = true
NTS_ROUTE_LOCAL_BIAS = 10
NTS_ROUTE_REJECT_IF_UNAVAILABLE = true
NTS_ROUTE_UPGRADE_BIAS = 20
NTS_SAAS = false
NTS_SAAS_MONITOR_USERID = "QoS Probe"
NTS_SENDMAILCACHE_ENABLED = true
NTS_SENDMAILCACHE_EXPINTERVAL = 10
NTS_SENDMAILCACHE_LIFETIME = 60
NTS_SENDMAIL_SAVE_OPTIONS = ""
NTS_SERVLET_ALLOW_CLIENT_INSTALL* Befine what is displayed and available on the
servlet home page.
NTS_SERVLET_ALLOW_CLIENT_INSTALL = true
NTS_SERVLET_ALLOW_CLIENT_INSTALL_ANDROID = true
NTS_SERVLET_ALLOW_CLIENT_INSTALL_APPLE = true
NTS_SERVLET_ALLOW_CLIENT_INSTALL_NOKIA = true
NTS_SERVLET_ALLOW_CLIENT_INSTALL_WM = true
NTS_SERVLET_ALLOW_DELETE_IDFILE = false
NTS_SERVLET_ALLOW_MANAGE_NOTES_ID = true
NTS_SERVLET_ALLOW_REPORT_PROBLEM = true
NTS_SERVLET_ALLOW_USER_COMMANDS = false
NTS_SERVLET_ALLOW_USER_MANAGE_SECURITY = true
NTS_SERVLET_NO_RESPONSE_MSG_INTERVAL = 20
NTS_SERVLET_TIMEOUT_BUFFER = 5
NTS_SERVLET_WEB_FOOTER_INCLUDES_SERVER_INFO = true
NTS_SET_EXTERNAL_URL = ""
NTS_SMS_SENDER_ADDRESS = ""
NTS_SSL = false <---- Indicates that the SSL is off
Chapter 10. Appendix A 403
NTS_SSL_CLIENT_AUTH = true <---- false turns off client authentication, probably never need
this NTS_SSL_KEYSTORE defines the fully qualified path and file name for the Java key store file
to use. If it is not set, the default key store from the JVM environment is used.
NTS_SSL_KEYSTORE = "" <---- The key store password is required if the key store file is
specified. The KEYSTORE and TRUSTSTORE passwords are stored in LotusNotesTraveler.nsf and then
removed from notes.ini
NTS_SSL_KEYSTORE_PASSWORD = "********"
NTS_SSL_KEY_ALIAS = "" <---- NTS_SSL_TRUSTSTORE defines the fully qualified path and file
name for the Java key store file to use for trusted certificates. If it is not set, the key
store will be used.
NTS_SSL_PASSWORD_RESET = ""
NTS_SSL_TRUSTSTORE = ""
NTS_SSL_TRUSTSTORE_PASSWORD = "********" <---- The trust store password is required if the
trust store file is specified.
NTS_SERVLET_ALLOW_CLIENT_INSTALL = true
NTS_SERVLET_ALLOW_CLIENT_INSTALL_ANDROID = true
NTS_SERVLET_ALLOW_CLIENT_INSTALL_APPLE = true
NTS_SERVLET_ALLOW_CLIENT_INSTALL_NOKIA = true
NTS_SERVLET_ALLOW_CLIENT_INSTALL_WM = true
NTS_SERVLET_ALLOW_DELETE_IDFILE = false
NTS_SERVLET_ALLOW_MANAGE_NOTES_ID = true
NTS_SERVLET_ALLOW_REPORT_PROBLEM = true
NTS_SERVLET_ALLOW_USER_COMMANDS = false
NTS_SERVLET_ALLOW_USER_MANAGE_SECURITY = true
NTS_SERVLET_NO_RESPONSE_MSG_INTERVAL = 20
NTS_SERVLET_TIMEOUT_BUFFER = 5
NTS_SERVLET_WEB_FOOTER_INCLUDES_SERVER_INFO = true
NTS_SET_EXTERNAL_URL = ""
NTS_SMS_SENDER_ADDRESS = ""
NTS_SSL = false <---- Indicates that the SSL is off
NTS_SSL_CLIENT_AUTH = true <---- false turns off client authentication, probably never need
this NTS_SSL_KEYSTORE defines the fully qualified path and file name for the Java key store file
to use. If it is not set, the default key store from the JVM environment is used.
NTS_SSL_KEYSTORE = "" <---- The key store password is required if the key store file is
specified. The KEYSTORE and TRUSTSTORE passwords are stored in LotusNotesTraveler.nsf and then
removed from notes.ini
NTS_SSL_KEYSTORE_PASSWORD = "********"
NTS_SSL_KEY_ALIAS = "" <---- NTS_SSL_TRUSTSTORE defines the fully qualified path and file
name for the Java key store file to use for trusted certificates. If it is not set, the key
store will be used.
NTS_SSL_PASSWORD_RESET = ""
NTS_SSL_TRUSTSTORE = ""
NTS_SSL_TRUSTSTORE_PASSWORD = "********" <---- The trust store password is required if the
trust store file is specified.
NTS_STATS_PER_USER_REGEX = ""
NTS_STATS_REFRESH_TIME = 60
NTS_STATS_PER_USER_REGEX = ""
NTS_STATS_REFRESH_TIME = 60
The NTS_STATUS* parameters define the threshold of when the server status is in a
particular green, yellow, or red state.
NTS_STATUS_CONSTRAINT_ERROR_INTERVAL_MINUTES = 60
NTS_STATUS_CPU_PCT_RED_THRESHOLD = 90
NTS_STATUS_CPU_PCT_YELLOW_THRESHOLD = 70
404 IBM Notes Traveler Hints and Tips for a Successful Deployment
NTS_STATUS_DATA_DIR_FREE_PERCENTAGE_RED = 5
NTS_STATUS_SSL_CERT_EXPIRATION_YELLOW = 30
NTS_STATUS_THREAD_MAX_RUN_RED = 120
NTS_STATUS_THREAD_MAX_RUN_YELLOW = 30
NTS_SUPPORT_HTML_EMAIL = true <---- true to support HTML email on the server.
NTS_SYNCML* parameter define the behavior for syncml actions.
NTS_SYNCML_ACCESS_CONTEXT_FAIL_STATUS = "200"
NTS_SYNCML_ALERT_SYNC_DISABLED_FOR_SYNCML10 = false
NTS_SYNCML_ALERT_SYNC_UNCONDITIONALLY = false
NTS_SYNCML_COMPRESS = true
NTS_SYNCML_COMPRESSION_ERR_415 = true
NTS_SYNCML_DEFAULT_AUTH_TYPE = "syncml:auth-httpServer"
NTS_SYNCML_DEFAULT_PREVIEW_CHARS = 300
NTS_SYNCML_DISABLE_1WAY_FROM_CLIENT = true
NTS_SYNCML_DUMP_RECORD_DATA_ON_EXCEPTIONS = true
NTS_SYNCML_FAKE_SERVER_BUSY_SIGNALLING_WITH_EMPTY_MSG = true
NTS_SYNCML_ICAL_FORCE_UTC = false
NTS_SYNCML_LOOP_STOP_COUNT_CLIENT = 10
NTS_SYNCML_LOOP_STOP_COUNT_SERVER = 20
NTS_SYNCML_MAX_DEVICE_FULL_COUNT = 3
NTS_SYNCML_MAX_OTHER_SYNC_ACTIVE_COUNT = 0
NTS_SYNCML_MAX_RECORDS_PER_MESSAGE = 60
NTS_SYNCML_MAX_RECORD_TOO_LARGE_COUNT = 5
NTS_SYNCML_MAX_RETRIES_WITH_BUSY_SESSIONS = 1
NTS_SYNCML_REQUEST_TIME_LIMIT = 60
NTS_SYNCML_RESEND_TOO_LARGE_RECORDS = false
NTS_SYNCML_RESUME_SYNC_CHECKS = true
NTS_SYNCML_SEND_DELETES_BEFORE_INSERTS = true
NTS_SYNCML_SERVER_PATH = ["http://localhost:12350"]
NTS_SYNCML_SERVLET_SOCKETS = 20
NTS_SYNCML_SESSION_EXPIRATION = 600
NTS_SYNCML_SESSION_REAPER_INTERVAL = 60
NTS_SYNCML_SET_FIELDS_FOR_RETRIEVE = false
NTS_SYNCML_SHORTCIRCUIT_PERCENTAGE = 75
NTS_SYNCML_TIMESTAMPS_IN_HTTP = false
NTS_SYNCML_UGHATO_CHECK_IF_CAF_IS_DOWN = false
NTS_SYNCML_USE_SERVER_BUSY_SIGNALLING = false
NTS_SYSTEM_DUMP_DEFAULT_COMMANDS =
["status","java","configuration","threads","threaddata","stat","push","security","
sync","banneddoc","mailreplicas","database","dbconfig","ha"] The default
parameters used when a systemdump is generated.
NTS_SYSTEM_DUMP_TIMEOUT = 300 <---- in seconds
NTS_TELL_COMMAND_STATUS_INTERVAL = 30
NTS_THREADS are the settings for the numbers of threads in the server..
NTS_THREADS_ADMINQ = 3
NTS_THREADS_ALARM = 20
NTS_THREADS_DEVICESYNC = 5000
NTS_THREADS_MINIMUM_DEVICESYNC = 10
NTS_THREADS_MINIMUM_PRIMESYNC = 5
NTS_THREADS_PRIMESYNC = 200
Chapter 10. Appendix A 405
NTS_THREADS_PRIMESYNC_CONSTRAINT_MULTIPLE = 1000
NTS_THREADS_TELL_COMMAND = 50
NTS_THREADS_WORKER = 5000
NTS_TPR_RECEIVED_CLASS = ""
NTS_TRAVELER_AS_LOOKUP_SERVER = false
NTS_TSS_REGISTER_DUPLICATE_CHECKERS =
"NOKIA_9500=com.lotus.sync.TSS.ExtRoutine.IBM.duplicateChecker.DuplicateCheckerNok
ia9500"
NTS_TSS_SESSION_EXPIRATION = 600
NTS_TSS_SESSION_REAPER_INTERVAL = 60
NTS_USERCACHE* is used to cache objects that are expensive to retrieve or create and are
long lasting. Typically that is going to be information retrieved from the user's mail database
that stays constant most of the time, for example the ACL on their DB, the device profiles and
preferences and their home mail server information.
NTS_USERCACHE_ENABLED = true
NTS_USERCACHE_EXPINTERVAL = 30
NTS_USERCACHE_LIFETIME = 240
NTS_USER_AGENT_ALLOWED_ANDROID = true
NTS_USER_AGENT_ALLOWED_APPLE = true
NTS_USER_AGENT_ALLOWED_NOKIA = true
NTS_USER_AGENT_ALLOWED_REGEX = ".*"
NTS_USER_AGENT_ALLOWED_WM = true
NTS_USER_EMAIL_LIMIT = 0
NTS_USER_EVENTS_LIMIT = 0
NTS_USER_ID_ALLOWED_REGEX = ".*"
NTS_USER_ID_DENIED_REGEX = ""
NTS_USER_LIMITS_MIGRATE = false
NTS_USER_NOTES_LIMIT = 0
NTS_WEBSITE_HOME = "/traveler"
NTS_WEB_REALM_STRING = ""
Non-default configuraton values:
--------------------------------
NTS_BUILD = "8.5.3.100 Upgrade Pack 1 Build 201206132102" (default = "") <---- Shows the the
build that is running.
NTS_DBCONNECTIONURL = "jdbc:db2://chevy.rtp.raleigh.ibm.com:50000/trvlrdb" (default = "")
<---- This is the URL to connect to the database.
NTS_DBPASSWORD = "********" (default = "********") <---- This is the encrypted database
password.
NTS_DBPATH = "C:\IBM\Lotus\Domino\Traveler\lib\db2jcc4.jar" (default = "") . <---- Shows the
path to the driver is HA is used.
NTS_DBUSER = "********" (default = "********") <---- This is the encrypted database user id.
NTS_EXTERNAL_URL = "http://9.37.30.206/traveler" (default = "")
NTS_HOST_IP_ADDR = "9.37.30.206" (default = "") <---- Shows the host IP address of the Lotus
Notes Traveler server.
NTS_MIGRATION_FINISHED = true (default = false) <---- True if derby to enterprise database
migration finished successfully during HA configuration.
NTS_SERVER_LANG = "en" (default = "") <---- Shows the language of the server.
NTS_TEMPLATE_INSTALL = 0 (default = 1)
--- notes.ini ---
The notes.ini is listed here.
[Notes]
406 IBM Notes Traveler Hints and Tips for a Successful Deployment
NotesProgram=C:\IBM\Lotus\Domino
Directory=C:\IBM\Lotus\Domino\data
KitType=2
InstallType=4
PartitionNumber=1
ServiceName=Lotus Domino Server (CIBMLotusDominodata)
FaultRecovery_Build=Release 8.5.3
DSTLAW=3,2,1,11,1,1
FileDlgDirectory=C:\Documents and Settings\Administrator\My Documents
SHARED_MAIL=0
DisableLDAPOnAdmin=0
Passthru_LogLevel=0
Console_LogLevel=2
DDETimeout=10
NAMEDSTYLE0=030042617369630000000000000000000000000000000000000000000000000000000000000001010100
000A0000000000000100A0050A0000006400A0050A000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000009404000000000000
NAMEDSTYLE0_FACE=Default Sans Serif
NAMEDSTYLE1=030042756C6C657400000000000000000000000000000000000000000000000000000000000001010100
000A000000000000000008070A000000640008070A000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000049404000000000000
NAMEDSTYLE1_FACE=Default Sans Serif
NAMEDSTYLE2=0300486561646C696E650000000000000000000000000000000000000000000000000000000001010101
0B0C0000000000000100A0050A0000006400A0050A000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000009404000000000000
NAMEDSTYLE2_FACE=Default Sans Serif
DefaultMailTemplate=mail85.ntf
Preferences=32
ServerTasks=Update,Replica,Router,AMgr,AdminP,CalConn,Sched,LDAP,RnRMgr,TRAVELER
ServerTasksAt1=Catalog,Design
ServerTasksAt2=UpdAll
ServerTasksAt5=Statlog
TCPIP=TCP, 0, 15, 0
LAN0=NETBIOS, 0, 15, 0
LAN1=NETBIOS, 1, 15, 0
LAN2=NETBIOS, 2, 15, 0
LAN3=NETBIOS, 3, 15, 0
LAN4=NETBIOS, 4, 15, 0
LAN5=NETBIOS, 5, 15, 0
LAN6=NETBIOS, 6, 15, 0
LAN7=NETBIOS, 7, 15, 0
LAN8=NETBIOS, 8, 15, 0
Timezone=5
DST=1
MailType=0
$$HasLANPort=1
Ports=TCPIP
DisabledPorts=LAN0,LAN1,LAN2,LAN3,LAN4,LAN5,LAN6,LAN7,LAN8
LOG_REPLICATION=1
LOG_SESSIONS=1
KeyFileName=C:\IBM\Lotus\Domino\data\server.id
KeyFileName_Owner=CN=9.37.30.206/O=organization
CertifierIDFile=C:\IBM\Lotus\Domino\data\cert.id
MailServer=CN=9.37.30.206/O=organization
PhoneLog=2
Chapter 10. Appendix A 407
Log=log.nsf, 1, 0, 7, 40000
FirstServerInDomain=1
ServerKeyFileName=server.id
Domain=matt
Admin=CN=Administrator/O=organization
TemplateSetup=850300
Setup=850300
ServerSetup=850300
ServerKeyFileName_Owner=CN=9.37.30.206/O=organization
NAMELOOKUP_TRUST_DIRCAT=0
CleanSetup=1
ServerName=9.37.30.206/organization
ServerNameNative=047F047F392E33372E33302E3230362F6D756E7365
DAOSDeferredDeleteInterval=30
DAOSBasePath=DAOS
DAOSMinObjSize=64000
DAOSEnable=0
DB2QUERYVIEWROWLIMIT=500
DB2_PW_EXP_ALARM_DAYS_PRIOR=15
DB2_DBS_PER_SCHEMA=10
DB_CREATION_DEFAULT_TYPE=NSF
FormulaTimeout=120
NSF_QUOTA_METHOD=2
TRANSLOG_AutoFixup=1
TRANSLOG_UseAll=0
TRANSLOG_Style=0
TRANSLOG_Performance=2
TRANSLOG_Status=0
ServerController=0
MTEnabled=0
SCHEDULE_DB_BOSS=1
SCHEDULE_VERSION=4
SCHEDULE_VERSION_MINOR=10
LDAPNoAutoStartRepairDIT=1
HTTPJVMMaxHeapSize=64M
HTTPJVMMaxHeapSizeSet=1
LDAPSERVER=ldap://9.37.30.206:389
LDAPSERVERSSL=ldap://9.37.30.206:0
CLEANUP_EVENTS4_ON_FIRST_NIGHT=0
WebAdminSetup=850
DominoConfigLevel=1
EventSetup=850300
DELETE_DUPLICATE_PUID_NOTES=0
DDMSetup=850300
LAST_DOMINO_TIME=005A893B85257A70
ServerRestarted=0
CONSOLE_9=80 300 7 154 154 822 485
NTS_TEMPLATE_INSTALL=0
NTS_AUTO_CONFIG=true
NTS_AUTOSTART_HTTP=true
NTS_DBCONNECTIONURL=jdbc:db2://chevy.rtp.raleigh.ibm.com:50000/trvlrdb
NTS_SERVLET_ALLOW_CLIENT_INSTALL=true
NTS_NEW_INSTALL=false
NTS_INSTALLATION_TYPE=ON_PREMISE
NTS_SERVER_LANG=en
408 IBM Notes Traveler Hints and Tips for a Successful Deployment
NTS_BUILD=8.5.3.100 Upgrade Pack 1 Build 201206132102
CATALOG_UPDATED_BY_BUILD=510
CLEANUP_EVENTS4_DDMFILTERS_VIEW=0
CLEANUP_EVENTS4_DDMCONFIG_VIEW=0
CLEANUP_EVENTS4_METHODS_VIEW=0
CLEANUP_EVENTS4_STATS_VIEW=0
CLEANUP_EVENTS4_MESSAGES_VIEW=0
ADMINP_LAST_SAVED_POLICY_TIME=09/05/2012 04:39:25 AM
ADMINP_LAST_SAVED_USER_TIME=09/04/2012 04:39:43 PM
ADMINP_LAST_SAVED_DIRECTORY_TIME=09/05/2012 02:01:02 AM
FaultRecovery=0
CleanupTimeout=600
NTS_DBPATH=C:\IBM\Lotus\Domino\Traveler\lib\db2jcc4.jar
NTS_MIGRATION_FINISHED=true
JrnlEnbld=0
TravelerUtil Configuration (Wed Sep 05 12:29:04 EDT 2012)
The travelerUtil command is created at install time, and obtains the values from the system at
this time.
########## TravelerUtil Configuration (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: Current status of all configuration possible using travelerUtil
command.
PMR Host: ftp.ecurep.ibm.com
PMR Path: /toibm/windows
PMR username: anonymous
PMR password: ********
Database Connection URL: jdbc:db2://chevy.rtp.raleigh.ibm.com:50000/trvlrdb
notes.ini JDBC Driver Path: C:\IBM\Lotus\Domino\Traveler\lib\db2jcc4.jar
DB username: db2admin
DB password: ********
Retrieving SSL key store password from Traveler database.
SSL key store file is not configured.
XLogManager (Wed Sep 05 12:29:04 EDT 2012)
The logging can be modified by using tell commands at runtime. Please reference the 8.6,
Logging on page 340 for this information.
########## XLogManager (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: List of the current logging settings the Traveler process as well as
the Traveler servlet running in the HTTP process.
Logging Home Directory =
C:/IBM/Lotus/Domino/data/IBM_TECHNICAL_SUPPORT/traveler/logs/
--- settings stored in database ---
Chapter 10. Appendix A 409
LogLevel=INFO
NTSActivityLogger.useParentHandlers=false
NTSActivityLogger.handlers=com.lotus.sync.logging.ActivityFileHandler
com.lotus.sync.logging.ErrorFileHandler com.lotus.sync.logging.UsageFileHandler
com.lotus.sync.logging.LogNsfHandler com.lotus.sync.logging.ConsoleHandler
NTSActivityLogger.level=ALL
com.lotus.sync.logging.ActivityFileHandler.level=ALL
com.lotus.sync.logging.ActivityFileHandler.filter=com.lotus.sync.logging.PackageFi
lter
com.lotus.sync.logging.ActivityFileHandler.formatter=com.lotus.sync.logging.Activi
tyFormatter
...
com.lotus.sync.logging.XMLLogger.pattern=xml/xml_%g
com.lotus.sync.logging.XMLLogger.append=true
UserFilter=
PackageFilter=
Privacy=0x001e
UsageLoggingEnabled=true
LogDataObjectLength=20000
Domino Configuration(Wed Sep 05 12:29:04 EDT 2012)
########## Domino Configuration (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: List of the current Domino configuration values used by the Lotus Notes Traveler
server based on the server document (not just the Lotus Traveler tab).
The complete client configuration files (Apple.xml) are also included.
The complete listing of the Domino server document and any Internet Site Documents are also
included .
Configuration Properties
DOMINO_DATA_DIR=C:/IBM/Lotus/Domino/data
TRAVELER_BINARY_DIR=C:/IBM/Lotus/Domino
TRAVELER_BINARY_FILE=C:/IBM/Lotus/Domino\Traveler\lib\traveler.jar
TRAVELER_DATA_DIR=C:/IBM/Lotus/Domino/data/traveler
TRAVELER_CFG_DIR=C:/IBM/Lotus/Domino/data/traveler\cfg\
TRAVELER_CLIENT_CONFIG_FILENAME_APPLE=C:/IBM/Lotus/Domino/data/traveler\cfg\client\Apple.xml
TRAVELER_CLIENT_CONFIG_TEMPLATE_FILENAME_APPLE=C:/IBM/Lotus/Domino/data/traveler\cfg\client\Appl
eTemplate.xml
OS_STRING=Windows Server 2003
fullServerUserName=CN=9.37.30.206/O=organization
serverUserName=9.37.30.206
organization=organization
serverHostName=9
serverName=9.37.30.206/organization
fullServerHostName=9.37.30.206
serverDomain=matt
verifyHTTPServerSettings=true
restartHTTPServer=false
isiteDocsEnabled=false
notesINIPath=C:\IBM\Lotus\Domino\notes.ini
--- Java System Properties ---
410 IBM Notes Traveler Hints and Tips for a Successful Deployment
java.vendor=IBM Corporation
os.name=Windows Server 2003
sun.boot.class.path=C:\IBM\Lotus\Domino\jvm\lib\vm.jar;C:\IBM\Lotus\Domino\jvm\lib\ibmallorb.jar
;C:\IBM\Lotus\Domino\jvm\lib\rt.jar;C:\IBM\Lotus\Domino\jvm\lib\ibmpkcs.jar;C:\IBM\Lotus\Domino\
jvm\lib\ibmjcefw.jar
sun.java2d.fontpath=
java.vm.specification.vendor=Sun Microsystems Inc.
java.runtime.version=jvmwi3260sr9-20110712_86792
user.name=Administrator
java.compiler=j9jit24
os.encoding=UTF8
com.ibm.util.extralibs.properties=
com.ibm.jcl.checkClassPath=
Debug=false
user.language=en
com.ibm.oti.vm.bootstrap.library.path=C:\IBM\Lotus\Domino\jvm\bin
derby.system.home=C:/IBM/Lotus/Domino/data/traveler
sun.boot.library.path=C:\IBM\Lotus\Domino\jvm\bin
derby.storage.pageCacheSize=1000
server.binary.dir=C:/IBM/Lotus/Domino
java.version=1.6.0
user.timezone=America/New_York
sun.arch.data.model=32
com.ibm.zero.version=1
java.endorsed.dirs=C:\IBM\Lotus\Domino\jvm\lib\endorsed
com.ibm.oti.vm.library.version=24
NTS.dst=1
sun.jnu.encoding=Cp1252
jxe.current.romimage.version=15
file.separator=\
java.specification.name=Java Platform API Specification
java.class.version=50.0
user.country=US
java.home=C:\IBM\Lotus\Domino\jvm
domino.diag.dir=C:/IBM/Lotus/Domino/data/IBM_TECHNICAL_SUPPORT
java.vm.info=JRE 1.6.0 IBM J9 2.4 Windows Server 2003 x86-32 jvmwi3260sr9-20110712_86792 (JIT
enabled, AOT enabled)
J9VM - 20110712_086792
JIT - r9_20101028_17488ifx19
GC - 20101027_AA
os.version=5.2 build 3790 Service Pack 2
java.awt.fonts=
path.separator=;
java.vm.version=2.4
java.util.prefs.PreferencesFactory=java.util.prefs.WindowsPreferencesFactory
user.variant=
java.awt.printerjob=sun.awt.windows.WPrinterJob
sun.io.unicode.encoding=UnicodeLittle
awt.toolkit=sun.awt.windows.WToolkit
ibm.signalhandling.sigint=true
java.assistive=ON
NTS.tz=5
server.data.dir=C:/IBM/Lotus/Domino/data/traveler
user.home=C:\Documents and Settings\Administrator
com.ibm.cpu.endian=little
Chapter 10. Appendix A 411
java.specification.vendor=Sun Microsystems Inc.
ibm.signalhandling.sigchain=true
java.library.path=C:\IBM\Lotus\Domino\jvm\bin;.;C:\STAF\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WI
NDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0
java.vendor.url=http://www.ibm.com/
java.vm.vendor=IBM Corporation
java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows Server 2003 x86-32 jvmwi3260sr9-20110712_86792
(JIT enabled, AOT enabled)
J9VM - 20110712_086792
JIT - r9_20101028_17488ifx19
GC - 20101027_AA
java.runtime.name=Java(TM) SE Runtime Environment
java.class.path=C:/IBM/Lotus/Domino/Traveler/lib/commons-net-2.0.jar;C:/IBM/Lotus/Domino/Travele
r/lib/db2jcc4.jar;C:/IBM/Lotus/Domino/Traveler/lib/derby.jar;C:/IBM/Lotus/Domino/Traveler/lib/tr
aveler.jar;C:/IBM/Lotus/Domino/Traveler/lib/db2jcc4.jar
derby.stream.error.file=C:/IBM/Lotus/Domino/data/IBM_TECHNICAL_SUPPORT/traveler/logs/traveler_da
tabase.log
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.version=1.0
java.io.tmpdir=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\
java.jcl.version=20110713_06
ibm.system.encoding=Cp1252
os.arch=x86
java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment
ibm.signalhandling.rs=false
java.ext.dirs=C:/IBM/Lotus/Domino/ndext;C:/IBM/Lotus/Domino/jvm/lib/ext;
NTS.tzname=Eastern
user.dir=C:\IBM\Lotus\Domino
line.separator=
java.vm.name=IBM J9 VM
com.ibm.oti.shared.enabled=false
com.ibm.vm.bitmode=32
domino.data.dir=C:/IBM/Lotus/Domino/data
jxe.lowest.romimage.version=15
file.encoding=Cp1252
com.ibm.oti.jcl.build=20110202_1316
java.specification.version=1.6
com.ibm.oti.configuration=scar
--- C:/IBM/Lotus/Domino/data/traveler\cfg\client\Apple.xml ---
This is the template that is used to generate the Apple profile.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<!--
Copyright (c) 2011, 2012 IBM Corporation
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions
and the following disclaimer.
412 IBM Notes Traveler Hints and Tips for a Successful Deployment
* Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials provided
with the distribution.
* Neither the name of IBM Corporation nor the names of its contributors may be used to endorse
or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY IBM CORPORATION AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
ILNT_Address will be replaced with the user's email address
ILNT_HostName will be replaced with the server host name
ILNT_HostPath will be replaced with the servlet path name (e.g., /traveler)
ILNT_HostPortHTTP will be replaced with the server host port when using HTTP if the port is not
the default port of 80 (e.g., 81) or with an empty string when using HTTPS
ILNT_HostPortHTTPS will be replaced with the server host port when using HTTPS if the port is ot
the default port of 443 (e.g., 8443) or with an empty string when using HTTP
ILNT_HostProtocol will be replaced with the server host protocol (<false/> or <true/> for SSL
off or SSL on)
ILNT_User will be replaced with the user name
If you are using a proxy between the client and the Traveler server,
you should set the "External Server URL" on the "Lotus Traveler" tab in the server document
so that the ILNT wildcards below are filled in properly.
Do NOT modify any the the <key> values. Only modify the values associated with the keys as
needed.
-->
<plist version="1.0">
<dict>
<key>PayloadUUID</key>
<string>8B9A9E2E-53E7-44EC-A361-74EC8136B4CE-ILNT_HostNameILNT_HostPortHTTPILNT_HostPortHTTPS-IL
NT_User</string>
<!--
Customizable and displayed on the Apple UI.
On the Profile UI, this shows up as the top-most, bold line (no wrapping).
-->
<key>PayloadDisplayName</key>
<string>ILNT_User - IBM Lotus Notes Traveler</string>
<!--
Customizable and displayed on the Apple UI.
On the Profile UI, this shows up right below the PayloadDisplayName (no wrapping).
-->
Chapter 10. Appendix A 413
<key>PayloadOrganization</key>
<string>IBM Lotus Notes Traveler</string>
<!--
Customizable and displayed on the Apple UI.
On the Profile UI, this shows up as the multi-line (up to 10) wrapped Description.
-->
<key>PayloadDescription</key>
<string>Configures the device for use with IBM Lotus Notes Traveler for
ILNT_User.</string>
<!--
Customizable, but not known to be displayed on the Apple UI anywhere.
A reverse-DNS style identifier (com.example.myprofile, for example) that
identifies the profile. This string is used to determine whether a new profile
should replace an existing one or should be added.
-->
<key>PayloadIdentifier</key>
<string>com.lotus.sync.ILNT_HostName.ILNT_HostPortHTTPILNT_HostPortHTTPS.ILNT_User</string>
<key>PayloadVersion</key>
<integer>1</integer>
<key>PayloadType</key>
<string>Configuration</string>
<key>PayloadContent</key>
<array>
<!--
If you want this profile to include more than just the com.apple.eas.account,
you should create the profile using iPhone Configuration Utility, add/replace
the com.apple.eas.account <dict>...</dict> in the newly created profile with
the com.apple.eas.account shown below, rename the newly created profile to
Apple.xml, and replace the existing Apple.xml file with the new Apple.xml file.
See the InfoCenter for more details.
-->
<dict>
<key>PayloadUUID</key>
<string>837AE5F3-1380-4234-BAD0-8246A644AC2F-ILNT_HostNameILNT_HostPortHTTPILNT_HostPortHTTPS-IL
NT_User</string>
<!--
Customizable and displayed on the Apple UI.
During Profile installation, this shows up under More Details as the "Exchange
Account"
along with the Host and EmailAddress values.
This is the account name shown at the bottom of the password prompt during Profile
installation.
This is the account name shown under General - Mail, Contacts, Calendar - Account.
414 IBM Notes Traveler Hints and Tips for a Successful Deployment
This is the account name shown in the Mail, Contact, and Calendar applications as
needed.
-->
<key>PayloadDisplayName</key>
<string>ILNT_User - IBM Lotus Notes Traveler</string>
<!-- Customizable, but not known to be displayed on the Apple UI anywhere. -->
<key>PayloadDescription</key>
<string>IBM Lotus Notes Traveler for ILNT_User.</string>
<!-- Customizable, but not known to be displayed on the Apple UI anywhere. -->
<key>PayloadOrganization</key>
<string>IBM Lotus Notes Traveler</string>
<key>PayloadVersion</key>
<integer>1</integer>
<!--
Customizable, but not known to be displayed on the Apple UI anywhere.
A reverse-DNS style identifier (com.example.myprofile, for example) that
identifies the profile. This string is used to determine whether a new profile
should replace an existing one or should be added.
-->
<key>PayloadIdentifier</key>
<string>com.lotus.sync.eas.ILNT_HostName.ILNT_HostPortHTTPILNT_HostPortHTTPS.ILNT_User</string>
<key>PayloadType</key>
<string>com.apple.eas.account</string>
<!--
Whether or not the user should be prevented from creating mail using
this account from apps other than the Mail app (for example, the Photos app).
This only applies to iOS5 or later devices. Default: <false/>.
-->
<key>PreventAppSheet</key>
<false/>
<!--
Whether or not mails should be prevented from being moved from the
Traveler (Exchange) account into a different account. This only applies to
iOS5 or later devices. Default: <true/>.
-->
<key>PreventMove</key>
<true/>
<!--
Default value for the number of past days of mail to sync; this
is the "Mail Days to Sync" value on the Apple UI. The user can still change the
setting (higher and lower) on the Apple UI.
Valid values are 1, 3, 7, 14, 31, and 0 (unlimited/no limit).
-->
<key>MailNumberOfPastDaysToSync</key>
<integer>3</integer>
Chapter 10. Appendix A 415
<key>UserName</key>
<string>ILNT_User</string>
<key>EmailAddress</key>
<string>ILNT_Address</string>
<!--
If you are using a proxy between the client and the Traveler server,
you should set the "External Server URL" on the "Lotus Traveler" tab
in the server document and leave this as the default value
(ILNT_HostNameILNT_HostPortHTTPILNT_HostPortHTTPS).
You should not need to modify the Host or SSL values (use the ILNT wildcards).
If you do modify this value, it cannot have "http://" or "https:// at
the beginning as that is automatically prepended based on the SSL key's value.
The Apple device will automatically append the ActiveSync path
(/Microsoft-Server-ActiveSync)
to whatever value is delivered in this profile. By default,
/Microsoft-Server-ActiveSync/*
should be configured to route to the main servlet (e.g.,
/traveler/Microsoft-Server-ActiveSync/*).
If something in the network path (such as a proxy) is not configured to route
/Microsoft-Server-ActiveSync/* to the main servlet, you may need to add ILNT_HostPath
back to
the end of this value so that the servlet path part of the External Server URL is
included here.
-->
<key>Host</key>
<string>ILNT_HostNameILNT_HostPortHTTPILNT_HostPortHTTPS</string>
<!-- Actual values are <true/> or <false/> if not using the ILNT_HostProtocol
wildcard. -->
<key>SSL</key>
ILNT_HostProtocol
</dict>
</array>
</dict>
</plist>
Server Document
--- Server Document ---
*********************************************************************************
******************** BEGIN DUMP OF DOCUMENT *************************************
*********************************************************************************
This is the values of the server document. Lotus Notes Traveler parameters are listed with the
begining of the parameter name starting with "ts" For example: "Name: tsMaxMem
Type: Number/number list Size: 10 Value: 512"
416 IBM Notes Traveler Hints and Tips for a Successful Deployment
The value of this property is "512 M" as set in the server document for the Lotus Traveler tab.
UNID: 08B5C5099E6B2B7785257A6F006D0CE2
NoteId: 1CCE
Last Modifed: Wed Sep 05 11:25:59 EDT 2012
Create Date: Tue Sep 04 15:51:07 EDT 2012
Updated By: CN=9.37.30.206/O=organization
Name: MailSystem Type: Text/text list Size: 3 Value: 1
Name: MajVer Type: Number/number list Size: 10 Value: 8
Name: MinVer Type: Number/number list Size: 10 Value: 5
Name: QMRVer Type: Number/number list Size: 10 Value: 3
Name: QMUVer Type: Number/number list Size: 10 Value: 0
Name: HotVer Type: Number/number list Size: 10 Value: 0
Name: FixPVer Type: Number/number list Size: 10 Value: 0
Name: FlagsVer Type: Number/number list Size: 10 Value: 0
Name: ServerDirectoryName Type: Text/text list Size: 11 Value:
names.nsf
Name: Form Type: Text/text list Size: 8 Value:
Server
Name: Type Type: Text/text list Size: 8 Value:
Server
Name: ServerName Type: Names Size: 24 Value:
CN=9.37.30.206/O=organization
Name: ServerTitle Type: Text/text list Size: 2 Value: [no
text]
Name: Tasks Type: Text/text list Size: 14 Value: Mail
Routing
Name: Domain Type: Text/text list Size: 6 Value: matt
Name: SMTPListenerEnabled Type: Text/text list Size: 3 Value: 0
Name: SMTPFullHostDomain Type: Text/text list Size: 13 Value:
9.37.30.206
Name: ServerPhoneNumber Type: Text/text list Size: 2 Value: [no
text]
Name: LdISite Type: Text/text list Size: 3 Value: 0
Name: FormulaTimeout Type: Number/number list Size: 10 Value: 120
Name: Sametime Type: Text/text list Size: 3 Value: 0
Name: MasterAddressBook Type: Text/text list Size: 2 Value: [no
text]
Name: FltRcvryScrpt Type: Text/text list Size: 2 Value: [no
text]
Name: LEDName Type: Text/text list Size: 2 Value: [no
text]
Name: TrustDircat Type: Text/text list Size: 2 Value: [no
text]
Name: FREnbld Type: Text/text list Size: 2 Value: [no
text]
Name: FltRcvryMax Type: Number/number list Size: 10 Value: 600
Name: NoCntDir Type: Text/text list Size: 3 Value: 1
Name: FltRcvryHng Type: Number/number list Size: 10 Value: 300
Name: FltRcvryCrsh Type: Number/number list Size: 10 Value: 3
Name: FltRcvryMin Type: Number/number list Size: 10 Value: 5
Name: FltRcvryNot Type: Names Size: 2 Value: [no
text]
Chapter 10. Appendix A 417
Name: OutsideLine Type: Text/text list Size: 2 Value: [no
text]
Name: CallPre Type: Text/text list Size: 2 Value: [no
text]
Name: InternationalPrefix Type: Text/text list Size: 2 Value: [no
text]
Name: Suffix Type: Text/text list Size: 2 Value: [no
text]
Name: country Type: Text/text list Size: 2 Value: [no
text]
Name: LongDistancePrefix Type: Text/text list Size: 3 Value: 1
Name: RLANIdleTimeout Type: Text/text list Size: 2 Value: [no
text]
Name: TimeZone Type: Text/text list Size: 3 Value: 5
Name: MailServer Type: Names Size: 24 Value:
CN=9.37.30.206/O=organization
Name: DST Type: Text/text list Size: 3 Value: 1
Name: DefaultPassthruServer Type: Names Size: 2 Value: [no
text]
Name: InterNotes Type: Names Size: 2 Value: [no
text]
Name: FullAdmin Type: Names Size: 2 Value: [no
text]
Name: UnrestrictedList Type: Names Size: 2 Value: [no
text]
Name: Administrator Type: Names Size: 26 Value:
CN=Administrator/O=organization
Name: OnBehalfOfLst Type: Names Size: 2 Value: [no
text]
Name: DBAdmin Type: Names Size: 2 Value: [no
text]
Name: OnBehalfOfInvokerLst Type: Names Size: 2 Value: [no
text]
Name: RemoteAdmin Type: Names Size: 2 Value: [no
text]
Name: RestrictedList Type: Names Size: 2 Value: [no
text]
Name: VOAdmin Type: Names Size: 2 Value: [no
text]
Name: PrivateList Type: Names Size: 2 Value: [no
text]
Name: SysAdmin Type: Names Size: 2 Value: [no
text]
Name: LibsLst Type: Names Size: 2 Value: [no
text]
Name: ResSysAdmin Type: Names Size: 2 Value: [no
text]
Name: ResSystemCmds Type: Text/text list Size: 2 Value: [no
text]
Name: NOIRestrictedList Type: Names Size: 2 Value: [no
text]
Name: BrowserAdminAccess Type: Names Size: 2 Value: [no
text]
Name: NOIUnrestrictedList Type: Names Size: 2 Value: [no
text]
418 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: WhiteList Type: Text/text list Size: 2 Value: [no
text]
Name: WhiteListLog Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_AuthView Type: Text/text list Size: 10 Value:
($Users)
Name: AnonymousAccess Type: Text/text list Size: 3 Value: 0
Name: ServerCheckPasswords Type: Text/text list Size: 3 Value: 0
Name: AddressBookAccess Type: Text/text list Size: 2 Value: [no
text]
Name: PTAccess Type: Names Size: 2 Value: [no
text]
Name: DenyAccess Type: Names Size: 2 Value: [no
text]
Name: PTClients Type: Names Size: 2 Value: [no
text]
Name: CreateAccess Type: Names Size: 2 Value: [no
text]
Name: PTCallers Type: Names Size: 2 Value: [no
text]
Name: ReplicaAccess Type: Names Size: 2 Value: [no
text]
Name: PTTargets Type: Names Size: 2 Value: [no
text]
Name: TemplateAccess Type: Names Size: 2 Value: [no
text]
Name: AllowMonitors Type: Names Size: 3 Value: *
Name: DenyMonitors Type: Names Size: 2 Value: [no
text]
Name: TrustedSrvrs Type: Names Size: 2 Value: [no
text]
Name: Port_0 Type: Text/text list Size: 7 Value: TCPIP
Name: Enabled_0 Type: Text/text list Size: 3 Value: 1
Name: Port_1 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_1 Type: Text/text list Size: 3 Value: 0
Name: Port_2 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_2 Type: Text/text list Size: 3 Value: 0
Name: Port_3 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_3 Type: Text/text list Size: 3 Value: 0
Name: Port_4 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_4 Type: Text/text list Size: 3 Value: 0
Name: Port_5 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_5 Type: Text/text list Size: 3 Value: 0
Name: Port_6 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_6 Type: Text/text list Size: 3 Value: 0
Name: Port_7 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_7 Type: Text/text list Size: 3 Value: 0
Chapter 10. Appendix A 419
Name: HTTP_SSLKeyFile Type: Text/text list Size: 13 Value:
keyfile.kyr
Name: SSLProtocolVersion Type: Text/text list Size: 3 Value: 0
Name: SSLSiteCerts Type: Text/text list Size: 3 Value: 0
Name: SSLExpiredCerts Type: Text/text list Size: 3 Value: 1
Name: SSLCipherList Type: Text/text list Size: 24 Value:
04;05;0A;09;03
Name: SSLV2Enabled Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_Port Type: Number/number list Size: 10 Value: 80
Name: HTTP_NormalMode Type: Text/text list Size: 3 Value: 1
Name: HTTP_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: HTTP_TCPNP Type: Text/text list Size: 3 Value: 1
Name: HTTP_AllowAnonymous Type: Text/text list Size: 3 Value: 1
Name: HTTP_SSLPort Type: Number/number list Size: 10 Value: 443
Name: HTTP_SSLMode Type: Text/text list Size: 3 Value: 0
Name: HTTP_SSLCert Type: Text/text list Size: 3 Value: 0
Name: HTTP_SSLNP Type: Text/text list Size: 3 Value: 1
Name: HTTP_SSLAnonymous Type: Text/text list Size: 3 Value: 1
Name: LDAP_Port Type: Number/number list Size: 10 Value: 389
Name: LDAP_PortStatus Type: Text/text list Size: 3 Value: 1
Name: LDAP_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: LDAP_TCPNP Type: Text/text list Size: 3 Value: 1
Name: LDAP_AllowAnonymous Type: Text/text list Size: 3 Value: 1
Name: LDAP_SSLPort Type: Number/number list Size: 10 Value: 636
Name: LDAP_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: LDAP_SSLCert Type: Text/text list Size: 3 Value: 0
Name: LDAP_SSLNP Type: Text/text list Size: 3 Value: 0
Name: LDAP_SSLAnonymous Type: Text/text list Size: 3 Value: 1
Name: NNTP_Port Type: Number/number list Size: 10 Value: 119
Name: NNTP_PortStatus Type: Text/text list Size: 3 Value: 1
Name: NNTP_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: NNTP_TCPNP Type: Text/text list Size: 3 Value: 1
Name: NNTP_TCPAnonymous Type: Text/text list Size: 3 Value: 1
Name: NNTP_SSLPort Type: Number/number list Size: 10 Value: 563
Name: NNTP_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: NNTP_SSLCert Type: Text/text list Size: 3 Value: 0
Name: NNTP_SSLNP Type: Text/text list Size: 3 Value: 1
Name: NNTP_SSLAnonymous Type: Text/text list Size: 3 Value: 0
Name: IMAP_Port Type: Number/number list Size: 10 Value: 143
Name: POP3_Port Type: Number/number list Size: 10 Value: 110
Name: SMTP_Port Type: Number/number list Size: 10 Value: 25
Name: Router_Port Type: Number/number list Size: 10 Value: 25
Name: IMAP_PortStatus Type: Text/text list Size: 3 Value: 1
Name: POP3_PortStatus Type: Text/text list Size: 3 Value: 1
Name: SMTP_PortStatus Type: Text/text list Size: 3 Value: 1
Name: Router_PortStatus Type: Text/text list Size: 3 Value: 1
Name: IMAP_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: POP3_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: SMTP_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: SMTP_TCPNP Type: Text/text list Size: 3 Value: 0
Name: SMTP_AllowAnonymous Type: Text/text list Size: 3 Value: 1
Name: IMAP_SSLPort Type: Number/number list Size: 10 Value: 993
Name: POP3_SSLPort Type: Number/number list Size: 10 Value: 995
Name: SMTP_SSLPort Type: Number/number list Size: 10 Value: 465
420 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: Router_SSLPort Type: Number/number list Size: 10 Value: 465
Name: IMAP_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: POP3_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: SMTP_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: Router_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: IMAP_SSLCert Type: Text/text list Size: 3 Value: 0
Name: POP3_SSLCert Type: Text/text list Size: 3 Value: 0
Name: IMAP_SSLNP Type: Text/text list Size: 3 Value: 1
Name: POP3_SSLNP Type: Text/text list Size: 3 Value: 1
Name: SMTP_SSLNP Type: Text/text list Size: 3 Value: 0
Name: SMTP_SSLAnonymous Type: Text/text list Size: 3 Value: 1
Name: IIOP_Port Type: Number/number list Size: 10 Value: 63148
Name: IIOP_PortStatus Type: Text/text list Size: 3 Value: 1
Name: IIOP_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: IIOP_TCPNP Type: Text/text list Size: 3 Value: 1
Name: IIOP_AllowAnonymous Type: Text/text list Size: 3 Value: 1
Name: IIOP_SSLPort Type: Number/number list Size: 10 Value: 63149
Name: IIOP_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: IIOP_SSLNP Type: Text/text list Size: 3 Value: 0
Name: IIOP_SSLAnonymous Type: Text/text list Size: 3 Value: 1
Name: RDM_Port Type: Number/number list Size: 10 Value: 60000
Name: RDM_PortStatus Type: Text/text list Size: 3 Value: 1
Name: RDM_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: RDM_SSLPort Type: Number/number list Size: 10 Value: 60001
Name: RDM_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: DC_IP_Address Type: Text/text list Size: 2 Value: [no
text]
Name: DC_Port Type: Text/text list Size: 6 Value: 2050
Name: Proxy_HTTP Type: Text/text list Size: 2 Value: [no
text]
Name: Proxy_FTP Type: Text/text list Size: 2 Value: [no
text]
Name: Proxy_Gopher Type: Text/text list Size: 2 Value: [no
text]
Name: Proxy_SSL Type: Text/text list Size: 2 Value: [no
text]
Name: Proxy_NotesHTTP Type: Text/text list Size: 2 Value: [no
text]
Name: Proxy_SOCKs Type: Text/text list Size: 2 Value: [no
text]
Name: No_Proxy Type: Text/text list Size: 2 Value: [no
text]
Name: AdminPMaxThreads Type: Number/number list Size: 10 Value: 3
Name: AdminPMailfileDelInt Type: Text/text list Size: 2 Value: [no
text]
Name: AdminPInterval Type: Text/text list Size: 2 Value: [no
text]
Name: AdminPWeekDays Type: Text/text list Size: 3 Value: 1
Name: AdminPDailyTime Type: Text/text list Size: 2 Value: [no
text]
Name: AdminPDelayedTime Type: Text/text list Size: 2 Value: [no
text]
Name: AdminPNameChangeExpiration Type: Number/number list Size: 10 Value: 21
Name: InboxTrimDays Type: Text/text list Size: 3 Value: 7
Name: AdminPLogSetting Type: Text/text list Size: 3 Value: 0
Chapter 10. Appendix A 421
Name: InboxTrimTime Type: Date-time/range Size: 10 Value:
01:00:00 AM
Name: AdminPSuspendStart Type: Text/text list Size: 2 Value: [no
text]
Name: InboxTrimLoc Type: Text/text list Size: 3 Value: 2
Name: AdminPSuspendEnd Type: Text/text list Size: 2 Value: [no
text]
Name: InboxTrimUsers Type: Names Size: 2 Value: [no
text]
Name: gracedays Type: Number/number list Size: 10 Value: 90
Name: MaxRemDocs Type: Number/number list Size: 10 Value: 500
Name: SaveUnread Type: Text/text list Size: 2 Value: [no
text]
Name: ReloadTime Type: Date-time/range Size: 10 Value:
12:00:00 AM
Name: StartTime Type: Date-time/range Size: 10 Value:
08:00:00 AM
Name: MaxStartTime Type: Date-time/range Size: 10 Value:
08:00:00 PM
Name: EndTime Type: Date-time/range Size: 10 Value:
08:00:00 PM
Name: MaxEndTime Type: Date-time/range Size: 10 Value:
08:00:00 AM
Name: ConcurrentAgents Type: Number/number list Size: 10 Value: 1
Name: MaxConcurrentAgents Type: Number/number list Size: 10 Value: 2
Name: MaxExecution Type: Number/number list Size: 10 Value: 10
Name: MaxMaxExecution Type: Number/number list Size: 10 Value: 15
Name: PercentTime Type: Number/number list Size: 10 Value: 50
Name: MaxPercentTime Type: Number/number list Size: 10 Value: 70
Name: CatalogDomainScope Type: Names Size: 2 Value: [no
text]
Name: CatalogEnabled Type: Text/text list Size: 3 Value: 0
Name: CatalogSchedule Type: Date-time/range Size: 22 Value:
12:01:00 AM-11:59:00 PM
Name: CatalogInterval Type: Number/number list Size: 10 Value: 60
Name: CatalogIndexerScope Type: Names Size: 2 Value: [no
text]
Name: EDFilenames Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled Type: Text/text list Size: 3 Value: 0
Name: Schedule Type: Date-time/range Size: 22 Value:
08:00:00 AM-10:00:00 PM
Name: Interval Type: Number/number list Size: 10 Value: 360
Name: ICMClusterName Type: Text/text list Size: 2 Value: [no
text]
Name: ICMNotesPort Type: Text/text list Size: 2 Value: [no
text]
Name: ICMSSLKeyfile Type: Text/text list Size: 13 Value:
keyfile.kyr
Name: ICM_BrowseDatabases Type: Text/text list Size: 3 Value: 0
Name: ICMConfiguration Type: Text/text list Size: 3 Value: 1
Name: ICMHostname Type: Text/text list Size: 2 Value: [no
text]
Name: ICMRemoteServerName Type: Text/text list Size: 2 Value: [no
text]
422 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: ICMHTTP_Port Type: Number/number list Size: 10 Value: 80
Name: ICMHTTP_PortStatus Type: Text/text list Size: 3 Value: 1
Name: ICMHTTP_SSLPort Type: Number/number list Size: 10 Value: 443
Name: ICMHTTP_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: WebDbName Type: Text/text list Size: 9 Value:
web.nsf
Name: WebAllow Type: Text/text list Size: 3 Value: *
Name: WebServices Type: Text/text list Size: 23 Value:
HTTP;FTP;GOPHER
Name: WebDeny Type: Text/text list Size: 2 Value: [no
text]
Name: WebRetrievers Type: Number/number list Size: 10 Value: 50
Name: WebLogLevel Type: Text/text list Size: 3 Value: 0
Name: WebUpdateCache Type: Text/text list Size: 3 Value: 1
Name: SMTP_Domain Type: Text/text list Size: 2 Value: [no
text]
Name: RDMgrEnbld Type: Text/text list Size: 3 Value: 0
Name: RDOff Type: Number/number list Size: 10 Value: 24
Name: RDWait Type: Number/number list Size: 10 Value: 0
Name: HTTP_HostName Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_HomeURL Type: Text/text list Size: 11 Value:
/traveler
Name: HTTP_BindToHostName Type: Text/text list Size: 3 Value: 0
Name: HTTP_HTMLDir Type: Text/text list Size: 13 Value:
domino\html
Name: HTTP_DNSLookup Type: Text/text list Size: 3 Value: 0
Name: HTTP_IconsDir Type: Text/text list Size: 14 Value:
domino\icons
Name: HTTP_DNSLookupCache Type: Text/text list Size: 3 Value: 1
Name: HTTP_IconsPath Type: Text/text list Size: 8 Value:
/icons
Name: HTTP_DNSCacheSize Type: Number/number list Size: 10 Value: 256
Name: HTTP_CGIDir Type: Text/text list Size: 16 Value:
domino\cgi-bin
Name: HTTP_DNSCacheFoundTimeout Type: Number/number list Size: 10 Value: 120
Name: HTTP_CGIPath Type: Text/text list Size: 10 Value:
/cgi-bin
Name: HTTP_DNSCacheNotFoundTimeout Type: Number/number list Size: 10 Value: 240
Name: HTTP_MaxActiveThreads Type: Number/number list Size: 10 Value: 100
This is the max active HTTP threads, this should be 1.2* the number of devices on the system
(Push.Devices.Total).
Name: HTTP_DatabaseBrowsing Type: Text/text list Size: 3 Value: 0
Name: HTTP_AccessLogFormat Type: Text/text list Size: 3 Value: 0
Name: HTTP_MaxRequests Type: Number/number list Size: 10 Value: 1
Name: HTTP_LogTime Type: Text/text list Size: 3 Value: 0
Name: HTTP_MinActiveThreads Type: Number/number list Size: 10 Value: 20
Name: HTTP_LogFileDuration Type: Text/text list Size: 3 Value: 0
Name: HTTP_Welcome Type: Text/text list Size: 13 Value:
default.htm
Name: HTTP_MaxLogEntrySize Type: Number/number list Size: 10 Value: 10
Name: HTTP_MaxCachedCommands Type: Text/text list Size: 5 Value: 128
Name: HTTP_MaxLogFileSize Type: Number/number list Size: 10 Value: 0
Name: HTTP_Audience Type: Text/text list Size: 3 Value: 0
Name: HTTP_LogToFiles Type: Text/text list Size: 3 Value: 0
Chapter 10. Appendix A 423
Name: HTTP_FilterLibrary Type: Text/text list Size: 10 Value:
ndolextn
Name: HTTP_LogToDomLog Type: Text/text list Size: 3 Value: 0
Name: HTTP_LogDirectory Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_ExcludeURLs Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_AccessLog Type: Text/text list Size: 8 Value:
access
Name: HTTP_ExcludeMethods Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_AgentLog Type: Text/text list Size: 7 Value: agent
Name: HTTP_ExcludeMIMETypes Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_RefererLog Type: Text/text list Size: 9 Value:
referer
Name: HTTP_ExcludeUserAgents Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_ErrorLog Type: Text/text list Size: 7 Value: error
Name: HTTP_ExcludeReturnCodes Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_CGIErrorLog Type: Text/text list Size: 11 Value:
cgi-error
Name: HTTP_NoLog Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_11Connections Type: Text/text list Size: 3 Value: 1
Name: HTTP_InputTimeout Type: Number/number list Size: 10 Value: 2
Name: HTTP_Max11Requests Type: Number/number list Size: 10 Value: 100
Name: HTTP_OutputTimeout Type: Number/number list Size: 10 Value: 20
Name: HTTP_PersistentTimeout Type: Number/number list Size: 10 Value: 180
Name: HTTP_ScriptTimeout Type: Number/number list Size: 10 Value: 5
Name: HTTP_RequestTimeout Type: Number/number list Size: 10 Value: 60
Name: HTTP_IdleThreadTimeout Type: Number/number list Size: 10 Value: 0
Name: HTTP_RNInputTimeout Type: Number/number list Size: 10 Value: 75
Name: HTTP_RNOutputTimeout Type: Number/number list Size: 10 Value: 180
Name: HTTP_RNCGITimeout Type: Number/number list Size: 10 Value: 180
Name: HTTP_ListenQueueSize Type: Number/number list Size: 10 Value: 512
Name: HTTP_MaxURLBytes Type: Number/number list Size: 10 Value: 4
Name: HTTP_MaxConcurrentNetwkSessions Type: Number/number list Size: 10 Value: 2000
Name: HTTP_MaxURLPathSegments Type: Number/number list Size: 10 Value: 64
Name: HTTP_AllowDenyPriority Type: Text/text list Size: 3 Value: 1
Name: HTTP_MaxHeaderLines Type: Number/number list Size: 10 Value: 48
Name: HTTP_AllowIPList Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_MaxHeaderBytes Type: Number/number list Size: 10 Value: 16
Name: HTTP_DenyIPList Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_MaxContentLength Type: Number/number list Size: 10 Value: 10000
Name: HTTP_Comp Type: Text/text list Size: 3 Value: 0
Name: HTTP_CompEUA Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_CompIMT Type: Text/text list Size: 27 Value:
text/*;application/*
Name: HTTP_CompEMT Type: Text/text list Size: 2 Value: [no
text]
424 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: HTTP_EnableSessionAuth Type: Text/text list Size: 3 Value: 0
Name: HTTP_JavaServletSupport Type: Text/text list Size: 3 Value: 0
Name: HTTP_IdleSessionTimeout Type: Number/number list Size: 10 Value: 30
Name: HTTP_SSOCfg Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_ServletPath Type: Text/text list Size: 10 Value:
/servlet
Name: HTTP_ForceLoginOnSSL Type: Text/text list Size: 3 Value: 0
Name: HTTP_JSClasspath Type: Text/text list Size: 16 Value:
domino\servlet
Name: HTTP_MaxActiveSessions Type: Number/number list Size: 10 Value: 1000
Name: HTTP_JSFileExtensions Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_EnableJSessions Type: Text/text list Size: 3 Value: 1
Name: HTTP_CompanionStack Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_IdleJSTimeout Type: Number/number list Size: 10 Value: 30
Name: HTTP_RedirectUseHTTPS Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_MaxActiveJSessions Type: Number/number list Size: 10 Value: 1000
Name: HTTP_RedirectServerName Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_EnableJSPersistence Type: Text/text list Size: 3 Value: 0
Name: HTTP_RedirectPortNo Type: Number/number list Size: 10 Value: 80
Name: HTTP_MaxCachedDesigns Type: Text/text list Size: 5 Value: 128
Name: HTTP_maxPostDataLength Type: Text/text list Size: 7 Value: 10000
Name: HTTP_MaxCachedUsers Type: Text/text list Size: 4 Value: 64
Name: HTTP_compressUploadedFiles Type: Text/text list Size: 3 Value: 0
Name: HTTP_ExpireCachedUsers Type: Text/text list Size: 5 Value: 120
Name: HTTP_PrfCookieOption Type: Text/text list Size: 3 Value: 2
Name: HTTP_ResourceLang Type: Text/text list Size: 4 Value: en
Name: HTTP_useUserLocale Type: Text/text list Size: 3 Value: 1
Name: HTTP_AltResourceLang Type: Text/text list Size: 4 Value: en
Name: HTTP_ImageFormat Type: Text/text list Size: 3 Value: 0
Name: HTTP_UTF8 Type: Text/text list Size: 3 Value: 1
Name: HTTP_ImageProgressive Type: Text/text list Size: 3 Value: 1
Name: HTTP_NoUTF8Forms Type: Text/text list Size: 3 Value: 0
Name: HTTP_ImageQuality Type: Number/number list Size: 10 Value: 75
Name: HTTP_DefViewRows Type: Number/number list Size: 10 Value: 30
Name: HTTP_CS5Default Type: Text/text list Size: 3 Value: 2
Name: HTTP_MaxViewRows Type: Number/number list Size: 10 Value: 1000
Name: HTTP_CSWestern Type: Text/text list Size: 4 Value: 32
Name: HTTP_DefSearchMax Type: Number/number list Size: 10 Value: 250
Name: HTTP_CSCentralEuropean Type: Text/text list Size: 4 Value: 80
Name: HTTP_MaxSearchMax Type: Number/number list Size: 10 Value: 1000
Name: HTTP_CSJapanese Type: Text/text list Size: 4 Value: 18
Name: HTTP_GenBangUrls Type: Text/text list Size: 3 Value: 0
Name: HTTP_CSTaiwanese Type: Text/text list Size: 4 Value: 26
Name: HTTP_EnableRedirectCmd Type: Text/text list Size: 3 Value: 1
Name: HTTP_CSChinese Type: Text/text list Size: 6 Value: 3377
Name: HTTP_CSKorean Type: Text/text list Size: 4 Value: 24
Name: HTTP_CSCyrillic Type: Text/text list Size: 6 Value: 3308
Name: HTTP_CSGreek Type: Text/text list Size: 4 Value: 83
Name: HTTP_CacheDir Type: Text/text list Size: 14 Value:
domino\cache
Chapter 10. Appendix A 425
Name: HTTP_CSTurkish Type: Text/text list Size: 4 Value: 84
Name: HTTP_MaxCacheSize Type: Number/number list Size: 10 Value: 50
Name: HTTP_CSThai Type: Text/text list Size: 5 Value: 144
Name: HTTP_DeleteCache Type: Text/text list Size: 3 Value: 0
Name: HTTP_CSBaltic Type: Text/text list Size: 4 Value: 87
Name: HTTP_EnableGC Type: Text/text list Size: 3 Value: 1
Name: HTTP_CSArabic Type: Text/text list Size: 4 Value: 86
Name: HTTP_GCInterval Type: Number/number list Size: 10 Value: 60
Name: HTTP_CSHebrew Type: Text/text list Size: 6 Value: 3356
Name: HTTP_CSVietnamese Type: Text/text list Size: 6 Value: 3310
Name: HTTP_CSIndic Type: Text/text list Size: 5 Value: 171
Name: HTTP_AutoDetect Type: Text/text list Size: 3 Value: 0
Name: HTTP_asynchronizeAgents Type: Text/text list Size: 3 Value: 0
Name: HTTP_webAgentTimeout Type: Number/number list Size: 10 Value: 0
Name: HTTP_HeaderCharset Type: Text/text list Size: 3 Value: 1
Name: HTTP_MetaCharset Type: Text/text list Size: 3 Value: 0
Name: HTTP_DomWSAppSpace Type: Text/text list Size: 3 Value: 1
Name: HTTP_DomWSAddinMaxThreads Type: Number/number list Size: 10 Value: 20
Name: HTTP_DomWSForceFromValue Type: Text/text list Size: 3 Value: 1
Name: HTTP_EnabledServices Type: Text/text list Size: 2 Value: [no
text]
Name: IIOP_HtmlDir Type: Text/text list Size: 2 Value: [no
text]
Name: IIOP_IORHost Type: Text/text list Size: 2 Value: [no
text]
Name: IIOP_ThreadPoolSize Type: Number/number list Size: 10 Value: 10
Name: NNTP_Admin Type: Names Size: 2 Value: [no
text]
Name: NNTPLogLevel Type: Text/text list Size: 3 Value: 0
Name: NNTPRdrDefaultAccess Type: Text/text list Size: 3 Value: 1
Name: NNTPRdrDefaultExceptions Type: Text/text list Size: 2 Value: [no
text]
Name: NNTPAllowRdrPosting Type: Text/text list Size: 3 Value: 1
Name: NNTPAllowFeedPosting Type: Text/text list Size: 3 Value: 1
Name: NNTPMaxRdrPostSize Type: Number/number list Size: 10 Value: 1024
Name: NNTPMaxFeedPostSize Type: Number/number list Size: 10 Value: 1024
Name: NNTPMaxRdrConSize Type: Number/number list Size: 10 Value: 10
Name: NNTPMaxFeedConSize Type: Number/number list Size: 10 Value: 100
Name: NNTPRdrConTimeout Type: Number/number list Size: 10 Value: 600
Name: NNTPMaxFeedConnections Type: Number/number list Size: 10 Value: 5
Name: NNTPMaxRdrConnections Type: Number/number list Size: 10 Value: 20
Name: SMTPGlobalDomain Type: Text/text list Size: 2 Value: [no
text]
Name: SMTPPollingPeriod Type: Number/number list Size: 10 Value: 120
Name: SMTPAdministrator Type: Names Size: 2 Value: [no
text]
Name: SMTPWork Type: Text/text list Size: 2 Value: [no
text]
Name: SMTPLogLevel Type: Text/text list Size: 3 Value: 1
Name: SMTPEnableHK Type: Text/text list Size: 3 Value: 1
Name: SMTPDailyHKAt Type: Date-time/range Size: 10 Value:
01:00:00 AM
Name: SMTP822HeaderOption Type: Text/text list Size: 3 Value: 2
Name: SMTPAddrResolutionCntl Type: Text/text list Size: 3 Value: 3
Name: SMTPEncodingScheme Type: Text/text list Size: 3 Value: 1
426 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: SMTPRetryAttempts Type: Number/number list Size: 10 Value: 8
Name: SMTPMessageContent Type: Text/text list Size: 3 Value: T
Name: SMTPRetryInterval Type: Number/number list Size: 10 Value: 15
Name: SMTPReturnReceipts Type: Text/text list Size: 3 Value: 1
Name: SMTPTransferMode Type: Text/text list Size: 3 Value: 1
Name: SMTPLanguageParam Type: Text/text list Size: 2 Value: [no
text]
Name: SMTPCharSetDetect Type: Text/text list Size: 3 Value: 2
Name: SMTPTypeface Type: Text/text list Size: 3 Value: 3
Name: SMTPPointSize Type: Text/text list Size: 3 Value: 9
Name: SMTPMacAttachConvertOption Type: Text/text list Size: 3 Value: 1
Name: SMTPMaxInbTasks Type: Number/number list Size: 10 Value: 3
Name: SMTPMaxOutbTasks Type: Number/number list Size: 10 Value: 3
Name: SMTPMaxOutbMsgSize Type: Number/number list Size: 10 Value: 0
Name: DiskC Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtC Type: Text/text list Size: 3 Value: 1
Name: DiskO Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtO Type: Text/text list Size: 3 Value: 1
Name: DiskD Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtD Type: Text/text list Size: 3 Value: 1
Name: DiskP Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtP Type: Text/text list Size: 3 Value: 1
Name: DiskE Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtE Type: Text/text list Size: 3 Value: 1
Name: DiskQ Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtQ Type: Text/text list Size: 3 Value: 1
Name: DiskF Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtF Type: Text/text list Size: 3 Value: 1
Name: DiskR Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtR Type: Text/text list Size: 3 Value: 1
Name: DiskG Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtG Type: Text/text list Size: 3 Value: 1
Name: DiskS Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtS Type: Text/text list Size: 3 Value: 1
Name: DiskH Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtH Type: Text/text list Size: 3 Value: 1
Name: DiskT Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtT Type: Text/text list Size: 3 Value: 1
Name: DiskI Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtI Type: Text/text list Size: 3 Value: 1
Name: DiskU Type: Text/text list Size: 2 Value: [no
text]
Chapter 10. Appendix A 427
Name: SpndlCtU Type: Text/text list Size: 3 Value: 1
Name: DiskJ Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtJ Type: Text/text list Size: 3 Value: 1
Name: DiskV Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtV Type: Text/text list Size: 3 Value: 1
Name: DiskK Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtK Type: Text/text list Size: 3 Value: 1
Name: DiskW Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtW Type: Text/text list Size: 3 Value: 1
Name: DiskL Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtL Type: Text/text list Size: 3 Value: 1
Name: DiskX Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtX Type: Text/text list Size: 3 Value: 1
Name: DiskM Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtM Type: Text/text list Size: 3 Value: 1
Name: DiskY Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtY Type: Text/text list Size: 3 Value: 1
Name: DiskN Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtN Type: Text/text list Size: 3 Value: 1
Name: DiskZ Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtZ Type: Text/text list Size: 3 Value: 1
Name: Location Type: Text/text list Size: 2 Value: [no
text]
Name: Department Type: Text/text list Size: 2 Value: [no
text]
Name: Comment Type: Text/text list Size: 2 Value: [no
text]
Name: ServerDescription Type: Rich text Size: 104 Value: [no
text]
Name: TRANSLOG_Status Type: Text/text list Size: 3 Value: 0
Name: TRANSLOG_Style Type: Text/text list Size: 3 Value: 0
Name: TRANSLOG_UseAll Type: Text/text list Size: 3 Value: 0
Name: TRANSLOG_MaxSize Type: Text/text list Size: 2 Value: [no
text]
Name: TRANSLOG_AutoFixup Type: Text/text list Size: 3 Value: 1
Name: TRANSLOG_Performance Type: Text/text list Size: 3 Value: 2
Name: QtaMthd Type: Text/text list Size: 3 Value: 2
Name: STVPClientPort Type: Number/number list Size: 10 Value: 1533
Name: STPort_T120 Type: Number/number list Size: 10 Value: 8081
Name: STPort_VP Type: Number/number list Size: 10 Value: 1516
Name: STPort_T123 Type: Number/number list Size: 10 Value: 1503
Name: STCommunityHTTPSPort Type: Number/number list Size: 10 Value: 1533
Name: STMeetingHTTPSPort Type: Number/number list Size: 10 Value: 8081
Name: STCommunityHTTPTunneling Type: Text/text list Size: 3 Value: 1
Name: STCommunityHTTPTunnelingPort Type: Number/number list Size: 10 Value: 8082
428 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: STMeetingHTTPTunnelingPort Type: Number/number list Size: 10 Value: 8081
Name: STMaxCommunityConnections Type: Number/number list Size: 10 Value: 8000
Name: ST_HostName Type: Text/text list Size: 2 Value: [no
text]
Name: STDirChunkSize Type: Number/number list Size: 10 Value: 100
Name: ST_BindToHostName Type: Text/text list Size: 3 Value: 0
Name: STDirRefreshInterval Type: Number/number list Size: 10 Value: 60
Name: STActiveMeetingsLimitEnabled Type: Text/text list Size: 2 Value: [no
text]
Name: STActiveMeetingsLimit Type: Number/number list Size: 10 Value: 100
Name: STConfigRefreshInterval Type: Number/number list Size: 10 Value: 60
Name: STTotalUsersLimitEnabled Type: Text/text list Size: 2 Value: [no
text]
Name: STTotalUsersLimit Type: Number/number list Size: 10 Value: 500
Name: STMeetingUsersLimitEnabled Type: Text/text list Size: 2 Value: [no
text]
Name: STMeetingUsersLimit Type: Number/number list Size: 10 Value: 50
Name: STAutoExtendMeetingEnabled Type: Text/text list Size: 3 Value: 1
Name: STMeetingExtendTime Type: Number/number list Size: 10 Value: 15
Name: STLogTime Type: Text/text list Size: 3 Value: 0
Name: STCommunityLogin Type: Text/text list Size: 3 Value: 1
Name: STCommunityLoginFailed Type: Text/text list Size: 2 Value: [no
text]
Name: STCommunityTotalConnections Type: Text/text list Size: 2 Value: [no
text]
Name: STLogHistory Type: Number/number list Size: 10 Value: 30
Name: STCommunityLogUsageFrequency Type: Number/number list Size: 10 Value: 10
Name: STLogToFiles Type: Text/text list Size: 3 Value: 0
Name: STMeetingLogEvents Type: Text/text list Size: 3 Value: 1
Name: STMeetingLogParticipants Type: Text/text list Size: 3 Value: 1
Name: STLogToNSF Type: Text/text list Size: 3 Value: 1
Name: STLogFileName Type: Text/text list Size: 14 Value:
sametime.log
Name: SHARED_MAIL Type: Text/text list Size: 3 Value: 0
Name: SCOS_DIR_1 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_1 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_1 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_2 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_2 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_2 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_3 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_3 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_3 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_4 Type: Text/text list Size: 2 Value: [no
text]
Chapter 10. Appendix A 429
Name: SCOS_DIR_MAX_SIZE_MB_4 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_4 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_5 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_5 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_5 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_6 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_6 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_6 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_7 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_7 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_7 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_8 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_8 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_8 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_9 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_9 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_9 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_10 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_10 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_10 Type: Text/text list Size: 2 Value: [no
text]
Name: DAOSEnable Type: Text/text list Size: 3 Value: 0
Name: DAOSObjDelete Type: Number/number list Size: 10 Value: 30
Name: DB2Host Type: Text/text list Size: 2 Value: [no
text]
Name: DB2Port Type: Text/text list Size: 2 Value: [no
text]
Name: DB2Inst Type: Text/text list Size: 2 Value: [no
text]
Name: DB2Db Type: Text/text list Size: 2 Value: [no
text]
Name: DB2Dir Type: Text/text list Size: 2 Value: [no
text]
Name: DB2Def Type: Text/text list Size: 3 Value: 1
Name: DB2UDFSrv Type: Text/text list Size: 2 Value: [no
text]
430 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: DB2UDFPath Type: Text/text list Size: 2 Value: [no
text]
Name: DB2GroupMax Type: Number/number list Size: 10 Value: 10
Name: DB2DefUser Type: Text/text list Size: 2 Value: [no
text]
Name: DB2QVRows Type: Number/number list Size: 10 Value: 500
Name: tsMaxMem Type: Number/number list Size: 10 Value: 512
Name: tsIPCPort Type: Number/number list Size: 10 Value: 50125
Name: tsIPCPort2 Type: Number/number list Size: 10 Value: 50126
Name: tsExternalURL Type: Text/text list Size: 29 Value:
http://9.37.30.206/traveler
Name: tsAddressBookAccess Type: Text/text list Size: 2 Value: [no
text]
Name: tsDenyAccess Type: Names Size: 2 Value: [no
text]
Name: tsUserCMD Type: Text/text list Size: 3 Value: 0
Name: tsUserWipe Type: Text/text list Size: 3 Value: 1
Name: tsLogLevel Type: Text/text list Size: 3 Value: 3
Name: tsTrcLevel Type: Text/text list Size: 3 Value: 0
Name: tsTrcCmp Type: Text/text list Size: 3 Value: *
Name: tsTrcSize Type: Number/number list Size: 10 Value: 50
Name: tsTrcFiles Type: Number/number list Size: 10 Value: 10
Name: tsTrcPriv Type: Text/text list Size: 17 Value:
2;4;8;16
Name: tsPollTime Type: Number/number list Size: 10 Value: 3
Name: devPTCPP Type: Number/number list Size: 10 Value: 8642
Name: tsPHBeatAlg Type: Text/text list Size: 3 Value: 2
Name: tsPHBFixed Type: Number/number list Size: 10 Value: 55
Name: tsPHBInitial Type: Number/number list Size: 10 Value: 30
Name: tsPHBAmim Type: Number/number list Size: 10 Value: 30
Name: tsPHBAmaxsec Type: Number/number list Size: 10 Value: 15
Name: tsPHBAretry Type: Number/number list Size: 10 Value: 30
Name: tsPofflinehr Type: Number/number list Size: 10 Value: 24
Name: tsPcleanup Type: Number/number list Size: 10 Value: 30
Name: Owner Type: Authors Size: 2 Value: [no
text]
Name: LocalAdmin Type: Authors Size: 2 Value: [no
text]
Name: PKMinWidth Type: Text/text list Size: 3 Value: 0
Name: PKMaxWidth Type: Text/text list Size: 6 Value: 1024
Name: PKDefWidth Type: Text/text list Size: 6 Value: 1024
Name: PKMaxAge Type: Number/number list Size: 10 Value: 36500
Name: PKMinDate Type: Date-time/range Size: 10 Value:
08/01/1977
Name: PKDueDate Type: Date-time/range Size: 10 Value:
09/04/2112
Name: PKOldKeyDays Type: Number/number list Size: 10 Value: 365
Name: ChangeRequest Type: Text/text list Size: 2 Value: [no
text]
Name: DocumentAccess Type: Authors Size: 18 Value:
[ServerModifier]
Name: BookmarkDB Type: Text/text list Size: 14 Value:
bookmark.nsf
Name: ServerPlatform Type: Text/text list Size: 32 Value:
Windows/2003 5.2 Intel Pentium
Chapter 10. Appendix A 431
Name: ASPServer Type: Text/text list Size: 3 Value: 0
Name: DAOSWarned Type: Text/text list Size: 3 Value: 0
Name: $ServerMain Type: Number/number list Size: 10 Value: 0
Name: $Server_Ports_Tabs Type: Number/number list Size: 10 Value: 0
Name: $Server_Ports_Internet2_Tabs Type: Number/number list Size: 10 Value: 0
Name: $Server_Tasks_Tabs Type: Number/number list Size: 10 Value: 0
Name: $Server_InetProt_Tabs Type: Number/number list Size: 10 Value: 0
Name: $Server_MTA_Tabs Type: Number/number list Size: 10 Value: 0
Name: FltRcvryMD Type: Text/text list Size: 6 Value: 8530
Name: ServerBuildNumber Type: Text/text list Size: 15 Value:
Release 8.5.3
Name: ClusterName Type: Text/text list Size: 2 Value: [no
text]
Name: ServerCPUCount Type: Number/number list Size: 10 Value: 2
Name: NSDEnbld Type: Text/text list Size: 3 Value: 1
Name: CfgNABonly Type: Text/text list Size: 3 Value: 0
Name: AllowAccess Type: Names Size: 2 Value: [no
text]
Name: Protocol_0 Type: Text/text list Size: 5 Value: TCP
Name: NetName_0 Type: Text/text list Size: 15 Value: TCPIP
Network
Name: NetAddr_0 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocol_1 Type: Text/text list Size: 2 Value: [no
text]
Name: NetName_1 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_1 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocol_2 Type: Text/text list Size: 2 Value: [no
text]
Name: NetName_2 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_2 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocol_3 Type: Text/text list Size: 2 Value: [no
text]
Name: NetName_3 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_3 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocol_4 Type: Text/text list Size: 2 Value: [no
text]
Name: NetName_4 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_4 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocol_5 Type: Text/text list Size: 2 Value: [no
text]
Name: NetName_5 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_5 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocol_6 Type: Text/text list Size: 2 Value: [no
text]
432 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: NetName_6 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_6 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocol_7 Type: Text/text list Size: 2 Value: [no
text]
Name: NetName_7 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_7 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: EnabledList Type: Text/text list Size: 28 Value:
1;0;0;0;0;0;0;0
Name: Ports Type: Text/text list Size: 7 Value: TCPIP
Name: Network Type: Text/text list Size: 15 Value: TCPIP
Network
Name: NetAddresses Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocols Type: Text/text list Size: 5 Value: TCP
Name: SSLStrongEncryption Type: Text/text list Size: 14 Value:
03040506090A
Name: IMAP_TCPNP Type: Text/text list Size: 3 Value: 1
Name: POP3_TCPNP Type: Text/text list Size: 3 Value: 1
Name: AdminPSuspendRange Type: Text/text list Size: 2 Value: [no
text]
Name: CatalogType Type: Text/text list Size: 3 Value: 0
Name: CatalogWeekDays Type: Text/text list Size: 25 Value:
1;2;3;4;5;6;7
Name: WeekDays Type: Text/text list Size: 25 Value:
1;2;3;4;5;6;7
Name: HTTP_CompMinS Type: Number/number list Size: 10 Value: 1
Name: HTTP_CompMaxS Type: Number/number list Size: 10 Value: 128
Name: HTTP_CompMM Type: Number/number list Size: 10 Value: 20
Name: HTTP_CSDefault Type: Text/text list Size: 4 Value: 98
Name: HTTP_Version Type: Number/number list Size: 10 Value: 1
Name: IIOP_IdleMinsAllowed Type: Number/number list Size: 10 Value: 60
Name: TRANSLOG_Path Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_1 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_1 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_2 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_2 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_3 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_3 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_4 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_4 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_5 Type: Text/text list Size: 2 Value: [no
text]
Chapter 10. Appendix A 433
Name: SCOS_ONLINE_5 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_6 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_6 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_7 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_7 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_8 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_8 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_9 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_9 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_10 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_10 Type: Text/text list Size: 2 Value: [no
text]
Name: DAOSMinObjSize Type: Text/text list Size: 7 Value: 64000
Name: DAOSBasePath Type: Text/text list Size: 6 Value: DAOS
Name: DB2AcWrn Type: Number/number list Size: 10 Value: 15
Name: tsAllowAccess Type: Names Size: 2 Value: [no
text]
Name: tsPHBAmax Type: Number/number list Size: 10 Value: 900
Name: tsPoffline Type: Number/number list Size: 10 Value: 1440
Name: Certificate Type: Text/text list Size: 910 Value:
0400B301 0DA1125D 07G01616 G00281BE
DAC44E03 G0030200 0120A200 DF0C6D00
6F7A25G0 0280G002 E10C6D00 6E7A2500
D20C6D00 1B092600 01A0G001 DF0C6D00
6F7A25G0 06E10C6D 006E7A25 00D20C6D
001B0926 004F3D6D 756E7365 434E3D39
2E33372E 33302E32 30362F4F 3D6D756E
73653081 9F300D06 092A8648 86F70D01
01010500 03818D00 30818902 818100BE
79779991 0E2DFD24 5AF6F1B3 A6995F36
7D5DADE7 945C3667 C71FC299 1F492BBF
36F69F63 40C8BF8D FCFC2A02 4275CB5A
BAB17D2B 05A9698C 223FD748 70C92F42
00FF28F0 8D81F77E FD4CA5AB EDF281DE
5C90458D 0F67C733 2DB70AAA 5BE8A57A
2AF45370 7AD29EFB 7D18408C 6C215E61
616306C8 22196973 37A81D8E BA40D902
03010001 CAD65DFB 6D93DBAE 7AA46724
16FAB20B 8AA4C377 DAF24DB5 D6B555B9
81857E90 2489581C 52545E8D 07732716
30A6C754 BE34060E E353A5F8 BDD49527
F97BD2EF DEE75526 BFE13B70 9D903F6D
778CE7EA F43FD383 F02D5AAF 2990E424
93FE2913 56F06CC6 DB6C4835 AD806676
BA18A69A 8C1EC94F 9ACC0307 112B7096
434 IBM Notes Traveler Hints and Tips for a Successful Deployment
1D103A2E
Name: AreaCode Type: Text/text list Size: 2 Value: [no
text]
Name: $LocationVersion Type: Text/text list Size: 3 Value: 2
Name: DB2AccessServer Type: Text/text list Size: 3 Value: 0
Name: IsVirDir Type: Number/number list Size: 10 Value: 0
Name: $UpdatedBy Type: Names Size: 54 Value:
CN=9.37.30.206/O=organization;CN=Administrator/O=organization
Name: $Revisions Type: Date-time/range Size: 22 Value:
09/04/2012 04:35:26 PM;09/05/2012 11:20:28 AM
******************** END DUMP OF DOCUMENT *************************************
--- Web Configuration Documents ---
*********************************************************************************
******************** BEGIN DUMP OF DOCUMENT *************************************
*********************************************************************************
UNID: 08B5C5099E6B2B7785257A6F006D0CE2
NoteId: 1CCE
Last Modifed: Wed Sep 05 11:25:59 EDT 2012
Create Date: Tue Sep 04 15:51:07 EDT 2012
Updated By: CN=9.37.30.206/O=organization
Name: MailSystem Type: Text/text list Size: 3 Value: 1
Name: MajVer Type: Number/number list Size: 10 Value: 8
Name: MinVer Type: Number/number list Size: 10 Value: 5
Name: QMRVer Type: Number/number list Size: 10 Value: 3
Name: QMUVer Type: Number/number list Size: 10 Value: 0
Name: HotVer Type: Number/number list Size: 10 Value: 0
Name: FixPVer Type: Number/number list Size: 10 Value: 0
Name: FlagsVer Type: Number/number list Size: 10 Value: 0
Name: ServerDirectoryName Type: Text/text list Size: 11 Value:
names.nsf
Name: Form Type: Text/text list Size: 8 Value:
Server
Name: Type Type: Text/text list Size: 8 Value:
Server
Name: ServerName Type: Names Size: 24 Value:
CN=9.37.30.206/O=organization
Name: ServerTitle Type: Text/text list Size: 2 Value: [no
text]
Name: Tasks Type: Text/text list Size: 14 Value: Mail
Routing
Name: Domain Type: Text/text list Size: 6 Value: matt
Name: SMTPListenerEnabled Type: Text/text list Size: 3 Value: 0
Name: SMTPFullHostDomain Type: Text/text list Size: 13 Value:
9.37.30.206
Name: ServerPhoneNumber Type: Text/text list Size: 2 Value: [no
text]
Name: LdISite Type: Text/text list Size: 3 Value: 0
Name: FormulaTimeout Type: Number/number list Size: 10 Value: 120
Name: Sametime Type: Text/text list Size: 3 Value: 0
Name: MasterAddressBook Type: Text/text list Size: 2 Value: [no
text]
Chapter 10. Appendix A 435
Name: FltRcvryScrpt Type: Text/text list Size: 2 Value: [no
text]
Name: LEDName Type: Text/text list Size: 2 Value: [no
text]
Name: TrustDircat Type: Text/text list Size: 2 Value: [no
text]
Name: FREnbld Type: Text/text list Size: 2 Value: [no
text]
Name: FltRcvryMax Type: Number/number list Size: 10 Value: 600
Name: NoCntDir Type: Text/text list Size: 3 Value: 1
Name: FltRcvryHng Type: Number/number list Size: 10 Value: 300
Name: FltRcvryCrsh Type: Number/number list Size: 10 Value: 3
Name: FltRcvryMin Type: Number/number list Size: 10 Value: 5
Name: FltRcvryNot Type: Names Size: 2 Value: [no
text]
Name: OutsideLine Type: Text/text list Size: 2 Value: [no
text]
Name: CallPre Type: Text/text list Size: 2 Value: [no
text]
Name: InternationalPrefix Type: Text/text list Size: 2 Value: [no
text]
Name: Suffix Type: Text/text list Size: 2 Value: [no
text]
Name: country Type: Text/text list Size: 2 Value: [no
text]
Name: LongDistancePrefix Type: Text/text list Size: 3 Value: 1
Name: RLANIdleTimeout Type: Text/text list Size: 2 Value: [no
text]
Name: TimeZone Type: Text/text list Size: 3 Value: 5
Name: MailServer Type: Names Size: 24 Value:
CN=9.37.30.206/O=organization
Name: DST Type: Text/text list Size: 3 Value: 1
Name: DefaultPassthruServer Type: Names Size: 2 Value: [no
text]
Name: InterNotes Type: Names Size: 2 Value: [no
text]
Name: FullAdmin Type: Names Size: 2 Value: [no
text]
Name: UnrestrictedList Type: Names Size: 2 Value: [no
text]
Name: Administrator Type: Names Size: 26 Value:
CN=Administrator/O=organization
Name: OnBehalfOfLst Type: Names Size: 2 Value: [no
text]
Name: DBAdmin Type: Names Size: 2 Value: [no
text]
Name: OnBehalfOfInvokerLst Type: Names Size: 2 Value: [no
text]
Name: RemoteAdmin Type: Names Size: 2 Value: [no
text]
Name: RestrictedList Type: Names Size: 2 Value: [no
text]
Name: VOAdmin Type: Names Size: 2 Value: [no
text]
436 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: PrivateList Type: Names Size: 2 Value: [no
text]
Name: SysAdmin Type: Names Size: 2 Value: [no
text]
Name: LibsLst Type: Names Size: 2 Value: [no
text]
Name: ResSysAdmin Type: Names Size: 2 Value: [no
text]
Name: ResSystemCmds Type: Text/text list Size: 2 Value: [no
text]
Name: NOIRestrictedList Type: Names Size: 2 Value: [no
text]
Name: BrowserAdminAccess Type: Names Size: 2 Value: [no
text]
Name: NOIUnrestrictedList Type: Names Size: 2 Value: [no
text]
Name: WhiteList Type: Text/text list Size: 2 Value: [no
text]
Name: WhiteListLog Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_AuthView Type: Text/text list Size: 10 Value:
($Users)
Name: AnonymousAccess Type: Text/text list Size: 3 Value: 0
Name: ServerCheckPasswords Type: Text/text list Size: 3 Value: 0
Name: AddressBookAccess Type: Text/text list Size: 2 Value: [no
text]
Name: PTAccess Type: Names Size: 2 Value: [no
text]
Name: DenyAccess Type: Names Size: 2 Value: [no
text]
Name: PTClients Type: Names Size: 2 Value: [no
text]
Name: CreateAccess Type: Names Size: 2 Value: [no
text]
Name: PTCallers Type: Names Size: 2 Value: [no
text]
Name: ReplicaAccess Type: Names Size: 2 Value: [no
text]
Name: PTTargets Type: Names Size: 2 Value: [no
text]
Name: TemplateAccess Type: Names Size: 2 Value: [no
text]
Name: AllowMonitors Type: Names Size: 3 Value: *
Name: DenyMonitors Type: Names Size: 2 Value: [no
text]
Name: TrustedSrvrs Type: Names Size: 2 Value: [no
text]
Name: Port_0 Type: Text/text list Size: 7 Value: TCPIP
Name: Enabled_0 Type: Text/text list Size: 3 Value: 1
Name: Port_1 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_1 Type: Text/text list Size: 3 Value: 0
Name: Port_2 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_2 Type: Text/text list Size: 3 Value: 0
Chapter 10. Appendix A 437
Name: Port_3 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_3 Type: Text/text list Size: 3 Value: 0
Name: Port_4 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_4 Type: Text/text list Size: 3 Value: 0
Name: Port_5 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_5 Type: Text/text list Size: 3 Value: 0
Name: Port_6 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_6 Type: Text/text list Size: 3 Value: 0
Name: Port_7 Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled_7 Type: Text/text list Size: 3 Value: 0
Name: HTTP_SSLKeyFile Type: Text/text list Size: 13 Value:
keyfile.kyr
Name: SSLProtocolVersion Type: Text/text list Size: 3 Value: 0
Name: SSLSiteCerts Type: Text/text list Size: 3 Value: 0
Name: SSLExpiredCerts Type: Text/text list Size: 3 Value: 1
Name: SSLCipherList Type: Text/text list Size: 24 Value:
04;05;0A;09;03
Name: SSLV2Enabled Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_Port Type: Number/number list Size: 10 Value: 80
Name: HTTP_NormalMode Type: Text/text list Size: 3 Value: 1
Name: HTTP_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: HTTP_TCPNP Type: Text/text list Size: 3 Value: 1
Name: HTTP_AllowAnonymous Type: Text/text list Size: 3 Value: 1
Name: HTTP_SSLPort Type: Number/number list Size: 10 Value: 443
Name: HTTP_SSLMode Type: Text/text list Size: 3 Value: 0
Name: HTTP_SSLCert Type: Text/text list Size: 3 Value: 0
Name: HTTP_SSLNP Type: Text/text list Size: 3 Value: 1
Name: HTTP_SSLAnonymous Type: Text/text list Size: 3 Value: 1
Name: LDAP_Port Type: Number/number list Size: 10 Value: 389
Name: LDAP_PortStatus Type: Text/text list Size: 3 Value: 1
Name: LDAP_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: LDAP_TCPNP Type: Text/text list Size: 3 Value: 1
Name: LDAP_AllowAnonymous Type: Text/text list Size: 3 Value: 1
Name: LDAP_SSLPort Type: Number/number list Size: 10 Value: 636
Name: LDAP_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: LDAP_SSLCert Type: Text/text list Size: 3 Value: 0
Name: LDAP_SSLNP Type: Text/text list Size: 3 Value: 0
Name: LDAP_SSLAnonymous Type: Text/text list Size: 3 Value: 1
Name: NNTP_Port Type: Number/number list Size: 10 Value: 119
Name: NNTP_PortStatus Type: Text/text list Size: 3 Value: 1
Name: NNTP_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: NNTP_TCPNP Type: Text/text list Size: 3 Value: 1
Name: NNTP_TCPAnonymous Type: Text/text list Size: 3 Value: 1
Name: NNTP_SSLPort Type: Number/number list Size: 10 Value: 563
Name: NNTP_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: NNTP_SSLCert Type: Text/text list Size: 3 Value: 0
Name: NNTP_SSLNP Type: Text/text list Size: 3 Value: 1
Name: NNTP_SSLAnonymous Type: Text/text list Size: 3 Value: 0
Name: IMAP_Port Type: Number/number list Size: 10 Value: 143
438 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: POP3_Port Type: Number/number list Size: 10 Value: 110
Name: SMTP_Port Type: Number/number list Size: 10 Value: 25
Name: Router_Port Type: Number/number list Size: 10 Value: 25
Name: IMAP_PortStatus Type: Text/text list Size: 3 Value: 1
Name: POP3_PortStatus Type: Text/text list Size: 3 Value: 1
Name: SMTP_PortStatus Type: Text/text list Size: 3 Value: 1
Name: Router_PortStatus Type: Text/text list Size: 3 Value: 1
Name: IMAP_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: POP3_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: SMTP_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: SMTP_TCPNP Type: Text/text list Size: 3 Value: 0
Name: SMTP_AllowAnonymous Type: Text/text list Size: 3 Value: 1
Name: IMAP_SSLPort Type: Number/number list Size: 10 Value: 993
Name: POP3_SSLPort Type: Number/number list Size: 10 Value: 995
Name: SMTP_SSLPort Type: Number/number list Size: 10 Value: 465
Name: Router_SSLPort Type: Number/number list Size: 10 Value: 465
Name: IMAP_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: POP3_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: SMTP_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: Router_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: IMAP_SSLCert Type: Text/text list Size: 3 Value: 0
Name: POP3_SSLCert Type: Text/text list Size: 3 Value: 0
Name: IMAP_SSLNP Type: Text/text list Size: 3 Value: 1
Name: POP3_SSLNP Type: Text/text list Size: 3 Value: 1
Name: SMTP_SSLNP Type: Text/text list Size: 3 Value: 0
Name: SMTP_SSLAnonymous Type: Text/text list Size: 3 Value: 1
Name: IIOP_Port Type: Number/number list Size: 10 Value: 63148
Name: IIOP_PortStatus Type: Text/text list Size: 3 Value: 1
Name: IIOP_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: IIOP_TCPNP Type: Text/text list Size: 3 Value: 1
Name: IIOP_AllowAnonymous Type: Text/text list Size: 3 Value: 1
Name: IIOP_SSLPort Type: Number/number list Size: 10 Value: 63149
Name: IIOP_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: IIOP_SSLNP Type: Text/text list Size: 3 Value: 0
Name: IIOP_SSLAnonymous Type: Text/text list Size: 3 Value: 1
Name: RDM_Port Type: Number/number list Size: 10 Value: 60000
Name: RDM_PortStatus Type: Text/text list Size: 3 Value: 1
Name: RDM_EnforceAccess Type: Text/text list Size: 3 Value: 0
Name: RDM_SSLPort Type: Number/number list Size: 10 Value: 60001
Name: RDM_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: DC_IP_Address Type: Text/text list Size: 2 Value: [no
text]
Name: DC_Port Type: Text/text list Size: 6 Value: 2050
Name: Proxy_HTTP Type: Text/text list Size: 2 Value: [no
text]
Name: Proxy_FTP Type: Text/text list Size: 2 Value: [no
text]
Name: Proxy_Gopher Type: Text/text list Size: 2 Value: [no
text]
Name: Proxy_SSL Type: Text/text list Size: 2 Value: [no
text]
Name: Proxy_NotesHTTP Type: Text/text list Size: 2 Value: [no
text]
Name: Proxy_SOCKs Type: Text/text list Size: 2 Value: [no
text]
Chapter 10. Appendix A 439
Name: No_Proxy Type: Text/text list Size: 2 Value: [no
text]
Name: AdminPMaxThreads Type: Number/number list Size: 10 Value: 3
Name: AdminPMailfileDelInt Type: Text/text list Size: 2 Value: [no
text]
Name: AdminPInterval Type: Text/text list Size: 2 Value: [no
text]
Name: AdminPWeekDays Type: Text/text list Size: 3 Value: 1
Name: AdminPDailyTime Type: Text/text list Size: 2 Value: [no
text]
Name: AdminPDelayedTime Type: Text/text list Size: 2 Value: [no
text]
Name: AdminPNameChangeExpiration Type: Number/number list Size: 10 Value: 21
Name: InboxTrimDays Type: Text/text list Size: 3 Value: 7
Name: AdminPLogSetting Type: Text/text list Size: 3 Value: 0
Name: InboxTrimTime Type: Date-time/range Size: 10 Value:
01:00:00 AM
Name: AdminPSuspendStart Type: Text/text list Size: 2 Value: [no
text]
Name: InboxTrimLoc Type: Text/text list Size: 3 Value: 2
Name: AdminPSuspendEnd Type: Text/text list Size: 2 Value: [no
text]
Name: InboxTrimUsers Type: Names Size: 2 Value: [no
text]
Name: gracedays Type: Number/number list Size: 10 Value: 90
Name: MaxRemDocs Type: Number/number list Size: 10 Value: 500
Name: SaveUnread Type: Text/text list Size: 2 Value: [no
text]
Name: ReloadTime Type: Date-time/range Size: 10 Value:
12:00:00 AM
Name: StartTime Type: Date-time/range Size: 10 Value:
08:00:00 AM
Name: MaxStartTime Type: Date-time/range Size: 10 Value:
08:00:00 PM
Name: EndTime Type: Date-time/range Size: 10 Value:
08:00:00 PM
Name: MaxEndTime Type: Date-time/range Size: 10 Value:
08:00:00 AM
Name: ConcurrentAgents Type: Number/number list Size: 10 Value: 1
Name: MaxConcurrentAgents Type: Number/number list Size: 10 Value: 2
Name: MaxExecution Type: Number/number list Size: 10 Value: 10
Name: MaxMaxExecution Type: Number/number list Size: 10 Value: 15
Name: PercentTime Type: Number/number list Size: 10 Value: 50
Name: MaxPercentTime Type: Number/number list Size: 10 Value: 70
Name: CatalogDomainScope Type: Names Size: 2 Value: [no
text]
Name: CatalogEnabled Type: Text/text list Size: 3 Value: 0
Name: CatalogSchedule Type: Date-time/range Size: 22 Value:
12:01:00 AM-11:59:00 PM
Name: CatalogInterval Type: Number/number list Size: 10 Value: 60
Name: CatalogIndexerScope Type: Names Size: 2 Value: [no
text]
Name: EDFilenames Type: Text/text list Size: 2 Value: [no
text]
Name: Enabled Type: Text/text list Size: 3 Value: 0
440 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: Schedule Type: Date-time/range Size: 22 Value:
08:00:00 AM-10:00:00 PM
Name: Interval Type: Number/number list Size: 10 Value: 360
Name: ICMClusterName Type: Text/text list Size: 2 Value: [no
text]
Name: ICMNotesPort Type: Text/text list Size: 2 Value: [no
text]
Name: ICMSSLKeyfile Type: Text/text list Size: 13 Value:
keyfile.kyr
Name: ICM_BrowseDatabases Type: Text/text list Size: 3 Value: 0
Name: ICMConfiguration Type: Text/text list Size: 3 Value: 1
Name: ICMHostname Type: Text/text list Size: 2 Value: [no
text]
Name: ICMRemoteServerName Type: Text/text list Size: 2 Value: [no
text]
Name: ICMHTTP_Port Type: Number/number list Size: 10 Value: 80
Name: ICMHTTP_PortStatus Type: Text/text list Size: 3 Value: 1
Name: ICMHTTP_SSLPort Type: Number/number list Size: 10 Value: 443
Name: ICMHTTP_SSLStatus Type: Text/text list Size: 3 Value: 0
Name: WebDbName Type: Text/text list Size: 9 Value:
web.nsf
Name: WebAllow Type: Text/text list Size: 3 Value: *
Name: WebServices Type: Text/text list Size: 23 Value:
HTTP;FTP;GOPHER
Name: WebDeny Type: Text/text list Size: 2 Value: [no
text]
Name: WebRetrievers Type: Number/number list Size: 10 Value: 50
Name: WebLogLevel Type: Text/text list Size: 3 Value: 0
Name: WebUpdateCache Type: Text/text list Size: 3 Value: 1
Name: SMTP_Domain Type: Text/text list Size: 2 Value: [no
text]
Name: RDMgrEnbld Type: Text/text list Size: 3 Value: 0
Name: RDOff Type: Number/number list Size: 10 Value: 24
Name: RDWait Type: Number/number list Size: 10 Value: 0
Name: HTTP_HostName Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_HomeURL Type: Text/text list Size: 11 Value:
/traveler
Name: HTTP_BindToHostName Type: Text/text list Size: 3 Value: 0
Name: HTTP_HTMLDir Type: Text/text list Size: 13 Value:
domino\html
Name: HTTP_DNSLookup Type: Text/text list Size: 3 Value: 0
Name: HTTP_IconsDir Type: Text/text list Size: 14 Value:
domino\icons
Name: HTTP_DNSLookupCache Type: Text/text list Size: 3 Value: 1
Name: HTTP_IconsPath Type: Text/text list Size: 8 Value:
/icons
Name: HTTP_DNSCacheSize Type: Number/number list Size: 10 Value: 256
Name: HTTP_CGIDir Type: Text/text list Size: 16 Value:
domino\cgi-bin
Name: HTTP_DNSCacheFoundTimeout Type: Number/number list Size: 10 Value: 120
Name: HTTP_CGIPath Type: Text/text list Size: 10 Value:
/cgi-bin
Name: HTTP_DNSCacheNotFoundTimeout Type: Number/number list Size: 10 Value: 240
Name: HTTP_MaxActiveThreads Type: Number/number list Size: 10 Value: 100
Chapter 10. Appendix A 441
Name: HTTP_DatabaseBrowsing Type: Text/text list Size: 3 Value: 0
Name: HTTP_AccessLogFormat Type: Text/text list Size: 3 Value: 0
Name: HTTP_MaxRequests Type: Number/number list Size: 10 Value: 1
Name: HTTP_LogTime Type: Text/text list Size: 3 Value: 0
Name: HTTP_MinActiveThreads Type: Number/number list Size: 10 Value: 20
Name: HTTP_LogFileDuration Type: Text/text list Size: 3 Value: 0
Name: HTTP_Welcome Type: Text/text list Size: 13 Value:
default.htm
Name: HTTP_MaxLogEntrySize Type: Number/number list Size: 10 Value: 10
Name: HTTP_MaxCachedCommands Type: Text/text list Size: 5 Value: 128
Name: HTTP_MaxLogFileSize Type: Number/number list Size: 10 Value: 0
Name: HTTP_Audience Type: Text/text list Size: 3 Value: 0
Name: HTTP_LogToFiles Type: Text/text list Size: 3 Value: 0
Name: HTTP_FilterLibrary Type: Text/text list Size: 10 Value:
ndolextn
Name: HTTP_LogToDomLog Type: Text/text list Size: 3 Value: 0
Name: HTTP_LogDirectory Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_ExcludeURLs Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_AccessLog Type: Text/text list Size: 8 Value:
access
Name: HTTP_ExcludeMethods Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_AgentLog Type: Text/text list Size: 7 Value: agent
Name: HTTP_ExcludeMIMETypes Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_RefererLog Type: Text/text list Size: 9 Value:
referer
Name: HTTP_ExcludeUserAgents Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_ErrorLog Type: Text/text list Size: 7 Value: error
Name: HTTP_ExcludeReturnCodes Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_CGIErrorLog Type: Text/text list Size: 11 Value:
cgi-error
Name: HTTP_NoLog Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_11Connections Type: Text/text list Size: 3 Value: 1
Name: HTTP_InputTimeout Type: Number/number list Size: 10 Value: 2
Name: HTTP_Max11Requests Type: Number/number list Size: 10 Value: 100
Name: HTTP_OutputTimeout Type: Number/number list Size: 10 Value: 20
Name: HTTP_PersistentTimeout Type: Number/number list Size: 10 Value: 180
Name: HTTP_ScriptTimeout Type: Number/number list Size: 10 Value: 5
Name: HTTP_RequestTimeout Type: Number/number list Size: 10 Value: 60
Name: HTTP_IdleThreadTimeout Type: Number/number list Size: 10 Value: 0
Name: HTTP_RNInputTimeout Type: Number/number list Size: 10 Value: 75
Name: HTTP_RNOutputTimeout Type: Number/number list Size: 10 Value: 180
Name: HTTP_RNCGITimeout Type: Number/number list Size: 10 Value: 180
Name: HTTP_ListenQueueSize Type: Number/number list Size: 10 Value: 512
Name: HTTP_MaxURLBytes Type: Number/number list Size: 10 Value: 4
Name: HTTP_MaxConcurrentNetwkSessions Type: Number/number list Size: 10 Value: 2000
Name: HTTP_MaxURLPathSegments Type: Number/number list Size: 10 Value: 64
Name: HTTP_AllowDenyPriority Type: Text/text list Size: 3 Value: 1
Name: HTTP_MaxHeaderLines Type: Number/number list Size: 10 Value: 48
442 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: HTTP_AllowIPList Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_MaxHeaderBytes Type: Number/number list Size: 10 Value: 16
Name: HTTP_DenyIPList Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_MaxContentLength Type: Number/number list Size: 10 Value: 10000
Name: HTTP_Comp Type: Text/text list Size: 3 Value: 0
Name: HTTP_CompEUA Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_CompIMT Type: Text/text list Size: 27 Value:
text/*;application/*
Name: HTTP_CompEMT Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_EnableSessionAuth Type: Text/text list Size: 3 Value: 0
Name: HTTP_JavaServletSupport Type: Text/text list Size: 3 Value: 0
Name: HTTP_IdleSessionTimeout Type: Number/number list Size: 10 Value: 30
Name: HTTP_SSOCfg Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_ServletPath Type: Text/text list Size: 10 Value:
/servlet
Name: HTTP_ForceLoginOnSSL Type: Text/text list Size: 3 Value: 0
Name: HTTP_JSClasspath Type: Text/text list Size: 16 Value:
domino\servlet
Name: HTTP_MaxActiveSessions Type: Number/number list Size: 10 Value: 1000
Name: HTTP_JSFileExtensions Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_EnableJSessions Type: Text/text list Size: 3 Value: 1
Name: HTTP_CompanionStack Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_IdleJSTimeout Type: Number/number list Size: 10 Value: 30
Name: HTTP_RedirectUseHTTPS Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_MaxActiveJSessions Type: Number/number list Size: 10 Value: 1000
Name: HTTP_RedirectServerName Type: Text/text list Size: 2 Value: [no
text]
Name: HTTP_EnableJSPersistence Type: Text/text list Size: 3 Value: 0
Name: HTTP_RedirectPortNo Type: Number/number list Size: 10 Value: 80
Name: HTTP_MaxCachedDesigns Type: Text/text list Size: 5 Value: 128
Name: HTTP_maxPostDataLength Type: Text/text list Size: 7 Value: 10000
Name: HTTP_MaxCachedUsers Type: Text/text list Size: 4 Value: 64
Name: HTTP_compressUploadedFiles Type: Text/text list Size: 3 Value: 0
Name: HTTP_ExpireCachedUsers Type: Text/text list Size: 5 Value: 120
Name: HTTP_PrfCookieOption Type: Text/text list Size: 3 Value: 2
Name: HTTP_ResourceLang Type: Text/text list Size: 4 Value: en
Name: HTTP_useUserLocale Type: Text/text list Size: 3 Value: 1
Name: HTTP_AltResourceLang Type: Text/text list Size: 4 Value: en
Name: HTTP_ImageFormat Type: Text/text list Size: 3 Value: 0
Name: HTTP_UTF8 Type: Text/text list Size: 3 Value: 1
Name: HTTP_ImageProgressive Type: Text/text list Size: 3 Value: 1
Name: HTTP_NoUTF8Forms Type: Text/text list Size: 3 Value: 0
Name: HTTP_ImageQuality Type: Number/number list Size: 10 Value: 75
Name: HTTP_DefViewRows Type: Number/number list Size: 10 Value: 30
Name: HTTP_CS5Default Type: Text/text list Size: 3 Value: 2
Name: HTTP_MaxViewRows Type: Number/number list Size: 10 Value: 1000
Name: HTTP_CSWestern Type: Text/text list Size: 4 Value: 32
Chapter 10. Appendix A 443
Name: HTTP_DefSearchMax Type: Number/number list Size: 10 Value: 250
Name: HTTP_CSCentralEuropean Type: Text/text list Size: 4 Value: 80
Name: HTTP_MaxSearchMax Type: Number/number list Size: 10 Value: 1000
Name: HTTP_CSJapanese Type: Text/text list Size: 4 Value: 18
Name: HTTP_GenBangUrls Type: Text/text list Size: 3 Value: 0
Name: HTTP_CSTaiwanese Type: Text/text list Size: 4 Value: 26
Name: HTTP_EnableRedirectCmd Type: Text/text list Size: 3 Value: 1
Name: HTTP_CSChinese Type: Text/text list Size: 6 Value: 3377
Name: HTTP_CSKorean Type: Text/text list Size: 4 Value: 24
Name: HTTP_CSCyrillic Type: Text/text list Size: 6 Value: 3308
Name: HTTP_CSGreek Type: Text/text list Size: 4 Value: 83
Name: HTTP_CacheDir Type: Text/text list Size: 14 Value:
domino\cache
Name: HTTP_CSTurkish Type: Text/text list Size: 4 Value: 84
Name: HTTP_MaxCacheSize Type: Number/number list Size: 10 Value: 50
Name: HTTP_CSThai Type: Text/text list Size: 5 Value: 144
Name: HTTP_DeleteCache Type: Text/text list Size: 3 Value: 0
Name: HTTP_CSBaltic Type: Text/text list Size: 4 Value: 87
Name: HTTP_EnableGC Type: Text/text list Size: 3 Value: 1
Name: HTTP_CSArabic Type: Text/text list Size: 4 Value: 86
Name: HTTP_GCInterval Type: Number/number list Size: 10 Value: 60
Name: HTTP_CSHebrew Type: Text/text list Size: 6 Value: 3356
Name: HTTP_CSVietnamese Type: Text/text list Size: 6 Value: 3310
Name: HTTP_CSIndic Type: Text/text list Size: 5 Value: 171
Name: HTTP_AutoDetect Type: Text/text list Size: 3 Value: 0
Name: HTTP_asynchronizeAgents Type: Text/text list Size: 3 Value: 0
Name: HTTP_webAgentTimeout Type: Number/number list Size: 10 Value: 0
Name: HTTP_HeaderCharset Type: Text/text list Size: 3 Value: 1
Name: HTTP_MetaCharset Type: Text/text list Size: 3 Value: 0
Name: HTTP_DomWSAppSpace Type: Text/text list Size: 3 Value: 1
Name: HTTP_DomWSAddinMaxThreads Type: Number/number list Size: 10 Value: 20
Name: HTTP_DomWSForceFromValue Type: Text/text list Size: 3 Value: 1
Name: HTTP_EnabledServices Type: Text/text list Size: 2 Value: [no
text]
Name: IIOP_HtmlDir Type: Text/text list Size: 2 Value: [no
text]
Name: IIOP_IORHost Type: Text/text list Size: 2 Value: [no
text]
Name: IIOP_ThreadPoolSize Type: Number/number list Size: 10 Value: 10
Name: NNTP_Admin Type: Names Size: 2 Value: [no
text]
Name: NNTPLogLevel Type: Text/text list Size: 3 Value: 0
Name: NNTPRdrDefaultAccess Type: Text/text list Size: 3 Value: 1
Name: NNTPRdrDefaultExceptions Type: Text/text list Size: 2 Value: [no
text]
Name: NNTPAllowRdrPosting Type: Text/text list Size: 3 Value: 1
Name: NNTPAllowFeedPosting Type: Text/text list Size: 3 Value: 1
Name: NNTPMaxRdrPostSize Type: Number/number list Size: 10 Value: 1024
Name: NNTPMaxFeedPostSize Type: Number/number list Size: 10 Value: 1024
Name: NNTPMaxRdrConSize Type: Number/number list Size: 10 Value: 10
Name: NNTPMaxFeedConSize Type: Number/number list Size: 10 Value: 100
Name: NNTPRdrConTimeout Type: Number/number list Size: 10 Value: 600
Name: NNTPMaxFeedConnections Type: Number/number list Size: 10 Value: 5
Name: NNTPMaxRdrConnections Type: Number/number list Size: 10 Value: 20
444 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: SMTPGlobalDomain Type: Text/text list Size: 2 Value: [no
text]
Name: SMTPPollingPeriod Type: Number/number list Size: 10 Value: 120
Name: SMTPAdministrator Type: Names Size: 2 Value: [no
text]
Name: SMTPWork Type: Text/text list Size: 2 Value: [no
text]
Name: SMTPLogLevel Type: Text/text list Size: 3 Value: 1
Name: SMTPEnableHK Type: Text/text list Size: 3 Value: 1
Name: SMTPDailyHKAt Type: Date-time/range Size: 10 Value:
01:00:00 AM
Name: SMTP822HeaderOption Type: Text/text list Size: 3 Value: 2
Name: SMTPAddrResolutionCntl Type: Text/text list Size: 3 Value: 3
Name: SMTPEncodingScheme Type: Text/text list Size: 3 Value: 1
Name: SMTPRetryAttempts Type: Number/number list Size: 10 Value: 8
Name: SMTPMessageContent Type: Text/text list Size: 3 Value: T
Name: SMTPRetryInterval Type: Number/number list Size: 10 Value: 15
Name: SMTPReturnReceipts Type: Text/text list Size: 3 Value: 1
Name: SMTPTransferMode Type: Text/text list Size: 3 Value: 1
Name: SMTPLanguageParam Type: Text/text list Size: 2 Value: [no
text]
Name: SMTPCharSetDetect Type: Text/text list Size: 3 Value: 2
Name: SMTPTypeface Type: Text/text list Size: 3 Value: 3
Name: SMTPPointSize Type: Text/text list Size: 3 Value: 9
Name: SMTPMacAttachConvertOption Type: Text/text list Size: 3 Value: 1
Name: SMTPMaxInbTasks Type: Number/number list Size: 10 Value: 3
Name: SMTPMaxOutbTasks Type: Number/number list Size: 10 Value: 3
Name: SMTPMaxOutbMsgSize Type: Number/number list Size: 10 Value: 0
Name: DiskC Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtC Type: Text/text list Size: 3 Value: 1
Name: DiskO Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtO Type: Text/text list Size: 3 Value: 1
Name: DiskD Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtD Type: Text/text list Size: 3 Value: 1
Name: DiskP Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtP Type: Text/text list Size: 3 Value: 1
Name: DiskE Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtE Type: Text/text list Size: 3 Value: 1
Name: DiskQ Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtQ Type: Text/text list Size: 3 Value: 1
Name: DiskF Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtF Type: Text/text list Size: 3 Value: 1
Name: DiskR Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtR Type: Text/text list Size: 3 Value: 1
Name: DiskG Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtG Type: Text/text list Size: 3 Value: 1
Chapter 10. Appendix A 445
Name: DiskS Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtS Type: Text/text list Size: 3 Value: 1
Name: DiskH Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtH Type: Text/text list Size: 3 Value: 1
Name: DiskT Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtT Type: Text/text list Size: 3 Value: 1
Name: DiskI Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtI Type: Text/text list Size: 3 Value: 1
Name: DiskU Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtU Type: Text/text list Size: 3 Value: 1
Name: DiskJ Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtJ Type: Text/text list Size: 3 Value: 1
Name: DiskV Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtV Type: Text/text list Size: 3 Value: 1
Name: DiskK Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtK Type: Text/text list Size: 3 Value: 1
Name: DiskW Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtW Type: Text/text list Size: 3 Value: 1
Name: DiskL Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtL Type: Text/text list Size: 3 Value: 1
Name: DiskX Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtX Type: Text/text list Size: 3 Value: 1
Name: DiskM Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtM Type: Text/text list Size: 3 Value: 1
Name: DiskY Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtY Type: Text/text list Size: 3 Value: 1
Name: DiskN Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtN Type: Text/text list Size: 3 Value: 1
Name: DiskZ Type: Text/text list Size: 2 Value: [no
text]
Name: SpndlCtZ Type: Text/text list Size: 3 Value: 1
Name: Location Type: Text/text list Size: 2 Value: [no
text]
Name: Department Type: Text/text list Size: 2 Value: [no
text]
Name: Comment Type: Text/text list Size: 2 Value: [no
text]
Name: ServerDescription Type: Rich text Size: 104 Value: [no
text]
Name: TRANSLOG_Status Type: Text/text list Size: 3 Value: 0
Name: TRANSLOG_Style Type: Text/text list Size: 3 Value: 0
446 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: TRANSLOG_UseAll Type: Text/text list Size: 3 Value: 0
Name: TRANSLOG_MaxSize Type: Text/text list Size: 2 Value: [no
text]
Name: TRANSLOG_AutoFixup Type: Text/text list Size: 3 Value: 1
Name: TRANSLOG_Performance Type: Text/text list Size: 3 Value: 2
Name: QtaMthd Type: Text/text list Size: 3 Value: 2
Name: STVPClientPort Type: Number/number list Size: 10 Value: 1533
Name: STPort_T120 Type: Number/number list Size: 10 Value: 8081
Name: STPort_VP Type: Number/number list Size: 10 Value: 1516
Name: STPort_T123 Type: Number/number list Size: 10 Value: 1503
Name: STCommunityHTTPSPort Type: Number/number list Size: 10 Value: 1533
Name: STMeetingHTTPSPort Type: Number/number list Size: 10 Value: 8081
Name: STCommunityHTTPTunneling Type: Text/text list Size: 3 Value: 1
Name: STCommunityHTTPTunnelingPort Type: Number/number list Size: 10 Value: 8082
Name: STMeetingHTTPTunnelingPort Type: Number/number list Size: 10 Value: 8081
Name: STMaxCommunityConnections Type: Number/number list Size: 10 Value: 8000
Name: ST_HostName Type: Text/text list Size: 2 Value: [no
text]
Name: STDirChunkSize Type: Number/number list Size: 10 Value: 100
Name: ST_BindToHostName Type: Text/text list Size: 3 Value: 0
Name: STDirRefreshInterval Type: Number/number list Size: 10 Value: 60
Name: STActiveMeetingsLimitEnabled Type: Text/text list Size: 2 Value: [no
text]
Name: STActiveMeetingsLimit Type: Number/number list Size: 10 Value: 100
Name: STConfigRefreshInterval Type: Number/number list Size: 10 Value: 60
Name: STTotalUsersLimitEnabled Type: Text/text list Size: 2 Value: [no
text]
Name: STTotalUsersLimit Type: Number/number list Size: 10 Value: 500
Name: STMeetingUsersLimitEnabled Type: Text/text list Size: 2 Value: [no
text]
Name: STMeetingUsersLimit Type: Number/number list Size: 10 Value: 50
Name: STAutoExtendMeetingEnabled Type: Text/text list Size: 3 Value: 1
Name: STMeetingExtendTime Type: Number/number list Size: 10 Value: 15
Name: STLogTime Type: Text/text list Size: 3 Value: 0
Name: STCommunityLogin Type: Text/text list Size: 3 Value: 1
Name: STCommunityLoginFailed Type: Text/text list Size: 2 Value: [no
text]
Name: STCommunityTotalConnections Type: Text/text list Size: 2 Value: [no
text]
Name: STLogHistory Type: Number/number list Size: 10 Value: 30
Name: STCommunityLogUsageFrequency Type: Number/number list Size: 10 Value: 10
Name: STLogToFiles Type: Text/text list Size: 3 Value: 0
Name: STMeetingLogEvents Type: Text/text list Size: 3 Value: 1
Name: STMeetingLogParticipants Type: Text/text list Size: 3 Value: 1
Name: STLogToNSF Type: Text/text list Size: 3 Value: 1
Name: STLogFileName Type: Text/text list Size: 14 Value:
sametime.log
Name: SHARED_MAIL Type: Text/text list Size: 3 Value: 0
Name: SCOS_DIR_1 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_1 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_1 Type: Text/text list Size: 2 Value: [no
text]
Chapter 10. Appendix A 447
Name: SCOS_DIR_2 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_2 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_2 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_3 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_3 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_3 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_4 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_4 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_4 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_5 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_5 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_5 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_6 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_6 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_6 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_7 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_7 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_7 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_8 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_8 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_8 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_9 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_9 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_9 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_10 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_MAX_SIZE_MB_10 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ACTIVE_10 Type: Text/text list Size: 2 Value: [no
text]
Name: DAOSEnable Type: Text/text list Size: 3 Value: 0
448 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: DAOSObjDelete Type: Number/number list Size: 10 Value: 30
Name: DB2Host Type: Text/text list Size: 2 Value: [no
text]
Name: DB2Port Type: Text/text list Size: 2 Value: [no
text]
Name: DB2Inst Type: Text/text list Size: 2 Value: [no
text]
Name: DB2Db Type: Text/text list Size: 2 Value: [no
text]
Name: DB2Dir Type: Text/text list Size: 2 Value: [no
text]
Name: DB2Def Type: Text/text list Size: 3 Value: 1
Name: DB2UDFSrv Type: Text/text list Size: 2 Value: [no
text]
Name: DB2UDFPath Type: Text/text list Size: 2 Value: [no
text]
Name: DB2GroupMax Type: Number/number list Size: 10 Value: 10
Name: DB2DefUser Type: Text/text list Size: 2 Value: [no
text]
Name: DB2QVRows Type: Number/number list Size: 10 Value: 500
Name: tsMaxMem Type: Number/number list Size: 10 Value: 512
Name: tsIPCPort Type: Number/number list Size: 10 Value: 50125
Name: tsIPCPort2 Type: Number/number list Size: 10 Value: 50126
Name: tsExternalURL Type: Text/text list Size: 29 Value:
http://9.37.30.206/traveler
Name: tsAddressBookAccess Type: Text/text list Size: 2 Value: [no
text]
Name: tsDenyAccess Type: Names Size: 2 Value: [no
text]
Name: tsUserCMD Type: Text/text list Size: 3 Value: 0
Name: tsUserWipe Type: Text/text list Size: 3 Value: 1
Name: tsLogLevel Type: Text/text list Size: 3 Value: 3
Name: tsTrcLevel Type: Text/text list Size: 3 Value: 0
Name: tsTrcCmp Type: Text/text list Size: 3 Value: *
Name: tsTrcSize Type: Number/number list Size: 10 Value: 50
Name: tsTrcFiles Type: Number/number list Size: 10 Value: 10
Name: tsTrcPriv Type: Text/text list Size: 17 Value:
2;4;8;16
Name: tsPollTime Type: Number/number list Size: 10 Value: 3
Name: devPTCPP Type: Number/number list Size: 10 Value: 8642
Name: tsPHBeatAlg Type: Text/text list Size: 3 Value: 2
Name: tsPHBFixed Type: Number/number list Size: 10 Value: 55
Name: tsPHBInitial Type: Number/number list Size: 10 Value: 30
Name: tsPHBAmim Type: Number/number list Size: 10 Value: 30
Name: tsPHBAmaxsec Type: Number/number list Size: 10 Value: 15
Name: tsPHBAretry Type: Number/number list Size: 10 Value: 30
Name: tsPofflinehr Type: Number/number list Size: 10 Value: 24
Name: tsPcleanup Type: Number/number list Size: 10 Value: 30
Name: Owner Type: Authors Size: 2 Value: [no
text]
Name: LocalAdmin Type: Authors Size: 2 Value: [no
text]
Name: PKMinWidth Type: Text/text list Size: 3 Value: 0
Name: PKMaxWidth Type: Text/text list Size: 6 Value: 1024
Name: PKDefWidth Type: Text/text list Size: 6 Value: 1024
Chapter 10. Appendix A 449
Name: PKMaxAge Type: Number/number list Size: 10 Value: 36500
Name: PKMinDate Type: Date-time/range Size: 10 Value:
08/01/1977
Name: PKDueDate Type: Date-time/range Size: 10 Value:
09/04/2112
Name: PKOldKeyDays Type: Number/number list Size: 10 Value: 365
Name: ChangeRequest Type: Text/text list Size: 2 Value: [no
text]
Name: DocumentAccess Type: Authors Size: 18 Value:
[ServerModifier]
Name: BookmarkDB Type: Text/text list Size: 14 Value:
bookmark.nsf
Name: ServerPlatform Type: Text/text list Size: 32 Value:
Windows/2003 5.2 Intel Pentium
Name: ASPServer Type: Text/text list Size: 3 Value: 0
Name: DAOSWarned Type: Text/text list Size: 3 Value: 0
Name: $ServerMain Type: Number/number list Size: 10 Value: 0
Name: $Server_Ports_Tabs Type: Number/number list Size: 10 Value: 0
Name: $Server_Ports_Internet2_Tabs Type: Number/number list Size: 10 Value: 0
Name: $Server_Tasks_Tabs Type: Number/number list Size: 10 Value: 0
Name: $Server_InetProt_Tabs Type: Number/number list Size: 10 Value: 0
Name: $Server_MTA_Tabs Type: Number/number list Size: 10 Value: 0
Name: FltRcvryMD Type: Text/text list Size: 6 Value: 8530
Name: ServerBuildNumber Type: Text/text list Size: 15 Value:
Release 8.5.3
Name: ClusterName Type: Text/text list Size: 2 Value: [no
text]
Name: ServerCPUCount Type: Number/number list Size: 10 Value: 2
Name: NSDEnbld Type: Text/text list Size: 3 Value: 1
Name: CfgNABonly Type: Text/text list Size: 3 Value: 0
Name: AllowAccess Type: Names Size: 2 Value: [no
text]
Name: Protocol_0 Type: Text/text list Size: 5 Value: TCP
Name: NetName_0 Type: Text/text list Size: 15 Value: TCPIP
Network
Name: NetAddr_0 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocol_1 Type: Text/text list Size: 2 Value: [no
text]
Name: NetName_1 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_1 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocol_2 Type: Text/text list Size: 2 Value: [no
text]
Name: NetName_2 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_2 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocol_3 Type: Text/text list Size: 2 Value: [no
text]
Name: NetName_3 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_3 Type: Text/text list Size: 13 Value:
9.37.30.206
450 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: Protocol_4 Type: Text/text list Size: 2 Value: [no
text]
Name: NetName_4 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_4 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocol_5 Type: Text/text list Size: 2 Value: [no
text]
Name: NetName_5 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_5 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocol_6 Type: Text/text list Size: 2 Value: [no
text]
Name: NetName_6 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_6 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocol_7 Type: Text/text list Size: 2 Value: [no
text]
Name: NetName_7 Type: Text/text list Size: 2 Value: [no
text]
Name: NetAddr_7 Type: Text/text list Size: 13 Value:
9.37.30.206
Name: EnabledList Type: Text/text list Size: 28 Value:
1;0;0;0;0;0;0;0
Name: Ports Type: Text/text list Size: 7 Value: TCPIP
Name: Network Type: Text/text list Size: 15 Value: TCPIP
Network
Name: NetAddresses Type: Text/text list Size: 13 Value:
9.37.30.206
Name: Protocols Type: Text/text list Size: 5 Value: TCP
Name: SSLStrongEncryption Type: Text/text list Size: 14 Value:
03040506090A
Name: IMAP_TCPNP Type: Text/text list Size: 3 Value: 1
Name: POP3_TCPNP Type: Text/text list Size: 3 Value: 1
Name: AdminPSuspendRange Type: Text/text list Size: 2 Value: [no
text]
Name: CatalogType Type: Text/text list Size: 3 Value: 0
Name: CatalogWeekDays Type: Text/text list Size: 25 Value:
1;2;3;4;5;6;7
Name: WeekDays Type: Text/text list Size: 25 Value:
1;2;3;4;5;6;7
Name: HTTP_CompMinS Type: Number/number list Size: 10 Value: 1
Name: HTTP_CompMaxS Type: Number/number list Size: 10 Value: 128
Name: HTTP_CompMM Type: Number/number list Size: 10 Value: 20
Name: HTTP_CSDefault Type: Text/text list Size: 4 Value: 98
Name: HTTP_Version Type: Number/number list Size: 10 Value: 1
Name: IIOP_IdleMinsAllowed Type: Number/number list Size: 10 Value: 60
Name: TRANSLOG_Path Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_1 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_1 Type: Text/text list Size: 2 Value: [no
text]
Chapter 10. Appendix A 451
Name: SCOS_DIR_ACTIVE_FILES_2 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_2 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_3 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_3 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_4 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_4 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_5 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_5 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_6 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_6 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_7 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_7 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_8 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_8 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_9 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_9 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_DIR_ACTIVE_FILES_10 Type: Text/text list Size: 2 Value: [no
text]
Name: SCOS_ONLINE_10 Type: Text/text list Size: 2 Value: [no
text]
Name: DAOSMinObjSize Type: Text/text list Size: 7 Value: 64000
Name: DAOSBasePath Type: Text/text list Size: 6 Value: DAOS
Name: DB2AcWrn Type: Number/number list Size: 10 Value: 15
Name: tsAllowAccess Type: Names Size: 2 Value: [no
text]
Name: tsPHBAmax Type: Number/number list Size: 10 Value: 900
Name: tsPoffline Type: Number/number list Size: 10 Value: 1440
Name: Certificate Type: Text/text list Size: 910 Value:
0400B301 0DA1125D 07G01616 G00281BE
DAC44E03 G0030200 0120A200 DF0C6D00
6F7A25G0 0280G002 E10C6D00 6E7A2500
D20C6D00 1B092600 01A0G001 DF0C6D00
6F7A25G0 06E10C6D 006E7A25 00D20C6D
001B0926 004F3D6D 756E7365 434E3D39
2E33372E 33302E32 30362F4F 3D6D756E
73653081 9F300D06 092A8648 86F70D01
01010500 03818D00 30818902 818100BE
79779991 0E2DFD24 5AF6F1B3 A6995F36
7D5DADE7 945C3667 C71FC299 1F492BBF
452 IBM Notes Traveler Hints and Tips for a Successful Deployment
36F69F63 40C8BF8D FCFC2A02 4275CB5A
BAB17D2B 05A9698C 223FD748 70C92F42
00FF28F0 8D81F77E FD4CA5AB EDF281DE
5C90458D 0F67C733 2DB70AAA 5BE8A57A
2AF45370 7AD29EFB 7D18408C 6C215E61
616306C8 22196973 37A81D8E BA40D902
03010001 CAD65DFB 6D93DBAE 7AA46724
16FAB20B 8AA4C377 DAF24DB5 D6B555B9
81857E90 2489581C 52545E8D 07732716
30A6C754 BE34060E E353A5F8 BDD49527
F97BD2EF DEE75526 BFE13B70 9D903F6D
778CE7EA F43FD383 F02D5AAF 2990E424
93FE2913 56F06CC6 DB6C4835 AD806676
BA18A69A 8C1EC94F 9ACC0307 112B7096
1D103A2E
Name: AreaCode Type: Text/text list Size: 2 Value: [no
text]
Name: $LocationVersion Type: Text/text list Size: 3 Value: 2
Name: DB2AccessServer Type: Text/text list Size: 3 Value: 0
Name: IsVirDir Type: Number/number list Size: 10 Value: 0
Name: $UpdatedBy Type: Names Size: 54 Value:
CN=9.37.30.206/O=organization;CN=Administrator/O=organization
Name: $Revisions Type: Date-time/range Size: 22 Value:
09/04/2012 04:35:26 PM;09/05/2012 11:20:28 AM
******************** END DUMP OF DOCUMENT *************************************
*********************************************************************************
******************** BEGIN DUMP OF DOCUMENT *************************************
*********************************************************************************
UNID: 8BC142003A63F68385257A6F00710B65
NoteId: 1CEE
Last Modifed: Tue Sep 04 16:34:45 EDT 2012
Create Date: Tue Sep 04 16:34:44 EDT 2012
Updated By: CN=9.37.30.206/O=organization
Name: Form Type: Text/text list Size: 9 Value:
Mapping
Name: RM_MapType Type: Text/text list Size: 5 Value: Map
Name: ServerName Type: Text/text list Size: 24 Value:
CN=9.37.30.206/O=organization
Name: Owner Type: Authors Size: 24 Value:
CN=9.37.30.206/O=organization
Name: LocalAdmin Type: Authors Size: 54 Value:
CN=9.37.30.206/O=organization;CN=Administrator/O=organization
Name: ServerNameDisplay Type: Text/text list Size: 19 Value:
9.37.30.206/organization
Name: RM_MapFrom Type: Text/text list Size: 31 Value:
/Microsoft-Server-ActiveSync*
Name: RM_MapTo Type: Text/text list Size: 40 Value:
/traveler/Microsoft-Server-ActiveSync*
Name: RM_ServerIP Type: Text/text list Size: 2 Value: [no
text]
Chapter 10. Appendix A 453
Name: Comment Type: Text/text list Size: 2 Value: [no
text]
Name: DocumentAccess Type: Authors Size: 15 Value:
[NetModifier]
Name: $SrvMap Type: Number/number list Size: 10 Value: 0
Name: MappingType Type: Text/text list Size: 3 Value: 1
Name: Type Type: Text/text list Size: 9 Value:
Mapping
Name: $REF Type: Reference to parent Size: 20 Value:
08B5C5099E6B2B7785257A6F006D0CE2
Name: $UpdatedBy Type: Names Size: 28 Value:
CN=9.37.30.206/O=organization
Name: $Revisions Type: Date-time/range Size: 22 Value:
09/04/2012 04:34:45 PM;09/04/2012 04:34:45 PM
******************** END DUMP OF DOCUMENT *************************************
*********************************************************************************
******************** BEGIN DUMP OF DOCUMENT *************************************
*********************************************************************************
UNID: 8E3971D4FB10BFBB85257A6F00710B6C
NoteId: 1CF2
Last Modifed: Tue Sep 04 16:34:45 EDT 2012
Create Date: Tue Sep 04 16:34:44 EDT 2012
Updated By: CN=9.37.30.206/O=organization
Name: Form Type: Text/text list Size: 9 Value:
Mapping
Name: RM_MapType Type: Text/text list Size: 5 Value: Map
Name: ServerName Type: Text/text list Size: 24 Value:
CN=9.37.30.206/O=organization
Name: Owner Type: Authors Size: 24 Value:
CN=9.37.30.206/O=organization
Name: LocalAdmin Type: Authors Size: 54 Value:
CN=9.37.30.206/O=organization;CN=Administrator/O=organization
Name: ServerNameDisplay Type: Text/text list Size: 19 Value:
9.37.30.206/organization
Name: RM_MapFrom Type: Text/text list Size: 20 Value:
/servlet/traveler*
Name: RM_MapTo Type: Text/text list Size: 12 Value:
/traveler*
Name: RM_ServerIP Type: Text/text list Size: 2 Value: [no
text]
Name: Comment Type: Text/text list Size: 2 Value: [no
text]
Name: DocumentAccess Type: Authors Size: 15 Value:
[NetModifier]
Name: $SrvMap Type: Number/number list Size: 10 Value: 0
Name: MappingType Type: Text/text list Size: 3 Value: 1
Name: Type Type: Text/text list Size: 9 Value:
Mapping
Name: $REF Type: Reference to parent Size: 20 Value:
08B5C5099E6B2B7785257A6F006D0CE2
454 IBM Notes Traveler Hints and Tips for a Successful Deployment
Name: $UpdatedBy Type: Names Size: 28 Value:
CN=9.37.30.206/O=organization
Name: $Revisions Type: Date-time/range Size: 22 Value:
09/04/2012 04:34:45 PM;09/04/2012 04:34:45 PM
******************** END DUMP OF DOCUMENT *************************************
--- Internet Site Documents ---
ClientManager (Wed Sep 05 12:29:04 EDT 2012)
########## ClientManager (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: List of the client versions that are available to be installed on a device of a
particular type.
Version - the version number (matches the directory name and the About panel on the device).
DefaultState - 0 (not default), 1 (will be promoted to be the default client once all the
servers are on a version that can support this client), or 2 (yes, default).
LocalFile - file location on the local file system.
InDB - Whether or not the data is stored in the database (should be true).
AssignmentList - List of users or groups to which the client version applies. * indicates the
default which is any user not explicitly specified..
ANDROID_INSTALLER (100): [VersionInfo: version=8.5.3.0.201108300850, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusInstaller\android\8.5.3.0.20
1108300850\LotusInstaller.apk, inDB=true and assignmentList=]
ANDROID_SYNC (200): [VersionInfo: version=8.5.3.100.201206110951, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\android\8.5.3.100.2
01206110951\LotusTraveler.apk, inDB=true and assignmentList=]
NOKIA_INSTALLER (300): [VersionInfo: version=8.5.3.2.201205251525, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusInstaller\nokia\8.5.3.2.2012
05251525\LotusInstaller.sisx, inDB=true and assignmentList=]
NOKIA_SYNC_S60_3 (400): [VersionInfo: version=8.5.3.2.201205251525, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\nokia\8.5.3.2.20120
5251525\LotusTraveler_S60_3.0.sisx, inDB=true and assignmentList=]
NOKIA_SYNC_S60_5 (401): [VersionInfo: version=8.5.3.2.201205251525, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\nokia\8.5.3.2.20120
5251525\LotusTraveler_S60_5.0.sisx, inDB=true and assignmentList=]
NOKIA_SYNC_S3 (402): [VersionInfo: version=8.5.3.2.201205251525, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\nokia\8.5.3.2.20120
5251525\LotusTraveler_S3.sisx, inDB=true and assignmentList=]
WM_INSTALLER (500): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusInstaller\wm\8.5.3.2.2012052
82100\LotusInstaller.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_CA (600): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_ca.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_CS (601): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_cs.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_DA (602): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_da.armV4I.cab, inDB=true and assignmentList=]
Chapter 10. Appendix A 455
WM_SYNC_6_PPC_DE (603): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_de.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_EL (604): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_el.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_EN (605): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_en.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_ES (606): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_es.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_FI (607): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_fi.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_FR (608): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_fr.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_HU (609): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_hu.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_IT (610): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_it.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_JA (611): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_ja.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_KO (612): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_ko.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_NB_NO (613): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_nb_NO.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_NL (614): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_nl.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_PL (615): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_pl.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_PT (616): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_pt.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_PT_BR (617): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_pt_BR.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_RU (618): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_ru.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_SK (619): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_sk.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_SV (620): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_sv.armV4I.cab, inDB=true and assignmentList=]
456 IBM Notes Traveler Hints and Tips for a Successful Deployment
WM_SYNC_6_PPC_TR (621): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_tr.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_ZH_CN (622): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_zh_CN.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_PPC_ZH_TW (623): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6_zh_TW.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_CA (650): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_ca.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_CS (651): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_cs.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_DA (652): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_da.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_DE (653): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_de.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_EL (654): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_el.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_EN (655): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_en.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_ES (656): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_es.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_FI (657): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_fi.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_FR (658): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_fr.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_HU (659): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_hu.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_IT (660): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_it.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_JA (661): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_ja.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_KO (662): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_ko.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_NB_NO (663): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_nb_NO.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_NL (664): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_nl.armV4I.cab, inDB=true and assignmentList=]
Chapter 10. Appendix A 457
WM_SYNC_6_SP_PL (665): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_pl.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_PT (666): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_pt.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_PT_BR (667): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_pt_BR.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_RU (668): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_ru.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_SK (669): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_sk.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_SV (670): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_sv.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_TR (671): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_tr.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_ZH_CN (672): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_zh_CN.armV4I.cab, inDB=true and assignmentList=]
WM_SYNC_6_SP_ZH_TW (673): [VersionInfo: version=8.5.3.2.201205282100, defaultState=YES,
localFile=C:\IBM\Lotus\Domino\data\domino\html\travelerclients\LotusTraveler\wm\8.5.3.2.20120528
2100\LotusTravelerWM6SP_zh_TW.armV4I.cab, inDB=true and assignmentList=]
Default Settings (Wed Sep 05 12:29:04 EDT 2012)
########## Default Settings (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: List of the Default settings that would be used for a device that doesn't have
settings yet and doesn't have an applicable policy.
List of the users or groups to which they defaults could apply.
List of the users or groups which are excluded from having these defaults apply.
--- Properties (Wed Sep 05 12:29:04 EDT 2012) ---
{devPToDoF=2, devPbanUnsecureAction=3, devPandroidencryption=0, devPapplpwReqAlphanumeric=0,
devPapplpwExpiration=90, devPandroidExtDomainExclude=, devPs60wipeLocal=7, devPcalFEnable=1,
devPwipeLocal=7, devPcalFLimit=0, devPPeakStartTime=480, devPapplpwAction=3, devPs60SCEncrypt=0,
devPs60banUnsecureAction=3, devPs60pwEnable=0, devPandroidExtDomainValidation=0,
devPpwTaction=1, devPapplbanUnsecure=0, devPandroidpwExpiration=0, devPapplbanUnsecureAction=3,
devPandroidwipeEnable=0, devPandroidpwHistory=0, ToDoFHA=0, devPapplEncryption=0, devPlogS=2000,
devPJournalLimit=0, devPpwEnable=0, devPPeakEndTime=1020, devPlogL=1,
devPandroidbanCameraAction=3, devPapplwipeEnable=0, devPapplpwHistory=0, logLHA=0,
devPApprovalNumber=1, devPandroidpwMinUCase=0, devPSCEncrypt=0, devPs60pwReqUpperLower=0,
devPinactivity=30, applsHA=0, devPandroidbanUnsecure=0, devPandroidpwReqAlphanumeric=0,
devPapplpwComplex=0, devPJournFEnable=1, devPandroidbanCamera=0, devPs60pwAction=1,
devPandroidpwEnable=0, devPcalPEnable=1, bTruncEnableHA=0, devPpwSAction=1, devPapplbanCamera=0,
EmailFEnableHA=0, OffPeakOperationTypeHA=0, devPpwAction=1, devPbTrunc=5000, devPmaxAtt=4000,
devPandroidAppPw=0, PeakOperationTypeHA=0, devPimportance=1, devPs60inactivity=30,
devPapplpwComplexNum=0, devPandroidLocalPwStorage=0, calPEnableHA=0, devPs60pwConsecNum=0,
devPPeakDays=31, devPandroidExtDomain=0, devPappls=1:2:3:4:5, devPPeakOperationType=1,
458 IBM Notes Traveler Hints and Tips for a Successful Deployment
devPandroidbanUnsecureAction=3, AllowRoamingHA=0, devPandroidpwAction=1, attachSHA=0,
devPEmailFLimit=0, devPbanUnsecure=0, $DPLocked=, devPs60banUnsecure=0, devPs60pwExpiration=0,
devPattachS=100, devPapplpwLength=4, devPcalP=7, devPandroidwipeLocal=7, devPEmailFEnable=1,
devPandroidpwMinLetters=0, devPAllowRoaming=0, devPandroidAppPwTO=30,
DisableSyncWhenLowBatteryHA=0, devPattach=0, devPs60pwMaxRepeatedChar=0, devPEmailF=5,
devPcalF=90, devPs60pwHistory=0, devPapplwipeLocal=7, devPapplbanCameraAction=3,
devPapplinactivity=30, attachHA=0, devPcalPLimit=0, importanceHA=0, devPwipeEnable=0,
devPandroidinactivity=30, JournFEnableHA=0, PeakDaysHA=0, devPpwType=1,
devPOffPeakOperationType=1, PeakStartTimeHA=0, devPs60pwLength=4, devPandroidpwMinNumeric=0,
calFEnableHA=0, devPandroidClipboard=0, devPandroidpwType=1, devPNotifyAddress=,
devPApprovalEnable=0, devPandroidappWipeEnable=0, devPs60encryption=0,
devPs60pwReqAlphanumeric=0, devPs60SCEAction=1, devPSCEAction=1, devPapplpwEnable=0,
devPandroidpwNonLetters=0, devPpwInAction=1, devPandroidpwMinLCase=0,
devPandroidEncryptAction=3, devPJournF=7, devPandroidExportAttachments=0, devPpwStren=2,
devPandroidpwMinSymbols=0, devPandroidpwLength=4, devPbTruncEnable=1, devPs60wipeEnable=0,
devPandroidExtDomainMessage=, PeakEndTimeHA=0, logSHA=0, devPDisableSyncWhenLowBattery=1,
devPandroidappPwWipeCount=0}
--- Include Names (Wed Sep 05 12:29:04 EDT 2012) ---
[]
--- Exclude Names (Wed Sep 05 12:29:04 EDT 2012) ---
[]
Thread Manager (Wed Sep 05 12:29:04 EDT 2012)
########## Thread Manager (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: Lists the active threads, the mappings of tokens to threads, and an overall
summary.
The Running time for a thread being high could explain a long sync for a user or
higher than expected CPU utilization.
The Last Runnable time for a thread being well in the past could indicate a long
running sync (if the Running time is also high or increasing) or a hung thread (if the Running
time is low or not increasing).
For any thread with a token (after the Device ID in the Thread Detail) should show
up in the Token Mappings and vice versa.
If any threads appear hung, a StopSync command may be possible if the thread is
related to a sync (DS or PS). Otherwise and for all other issues, a restart of Traveler is
probably needed to clear up the issue.
--- Summary (Wed Sep 05 12:29:04 EDT 2012) ---
Shutdown requested: false
Threads total: 4
Threads available: 3
Threads busy: 1
Threads deadlocked: 0
Threads monitor deadlocked: 0
-- Busy Thread Counts (Name: Current / Peak / Max) -- This is important to look at to see if
there is a bad setting in the thread settings for the server.
DS: 0 / 1 / 5000
PS: 0 / 2 / 200
Worker: 0 / 1 / 5000
TC: 1 / 1 / 50
Chapter 10. Appendix A 459
Alarm: 0 / 4 / 20
HTTP: 0 / 10 / 100
--- Thread Details (4) (Wed Sep 05 12:29:04 EDT 2012) ---
TC-07d8 [null] [SYSADMIN] [systemdump] [null] [0 runnables] [Busy? true] [Last Runnable: Wed Sep
05 12:29:03 EDT 2012] [Running: 907ms] [Idle: 0ms]
Unassigned-11b4 [null] [null] [null] [null] [0 runnables] [Busy? false] [Last Runnable:
Never] [Running: 0ms] [Idle: 0ms]
Unassigned-11c0 [null] [null] [null] [null] [0 runnables] [Busy? false] [Last Runnable:
Never] [Running: 0ms] [Idle: 0ms]
Unassigned-12b0 [null] [null] [null] [null] [0 runnables] [Busy? false] [Last Runnable:
Never] [Running: 0ms] [Idle: 0ms]
--- Per Thread Type Mappings of Tokens to Threads (Wed Sep 05 12:29:04 EDT 2012) ---
--- Thread Stacks (32) (Wed Sep 05 12:29:04 EDT 2012) ---
Attach API wait loop (Thread[Attach API wait loop,10,main]) (ID=8) (State=RUNNABLE) (CPU
(Total): 0ms) (CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited:
Never) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
com.ibm.tools.attach.javaSE.IPC.waitSemaphore(Native Method)
com.ibm.tools.attach.javaSE.CommonDirectory.waitSemaphore(CommonDirectory.java:220)

com.ibm.tools.attach.javaSE.AttachHandler$WaitLoop.waitForNotification(AttachHandler.java:329)
com.ibm.tools.attach.javaSE.AttachHandler$WaitLoop.run(AttachHandler.java:396)
BusySig-b84 (Thread[BusySig-b84,5,main]) (ID=27) (State=WAITING) (CPU (Total): 0ms) (CPU
(User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 12 times for unknown ms)
(Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:184)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchr
onizer.java:1998)
java.util.concurrent.DelayQueue.take(DelayQueue.java:171)
com.lotus.sync.push.DelayQueue.dequeue(DelayQueue.java:262)

com.lotus.sync.push.messaging.DelayQueueDequeueThread.run(DelayQueueDequeueThread.java:146)
com.lotus.sync.servlet.BusySignaller$BusySignallerThread.run(BusySignaller.java:197)
CL(50125:/9.37.30.206)-888 (Thread[CL(50125:/9.37.30.206)-888,5,main]) (ID=30)
(State=RUNNABLE) (CPU (Total): 31ms) (CPU (User): 31ms) (Suspended: false) (In Native: true)
(Locked: No) (Waited: 1 times for unknown ms) (Blocked: 1 times for unknown ms) (Monitors Held:
None) (Synchronizers Held: None)
java.net.PlainSocketImpl.socketAccept(Native Method)
java.net.PlainSocketImpl.accept(PlainSocketImpl.java:451)
java.net.ServerSocket.implAccept(ServerSocket.java:464)
java.net.ServerSocket.accept(ServerSocket.java:432)
com.lotus.sync.servlet.ConnectionListener.runHTTP(ConnectionListener.java:523)
com.lotus.sync.servlet.ConnectionListener.run(ConnectionListener.java:445)
460 IBM Notes Traveler Hints and Tips for a Successful Deployment
CL(8642:/9.37.30.206)-1084 (Thread[CL(8642:/9.37.30.206)-1084,5,main]) (ID=29)
(State=RUNNABLE) (CPU (Total): 62ms) (CPU (User): 62ms) (Suspended: false) (In Native: true)
(Locked: No) (Waited: 1 times for unknown ms) (Blocked: Never) (Monitors Held: None)
(Synchronizers Held: None)
sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:322)
sun.nio.ch.WindowsSelectorImpl$SubSelector.access$500(WindowsSelectorImpl.java:304)
sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:185)
sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:81)
sun.nio.ch.SelectorImpl.select(SelectorImpl.java:92)
com.lotus.sync.servlet.ConnectionListener.runTCP(ConnectionListener.java:1035)
com.lotus.sync.servlet.ConnectionListener.run(ConnectionListener.java:449)
CLR(8642)-e28 (Thread[CLR(8642)-e28,5,main]) (ID=32) (State=RUNNABLE) (CPU (Total): 0ms) (CPU
(User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: Never) (Blocked: Never)
(Monitors Held: None) (Synchronizers Held: None)
sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:322)
sun.nio.ch.WindowsSelectorImpl$SubSelector.access$500(WindowsSelectorImpl.java:304)
sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:185)
sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:81)
sun.nio.ch.SelectorImpl.select(SelectorImpl.java:92)

com.lotus.sync.servlet.ConnectionListener$SelectorReadThread.run(ConnectionListener.java:647)
CLW(50125:/9.37.30.206)_1485-1120 (Thread[CLW(50125:/9.37.30.206)_1485-1120,5,main]) (ID=33)
(State=RUNNABLE) (CPU (Total): 62ms) (CPU (User): 46ms) (Suspended: false) (In Native: true)
(Locked: No) (Waited: Never) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:140)
java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2283)
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2296)
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2767)
java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:794)
java.io.ObjectInputStream.<init>(ObjectInputStream.java:294)
com.lotus.sync.servlet.ConnectionListener$CLWorker.run(ConnectionListener.java:1607)
ChangeProcessor-9dc (Thread[ChangeProcessor-9dc,5,main]) (ID=18) (State=TIMED_WAITING) (CPU
(Total): 0ms) (CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 15
times for unknown ms) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:224)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedS
ynchronizer.java:2036)
java.util.concurrent.DelayQueue.take(DelayQueue.java:175)
com.lotus.sync.push.DelayQueue.dequeue(DelayQueue.java:262)
com.lotus.sync.push.ChangeProcessor$ProcessChangeThread.run(ChangeProcessor.java:321)
DiscDelQ-11f4 (Thread[DiscDelQ-11f4,5,main]) (ID=19) (State=WAITING) (CPU (Total): 0ms) (CPU
(User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 4 times for unknown ms)
(Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:184)
Chapter 10. Appendix A 461

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchr
onizer.java:1998)
java.util.concurrent.DelayQueue.take(DelayQueue.java:171)
com.lotus.sync.push.DelayQueue.dequeue(DelayQueue.java:262)

com.lotus.sync.push.messaging.DelayQueueDequeueThread.run(DelayQueueDequeueThread.java:146)
com.lotus.sync.push.messaging.DiscoveryQueue$DiscoveryDelayQueueThread.run(DiscoveryQueue.java:2
36)
Finalizer thread (Thread[Finalizer thread,5,system]) (ID=40) (State=RUNNABLE) (CPU (Total): 0ms)
(CPU (User): 0ms) (Suspended: false) (In Native: false) (Locked: No) (Waited: Never) (Blocked:
Never) (Monitors Held: None) (Synchronizers Held: None)
Gc Slave Thread (Thread[Gc Slave Thread,5,system]) (ID=5) (State=RUNNABLE) (CPU (Total):
15ms) (CPU (User): 15ms) (Suspended: false) (In Native: false) (Locked: No) (Waited: Never)
(Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
JIT Compilation Thread (Thread[JIT Compilation Thread,10,system]) (ID=4) (State=RUNNABLE)
(CPU (Total): 2531ms) (CPU (User): 2515ms) (Suspended: false) (In Native: false) (Locked: No)
(Waited: Never) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
LogNsf-cc4 (Thread[LogNsf-cc4,5,main]) (ID=38) (State=TIMED_WAITING) (CPU (Total): 0ms) (CPU
(User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 221 times for unknown
ms) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:224)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedS
ynchronizer.java:2036)
java.util.concurrent.ArrayBlockingQueue.poll(ArrayBlockingQueue.java:353)
com.lotus.sync.logging.LogNsfHandler$NsfThread.run(LogNsfHandler.java:80)
MS-SMS-DelQ-7f0 (Thread[MS-SMS-DelQ-7f0,5,main]) (ID=28) (State=WAITING) (CPU (Total): 0ms)
(CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 1 times for unknown
ms) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:184)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchr
onizer.java:1998)
java.util.concurrent.DelayQueue.take(DelayQueue.java:171)
com.lotus.sync.push.DelayQueue.dequeue(DelayQueue.java:262)

com.lotus.sync.push.messaging.DelayQueueDequeueThread.run(DelayQueueDequeueThread.java:146)
com.lotus.sync.servlet.ConnectionSMSSender$SMSDelayQueueThread.run(ConnectionSMSSender.java:159)
Mntr-9.37.30.206-854 (Thread[Mntr-9.37.30.206-854,5,main]) (ID=37) (State=TIMED_WAITING) (CPU
(Total): 0ms) (CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 1138
times for unknown ms) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
java.lang.Thread.sleep(Native Method)
java.lang.Thread.sleep(Thread.java:851)
com.lotus.sync.push.NewAPIMonitor.monitor(NewAPIMonitor.java:315)
com.lotus.sync.push.NewAPIMonitor.run(NewAPIMonitor.java:258)
462 IBM Notes Traveler Hints and Tips for a Successful Deployment
MstrMntr-af8 (Thread[MstrMntr-af8,5,main]) (ID=20) (State=WAITING) (CPU (Total): 31ms) (CPU
(User): 31ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 10 times for unknown
ms) (Blocked: 1 times for unknown ms) (Monitors Held: None) (Synchronizers Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:184)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchr
onizer.java:1998)
java.util.concurrent.DelayQueue.take(DelayQueue.java:171)
com.lotus.sync.push.DelayQueue.dequeue(DelayQueue.java:262)
com.lotus.sync.push.MasterMonitor$EnableThread.run(MasterMonitor.java:199)
NotesGCThread0 (Thread[NotesGCThread0,5,main]) (ID=10) (State=WAITING) (CPU (Total): 0ms)
(CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 1 times for unknown
ms) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:196)
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:107)
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:79)
lotus.domino.local.NotesReferenceQueue.run(Unknown Source)
java.lang.Thread.run(Thread.java:736)
Signal Dispatcher (Thread[Signal Dispatcher,5,main]) (ID=2) (State=RUNNABLE) (CPU (Total):
0ms) (CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: Never)
(Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
com.ibm.misc.SignalDispatcher.waitForSignal(Native Method)
com.ibm.misc.SignalDispatcher.run(SignalDispatcher.java:66)
SrvCmdTrkr-DelQ-82c (Thread[SrvCmdTrkr-DelQ-82c,5,main]) (ID=31) (State=WAITING) (CPU
(Total): 0ms) (CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 1
times for unknown ms) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:184)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchr
onizer.java:1998)
java.util.concurrent.DelayQueue.take(DelayQueue.java:171)
com.lotus.sync.push.DelayQueue.dequeue(DelayQueue.java:262)

com.lotus.sync.push.messaging.DelayQueueDequeueThread.run(DelayQueueDequeueThread.java:146)
com.lotus.sync.hadr.ServerCommandTracker$TrackerThread.run(ServerCommandTracker.java:483)
StateController-aac (Thread[StateController-aac,5,main]) (ID=17) (State=TIMED_WAITING) (CPU
(Total): 0ms) (CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 1
times for unknown ms) (Blocked: 1 times for unknown ms) (Monitors Held: None) (Synchronizers
Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:224)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedS
ynchronizer.java:2036)
java.util.concurrent.DelayQueue.take(DelayQueue.java:175)
Chapter 10. Appendix A 463
com.lotus.sync.push.DelayQueue.dequeue(DelayQueue.java:262)
com.lotus.sync.push.StateController$StateTimerThread.run(StateController.java:700)
StatusMgr-DelQ-99c (Thread[StatusMgr-DelQ-99c,5,main]) (ID=25) (State=TIMED_WAITING) (CPU
(Total): 0ms) (CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 12
times for unknown ms) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:224)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedS
ynchronizer.java:2036)
java.util.concurrent.DelayQueue.take(DelayQueue.java:175)
com.lotus.sync.push.DelayQueue.dequeue(DelayQueue.java:262)

com.lotus.sync.push.messaging.DelayQueueDequeueThread.run(DelayQueueDequeueThread.java:146)
com.lotus.sync.admin.status.StatusManager$StatusMgrDelayQueueThread.run(StatusManager.java:396)
TC-07d8 (TC-07d8 [null] [SYSADMIN] [systemdump] [null] [0 runnables] [Busy? true] [Last
Runnable: Wed Sep 05 12:29:03 EDT 2012] [Running: 907ms] [Idle: 0ms]) (ID=36) (State=RUNNABLE)
(CPU (Total): 453ms) (CPU (User): 265ms) (Suspended: false) (In Native: true) (Locked: No)
(Waited: 137 times for unknown ms) (Blocked: 1 times for unknown ms) (Monitors Held: None)
(Synchronizers Held: None)
java.lang.Thread.getStackTraceImpl(Native Method)
java.lang.Thread.getStackTrace(Thread.java:1042)
java.lang.Thread.getAllStackTraces(Thread.java:1070)
com.lotus.sync.util.ThreadPool.printStatus(ThreadPool.java:460)
com.lotus.sync.admin.addin.SystemDump.process(SystemDump.java:470)
com.lotus.sync.admin.addin.AbstractAddinCommand.execute(AbstractAddinCommand.java:239)
com.lotus.sync.admin.DominoQueueListener.onMessage(DominoQueueListener.java:198)

com.lotus.sync.admin.DominoQueueListener$TellCommandRunnable.run(DominoQueueListener.java:267)
com.lotus.sync.util.ThreadPoolThread.run(ThreadPoolThread.java:405)
TCStatus-TC-07d8-e0c (Thread[TCStatus-TC-07d8-e0c,5,main]) (ID=42) (State=TIMED_WAITING) (CPU
(Total): 0ms) (CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 3
times for unknown ms) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
java.lang.Thread.sleep(Native Method)
java.lang.Thread.sleep(Thread.java:851)

com.lotus.sync.admin.addin.AbstractAddinCommand$StatusThread.run(AbstractAddinCommand.java:1199)
TravelerDBThread-26c (Thread[TravelerDBThread-26c,5,main]) (ID=14) (State=TIMED_WAITING) (CPU
(Total): 312ms) (CPU (User): 250ms) (Suspended: false) (In Native: true) (Locked: No) (Waited:
249 times for unknown ms) (Blocked: 2 times for unknown ms) (Monitors Held: None) (Synchronizers
Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:224)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedS
ynchronizer.java:2036)
java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:435)
464 IBM Notes Traveler Hints and Tips for a Successful Deployment

com.lotus.sync.admin.UpdateTravelerDB2$TravelerDB2Thread.pollAndServiceRequest(UpdateTravelerDB2
.java:1492)
com.lotus.sync.admin.UpdateTravelerDB$TravelerDBThread.run(UpdateTravelerDB.java:156)
TravelerDBThread-dd4 (Thread[TravelerDBThread-dd4,5,main]) (ID=16) (State=TIMED_WAITING) (CPU
(Total): 93ms) (CPU (User): 78ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 247
times for unknown ms) (Blocked: 3 times for unknown ms) (Monitors Held: None) (Synchronizers
Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:224)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedS
ynchronizer.java:2036)
java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:435)

com.lotus.sync.admin.UpdateTravelerDB2$TravelerDB2Thread.pollAndServiceRequest(UpdateTravelerDB2
.java:1492)
com.lotus.sync.admin.UpdateTravelerDB$TravelerDBThread.run(UpdateTravelerDB.java:156)
TravelerDBThread-f2c (Thread[TravelerDBThread-f2c,5,main]) (ID=15) (State=TIMED_WAITING) (CPU
(Total): 0ms) (CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 241
times for unknown ms) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:224)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedS
ynchronizer.java:2036)
java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:435)

com.lotus.sync.admin.UpdateTravelerDB2$TravelerDB2Thread.pollAndServiceRequest(UpdateTravelerDB2
.java:1492)
com.lotus.sync.admin.UpdateTravelerDB$TravelerDBThread.run(UpdateTravelerDB.java:156)
Unassigned-11b4 (Unassigned-11b4 [null] [null] [null] [null] [0 runnables] [Busy? false]
[Last Runnable: Never] [Running: 0ms] [Idle: 0ms]) (ID=34) (State=WAITING) (CPU (Total): 0ms)
(CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 135 times for
unknown ms) (Blocked: 5 times for unknown ms) (Monitors Held: None) (Synchronizers Held: None)
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:167)
com.lotus.sync.util.ThreadPoolThread.run(ThreadPoolThread.java:348)
Unassigned-11c0 (Unassigned-11c0 [null] [null] [null] [null] [0 runnables] [Busy? false]
[Last Runnable: Never] [Running: 0ms] [Idle: 0ms]) (ID=35) (State=WAITING) (CPU (Total): 0ms)
(CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 132 times for
unknown ms) (Blocked: 5 times for unknown ms) (Monitors Held: None) (Synchronizers Held: None)
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:167)
com.lotus.sync.util.ThreadPoolThread.run(ThreadPoolThread.java:348)
Unassigned-12b0 (Unassigned-12b0 [null] [null] [null] [null] [0 runnables] [Busy? false]
[Last Runnable: Never] [Running: 0ms] [Idle: 0ms]) (ID=41) (State=WAITING) (CPU (Total): 0ms)
Chapter 10. Appendix A 465
(CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 82 times for
unknown ms) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:167)
com.lotus.sync.util.ThreadPoolThread.run(ThreadPoolThread.java:348)
WallClock-2e4 (Thread[WallClock-2e4,5,main]) (ID=11) (State=TIMED_WAITING) (CPU (Total): 0ms)
(CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 725 times for
unknown ms) (Blocked: 7 times for unknown ms) (Monitors Held: None) (Synchronizers Held: None)
java.lang.Thread.sleep(Native Method)
java.lang.Thread.sleep(Thread.java:851)
com.lotus.sync.TSS.Util.WallClock.run(WallClock.java:261)
WorkMgr-DelQ-680 (Thread[WorkMgr-DelQ-680,5,main]) (ID=26) (State=WAITING) (CPU (Total):
15ms) (CPU (User): 15ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 34 times for
unknown ms) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:184)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchr
onizer.java:1998)
java.util.concurrent.DelayQueue.take(DelayQueue.java:171)
com.lotus.sync.push.DelayQueue.dequeue(DelayQueue.java:262)

com.lotus.sync.push.messaging.DelayQueueDequeueThread.run(DelayQueueDequeueThread.java:146)
com.lotus.sync.servlet.WorkManager$WorkMgrDelayQueueThread.run(WorkManager.java:310)
XMLLogger-DelQ-fdc (Thread[XMLLogger-DelQ-fdc,5,main]) (ID=39) (State=WAITING) (CPU (Total):
0ms) (CPU (User): 0ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 1 times for
unknown ms) (Blocked: Never) (Monitors Held: None) (Synchronizers Held: None)
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:184)

java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchr
onizer.java:1998)
java.util.concurrent.DelayQueue.take(DelayQueue.java:171)
com.lotus.sync.push.DelayQueue.dequeue(DelayQueue.java:262)

com.lotus.sync.push.messaging.DelayQueueDequeueThread.run(DelayQueueDequeueThread.java:146)
com.lotus.sync.logging.SyncMLLogger$XMLLoggerDelayQueueThread.run(SyncMLLogger.java:980)
main-df0 (Thread[main-df0,5,main]) (ID=1) (State=RUNNABLE) (CPU (Total): 3312ms) (CPU (User):
2671ms) (Suspended: false) (In Native: true) (Locked: No) (Waited: 9 times for unknown ms)
(Blocked: 1 times for unknown ms) (Monitors Held: None) (Synchronizers Held: None)
lotus.notes.addins.JavaServerAddin.AddInIdle(Native Method)
lotus.notes.addins.JavaServerAddin.addInRunning(JavaServerAddin.java:619)
com.lotus.sync.admin.MainTask.runDominoQueue(MainTask.java:959)
com.lotus.sync.admin.MainTask.runNotes(MainTask.java:1271)
lotus.domino.NotesThread.run(Unknown Source)
com.lotus.sync.admin.MainTask.main(MainTask.java:1462)
--- Summary (Wed Sep 05 12:29:04 EDT 2012) ---
Shutdown requested: false
466 IBM Notes Traveler Hints and Tips for a Successful Deployment
Threads total: 4
Threads available: 3
Threads busy: 1
Threads deadlocked: 0
Threads monitor deadlocked: 0
-- Busy Thread Counts (Name: Current / Peak / Max) --
DS: 0 / 1 / 5000
PS: 0 / 2 / 200
Worker: 0 / 1 / 5000
TC: 1 / 1 / 50
Alarm: 0 / 4 / 20
HTTP: 0 / 10 / 100
Dispatch (Wed Sep 05 12:29:04 EDT 2012)
########## Dispatch (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: List of the data stored on each thread. This is used for internal processing by
Level 3.
--- Dispatch Thread Data Details (Wed Sep 05 12:29:04 EDT 2012) ---
BusySig-b84, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=false
CL(50125:/9.37.30.206)-888, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=false
CL(8642:/9.37.30.206)-1084, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=false
CLR(8642)-e28, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=false
CLW(50125:/9.37.30.206)_1485-1120, databaseMap has 0 entries, databaseToACLMgrMap has 0
entries, jniThreadInited=true, jniSessionStarted=false, notesThreadInited=false
ChangeProcessor-9dc, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=false
DiscDelQ-11f4, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=false
LogNsf-cc4, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=false, jniSessionStarted=false, notesThreadInited=true
MS-SMS-DelQ-7f0, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=false
Mntr-9.37.30.206-854, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=false
MstrMntr-af8, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=true, notesThreadInited=true,
notesSession=CN=9.37.30.206/O=organization, dbInfo=DominoDBInfo: CN=t u3/O=organization
InternetAddress=null Active Server=CN=9.37.30.206/O=organization Active Path=mail/tu3.nsf
Primary Server=CN=9.37.30.206/O=organization Primary Path=mail/tu3.nsf Mail
Domain=domainTravelerAccessRights=allow Has Validated DB=True ExplicitPolicy=null ShortName
List=[tu3] FullName List=[CN=t u3/O=organization, t u3] designFlags=null
SrvCmdTrkr-DelQ-82c, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=false
StateController-aac, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=false
Chapter 10. Appendix A 467
StatusMgr-DelQ-99c, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=true
TC-07d8, databaseMap has 1 entries, databaseToACLMgrMap has 0 entries, jniThreadInited=true,
jniSessionStarted=false, notesThreadInited=true, notesSession=CN=9.37.30.206/O=organization
TCStatus-TC-07d8-e0c, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=true
TravelerDBThread-26c, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=false, jniSessionStarted=false, notesThreadInited=true,
notesSession=CN=9.37.30.206/O=organization
TravelerDBThread-dd4, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=false, jniSessionStarted=false, notesThreadInited=true,
notesSession=CN=9.37.30.206/O=organization
TravelerDBThread-f2c, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=false, jniSessionStarted=false, notesThreadInited=false
WallClock-2e4, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=false
WorkMgr-DelQ-680, databaseMap has 0 entries, databaseToACLMgrMap has 0 entries,
jniThreadInited=true, jniSessionStarted=false, notesThreadInited=false
Statistics (Wed Sep 05 12:29:04 EDT 2012)
########## Statistics (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: List of all the Traveler statistics that have been collected since the stats were
last reset (the statistics are automatically reset each time the Traveler process is restarted).
After the raw statistics, a summary of the synchronizations and some percentage
calculations based on multiple statistics is given.
Availability.Index.090-100 = 61 The amount of time that the server is in the available state
Availability.Index.Current = 100 The availability of the server. 100 is very available, -200
is not available.
CPU.Pct.<bucket>
Traveler checks the CPU usage on a periodic basis. This stat is a histogram showing how many
times the CPU percentage was in the specified range or bucket. The bucket values are "000-010",
"010-020", "020-030", "030-040", "040-050", "050-060", "060-070", "070-080", "080-090",
"090-100". As an example, CPU.Pct.040-050 would show the number of times the CPU usage was
between 40% and 50%
CPU.Pct.000-010 = 5
ConnectionManager.Count.GET = 0
ConnectionManager.Count.getClientConfigFile = 0
ConnectionManager.Count.getConfigAS = 0
ConnectionManager.Count.pushAS = 0
ConnectionManager.Count.syncAS = 0
ConnectionManager.Peak.GET.Count = 1
ConnectionManager.Peak.GET.Time = Wed Sep 05 11:31:32 EDT 2012
ConnectionManager.Peak.Total.Count = 2
ConnectionManager.Peak.Total.Time = Wed Sep 05 11:43:20 EDT 2012
ConnectionManager.Peak.getClientConfigFile.Count = 1
ConnectionManager.Peak.getClientConfigFile.Time = Wed Sep 05 11:31:54 EDT 2012
468 IBM Notes Traveler Hints and Tips for a Successful Deployment
ConnectionManager.Peak.getConfigAS.Count = 1
ConnectionManager.Peak.getConfigAS.Time = Wed Sep 05 11:33:02 EDT 2012
ConnectionManager.Peak.pushAS.Count = 2
ConnectionManager.Peak.pushAS.Time = Wed Sep 05 11:43:20 EDT 2012
ConnectionManager.Peak.syncAS.Count = 1
ConnectionManager.Peak.syncAS.Time = Wed Sep 05 11:35:11 EDT 2012
DB.Connections = 3 The total number of connections currently allocated.
DB.Connections.Idle = 3 The number of currently allocated connections available for new work.
DB.Connections.Max = 600 The maximum number of connections that could be allocated.
DB.Connections.Peak = 3 The peak number of connections to the database at any time of the
server's instance.
DCA.C.CheckAccessRights = 8 The number of times the access rights were checked for a database
using the Domino C API call.
DCA.C.Count.NSFDbClose = 34 The number of times a database was closed using the Domino C API
call.
DCA.C.Count.NSFDbOpen = 34 The number of times a database was opened using the Domino C API
call.
DCA.C.Count.NSFNoteClose = 122 The number of times a note was closed using the Domino C API
call.
DCA.C.Count.NSFNoteOpen = 122 The number of times a note was opened using the Domino C API
call.
DCA.C.HTMLCreateConverter = 8 The number of times an HTML Converter object was created.
DCA.C.HTMLDestroyConverter = 8 The number of times an HTML Converter object was destroyed.
DCA.C.ModDoc.RunCount = 18 Count of the number of times Lotus Notes Traveler had to determine
which documents were changed.
DCA.C.ModDoc.SkippedDocs = 191 The number of documents that Lotus Notes Traveler is ignoring
because the document is not one of the documents that are syncable to device (i.e. hidden view,
etc.)
DCA.C.ModDoc.SyncableDocs = 14 The number of documents that can be synced to the device.
DCA.C.ModDoc.Time = 1048 The amount of time used to determine the syncable documents.
DCA.C.NAMELookup = 11 The number of times directory lookup is performed.
DCA.C.NSFDbGetNoteInfo = 1 The number of times a document is access via the GetNoteInfo call.
DCA.ChangeDelayCount.<bucket> The amount of time (in seconds) between when the document was last
modified and when Traveler has detected the change during the prime sync. Buckets are "000-003",
"003-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".
DCA.ChangeDelayCount.000-003 = 7
DCA.ChangeDelayCount.003-005 = 1
DCA.DB_CLOSE = 73 The number of times a database was closed using the Domino Java API.
DCA.DB_OPEN = 60 The number of times a database was opened using the Domino Java API.
DCA.DB_OPEN.Time.Histogram..000-001 = 26
DCA.DB_OPEN.Time.Histogram.<server>.<bucket>
Histogram of the time spent (in seconds) to open a database on the given server using the Domino
Java API call. Server is the name of the Domino server on which the database was opened. Buckets
are "000-001", "001-002", "002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".
DCA.DB_OPEN.Time.Histogram.CN=9.37.30.206/O=organization.000-001 = 34
DCA.DOCUMENT_CLOSE = 811 The number of times a document was closed using the Domino Java API.
DCA.DOCUMENT_OPEN = 812 The number of times a document was opened using the Domino Java API.
Database.Query.Histogram.<query>.<bucket>
Chapter 10. Appendix A 469
Histogram of the time spent (in seconds) to execute the specified query against Traveler's
internal database. Query is the query that was executed. Buckets are "000-001", "001-002",
"002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".
Database.Query.Histogram.AddNewDeviceRecord.000-001 = 1
Database.Query.Histogram.AddNewUserAccounts.000-001 = 1
Database.Query.Histogram.ClientVersionSelectAllExceptFileImage.000-001 = 2
Database.Query.Histogram.DeleteAccountByAccountId.000-001 = 1
Database.Query.Histogram.GudSelect.<bucket>
Histogram of the time spent (in seconds) to execute the lookup of a user against Traveler's
internal database.
Database.Query.Histogram.GudSelect.000-001 = 12 Most of the values should be in the 000-001
range for a healthy database.
Database.Query.Histogram.GudSelectOODEmailsInFolderFetchFirst.000-001 = 3
Database.Query.Histogram.GudSelectOODPimRecords.000-001 = 2
Database.Query.Histogram.GudSelectOODPimRecordsOrderByGudRec.000-001 = 2
Database.Query.Histogram.GudSelectQueryForUnmappedRecords.000-001 = 3
Database.Query.Histogram.GudSelectRecordsMappedNull.000-001 = 3
Database.Query.Histogram.GudSelectSoftDeletesInFolder.000-001 = 4
Database.Query.Histogram.GudSelectValuesForReadOnlyChange.000-001 = 2
Database.Query.Histogram.GuidMapSelectBannedForAccount.000-001 = 2
Database.Query.Histogram.InsertAccount.000-001 = 2
Database.Query.Histogram.InsertBinding.000-001 = 2
Database.Query.Histogram.InsertFieldName.000-001 = 28
Database.Query.Histogram.InsertFilterData.000-001 = 1
Database.Query.Histogram.InsertGudTimestamp.000-001 = 10
Database.Query.Histogram.InsertGuidMappingInsertLong.000-001 = 8
Database.Query.Histogram.InsertListener.000-001 = 1
Database.Query.Histogram.InsertRecordMapping.000-001 = 10
Database.Query.Histogram.InsertSecurityRecord.000-001 = 1
Database.Query.Histogram.InsertSyncTimestamp.000-001 = 2
Database.Query.Histogram.InsertSyncTimestampFolder.000-001 = 6
Database.Query.Histogram.ListenerSelectAllListenersForUser.000-001 = 2
Database.Query.Histogram.ListenerSelectListenerAllServers.000-001 = 1
Database.Query.Histogram.ListenerSelectListenersForServer.000-001 = 2
Database.Query.Histogram.LogSettingsClearAll.000-001 = 1
Database.Query.Histogram.LogSettingsInsertProperty.000-001 = 45
Database.Query.Histogram.LogSettingsSelectAll.000-001 = 2
Database.Query.Histogram.ReplicasDelete.000-001 = 1
Database.Query.Histogram.ReplicasInsert.000-001 = 1
Database.Query.Histogram.ReplicasSelectByAccountID.000-001 = 4
Database.Query.Histogram.SelectAccountById.000-001 = 4
Database.Query.Histogram.SelectAllAccountIdsFromAccount.000-001 = 1
Database.Query.Histogram.SelectAllUsers.000-001 = 1
Database.Query.Histogram.SelectApprovalNotifyNames.000-001 = 1
Database.Query.Histogram.SelectBindingsForUser.000-001 = 28
Database.Query.Histogram.SelectCafIDSequence.000-001 = 1
Database.Query.Histogram.SelectCheckPrimary.000-001 = 61
Database.Query.Histogram.SelectDataReapRecords.000-001 = 36
Database.Query.Histogram.SelectDefaultSettings.000-001 = 2
Database.Query.Histogram.SelectDeviceRecordByDeviceID.000-001 = 32
Database.Query.Histogram.SelectDeviceRecordID.000-001 = 8
470 IBM Notes Traveler Hints and Tips for a Successful Deployment
Database.Query.Histogram.SelectDeviceRecordToGudMapping.000-001 = 63
Database.Query.Histogram.SelectDeviceSecurityDetailRecord.000-001 = 35
Database.Query.Histogram.SelectDeviceWithAccountIdZeroandDeviceId.000-001 = 1
Database.Query.Histogram.SelectDeviceWithAccountIdZeroandUserId.000-001 = 1
Database.Query.Histogram.SelectDeviceWithAccountIdandDeviceId.000-001 = 1
Database.Query.Histogram.SelectDeviceWithUserNameandDeviceId.000-001 = 39
Database.Query.Histogram.SelectDevicesByAccountID.000-001 = 2
Database.Query.Histogram.SelectDevicesWithAccountIDZero.000-001 = 3
Database.Query.Histogram.SelectExcludeAndroidDomainNames.000-001 = 1
Database.Query.Histogram.SelectExcludeNames.000-001 = 1
Database.Query.Histogram.SelectFilterList.000-001 = 2
Database.Query.Histogram.SelectFolderSyncing.000-001 = 1
Database.Query.Histogram.SelectFolderTypeforGuid.000-001 = 11
Database.Query.Histogram.SelectGUDbyIDAccount.000-001 = 1
Database.Query.Histogram.SelectGUIDFromLong.000-001 = 2
Database.Query.Histogram.SelectHeartbeats.000-001 = 61
Database.Query.Histogram.SelectIdByDeviceName.000-001 = 26
Database.Query.Histogram.SelectIdMappingByFieldName.000-001 = 132
Database.Query.Histogram.SelectIncludeNames.000-001 = 1
Database.Query.Histogram.SelectLGUIDFromGUID.000-001 = 14
Database.Query.Histogram.SelectLoginAccount.000-001 = 24
Database.Query.Histogram.SelectMasterBindingForUser.000-001 = 12
Database.Query.Histogram.SelectModTimeInBE.000-001 = 3
Database.Query.Histogram.SelectNameByDeviceId.000-001 = 1
Database.Query.Histogram.SelectRecordFromDatabase.000-001 = 24
Database.Query.Histogram.SelectSecurityRecordsAll.000-001 = 1
Database.Query.Histogram.SelectSecurityRecordsForUserDevice.000-001 = 9
Database.Query.Histogram.SelectSqlRunner.000-001 = 1
Database.Query.Histogram.SelectSyncTimestampFolder.000-001 = 74
Database.Query.Histogram.SelectTaggedEmailRecords.000-001 = 5
Database.Query.Histogram.SelectTaggedPIMRecords.000-001 = 3
Database.Query.Histogram.SelectTsGlobalByName.000-001 = 1
Database.Query.Histogram.SelectTsGudTimestampByRole.000-001 = 4
Database.Query.Histogram.SelectUserWithUserName.000-001 = 2
Database.Query.Histogram.SelectUsersWithAccountIDZero.000-001 = 3
Database.Query.Histogram.SelectVersion.000-001 = 1
Database.Query.Histogram.SelecttsAccountIDFromName.000-001 = 3
Database.Query.Histogram.TestTableExistence.000-001 = 1
Database.Query.Histogram.UpdateAndTagRecordMapping.000-001 = 8
Database.Query.Histogram.UpdateBindingLockType.000-001 = 2
Database.Query.Histogram.UpdateDevicePolicyCompliance.000-001 = 15
Database.Query.Histogram.UpdateDevicePolicySettings.000-001 = 14
Database.Query.Histogram.UpdateDeviceSecurityInfo.000-001 = 4
Database.Query.Histogram.UpdateDeviceWipeOptions.000-001 = 6
Database.Query.Histogram.UpdateDeviceWithAccessandWipeStatus.000-001 = 4
Database.Query.Histogram.UpdateDeviceWithApplPwSupport.000-001 = 2
Database.Query.Histogram.UpdateDeviceWithApprovalInfo.000-001 = 4
Database.Query.Histogram.UpdateDeviceWithExtEmailSupport.000-001 = 2
Database.Query.Histogram.UpdateDeviceWithNotificationType.000-001 = 3
Database.Query.Histogram.UpdateDeviceWithProvider.000-001 = 2
Database.Query.Histogram.UpdateDeviceWithSecPolicy.000-001 = 2
Database.Query.Histogram.UpdateDeviceWithSmsAddress.000-001 = 4
Database.Query.Histogram.UpdateDeviceWithSyncTime.000-001 = 7
Database.Query.Histogram.UpdateDeviceWithType.000-001 = 2
Database.Query.Histogram.UpdateDeviceWithWipeConfirmed.000-001 = 4
Chapter 10. Appendix A 471
Database.Query.Histogram.UpdateDeviceWithWipeRequested.000-001 = 4
Database.Query.Histogram.UpdateDeviceWithWipeSupport.000-001 = 2
Database.Query.Histogram.UpdateFilterData.000-001 = 9
Database.Query.Histogram.UpdateFolderName.000-001 = 4
Database.Query.Histogram.UpdateGudRecordBackendTimestamp.000-001 = 1
Database.Query.Histogram.UpdateGudTimestamp.000-001 = 2
Database.Query.Histogram.UpdateGudTimestampForDelete.000-001 = 1
Database.Query.Histogram.UpdateGudTimestampShortValue.000-001 = 12
Database.Query.Histogram.UpdateListener.000-001 = 2
Database.Query.Histogram.UpdateListenerChangeFlags.000-001 = 7
Database.Query.Histogram.UpdateListenerOfflineTime.000-001 = 1
Database.Query.Histogram.UpdateNokiaSecurityDefaultSettings.000-001 = 1
Database.Query.Histogram.UpdateRecordMapping.000-001 = 4
Database.Query.Histogram.UpdateRecordMappingClearTag.000-001 = 1
Database.Query.Histogram.UpdateRecordMappingDeviceTimeSyncForEmail.000-001 = 1
Database.Query.Histogram.UpdateRecordMappingForOODLeaveChangeFlags.000-001 = 1
Database.Query.Histogram.UpdateRecordMappingSetTaggedOODAndClearMap.000-001 = 3
Database.Query.Histogram.UpdateRecordMappingTagRecordClearMapping.000-001 = 4
Database.Query.Histogram.UpdateRecordMappingTimeSent.000-001 = 8
Database.Query.Histogram.UpdateRecordMappingWithBitSetTaggedOOD.000-001 = 6
Database.Query.Histogram.UpdateRecordMappingWithBitSetTaggedOODAndClearMap.000-001 = 3
Database.Query.Histogram.UpdateSecurityRecord.000-001 = 4
Database.Query.Histogram.UpdateSqlRunner.000-001 = 2
Database.Query.Histogram.UpdateSyncTimestampDescription.000-001 = 1
Database.Query.Histogram.UpdateSyncTimestampFolder.000-001 = 72
Database.Query.Histogram.UpdateSyncTimestampGudSyncTime.000-001 = 7
Database.Query.Histogram.UpdateTimeSyncInDevice.000-001 = 4
Database.Query.Histogram.UpdateTsGlobal.000-001 = 1
Database.Query.Histogram.UpdateTsGlobalHeartbeat.000-001 = 61
Database.Query.Histogram.UpdateUserWithMailInfo.000-001 = 2
Database.Query.Histogram.UpdateUserWithUserState.000-001 = 3
Database.Query.Histogram.VerifyRecordMapStillOOD.000-001 = 1
DelayQueue.DequeueDelayTime.<DelayQueue>.<bucket>
Histogram of the amount of time between a DelayQueueElement being dequeued from a DelayQueue and
when it should have been dequeued. DelayQueue is the name of the DelayQueue. Buckets are
"00-01", "01-10", "10-60", "60-Inf".
DelayQueue.DequeueDelayTime.ChangeProcessor.00-01 = 12
DelayQueue.DequeueDelayTime.DiscDelQ.00-01 = 2
DelayQueue.DequeueDelayTime.Monitor.00-01 = 8
DelayQueue.DequeueDelayTime.StatusMgr-DelQ.00-01 = 5
DelayQueue.DequeueDelayTime.WorkMgr-DelQ.00-01 = 32
DelayQueue.Peak.Count.BusySig = 1
DelayQueue.Peak.Count.ChangeProcessor = 2
DelayQueue.Peak.Count.DiscDelQ = 2
DelayQueue.Peak.Count.Monitor = 1
DelayQueue.Peak.Count.StateController = 3
DelayQueue.Peak.Count.StatusMgr-DelQ = 3
DelayQueue.Peak.Count.WorkMgr-DelQ = 1
DelayQueue.Peak.Time.BusySig = Wed Sep 05 11:33:06 EDT 2012
DelayQueue.Peak.Time.ChangeProcessor = Wed Sep 05 11:32:12 EDT 2012
DelayQueue.Peak.Time.DiscDelQ = Wed Sep 05 11:43:20 EDT 2012
DelayQueue.Peak.Time.Monitor = Wed Sep 05 11:29:49 EDT 2012
DelayQueue.Peak.Time.StateController = Wed Sep 05 11:58:15 EDT 2012
472 IBM Notes Traveler Hints and Tips for a Successful Deployment
DelayQueue.Peak.Time.StatusMgr-DelQ = Wed Sep 05 11:28:58 EDT 2012
DelayQueue.Peak.Time.WorkMgr-DelQ = Wed Sep 05 11:29:48 EDT 2012
DeviceSync.Bytes.In.B = 2338 The total number of bytes received from devices during sync
operations.
DeviceSync.Bytes.Out.B = 3511 The total number of bytes sent to devices during sync
operations.
DeviceSync.Count.<SyncReturnCode>
The number of device syncs that had the specified return code. Most common return codes are:
200=OK, 408=Request Timeout (Device did not respond before the Server timed out the session),
409=Conflict (Device started a new session which caused this session to be aborted), 500=Unknown
Error, 503=Server Busy
DeviceSync.Count.200 = 18
DeviceSync.Documents.ToDevice.Mail.Add = 4 The total number of mail document adds sent from
the server to a device.
DeviceSync.Documents.ToDevice.Mail.Delete = 2 The total number of mail document deletes sent
from the server to a device.
DeviceSync.Documents.ToDevice.Mail.Update = 4 The total number of mail document updates sent
from the server to a device.
DeviceSync.Documents.ToDevice.Calendar.Add = 1 The total number of calendar event adds sent
from the server to a device.
DeviceSync.Documents.ToDevice.Calendar.Delete = 1 The total number of calendar event deletes
sent from the server to a device.
DeviceSync.Documents.ToDevice.Calendar.Update = 1 The total number of calendar event updates
sent from the server to a device.
DeviceSync.Documents.ToDevice.Contacts.Add = 1 The total number of contact adds sent server
from the to a device.
DeviceSync.Documents.ToDevice.Contacts.Delete = 1 The total number of contact deletes sent
from the server to a device.
DeviceSync.Documents.ToDevice.Contacts.Update = 1 The total number of contact updates sent
from the server to a device.
DeviceSync.Documents.ToDevice.ToDo.Add = 1 The total number of todo adds sent from the server
to device.
DeviceSync.Documents.ToDevice.ToDo.Delete = 1 The total number of todo deletes sent from the
server to a device.
DeviceSync.Documents.ToDevice.ToDo.Update = 1 The total number of todo updates sent from the
server to a device.
DeviceSync.Documents.ToDevice.Journal.Add = 1 The total number of journal document adds sent
from the server to a device.
DeviceSync.Documents.ToDevice.Journal.Delete = 1 The total number of journal document deletes
sent from the server to a device.
DeviceSync.Documents.ToDevice.Journal.Update = 1 The total number of journal document updates
sent from the server to a device.
DeviceSync.Documents.ToDevice.Folder.Add = 1 The total number of folder document adds sent
from the server to a device.
DeviceSync.Documents.ToDevice.Folder.Delete = 1 The total number of folder document deletes
sent from the server to a device.
DeviceSync.Documents.ToDevice.Folder.Update = 1 The total number of folder document updates
sent from the server to a device.
DeviceSync.Documents.ToServer.Calendar.Add = 1 The total number of calendar event adds sent
from the device to a server.
DeviceSync.Documents.ToServer.Calendar.Delete = 1 The total number of calendar event deletes
sent from the device to a server.
Chapter 10. Appendix A 473
DeviceSync.Documents.ToServer.Calendar.Update = 1 The total number of calendar event updates
sent from the device to a server.
DeviceSync.Documents.ToServer.Contacts.Add = 1 The total number of contact adds sent from a
device to the server.
DeviceSync.Documents.ToServer.Contacts.Delete = 1 The total number of contact deletes sent
from a device to the server.
DeviceSync.Documents.ToServer.Contacts.Update = 1 The total number of contact updates sent
from a device to the server.
DeviceSync.Documents.ToServer.Folder.Add = 1 The total number of folder document adds sent
from a device to the server.
DeviceSync.Documents.ToServer.Folder.Delete = 1 The total number of folder document deletes
sent from a device to the server.
DeviceSync.Documents.ToServer.Folder.Update = 1 The total number of folder document updates
sent from a device to the server.
DeviceSync.Documents.ToServer.Journal.Add = 1 The total number of journal document adds sent
from a device to the server.
DeviceSync.Documents.ToServer.Journal.Delete = 1 The total number of journal document deletes
sent from a device to the server.
DeviceSync.Documents.ToServer.Journal.Update = 1 The total number of journal document updates
sent from a device to the server.
DeviceSync.Documents.ToServer.Mail.Add = 1 The total number of mail document adds sent from a
device to the server.
DeviceSync.Documents.ToServer.Mail.Delete = 1 The total number of mail document deletes sent
from a device to the server.
DeviceSync.Documents.ToServer.Mail.Update = 1 The total number of mail document updates sent
from a device to the server.
DeviceSync.Documents.ToServer.ToDo.Add = 1 The total number of todo adds sent from a device
to the server.
DeviceSync.Documents.ToServer.ToDo.Delete = 1 The total number of todo deletes sent from a
device to the server.
DeviceSync.Documents.ToServer.ToDo.Update = 1 The total number of todo updates sent from a
device to the server.
DeviceSync.FetchCache.Add = 4 The total number of times that records could not be added to
the fetch cache because the cache was full.
DeviceSync.FetchCache.Oversize = 1 The total number of times records were added to the fetch
cache.
DeviceSync.FetchCache.Expired = 1 The total number of times records expired out of the cache
before they were fetched.
DeviceSync.FetchCache.Missing = 1 The total number of times the fetch cache was searched for
a record but records could not be found.
DeviceSync.Time.<SyncReturnCode>.Milliseconds
The amount of milliseconds that the server has spent (total) during device syncs. The most
common return codes are: 200=OK, 408=Request Timeout (Device did not respond before the Server
timed out the session), 409=Conflict (Device started a new session which caused this session to
be aborted), 500=Unknown Error, 503=Server Busy.
DeviceSync.Time.200.Milliseconds = 3094
DeviceSync.Time.<SyncReturnCode>.Days
The amount of days that the server has spent (total) during device syncs. This is only present
when the Milliseconds becomes too large, so the real value is the combination of the two. The
most common return codes are: 200=OK, 408=Request Timeout (Device did not respond before the
Server timed out the session), 409=Conflict (Device started a new session which caused this
session to be aborted), 500=Unknown Error, 503=Server Busy.
474 IBM Notes Traveler Hints and Tips for a Successful Deployment
DeviceSync.Time.200.days
DeviceSync.Time.Histogram.<SyncReturnCode>.<bucket>
Histogram of the time spent (in seconds) to complete the device sync with the given sync return
code. The most common return codes are: 200=OK, 408=Request Timeout (Device did not respond
before the Server timed out the session), 409=Conflict (Device started a new session which
caused this session to be aborted), 500=Unknown Error, 503=Server Busy Buckets are "000-001",
"001-002", "002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".
DeviceSync.Time.Histogram.200.000-001 = 18
GetAlarm.Time.Histogram.<bucket>
Number of errors logged for the specified type.
GetAlarm.Time.Histogram.000-001 = 3
IPC.DelayTime.<bucket>
Histogram of the time spent (in seconds) to get an Alarm UNID. Buckets are "000-001", "001-002",
"002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf".
IPC.DelayTime.00000-00500 = 30
IPC.DelayTime.01000-02000 = 1
Memory.C.Current = 960 C memory current
Memory.Java.Current = 30 Java memory current
Monitor.LoopTime.9.37.30.206.000-004 = 1138
Monitor.Users = 2 Users monitored in the mail server
NameLookup.Time.Histogram.<returncode>.<bucket>
Histogram of the time (in seconds) to complete the name lookup request. Return code 0 is success
and everything else is a failure. Buckets are "000-001", "001-002", "002-005", "005-010",
"010-030", "030-060", "060-120", "120-Inf".
NameLookup.Time.Histogram.0.000-001 = 10
NameLookup.Time.Histogram.8.000-001 = 1
PrimeSync.Count.<SyncReturnCode>
The number of prime syncs that had the specified return code. The most common return codes are:
200=OK, 408=Request Timeout (Device did not respond before the Server timed out the session),
409=Conflict (Device started a new session which caused this session to be aborted), 500=Unknown
Error, 503=Server Busy
PrimeSync.Count.200 = 12
PrimeSync.Count.Current = 0 The number of prime syncs that are currently running.
PrimeSync.Count.InQueue = 0 The number of prime syncs that are queued up and need to be run
but have not started running.
PrimeSync.Time.<SyncReturnCode>.Milliseconds
The amount of milliseconds that the server has spent (total) during prime syncs. Most common
return codes are: 200=OK, 408=Request Timeout (Device did not respond before the Server timed
Chapter 10. Appendix A 475
out the session), 409=Conflict (Device started a new session which caused this session to be
aborted), 500=Unknown Error, 503=Server Busy
PrimeSync.Time.200.Milliseconds = 2906
PrimeSync.Time.<SyncReturnCode>.Days
The amount of days that the server has spent (total) during prime syncs. This is only present
when the Milliseconds becomes too large, so the real value is the combination of the two. The
most common return codes are: 200=OK, 408=Request Timeout (Device did not respond before the
Server timed out the session), 409=Conflict (Device started a new session which caused this
session to be aborted), 500=Unknown Error, 503=Server Busy
PrimeSync.Time.200.Days = 2906
PrimeSync.Time.Histogram.<SyncReturnCode>.<bucket>
Histogram of the time spent (in seconds) to complete the prime sync with the given sync return
code. The most common return codes are: 200=OK, 408=Request Timeout (Device did not respond
before the Server timed out the session), 409=Conflict (Device started a new session which
caused this session to be aborted), 500=Unknown Error, 503=Server Busy Buckets are "000-001",
"001-002", "002-005", "005-010", "010-030", "030-060", "060-120", "120-Inf"
PrimeSync.Time.Histogram.200.000-001 = 12
Push.Devices.ActiveSync = 2 The number of devices registered for ActiveSync notifications.
Push.Devices.ActiveSync.Connected = 0 The number of devices with connected ActiveSync
sockets.
Push.Devices.Online = 2 The number of devices registered with push that are in the device
online or status unknown state. These states mean that the user's mail database is actively
being monitored for changes for this device; they do not indicate whether or not the device is
connected.
Push.Devices.Total = 2 The total number of devices registered with push.
Push.Received.ActiveSync = 2
Push.Sent.ActiveSync = 2
Push.Users.Online = 2 The number of users registered with push that are in the user online
state. The user online state means that the user's mail database is actively being monitored for
changes; it does not indicate whether or not a device for this user is connected.
Push.Users.Total = 2 The total number of users registered with push.
Status.State = Green
ThreadPool.Count.Max.Alarm = 4
ThreadPool.Count.Max.DS = 1
ThreadPool.Count.Max.PS = 2
ThreadPool.Count.Max.TC = 1
ThreadPool.Count.Max.Worker = 1
ThreadPool.GetThreadDelayTime.<threadtype>.<bucket>
Histogram of the time spent (in seconds) between a thread being requested and when it actually
started running. Thread types are PS (prime sync), DS (device sync), Worker (general usage), TC
(tell commands), and Alarm (periodic tasks). Buckets are "00-02", "02-05", "05-10", "10-Inf".
476 IBM Notes Traveler Hints and Tips for a Successful Deployment
For example, the stat ThreadPool.GetThreadDelayTime.PS.01-02 will hold the number of prim esyncs
that started with a delay of between 1 (inclusive) and 2 (exclusive) seconds.
ThreadPool.GetThreadDelayTime.Alarm.00-02 = 420
ThreadPool.GetThreadDelayTime.DS.00-02 = 16
ThreadPool.GetThreadDelayTime.PS.00-02 = 12
ThreadPool.GetThreadDelayTime.TC.00-02 = 3
ThreadPool.GetThreadDelayTime.Worker.00-02 = 32
Version = 8.5.3.100 The Lotus Notes Traveler Version.
Version.BuildNumber = 201206132102 The Lotus Notes Traveler Build Number.
There are 2 users known to the system.
100 percent (2) of the users are online or have been within the past 24 hours.
There are 2 mailfiles currently being monitored for these online users.
There are 2 devices known to the system.
100 percent (2) of the devices are registered for ActiveSync notifications.
100 percent (2) of the devices are online or have been within the past 24 hours.
There have been 12 prime syncs.
The average prime sync took 242 ms.
100 percent (12) of the prime syncs were successful.
The average successful prime sync took 242 ms.
0 percent (0) of the prime syncs failed.
The average failed prime sync took N/A ms.
There are an average of 0.001 prime syncs running at any given time.
There have been 18 device syncs.
The average device sync took 171 ms and transferred 195 bytes.
100 percent (18) of the device syncs were successful.
The average successful device sync took 171 ms.
0 percent (0) of the device syncs failed.
The average failed device sync took N/A ms.
There are an average of 0.001 device syncs occurring at any given time.
The Lotus Notes Traveler task has been running since 9/5/12 11:28 AM.
Domino Statistics
########## Domino Statistics (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: List of all the Domino Platform, HTTP, server statistics that have
been collected since the stats were last reset (the statistics are automatically
reset each time the Domino server is restarted).
Http.Accept.ConnectionsAccepted = 87
Http.Accept.ConnectionsDenied = 0
Http.Accept.ConnectionsRefused = 0
Http.Accept.Errors = 0
Http.Accept.PollTimeouts = 17548
Chapter 10. Appendix A 477
Http.Accept.Polls = 17636
Http.Accept.ServerBusy = 0
Http.CurrentConnections = 0
Http.JavaCache.Enabled = 1
Http.JavaCache.Entries.Current = 0
Http.JavaCache.Entries.Maximum = 1000
Http.JavaCache.Prune.Run.Interval = 10
Http.JavaCache.Prune.Run.Next = 09/05/2012 12:29:36 EDT
Http.JavaCache.Prune.Time.Locked.Avg = 0
Http.JavaCache.Prune.Time.Locked.Max = 0
Http.JavaCache.Prune.Time.Locked.Min = 0
Http.JavaCache.Prune.Time.Total.Avg = 0
Http.JavaCache.Prune.Time.Total.Max = 0
Http.JavaCache.Prune.Time.Total.Min = 0
Http.JavaCache.Size.Current = 0
Http.JavaCache.Size.Maximum = 4000000
Http.JavaCache.Total.Adds = 0
Http.JavaCache.Total.Adds.Missed = 0
Http.JavaCache.Total.Errors = 0
Http.JavaCache.Total.Hits = 0
Http.JavaCache.Total.Misses = 0
Http.MaxConnections = 2000
Http.PeakConnections = 10
Http.Worker.Total.BytesRead = 448,787
Http.Worker.Total.BytesWritten = 2,165,956
Http.Worker.Total.Cgi.RequestTime = 0
Http.Worker.Total.Cgi.Requests = 0
Http.Worker.Total.DomWS.RequestTime = 0
Http.Worker.Total.DomWS.Requests = 0
Http.Worker.Total.Dsapi.RequestTime = 0
Http.Worker.Total.Dsapi.Requests = 0
Http.Worker.Total.File.RequestTime = 107
Http.Worker.Total.File.Requests = 37
Http.Worker.Total.Http.RequestTime = 0
Http.Worker.Total.Http.Requests = 0
Http.Worker.Total.IdleSessionTimeouts = 0
Http.Worker.Total.InputTimeouts = 6
Http.Worker.Total.Notes.RequestTime = 1,812,422
Http.Worker.Total.Notes.Requests = 634
Http.Worker.Total.OutputTimeouts = 0
Http.Worker.Total.QuickPlace.RequestTime = 0
Http.Worker.Total.QuickPlace.Requests = 0
Http.Worker.Total.RequestsProcessed = 671
Http.Worker.Total.TotalRequestTime = 1,812,529
Http.Workers = 100
Platform.ActiveNumOfDominoPartitions = 1
Platform.LogicalDisk.1.AssignedName = C
Platform.LogicalDisk.1.AvgQueueLen = 0.01
Platform.LogicalDisk.1.AvgQueueLen.Avg = 0
Platform.LogicalDisk.1.AvgQueueLen.Peak = 0.03
Platform.LogicalDisk.1.BytesReadPerSec = 19,674.95
Platform.LogicalDisk.1.BytesWrittenPerSec = 44,215.29
Platform.LogicalDisk.1.PctUtil = 1.05
Platform.LogicalDisk.1.PctUtil.Avg = 0.29
Platform.LogicalDisk.1.PctUtil.Peak = 3.47
478 IBM Notes Traveler Hints and Tips for a Successful Deployment
Platform.LogicalDisk.1.ReadsPerSec = 1.88
Platform.LogicalDisk.1.WritesPerSec = 5.94
Platform.LogicalDisk.TotalNumofDisks = 1
Platform.Memory.PageFaultsPerSec = 520.08
Platform.Memory.PagesPerSec = 3.97
Platform.Memory.PagesPerSec.Avg = 3.09
Platform.Memory.PagesPerSec.Peak = 134.97
Platform.Memory.RAM.AvailMBytes = 972
Platform.Memory.RAM.AvailMBytes.Avg = 995.02
Platform.Memory.RAM.AvailMBytes.Min = 928
Platform.Memory.RAM.AvailMBytes.Peak = 1,099
Platform.Memory.RAM.PctUtil = 52
Platform.Memory.RAM.TotalMBytes = 2048
Platform.Network.1.AdapterName = Intel[R] PRO_1000 MT Network Connection
Platform.Network.1.BytesRecvdPerSec = 2,369.29
Platform.Network.1.BytesSentPerSec = 1,582.55
Platform.Network.1.CurrBandwidthMbitsPerSec = 1,000
Platform.Network.1.TotalBytesPerSec = 3,951.84
Platform.Network.2.AdapterName = MS TCP Loopback interface
Platform.Network.2.BytesRecvdPerSec = 132.7
Platform.Network.2.BytesSentPerSec = 132.7
Platform.Network.2.CurrBandwidthMbitsPerSec = 10
Platform.Network.2.TotalBytesPerSec = 265.41
Platform.Network.Total.BytesRecvdPerSec = 2,502
Platform.Network.Total.BytesSentPerSec = 1,715.26
Platform.Network.Total.CurrBandwidthMbitsPerSec = 1,010
Platform.Network.Total.NetworkBytesPerSec = 4,217.25
Platform.Network.TotalNumofAdapters = 2
Platform.PagingFile.Total.PctUtil = 0.04
Platform.PagingFile.Total.PctUtil.Avg = 0.03
Platform.PagingFile.Total.PctUtil.Peak = 0.04
Platform.Process.ActiveDomino.TotalCpuUtil = 0.45
Platform.Process.ActiveNumOfDominoProc = 15
Platform.Process.adminp.1.DominoLocalFreeKBytes = 250
Platform.Process.adminp.1.DominoSharedFreeKBytes = 41,714
Platform.Process.adminp.1.MemFreeKBytes = 1,780,204
Platform.Process.adminp.1.MemUsedKBytes = 42,032
Platform.Process.adminp.1.PctCpuUtil = 0.08
Platform.Process.adminp.1.PgFaultsPerSec = 1.17
Platform.Process.adminp.1.ProcessID = 1228
Platform.Process.adminp.1.VMSizeKBytes = 16,492
Platform.Process.amgr.1.DominoLocalFreeKBytes = 289
Platform.Process.amgr.1.DominoSharedFreeKBytes = 41,714
Platform.Process.amgr.1.MemFreeKBytes = 1,769,856
Platform.Process.amgr.1.MemUsedKBytes = 21,528
Platform.Process.amgr.1.PctCpuUtil = 0
Platform.Process.amgr.1.PgFaultsPerSec = 0
Platform.Process.amgr.1.ProcessID = 3580
Platform.Process.amgr.1.VMSizeKBytes = 16,520
Platform.Process.amgr.2.DominoLocalFreeKBytes = 1,229
Platform.Process.amgr.2.DominoSharedFreeKBytes = 41,714
Platform.Process.amgr.2.MemFreeKBytes = 1,764,112
Platform.Process.amgr.2.MemUsedKBytes = 25,128
Platform.Process.amgr.2.PctCpuUtil = 0
Platform.Process.amgr.2.PgFaultsPerSec = 0
Chapter 10. Appendix A 479
Platform.Process.amgr.2.ProcessID = 816
Platform.Process.amgr.2.VMSizeKBytes = 18,872
Platform.Process.calconn.1.DominoLocalFreeKBytes = 294
Platform.Process.calconn.1.DominoSharedFreeKBytes = 41,714
Platform.Process.calconn.1.MemFreeKBytes = 1,782,940
Platform.Process.calconn.1.MemUsedKBytes = 12,736
Platform.Process.calconn.1.PctCpuUtil = 0
Platform.Process.calconn.1.PgFaultsPerSec = 0
Platform.Process.calconn.1.ProcessID = 2840
Platform.Process.calconn.1.VMSizeKBytes = 15,976
Platform.Process.event.1.DominoLocalFreeKBytes = 876
Platform.Process.event.1.DominoSharedFreeKBytes = 41,714
Platform.Process.event.1.MemFreeKBytes = 1,766,840
Platform.Process.event.1.MemUsedKBytes = 66,632
Platform.Process.event.1.PctCpuUtil = 0
Platform.Process.event.1.PgFaultsPerSec = 0.15
Platform.Process.event.1.ProcessID = 4600
Platform.Process.event.1.VMSizeKBytes = 21,532
Platform.Process.http.1.DominoLocalFreeKBytes = 1,987
Platform.Process.http.1.DominoSharedFreeKBytes = 41,714
Platform.Process.http.1.MemFreeKBytes = 1,458,932
Platform.Process.http.1.MemUsedKBytes = 180,580
Platform.Process.http.1.PctCpuUtil = 0
Platform.Process.http.1.PgFaultsPerSec = 0
Platform.Process.http.1.ProcessID = 5728
Platform.Process.http.1.VMSizeKBytes = 194,752
Platform.Process.ldap.1.DominoLocalFreeKBytes = 1,212
Platform.Process.ldap.1.DominoSharedFreeKBytes = 41,714
Platform.Process.ldap.1.MemFreeKBytes = 1,770,508
Platform.Process.ldap.1.MemUsedKBytes = 37,116
Platform.Process.ldap.1.PctCpuUtil = 0.16
Platform.Process.ldap.1.PgFaultsPerSec = 8.37
Platform.Process.ldap.1.ProcessID = 4116
Platform.Process.ldap.1.VMSizeKBytes = 21,440
Platform.Process.procmon.1.DominoLocalFreeKBytes = 294
Platform.Process.procmon.1.DominoSharedFreeKBytes = 41,714
Platform.Process.procmon.1.MemFreeKBytes = 1,782,944
Platform.Process.procmon.1.MemUsedKBytes = 13,332
Platform.Process.procmon.1.PctCpuUtil = 0
Platform.Process.procmon.1.PgFaultsPerSec = 0
Platform.Process.procmon.1.ProcessID = 2788
Platform.Process.procmon.1.VMSizeKBytes = 15,976
Platform.Process.replica.1.DominoLocalFreeKBytes = 288
Platform.Process.replica.1.DominoSharedFreeKBytes = 41,714
Platform.Process.replica.1.MemFreeKBytes = 1,781,676
Platform.Process.replica.1.MemUsedKBytes = 17,612
Platform.Process.replica.1.PctCpuUtil = 0
Platform.Process.replica.1.PgFaultsPerSec = 0
Platform.Process.replica.1.ProcessID = 2464
Platform.Process.replica.1.VMSizeKBytes = 16,248
Platform.Process.rnrmgr.1.DominoLocalFreeKBytes = 262
Platform.Process.rnrmgr.1.DominoSharedFreeKBytes = 41,714
Platform.Process.rnrmgr.1.MemFreeKBytes = 1,781,596
Platform.Process.rnrmgr.1.MemUsedKBytes = 21,368
Platform.Process.rnrmgr.1.PctCpuUtil = 0
480 IBM Notes Traveler Hints and Tips for a Successful Deployment
Platform.Process.rnrmgr.1.PgFaultsPerSec = 0
Platform.Process.rnrmgr.1.ProcessID = 4120
Platform.Process.rnrmgr.1.VMSizeKBytes = 16,296
Platform.Process.router.1.DominoLocalFreeKBytes = 675
Platform.Process.router.1.DominoSharedFreeKBytes = 41,714
Platform.Process.router.1.MemFreeKBytes = 1,768,372
Platform.Process.router.1.MemUsedKBytes = 26,496
Platform.Process.router.1.PctCpuUtil = 0
Platform.Process.router.1.PgFaultsPerSec = 1.15
Platform.Process.router.1.ProcessID = 4460
Platform.Process.router.1.VMSizeKBytes = 22,632
Platform.Process.sched.1.DominoLocalFreeKBytes = 262
Platform.Process.sched.1.DominoSharedFreeKBytes = 41,714
Platform.Process.sched.1.MemFreeKBytes = 1,780,600
Platform.Process.sched.1.MemUsedKBytes = 21,452
Platform.Process.sched.1.PctCpuUtil = 0
Platform.Process.sched.1.PgFaultsPerSec = 0
Platform.Process.sched.1.ProcessID = 2088
Platform.Process.sched.1.VMSizeKBytes = 16,564
Platform.Process.server.1.DominoLocalFreeKBytes = 1,123
Platform.Process.server.1.DominoSharedFreeKBytes = 41,714
Platform.Process.server.1.MemFreeKBytes = 1,681,348
Platform.Process.server.1.MemUsedKBytes = 52,068
Platform.Process.server.1.PctCpuUtil = 0.16
Platform.Process.server.1.PgFaultsPerSec = 3.23
Platform.Process.server.1.ProcessID = 3768
Platform.Process.server.1.VMSizeKBytes = 44,220
Platform.Process.traveler.1.DominoLocalFreeKBytes = 768
Platform.Process.traveler.1.DominoSharedFreeKBytes = 41,714
Platform.Process.traveler.1.MemFreeKBytes = 1,113,228
Platform.Process.traveler.1.MemUsedKBytes = 193,164
Platform.Process.traveler.1.PctCpuUtil = 0.05
Platform.Process.traveler.1.PgFaultsPerSec = 6.69
Platform.Process.traveler.1.ProcessID = 5800
Platform.Process.traveler.1.VMSizeKBytes = 165,128
Platform.Process.update.1.DominoLocalFreeKBytes = 279
Platform.Process.update.1.DominoSharedFreeKBytes = 41,714
Platform.Process.update.1.MemFreeKBytes = 1,777,644
Platform.Process.update.1.MemUsedKBytes = 27,600
Platform.Process.update.1.PctCpuUtil = 0
Platform.Process.update.1.PgFaultsPerSec = 0
Platform.Process.update.1.ProcessID = 1816
Platform.Process.update.1.VMSizeKBytes = 18,812
Platform.System.ContextSwitchesPerSec = 1,034.65
Platform.System.PctCombinedCpuUtil = 1
Platform.System.PctTotalPrivilegedCpuUtil = 0.57
Platform.System.PctTotalUserCpuUtil = 0.43
Platform.Time.LastSample = 09/05/2012 12:29:03 EDT
Platform.Time.SampleRateInMins = 1
Server.Administrators = CN=Administrator/O=organization
Server.Administrators.Access = CN=Administrator/O=organization
Server.AvailabilityIndex = 100
Server.AvailabilityThreshold = 0
Server.BootID = 5573167
Server.CPU.Count = 2
Chapter 10. Appendix A 481
Server.CPU.Type = Intel Pentium
Server.ConcurrentTasks = 0
Server.ConcurrentTasks.Max = 2
Server.ConcurrentTasks.UpperBound = 40
Server.ConcurrentTasks.Waiting = 0
Server.ElapsedTime = 01:00:01
Server.ExpansionFactor = 1
Server.MailBoxes = 1
Server.Monitor.Start = 09/05/2012 11:28:52 EDT
Server.Monitor.Threads = 1
Server.Name = CN=9.37.30.206/O=organization
Server.Path.Configfile = C:\IBM\Lotus\Domino\notes.ini
Server.Path.Data = C:\IBM\Lotus\Domino\data
Server.Path.Executable = C:\IBM\Lotus\Domino\
Server.Ports = TCPIP
Server.PoweredBy = Notes
Server.RecentContactSync.Entries.Added = 0
Server.RecentContactSync.Entries.Found = 0
Server.RecentContactSync.Entries.InUse = 0
Server.RecentContactSync.Lookups.Allowed = 0
Server.RecentContactSync.Lookups.Blocked = 0
Server.Sessions.AuthAvgMSecs = 0
Server.Sessions.Authenticated = 119
Server.Sessions.Dropped = 0
Server.SharedMail = 0
Server.SmartUpgrade.Users.Current = 0
Server.Task = Event Monitor: Idle: [09/05/2012 12:28:52 EDT]
Server.Task.DB = Database Server: Idle: [09/05/2012 12:28:53 EDT]
Server.Tasks = 95
Server.Time.Start = 09/05/2012 11:28:52 EDT
Server.Title =
Server.Trans.PerMinute = 20
Server.Trans.PerMinute.Peak = 272
Server.Trans.PerMinute.Peak.Time = 09/05/2012 11:32:53 EDT
Server.Trans.Total = 1661
Server.Users = 3
Server.Users.1MinPeak = 3
Server.Users.1MinPeakTime = 09/05/2012 11:33:53 EDT
Server.Users.5MinPeak = 3
Server.Users.5MinPeakTime = 09/05/2012 11:33:53 EDT
Server.Users.Active = 0
Server.Users.Active15Min = 1
Server.Users.Active1Min = 1
Server.Users.Active30Min = 2
Server.Users.Active3Min = 1
Server.Users.Active5Min = 1
Server.Users.Peak = 5
Server.Users.Peak.Time = 09/05/2012 11:33:00 EDT
Server.Version.Architecture = 32 Bit
Server.Version.NIFODS_VERSION = 114
Server.Version.Notes = Release 8.5.3
Server.Version.Notes.BuildNumber = 390
Server.Version.ODS_MACHINETYPE = 0
Server.Version.OS = Windows/2003 5.2 Intel Pentium
482 IBM Notes Traveler Hints and Tips for a Successful Deployment
Server.WorkThreads.TCPIP = 40
PushServer (Wed Sep 05 12:29:04 EDT 2012)
########## PushServer (Wed Sep 05 12:29:04 EDT 2012) ##########
-- user2UserCNMap --
State Controller (Wed Sep 05 12:29:04 EDT 2012)
########## State Controller (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: Current device and user states utilized by push.
running: true
statusUnknownTimeout: 86400000 ms
deviceOfflineTimeout: 2592000000 ms
reapInterval: 18000000 ms
-- deviceIdToStateMap (Wed Sep 05 12:29:04 EDT 2012) --
CN=t
u1/O=organization:Appl1B017URA75J=ESM_PUSH_STATE_WAITING_FOR_MESSAGE_FROM_DEVICE
CN=t
u3/O=organization:Appl1B017URA75J=ESM_PUSH_STATE_WAITING_FOR_MESSAGE_FROM_DEVICE
-- userIdToStateMap (Wed Sep 05 12:29:04 EDT 2012) --
CN=t u1/O=organization=ESM_PUSH_STATE_ONLINE
CN=t u3/O=organization=ESM_PUSH_STATE_ONLINE
-- timerQueue (StateController) --
DelayQueue (Name: StateController, Size: 3 object(s), Head: { dequeues at
1346876937959 [2012-09-05 16:28:57.959 EDT], enqueued at 1346858937959 [2012-09-05
11:28:57.959 EDT], reap }, Current Date: Wed Sep 05 12:29:04 EDT 2012)
{ dequeues at 1346876937959 [2012-09-05 16:28:57.959 EDT], enqueued at
1346858937959 [2012-09-05 11:28:57.959 EDT], reap }
{ dequeues at 1346947095203 [2012-09-06 11:58:15.203 EDT], enqueued at
1346860695203 [2012-09-05 11:58:15.203 EDT], CN=t
u3/O=organization:Appl1B017URA75J }
{ dequeues at 1346947095204 [2012-09-06 11:58:15.204 EDT], enqueued at
1346860695203 [2012-09-05 11:58:15.203 EDT], CN=t
u1/O=organization:Appl1B017URA75J }
obj2DqeMap (Object To DelayQueueElement Map) (3 objects sorted by dequeue time)
{ dequeues at 1346876937959 [2012-09-05 16:28:57.959 EDT], enqueued at
1346858937959 [2012-09-05 11:28:57.959 EDT], reap }
{ dequeues at 1346947095203 [2012-09-06 11:58:15.203 EDT], enqueued at
1346860695203 [2012-09-05 11:58:15.203 EDT], CN=t
u3/O=organization:Appl1B017URA75J }
{ dequeues at 1346947095204 [2012-09-06 11:58:15.204 EDT], enqueued at
1346860695203 [2012-09-05 11:58:15.203 EDT], CN=t
u1/O=organization:Appl1B017URA75J }
Chapter 10. Appendix A 483
MasterMonitor (Wed Sep 05 12:29:04 EDT 2012
########## MasterMonitor (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: Status of the users being enabled for monitoring of mail database changes and the
current state for those being monitored.
Monitoring is the process by which Traveler detects changes in the user's mail
database on a periodic basis. When a change is detected, the user is enqueued for a prime sync
which may result in push messages if push is enabled.
Monitoring can be done against any of the user's mail servers (replicas) with an
affinity for the user's home mail server, but this shows which users are currently being
monitored on which servers.
If a user is not being actively monitored, changes in the user's mail database will
not be known to Lotus Notes Traveler and all syncs will be empty of server side data.
Shutdown: false
Enabled: true
Debug: false
-- enableQueue (Monitor) --
DelayQueue (Name: Monitor, Size: 0 object(s), Head: null, Current Date: Wed Sep 05 12:29:04 EDT
2012)
obj2DqeMap (Object To DelayQueueElement Map) (0 objects sorted by dequeue time)
----- Monitor Info for CN=9.37.30.206/O=organization(Mntr-9.37.30.206-854) (Wed Sep 05 12:29:04
EDT 2012) -----
shutdownRequested: false
Monitor.LoopTime.9.37.30.206.000-004 = {Long,1138}
-- ServerDBsInfo (Wed Sep 05 12:29:04 EDT 2012) --
ServerDbsInfo[ CN=9.37.30.206/O=organization, BuildNumber=390 supportsWatchedList=true,
1346862544330 (Wed Sep 05 12:29:04 EDT 2012) backLevel=false, User Count=2 {mail/tu1.nsf=CN=t
u1/O=organization, mail/tu3.nsf=CN=t u3/O=organization}]
-- user2ServerDbPairMap (Wed Sep 05 12:29:04 EDT 2012) --
CN=t u1/O=organization=[userName='CN=t u1/O=organization'
serverName='CN=9.37.30.206/O=organization' path='mail/tu1.nsf']
CN=t u3/O=organization=[userName='CN=t u3/O=organization'
serverName='CN=9.37.30.206/O=organization' path='mail/tu3.nsf']
Heartbeat Discovery Queue (Wed Sep 05 12:29:04 EDT 2012)
########## Heartbeat Discovery Queue (Wed Sep 05 12:29:04 EDT 2012) ##########
-- DiscDelQ --
DelayQueue (Name: DiscDelQ, Size: 0 object(s), Head: null, Current Date: Wed Sep
05 12:29:04 EDT 2012)
obj2DqeMap (Object To DelayQueueElement Map) (0 objects sorted by dequeue time)
Change Processing (Wed Sep 05 12:29:04 EDT 2012)
########## Change Processing (Wed Sep 05 12:29:04 EDT 2012) ##########
484 IBM Notes Traveler Hints and Tips for a Successful Deployment
Description: List of the users with detected changes in the mail database for
which a prime sync needs to be run.
running: true
-- usersWithChangesQueue (ChangeProcessor) --
DelayQueue (Name: ChangeProcessor, Size: 1 object(s), Head: { dequeues at
1346873338959 [2012-09-05 15:28:58.959 EDT], enqueued at 1346858938959 [2012-09-05
11:28:58.959 EDT], primesyncTimer }, Current Date: Wed Sep 05 12:29:04 EDT 2012)
{ dequeues at 1346873338959 [2012-09-05 15:28:58.959 EDT], enqueued at
1346858938959 [2012-09-05 11:28:58.959 EDT], primesyncTimer }
obj2DqeMap (Object To DelayQueueElement Map) (1 objects sorted by dequeue time)
{ dequeues at 1346873338959 [2012-09-05 15:28:58.959 EDT], enqueued at
1346858938959 [2012-09-05 11:28:58.959 EDT], primesyncTimer }
Connection Manager (Wed Sep 05 12:29:04 EDT 2012)
########## Connection Manager (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: Statistics for current connections and peak connections. List of all
current connections between devices and the server.
-- Current Total Connection Counts (Wed Sep 05 12:29:04 EDT 2012): 0 --
-- Peak Connection Counts and Times (Wed Sep 05 12:29:04 EDT 2012) --
ConnectionManager.Peak.GET.Count: 1
ConnectionManager.Peak.GET.Time: Wed Sep 05 11:31:32 EDT 2012
ConnectionManager.Peak.Total.Count: 2
ConnectionManager.Peak.Total.Time: Wed Sep 05 11:43:20 EDT 2012
ConnectionManager.Peak.getClientConfigFile.Count: 1
ConnectionManager.Peak.getClientConfigFile.Time: Wed Sep 05 11:31:54 EDT 2012
ConnectionManager.Peak.getConfigAS.Count: 1
ConnectionManager.Peak.getConfigAS.Time: Wed Sep 05 11:33:02 EDT 2012
ConnectionManager.Peak.pushAS.Count: 2
ConnectionManager.Peak.pushAS.Time: Wed Sep 05 11:43:20 EDT 2012
ConnectionManager.Peak.syncAS.Count: 1
ConnectionManager.Peak.syncAS.Time: Wed Sep 05 11:35:11 EDT 2012
-- Current Connections (Wed Sep 05 12:29:04 EDT 2012): 0 --
Connection SMS Sender (Wed Sep 05 12:29:04 EDT 2012)
########## Connection SMS Sender (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: List of all pending SMS messages to be sent.
-- MS-SMS-DelQ --
DelayQueue (Name: MS-SMS-DelQ, Size: 0 object(s), Head: null, Current Date: Wed
Sep 05 12:29:04 EDT 2012)
obj2DqeMap (Object To DelayQueueElement Map) (0 objects sorted by dequeue time)
Chapter 10. Appendix A 485
Listener Store (Wed Sep 05 12:29:04 EDT 2012)
########## Listener Store (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: Each Listener represents the push state of a user's device. Thus,
the list of Listeners is the list of devices known to the system.
-- Listeners --
Record Count (Wed Sep 05 12:29:04 EDT 2012): 2
User ID = CN=t u1/O=organization; Device ID = Appl1B017URA75J; Account ID
(database ID) = 1050; Device ID (database ID) = 1051; Notification Type =
ActiveSync; SeqNumber = 9; Applications to Synchronize = folder, mail, calendar,
contact, serviceability, security; Application Folders to Synchronize = mail:4,
calendar:3, contact:2; Change Flags = mail:add(1057:add); Connection =
Disconnected (Wed Sep 05 11:58:15 EDT 2012); Last Message Received = Wed Sep 05
11:43:20 EDT 2012; Last Message Sent = Wed Sep 05 11:58:15 EDT 2012; Next Message
Scheduled to be Sent = Wed Sep 05 12:13:10 EDT 2012 (in -954 seconds); Discovery
Queue Element = User ID = CN=t u1/O=organization, Device ID = Appl1B017URA75J,
Current Interval (seconds) = 895, Current Upper Bound (seconds) = 900
User ID = CN=t u3/O=organization; Device ID = Appl1B017URA75J; Account ID
(database ID) = 2050; Device ID (database ID) = 2051; Notification Type =
ActiveSync; SeqNumber = 5; Applications to Synchronize = folder, mail, calendar,
contact, serviceability, security; Application Folders to Synchronize = mail:4,
calendar:3, contact:2; Change Flags = clear; Connection = Disconnected (Wed Sep 05
11:58:15 EDT 2012); Last Message Received = Wed Sep 05 11:43:19 EDT 2012; Last
Message Sent = Wed Sep 05 11:58:15 EDT 2012; Next Message Scheduled to be Sent =
Wed Sep 05 12:13:10 EDT 2012 (in -954 seconds); Discovery Queue Element = User ID
= CN=t u3/O=organization, Device ID = Appl1B017URA75J, Current Interval (seconds)
= 895, Current Upper Bound (seconds) = 900
Security Record Store (Wed Sep 05 12:29:04 EDT 2012)
These are the security records for the users and the devices. This is a reflection of the
security table that Lotus Notes Traveler maintains.
########## Security Record Store (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: The security record tracks any security action requests (for example,
wipe) as well as the status of any requests. If any Security Flag is set for the
user's device, the device is denied access to the system.
The security records must be explicitly cleared to regain access to
the system and are NOT cleared with a delete or reset command to prevent access
after a device has been reaped.
If a user has access to the system but a particular device for that
user is being denied access to the system, it could be because the device has a
Security Flag set in the Security Record.
The approval state of the device is appended to the end of the
security record. Unlike the other security actions where the user may be able to
take the actions themselves, the Administrator must take all approval related
actions as needed.
-- Security Records (User:Device:SMS Address:Nonce:Time Created:Time
Requested:Time Executed:Security Flags:Security Flags Failed:Failure Reason
Code:Requester ID:Approval State:Approver ID:Approval Time) --
Record Count (Wed Sep 05 12:29:04 EDT 2012): 2
486 IBM Notes Traveler Hints and Tips for a Successful Deployment
CN=t u1/O=organization:Appl1B017URA75J:null:2533859233:Wed Sep 05 11:23:34 EDT
2012:Never:Never:none:none:0:null:Not required:null:Never
CN=t u3/O=organization:Appl1B017URA75J:null:2534419247:Wed Sep 05 11:32:12 EDT
2012:Never:Never:none:none:0:null:Not required:null:Never
Show Active (Wed Sep 05 12:29:04 EDT 2012)
These are the active users on the server (those currently connected).
########## Show Active (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: List of the users actively syncing and the type of sync.
Number of Active Users: 0
User Cache (Wed Sep 05 12:29:04 EDT 2012)
These are the users that Traveler is aware of.
########## User Cache (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: User information cached by the system to limit the number of Domino
database accesses.
UserCacheManager (Wed Sep 05 12:29:04 EDT 2012): 2 entries in the cache.
*********** Record # 1 ***********
User: CN=t u1/O=organization
DominoDBInfo: CN=t u1/O=organization InternetAddress=null Active
Server=CN=9.37.30.206/O=organization Active Path=mail/tu1.nsf Primary
Server=CN=9.37.30.206/O=organization Primary Path=mail/tu1.nsf Mail
Domain=domainTravelerAccessRights=allow Has Validated DB=False ExplicitPolicy=null
ShortName List=[tu1] FullName List=[CN=t u1/O=organization, t u1] designFlags=null
NTSPreferences - User Settings:{_canonicalName=CN=t u1/O=organization,
devPNotifyAddress=, -5limit=7, -26limit=3, devPApprovalEnable=0,
_mailPath=mail/tu1.nsf, _adminMaxAttSize=4000, devPApprovalNumber=1,
!TimezoneID=sun.util.calendar.ZoneInfo[id="America/New_York",offset=-18000000,dstS
avings=3600000,useDaylight=true,transitions=235,lastRule=java.util.SimpleTimeZone[
id=America/New_York,offset=-18000000,dstSavings=3600000,useDaylight=true,startYear
=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTim
eMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=
0]], _userAccountID=1050, -3limit=30, _mailServer=CN=9.37.30.206/O=organization}
NTSPreferences - URI Mappings:{./Task=URI: http://localhost/mailfile.nsf LOOKUP:
true, ./Folder=URI: http://localhost/mailfile.nsf LOOKUP: true, ./Contact=URI:
http://localhost/mailfile.nsf LOOKUP: true, ./Event=URI:
http://localhost/mailfile.nsf LOOKUP: true, ./EMail=URI:
http://localhost/mailfile.nsf LOOKUP: true, ./Note=URI:
http://localhost/mailfile.nsf LOOKUP: true}
NTSPreferences - Device
Preferences:{Appl1B017URA75J={!sync_SyncFilterCaf=includeAttachments=false,
!sync_SyncFilterEvent=startdate>=last:30:days, -5limit=7,
!sync_SyncFilterProtocol=ACTIVESYNC, _preferLang=en, -26limit=3,
!sync_SyncFilterEMail=receiveddate>=last:3:days, devPappls=1:2:4,
!sync_conflict=DeviceLoses, devPinfo=Apple-iPod2C1:Apple-iPod2C1/803.148 (OS 4),
Chapter 10. Appendix A 487
!sync_SyncFilterTask=complete=f, !sync_SyncFilterNote=modtime>=last:7:days,
-3limit=30, !sync_direction=Sync}}
NTSPreferences - Device Filters:{!sync_SyncFilterAppl1B017URA75JTask=complete=f,
!sync_SyncFilterDevices=Appl1B017URA75J,
!sync_SyncFilterAppl1B017URA75JProtocol=ACTIVESYNC,
!sync_SyncFilterAppl1B017URA75JEMail=receiveddate>=last:3:days,
!sync_SyncFilterAppl1B017URA75JNote=modtime>=last:7:days,
!sync_SyncFilterAppl1B017URA75JEvent=startdate>=last:30:days}
*********** Record # 2 ***********
User: CN=t u3/O=organization
DominoDBInfo: CN=t u3/O=organization InternetAddress=null Active
Server=CN=9.37.30.206/O=organization Active Path=mail/tu3.nsf Primary
Server=CN=9.37.30.206/O=organization Primary Path=mail/tu3.nsf Mail
Domain=domainTravelerAccessRights=allow Has Validated DB=True ExplicitPolicy=null
ShortName List=[tu3] FullName List=[CN=t u3/O=organization, t u3] designFlags=null
NTSPreferences - User Settings:{_canonicalName=CN=t u3/O=organization,
devPNotifyAddress=, -5limit=7, -26limit=3, devPApprovalEnable=0,
_mailPath=mail/tu3.nsf, _adminMaxAttSize=4000, devPApprovalNumber=1,
!TimezoneID=sun.util.calendar.ZoneInfo[id="America/New_York",offset=-18000000,dstS
avings=3600000,useDaylight=true,transitions=235,lastRule=java.util.SimpleTimeZone[
id=America/New_York,offset=-18000000,dstSavings=3600000,useDaylight=true,startYear
=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTim
eMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=
0]], _userAccountID=2050, -3limit=30, _mailServer=CN=9.37.30.206/O=organization}
NTSPreferences - URI Mappings:{./Task=URI: http://localhost/mailfile.nsf LOOKUP:
true, ./Folder=URI: http://localhost/mailfile.nsf LOOKUP: true, ./Contact=URI:
http://localhost/mailfile.nsf LOOKUP: true, ./Event=URI:
http://localhost/mailfile.nsf LOOKUP: true, ./EMail=URI:
http://localhost/mailfile.nsf LOOKUP: true, ./Note=URI:
http://localhost/mailfile.nsf LOOKUP: true}
NTSPreferences - Device
Preferences:{Appl1B017URA75J={!sync_SyncFilterCaf=includeAttachments=false,
!sync_SyncFilterEvent=startdate>=last:30:days, -5limit=7,
!sync_SyncFilterProtocol=ACTIVESYNC, _preferLang=en, -26limit=3,
!sync_SyncFilterEMail=receiveddate>=last:3:days, devPappls=1:2:4,
!sync_conflict=DeviceLoses, devPinfo=Apple-iPod2C1:Apple-iPod2C1/803.148 (OS 4),
!sync_SyncFilterTask=complete=f, !sync_SyncFilterNote=modtime>=last:7:days,
-3limit=30, !sync_direction=Sync}}
NTSPreferences - Device Filters:{!sync_SyncFilterAppl1B017URA75JTask=complete=f,
!sync_SyncFilterDevices=Appl1B017URA75J,
!sync_SyncFilterAppl1B017URA75JProtocol=ACTIVESYNC,
!sync_SyncFilterAppl1B017URA75JEMail=receiveddate>=last:3:days,
!sync_SyncFilterAppl1B017URA75JNote=modtime>=last:7:days,
!sync_SyncFilterAppl1B017URA75JEvent=startdate>=last:30:days}
Address Cache (Wed Sep 05 12:29:04 EDT 2012)
########## Address Cache (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: Email address information cached by the system to limit the number of
Domino database accesses.
488 IBM Notes Traveler Hints and Tips for a Successful Deployment
AddressCacheManager (Wed Sep 05 12:29:04 EDT 2012): 4 entries in the cache out of
a maximum of 10000 entries.
Key: t u1/organization, Canonical Name: null, Internet Address: null
Key: t u2/organization, Canonical Name: null, Internet Address: null
Key: t u3/organization, Canonical Name: null, Internet Address: null
Key: Tu1@9.37.30.206, Canonical Name: null, Internet Address: null
Fetch Cache (Wed Sep 05 12:29:04 EDT 2012)
########## Fetch Cache (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: ActiveSync devices may request a plain text version of a document and
then come back and ask for the rich text version of the same document.
The device may make these two requests in quick succession, so this
cache contains the rich text version of the document to limit having to go back to
the Domino mail database to get the rich text version of the document.
FetchCacheManager (Wed Sep 05 12:29:04 EDT 2012): 0 entries in the cache using
approximately 0 bytes.
Nonce Cache (Wed Sep 05 12:29:04 EDT 2012)
########## Nonce Cache (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: Nonces used to prevent replay vulnerabilities.
NonceCacheManager (Wed Sep 05 12:29:04 EDT 2012): 0 entries in the cache.
SendMail Cache (Wed Sep 05 12:29:04 EDT 2012)
########## SendMail Cache (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: Hashes of mails sent by ActiveSync devices to prevent the devices
from resending the same mails multiple times.
SendMailCacheManager (Wed Sep 05 12:29:04 EDT 2012): 1 entries in the cache.
*********** Record # 1 ***********
Key: CN=t u1/O=organizationAppl1B017URA75JSendMail-730253663
Is Expired: false
Database Configuration Information (Wed Sep 05 12:29:04 EDT
2012}
########## Database Configuration Information (Wed Sep 05 12:29:04 EDT 2012)
##########
Description: Lotus Traveler Database Configuration Information.
Database Product Name: DB2/NT64
Database Product Version: SQL09075
Database Version Major.Minor: 9.7
Chapter 10. Appendix A 489
Database Driver Major.Minor: 4.0
Database Connection URL: jdbc:db2://chevy.rtp.raleigh.ibm.com:50000/trvlrdb
Database Schema Current Version: 8.5.3.100.20120430
Database Schema Maximum Version: 8.5.3.100.20120430
Database HADR configuration: None
Banned Documents (Wed Sep 05 12:29:04 EDT 2012)
These are the banned documents either banned by the admin, or the result of a Lotus Notes
Traveler crash.
########## Banned Documents (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: List of documents that have been banned.
No banned documents for command 'null show *'.
Mail Replicas (Wed Sep 05 12:29:04 EDT 2012)
########## Mail Replicas (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: Mail replica information stored in the Traveler database for all
users.
CN=t u1/O=organization = {[CN=9.37.30.206/O=organization, mail/tu1.nsf]}
High Availability (HA) (Wed Sep 05 12:29:04 EDT 2012)
These are the high availability servers in the pool as well as the devices and user information.
A user is monitored on the same server for 24 hours after they access the server. That server
will monitor their mail database for changes. If the AI is different and the user needs to be
moved, this table will be updated with the new HA server they are monitored by.
########## High Availability (HA) (Wed Sep 05 12:29:04 EDT 2012) ##########
Description: High availability information stored in the Traveler database.
--- HA Servers (Wed Sep 05 12:29:04 EDT 2012) ---
Domino Name Hostname IP:Port Alive Reachable Last Heartbeat
AI Users Devices Build Level
9.37.30.206/organization 9.37.30.206 9.37.30.206:50125 true true 2012-09-05
12:29:04.765 95 2 2 8.5.3.100.201206132102
--- HA Devices (Wed Sep 05 12:29:04 EDT 2012) ---
Total number of devices for the HA pool : 2
--- HA Users (Wed Sep 05 12:29:04 EDT 2012) ---
Number of user bindings: 2
User Server Until Type Version
--------------- ----------------- ----------------------- ---- -------
CN=t u1/O=organization 9.37.30.206/organization 2012-09-05 11:40:12.118 0x00 5
CN=t u3/O=organization 9.37.30.206/organization 2012-09-05 11:42:12.055 0x00 5
490 IBM Notes Traveler Hints and Tips for a Successful Deployment
Number of user bindings: 2

INTERNATIONAL
TECHNICAL
SUPPORT
ORGANIZATION
BUILDING TECHNICAL
INFORMATION BASED ON
PRACTICAL EXPERIENCE
IBM Redbooks are developed
by the IBM International
Technical Support
Organization. Experts from
IBM, Customers and Partners
from around the world create
timely technical information
based on realistic scenarios.
Specific recommendations
are provided to help you
implement IT solutions more
effectively in your
environment.
For more information:
ibm.com/redbooks

Produced in
collaboration with:
Content in this document was produced in collaboration with Lotus and IBM Redbooks
IBM Redbooks: IBM Notes Traveler Hints and
Tips for a Successful Deployment
Back cover

You might also like