NMS.TXT Headings: 1.0 Appendix E NMS Smart-Launch Support 1.1 Enabling LAN Inventory Smart-Launch within NMS 1.1.1 Activating the Smart-Launch Feature 1.2 Quick Start Guide 1.0 Appendix E NMS Smart-Launch Support Appendix D provided Btrieve status codes. This appendix provides instructions for enabling SiteMeter smart-launch within NMS. NOTE: In addition to detailed instructions, this appendix also has a quick start guide at the end for experienced users. 1.1 Enabling LAN Inventory Smart-Launch within NMS Many McAfee customers have expressed an interest in utilizing the McAfee network management applications as snap-in applications within the Novell NetWare Management System framework. In response to this request, McAfee has implemented support for NMS smart-launch with five of its currently shipping applications: BrightWorks, LAN Inventory, SiteMeter, NetShield and NetRemote. After following the instructions below, the user will be able to point at an object on an NMS map, select a McAfee command from the NMS Tools menu, and launch the selected McAfee application in a context-sensitive fashion. 1.1.1 Activating the Smart-Launch Feature Use the following procedure to activate the smart-launch feature. 1. Obtain the McAfee NMS Explorer disk. Contact your McAfee representative to obtain a copy of the "McAfee NMS Explorer" Disk. It is available free of charge. 2. Copy all files from the NMS Explorer disk. Two sets of files must be copied from this disk for later use, plus one other file must be created. a. Copy all of the program files (EXE, DLL) to a new directory (e.g., NMS\BDI2NMS) on your NMS console (not into the NMS directories!). NOTE: It is important to NOT copy these files into the NMS\BIN directory as some of the Novell DLLs that are shipped on this disk may not be the latest DLLs available from Novell for NMS. b. Copy the WLAI.OLF file from this disk into the NMS\OLF directory. The McAfee disk includes all .OLF files that are necessary for the smart-launch ready McAfee applications. The .OLF file prefixes match the McAfee product EXE names (e.g., for SiteMeter the relevant files are WLAI.EXE and, therefore, WLAI.OLF). c. Copy any icon in the NMS\ICONS directory to NULL.ICO. When the Novell OLF Introducer (see below) is run it will require a named icon (.ICO file) for each class introduction in case the icon were to show up on an NMS map. Since McAfee does not force one of its icons onto the map, no icons are shipped on this floppy. Any of the icons in that directory may be used as the source icon. 3. Introduce NMS to McAfee. Note that the Novell N-OLFI.EXE file must be in the NMS\BIN directory. a. Use Novell's OLF Introducer to add the McAfee classes to the NMS database. The Introducer takes .OLF files as input. As mentioned above, .OLF files for all smart-launch ready McAfee applications can be found on this disk. It is necessary only to introduce those applications that are installed to NMS. Choose the classes that you need for the McAfee applications that are desired. b. Run the OLF Introducer (N-OLFI.EXE). This latter program has no menu; by default it displays a standard Windows common dialog for opening a file. Browse to find the target McAfee .OLF file (e.g., FUSION.OLF, WLAI.OLF, SITEMETR.OLF, WNR.OLF), as appropriate. c. Run the Introducer once for each .OLF file, specifically for WLAI.OLF. HINT: By default the Introducer has no main window; therefore, any success/failure indications cannot be seen. Invoke N-OLFI.EXE with a -s switch (for "show") to see status messages regarding class introductions. The syntax is as follows: syntax: N-OLFI.EXE -s 4. Explore the NMS databases for nodes and servers. Run the McAfee BDI2NMS.EXE program included on this disk. This program requires no "setup," but it should be copied (as mentioned above) to its own directory. It requires several DLLs that are included on this diskette. These include the NWNETAPI.DLL and several of the N-.DLLs from the NMS BIN directory. When you run BDI2NMS.EXE, you may either run the "Enable All" command or select a specific McAfee product, such as SiteMeter. BDI2NMS.EXE uses the NMS database APIs to search the NMS data for workstations and servers. Smart-launch is enabled for each McAfee product in the following manner: o BrightWorks - smart-launch is enabled for servers only o SiteMeter and LAI - smart-launch is enabled for all workstations and servers o NetRemote - smart-launch is enabled for workstations only NOTE: McAfee COULD have implemented BDI2NMS.EXE so that it would cross-check the existence of inventory data or an installed SiteMeter NLM set before enabling the smart-launch on an individual basis. However, doing so would have made the software slower and would have also required the user to perform the NMS database query far more often than is necessary for normal use. To remove these settings within the NMS database, use the Disable All command to erase them. This software has been tested against NMS 1.15 and 2.0. If the NMS database is large, the enabling exploration may take a while--this is due strictly to the speed of the NMS database callback API. 5. Smart-launch the desired module. o BrightWorks - Select the target PC or server where either EQUIP or an audit have been run, and then select the BWORKS command in the NMS Tools menu. SiteMeter will skip a few steps and invoke the inventory details dialog box for the target node. The network number and NIC address are used as the synchronization key between SiteMeter and NMS. o LAN Inventory - same as SiteMeter. o SiteMeter - Select the server within an NMS map where SiteMeter is installed, and then select the SiteMeter command in the NMS Tools menu. The SiteMeter administration program is launched with an Application Usage Monitor showing information on application usage on that server. o NetRemote - Select the target workstation, and then choose the NetRemote command in the NMS Tools menu. NetRemote will be invoked with the NetRemote options that are configured for the target PC. If the target PC is configured for remote control and has "listen" enabled, then NetRemote will automatically take control of the target PC. Should you have any questions regarding any of these steps or regarding the smart-launch of McAfee applications within NMS, please do not hesitate to contact McAfee Technical Support. 1.2 Quick Start Guide This section offers a brief outline of how to configure McAfee products (LAN Inventory, SiteMeter, and BrightWorks) with NMS. Use the following procedure: 1. NMS must be installed. 2. Install McAfee products into the NMS/BIN directory. 3. Copy all .OLFs from the NMS Explorer diskette to the NMS/OLF directory. 4. Go into Windows and select the Novell-NMS group icon (or wherever the NMS icons are located) and double click on the OLF icon. If there is no icon, select the Run command from the File menu in the Program Manager, browse the NMS/BIN directory for N-OLFI.EXE and choose the OK button. 5. From the NMS/OLF directory, select the .OLF corresponding to the McAfee product you are trying to smart-launch and choose the OK button. 6. Once the OLF is done, select the Run command from the File menu (in the Program Manager) and select BDI2NMS.EXE from drive a: (the NMS Explorer disk) and choose the OK button. 7. Once done, select DISCOVER from the Smart-Launch Menu and select either ALL or the individual McAfee product. 8. From the Novell-NMS group icon, select NMS. Then, from the Main Menu, select File\Open\InternetMap. This displays the map of the network. 9. From the Main Menu, select Tools. This should show the McAfee products that are smart-launchable. NOTE: If you launch LAN Inventory, the View/Inventory Site-Last Updated screen comes up. For NetRemote, it will control the PC selected. For SiteMeter, the usage screen will display. Also note that this procedure works fine for NMS v1.0. For NMS v2.0, NMS looks for a NULL.ICO file during the .OLF step. If there is not NULL.ICO, copy any .ICO file as NULL.ICO.