This topic describes configuration file locations, a Solaris configuration tip, and how to avoid a DSAPI filter-loading error when starting the Lotus Domino Web server as a non-root user on Linux and UNIX operating systems.
Lotus Domino Server file locations
Lotus Domino server file locations are:
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 a Linux or UNIX operating system, if the Lotus Domino Web server starts using a non-root user, you are likely to generate a DSAPI filter-loading error when the Lotus Domino Server starts:
Error loading DSAPI filter. Filter not loaded: /usr/WebSphere/AppServer/bin/libdomino6_http.a
Manually change the WebSphere Application Server bin directory permissions from 750 to 755 to run Lotus Domino Server as a non-root 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.