
DB Cruiser J2EE Installation Guide:

First of all, please read the LicenseAgreement.txt carefully.

You must agree all the items listed there in order to use DB Cruiser.

Overall, deploying DB Cruiser is exactly same as deploy any J2EE web application (WAR file) to 
a servlet/JSP container or J2EE application server, plus an aditional step to place the DB Cruiser 
configuration file and license file into a folder/directory and add the folder/directory into the 
CLASSPATH of the servlet/JSP container or appliacation server.

NOTE: If you do not agree any of the items listed in the LicenseAgreement.txt, 
      please DO NOT use DB Cruiser.

(1)  Download the newst version of DB Cruiser:

     Make sure you download the newest version of DB Cruiser from:
     http://www.maththinking.com/dbcruiserLicenseAgreement.html

(2)  System Requirements:
     a) JDK 1.2.2 or later, 
     b) Servlet/JSP containers which support Servlet 2.2 and JSP 1.1 or later.
        The Servlet/JSP containers MUST support J2EE web application deployment description.

        NOTE: currently, most Servlet/JSP containers support Servlet 2.2 and JSP 1.1, 
	      the following just some examples: 

              Tomcat 3.x or later, 
              BEA WebLogic Application Server version 5.x or later, 
              iPlanet (now SUN ONE) Web/Application Server 4.x or later, 
              IBM WebSphere Application Server, 
              Oracle Application Server, 
              Resin Application Server, 
              Borland Enterprise Application Server, 
              JRun 3.0 or later, etc. 

              For a list of Servlet/JSP containers, please visit the following site: 
              http://servlets.com/engines/index.html
             
     c) JBDC 2.0 compatible JDBC drivers.

(3)  Remove old version of DB Cruiser:

     If an old version of DB Cruiser installed, remove it COMPLETELY,
     that means. remove the dbcruiser.war and related directory/folder.

     NOTE: for Tomcat, you must remove webapps\dbcruiser\ in order for 
           new version to take effection. For better result, remove work/Catalina/localhost/dbcruiser too.
     
(4)  Unzip dbcruiser-j2ee.zip to a temp directory, say dbcruiser-j2ee/
     There are following files in dbcruiser-j2ee/

     LicenseAgreement.txt   (Please read)
     dbcruiser.war
     dbcruiser_config.xml
     dbcruiser_installation.txt (this file)
     dbcruiser_readme.txt
     Apache_Software_License.txt (Apache Software License, for using xerces Java XML parser)
     EmpBean.java          (a sample JavaBean generated by DB Cruiser)
     EmpBeanTest.java   (a sample program show you how to use generated JavaBean)
     
(5)  Read the dbcruiser_readme.txt carefully.
     
(6)  Deploy the dbcruiser.war to the Servlet/JSP container or J2EE application server.In general, you may move 
     dbcruiser.war to the web application directory of the Servlet/JSP container.

     For examples (only examples):
     Tomcat:       move to TOMCAT_HOME/webapps/
     WebLogic 6.x: move to WEBLOGIC_HOME/wlserver6.x/config/mydomain/applications/ 
     WebLogic 7.x: move to WEBLOGIC_HOME/user_projects/mydomain/applications/
     WebLogic 8.x: move to WEBLOGIC_HOME/user_projects/domains/mydomain/applications/
     WebLogic 9.x: move to WEBLOGIC_HOME/user_projects/domains/mydomain/autodeploy/

     NOTE: 
     (a) Make sure dbcruiser.war is deployed to the Servlet/JSP container.
     (b) If there is previous installed DB Cruiser, please remove it COMPLETELY, i.e. remove the old 
         dbcruiser.war AND the dbcruiser diretory (if any) from the web applications directory.
	 (In Tomcat, if DB Cruiser was installed, make sure dbcruiser directory under webapps is removed)

(7)  (OPTIONAL) Copy the configuration file,  dbcruiser_config.xml, to a folder/directory, and add that folder/directory 
     into the CLASSPATH of your Servlet engine.

     TIP: for Tomcat 4.x or later version users: simply copy dbcruiser_config.xml into TOMCAT_HOME/shared/classes

     ALTERNATIVE: 
     Copy both dbcruiser_config.xml and the license file dbcruiser_license.xml (see step (1) above) to the 
     Servlet/JSP container startup directory (please keep the original):

     For examples:
     Tomcat:       copy to %TOMCAT_HOME%/bin
     WebLogic 6.x: copy to BEA_HOME/wlserver6.x
     WebLogic 7.x: copy to BEA_HOME/user_projects/mydomain/
     WebLogic 8.x: copy to BEA_HOME/user_projects/mydomain/
     WebLogic 9.x: copy to BEA_HOME/user_projects/mydomain/

     if you have a the license file, dbcruiser_license.xml, place it to the same place as dbcruiser_config.xml

(8)  Set CLASSPATH for your JDBC drivers.
     You may set them at your system startup environment, or in the Servlet/JSP container start scripts.
     For Tomcat, it's tomcat.bat or tomcat.sh file, or read the Tomcat documents for details.
     For WebLogic 6.x, it's startWebLogic.cmd or startWebLogic.sh


(9) Start or re-start the Servlet/JSP container.

(10) Access dbcruiser at http://hostname:port/dbcruiser/
     For Tomcat: http://hostname:8080/dbcruiser/
     For WebLogic http://hostname:7001/dbcruiser/

     In general, the URL should be:
     http://hostname:port/dbcruiser/

(11) Access the Administration Panel:
     You may access DB Cruiser Administration via "Admin" menu on the top right of the main page.

     The intial userid and password are "admin" and "password".
     You may modify them in the Administration Pane, or edit dbcruiser_config.xml directly.

     After login, select "Server Configuration", then:
     (1) Modify the user id and password for the adminition panel.
     (2) Add, modify, or delete the connections to fit your specific environment.
     
(12) If the license is expired, renew or puchase licenses at:
     http://www.maththinking.com/serviceProductsLicensing.html
     Or send an email to license@maththinking.com   
     
(13) If problem occured:
     a) Turn on the debug by settting debug="on" in dbcruiser_config_xml
     b) Start/re-statrt the Servlet/JSP container
     c) Run the same procedure until the place/page which problen occuered.
     d) Read the dbcruiser.log to feagure out the problem.
     e) If problem persists, email both dbcruiser_config.xml and dbcruiser.log to:
        support@maththinking.com
    

       
(15) Obtain the up to date DB Cruiser User's Guide at:
     http://www.maththinking.com/dbcruiserDocuments.html
     
     
Copyright @ MathThinking Technologies Inc. All rights reversed.
