...
Preparing Bedework for production involves copying modifying the configuration files , modifying them for your site, and building Bedework. Bedework uses ant for the build and deploy process and a number of property files are used to control that processeither by editing them directly or using the JMX console. It should not be necessary to rebuild Bedework.
The steps are as follows:
- Copy the entire <quickstart>/bedework/config/bwbuild directory ... most typically to the home directory of the user building the system.
- Copy an appropriate configuration directory for your use, e.g. copy bwbuild/jboss-postgresql to bwbuild/myconfig.
- Edit Execute the deployConf target – this is required to set up platform dependent paths in the configuration files installed in the system.
Do this only once: it will overwrite any future changes you make. Aside from editing the database configuration files (step 3), all future configuration changes should be made in the JMX-Console. - Ensure the quickstart works as distributed – it comes with a base set of data. Ensure the clients work and try some of the functions.
- Copy and edit the -ds.xml file for each database. There are five four datasource files - one for each database. Set the <connection-url>, <user-name>, and <password> in each file.
- Add any overrides to bwbuild/myconfig/cal.properties -- copy in text from bwbuild/.defaults/cal.properties as needed (but don't overwrite the org.bedework.global.hibernate.dialect property).
- Copy bwbuild/.defaults/cal.options.xml to bwbuild/myconfig/cal.options.xml; set appropriate values for <tzid> and <systemid>Change the hibernate dialect -- to match the database
- Make remaining changes to your configuration (using the JMX-Console)
- Copy and update the deploy configuration
The pages that follow explain these steps.
...