Start Bedework
- Open three two console windows and cd . cd to the quickstart directory in each.
- For each console, set JAVA_HOME environment variable. For example:
- Linux: export JAVA_HOME=/usr/java/jdk1.7.0_51
- Windows: set JAVA_HOME=C:\Program Files\Java\jdk1.7.0_51
- Mac OS X: export JAVA_HOME=$(/usr/libexec/java_home)
- Enter the following, one command line per console:
- Console 1: ./bw -quickstart dirstart ← Starts ApacheDS ldap directory server for Bedework on port 10389
- Console 2:
- FIRST TIME ONLY: ./bw -quickstart deployConf ← Deploys the platform-dependent configuration files. Do this only once! Doing it a second time will overwrite any subsequent changes made through the jmx-console where the quickstart is configured.
- ./startjboss or ./startjboss -debug ← Starts Bedework core services in JBoss on port 8080 (and several others). Add The -debug to increase the amount of information logged.
- flag places debugging information in the log. You will want to remove this flag at the point of going production - but having it on is helpful when you begin.
- Optionally, open a third console and enter: ./runcache ← Starts the webcache on port 7070. (This service is for production caching of data feeds. It is not required for testing.)
Info | ||
---|---|---|
| ||
JVM settings can be passed as parameters to the startjboss script. Enter "startjboss -usage" or see "Reviewing JVM parameters" for more information. If you have the memory, try increasing the heap size for better performance, e.g. ./startjboss -heap 2G. |
Tip | ||
---|---|---|
| ||
Throughout this manual, you can replace all commands of the form “./command” with “command” or “command.bat”. For example, to start Bedework's directory server, enter: “bw -quickstart dirstart”, and to start Bedework enter "startjboss". |
...