SAV Interface for NetWare installation notes -------------------------------------------- www.sophos.com Contents -------- About SAV Interface for NetWare Subscribing to SAV Interface for NetWare using EM Library Installing SAV Interface for NetWare Loading SAVI.NLM Updating SAV Interface for NetWare Configuring SAV Interface for NetWare SAVI Developer Toolkit About SAV Interface for NetWare ------------------------------- SAV Interface is a software library which encapsulates the Sophos virus engine and which may be used by third-party application software to perform virus scanning. SAV Interface for NetWare is supplied in the form of a NetWare Loadable Module (NLM) called SAVI.NLM. To subscribe to SAV Interface for NetWare you require an installation of Sophos EM Library. SAV Interface for NetWare supports NetWare 5.1, 6 and 6.5. Subscribing to SAV Interface for NetWare using EM Library --------------------------------------------------------- This procedure assumes you have installed Sophos EM Library to manage automatic updating of Sophos software. For further information, please refer to the "EM Library startup guide" on the Sophos website. 1. Open the EM Library console. In the console tree, double-click "EM Library". Double-click "Packages" and then click "Unsubscribed". 2. In the list of unsubscribed packages shown in the details pane, highlight the "SAV Interface for NetWare Latest" package. Right-click to display a menu and select "Subscribe". 3. In the message box, click "Yes" to specify a central installation directory into which the software will be placed. The "Central installation configuration" wizard now guides you through the steps needed to specify a new central installation directory. 4. If necessary, in the "CID Credentials" dialog box, specify a NetWare NDS account for accessing the NetWare server: Click "NDS details". In the "NDS Information" dialog box, enter the tree name and fully distinguished names for the user and server in the format cn=user.o=organisation If you are uncertain what to enter, run the NetWare NWADMIN utility supplied with the NetWare Windows client. Then click "OK" to return to the "CID Credentials" dialog box. 5. In the "CID Location" dialog box, click "Custom CID location". You must ensure that EM Library places SAV Interface for NetWare updates directly into the updates folder on the NetWare server. By default, this folder is \\[servername]\SYS\SOPHOS\SAVIUPD (where [servername] is the name of the NetWare server). Make sure that this directory exists on the NetWare server and is visible to the EM Library computer. The NetWare server checks for updates placed here, by default, every 5 minutes. 6. For other central installation configurations Sophos recommends that you use the default settings. 7. In the details pane of the EM Library console, check that the new central installation location is displayed. 8. In the "Configuration" view, click "Download Packages". In the "EM Library" message box, click "Yes". The "Updating packages from the parent" progress dialog box is displayed. When downloading is complete, the "Updating your central installations" progress dialog box is displayed. Whenever EM Library downloads updates from Sophos, it updates the files in SYS:/SOPHOS/SAVIUPD. NB Sophos strongly recommends the use of Novell-supplied NetWare clients on Windows computers, rather than the Microsoft NetWare clients. Installing SAV Interface for NetWare ------------------------------------ The SAV Interface for NetWare distribution comprises SAVI.NLM, VEEX.NLM, CIDSYNC.UPD, a number of VDL*.* files and also, possibly, *.IDE files. These files are kept up to date via EM Library once you have successfully subscribed to SAV Interface for NetWare using the steps in the section entitled "Subscribing to SAV Interface for NetWare using EM Library". Create the SAV Interface working directory. By default this is SYS:/SOPHOS/SAVI, but this can be changed using the SAV Interface configuration file (refer to the section entitled "Configuring SAV Interface for NetWare"). Copy the contents of SYS:/SOPHOS/SAVIUPD to the SAV Interface working directory (by default SYS:/SOPHOS/SAVI). NB SAVI.NLM and VEEX.NLM can be saved to any folder which is included in your search path. (To find out how to do this, refer to your NetWare documentation.) Loading SAVI.NLM ---------------- A client application must load SAVI.NLM before calling the functions exported by the NLM. A client application needs to load and unload only SAVI.NLM. The other NLM supplied in this package, VEEX.NLM, is automatically loaded and unloaded by SAVI.NLM when necessary. SAVI.NLM can be loaded in the following ways: * Add SAVI.NLM to the autoload list of the client application. To do this, type MODULE SAVI in the linker command file, or whatever is appropriate for the particular linker. Applications built this way must use the import file SAVINW.IMP supplied with the SAVI Developer Toolkit. This is the preferred method of loading SAVI.NLM. This is because it is easy, and the operating system unloads SAVI.NLM automatically when the last application that loaded SAVI.NLM in this way exits. This method of loading SAVI.NLM is demonstrated in the C demo described in the section entitled "SAVI Developer Toolkit". * SAVI.NLM can be loaded dynamically, and the API functions exported by SAVI.NLM can be imported and un-imported dynamically using the CLIB API functions ImportSymbol and UnimportSymbol. In this case, if you run several client applications, you may need to make sure that one of these applications does not try to unload SAVI.NLM while the other applications are running. * SAVI.NLM can be loaded and unloaded from the NetWare console using the console commands LOAD and UNLOAD. Unless you run these commands from the same directory as SAVI.NLM, you must specify the path, for example LOAD SYS:/SOPHOS/SAVI/SAVI or add the directory to your search path. (To find out how to do this, refer to your NetWare documentation.) Updating SAV Interface for NetWare ---------------------------------- SAV Interface for NetWare can perform a "hot update" of VEEX.NLM and/or virus data files. Hot updating is when the virus data (and also, possibly, the Sophos virus engine itself) is updated without needing to stop and restart the SAV Interface client application. This works as follows: when loaded, SAVI.NLM polls the SAV Interface update folder (the default is SYS:/SOPHOS/SAVIUPD) at a specified interval (the default is 5 minutes). When it finds in this folder a version of SAV Interface for NetWare that is different from what is currently running, it performs a hot update, during which it: * deletes the old files * copies the new files from SYS:/SOPHOS/SAVIUPD into SYS:/SOPHOS/SAVI * restarts SAV Interface to load any new virus data and/or updated virus engine (VEEX.NLM). NB When SAVI.NLM itself is updated the new version is not loaded until the client application reloads the API. Configuring SAV Interface for NetWare ------------------------------------- SAV Interface for NetWare can be configured using a configuration file SYS:/ETC/SAVI.CFG. This contains lines of the form "optionname = value", where optionname is not case-sensitive and spaces in optionname may be omitted. Also, underscores in the option name are interpreted as spaces, and leading and trailing spaces are ignored. The options currently supported are as follows. * "SAVI virus data directory" This specifies the SAV Interface working directory. All files comprising SAV Interface for NetWare (SAVI.NLM, VEEX.NLM, CIDSYNC.UPD and VDL*.*) and any IDE files must be placed in this directory. The aliases "SAVI virus data dir" and "SAVI directory" may be used. The default directory is SYS:/SOPHOS/SAVI, although the *.NLM files can alternatively be placed in any directory which is on the search path. * "SAVI temp directory" This specifies which directory Sophos Anti-Virus should use for the contents of archive files that need to be uncompressed in order to be scanned. The aliases "SAVI temp dir", "SAVI tmp directory" and "SAVI tmp dir" may be used. The default directory is SYS:/SOPHOS/SAVI. * "SAVI update dir" This specifies which directory SAV Interface should poll for updates. The aliases "SAVI update directory" and "update directory" may be used. The default directory is SYS:/SOPHOS/SAVIUPD. * "check for update period" This specifies the period (in minutes) for polling the SAV Interface update directory. The default is 5 minutes. SAVI Developer Toolkit ---------------------- The SAVI Developer Toolkit is aimed at application developers wishing to incorporate Sophos virus scanning capability into their products. It includes a user manual and supplement in PDF form as well as release notes and source code for demonstration programs. The SAVI Developer Toolkit can be downloaded by accessing the Sophos website at www.sophos.com and following links to "OEM" and then "Integration". The SAVI Developer Toolkit user manual, SAVI_MEN.PDF, applies to SAV Interface for NetWare as well. SAV Interface for NetWare includes two NLMs: SAVI.NLM and VEEX.NLM. They are coded to CLIB. The two demonstration programs available are as follows. * C demo program for NetWare The source files for building the C demo program (C_DEMO.NLM) are in the directory PRODUCTS\SAVI_DTK\C_DEMO. The file C_DEMO.MCP is a Metrowerks Codewarrior Project file, and can be used for building with CodeWarrior 7 (or with CodeWarrior 8 and PDK 5.0 after converting the project and adding nwsdk\imports\clibpre.o to it). The file MAKEFILE.NW is a makefile that can be used for building with the Watcom compiler. C_DEMO.DEF is a Linker Definition File. SAVINW.IMP is an Import File for the symbols imported from SAVI.NLM. * C++ demo program for NetWare The source files for building the C++ demo program (CPP_DEMO.NLM) are in the folder PRODUCTS\SAVI_DTK\CPP_DEMO\NETWARE. The file CPP_DEMO.MCP is a Metrowerks Codewarrior Project file, and can be used for building with CodeWarrior 7 (or with CodeWarrior 8 and PDK 5.0 after converting the project and adding nwsdk\imports\clibpre.o to it). The file MAKEFILE is a makefile that can be used for building with the Watcom compiler. There is no Linker Definition File or Import File in this directory because CPP_DEMO.NLM loads SAVI.NLM, and the symbols exported by it, dynamically. The file WATCOM.IMP is to be used only when building with Watcom. It contains the names of several symbols that are not available in the Watcom static C library.