Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. Open three two console windows and cd .  cd to the quickstart directory in each.

  2. 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)

  3. Enter the following, one command line per console:
    1. Console 1: ./bw dirstart  ← Starts ApacheDS ldap directory server for Bedework on port 10389
    2. Console 2: 
      1. FIRST TIME ONLY: ./bw deployConf ← Deploys the platform-dependent configuration files (you only need to do this once)./startjboss  or. Do this only once! Doing it a second time will overwrite any subsequent changes made through the jmx-console where the quickstart is configured.
      2. ./startjboss -debug ← Starts Bedework core services in JBoss on port 8080 (and several others).  Add The -debug to increase the amount of information logged.
      Console 3 (optional*)
      1. 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.

  4. 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
titleMemory settings:

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.
If JBoss has difficulty coming up, try decreasing the heap size, e.g. ./startjboss -heap 512M

...