Installing a Standalone KEW instance and building KFS to execute against it involves a few steps:
- Modify kuali-build.properties
- Build the Standalone KEW application
- Install the configuration file
- Build and install the KEW plugin for KFS
- Deploy Standalone KEW into Tomcat
- Update Workflow.AdminUrls application constants
In order to allow for building KFS in a mode where it communicates with a standalone KEW server, some configuration properties will need to be overridden as described in the build process overview. In particular, the
rice.use.standalone.workflow must be set to true. Making these changes also facilities the generation of the standalone KEW configuration file.
In the KFS project, there is an Ant target called
dist-standalone-kew-war. Executing this target will generate a war file in the root of the project named
en-dev.war. The "dev" name on this war file indicates the environment code for the standalone KEW application. This environment will derived from the
build.environment property in your
kuali-build.properties file. This war file can then be deployed into Tomcat once the configuration file and plugin are in place.