NICI on NetWare has multiple signed NLM programs called XLMs. The MODULES command displays the NLM names, not the XLMs. The startup directory is typically c:\nwserver.
ccs.xlm (ccs.nlm)
This file is located in the startup directory, and is the only XLIB module that exports APIs used by other NLM programs.
xmgr.xlm (xmgr.nlm)
This module is located in the startup directory. It has no usable APIs by other NLM programs.
expxeng.xlm (xengnul.nlm, xengexp.nlm, xngaexp.nlm)
This module is located in the startup directory. The presence of these NLM programs identifies the availability of weak/exportable cryptography.
domxeng.xlm (xengnul.nlm, xengexp.nlm, xengusc.nlm, xngausc.nlm)
This module is located in the startup directory. The presence of these NLM programs identifies the availability of strong/domestic cryptography. As of NICI 2.x, Novell ships strong cryptography worldwide.
xsup.xlm (xsup.nlm)
This module is located in the startup directory.
nicisdi.xlm (nicisdi.nlm)
This module is present in the sys:\system directory and is loaded by the autoexec.ncf file. This is the Security Domain Infrastructure management module. If this module is not loaded, then security domain keys (such as the tree key) are not loaded into NICI and they are not available. You usually see a 1460 error when this module is not loaded.
sasdfm.xlm (sasdfm.nlm)
This module is present in the sys:\system directory and is loaded by the autoexec.ncf file. This is the SAS Data Flow Manager file; it is responsible for handling NCP communications for session key setup, as well as handling client NICI initialization requests. The absence of this module disables session key support in NICI. Typical symptoms are not being able to export user certificates in ConsoleOne, or not being able to use NMAS to log in to eDirectory.