Build "server-side" installation of Kepler
Sounds like the Kepler webservice uses a snapshot (jar?) of Kepler to execute workflows via the webservice.
For sanparks/reporting we need to be able to build a version of kepler that includes the WRP suite features.
Maybe this is straightforward already - but I wanted to have a big for it to make sure we've addressed it
#1 Updated by Chad Berkley over 13 years ago
Jing and I are working on figuring out how to deploy kepler for the webservice. The jars for kepler can easily be created with the 'ant change-to -Dsuite=wrp jar' which will create a jar for each module in the suite. We just need to figure out exactly how the jars need to be arranged for the webservice to be able to access the API. For normal kepler runs, the runner and loader build the classpath and set the paths. These steps will probably need to be done in the servlet initialization or whatever a similar step is in the webservice environment that will be used.
#2 Updated by Chad Berkley about 13 years ago
This now works. The KeplerConfigurationApplication (a non-gui implementation of kepler that also loads a full configuration with the cache, object manager, et al) now works. From the command line, it can be executed with this command:
java -classpath build-area/lib/ant.jar:kepler.jar org.kepler.build.runner.Kepler -server -repository=keplerRepository -runwf -nogui somekar.kar
or by using the kepler.sh script generated by the 'ant startup-script' command:
./kepler.sh -server -repository=keplerRepository -runwf -nogui somekar.kar
or by using the ant build:
ant run-workflow-no-gui-server -Dworkflow=somekar.kar
Note that for this to work, Kepler must be installed and left in its normal directory structure. the kepler.jar file referred to in the first command is generated by the 'ant startup-script' command and resides in the kepler root directory (where it is assumed that this call will be made).
Marking this bug as closed.