Vanilla 4.4 – simplified architecture (post 2/2)

Dear Readers,

Simplified architecture comes also along with a reminder about Vanilla : all the configuration are stored in a single file, vanilla.properties, that you can edit either manually or using vanillapropertyeditor.jar (we updated this software also to reflect the latests changes and the new configuration options). We can do this because we are a software editor, not an agregator of various bundle solutions … this is a key point when it comes to deploy and manage your bi architecture at enterprise level. Since Vanilla v3 (almost 3 years ago), vanilla.properties has been the single document to manage Vanilla server configuration

Configuring a Vanilla server, turning it as a slave server for another Vanilla master server, turning it as a dedicated server for etl, reporting or olap, and even switiching its configuration to support https or any ldap authentification database, is just done in a minute using a text editor … clean architecture lead to clean and simple configuration … just review how it was last time you had to configure your Bi Server to make it part a of farms of bi servers (oups … I understand writing this that most of you can’t do this, for some obvious licences issues)

Have Fun !

Patrick

Advertisements

Vanilla 4.4 – simplified architecture (post 1/2)

Dear Readers,

Let’s start to review Vanilla 4.4 new features with an architecture decision : to make Vanilla more easy to deploy while removing unnecessary pieces of software (or unused one) !

Because of usage of engines like quartz and bonita (both available in Vanilla since the beginning, and both never upgraded for a while), we had to deploy additional catalogs (1 for scheduler and 2 for Bonita), which was not very difficult, but sometimes little boring. The benefits of using those engine was not clear anymore, as we already developped a workflow engine for our Etl, BiGateway, and scheduler was an easy subject to develop.

So, this first post is about what we removed. Sorry … I don’t want to rush into never ending discussion about the “what” and “how” for thoses decisions : we had no problems with quartz and we were using a Bonita v3 engine (which was doing its job), so I can’t comment about the very few concerns we had with Bonita.

Having said that, we also merged the others catalogs (we make the choice of the catalog 100% flexible) into a single one, vanilladata. Leading to cut down the number of catalogs to 3 : vanilla (for security), repository (for portal content and document) and vanilladata (for forms, maps, mdm …).

Have Fun !

Patrick

Announcing Vanilla 4.4

Dear Readers,

It’s 3 weeks now I received the rc5 of Vanilla 4.4, and this new version of your favorite Open Source Platform is promising ! It’s soon 9 months since version 4.2 : our development team has done a lot during this period … and at management level, we have done a lot to resize the development team to provide them with the resources needed to speed up the development and deployment of the next versions

During this period before making 4.4 public (sunday 29th 2013), I will post about the new features, modification of architecture and new components we will provide with 4.4. … so stay connected, you will be delighted by what we are about to provide

Have Fun !
Patrick