Key Measures of Lotus Traveler Server Health
Of course, monitoring Traveler begins with making sure the Traveler server task is operating. VitalSigns does that.
Lotus Notes Traveler is tightly tied to the HTTP task in Domino, so running HTTP is a prerequisite. VitalSigns watches over this key task.
IBM recommends 1.2 HTTP sessions for each Traveler device, and as the number of Traveler users grows, so too will the need for HTTP sessions.
VitalSigns automatically computes the number of HTTP sessions needed and warns you as your server starts to run out. It also shows you the peak number of sessions as a percentage of the number of availble sessions. See screenshot below:
VitalSigns tracks the number of device syncs between scans and makes sure that the number is always incrementing... indicating sucessful device syncs.
Officially, it is called "IBM® Lotus® Notes® Traveler software” but most of us just call it Lotus Notes Traveler or simply “Traveler”. Traveler provides mobile support for Lotus Notes and Web Access users with automatic, real-time replication of email, calendar, address book, journal, and to-do lists across mobile device platforms - Apple iOS, Google Android 2.x and 3.x, Nokia Symbian and Microsoft Windows Mobile. Frankly, it is just plain cool.
Because Lotus Traveler is so cool, it is crucial to be able to monitor your Lotus Traveler servers. Why? Bbecause as soon as you deploy Traveler, your users are going to be clamoring for it, and usage will explode. Traveler quickly becomes mission critical.
If you are responsible for multiple Traveler servers, you know that each server has its own LotusTraveler.nsf database, which maintains a list of users and offers a variety of actions that can be performed, such as wipe device, deny access, approve, etc.
The challenge for Administrators arises when an urgent request comes in to either wipe a device or cancel a wipe request. Canceling a wipe request only works if the device hasn't already been wiped. So time is of the essense.
Unless you have a strict (and working) system for putting users onto specific servers, finding a given user across multiple servers is not something that can happen instantly. In most cases, we find that users connect to whatever Traveler server they want to, regardless of what server they are "supposed" to use.
VitalSigns solves this problem by consolidating all Traveler users into a single database, which can be sorted and searched. All the usual Traveler actions, such as Wipe Device and Cancel Wipe Request are at your fingertips.
Watch as our Product Manager takes you through a quick demo of VitalSigns' Traveler monitoring capabilities in this short video.