/ - Diff - Metacat - Ecoinformatics Redmine

     Author: Chad Berkley
     Date: 3/5/2007
     This file covers deploying the gwt created ajax code and servlet to a non-google version of tomcat.  This allows for the installation of the servlet(s) along side a normal metacat installation.
     This file covers deploying the gwt created ajax code and servlet to a non-google
     version of tomcat.  This allows for the installation of the servlet(s) along
     side a normal metacat installation.  This file assumes you've already done
     the steps highlighted in the README file.
 ) Create a servlet on your tomcat instance called "rpc".  This is a simple servlet that just runs the gogle remote procedure call (rpc) services.  Use the web.xml file from the ./tomcat/webapps/ROOT/WEB-INF directory.  You'll also need to copy all of the gwt jar files from your gwt installation as well as all of the jar files in ./lib
 ) Create a servlet on your tomcat instance called "rpc".  This is a simple
     servlet that just runs the google remote procedure call (rpc) services.  Use
     the web.xml file from the ./tomcat/webapps/ROOT/WEB-INF directory.  You'll
     also need to copy all of the gwt jar files from your gwt installation as well
     as all of the jar files in ./lib.  Use the gwt-user.jar and gwt-dev.jar from
     metacat/lib.  If you use the ones from the gwt distro, tomcat won't load them
     due to the presence of javax.servlet.Servlet.
 ) copy ./src/org/kepler/web/service/KeplerServiceServlet.java to metacat/src/org/kepler/web/service/ and update the KeplerServiceServlet.java file with the correct url to your metacat servlet (line 6 in the code).
 ) copy ./src/org/kepler/web/service/KeplerServiceServlet.java to
     metacat/src/org/kepler/web/service/ and update the KeplerServiceServlet.java
     Edit the file with the correct url to your metacat servlet (line 6 in the code).
     Make sure the moduleRelativeURL exactly matches the url that will be browsed
     to!  I.E. Don't use "localhost" if you intend to browse to an actual machine
     name.  This confuses the RPC and will cause problems.
 ) run 'ant package' (from the ajax dir) and copy the newly created kepler-web.jar file to metacat/lib/
 ) run 'ant package' (from the ajax dir) and copy the newly created
     kepler-web.jar file to metacat/lib/.  Make sure you updated the hard coded
     servlet paths in the java code before doing this.
 ) run 'ant install' from your metacat directory
 ) make sure tomcat restarts
 ) run ./KeplerClient-compile and copy the contents of the www directory to some web accessible location, then browse to the KeplerClient.html file and the javascript should run.  Note that you may need to update any hard coded servlet paths in the ajax code before copying the www files to the web location.
 ) run ./KeplerClient-compile and copy the contents of the www directory
     to some web accessible location, then browse to the KeplerClient.html file
     and the javascript should run.
     --------------------------------
     If this doesn't work for some reason, keep in mind the main things you need.  They are:
     If this doesn't work for some reason, keep in mind the main things you need.
     They are:
     * the rpc servlet
     * the KeplerServiceServlet servlet.  In the web.xml file, I have called this 'gwt' so the address will be: http://server:8080/servletpath/gwt
     * the compile javascript (ajax) code
     * the KeplerServiceServlet servlet.  In the web.xml file, I have called this
       'gwt' so the address will be: http://server:8080/servletpath/gwt
     * the compiled javascript (ajax) code
     * hard coded server/servlet paths correctly changed
     * all jar files accessible to tomcat

     #!/bin/sh
     APPDIR=`dirname $0`;
     GWT=/Users/berkley/tools/gwt
     GWT=/home/berkley/tools/gwt
     CLASSPATH="$APPDIR/src:$APPDIR/bin:$GWT/gwt-user.jar:$GWT/gwt-dev.jar:$APPDIR/lib/client.jar:$APPDIR/lib/utilities.jar:$APPDIR/lib/xalan.jar:$APPDIR/lib/xml-apis.jar"
     java -XstartOnFirstThread -cp $CLASSPATH com.google.gwt.dev.GWTShell -out "$APPDIR/www" "$@" org.kepler.web.KeplerClient/KeplerClient.html;
     java -cp $CLASSPATH com.google.gwt.dev.GWTShell -out "$APPDIR/www" "$@" org.kepler.web.KeplerClient/KeplerClient.html;

     #!/bin/sh
     APPDIR=`dirname $0`;
     GWT=/Users/berkley/tools/gwt
     GWT=/home/berkley/tools/gwt
     CLASSPATH="$APPDIR/src:$APPDIR/bin:$GWT/gwt-user.jar:$GWT/gwt-dev.jar:$APPDIR/lib/client.jar:$APPDIR/lib/utilities.jar:$APPDIR/lib/xalan.jar:$APPDIR/lib/xml-apis.jar"
     java -XstartOnFirstThread -cp $CLASSPATH com.google.gwt.dev.GWTCompiler -out "$APPDIR/www" "$@" org.kepler.web.KeplerClient;
     java -cp $CLASSPATH com.google.gwt.dev.GWTCompiler -out "$APPDIR/www" "$@" org.kepler.web.KeplerClient;

     public class KeplerServiceServlet extends RemoteServiceServlet implements KeplerService
+    {
       private String url = "http://localhost:8080/kepler/metacat";
       private String url = "http://library.kepler-project.org/kepler/metacat";
       /**
        * takes in a query string and a sessionid and returns a resultset

           // Use a module-relative URLs to ensure that this client code can find
           // its way home, even when the URL changes (as might happen when you
           // deploy this as a webapp under an external servlet container).
           String moduleRelativeURL = GWT.getModuleBaseURL() + "kepler";
           moduleRelativeURL = "http://offhegoes.kicks-ass.net:8080/kepler/gwt";
           //String moduleRelativeURL = GWT.getModuleBaseURL() + "kepler";
     //      String moduleRelativeURL = "http://library.kepler-project.org/kepler/gwt";
           String moduleRelativeURL = "http://dana:8080/kepler/gwt";
           System.out.println("connection url: " + moduleRelativeURL);
           target.setServiceEntryPoint(moduleRelativeURL);
+        }

           setText(title);
           Frame iframe = new Frame("http://offhegoes.kicks-ass.net:8080/kepler/metacat?action=read&docid=" + docid + "&qformat=kepler");
           Frame iframe = new Frame("http://library.kepler-project.org/kepler/metacat?action=read&docid=" + docid + "&qformat=kepler");
           Button closeButton = new Button("Close", this);
           /*HTML msg = new HTML(
             "<center>This is an example of a standard dialog box component.<br>  "

     Setup
     -----
 ) Make sure you have the google web toolkit installed.  You can get it from http://code.google.com/webtoolkit/.  From now on, I will refer to the google web toolkit directory as the "gwt" directory.
 ) Make a symbolic link in the gwt directory so that gwt-dev.jar -> gwt-dev-xxx.jar where xxx is either "mac", "linux" or "windows".  This just makes the scripting easier to deal with.
 ) Edit the KeplerClient-shell file and make sure $GWT points to your gwt installation.  Do the same for KeplerClient-compile
 ) Make sure you have the google web toolkit installed.  You can get it from
     http://code.google.com/webtoolkit/.  From now on, I will refer to the google
     web toolkit directory as the "gwt" directory.
 ) Make a symbolic link in the gwt directory so that
     gwt-dev.jar -> gwt-dev-xxx.jar where xxx is either "mac", "linux" or "windows".
     This just makes the scripting easier to deal with.
 ) Edit the KeplerClient-shell file and make sure $GWT points to your
     gwt installation.  Do the same for KeplerClient-compile
     Building
     --------
     Run the KeplerClient-shell script.  Upon successful compilation, you should see two windows open.  One is the tomcat server shell, the other is a test browser where you will see the web page.
     Run the KeplerClient-shell script.  Upon successful compilation, you should
     see two windows open.  One is the tomcat server shell, the other is a test
     browser where you will see the web page.
     Testing
     -------
     You can use the -shell file for incremental building and testing.  If you want to "clean" the project, you can use the ant build.xml file.  The build file really is not needed.
     You can use the -shell file for incremental building and testing.  If you want
     to "clean" the project, you can use the ant build.xml file.  The build file
     really is not needed.
     Installation/Deployment
     -----------------------
     Once you have a working product and you want to deploy to a normal instance of Tomcat, you can first test that your code works under a normal browser by clicking the "compile/test" button on the google browser.  This will open your page in whatever your default browswer is.  Your server side code is still running on the google tomcat instance (port 8888).  If you want to deploy the servlet and client side code to another instance of Tomcat, follow the instructions in the INSTALL file.
     Once you have a working product and you want to deploy to a normal instance
     of Tomcat, you can first test that your code works under a normal browser by
     clicking the "compile/test" button on the google browser.  This will open your
     page in whatever your default browswer is.  Your server side code is still
     running on the google tomcat instance (port 8888).  If you want to deploy the
     servlet and client side code to another instance of Tomcat, follow the
     instructions in the INSTALL file.
     A note on using different OSs
     -----------------------------
     There are a few differences when moving between windows, linux and osx.  On OSX, the -XstartOnFirstThread flag must be set in the KeplerClient-shell and KeplerClient-compile scripts.  Also, make sure you make a symlink for the gwt-dev jar file.  For some reason, google renames this jar depending on what system you download gwt for.
     There are a few differences when moving between windows, linux and osx.
     On OSX, the -XstartOnFirstThread flag must be set in the KeplerClient-shell
     and KeplerClient-compile scripts.  Also, make sure you make a symlink for the
     gwt-dev jar file.  For some reason, google renames this jar depending on what
     system you download gwt for.

Project

General

Profile

Metacat

Revision 3195

Added by berkley almost 18 years ago