Enterprise Webapp Configuration

This page documents how to do a minimal deploy of the onebusaway-enterprise-acta-webapp module introduced by Pull 176. Consider it a preview of things to come!

Basic Steps

• Build the project

// example commands to follow
// this will be from onebusaway repo shortly -- still some issues to sort out
$ git clone git@github.com:camsys/onebusaway-application-modules oba-app-mods
$ git checkout unified
$ mvn clean install 

• Build a Transit Data Federated Bundle using the same version of onebusaway-transit-data-builder as onebusaway-enterprise-acta-webapp. See instructions elsewhere on this wiki.
• deploy onebusaway-transit-data-federation-webapp to tomcat

• edit data-sources to reflect your data sources

// example to follow

• restart tomcat
• verify deployment: go to http://localhost:8080/onebusaway-transit-data-federation-webapp/ and ensure the index page comes up.
• deploy onebusaway-application-webapp to tomcat
• edit data-sources to reflect the path to above

// example to follow

• restart tomcat
• verify deployment: go to http://localhost:8080/onebusaway-api-webapp/api/where/config.json?key=TEST and ensure the api returns with valid JSON
• deploy onebusaway-enterprise-acta-webapp to tomcat
• edit data-sources to reflect the path above and any additional configuration (geocoders, service area, etc)

// example to follow

• restart tomcat
• verify deployment: go to http://localhost:8080/routes and verify the list of routes renders.