Lotus Domino file locations and troubleshooting tips
Lotus® Domino® Server is one of the Web servers that WebSphere® Application Server supports. You must be aware of configuration file locations and other useful tips related to using Lotus Domino.
Lotus Domino Server file locations
Lotus Domino server file locations are:
The Domino Server plug-in might fail to load on an IBM i system
Error messages in the Domino console can indicate more detailed error messages in the Notes® spool files. For example, if you see the following error message on your Domino console, perform the following steps:
Sample error message:
01/05/2006 13:28:56 HTTP Server:
Failed to load DSAPI module
/QSYS.LIB/QWAS9.LIB/LIBDOMINOH.SRVPGM
The Domino Server plug-in might fail to configure on a Solaris platform
lotus.notes.NotesException: Could not load dll for system name SUNOS
at lotus.notes.NotesThread.load(NotesThread.java:210)
at lotus.notes.NotesThread.<clinit>(NotesThread.java:24)
java.lang.UnsatisfiedLinkError: NnotesInitThread
at lotus.notes.NotesThread.NnotesInitThread(Native Method)
at lotus.notes.NotesThread.initThread(NotesThread.java:99)
at lotus.notes.NotesThread.run(NotesThread.java:133)
Avoiding a DSAPI filter-loading error when the Lotus Domino Server starts
On operating systems such as AIX® or Linux®, if the Lotus Domino Web Server starts using a nonroot user, you are likely to generate a DSAPI filter-loading error when the Lotus Domino Server starts:
Error loading DSAPI filter.
Filter not loaded: app_server_root/bin/libdomino6_http.a
Manually change the WebSphere Application Server bin directory permissions from 750 to 755 to run Lotus Domino Server as a nonroot user and not generate the error.
You must also change permissions on the WebSphere Application Server logs directory to 777 to allow Lotus Domino Server to write to the log. However, this change poses a security risk.
If the Lotus Domino Server is started as root, the problem does not occur.