DB Worker Node Add-on

The DB Worker Node Add-on is a all-in-one-system z2 installation comprising the z2-Environment plus a database (at the moment H2 Database Engine and Apache Derby are supported). The purpose is to have a quick and easy system setup like development or demonstration environments. Of course one can use it also for productive systems if H2 or Derby fulfills your requirements.

The add-on provides wrapper components that launches the actual database during the z2 bootstrap. Since the wrapper is launched on a separate z2 worker node (i.e. the DB Worker node), the database runs in server mode from the web applications point of view (which are running on the web worker node). So in short, all worker nodes connect to the database worker node like they would connect to any other database server.

Using the DB Worker Node Add-on

At first one have to tell the z2-Environment where to find the DB Worker Node Add-on. Usually this is done in the environment module which is used to describe the overall system setup. The file attached to this page is a z2 repository component for this add-on which you can directly add to the environment. Here is the gist of it, pointing to the master branch of the ZFabrik provided repositories:


Secondly the DB worker must be launched in addition to the web worker (and possibly other worker nodes, like a batch job processing job worker). To achieve that, we modify the home layout, that is defined in the environment at environment/ Attached to this page is a modified that launches the DB worker and afterwards the web worker:

home.workers = com.zfabrik.db.environment/h2Worker, environment/webWorker

Note that com.zfabrik.db.environment/h2Worker precedes environment/webWorker so that the DB is up and running before the web worker is started.
To use Derby instead of H2 you simply replace the property home.workers by

home.workers = com.zfabrik.db.environment/derbyWorker, environment/webWorker

The DB worker node is fully transparent to the web applications so there is no need for further changes. As usual you have to make sure that the applications on the web worker are using the corresponding JDBC drivers and database client settings (connection string, user and password etc). Also using migration tools like flyway or other automatic schema generation feature as provided by hibernate for example can be used as usual.

Updated by Henning Blohm about 11 years ago · 14 revisions