For mobile access, there are different options available for a variety of device types. This article discusses various options and solutions available for mobile access.
The following table summarizes the supported device types and the available features for each.
Device Type | Traveler | BES Server | POP/IMAP | iNotes Ultra Lite |
|
|
| X |
|
|
|
| X |
| X | X |
|
| X |
|
| X |
|
| X |
|
|
|
Traveler
Lotus Traveler is a Push-mail solution included in Lotus Notes licence. It is available at no additional charge if you have purchased Lotus Notes 8.x or Lotus Notes.8.5.x.
It is recommended to run Traveler on a separate server. Traveler must installed on top of the Domino server and it is called an Advanced Product (a product/component that is installed on top of Domino). The version of Lotus Traveler you may install depends on Lotus Domino version you server is currently running. Review the software requirements to check which version is supported for this Traveler version you desire (for example, Lotus Traveler 8.5.2 can be installed only on Lotus Domino 8.5.2). Additional information on Traveler can be found in the following link:
http://www-01.ibm.com/software/lotus/products/notes/traveler.html
Lotus Traveler supports Windows Mobile, Nokia Symbian, Apple iPod/iPhone/iPad. Android phone support is added in fixpack 1 of 8.5.2.
To deploy Lotus Traveler, you need:
- Install Lotus Traveler on top of Lotus Domino.
- Distribute Traveler clients on mobile phone (they can be downloaded from Traveler homepage, or distributed remotely).
Installing Traveler Server
Lotus Traveler server is supported on Windows 32, Windows 64 and Linux OS. Linux OS support was added in release 8.5.2.
Lotus Notes Traveler system requirements can be found in the following link:
http://www-01.ibm.com/support/docview.wss?rs=475&uid=swg27007909
Things to check before you start installation:
- The Domino Servlet Manager is enabled. To do this, open the Server Document of the Traveler server, Internet Protocols -> Domino WEB Engine tab. Set the Java Servlets to Domino servlet manager.
- Verify that the Lotus Traveler server is included in LocalDomainServers group so it has Manager access to all mail files.
- If your Traveler server is located in a DMZ, enable Configuration Directory. When using a configuration only directory the Domino Directory will contain only configuration files as all other information will be requested from other servers that has a full copy of names.nsf.
- It is recommended to have a SSL certificate on a server. This improves the security of your server. Using a HTTPS connection ensures that no one can intercept (listen to the network traffic) when a password is sent from the phone to the server. With a standard HTTP connection the password is transmitted in plain text.
- Traveler versions prior to 8.5.2 use two ports, one for AutoSync and the second for data transmission. In 8.5.2, there is only communications on HTTP or HTTPS port.
For complete and updated information on things to check prior to installing Lotus Notes Traveler, review the information from the following link:
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Before_you_install_LNT8521
Installing a Traveler server on both Windows and Linux is quite easy. On Windows, the LotusTraveler setup file is launched, and you choose what you need to install, see options below. On Linux, the Traveler installation can be performed in two ways, via graphical mode or silent install. The Silent install is preferred method since it does not require graphical mode which maybe missing on some systems. Just configure a silent install answer file and run installation with silent install switch:
- Clients (installs only images for Nokia/Windows mobile/Apple)
- Server only (install only server part without clients
- Both (recommended option) - this will install both option, server and client
After you complete the Traveler installation wizard, pay attention to last screen of installation wizard. Check to make sure the installation is completed successfully.
Lotus Traveler stores information about registered devices in lotustraveler.nsf database. Do not delete device documents from this application, Lotus Traveler can be managed only with console commands.
Troubleshooting
If you have issue with phone, try to understand if this is the problem for one user or for all users. This helps you understand, where to look for solution on device or on a server.
The most popular problem is autosync is not working. In most cases restarting the phone solves this problem.
If only one user has problems, try to login to Traveler server using a web browser with the user's credentials. You may see additional valuable information that may help you as you investigate the problem.
You may add additional logging for this device/user with Lotus Traveler console commands. When the problem is solved, do not forget to disable logging, as this generates debug XML files on server, and they fill disk space.
In case the entire server is not functioning, search the console for JAVA errors and search for a solution from IBM support. Reinstalling Traveler is also an option. Reinstalling does not require much time and it will fix problems with missing components of Traveler.
For more troubleshooting information, refer to the following references:
For Lotus Traveler console commands information, refer to the following link:
http://www.lotus.com/ldd/dominowiki.nsf/dx/Console_commands_LNT8521
BlackBerry
If you are looking for information about Domino and you BES, consult this table as it shows the Domino Release/Server OS and BES:
http://na.blackberry.com/eng/support/software/server_domino_ver_march_05_10.pdf
Domino Server Installation on a Windows Server Before Blackberry Enterprise Server Install
A Domino Server installation is recommended on the server where the Blackberry Enterprise Server will be installed. The installation makes the administration easier.
The installation should follow a usual Domino installation as shown below:
- Check if the server document for the new server has been created and exists in the Domino Directory.
- Prepare for the Domino server build, placing the following files on the server in a temporary location: Server ID file , Domino server executable file, and Domino system files.
- Install the Domino server code by running the self-extracting installation executable, answering the prompt questions.
- Copy or move the files from the temporary location to the permanent place.
- Execute a compact in the system files by opening a command prompt. Use ncompact -D filename.nsf (for more info about compact).
- Configure the Domino server by double clicking on the server program icon, answering the prompt questions.
- Click on Domino server program icon to start the server for the first time. Server is ready for installation of BES.
Preparing the Environment
To have the environment prepared, perform these steps (which help to prevent problems in the future):
- Check if the Domino Server is a member of the LocalDomainServer group in the Domino Directory and if Adminp is running. Try opening admin4.nsf,
- Check if the server can access the other servers in the environment.
- Check if the setup application for the BlackBerry Enterprise Server can access the Domino environment variables in the NOTES.INI file.
- Verify that the remote DB2 or SQL Server is accessible. This step must be performed if you choose to have Blackberry Manager to use authentication in a SQL or DB2 Environment.
To verify, type CMD and then type telnet 1433. If you have connection, the cursor will be blinking. If that happens, close the Command Prompt because you can connect to server.
Post Blackberry Enterprise Server Installation
After you complete the BES installation and you want to be sure Domino is properly running, check the console for messages such as “Message sent to handheld”, “OTAFM” or “OTAC”. These messages indicate that messages are flowing from the server to the environment.
Start the Blackberry Controller after the messages are being delivered that will prevent a silent crash causing nbes and domino to restart on the server again.
If dispatcher is not starting up, it is necessary to check SQL or DB2 environment. In most of the cases, the connection between the BES and the server is causing the problem.
There are some cases where a recycle of the SQL machine that holds the SQL/DB2 needs to be performed. NBES is related to the Domino task that starts the BES for Domino. To start it using “load nbes” command at Domino Console and to finish it use “tell nbes quit” command at Domino Console.
Blackberry Controller can be stopped while server is initializing users. It must be started once all the users were initialized and mails are flowing properly. We can Stop/Start anytime it to prevent a silent crash (unexpected reboot).
Locating a Problematic Blackberry State Database
Many times if a Blackberry server crashes it is due to a problematic end user Blackberry state database. To find out where the problem is, you can do the following:
- From the console log file, locate problem thread ID
[1114:000D-1384] Thread=[1114:000D-1384]
Stack base=0x07110090, Stack size = 12068 bytes
PANIC: LookupHandle: null handle
- Do a search in NSD on "FATAL" to find the problem thread id to confirm.
- If there are multiple crashes, several NSDs can also be checked to ensure it is the same file causing the problem.
FATAL THREAD with PARAMETER DATA 12/143 [ nserver: 1114: 1384]
- Search NSD on "Open Databases" and look for file with problem thread ID.
[Domino Install directory]\data\BES\state\123456789.nsf
Version = 43.0
SizeLimit = 0, WarningThreshold = 0
ReplicaID = 0x87256f00:0x004b5bba
bContQueue = NSFPool [ 000f6545]
Offline = No
DeleteInProgress = No
FDGHandle = 0xf0240409, RefCnt = 1, Dirty = N
DB Sem = (FRWSEM:0x0244) state=-1, waiters=0, refcnt=1, nlrdrs=0 Writer=[ nserver: 1114: 1384]
SemContQueue ( RWSEM:#0:0x029d) rdcnt=-1, refcnt=1 Writer=[ nserver: 1114: 1384], n=0, wcnt=0, Users=-1, Owner=[ nserver: 1114: 1384]
By: [ nserver: 1114: 000d] DBH= 154, User=CN=COMPANY/NEWORG
- From the information we get from the NSD, we see that the 123456789.nsf file caused the server to crash.
Fixing a problematic Blackberry state database
You can fix a problematic database by doing one of the following options (you must decide which one can be applied to your environment):
- Deleting or renaming the .NSF file with the problem and recreating it.
- Executing maintenance (fixup, compact or an updall) on the DB using the Domino console.
For more information, tips and tricks from RIM Website:
http://na.blackberry.com/eng/support/blackberry101/tips/
Lotus iNotes Ultra-Lite
Lotus iNotes Ulta-Lite is for mobile devices and can also be with a traditional PC browser. For reference, go to http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg21315871
Lotus iNotes runs on the following client operating systems:
- Microsoft Windows XP Professional and Microsoft Windows Vista Business and Enterprise Editions using the following browsers:
Internet Explorer or Mozilla Firefox
- Novell SUSE Linux Enterprise Desktop 10 using the following browsers:
Mozilla Firefox
- RedHat Enterprise Linux Desktop 5.2 using the following browsers:
Mozilla Firefox
- Macintosh OS X 10.5 using the following browsers:
Mozilla Firefox
Safari 3.1.x
- Apple iPhone and iPod Touch firmware version 1.1.4 or later (for the ultra-light mode)
There is increase in mobility request to have mail configured or available on devices using a web browser. When enabling iNotes, confirm the following settings are enabled/configured:
- End user mail file:
ACL to Anonymous=No Access
ACL Advanced tab = Maximum Internet access to Editor.
- Server Address Book:
Must be Domino 851 or greater
- Forms85.nsf File
Must be the only Formsxx.nsf located on server iNotes directory. If not, it can cause an end user issue when opening in the browser. Be sure to remove any old Formsxx.nsf listed from old installations.
- Remember that any change that you do with FormsXX (like removing old files) requires you to reload HTTP on server (restart task http). If you do not execute this command, it will give you a “Read Only” error when trying to open a mail file via Internet Browser.
- Directory Assistance File
This should be on the lastest template available.
- SSL Configuration
Install the SSL certificate by copying the necessary files to Domino Data directory (.kyr & .sth files).
Open your the server document for your server and go to the Configuration -> Servers -> All Servers -> your server -> Ports -> Internet Ports tab and enter the SSL Key file name. You should also verify the SSL port is enabled.
- HTTP Config
- Define the hostname and/or IP addresses to be used by this server. To do this, open your Address book and go to Configuration -> Servers -> All Servers -> your server -> Internet Protocols -> HTTP. Set the Bind to host name field to enabled and set the Hostname(s) field to the proper host names and/or IP addresses for your server.
- Ensure the operating system is not running any other http task that could interfere with the Domino server. If it is, disable it before enabling Domino's http server. If you do not do that, Domino will not be able to use port 80/443.
- Verify HTTP and SSL is working properly:
Via the Domino Administrator client review the active tasks. Verify that the HTTP task is running.
To verify a SSL connection is in use, access the server using this syntax -> http://yourserveraddress and confirm that you see the little lock on the bottom of your browser.
For more information, go to
http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=/com.ibm.help.domino.admin85.doc/H_LOTUS_INOTES_ULTRALITE_MODE_STEPS.html
IMAP/POP
What is IMAP?
You can view just the heading and the sender of the message and then decide whether to download the mail. You can also create and manipulate folders or mailboxes on the server, delete messages, or search for certain portions or an entire message.
Domino IMAP users can:
- Replicate messages from the server that runs the IMAP service and store them on end user local replica.
- Access messages directly from the server (different from POP3 users who download the messages first).
What is POP3?
Post Office Protocol 3 (POP3) is old and less sophisticated e-mail protocol. When you read your mail, all of it is immediately downloaded to your computer and it is no longer kept on the server. This can be a problem if you want to access your mailbox on the server or different computers due to possible hardware problems, virus, or preference .
The IMAP protocol is preferred over the POP3 protocol because if we enable both, we can downgrade the performance of the server running Domino. Other considerations:
- When using POP3, we will force the end user computer to connect to server, start a push/pull to bring messages to the end user computer.
- When using IMAP, the end user will synchronize the local replica with the server only for new messages to avoid server to be in a sync mode for a long time which consumes CPU of the server.
- Other item that must be considered is that the messages should be stored in MIME in order to prevent CPU issues.
For more information about performance, go to:
|