Table of contents
Community Build Framework (CBF) is an ant build.xml file script and alternate way to setup and deploy Pentaho based applications. Focused on a multi-project/ multi-environment scenario, here are the main characteristics:
- Ability to switch from totally different projects on the fly
- Supports multiple environments (eg: development, production, worker1, worker2...)
- No changes to the original files that could get overwritten in a upgrade
- Supports multiple platform versions
- Support for jboss and tomcat (the latest only for platform >= 1.7)
- Simplifies version upgrades
- Support all kinds of different customization in different projects, from using a different databases to different security types.
- Supports patches to the source code for fine-grain customization
- Supports deploy to local/remote machines
- OS independent
Project pentaho already has a good dev_build.xml ant script, but it wasn't enough for my needs, since I needed to change the svn sources in order to configure a solution. So I built my own structure, and its like this:
Directory layout and code checkout
pentaho/* directories are cheched out from svn, and for me are read-only. Feel free to use any svn client you want; I usually work in linux, or on a windows machine with cygwin, so I use the original client. I checked out the sources with:
If you are under a proxy you can use http:// instead of svn:// . I'm currently using version 1.7 (this one, or later, is required for tomcat support)
target-/* directories are the ones generated by the build script. I don't use target-solutions at all (honestly, I'm not sure what this are for, cause they seem a copy of pentaho-solutions. Guess the point is to pick target* and copy it, w/o any other dependencies, to the desired machine). target-build is the temporary build directory. Since we may need to patch the pentaho source, CBF will make an entire copy of pentaho/ to target-build and patch the later, leaving the original source intact.
This leaves us with the "project-client" directory. As mentioned before, the idea is not write anything under pentaho* directories, so all my changes go to this directory. Here is an example structure in more detail:
All this is created manually according to the specific project needs.
Note to CBF version 1 users
Note the absence of a patched override.properties file; All the needed information is in the properties files under the config directory
The idea is very simple: All changes that would normally go to pentaho/* are placed under "patches" directory. CBF ant script just picks them and copies the files to the top level directory. It's not recommended to patch anything under pentaho/*; sources changes are patched in to target-build/* and all other changes are made by patching the final directory, target-preconfiguredinstal (for jboss) or target-preconfiguredinstall-tomcat (for tomcat)
Tip: Making the solution ready to both jboss and tomcat
One very simple way to make the project running in both jboss and tomcat with no relevant maintenance is to make a symbolic from target-preconfiguredinstall/server/default/deploy/pentaho.war to target-preconfiguredinstall-tomcat/webapps/pentaho and the same to pentaho-style.war
For the example scenario, those were the files I had to change. I had to change some jboss's config files just because I had to change a port that was unavailable; added my datasource (client-ds.xml) and changed the jboss-web.xml and web.xml to register it; changed all other ds's cause I'm using postgresql instead of hsql; added the jdbc lib; changed the security system from memory to jdbc.
This is scalable. Just change files there and they will be copied to the destination target. CBF does not allow (yet) to remove files from target to destination, but I also don't think that's a relevant issue.
Tip: Upgrading Jars
Sometimes there's the need to upgrade some Jar version. A very simple way to do so is to patch 2 files: myJar-oldversion.jar and myJar-newVersion.jar where the first one is an empty zip file that will overwrite the original one
The solution is under project-client/solution, and our build.properties points to this dir. For now, I just copied pentaho-solutions to here, and will start from there by adding new solutions and playing a bit.
Tip: Maintaining system files
Tip: Since project-client/solution/system is a generally untouched directory, it's easier to maintain the svn info there. Just copying the directory from pentaho-solutions/system or making a
will allow svn updates later. The same approach can be used for admin, samples and test directories.
The main config file is in config/build.properties; specific environment configurations can then be set in config/build-env.properties . Here's an example file:
I use this to set the default options and put my specific information in my environment configuration
To extend customization to a greater extent, I've implemented dynamic filter tokens for changeable attributes, such as database locations and passwords. Whenever CDF finds a text file with a string of the form @@DB_LOCATION@@ that token will be replaced at compile time.
CBF execution and available targets
Building and executing
After all this environment is correctly set up, CBF is ready to be executed. ant executable needs to be on the path and the properties project and optionally env need to be passed. If no env property is passed only build.properties will be used.
Here are the available targets. The description speaks for itself:
To clean, compile and run pentaho all that's needed is, for example:
Just by passing different properties we can immediately build and run a totally different project, in a different platform version or different application server. With the right properties and tokens, we can instantly deploy a solution in a remote server.
Despite the property deploy.mode, only the rsync method is currently supported. It's by far the most appropriate way to handle my kind of requirements, but a lot more modes can be implemented, like copy, scp or even ftp transfer.
With the appropriate JAVA_OPTS parameters, all that's needed to debug the platform is do a socket attach using your favorite IDE.
I don't have any questions. Do you?
Major changes; Introduced different configurations and deployments; dynamic tokens; deploys