[kepler-users] Kepler Web Service "Footprint"

[Amrhein, James S. (GSFC-610.2)[ADNET SYSTEMS INC]]

What is the smallest footprint can I get Kepler/Web service  to be on a deployed server? Currently deployed  it's ~ 2.0 gigs.  I'm asking for suggestions where I can prune extra items, or at least make this process easier to use with CVS. I'm currently archiving a zipped version of webservice directory in CVS.  So here's what I'm doing so far:

My current "build procedure" is the following:
   (From build-area) :
                       ant compile
                       ant jar
                       cp ../mymodules/target/mymodule.jar
../webservice/KeplerWebService/lib/kepler/
                       ant package -Dname=keplerPkg

What I end up with is :

-rw-r--r--  1 me users 834M Jan 13 19:28 keplerPkg.zip

Which gets deployed to a baseline server.

Once it's unpackaged, on the server, the following steps are executed:

1. webservice/KeplerWebService/conf/wfWSProps.properties is updated
with the proper information
2. From webservice/KeplerWebService/
     ant compile/generate.service and deployToTomcat.


Are there any tricks to making this deployment smaller? One approach I
tried, was to build Kepler once (like I described)
and any updates I made to my actors. I would deploy the actors to
webservice and zip/copy the webservice directory. That turned out to
still be 125 mbs. Smaller, but it felt clumsy.  Any better approaches?

Thanks,
       JSA