readme.txt Compatibility: You can use APC's PowerChute(R) Web Device Manager v2.0.0 to create device groups, sets of links to web-enabled devices, and to monitor any APC Smart-UPS that connects to your network through one of the following types of servers or workstations: - Windows NT(TM) v4.0 servers which use PowerChute plus v5.x for Windows NT. - Windows(R) 95 workstations which use PowerChute plus v5.x for Windows 95. - NetWare(R) servers which use PowerChute plus v4.3.2 or v4.3.3 for NetWare. Note: For PowerChute Web Device Manager to monitor a NetWare server, that server must be running ApcProxy.nlm and Prxy2pcp.nlm in conjunction with PowerChute plus. For PowerChute plus v4.3.3 for Netware, the two nlm files are located in the PowerChute plus installation directory. For PowerChute plus v4.3.2 for Netware, the nlm files are contained in an apcproxy.zip file that must be downloaded, free of charge, from APC's web site. See the Operational Notes section for information on how to download or install the ApcProxy.nlm and Prxy2pcp.nlm files. - SGI(R) IRIX(R), Solaris(R), HP-UX(R), or AIX(R) servers which use PowerChute plus v4.2.3 for UNIX(R). - SCO(R) UNIX servers which use PowerChute plus v4.2.2 for UNIX. PowerChute Web Device Manager also requires that you use one of the following web servers and browsers: - Either a Netscape(R) Enterprise Server(R) (v2.0 through v3.6) or a Microsoft(R) Internet Information Server(R) (IIS) (v3.0 or v4.0) web server on a Windows NT v4.0 operating system (OS). Note: If you encounter problems installing PowerChute Web Device Manager with Microsoft's IIS 4.0, see the procedure for correcting this issue listed in the Operational Notes section below. - Either a Netscape Navigator(R) (v3.x or v4.x) or a Microsoft Internet Explorer(R) (v3.x or v4.x) web browser. Operational Notes: - PowerChute Web Device Manager runs as a Windows NT service called APC PowerChute Web Device Manager. - From a browser, enter a URL with the following syntax: http://{your_server}/devmgr/index.htm Where devmgr is the default URL prefix, a prefix that can be changed during the installation. Also, you can use your server’s IP address or server name to define the {your_server} variable. - The PowerChute Web Device Manager directory is added as an additional document directory, which allows the standard web server administration tools to be used to provide password- protected access to the files. - If you encounter problems installing PowerChute Web Device Manager with IIS v4.0, do one of the following: * Download BackOffice Option Pack 4 from Microsoft's web site (www.microsoft.com). This version of IIS works correctly with the PowerChute Web Device Manager installation. * If you do not want to download Option Pack 4, use the New Virtual Directory Wizard in your current IIS version 4.0 application to add an alias to the PowerChute Web Device Manager directory. Note: Make sure that Allow Read Access, Allow Script Access, and Allow Execute Access are all enabled. - Some Netscape servers are set up so that .exe files will not execute. This allows .exe files to be available on the server for downloading, but prevents the PowerChute Web Device Manager webcgi.exe from running. To solve this problem: 1. Rename the webcgi.exe to webcgi.cgi. 2. Edit the following files to change all references to webcgi.exe to read webcgi.cgi: checkfordevices.tpl index.htm index_collapsed.tpl index_data.tpl index_diag.tpl index_event.tpl index_expanded.tpl index_nodevices.tpl index_page_error.htm index_server_error.tpl index_status.tpl main_discovery.tpl main_server_error.tpl menu_data.tpl menu_devicescollapsed.tpl menu_devicesexpanded.tpl menu_diagnostics.tpl menu_error.tpl menu_event.tpl menu_nodevices.tpl menu_status.tpl - PowerChute Web Device Manager does not support Secure http. - PowerChute Web Device Manager requires some means of name resolution in order to discover/communicate with PowerChute plus servers. This means that there needs to be a DNS table defined with the servers names and IP addresses accessable to the NT server that PowerChute Web Device Manager is installed on. If DNS is not used, the Hosts file on the NT server can be modifed to include the IP address/name of the servers to be monitored. The hosts file resides in: C:\WINNT\system32\drivers\etc - PowerChute Web Device Manager can only monitor a NetWare server when that server uses the ApcProxy.nlm and Prxy2pcp.nlm in conjunction with the PowerChute plus v4.3.2 or v4.3.3 for NetWare application. Follow the instructions given in the ApcProxy.txt file to install the ApcProxy.nlm (which automatically installs the Prxy2pcp.nlm, if that nlm is not already installed on the NetWare server). For PowerChute plus v4.3.3, the ApcProxy.txt, ApcProxy.nlm and Prxy2pcp.nlm files are located in the PowerChute plus installation directory. For PowerChute plus v4.3.2, the ApcProxy.txt, ApcProxy.nlm and Prxy2pcp.nlm files are available in an ApcProxy.zip file. You can download the ApcProxy.zip file, free of charge, from APC’s web site, as follows: 1. Go to http://www.apcc.com/english/prods/index.cfm. 2. Select the Free software upgrades entry under the Software download listing. 3. Register for the free download, or login, if you are already registered. 4. When the Free Software Upgrades page appears, select NetWare from the left-hand column. 5. When the NetWare Upgrades page appears, select the ApcProxy.zip entry from the PowerChute plus with support for NDS listings to download this zip file to your server. 6. Unzip ApcProxy.zip. 7. Use the ApcProxy.txt file to install the ApcProxy.nlm (which automatically installs the Prxy2pcp.nlm, if that nlm is not already installed on the NetWare server). - If you experience trouble connecting to the PowerChute Web Device Manager when using Internet Explorer v4.0 and Netscape Enterprise Server v3.0, make the following adjustments to your Netscape Enterprise Server v3.0 installation: 1. Select Netscape Suite Spot from the Programs menu listing in the Start menu. 2. Select Administration. 3. Log into the Web Server Administration. 4. Select the Web Server installation you want to administer. Note: If you have just installed PowerChute Web Device Manager, you will be prompted to save manual configuration changes. When prompted, select OK, and then select Save and Apply. This will save the changes the PowerChute Web Device Manager made to the Web Servers installation. 5. Select Performance Tuning. 6. Locate the HTTP Persistent Connection Time-out parameter, and enter 0 as the new value. 7. Select OK from the Performance Tuning menu. 8. Click Save and Apply. You will now be able to connect to the Netscape Enterprise Server v3.0 using Internet Explorer v4.0.