Lotus Domino tips

 

Lotus Domino tips

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:

On OS/400 systems:

If the plug-in fails to initialize, look for error messages in the Domino console and the Notes spool files. For example if you see the following error message in your Domino console, perform the steps below.

Sample error message: 01/05/2005 13:28:56 HTTP Server: Failed to load DSAPI module /QSYS.LIB/QWAS6.LIB/LIBDOMINOH.SRVPGM

  1. From a CL command prompt, enter the Work with Spool Files command:
    WRKSPLF QNOTES 
  2. Use option 5 to open the applicable spool file for your notes server.

    Note: you may have to end your domino server to be able to view the spool file.

  3. Inspect the output to find applicable error messages. In this example, the following entry is displayed in the log:
    ERROR: lib_sxp: sxpCreate: Can't open '/qibm/userdata/webas5/base/rb5025test/config/cells     /plugin-cfg.xml', OS Err: 3401 
    ERROR: ws_config_parser: configParserParse: Failed to create the sxpParser object for     /qibm/userdata/websphere/appserver/v6/base/profiles/myprofile/config/plugin-cfg.xml 
    ERROR: ws_common: websphereUpdateConfig: Failed parsing plugin config file: 
    ERROR: /qibm/userdata/websphere/appserver/v6/base/profiles/myprofile/config/plugin-cfg.xml 
    ERROR: The above file may not have correct authorities. 
    ERROR: Do WRKLNK, Opt 9 on above file. 
    ERROR: Check that QTMHHTTP and QNOTES have correct authorities: 
    ERROR: QTMHHTTP *RX 
    ERROR: QNOTES *RX 
    ERROR: ws_common: websphereInit: Failed to load the config file 
    ERROR: domino5_plugin: FilterInit: Failed to initialize WebSphere 
    [Solaris]

    The Domino Server plug-in might fail to configure on a Solaris platformIf this occurs during installation, a dsapi_stderr.txt file is created in the logs directory and you get the following error messages:

    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)
    You can configure the WebSphere Application Server or Domino Server plug-in manually using the Domino Server Web administration tool. Use the following procedures:

    1. Start the Domino Server.

    2. Enter the URL for the Domino Server Web Administration site using a browser. For example, http://host_name/names.nsf. Enter the administrator user name and password.

    3. Double-click Server-Servers .

    4. Double-click WebServer to configure.

    5. Double-click Edit Server .

    6. Double-click Internet Protocol .

    7. Add the WebSphere Application Server DSAPI plug-in to the DSAPI field. For example, /opt/WebSphere/AppServer/bin/libdomino5_http.so Note: If there are already DSAPI filter files specified use a space to delimit the WebSphere plug-in file.

    8. Double-click Save and Close .

    9. Restart the Domino Server.
    [Linux][UNIX]

    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.