1. jumpmanager_2.1.25.4.zip Driver
2. install.txt File Contents

install.txt Driver File Contents (jumpmanager_2.1.25.4.zip)

               Installation of JUMP Manager

     Installation of JUMP Manager is really simple. It consists of a 
communication server, that does all the hard work of communicating with 
managed UPSes.

    Requirements 

 Software requirement for installation is similar as for running JUMP 
Manager package - functional Java runtime support of version 1.2 or higher 
on any platform where Java support exists (Windows, Linux, Unixes, Mac, 
Netware and others). Hardware requirements are very non demanding with 
respect to hard disk space - you need around 5 Mb space for JUMP Manager, 
where you have to take into consideration growing of the databases used to 
store all configuration and management information. With respect to random 
access memory (RAM) server needs between 30 to 40 Mb of FREE RAM for its work.
So the minimal amount of free memory to run JUMP Manager software efficiently, 
which translates for instance for Windows platform to machine with 64 Mb of 
RAM or more (and applies similarly to other platforms). Of course wih larger
number of monitored UPSes memeory requirements grow, so we recommend to get
much more memory for comfortable work (at least 128 or 256 MB and more).
 You probably don't want to use anything less powerfull then Pentium 300 Mhz
processor, but it is not excluded - on such machine with enough RAM memory 
the program has a very decent performance.


    First installation step

    JUMP Manager comes prepackaged in the form of one Java class file
called serversetup.class. The package is installed using previously 
installed Java support (version 1.2 or higher) on the target machine 
by starting installation program (in the simplest case):

      install.bat  (on windows platforms)

      install.unix (on UNIX platforms)

      java -cp . serversetup    (on any other platform)

Each of these commands start an interactive installation procedure that
unpacks all necessary files in the directory specified by user and also
creates startup scripts (on most supported platforms) for starting server 
part of the package as well for uninstallation of the package. Each part 
is prepared to live in several subdirectories of one main directory.

  In case of problems

  If you run into the problem with the above mentioned command, the most 
probable case is that your Java support is not included in the PATH of your 
operating system (simply your system cannot find Java executable). You can 
specify fully qualified name of Java executable to fix it or (better yet) 
include path to Java executable to your PATH configuration (this step is 
platform dependent).

   Remark about new Java 2 platform: JUMP Manager software requires for
it's work presence of  Java version 2. We assume this condition will be not
critical for you as the JUMP Manager software is comming out more then one 
year later then introduction of Java version 2. Any Java runtime version 1.2 
and higher is supported - on Windows platform we recommend new improved 
Java 1.3.


  Second step of installation (Server license scheme)

  JUMP Manager is a commercial product of GE Digital Energy and because of that it is 
protected using a license key scheme. That means, that the server part of 
the software will not start successfully, until user does generate 
proper license key file using information about personal code
(generated uniquely on each machine) and validation code (provided by GE Digital 
Energy after user supplies his personal code). 
  So the next installation step will normally consist in getting that 
validation code for the server from GE Digital Energy and use it to register the 
program when you start JUMP Manager Server. The activation 
code is stored in the file "license.key" which resides in the JUMP 
Manager's directory. 
The user should make a backup copy of this file on diskette or save place
so that he can use it in case he has to reinstall Server software on the
same machine (the code is not depending on the position of installed 
server in the machine file system). 

   If the user later decides to move the server to a different machine (more
powerful, different platform or other reason) or even different machine of 
the same platform, he has to register the program again. It is important to
understand, that licence scheme is derived from IP number of the machine
where JUMP Manager is running (not only, but mainly that parameter). Therefore
in case of use of dynamicaly allocated IP numbers (DHCP) setup should be
modified to ensure stability of IP number for JUMP Manager server, otherwise 
user will run into repeated requests for validation of the product.

   After successfull registration, JUMP Manager server is started and users 
can connect using their Web browsers to configure server for specific needs 
of their organization.
   When the user wants to change the configuration of options for his 
JUMP Manager server, he can start the server application with 
command line switch '-validate' which triggers the appearance of the
validation dialog at the start of server.

    Logging in into the program

  The User uses Web browser without any additional software to 
log on to Web server inside the running JUMP Manager server by using 
a special dedicated port: 6151. There he gets the login page and after 
successful login he can manage UPSes from anywhere without having any
specialised software.

    JUMP Manager uses concept of known users with their own password. On top 
of that it has implemented an access level scheme that enables to configure 
access rights to specific activities on a more detailed level. 
     After installation the program comes predefined with two users:
"supervisor"  and "user". Both user accounts use originally the same password
which is equal to their username (so user for user and supervisor for that most 
important user). The first thing to do after you log into JUMP Manager server 
as supervisor is to go to Global properties panel, to the tab called User and
change password for the supervisor. Default password is too easy to guess and 
gives no protection. It is a good idea to generate at that time new user into 
database where you specify your user identification (for instance for Joe Black
it would be black, full name is of course Joe Black) and you can specify not 
only password but also access level. Actually, specifying correct access level 
is pretty important - 1 stays for highest, 8 for lowest. We suggest you start 
with access level 1 for a new user.

  Similarly if user wants to access WAP server built into JUMP Manager he
has to specify adress in the form:
  http://IP_Address:6151/jw
where jw stands for the name of servlet implementing WAP server.


    Use JUMP Manager server with external SQL database
 
    Use of external SQL database can be useful if your company uses one
SQL engine to store all its bussiness data.
JUMP Manager uses JDBC interface to talk to SQL server so this interface 
has to be available for SQL server to be used. If it is available, you have 
to configure JUMP Manager to use your preferred SQL JDBC interface. 
For configuring SQL interface configuration file SQL.properties comes 
into play - it can be found in the config directory of installed JUMP Manager.
In the directory where JUMP Manager has been installed you will find batch 
file sqlparams.bat (for Win platform, sqlparamsu for Unixes) representing 
interface to command line utility for setting parameters for SQL communication 
using JDBC library. Main idea here is to enable to have scrambled password 
for connection to SQL database in this configuration file - that is why user 
has to use this command line utility sqlparams.bat. In SQL.properties file 
several parameters are supposed to be configured that are used in attempt 
to connect to SQL database using URL of the form:

     Conn = DriverManager.getConnection(
     "jdbc:"+dbtype+"://"+host+":"+dblport+"/"+dbname, sqluser, passwd);

  This is standard form of URL specification for connection to SQL database 
using JDBC interface. Based on the JDBC driver  and SQL server used user 
has to match these parameters to recomendations of the JDBC intercase provider. 
JUMP Manager server contains example SQL.properties file for several JDBC
interfaces to popular SQL engines.
  Rest of the configuration is simple. User has to modify also runman batch 
file to contain reference to jar file containing JDBC driver (not normaly 
supplied with JUMP Manager, but provided by third party). 
  Very last preparation step for successful usage of SQL server with JUMP 
Manager is to actualy create a database for JUMP Manager on SQL server 
(usualy by administrator) with proper rights to be able to create tables 
within database and with rights enabling to connect to this particular 
database using sqluser - passwd pair specified in SQL.properties file. 
Also name of the database created should match parameter dbname from 
SQL.properties file.

  Whole configuration looks a little too complicated, but it looks worse 
then it is. User knowledgable about SQL servers and JDBC interface will be 
able to make it work with his particular setup in short time. 
  Interface of JUMP Manager to actual SQL server used is on purpose 
very generic so that code works without changes on all presently used major 
SQL database engines. Of course GE Digital Energy could not test all possible 
combinations of SQL servers and JDBC drivers, but GE Digital Energy can 
certainly assist you in making your SQL setup to work.

   
   Use JUMP Manager with Secure Web option

   One of the optional modules user can purchase is the inclusion of secure
Web server, enabling use of secure (encrypted) communication between JUMP
Manager Server and Web browser. After including the option into licence
structure of the program there are only two additional steps to perform
in order to make it work for you:
1. Add one line to configuration file Server.properties in the form:
    WWW-sport=6152
   you can use any free UDP port in the machine that is acceptable for
   your system. The configuration is very similar to normal (non-secure)
   Web server specified by very similar line in configuration file:
    WWW-port=6151
   After you include specification for secure Web server, it will run
   alongside normal Web server, so in effect you will have two possibilities
   to connect for JUMP Manager - non-secure standard Web port and also
   different secure Web port.
2. User has to generate certificate used to initiate secure Web connection
   between JUMP Manager secure web server and your Web browser. This 
   certificate is generated using script file called makecert (on Win
   platforms makecert.bat). It will start short dialog asking you to enter 
   name, organization, town etc. to be included into certificate. To generate
   certificate standard Java program (delivered with Java runtime support)
   keytool is used. If batch file doe snot start successfully you have to
   include the path to this program into your path specification or use fully
   qualified name for keytool program. Generated certificate will be saved
   to file JUMPkey in config subdirectory of JUMP manager and is valid for 
   10 years from the day of its generation. You can always generate new
   one by running that batch file again. 
   When user attempts to connect to JUMP Manager secure web server for the
   first time he will be confronted with dialog asking him to accept (or
   deny) use of the generated certificate, because it was issued by user and
   not by generaly recognized certificate authority (like VeriSign). We
   recommend to accept the certificate either for one time connection or
   for longer period of time.
That is all to it to make module of secure Web server active within JUMP
Manager. After these steps are performed (and option is included in actual
licence string) secure Web server is automatically started when JUMP
Manager is started.


   Platform specific installation notes

    Windows:

    The installation creates start scripts on Windows platforms so that you
can easily start JUMP Manager Server.
It also creates shortcuts into a special directory in the user's Program 
folder so that user can easily start both programs in standard Windows way. 
The installation program creates also a shortcut for uninstallation of 
each part of software package.
A nice feature of the installation is, that it automatically discovers place
where user's standard Java support resides and includes it into generated
startup scripts.

     Unix:

   For the UNIX platform we provide generic startup scripts for both 
programs called runmanu and runclientu. From their content it is clear 
which additional Java libraries are necessary for each program. On a 
Unix system standard classes are usually found thanks to CLASSPATH 
environmental variable being already set - so we simply append it to
required new classes that live in install_directory/classes.

   You can start the server part of the package by giving on command line
(in the main installation directory for the whole package)
   runmanu
That starts non graphics part of the package together with built in Web
server.

  Sometimes an installation doesn't change execution flag on the described
scripts starting various parts of the package. If this happens, please 
make those scripts executable and report it as a bug to service@imv.com.


                                                   GE Digital Energy