STARTING BORA:

Once you eliminate the recurring problem of multiple postmasters clashing on the same port, you can cleanly boot Bora Builder's postgreSQL instance by logging on as DBA and executing:

on the command line. That will boot the postgreSQL database.

Now the database is up, you can start Bora by logging on as Bora Admin in another window, and execute:

'bora.sh' will attempt to see if the postmaster is up (although it cannot tell if the correct one is up; that's why multiple postmasters need to be resolved by hand), and will complain if none found in the process table.

It then will boot Apache Web Server that comes in the Bora Builder bundle, and then it will boot Tomcat. Apache listens on port 8080, and Tomcat uses ports 8007 and 8009. The multiple server instances problem of postgreSQL we just dealt with might perfectly hit us again for Apache now. It is not uncommon for some Linux packages to install Apache, very likely on port 80. If you already happen to have an Apache server in the system and want to merge the two, we strongly encourage you to choose the one came with the Bora Builder and get rid of the other. And finally, you may want to change the Bora Builder Apache port address from 8080 to standard web server port 80. That would be done in:

Once Bora is started via 'bora.sh start', keep an eye on the log. At this point the log should look something like:

    
Using classpath: /usr/local/bora/jars/bora.jar:/usr/local/bora/jars/xerces.jar:
/usr/local/bora/tomcat/lib/ant.jar:/usr/local/bora/tomcat/lib/jasper.jar:
/usr/local/bora/tomcat/lib/jaxp.jar:/usr/local/bora/tomcat/lib/parser.jar:
/usr/local/bora/tomcat/lib/servlet.jar:/usr/local/bora/tomcat/lib/test:
/usr/local/bora/tomcat/lib/webserver.jar
Starting tomcat. Check logs/tomcat.log for error messages
/usr/local/bora/apache/bin/apachectl start: httpd started

As you may have noticed, only the Apache server is up; Bora engine will not get instantiated immediately. Bora, as a servlet, will be loaded on-demand. Hence it should be requested at least once to come into existence. A request by a browser for the URL:

will do the job. Keep an eye on Bora log. You should see messages about loading service libraries, etc.:

I    1001    [DataMgr.jp:119]    Creating data channel: home=/usr/local/bora/t..
I    1001    [NativeChn.jp:46]    Loading library ntvchn
I    1002    [NativeChn.jp:64]    Initializing NativeChn
I    1003    [NativeChn.jp:64]    Initializing NativeChn
I    1001    [ChannelMgr.jp:63]    Worker thread(s) for the channel type=2 are..
I    1001    [DataMgr.jp:138]    Instantiating Data Manager
W    1001    [Template.jp:118]    Loading template "/usr/local/bora/tomcat/we.."
I    1004    [DataMgr.jp:138]    Instantiating Data Manager

Home page URL above does not interact with the database, and is not a good indicator for 'up' status. For at least one database interactivity, log on to the system using the login page:

with username 'admin' and password 'admin'.

Any line on the log that starts with an 'E' as the first character indicates an error. 'W' is a warning, and 'I' is an informational message. As guessed by now, the first column of the log indicates severity. You must not have any errors at this point. If you do, don't bother proceeding any further. Whatever the error is it must be fixed first. It is likely a problem of finding service libraries, or permission troubles, or not finding the postgreSQL server, etc.

For your information, second column of the log is the thread Id, the third one is the source of the message (which is no use to you), and the last is the message itself.

SHUTTING DOWN:

If you decide to shut down Bora, execute the command:

as Bora admin. You may shut down the database with an interrupt signal as a DBA, or Ctrl-C (in most terminal settings) on the postgres window.

Bora always needs the database in place; therefore the boot sequence is always postgreSQL first, and then Bora. While the shutdown sequence is just the reverse; 'bora.sh shutdown' first, then the database.

Of course you may be using the database for other purposes as well, in which case you may never bring it down.