Table of Contents
      1.0  Operating System Requirements
      2.0  Installing the PowerChute Business Edition Agent
      3.0  Starting the PowerChute Business Edition Agent
      4.0  Stopping the PowerChute Business Edition Agent
      5.0  Uninstalling the PowerChute Business Edition Agent
      6.0  Known Issues with PowerChute Business Edition Agent



1.0 Operating System Requirements
	
      - The PowerChute Business Edition Agent is compatible with Red
      Hat 7.3, Red Hat 8.0, Red Hat 9.0, SuSE 8.0, SuSE 8.1, SuSE 8.2,
      Turbolinux 7.0, and Turbolinux 8.0.
      - The PowerChute Business Edition Agent requires at least 
      Sun Microsystems' JVM 1.4.1.



2.0 Installing the PowerChute Business Edition Agent

    Launch the PowerChute Business Edition for Linux installer by entering
    the absolute path to the pbe_agent_redhat_jvm.bin file. This file can 
    be found in the Linux directory on the CD-ROM.  For example, if the 
    CD-ROM is mounted to /mnt/cdrom,  you would enter the following at the 
    shell prompt...
 
    /mnt/cdrom/Linux/pbe_agent_linux_jvm.bin


    An RPM package of the PowerChute Business Edition Agent for Linux is also 
    available.  This is also found in the Linux directory on the CD-ROM.  
    Install the package using the -i (install) option.  For example, if the 
    CD-ROM is mounted to /mnt/cdrom, you would enter the following at the 
    shell prompt...

    rpm -i /mnt/cdrom/Linux/pbeagent-xxx.i386.rpm
   
    ...where xxx is the version of the product.
    This installs PowerChute Business Edition to the default directory, 
    /opt/APC/PowerchuteBusinessEdition/Agent.

    This rpm also supports the --prefix option to allow you to specify the 
    destination directory.  For example, 

    rpm -i /mnt/cdrom/Linux/pbeagent-xxx.i386.rpm --prefix /PCBE_Agent

    ...would install the PowerChute Business Edition Agent to the /PCBE_Agent 
    directory.

    Once the RPM has been installed, you must configure the Agent for login
    information and the UPS type.  This is handled by running the config.sh script
    located within the PowerChute Business Edition installation directory.  
   
    This utility allows you to create an account name and password, and to configure the
    UPS by entering the communication type and communication port.  After completing the
    configuration, you may start the PowerChute Business Edition Agent.



3.0 Starting the PowerChute Business Edition Agent
   
    After the installation process is completed, the PowerChute Business Edition Agent
    begins running automatically.  The Agent runs automatically each time the 
    operating system is started.  To manually start the PowerChute Business Edition Agent
    after it has been deliberately stopped, you can enter the following command at the 
    shell prompt from anywhere in the file system ...

    /etc/init.d/PBEAgent start



4.0 Stopping the PowerChute Business Edition Agent

    To stop the PowerChute Business Edition Agent when it is running, you can enter the
    following command from anywhere in the file system ...

    /etc/init.d/PBEAgent stop



5.0 Uninstalling the PowerChute Business Edition Agent

    To uninstall the PowerChute Business Edition Agent if you used the .bin executable,
    enter the absolute path to the uninstallPowerChuteBusinessEditionAgent script that is
    located in the directory where the Agent has been installed.  For example, if the Agent
    is installed to /opt/APC/PowerChuteBusinessEdition/Agent directory, enter the following
    command at the shell prompt to uninstall the PowerChute Business Edition Agent ...
  
    /opt/APC/PowerChuteBusinessEdition/Agent/uninstallPowerChuteBusinessEditionAgent


    If you used the rpm to install the PowerChute Business Edition Agent, use the -e (erase)
    rpm option to uninstall Powerchute Business Edition.
    For example:

    rpm -e pbeagent



6.0 Known Issues
    
    6.1 Issue: The product does not perform properly with an APC Back-UPS
               or an APC UPS using Simple Signaling.

        Solution: PowerChute Business Edition requires the 940-0020B cable
                  for UPS communications using Simple Signaling.  If you
                  were using the 940-0023A cable with a previous PowerChute
                  product, you must replace it with the 940-0020B cable when
                  you use PowerChute Business Edition. 

    6.2 Issue: PowerChute Business Edition does not install on a system
               which is using the SJIS locale.

        Solution: The SJIS locale is not supported by PowerChute Business
                  Edition.  The only Japanese locale supported by PowerChute
                  is eucJ.

    6.3 Issue: SNMP Communication cannot be configured.

        Solution: SNMP communication is not available on PowerChute Business
                  Edition Agent for Linux.

    6.4 Issue: PowerChute Business Edition Agents running on Linux may not be
               able to send broadcast messages to Windows systems.  If you
               are using Japanese-language systems, messages sent from Linux
               to Windows may not be readable.

        Solution: These problems are the result of incompatibilities between
                  Windows and Linux, and cannot be resolved through PowerChute.

    6.5 Issue: When the PowerChute Business Edition daemon is stopped, the
              "Monitoring Stopped" event is not recorded in the PowerChute
              Business Edition event log.

        Solution: This is a known issue which will be corrected in a future
                  release of PowerChute.

    6.6 Issue: During the PowerChute Business Edition Agent install using the 
               graphical .bin install file on a RedHat 7.3 Japanese system, 
               dialog boxes display incorrect characters and text.
        
        Solution: Install the PowerChute Business Edition Agent using the RPM file
    
    6.7 Issue: When the --prefix option is used to install the RPM on RedHat 8.x,
               the PowerChute Business Edition Agent does not install to the
               directory specified.

        Solution: There is a known issue with RPM version 4.1x which ships with
                  RedHat 8.0 where the --prefix option does not
                  operate correctly.  If this version of RPM is installed, the
                  PowerChute Business Edition Agent will install to the default
                  directory, /opt/APC/PowerChuteBusinessEdition/Agent, regardless
                  of the directory specified.

    6.8 Issue: When the --prefix option is used to install the RPM on Turbolinux
               8.x, the /opt/APC/PowerChuteBusinessEdition/Agent directory is
               still created.

        Solution: This is an issue that will not affect the performance of
                  PowerChute.  This empty folder is removed upon uninstallation
                  of the PowerChute Business Edition Agent.

    6.9 Issue: During the boot process, the server momentarily pauses and displays
               messages similar to one of the following:
 
               devfs:  devfs_register(): device already registered: "cup"
               rc0: RISCom/8 Board at 0x220 not found.

        Solution: This is an issue that will not affect the performance of 
                  PowerChute.

    6.10 Issue: PowerChute Business Edition Agent installer generates the following
               error on RedHat 9.0:

               Exception in main class "JExpressLoader"

         Solution: The package compat-libstdc++-7.3-2.96.118.i386.rpm is required on
                   the system prior to installing the PowerChute Business Edition
                   Agent.

    6.11 Issue: RPM uninstall reports "error: cannot remove
                /opt/APC/PowerChuteBusinessEditionAgent directory not empty".

         Solution: This is a cosmetic issue that does not affect the performance of
                   Powerchute.  The directory is properly removed during the uninstall.         
