Professional Documents
Culture Documents
IBMRedbooks Notes Traveler Deployment PDF
IBMRedbooks Notes Traveler Deployment PDF
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.
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.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
Contents
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
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
Preface
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
10
Preface
11
12
Chapter 1.
13
14
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:
15
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
16
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:
17
18
19
20
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.
21
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.
23
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.
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
24
Feature
Requirement
Network protocols
Notes
Notes
Chapter 2. Planning
25
26
Operating system
Notes
Operating system
Notes
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
Chapter 2. Planning
27
Applicable OS
Notes
Device memory
Nokia Symbian^3
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
Device memory
Android
28
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
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.
Supported.
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
Chapter 2. Planning
29
Device/Operating
System
Notes
Lotus Notes Traveler supports all Windows Mobile 6.0, 6.1, and 6.5 devices.
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.
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
30
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.
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.
For details of how many users IBM host on Lotus Notes Traveler servers of this specification,
see 2.4, Capacity planning on page 43.
Chapter 2. Planning
31
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.
32
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.
Chapter 2. Planning
33
34
Lotus Notes Traveler direct connection with high availability via round robin DNS:
Chapter 2. Planning
35
Lotus Notes Traveler direct connection with high availability using an IP sprayer:
36
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.
37
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.
38
Lotus Notes Traveler reverse proxy connection with high availability using combined proxy
and IP sprayer:
39
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.
40
41
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.
42
43
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.
44
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
Chapter 2. Planning
45
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
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.
Chapter 2. Planning
47
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
48
Chapter 2. Planning
49
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.
50
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.
Chapter 2. Planning
51
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.
52
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.
Chapter 2. Planning
53
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.
54
55
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
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
56
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.
Chapter 2. Planning
57
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.
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.
Chapter 2. Planning
59
60
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.
Chapter 2. Planning
61
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.
Product
Notes
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.
62
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.
Chapter 2. Planning
63
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.
64
Chapter 3.
65
In this section we walk through both the the Linux and Windows installation procedures.
66
67
68
4. Licence agreement:
Review and accept the license agreement.
69
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.
70
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.
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.
71
72
73
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:
74
75
12.Review:
Review your selections. If any changes are required, select Previous to update the
selections, otherwise, select Install to continue.
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.
77
You can validate the install is working correctly by accessing the server in a browser from a
laptop, a desktop machine, or a device.
78
79
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.
80
4. Licence agreement:
Review and accept the license agreement.
81
82
83
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:
84
85
10.Review:
Review your selections. If any changes are required, select Previous to update the
selections, otherwise, select Install to continue.
86
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.
87
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.
88
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
89
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.
90
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.
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.
91
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.
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
92
93
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.
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.
In the Lotus Traveler Access section, the Administrators can select whom to allow
access to the server and what controls the users may have.
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.
94
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.
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.
95
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.
96
97
3. Destination Folder:
Accept or change the destination folder to where the Lotus Mobile Connect will be
installed.
98
99
During the installation, you are informed that the virtual adapter device driver is going to
be installed:
100
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.
101
102
103
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:
104
105
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.
106
3. Enter the Login profile name and either a Host name or IP address, then click OK.
107
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.
108
7. Choose All for the logging level so that you have complete setup logs. Click Next.
109
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.
110
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.
111
112
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.
113
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.
114
19.The Connection Manager can manage its own user accounts or use an external
authentication server. We chose the latter, 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 .
115
b. Provide a Common name, the name or address of the server, and Base distinguished
name, then click Next.
116
117
118
c. Select the Directory Server and User key field, then click Next.
119
3. Modify the HTTP Access Service to use the new Authentication Profile.
a. In Gatekeeper on the Resource tab, right-click http-service0 Properties.
120
b. On the Mode tab, change Credential challenge type to HTTP 401 basic authorization
challenge and change Authentication Profile to the one just created.
121
c. On the Lotus Mobility tab, select Enable Lotus Traveler integration and click OK.
122
123
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.
124
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.
125
127
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.
128
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.
129
130
Chapter 4.
131
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.
132
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.
133
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.
134
135
136
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
137
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.
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.
138
139
140
141
142
143
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.
144
145
146
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.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.
147
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.
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.
Enter the information for the new server that you are registering with the Domino
environment.
149
150
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.
151
152
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.
153
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).
154
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.
155
12.This completes the configuration. Reboot the operating system to ensure the Domino
server launches automatically.
156
2. Follow the Create Database Wizard. Fill in the Database name, In this example, it is called
traveler.
157
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.
158
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.
159
4. Specify a typical database transaction. Select More than 10 (long transactions) and set
the Transaction per minute (estimate) to 120.
160
161
162
163
Tip: Go to 4.3.2, Database configuration on page 156 for instruction on locating the
DB2 connection port number.
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.
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
Tip: Go to 4.3.2, Database configuration on page 156 for instruction on locating the
DB2 connection port number.
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).
165
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.
166
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.
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.
167
Tip: Go to 4.3.2, Database configuration on page 156 for instruction on locating the
DB2 connection port number.
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.
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.
168
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.
169
170
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:
171
In edit mode of the server document, the above figure appears like this:
Access server
172
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.
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.
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:
173
174
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.
175
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.
176
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.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.
177
178
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).
179
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.
180
4. Install profile:
Select Install to begin the installation page.
181
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.
182
183
184
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.
185
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.
186
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.
187
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.
188
189
190
To discard the message, click Cancel, and then click Don't Save.
191
192
193
194
Option
Description
Server
Option
Description
User name
The user name you use to connect to your Lotus Notes Traveler
server.
Password
Require SSL
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.
How do I...
Action
195
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).
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
196
197
198
5.3.1 Preparation
Here are some preparatory items for Lotus Notes Traveler installation.
199
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.
200
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.
201
202
203
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.
204
The Lotus Traveler installation starts and a progress bar appears while installation. When
the application installation is complete, tap Open.
205
7. Start configuration:
206
Confirm server address and user ID, and input the password used for connecting to your
Lotus Notes Traveler server. Click Next to continue.
Tip: This is the same user ID and password used to access the Lotus Notes Traveler
homepage.
207
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.
208
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.
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.
209
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.
Tip: There is no new Contact app installed for Lotus Traveler, it uses the native Contact
application on the device.
210
Filters
Description
Options
1 day
3 days
5 days (default)
1 week
1 month
Show all
Filters
Description
Options
Importance
Truncate mail to
Off
1K
2K
5 K (default)
10 K
50 K
100 K
Off (default)
5K
25K
100K
500K
Off (default)
25K
100K
500K
2MB
10MB
1 day
3 days
1 week (default)
2 weeks
1 month
3 months
6 months
Show all
1 day
3 days
1 week
2 weeks
1 month
3 months (default)
6 months
1 year
Show all
211
212
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.
213
214
215
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
216
217
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.
How do I...
Action
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.
218
Action
Reschedule or update a
meeting?
219
How do I...
Action
Set an alarm?
220
Tip: On tablets, the Accept and Decline menu options are also available directly from the
action bar.
The following table describes meeting invitation icons.
Icon
Description
Signifies a new invitation to which your response is requested.
An existing meeting has been rescheduled to a new time and day 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.
221
Icon
Description
Indicates that a cancelation notice has been applied to your calendar.
Description
Accept
Decline
Tentative
Creates an email response addressed to the meeting chair. Busy time is not
updated.
222
How do I...
Action
Create a contact?
1.
2.
3.
4.
5.
Edit a contact?
1.
2.
3.
4.
5.
Delete a contact?
1.
2.
3.
4.
How do I...
Action
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.
223
224
4. Start installation:
You can either launch the file right now or later.
225
The Lotus Traveler installation starts and a progress bar appears while installation.
226
227
228
229
7. Confirm server address, user ID, and input password used for connecting to your Lotus
Notes Traveler server. Click Next to continue.
230
231
232
233
234
235
9. Select the features on your device that you want to synchronize with the server.
236
10.Complete configuration.
237
238
239
240
241
242
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.
243
244
245
246
6. You can also select the Delivery options by using Menu Message Options.
247
248
2. You can also manage folders and choose which ones to subscribe.
249
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.
250
4. The installer downloads the Lotus Notes Traveler application to your device.
251
5. Start Installation: The installer is also available in the downloaded files section of the
device.
252
Click Start to download and install Lotus Notes Traveler client application.
7. Start Configuration:
Enter the server details
253
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).
254
10.Select the features on device you want to synchronize with your server.
11.Complete configuration.
255
3. Select Settings.
You have the option for configuring your Account, Mail, Calendar and Tasks, Other
Applications, Auto Sync, and Server Settings.
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.
256
257
258
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
259
260
For information on how to install Lotus Domino and Lotus Notes Traveler, see 3.0
Deploying a stand-alone Lotus Notes Traveler environment.
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.
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
Tip: If you are using transaction logging, use the option "-J" instead of "-F".
Compact
/ncompact names.nsf -c
/ncompact admin4.nsf -c
Tip: If you are using transaction logging, use the option "-c -i" instead of "-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
Tip: If you are using transaction logging, use the option "-R -X" instead of "-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.
Chapter 6. Migration
261
262
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.
Chapter 6. Migration
263
264
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.
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.
Linux
Chapter 6. Migration
265
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.
2. Welcome page:
Ensure that Lotus Domino server is stopped and click Next.
266
3. Licence agreement:
Review and accept the license agreement.
267
268
Linux
Chapter 6. Migration
269
8. Review:
Review your selections. If any changes are required, select Previous to update the
selections, otherwise, select Install to continue.
Windows
270
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.
Chapter 6. Migration
271
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.
272
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
Chapter 6. Migration
273
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.
Access http://LotusTraveler.nsf and log in as an administrator of Lotus Notes Traveler.
274
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.
275
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.
276
b. Replace application:
Tap OK.
Chapter 6. Migration
277
c. Review:
Review what can be accessed by Lotus Installer and select Install.
278
Chapter 6. Migration
279
280
Chapter 6. Migration
281
g. Finish uninstallation:
When uninstallation finishes, tap OK.
282
Chapter 6. Migration
283
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.
284
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.
Chapter 6. Migration
285
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.
286
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:
Chapter 6. Migration
287
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.
288
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.
To create the second DB2 HA pool, and add any subsequent servers to this pool:
Chapter 6. Migration
289
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
290
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
291
292
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.
293
294
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.
Chapter 7. Enterprise integration
295
The completed LDAP tab should look similar to the following example, but with the
correct settings where appropriate for your environment:
296
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).
297
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.
298
Chapter 8.
299
300
Command
Result
Active
Command
Result
Available on/off
BannedDoc show *
Removes the ban for all banned documents for the specified
user.
BannedDoc Remove *
BannedDoc dump
Bind show
Bind showall
301
Command
Result
Client refresh
Makes the specified build the default for clients of the given
type.
Config regex
Dump user
HADR show
Removes the server from the High Availability pool. You must
take the server offline before executing this action.
Help
302
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.
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
Log Collect
Log Count #
Command
Result
Log Help
Log MaxEntrySize #
Log Show
Log Size #
Memory
303
Command
Result
304
Policy Help
Sets the approval state for a user's device. flag can be either
Approve or Deny.
Security DeleteAll
Sets the flag for the device. The flag options are all,
wipeDevice, wipeApps, wipeStorageCard, and lock.
Removes the flag for the device. The flag options are the
same as those for Security flagsAdd.
Security Help
Show user
Command
Result
Shutdown
Stat Clear
Stat Help
Stat Show
Status
SystemDump Help
Threads
User user
Users
Version
305
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.
306
The following figure shows the top page of the Notes Traveler web-based administration
function.
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.
307
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
308
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.
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.
309
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.
310
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.
311
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.
312
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.
313
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.
314
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):
315
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):
316
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):
317
318
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.
319
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.
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
320
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.
Information displayed
User
Device Name
The most recent date and time the device was synchronized.
OS Type
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.
321
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.
322
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.
Information displayed
User
User State
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
323
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.
Description
Domino Name
Server Status
Availability Index
Number of Users
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
Host
Port
IP Address
324
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.
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.
325
Column
Description
Default
Assignments
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.
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.
326
Search: A search bar is located at the top right corner of the page and you can search by
user and build level.
327
328
4. Apply any settings that you want for this policy to implement in the remaining tabs.
329
330
Basics
The following figure shows the Basics section.
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,
331
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.
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).
332
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.
333
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.
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
334
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:
Server Access
The following figure shows the Server Access section of the Security tab:
335
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."
336
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.
Basics
The following figure shows the Basics section:
337
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:
338
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
339
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
340
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
Location
<DominoDataDir>/IBM_TECHNICAL_SUPPORT/javacore.traveler.*.l
og
<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
<DominoDataDir>/IBM_TECHNICAL_SUPPORT/htthr*.log
Servlet logs
<Domino data>/domino/workspace/logs/trace-log-*.xml
<Domino data>/domino/workspace/logs/error-log-*.xml
Description
Level <level>
Set the logging capture level to: FINEST, FINER, FINE, INFO,
WARNING, or SEVERE.
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>
ListPackage
Usage <on|off>
341
Variables
Description
MaxEntrySize <#>
Size <#>
Sets the maximum size (in MB) before the activity file wraps.
Count <#>
Fields <fields>
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.
342
Show
Clear
Collect
Import <file>
Imports the log settings from the fully qualified file name.
Export <file>
AddHandler <hlr>
RemoveHandler <hlr>
Handler
Variables
Description
level
formatter
filter
limit
count
pattern
append
Sets a property for the XML handler. Choices for <prop name>
include:
limit
count
pattern
append
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.
343
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.
344
345
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:
346
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.
347
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.
Examples:
"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
349
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.
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
350
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.
351
352
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
353
354
355
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.
356
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.
Usage History
CPU Pct
Java Mem
C Mem
Avl Indx
# Users
EDT
0.01
31
2594
100
EDT
0.01
32
2594
100
EDT
0.01
34
2594
100
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]
[1070:7CE0-0BB8]
[1070:7CE0-0BB8]
[1070:7CE0-0BB8]
[1070:7CE0-0BB8]
357
[1070:7CE0-0BB8]
[1070:7CE0-0BB8]
[1070:7CE0-0BB8]
[1070:7CE0-0BB8]
[1070:7CE0-0BB8]
[1070:7CE0-0BB8]
[1070:7CE0-0BB8]
[1070:7CE0-0BB8]
358
[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.
359
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.
360
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.
361
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.
363
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
364
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.
365
366
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.
367
./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):
368
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.
369
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.
370
371
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.
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.
373
374
Chapter 9.
375
376
377
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.
378
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.
379
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.
380
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
381
382
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)
383
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).
384
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.
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
385
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.
386
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.
387
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.
388
389
***
***
***
***
***
***
***
***
***
***
***
***
***
***
390
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.
391
392
10
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:
393
Avl Indx
100
100
# Users
2
2
# Errors
0
0
0.01
0.02
29
30
920
960
100
100
2
2
0
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)
395
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.
Chapter 10. Appendix A
397
NTS_CONSTRAINT_DB_CONNECTION_ENTRY = 280
number of database connections.
NTS_CONSTRAINT_DB_CONNECTION_EXIT = 224
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 = ""
398
399
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
400
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
Chapter 10. Appendix A
401
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
402
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
Chapter 10. Appendix A
403
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
404
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]
Chapter 10. Appendix A
405
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
406
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
407
Host: ftp.ecurep.ibm.com
Path: /toibm/windows
username: anonymous
password: ********
jdbc:db2://chevy.rtp.raleigh.ibm.com:50000/trvlrdb
C:\IBM\Lotus\Domino\Traveler\lib\db2jcc4.jar
db2admin
********
408
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
409
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
410
411
* 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.
<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).
-->
412
<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.
413
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>
414
<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"
415
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
Name: MajVer
Name: MinVer
Name: QMRVer
Name: QMUVer
Name: HotVer
Name: FixPVer
Name: FlagsVer
Name: ServerDirectoryName
names.nsf
Name: Form
Server
Name: Type
Server
Name: ServerName
CN=9.37.30.206/O=organization
Name: ServerTitle
text]
Name: Tasks
Routing
Name: Domain
Name: SMTPListenerEnabled
Name: SMTPFullHostDomain
9.37.30.206
Name: ServerPhoneNumber
text]
Name: LdISite
Name: FormulaTimeout
Name: Sametime
Name: MasterAddressBook
text]
Name: FltRcvryScrpt
text]
Name: LEDName
text]
Name: TrustDircat
text]
Name: FREnbld
text]
Name: FltRcvryMax
Name: NoCntDir
Name: FltRcvryHng
Name: FltRcvryCrsh
Name: FltRcvryMin
Name: FltRcvryNot
text]
416
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
3
10
10
10
10
10
10
10
11
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
1
8
5
3
0
0
0
0
Size: 8
Value:
Size: 8
Value:
Type: Names
Size: 24
Value:
Size: 2
Value: [no
Size: 14
Value: Mail
Size: 6
Size: 3
Size: 13
Value: matt
Value: 0
Value:
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Text/text list
Number/number list
Text/text list
Text/text list
3
10
3
2
0
120
0
[no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Number/number list
Text/text list
Number/number list
Number/number list
Number/number list
Names
10
3
10
10
10
2
600
1
300
3
5
[no
Name: OutsideLine
text]
Name: CallPre
text]
Name: InternationalPrefix
text]
Name: Suffix
text]
Name: country
text]
Name: LongDistancePrefix
Name: RLANIdleTimeout
text]
Name: TimeZone
Name: MailServer
CN=9.37.30.206/O=organization
Name: DST
Name: DefaultPassthruServer
text]
Name: InterNotes
text]
Name: FullAdmin
text]
Name: UnrestrictedList
text]
Name: Administrator
CN=Administrator/O=organization
Name: OnBehalfOfLst
text]
Name: DBAdmin
text]
Name: OnBehalfOfInvokerLst
text]
Name: RemoteAdmin
text]
Name: RestrictedList
text]
Name: VOAdmin
text]
Name: PrivateList
text]
Name: SysAdmin
text]
Name: LibsLst
text]
Name: ResSysAdmin
text]
Name: ResSystemCmds
text]
Name: NOIRestrictedList
text]
Name: BrowserAdminAccess
text]
Name: NOIUnrestrictedList
text]
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 3
Size: 24
Value: 5
Value:
Size: 3
Size: 2
Value: 1
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 26
Value:
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
417
Name: WhiteList
text]
Name: WhiteListLog
text]
Name: HTTP_AuthView
($Users)
Name: AnonymousAccess
Name: ServerCheckPasswords
Name: AddressBookAccess
text]
Name: PTAccess
text]
Name: DenyAccess
text]
Name: PTClients
text]
Name: CreateAccess
text]
Name: PTCallers
text]
Name: ReplicaAccess
text]
Name: PTTargets
text]
Name: TemplateAccess
text]
Name: AllowMonitors
Name: DenyMonitors
text]
Name: TrustedSrvrs
text]
Name: Port_0
Name: Enabled_0
Name: Port_1
text]
Name: Enabled_1
Name: Port_2
text]
Name: Enabled_2
Name: Port_3
text]
Name: Enabled_3
Name: Port_4
text]
Name: Enabled_4
Name: Port_5
text]
Name: Enabled_5
Name: Port_6
text]
Name: Enabled_6
Name: Port_7
text]
Name: Enabled_7
418
Size: 2
Value: [no
Size: 2
Value: [no
Size: 10
Value:
Size: 3
Size: 3
Size: 2
Value: 0
Value: 0
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Type: Names
Size: 3
Size: 2
Value: *
Value: [no
Type: Names
Size: 2
Value: [no
Size: 7
Size: 3
Size: 2
Value: TCPIP
Value: 1
Value: [no
Size: 3
Size: 2
Value: 0
Value: [no
Size: 3
Size: 2
Value: 0
Value: [no
Size: 3
Size: 2
Value: 0
Value: [no
Size: 3
Size: 2
Value: 0
Value: [no
Size: 3
Size: 2
Value: 0
Value: [no
Size: 3
Size: 2
Value: 0
Value: [no
Size: 3
Value: 0
Name: HTTP_SSLKeyFile
keyfile.kyr
Name: SSLProtocolVersion
Name: SSLSiteCerts
Name: SSLExpiredCerts
Name: SSLCipherList
04;05;0A;09;03
Name: SSLV2Enabled
text]
Name: HTTP_Port
Name: HTTP_NormalMode
Name: HTTP_EnforceAccess
Name: HTTP_TCPNP
Name: HTTP_AllowAnonymous
Name: HTTP_SSLPort
Name: HTTP_SSLMode
Name: HTTP_SSLCert
Name: HTTP_SSLNP
Name: HTTP_SSLAnonymous
Name: LDAP_Port
Name: LDAP_PortStatus
Name: LDAP_EnforceAccess
Name: LDAP_TCPNP
Name: LDAP_AllowAnonymous
Name: LDAP_SSLPort
Name: LDAP_SSLStatus
Name: LDAP_SSLCert
Name: LDAP_SSLNP
Name: LDAP_SSLAnonymous
Name: NNTP_Port
Name: NNTP_PortStatus
Name: NNTP_EnforceAccess
Name: NNTP_TCPNP
Name: NNTP_TCPAnonymous
Name: NNTP_SSLPort
Name: NNTP_SSLStatus
Name: NNTP_SSLCert
Name: NNTP_SSLNP
Name: NNTP_SSLAnonymous
Name: IMAP_Port
Name: POP3_Port
Name: SMTP_Port
Name: Router_Port
Name: IMAP_PortStatus
Name: POP3_PortStatus
Name: SMTP_PortStatus
Name: Router_PortStatus
Name: IMAP_EnforceAccess
Name: POP3_EnforceAccess
Name: SMTP_EnforceAccess
Name: SMTP_TCPNP
Name: SMTP_AllowAnonymous
Name: IMAP_SSLPort
Name: POP3_SSLPort
Name: SMTP_SSLPort
Size: 13
Value:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Value: 0
Value: 0
Value: 1
Value:
Text/text
Text/text
Text/text
Text/text
list
list
list
list
3
3
3
24
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Number/number list
Number/number list
10
3
3
3
3
10
3
3
3
3
10
3
3
3
3
10
3
3
3
3
10
3
3
3
3
10
3
3
3
3
10
10
10
10
3
3
3
3
3
3
3
3
3
10
10
10
80
1
0
1
1
443
0
0
1
1
389
1
0
1
1
636
0
0
0
1
119
1
0
1
1
563
0
0
1
0
143
110
25
25
1
1
1
1
0
0
0
0
1
993
995
465
419
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
text]
Name:
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
Name:
text]
Name:
text]
Name:
Name:
text]
Name:
text]
Name:
Name:
Name:
420
Router_SSLPort
IMAP_SSLStatus
POP3_SSLStatus
SMTP_SSLStatus
Router_SSLStatus
IMAP_SSLCert
POP3_SSLCert
IMAP_SSLNP
POP3_SSLNP
SMTP_SSLNP
SMTP_SSLAnonymous
IIOP_Port
IIOP_PortStatus
IIOP_EnforceAccess
IIOP_TCPNP
IIOP_AllowAnonymous
IIOP_SSLPort
IIOP_SSLStatus
IIOP_SSLNP
IIOP_SSLAnonymous
RDM_Port
RDM_PortStatus
RDM_EnforceAccess
RDM_SSLPort
RDM_SSLStatus
DC_IP_Address
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
DC_Port
Proxy_HTTP
Size: 6
Size: 2
Value: 2050
Value: [no
Proxy_FTP
Size: 2
Value: [no
Proxy_Gopher
Size: 2
Value: [no
Proxy_SSL
Size: 2
Value: [no
Proxy_NotesHTTP
Size: 2
Value: [no
Proxy_SOCKs
Size: 2
Value: [no
No_Proxy
Size: 2
Value: [no
AdminPMaxThreads
AdminPMailfileDelInt
Size: 10
Size: 2
Value: 3
Value: [no
AdminPInterval
Size: 2
Value: [no
AdminPWeekDays
AdminPDailyTime
Size: 3
Size: 2
Value: 1
Value: [no
AdminPDelayedTime
Size: 2
Value: [no
AdminPNameChangeExpiration
InboxTrimDays
AdminPLogSetting
Size: 10
Size: 3
Size: 3
Value: 21
Value: 7
Value: 0
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
10
3
3
3
3
3
3
3
3
3
3
10
3
3
3
3
10
3
3
3
10
3
3
10
3
2
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
465
0
0
0
0
0
0
1
1
0
1
63148
1
0
1
1
63149
0
0
1
60000
1
0
60001
0
[no
Name: InboxTrimTime
01:00:00 AM
Name: AdminPSuspendStart
text]
Name: InboxTrimLoc
Name: AdminPSuspendEnd
text]
Name: InboxTrimUsers
text]
Name: gracedays
Name: MaxRemDocs
Name: SaveUnread
text]
Name: ReloadTime
12:00:00 AM
Name: StartTime
08:00:00 AM
Name: MaxStartTime
08:00:00 PM
Name: EndTime
08:00:00 PM
Name: MaxEndTime
08:00:00 AM
Name: ConcurrentAgents
Name: MaxConcurrentAgents
Name: MaxExecution
Name: MaxMaxExecution
Name: PercentTime
Name: MaxPercentTime
Name: CatalogDomainScope
text]
Name: CatalogEnabled
Name: CatalogSchedule
12:01:00 AM-11:59:00 PM
Name: CatalogInterval
Name: CatalogIndexerScope
text]
Name: EDFilenames
text]
Name: Enabled
Name: Schedule
08:00:00 AM-10:00:00 PM
Name: Interval
Name: ICMClusterName
text]
Name: ICMNotesPort
text]
Name: ICMSSLKeyfile
keyfile.kyr
Name: ICM_BrowseDatabases
Name: ICMConfiguration
Name: ICMHostname
text]
Name: ICMRemoteServerName
text]
Type: Date-time/range
Size: 10
Value:
Size: 2
Value: [no
Size: 3
Size: 2
Value: 2
Value: [no
Type: Names
Size: 2
Value: [no
Size: 10
Size: 10
Size: 2
Value: 90
Value: 500
Value: [no
Type: Date-time/range
Size: 10
Value:
Type: Date-time/range
Size: 10
Value:
Type: Date-time/range
Size: 10
Value:
Type: Date-time/range
Size: 10
Value:
Type: Date-time/range
Size: 10
Value:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Number/number
Number/number
Number/number
Number/number
Number/number
Number/number
Names
list
list
list
list
list
list
10
10
10
10
10
10
2
1
2
10
15
50
70
[no
Size: 3
Size: 22
Value: 0
Value:
Size: 10
Size: 2
Value: 60
Value: [no
Size: 2
Value: [no
Size: 3
Size: 22
Value: 0
Value:
Size: 10
Size: 2
Value: 360
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 3
Size: 3
Size: 2
Value: 0
Value: 1
Value: [no
Size: 2
Value: [no
421
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
422
Name: HTTP_FilterLibrary
ndolextn
Name: HTTP_LogToDomLog
Name: HTTP_LogDirectory
text]
Name: HTTP_ExcludeURLs
text]
Name: HTTP_AccessLog
access
Name: HTTP_ExcludeMethods
text]
Name: HTTP_AgentLog
Name: HTTP_ExcludeMIMETypes
text]
Name: HTTP_RefererLog
referer
Name: HTTP_ExcludeUserAgents
text]
Name: HTTP_ErrorLog
Name: HTTP_ExcludeReturnCodes
text]
Name: HTTP_CGIErrorLog
cgi-error
Name: HTTP_NoLog
text]
Name: HTTP_11Connections
Name: HTTP_InputTimeout
Name: HTTP_Max11Requests
Name: HTTP_OutputTimeout
Name: HTTP_PersistentTimeout
Name: HTTP_ScriptTimeout
Name: HTTP_RequestTimeout
Name: HTTP_IdleThreadTimeout
Name: HTTP_RNInputTimeout
Name: HTTP_RNOutputTimeout
Name: HTTP_RNCGITimeout
Name: HTTP_ListenQueueSize
Name: HTTP_MaxURLBytes
Name: HTTP_MaxConcurrentNetwkSessions
Name: HTTP_MaxURLPathSegments
Name: HTTP_AllowDenyPriority
Name: HTTP_MaxHeaderLines
Name: HTTP_AllowIPList
text]
Name: HTTP_MaxHeaderBytes
Name: HTTP_DenyIPList
text]
Name: HTTP_MaxContentLength
Name: HTTP_Comp
Name: HTTP_CompEUA
text]
Name: HTTP_CompIMT
text/*;application/*
Name: HTTP_CompEMT
text]
Size: 10
Value:
Size: 3
Size: 2
Value: 0
Value: [no
Size: 2
Value: [no
Size: 8
Value:
Size: 2
Value: [no
Size: 7
Size: 2
Value: agent
Value: [no
Size: 9
Value:
Size: 2
Value: [no
Size: 7
Size: 2
Value: error
Value: [no
Size: 11
Value:
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Text/text list
Number/number list
Text/text list
3
10
10
10
10
10
10
10
10
10
10
10
10
10
10
3
10
2
1
2
100
20
180
5
60
0
75
180
180
512
4
2000
64
1
48
[no
Size: 10
Size: 2
Value: 16
Value: [no
Size: 10
Size: 3
Size: 2
Value: 10000
Value: 0
Value: [no
Size: 27
Value:
Size: 2
Value: [no
423
Name: HTTP_EnableSessionAuth
Name: HTTP_JavaServletSupport
Name: HTTP_IdleSessionTimeout
Name: HTTP_SSOCfg
text]
Name: HTTP_ServletPath
/servlet
Name: HTTP_ForceLoginOnSSL
Name: HTTP_JSClasspath
domino\servlet
Name: HTTP_MaxActiveSessions
Name: HTTP_JSFileExtensions
text]
Name: HTTP_EnableJSessions
Name: HTTP_CompanionStack
text]
Name: HTTP_IdleJSTimeout
Name: HTTP_RedirectUseHTTPS
text]
Name: HTTP_MaxActiveJSessions
Name: HTTP_RedirectServerName
text]
Name: HTTP_EnableJSPersistence
Name: HTTP_RedirectPortNo
Name: HTTP_MaxCachedDesigns
Name: HTTP_maxPostDataLength
Name: HTTP_MaxCachedUsers
Name: HTTP_compressUploadedFiles
Name: HTTP_ExpireCachedUsers
Name: HTTP_PrfCookieOption
Name: HTTP_ResourceLang
Name: HTTP_useUserLocale
Name: HTTP_AltResourceLang
Name: HTTP_ImageFormat
Name: HTTP_UTF8
Name: HTTP_ImageProgressive
Name: HTTP_NoUTF8Forms
Name: HTTP_ImageQuality
Name: HTTP_DefViewRows
Name: HTTP_CS5Default
Name: HTTP_MaxViewRows
Name: HTTP_CSWestern
Name: HTTP_DefSearchMax
Name: HTTP_CSCentralEuropean
Name: HTTP_MaxSearchMax
Name: HTTP_CSJapanese
Name: HTTP_GenBangUrls
Name: HTTP_CSTaiwanese
Name: HTTP_EnableRedirectCmd
Name: HTTP_CSChinese
Name: HTTP_CSKorean
Name: HTTP_CSCyrillic
Name: HTTP_CSGreek
Name: HTTP_CacheDir
domino\cache
424
Type:
Type:
Type:
Type:
Text/text list
Text/text list
Number/number list
Text/text list
3
3
10
2
Value:
Value:
Value:
Value:
Size: 10
Value:
Size: 3
Size: 16
Value: 0
Value:
Size: 10
Size: 2
Value: 1000
Value: [no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 10
Size: 2
Value: 30
Value: [no
Size: 10
Size: 2
Value: 1000
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Number/number list
Text/text list
Number/number list
Text/text list
Number/number list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Size:
Size:
Size:
Size:
3
10
5
7
4
3
5
3
4
3
4
3
3
3
3
10
10
3
10
4
10
4
10
4
3
4
3
6
4
6
4
14
0
0
30
[no
0
80
128
10000
64
0
120
2
en
1
en
0
1
1
0
75
30
2
1000
32
250
80
1000
18
0
26
1
3377
24
3308
83
Name: HTTP_CSTurkish
Name: HTTP_MaxCacheSize
Name: HTTP_CSThai
Name: HTTP_DeleteCache
Name: HTTP_CSBaltic
Name: HTTP_EnableGC
Name: HTTP_CSArabic
Name: HTTP_GCInterval
Name: HTTP_CSHebrew
Name: HTTP_CSVietnamese
Name: HTTP_CSIndic
Name: HTTP_AutoDetect
Name: HTTP_asynchronizeAgents
Name: HTTP_webAgentTimeout
Name: HTTP_HeaderCharset
Name: HTTP_MetaCharset
Name: HTTP_DomWSAppSpace
Name: HTTP_DomWSAddinMaxThreads
Name: HTTP_DomWSForceFromValue
Name: HTTP_EnabledServices
text]
Name: IIOP_HtmlDir
text]
Name: IIOP_IORHost
text]
Name: IIOP_ThreadPoolSize
Name: NNTP_Admin
text]
Name: NNTPLogLevel
Name: NNTPRdrDefaultAccess
Name: NNTPRdrDefaultExceptions
text]
Name: NNTPAllowRdrPosting
Name: NNTPAllowFeedPosting
Name: NNTPMaxRdrPostSize
Name: NNTPMaxFeedPostSize
Name: NNTPMaxRdrConSize
Name: NNTPMaxFeedConSize
Name: NNTPRdrConTimeout
Name: NNTPMaxFeedConnections
Name: NNTPMaxRdrConnections
Name: SMTPGlobalDomain
text]
Name: SMTPPollingPeriod
Name: SMTPAdministrator
text]
Name: SMTPWork
text]
Name: SMTPLogLevel
Name: SMTPEnableHK
Name: SMTPDailyHKAt
01:00:00 AM
Name: SMTP822HeaderOption
Name: SMTPAddrResolutionCntl
Name: SMTPEncodingScheme
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
4
10
5
3
4
3
4
10
6
6
5
3
3
10
3
3
3
10
3
2
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
84
50
144
0
87
1
86
60
3356
3310
171
0
0
0
1
0
1
20
1
[no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 10
Size: 2
Value: 10
Value: [no
Size: 3
Size: 3
Size: 2
Value: 0
Value: 1
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Text/text list
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Text/text list
3
3
10
10
10
10
10
10
10
2
1
1
1024
1024
10
100
600
5
20
[no
Size: 10
Size: 2
Value: 120
Value: [no
Size: 2
Value: [no
Size: 3
Size: 3
Size: 10
Value: 1
Value: 1
Value:
Size: 3
Size: 3
Size: 3
Value: 2
Value: 3
Value: 1
425
Name:
Name:
Name:
Name:
Name:
Name:
text]
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
426
SMTPRetryAttempts
SMTPMessageContent
SMTPRetryInterval
SMTPReturnReceipts
SMTPTransferMode
SMTPLanguageParam
Type:
Type:
Type:
Type:
Type:
Type:
Number/number list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
10
3
10
3
3
2
Value:
Value:
Value:
Value:
Value:
Value:
8
T
15
1
1
[no
SMTPCharSetDetect
SMTPTypeface
SMTPPointSize
SMTPMacAttachConvertOption
SMTPMaxInbTasks
SMTPMaxOutbTasks
SMTPMaxOutbMsgSize
DiskC
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Number/number list
Number/number list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
3
3
3
3
10
10
10
2
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
2
3
9
1
3
3
0
[no
SpndlCtC
DiskO
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtO
DiskD
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtD
DiskP
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtP
DiskE
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtE
DiskQ
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtQ
DiskF
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtF
DiskR
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtR
DiskG
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtG
DiskS
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtS
DiskH
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtH
DiskT
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtT
DiskI
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtI
DiskU
Size: 3
Size: 2
Value: 1
Value: [no
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
Name:
Name:
Name:
text]
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
SpndlCtU
DiskJ
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtJ
DiskV
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtV
DiskK
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtK
DiskW
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtW
DiskL
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtL
DiskX
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtX
DiskM
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtM
DiskY
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtY
DiskN
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtN
DiskZ
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtZ
Location
Size: 3
Size: 2
Value: 1
Value: [no
Department
Size: 2
Value: [no
Comment
Size: 2
Value: [no
ServerDescription
Size: 104
Value: [no
TRANSLOG_Status
TRANSLOG_Style
TRANSLOG_UseAll
TRANSLOG_MaxSize
Type:
Type:
Type:
Type:
Text/text
Text/text
Text/text
Text/text
Size:
Size:
Size:
Size:
3
3
3
2
Value:
Value:
Value:
Value:
0
0
0
[no
TRANSLOG_AutoFixup
TRANSLOG_Performance
QtaMthd
STVPClientPort
STPort_T120
STPort_VP
STPort_T123
STCommunityHTTPSPort
STMeetingHTTPSPort
STCommunityHTTPTunneling
STCommunityHTTPTunnelingPort
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Text/text list
Text/text list
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Text/text list
Number/number list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
3
3
3
10
10
10
10
10
10
3
10
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
1
2
2
1533
8081
1516
1503
1533
8081
1
8082
list
list
list
list
427
Name: STMeetingHTTPTunnelingPort
Name: STMaxCommunityConnections
Name: ST_HostName
text]
Name: STDirChunkSize
Name: ST_BindToHostName
Name: STDirRefreshInterval
Name: STActiveMeetingsLimitEnabled
text]
Name: STActiveMeetingsLimit
Name: STConfigRefreshInterval
Name: STTotalUsersLimitEnabled
text]
Name: STTotalUsersLimit
Name: STMeetingUsersLimitEnabled
text]
Name: STMeetingUsersLimit
Name: STAutoExtendMeetingEnabled
Name: STMeetingExtendTime
Name: STLogTime
Name: STCommunityLogin
Name: STCommunityLoginFailed
text]
Name: STCommunityTotalConnections
text]
Name: STLogHistory
Name: STCommunityLogUsageFrequency
Name: STLogToFiles
Name: STMeetingLogEvents
Name: STMeetingLogParticipants
Name: STLogToNSF
Name: STLogFileName
sametime.log
Name: SHARED_MAIL
Name: SCOS_DIR_1
text]
Name: SCOS_DIR_MAX_SIZE_MB_1
text]
Name: SCOS_ACTIVE_1
text]
Name: SCOS_DIR_2
text]
Name: SCOS_DIR_MAX_SIZE_MB_2
text]
Name: SCOS_ACTIVE_2
text]
Name: SCOS_DIR_3
text]
Name: SCOS_DIR_MAX_SIZE_MB_3
text]
Name: SCOS_ACTIVE_3
text]
Name: SCOS_DIR_4
text]
428
Size: 10
Size: 10
Size: 2
Value: 8081
Value: 8000
Value: [no
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Number/number list
Text/text list
Number/number list
Text/text list
10
3
10
2
100
0
60
[no
Size: 10
Size: 10
Size: 2
Value: 100
Value: 60
Value: [no
Size: 10
Size: 2
Value: 500
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Number/number list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
10
3
10
3
3
2
50
1
15
0
1
[no
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Number/number list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
10
10
3
3
3
3
14
30
10
0
1
1
1
Size: 3
Size: 2
Value: 0
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
Name:
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
Name:
text]
SCOS_DIR_MAX_SIZE_MB_4
Size: 2
Value: [no
SCOS_ACTIVE_4
Size: 2
Value: [no
SCOS_DIR_5
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_5
Size: 2
Value: [no
SCOS_ACTIVE_5
Size: 2
Value: [no
SCOS_DIR_6
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_6
Size: 2
Value: [no
SCOS_ACTIVE_6
Size: 2
Value: [no
SCOS_DIR_7
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_7
Size: 2
Value: [no
SCOS_ACTIVE_7
Size: 2
Value: [no
SCOS_DIR_8
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_8
Size: 2
Value: [no
SCOS_ACTIVE_8
Size: 2
Value: [no
SCOS_DIR_9
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_9
Size: 2
Value: [no
SCOS_ACTIVE_9
Size: 2
Value: [no
SCOS_DIR_10
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_10
Size: 2
Value: [no
SCOS_ACTIVE_10
Size: 2
Value: [no
DAOSEnable
DAOSObjDelete
DB2Host
Size: 3
Size: 10
Size: 2
Value: 0
Value: 30
Value: [no
DB2Port
Size: 2
Value: [no
DB2Inst
Size: 2
Value: [no
DB2Db
Size: 2
Value: [no
DB2Dir
Size: 2
Value: [no
DB2Def
DB2UDFSrv
Size: 3
Size: 2
Value: 1
Value: [no
429
Name: DB2UDFPath
text]
Name: DB2GroupMax
Name: DB2DefUser
text]
Name: DB2QVRows
Name: tsMaxMem
Name: tsIPCPort
Name: tsIPCPort2
Name: tsExternalURL
http://9.37.30.206/traveler
Name: tsAddressBookAccess
text]
Name: tsDenyAccess
text]
Name: tsUserCMD
Name: tsUserWipe
Name: tsLogLevel
Name: tsTrcLevel
Name: tsTrcCmp
Name: tsTrcSize
Name: tsTrcFiles
Name: tsTrcPriv
2;4;8;16
Name: tsPollTime
Name: devPTCPP
Name: tsPHBeatAlg
Name: tsPHBFixed
Name: tsPHBInitial
Name: tsPHBAmim
Name: tsPHBAmaxsec
Name: tsPHBAretry
Name: tsPofflinehr
Name: tsPcleanup
Name: Owner
text]
Name: LocalAdmin
text]
Name: PKMinWidth
Name: PKMaxWidth
Name: PKDefWidth
Name: PKMaxAge
Name: PKMinDate
08/01/1977
Name: PKDueDate
09/04/2112
Name: PKOldKeyDays
Name: ChangeRequest
text]
Name: DocumentAccess
[ServerModifier]
Name: BookmarkDB
bookmark.nsf
Name: ServerPlatform
Windows/2003 5.2 Intel Pentium
430
Size: 2
Value: [no
Size: 10
Size: 2
Value: 10
Value: [no
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Number/number list
Number/number list
Number/number list
Number/number list
Text/text list
10
10
10
10
29
500
512
50125
50126
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Number/number list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
3
3
3
3
3
10
10
17
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
0
1
3
0
*
50
10
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Number/number list
Number/number list
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Authors
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
10
10
3
10
10
10
10
10
10
10
2
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
3
8642
2
55
30
30
15
30
24
30
[no
Type: Authors
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
3
6
6
10
10
Value:
Value:
Value:
Value:
Value:
Type: Date-time/range
Size: 10
Value:
Size: 10
Size: 2
Value: 365
Value: [no
Type: Authors
Size: 18
Value:
Size: 14
Value:
Size: 32
Value:
Text/text list
Text/text list
Text/text list
Number/number list
Date-time/range
0
1024
1024
36500
Name: ASPServer
Name: DAOSWarned
Name: $ServerMain
Name: $Server_Ports_Tabs
Name: $Server_Ports_Internet2_Tabs
Name: $Server_Tasks_Tabs
Name: $Server_InetProt_Tabs
Name: $Server_MTA_Tabs
Name: FltRcvryMD
Name: ServerBuildNumber
Release 8.5.3
Name: ClusterName
text]
Name: ServerCPUCount
Name: NSDEnbld
Name: CfgNABonly
Name: AllowAccess
text]
Name: Protocol_0
Name: NetName_0
Network
Name: NetAddr_0
9.37.30.206
Name: Protocol_1
text]
Name: NetName_1
text]
Name: NetAddr_1
9.37.30.206
Name: Protocol_2
text]
Name: NetName_2
text]
Name: NetAddr_2
9.37.30.206
Name: Protocol_3
text]
Name: NetName_3
text]
Name: NetAddr_3
9.37.30.206
Name: Protocol_4
text]
Name: NetName_4
text]
Name: NetAddr_4
9.37.30.206
Name: Protocol_5
text]
Name: NetName_5
text]
Name: NetAddr_5
9.37.30.206
Name: Protocol_6
text]
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Text/text list
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Text/text list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
3
3
10
10
10
10
10
10
6
15
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
0
0
0
0
0
0
0
0
8530
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Number/number list
Text/text list
Text/text list
Names
10
3
3
2
2
1
0
[no
Size: 5
Size: 15
Value: TCP
Value: TCPIP
Size: 13
Value:
Size: 2
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 2
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 2
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 2
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 2
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 2
Value: [no
431
Name: NetName_6
text]
Name: NetAddr_6
9.37.30.206
Name: Protocol_7
text]
Name: NetName_7
text]
Name: NetAddr_7
9.37.30.206
Name: EnabledList
1;0;0;0;0;0;0;0
Name: Ports
Name: Network
Network
Name: NetAddresses
9.37.30.206
Name: Protocols
Name: SSLStrongEncryption
03040506090A
Name: IMAP_TCPNP
Name: POP3_TCPNP
Name: AdminPSuspendRange
text]
Name: CatalogType
Name: CatalogWeekDays
1;2;3;4;5;6;7
Name: WeekDays
1;2;3;4;5;6;7
Name: HTTP_CompMinS
Name: HTTP_CompMaxS
Name: HTTP_CompMM
Name: HTTP_CSDefault
Name: HTTP_Version
Name: IIOP_IdleMinsAllowed
Name: TRANSLOG_Path
text]
Name: SCOS_DIR_ACTIVE_FILES_1
text]
Name: SCOS_ONLINE_1
text]
Name: SCOS_DIR_ACTIVE_FILES_2
text]
Name: SCOS_ONLINE_2
text]
Name: SCOS_DIR_ACTIVE_FILES_3
text]
Name: SCOS_ONLINE_3
text]
Name: SCOS_DIR_ACTIVE_FILES_4
text]
Name: SCOS_ONLINE_4
text]
Name: SCOS_DIR_ACTIVE_FILES_5
text]
432
Size: 2
Value: [no
Size: 13
Value:
Size: 2
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 28
Value:
Size: 7
Size: 15
Value: TCPIP
Value: TCPIP
Size: 13
Value:
Size: 5
Size: 14
Value: TCP
Value:
Size: 3
Size: 3
Size: 2
Value: 1
Value: 1
Value: [no
Size: 3
Size: 25
Value: 0
Value:
Size: 25
Value:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Number/number list
Number/number list
Number/number list
Text/text list
Number/number list
Number/number list
Text/text list
10
10
10
4
10
10
2
1
128
20
98
1
60
[no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Name: SCOS_ONLINE_5
text]
Name: SCOS_DIR_ACTIVE_FILES_6
text]
Name: SCOS_ONLINE_6
text]
Name: SCOS_DIR_ACTIVE_FILES_7
text]
Name: SCOS_ONLINE_7
text]
Name: SCOS_DIR_ACTIVE_FILES_8
text]
Name: SCOS_ONLINE_8
text]
Name: SCOS_DIR_ACTIVE_FILES_9
text]
Name: SCOS_ONLINE_9
text]
Name: SCOS_DIR_ACTIVE_FILES_10
text]
Name: SCOS_ONLINE_10
text]
Name: DAOSMinObjSize
Name: DAOSBasePath
Name: DB2AcWrn
Name: tsAllowAccess
text]
Name: tsPHBAmax
Name: tsPoffline
Name: Certificate
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
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Text/text list
Text/text list
Number/number list
Names
7
6
10
2
Size: 10
Size: 10
Size: 910
64000
DAOS
15
[no
Value: 900
Value: 1440
Value:
433
1D103A2E
Name: AreaCode
Type: Text/text list
text]
Name: $LocationVersion
Type: Text/text list
Name: DB2AccessServer
Type: Text/text list
Name: IsVirDir
Type: Number/number list
Name: $UpdatedBy
Type: Names
CN=9.37.30.206/O=organization;CN=Administrator/O=organization
Name: $Revisions
Type: Date-time/range
09/04/2012 04:35:26 PM;09/05/2012 11:20:28 AM
Size: 2
Value: [no
Size:
Size:
Size:
Size:
Value: 2
Value: 0
Value: 0
Value:
3
3
10
54
Size: 22
Value:
434
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
3
10
10
10
10
10
10
10
11
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
1
8
5
3
0
0
0
0
Size: 8
Value:
Size: 8
Value:
Type: Names
Size: 24
Value:
Size: 2
Value: [no
Size: 14
Value: Mail
Size: 6
Size: 3
Size: 13
Value: matt
Value: 0
Value:
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Text/text list
Number/number list
Text/text list
Text/text list
3
10
3
2
0
120
0
[no
Name: FltRcvryScrpt
text]
Name: LEDName
text]
Name: TrustDircat
text]
Name: FREnbld
text]
Name: FltRcvryMax
Name: NoCntDir
Name: FltRcvryHng
Name: FltRcvryCrsh
Name: FltRcvryMin
Name: FltRcvryNot
text]
Name: OutsideLine
text]
Name: CallPre
text]
Name: InternationalPrefix
text]
Name: Suffix
text]
Name: country
text]
Name: LongDistancePrefix
Name: RLANIdleTimeout
text]
Name: TimeZone
Name: MailServer
CN=9.37.30.206/O=organization
Name: DST
Name: DefaultPassthruServer
text]
Name: InterNotes
text]
Name: FullAdmin
text]
Name: UnrestrictedList
text]
Name: Administrator
CN=Administrator/O=organization
Name: OnBehalfOfLst
text]
Name: DBAdmin
text]
Name: OnBehalfOfInvokerLst
text]
Name: RemoteAdmin
text]
Name: RestrictedList
text]
Name: VOAdmin
text]
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Number/number list
Text/text list
Number/number list
Number/number list
Number/number list
Names
10
3
10
10
10
2
600
1
300
3
5
[no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 3
Size: 24
Value: 5
Value:
Size: 3
Size: 2
Value: 1
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 26
Value:
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
435
Name: PrivateList
text]
Name: SysAdmin
text]
Name: LibsLst
text]
Name: ResSysAdmin
text]
Name: ResSystemCmds
text]
Name: NOIRestrictedList
text]
Name: BrowserAdminAccess
text]
Name: NOIUnrestrictedList
text]
Name: WhiteList
text]
Name: WhiteListLog
text]
Name: HTTP_AuthView
($Users)
Name: AnonymousAccess
Name: ServerCheckPasswords
Name: AddressBookAccess
text]
Name: PTAccess
text]
Name: DenyAccess
text]
Name: PTClients
text]
Name: CreateAccess
text]
Name: PTCallers
text]
Name: ReplicaAccess
text]
Name: PTTargets
text]
Name: TemplateAccess
text]
Name: AllowMonitors
Name: DenyMonitors
text]
Name: TrustedSrvrs
text]
Name: Port_0
Name: Enabled_0
Name: Port_1
text]
Name: Enabled_1
Name: Port_2
text]
Name: Enabled_2
436
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 10
Value:
Size: 3
Size: 3
Size: 2
Value: 0
Value: 0
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type: Names
Type: Names
Size: 3
Size: 2
Value: *
Value: [no
Type: Names
Size: 2
Value: [no
Size: 7
Size: 3
Size: 2
Value: TCPIP
Value: 1
Value: [no
Size: 3
Size: 2
Value: 0
Value: [no
Size: 3
Value: 0
Name: Port_3
text]
Name: Enabled_3
Name: Port_4
text]
Name: Enabled_4
Name: Port_5
text]
Name: Enabled_5
Name: Port_6
text]
Name: Enabled_6
Name: Port_7
text]
Name: Enabled_7
Name: HTTP_SSLKeyFile
keyfile.kyr
Name: SSLProtocolVersion
Name: SSLSiteCerts
Name: SSLExpiredCerts
Name: SSLCipherList
04;05;0A;09;03
Name: SSLV2Enabled
text]
Name: HTTP_Port
Name: HTTP_NormalMode
Name: HTTP_EnforceAccess
Name: HTTP_TCPNP
Name: HTTP_AllowAnonymous
Name: HTTP_SSLPort
Name: HTTP_SSLMode
Name: HTTP_SSLCert
Name: HTTP_SSLNP
Name: HTTP_SSLAnonymous
Name: LDAP_Port
Name: LDAP_PortStatus
Name: LDAP_EnforceAccess
Name: LDAP_TCPNP
Name: LDAP_AllowAnonymous
Name: LDAP_SSLPort
Name: LDAP_SSLStatus
Name: LDAP_SSLCert
Name: LDAP_SSLNP
Name: LDAP_SSLAnonymous
Name: NNTP_Port
Name: NNTP_PortStatus
Name: NNTP_EnforceAccess
Name: NNTP_TCPNP
Name: NNTP_TCPAnonymous
Name: NNTP_SSLPort
Name: NNTP_SSLStatus
Name: NNTP_SSLCert
Name: NNTP_SSLNP
Name: NNTP_SSLAnonymous
Name: IMAP_Port
Size: 2
Value: [no
Size: 3
Size: 2
Value: 0
Value: [no
Size: 3
Size: 2
Value: 0
Value: [no
Size: 3
Size: 2
Value: 0
Value: [no
Size: 3
Size: 2
Value: 0
Value: [no
Size: 3
Size: 13
Value: 0
Value:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Value: 0
Value: 0
Value: 1
Value:
Text/text
Text/text
Text/text
Text/text
list
list
list
list
3
3
3
24
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
10
3
3
3
3
10
3
3
3
3
10
3
3
3
3
10
3
3
3
3
10
3
3
3
3
10
3
3
3
3
10
80
1
0
1
1
443
0
0
1
1
389
1
0
1
1
636
0
0
0
1
119
1
0
1
1
563
0
0
1
0
143
437
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
Name:
text]
Name:
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
438
POP3_Port
SMTP_Port
Router_Port
IMAP_PortStatus
POP3_PortStatus
SMTP_PortStatus
Router_PortStatus
IMAP_EnforceAccess
POP3_EnforceAccess
SMTP_EnforceAccess
SMTP_TCPNP
SMTP_AllowAnonymous
IMAP_SSLPort
POP3_SSLPort
SMTP_SSLPort
Router_SSLPort
IMAP_SSLStatus
POP3_SSLStatus
SMTP_SSLStatus
Router_SSLStatus
IMAP_SSLCert
POP3_SSLCert
IMAP_SSLNP
POP3_SSLNP
SMTP_SSLNP
SMTP_SSLAnonymous
IIOP_Port
IIOP_PortStatus
IIOP_EnforceAccess
IIOP_TCPNP
IIOP_AllowAnonymous
IIOP_SSLPort
IIOP_SSLStatus
IIOP_SSLNP
IIOP_SSLAnonymous
RDM_Port
RDM_PortStatus
RDM_EnforceAccess
RDM_SSLPort
RDM_SSLStatus
DC_IP_Address
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Number/number list
Number/number list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
DC_Port
Proxy_HTTP
Size: 6
Size: 2
Value: 2050
Value: [no
Proxy_FTP
Size: 2
Value: [no
Proxy_Gopher
Size: 2
Value: [no
Proxy_SSL
Size: 2
Value: [no
Proxy_NotesHTTP
Size: 2
Value: [no
Proxy_SOCKs
Size: 2
Value: [no
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
10
10
10
3
3
3
3
3
3
3
3
3
10
10
10
10
3
3
3
3
3
3
3
3
3
3
10
3
3
3
3
10
3
3
3
10
3
3
10
3
2
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
110
25
25
1
1
1
1
0
0
0
0
1
993
995
465
465
0
0
0
0
0
0
1
1
0
1
63148
1
0
1
1
63149
0
0
1
60000
1
0
60001
0
[no
Name: No_Proxy
text]
Name: AdminPMaxThreads
Name: AdminPMailfileDelInt
text]
Name: AdminPInterval
text]
Name: AdminPWeekDays
Name: AdminPDailyTime
text]
Name: AdminPDelayedTime
text]
Name: AdminPNameChangeExpiration
Name: InboxTrimDays
Name: AdminPLogSetting
Name: InboxTrimTime
01:00:00 AM
Name: AdminPSuspendStart
text]
Name: InboxTrimLoc
Name: AdminPSuspendEnd
text]
Name: InboxTrimUsers
text]
Name: gracedays
Name: MaxRemDocs
Name: SaveUnread
text]
Name: ReloadTime
12:00:00 AM
Name: StartTime
08:00:00 AM
Name: MaxStartTime
08:00:00 PM
Name: EndTime
08:00:00 PM
Name: MaxEndTime
08:00:00 AM
Name: ConcurrentAgents
Name: MaxConcurrentAgents
Name: MaxExecution
Name: MaxMaxExecution
Name: PercentTime
Name: MaxPercentTime
Name: CatalogDomainScope
text]
Name: CatalogEnabled
Name: CatalogSchedule
12:01:00 AM-11:59:00 PM
Name: CatalogInterval
Name: CatalogIndexerScope
text]
Name: EDFilenames
text]
Name: Enabled
Size: 2
Value: [no
Size: 10
Size: 2
Value: 3
Value: [no
Size: 2
Value: [no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Value: 21
Value: 7
Value: 0
Value:
Number/number list
Text/text list
Text/text list
Date-time/range
10
3
3
10
Size: 2
Value: [no
Size: 3
Size: 2
Value: 2
Value: [no
Type: Names
Size: 2
Value: [no
Size: 10
Size: 10
Size: 2
Value: 90
Value: 500
Value: [no
Type: Date-time/range
Size: 10
Value:
Type: Date-time/range
Size: 10
Value:
Type: Date-time/range
Size: 10
Value:
Type: Date-time/range
Size: 10
Value:
Type: Date-time/range
Size: 10
Value:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Number/number
Number/number
Number/number
Number/number
Number/number
Number/number
Names
list
list
list
list
list
list
10
10
10
10
10
10
2
1
2
10
15
50
70
[no
Size: 3
Size: 22
Value: 0
Value:
Size: 10
Size: 2
Value: 60
Value: [no
Size: 2
Value: [no
Size: 3
Value: 0
439
Name: Schedule
08:00:00 AM-10:00:00 PM
Name: Interval
Name: ICMClusterName
text]
Name: ICMNotesPort
text]
Name: ICMSSLKeyfile
keyfile.kyr
Name: ICM_BrowseDatabases
Name: ICMConfiguration
Name: ICMHostname
text]
Name: ICMRemoteServerName
text]
Name: ICMHTTP_Port
Name: ICMHTTP_PortStatus
Name: ICMHTTP_SSLPort
Name: ICMHTTP_SSLStatus
Name: WebDbName
web.nsf
Name: WebAllow
Name: WebServices
HTTP;FTP;GOPHER
Name: WebDeny
text]
Name: WebRetrievers
Name: WebLogLevel
Name: WebUpdateCache
Name: SMTP_Domain
text]
Name: RDMgrEnbld
Name: RDOff
Name: RDWait
Name: HTTP_HostName
text]
Name: HTTP_HomeURL
/traveler
Name: HTTP_BindToHostName
Name: HTTP_HTMLDir
domino\html
Name: HTTP_DNSLookup
Name: HTTP_IconsDir
domino\icons
Name: HTTP_DNSLookupCache
Name: HTTP_IconsPath
/icons
Name: HTTP_DNSCacheSize
Name: HTTP_CGIDir
domino\cgi-bin
Name: HTTP_DNSCacheFoundTimeout
Name: HTTP_CGIPath
/cgi-bin
Name: HTTP_DNSCacheNotFoundTimeout
Name: HTTP_MaxActiveThreads
440
Type: Date-time/range
Size: 22
Value:
Size: 10
Size: 2
Value: 360
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 3
Size: 3
Size: 2
Value: 0
Value: 1
Value: [no
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Number/number list
Text/text list
Number/number list
Text/text list
Text/text list
10
3
10
3
9
80
1
443
0
Size: 3
Size: 23
Value: *
Value:
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Number/number list
Text/text list
Text/text list
Text/text list
Size:
Size:
Size:
Size:
10
3
3
2
Value:
Value:
Value:
Value:
50
0
1
[no
Type:
Type:
Type:
Type:
Text/text list
Number/number list
Number/number list
Text/text list
Size:
Size:
Size:
Size:
3
10
10
2
Value:
Value:
Value:
Value:
0
24
0
[no
Size: 11
Value:
Size: 3
Size: 13
Value: 0
Value:
Size: 3
Size: 14
Value: 0
Value:
Size: 3
Size: 8
Value: 1
Value:
Size: 10
Size: 16
Value: 256
Value:
Size: 10
Size: 10
Value: 120
Value:
Size: 10
Size: 10
Value: 240
Value: 100
Name: HTTP_DatabaseBrowsing
Name: HTTP_AccessLogFormat
Name: HTTP_MaxRequests
Name: HTTP_LogTime
Name: HTTP_MinActiveThreads
Name: HTTP_LogFileDuration
Name: HTTP_Welcome
default.htm
Name: HTTP_MaxLogEntrySize
Name: HTTP_MaxCachedCommands
Name: HTTP_MaxLogFileSize
Name: HTTP_Audience
Name: HTTP_LogToFiles
Name: HTTP_FilterLibrary
ndolextn
Name: HTTP_LogToDomLog
Name: HTTP_LogDirectory
text]
Name: HTTP_ExcludeURLs
text]
Name: HTTP_AccessLog
access
Name: HTTP_ExcludeMethods
text]
Name: HTTP_AgentLog
Name: HTTP_ExcludeMIMETypes
text]
Name: HTTP_RefererLog
referer
Name: HTTP_ExcludeUserAgents
text]
Name: HTTP_ErrorLog
Name: HTTP_ExcludeReturnCodes
text]
Name: HTTP_CGIErrorLog
cgi-error
Name: HTTP_NoLog
text]
Name: HTTP_11Connections
Name: HTTP_InputTimeout
Name: HTTP_Max11Requests
Name: HTTP_OutputTimeout
Name: HTTP_PersistentTimeout
Name: HTTP_ScriptTimeout
Name: HTTP_RequestTimeout
Name: HTTP_IdleThreadTimeout
Name: HTTP_RNInputTimeout
Name: HTTP_RNOutputTimeout
Name: HTTP_RNCGITimeout
Name: HTTP_ListenQueueSize
Name: HTTP_MaxURLBytes
Name: HTTP_MaxConcurrentNetwkSessions
Name: HTTP_MaxURLPathSegments
Name: HTTP_AllowDenyPriority
Name: HTTP_MaxHeaderLines
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Text/text list
Text/text list
Number/number list
Text/text list
Number/number list
Text/text list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
3
3
10
3
10
3
13
Value:
Value:
Value:
Value:
Value:
Value:
Value:
0
0
1
0
20
0
Type:
Type:
Type:
Type:
Type:
Type:
Number/number list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
10
5
10
3
3
10
Value:
Value:
Value:
Value:
Value:
Value:
10
128
0
0
0
Size: 3
Size: 2
Value: 0
Value: [no
Size: 2
Value: [no
Size: 8
Value:
Size: 2
Value: [no
Size: 7
Size: 2
Value: agent
Value: [no
Size: 9
Value:
Size: 2
Value: [no
Size: 7
Size: 2
Value: error
Value: [no
Size: 11
Value:
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Text/text list
Number/number list
3
10
10
10
10
10
10
10
10
10
10
10
10
10
10
3
10
1
2
100
20
180
5
60
0
75
180
180
512
4
2000
64
1
48
441
Name: HTTP_AllowIPList
text]
Name: HTTP_MaxHeaderBytes
Name: HTTP_DenyIPList
text]
Name: HTTP_MaxContentLength
Name: HTTP_Comp
Name: HTTP_CompEUA
text]
Name: HTTP_CompIMT
text/*;application/*
Name: HTTP_CompEMT
text]
Name: HTTP_EnableSessionAuth
Name: HTTP_JavaServletSupport
Name: HTTP_IdleSessionTimeout
Name: HTTP_SSOCfg
text]
Name: HTTP_ServletPath
/servlet
Name: HTTP_ForceLoginOnSSL
Name: HTTP_JSClasspath
domino\servlet
Name: HTTP_MaxActiveSessions
Name: HTTP_JSFileExtensions
text]
Name: HTTP_EnableJSessions
Name: HTTP_CompanionStack
text]
Name: HTTP_IdleJSTimeout
Name: HTTP_RedirectUseHTTPS
text]
Name: HTTP_MaxActiveJSessions
Name: HTTP_RedirectServerName
text]
Name: HTTP_EnableJSPersistence
Name: HTTP_RedirectPortNo
Name: HTTP_MaxCachedDesigns
Name: HTTP_maxPostDataLength
Name: HTTP_MaxCachedUsers
Name: HTTP_compressUploadedFiles
Name: HTTP_ExpireCachedUsers
Name: HTTP_PrfCookieOption
Name: HTTP_ResourceLang
Name: HTTP_useUserLocale
Name: HTTP_AltResourceLang
Name: HTTP_ImageFormat
Name: HTTP_UTF8
Name: HTTP_ImageProgressive
Name: HTTP_NoUTF8Forms
Name: HTTP_ImageQuality
Name: HTTP_DefViewRows
Name: HTTP_CS5Default
Name: HTTP_MaxViewRows
Name: HTTP_CSWestern
442
Size: 2
Value: [no
Size: 10
Size: 2
Value: 16
Value: [no
Size: 10
Size: 3
Size: 2
Value: 10000
Value: 0
Value: [no
Size: 27
Value:
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
3
3
10
2
Value:
Value:
Value:
Value:
Size: 10
Value:
Size: 3
Size: 16
Value: 0
Value:
Size: 10
Size: 2
Value: 1000
Value: [no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 10
Size: 2
Value: 30
Value: [no
Size: 10
Size: 2
Value: 1000
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Number/number list
Text/text list
Number/number list
Text/text list
3
10
5
7
4
3
5
3
4
3
4
3
3
3
3
10
10
3
10
4
0
0
30
[no
0
80
128
10000
64
0
120
2
en
1
en
0
1
1
0
75
30
2
1000
32
Name: HTTP_DefSearchMax
Name: HTTP_CSCentralEuropean
Name: HTTP_MaxSearchMax
Name: HTTP_CSJapanese
Name: HTTP_GenBangUrls
Name: HTTP_CSTaiwanese
Name: HTTP_EnableRedirectCmd
Name: HTTP_CSChinese
Name: HTTP_CSKorean
Name: HTTP_CSCyrillic
Name: HTTP_CSGreek
Name: HTTP_CacheDir
domino\cache
Name: HTTP_CSTurkish
Name: HTTP_MaxCacheSize
Name: HTTP_CSThai
Name: HTTP_DeleteCache
Name: HTTP_CSBaltic
Name: HTTP_EnableGC
Name: HTTP_CSArabic
Name: HTTP_GCInterval
Name: HTTP_CSHebrew
Name: HTTP_CSVietnamese
Name: HTTP_CSIndic
Name: HTTP_AutoDetect
Name: HTTP_asynchronizeAgents
Name: HTTP_webAgentTimeout
Name: HTTP_HeaderCharset
Name: HTTP_MetaCharset
Name: HTTP_DomWSAppSpace
Name: HTTP_DomWSAddinMaxThreads
Name: HTTP_DomWSForceFromValue
Name: HTTP_EnabledServices
text]
Name: IIOP_HtmlDir
text]
Name: IIOP_IORHost
text]
Name: IIOP_ThreadPoolSize
Name: NNTP_Admin
text]
Name: NNTPLogLevel
Name: NNTPRdrDefaultAccess
Name: NNTPRdrDefaultExceptions
text]
Name: NNTPAllowRdrPosting
Name: NNTPAllowFeedPosting
Name: NNTPMaxRdrPostSize
Name: NNTPMaxFeedPostSize
Name: NNTPMaxRdrConSize
Name: NNTPMaxFeedConSize
Name: NNTPRdrConTimeout
Name: NNTPMaxFeedConnections
Name: NNTPMaxRdrConnections
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Number/number list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
10
4
10
4
3
4
3
6
4
6
4
14
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
250
80
1000
18
0
26
1
3377
24
3308
83
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
4
10
5
3
4
3
4
10
6
6
5
3
3
10
3
3
3
10
3
2
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
84
50
144
0
87
1
86
60
3356
3310
171
0
0
0
1
0
1
20
1
[no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 10
Size: 2
Value: 10
Value: [no
Size: 3
Size: 3
Size: 2
Value: 0
Value: 1
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Text/text list
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
3
3
10
10
10
10
10
10
10
1
1
1024
1024
10
100
600
5
20
443
Name: SMTPGlobalDomain
text]
Name: SMTPPollingPeriod
Name: SMTPAdministrator
text]
Name: SMTPWork
text]
Name: SMTPLogLevel
Name: SMTPEnableHK
Name: SMTPDailyHKAt
01:00:00 AM
Name: SMTP822HeaderOption
Name: SMTPAddrResolutionCntl
Name: SMTPEncodingScheme
Name: SMTPRetryAttempts
Name: SMTPMessageContent
Name: SMTPRetryInterval
Name: SMTPReturnReceipts
Name: SMTPTransferMode
Name: SMTPLanguageParam
text]
Name: SMTPCharSetDetect
Name: SMTPTypeface
Name: SMTPPointSize
Name: SMTPMacAttachConvertOption
Name: SMTPMaxInbTasks
Name: SMTPMaxOutbTasks
Name: SMTPMaxOutbMsgSize
Name: DiskC
text]
Name: SpndlCtC
Name: DiskO
text]
Name: SpndlCtO
Name: DiskD
text]
Name: SpndlCtD
Name: DiskP
text]
Name: SpndlCtP
Name: DiskE
text]
Name: SpndlCtE
Name: DiskQ
text]
Name: SpndlCtQ
Name: DiskF
text]
Name: SpndlCtF
Name: DiskR
text]
Name: SpndlCtR
Name: DiskG
text]
Name: SpndlCtG
444
Size: 2
Value: [no
Size: 10
Size: 2
Value: 120
Value: [no
Size: 2
Value: [no
Size: 3
Size: 3
Size: 10
Value: 1
Value: 1
Value:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Text/text list
Text/text list
Text/text list
Number/number list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
3
3
3
10
3
10
3
3
2
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
2
3
1
8
T
15
1
1
[no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Number/number list
Number/number list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
3
3
3
3
10
10
10
2
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
2
3
9
1
3
3
0
[no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 3
Value: 1
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
Name:
DiskS
Size: 2
Value: [no
SpndlCtS
DiskH
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtH
DiskT
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtT
DiskI
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtI
DiskU
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtU
DiskJ
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtJ
DiskV
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtV
DiskK
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtK
DiskW
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtW
DiskL
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtL
DiskX
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtX
DiskM
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtM
DiskY
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtY
DiskN
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtN
DiskZ
Size: 3
Size: 2
Value: 1
Value: [no
SpndlCtZ
Location
Size: 3
Size: 2
Value: 1
Value: [no
Department
Size: 2
Value: [no
Comment
Size: 2
Value: [no
ServerDescription
Size: 104
Value: [no
TRANSLOG_Status
TRANSLOG_Style
Size: 3
Size: 3
Value: 0
Value: 0
445
Name: TRANSLOG_UseAll
Name: TRANSLOG_MaxSize
text]
Name: TRANSLOG_AutoFixup
Name: TRANSLOG_Performance
Name: QtaMthd
Name: STVPClientPort
Name: STPort_T120
Name: STPort_VP
Name: STPort_T123
Name: STCommunityHTTPSPort
Name: STMeetingHTTPSPort
Name: STCommunityHTTPTunneling
Name: STCommunityHTTPTunnelingPort
Name: STMeetingHTTPTunnelingPort
Name: STMaxCommunityConnections
Name: ST_HostName
text]
Name: STDirChunkSize
Name: ST_BindToHostName
Name: STDirRefreshInterval
Name: STActiveMeetingsLimitEnabled
text]
Name: STActiveMeetingsLimit
Name: STConfigRefreshInterval
Name: STTotalUsersLimitEnabled
text]
Name: STTotalUsersLimit
Name: STMeetingUsersLimitEnabled
text]
Name: STMeetingUsersLimit
Name: STAutoExtendMeetingEnabled
Name: STMeetingExtendTime
Name: STLogTime
Name: STCommunityLogin
Name: STCommunityLoginFailed
text]
Name: STCommunityTotalConnections
text]
Name: STLogHistory
Name: STCommunityLogUsageFrequency
Name: STLogToFiles
Name: STMeetingLogEvents
Name: STMeetingLogParticipants
Name: STLogToNSF
Name: STLogFileName
sametime.log
Name: SHARED_MAIL
Name: SCOS_DIR_1
text]
Name: SCOS_DIR_MAX_SIZE_MB_1
text]
Name: SCOS_ACTIVE_1
text]
446
Size: 3
Size: 2
Value: 0
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Text/text list
Text/text list
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Text/text list
Number/number list
Number/number list
Number/number list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
3
3
3
10
10
10
10
10
10
3
10
10
10
2
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
1
2
2
1533
8081
1516
1503
1533
8081
1
8082
8081
8000
[no
Type:
Type:
Type:
Type:
Number/number list
Text/text list
Number/number list
Text/text list
Size:
Size:
Size:
Size:
10
3
10
2
Value:
Value:
Value:
Value:
100
0
60
[no
Size: 10
Size: 10
Size: 2
Value: 100
Value: 60
Value: [no
Size: 10
Size: 2
Value: 500
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Number/number list
Text/text list
Number/number list
Text/text list
Text/text list
Text/text list
10
3
10
3
3
2
50
1
15
0
1
[no
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Number/number list
Number/number list
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
10
10
3
3
3
3
14
30
10
0
1
1
1
Size: 3
Size: 2
Value: 0
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
text]
Name:
SCOS_DIR_2
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_2
Size: 2
Value: [no
SCOS_ACTIVE_2
Size: 2
Value: [no
SCOS_DIR_3
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_3
Size: 2
Value: [no
SCOS_ACTIVE_3
Size: 2
Value: [no
SCOS_DIR_4
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_4
Size: 2
Value: [no
SCOS_ACTIVE_4
Size: 2
Value: [no
SCOS_DIR_5
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_5
Size: 2
Value: [no
SCOS_ACTIVE_5
Size: 2
Value: [no
SCOS_DIR_6
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_6
Size: 2
Value: [no
SCOS_ACTIVE_6
Size: 2
Value: [no
SCOS_DIR_7
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_7
Size: 2
Value: [no
SCOS_ACTIVE_7
Size: 2
Value: [no
SCOS_DIR_8
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_8
Size: 2
Value: [no
SCOS_ACTIVE_8
Size: 2
Value: [no
SCOS_DIR_9
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_9
Size: 2
Value: [no
SCOS_ACTIVE_9
Size: 2
Value: [no
SCOS_DIR_10
Size: 2
Value: [no
SCOS_DIR_MAX_SIZE_MB_10
Size: 2
Value: [no
SCOS_ACTIVE_10
Size: 2
Value: [no
DAOSEnable
Size: 3
Value: 0
447
Name: DAOSObjDelete
Name: DB2Host
text]
Name: DB2Port
text]
Name: DB2Inst
text]
Name: DB2Db
text]
Name: DB2Dir
text]
Name: DB2Def
Name: DB2UDFSrv
text]
Name: DB2UDFPath
text]
Name: DB2GroupMax
Name: DB2DefUser
text]
Name: DB2QVRows
Name: tsMaxMem
Name: tsIPCPort
Name: tsIPCPort2
Name: tsExternalURL
http://9.37.30.206/traveler
Name: tsAddressBookAccess
text]
Name: tsDenyAccess
text]
Name: tsUserCMD
Name: tsUserWipe
Name: tsLogLevel
Name: tsTrcLevel
Name: tsTrcCmp
Name: tsTrcSize
Name: tsTrcFiles
Name: tsTrcPriv
2;4;8;16
Name: tsPollTime
Name: devPTCPP
Name: tsPHBeatAlg
Name: tsPHBFixed
Name: tsPHBInitial
Name: tsPHBAmim
Name: tsPHBAmaxsec
Name: tsPHBAretry
Name: tsPofflinehr
Name: tsPcleanup
Name: Owner
text]
Name: LocalAdmin
text]
Name: PKMinWidth
Name: PKMaxWidth
Name: PKDefWidth
448
Size: 10
Size: 2
Value: 30
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 3
Size: 2
Value: 1
Value: [no
Size: 2
Value: [no
Size: 10
Size: 2
Value: 10
Value: [no
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Number/number list
Number/number list
Number/number list
Number/number list
Text/text list
10
10
10
10
29
500
512
50125
50126
Size: 2
Value: [no
Type: Names
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Text/text list
Text/text list
Text/text list
Text/text list
Text/text list
Number/number list
Number/number list
Text/text list
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
3
3
3
3
3
10
10
17
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
0
1
3
0
*
50
10
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Number/number list
Number/number list
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Authors
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
10
10
3
10
10
10
10
10
10
10
2
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
3
8642
2
55
30
30
15
30
24
30
[no
Type: Authors
Size: 2
Value: [no
Size: 3
Size: 6
Size: 6
Value: 0
Value: 1024
Value: 1024
Name: PKMaxAge
Name: PKMinDate
08/01/1977
Name: PKDueDate
09/04/2112
Name: PKOldKeyDays
Name: ChangeRequest
text]
Name: DocumentAccess
[ServerModifier]
Name: BookmarkDB
bookmark.nsf
Name: ServerPlatform
Windows/2003 5.2 Intel Pentium
Name: ASPServer
Name: DAOSWarned
Name: $ServerMain
Name: $Server_Ports_Tabs
Name: $Server_Ports_Internet2_Tabs
Name: $Server_Tasks_Tabs
Name: $Server_InetProt_Tabs
Name: $Server_MTA_Tabs
Name: FltRcvryMD
Name: ServerBuildNumber
Release 8.5.3
Name: ClusterName
text]
Name: ServerCPUCount
Name: NSDEnbld
Name: CfgNABonly
Name: AllowAccess
text]
Name: Protocol_0
Name: NetName_0
Network
Name: NetAddr_0
9.37.30.206
Name: Protocol_1
text]
Name: NetName_1
text]
Name: NetAddr_1
9.37.30.206
Name: Protocol_2
text]
Name: NetName_2
text]
Name: NetAddr_2
9.37.30.206
Name: Protocol_3
text]
Name: NetName_3
text]
Name: NetAddr_3
9.37.30.206
Size: 10
Size: 10
Value: 36500
Value:
Type: Date-time/range
Size: 10
Value:
Size: 10
Size: 2
Value: 365
Value: [no
Type: Authors
Size: 18
Value:
Size: 14
Value:
Size: 32
Value:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Text/text list
Text/text list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Number/number list
Text/text list
Text/text list
3
3
10
10
10
10
10
10
6
15
0
0
0
0
0
0
0
0
8530
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Number/number list
Text/text list
Text/text list
Names
10
3
3
2
2
1
0
[no
Size: 5
Size: 15
Value: TCP
Value: TCPIP
Size: 13
Value:
Size: 2
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 2
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 2
Value: [no
Size: 2
Value: [no
Size: 13
Value:
449
Name: Protocol_4
text]
Name: NetName_4
text]
Name: NetAddr_4
9.37.30.206
Name: Protocol_5
text]
Name: NetName_5
text]
Name: NetAddr_5
9.37.30.206
Name: Protocol_6
text]
Name: NetName_6
text]
Name: NetAddr_6
9.37.30.206
Name: Protocol_7
text]
Name: NetName_7
text]
Name: NetAddr_7
9.37.30.206
Name: EnabledList
1;0;0;0;0;0;0;0
Name: Ports
Name: Network
Network
Name: NetAddresses
9.37.30.206
Name: Protocols
Name: SSLStrongEncryption
03040506090A
Name: IMAP_TCPNP
Name: POP3_TCPNP
Name: AdminPSuspendRange
text]
Name: CatalogType
Name: CatalogWeekDays
1;2;3;4;5;6;7
Name: WeekDays
1;2;3;4;5;6;7
Name: HTTP_CompMinS
Name: HTTP_CompMaxS
Name: HTTP_CompMM
Name: HTTP_CSDefault
Name: HTTP_Version
Name: IIOP_IdleMinsAllowed
Name: TRANSLOG_Path
text]
Name: SCOS_DIR_ACTIVE_FILES_1
text]
Name: SCOS_ONLINE_1
text]
450
Size: 2
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 2
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 2
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 2
Value: [no
Size: 2
Value: [no
Size: 13
Value:
Size: 28
Value:
Size: 7
Size: 15
Value: TCPIP
Value: TCPIP
Size: 13
Value:
Size: 5
Size: 14
Value: TCP
Value:
Size: 3
Size: 3
Size: 2
Value: 1
Value: 1
Value: [no
Size: 3
Size: 25
Value: 0
Value:
Size: 25
Value:
Type:
Type:
Type:
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Value:
Value:
Value:
Number/number list
Number/number list
Number/number list
Text/text list
Number/number list
Number/number list
Text/text list
10
10
10
4
10
10
2
1
128
20
98
1
60
[no
Size: 2
Value: [no
Size: 2
Value: [no
Name: SCOS_DIR_ACTIVE_FILES_2
text]
Name: SCOS_ONLINE_2
text]
Name: SCOS_DIR_ACTIVE_FILES_3
text]
Name: SCOS_ONLINE_3
text]
Name: SCOS_DIR_ACTIVE_FILES_4
text]
Name: SCOS_ONLINE_4
text]
Name: SCOS_DIR_ACTIVE_FILES_5
text]
Name: SCOS_ONLINE_5
text]
Name: SCOS_DIR_ACTIVE_FILES_6
text]
Name: SCOS_ONLINE_6
text]
Name: SCOS_DIR_ACTIVE_FILES_7
text]
Name: SCOS_ONLINE_7
text]
Name: SCOS_DIR_ACTIVE_FILES_8
text]
Name: SCOS_ONLINE_8
text]
Name: SCOS_DIR_ACTIVE_FILES_9
text]
Name: SCOS_ONLINE_9
text]
Name: SCOS_DIR_ACTIVE_FILES_10
text]
Name: SCOS_ONLINE_10
text]
Name: DAOSMinObjSize
Name: DAOSBasePath
Name: DB2AcWrn
Name: tsAllowAccess
text]
Name: tsPHBAmax
Name: tsPoffline
Name: Certificate
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
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Size: 2
Value: [no
Type:
Type:
Type:
Type:
Size:
Size:
Size:
Size:
Value:
Value:
Value:
Value:
Text/text list
Text/text list
Number/number list
Names
7
6
10
2
Size: 10
Size: 10
Size: 910
64000
DAOS
15
[no
Value: 900
Value: 1440
Value:
451
Size: 2
Value: [no
Size:
Size:
Size:
Size:
Value: 2
Value: 0
Value: 0
Value:
3
3
10
54
Size: 22
Value:
*********************************************************************************
******************** 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
Mapping
Name: RM_MapType
Type: Text/text list
Name: ServerName
Type: Text/text list
CN=9.37.30.206/O=organization
Name: Owner
Type: Authors
CN=9.37.30.206/O=organization
Name: LocalAdmin
Type: Authors
CN=9.37.30.206/O=organization;CN=Administrator/O=organization
Name: ServerNameDisplay
Type: Text/text list
9.37.30.206/organization
Name: RM_MapFrom
Type: Text/text list
/Microsoft-Server-ActiveSync*
Name: RM_MapTo
Type: Text/text list
/traveler/Microsoft-Server-ActiveSync*
Name: RM_ServerIP
Type: Text/text list
text]
452
Size: 9
Value:
Size: 5
Size: 24
Value: Map
Value:
Size: 24
Value:
Size: 54
Value:
Size: 19
Value:
Size: 31
Value:
Size: 40
Value:
Size: 2
Value: [no
Name: Comment
Type:
text]
Name: DocumentAccess
Type:
[NetModifier]
Name: $SrvMap
Type:
Name: MappingType
Type:
Name: Type
Type:
Mapping
Name: $REF
Type:
08B5C5099E6B2B7785257A6F006D0CE2
Name: $UpdatedBy
Type:
CN=9.37.30.206/O=organization
Name: $Revisions
Type:
09/04/2012 04:34:45 PM;09/04/2012 04:34:45 PM
Text/text list
Size: 2
Value: [no
Authors
Size: 15
Value:
Number/number list
Text/text list
Text/text list
Size: 10
Size: 3
Size: 9
Value: 0
Value: 1
Value:
Value:
Names
Size: 28
Value:
Date-time/range
Size: 22
Value:
*********************************************************************************
******************** 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
Mapping
Name: RM_MapType
Type: Text/text list
Name: ServerName
Type: Text/text list
CN=9.37.30.206/O=organization
Name: Owner
Type: Authors
CN=9.37.30.206/O=organization
Name: LocalAdmin
Type: Authors
CN=9.37.30.206/O=organization;CN=Administrator/O=organization
Name: ServerNameDisplay
Type: Text/text list
9.37.30.206/organization
Name: RM_MapFrom
Type: Text/text list
/servlet/traveler*
Name: RM_MapTo
Type: Text/text list
/traveler*
Name: RM_ServerIP
Type: Text/text list
text]
Name: Comment
Type: Text/text list
text]
Name: DocumentAccess
Type: Authors
[NetModifier]
Name: $SrvMap
Type: Number/number list
Name: MappingType
Type: Text/text list
Name: Type
Type: Text/text list
Mapping
Name: $REF
Type: Reference to parent
08B5C5099E6B2B7785257A6F006D0CE2
Size: 9
Value:
Size: 5
Size: 24
Value: Map
Value:
Size: 24
Value:
Size: 54
Value:
Size: 19
Value:
Size: 20
Value:
Size: 12
Value:
Size: 2
Value: [no
Size: 2
Value: [no
Size: 15
Value:
Size: 10
Size: 3
Size: 9
Value: 0
Value: 1
Value:
Size: 20
Value:
453
Name: $UpdatedBy
Type: Names
CN=9.37.30.206/O=organization
Name: $Revisions
Type: Date-time/range
09/04/2012 04:34:45 PM;09/04/2012 04:34:45 PM
Size: 28
Value:
Size: 22
Value:
454
455
456
457
458
1
2
0
1
/
/
/
/
5000
200
1 / 5000
50
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)
459
460
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)
461
462
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)
463
com.lotus.sync.admin.UpdateTravelerDB2$TravelerDB2Thread.pollAndServiceRequest(UpdateTravelerDB2
.java:1492)
com.lotus.sync.admin.UpdateTravelerDB$TravelerDBThread.run(UpdateTravelerDB.java:156)
464
(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)
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
465
Threads
Threads
Threads
Threads
Threads
-- Busy
total: 4
available: 3
busy: 1
deadlocked: 0
monitor deadlocked: 0
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
466
467
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>
468
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
469
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
470
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
471
472
473
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
474
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
when the Milliseconds becomes too large, so the real value is the
most common return codes are: 200=OK, 408=Request Timeout (Device
Server timed out the session), 409=Conflict (Device started a new
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".
475
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
476
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
477
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
478
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
479
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
480
481
Server.WorkThreads.TCPIP = 40
482
483
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 }
484
485
486
!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}
487
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
Database
Database
Database
Database
Database
5
5
489
490
Back cover
Produced in
collaboration with:
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.
Content in this document was produced in collaboration with Lotus and IBM Redbooks