First off – congratulations to our friends at Pentaho on making a great strategic acquisition of LucidEra’s ClearView product and embedding it in Pentaho Enterprise Edition. With this, Pentaho will completely replace JPivot as the web UI to view and report OLAP data. Many of us (including OpenI) have lamented about JPivot UI at one point or another, about not providing the desired eye candy effect, so for Pentaho to finally be able to pull this off is a great accomplishment, and hats off to them.

There is, however, one catch — this new UI replacement will NOT be available in the open source version. You have to buy the Enterprise Edition license to get this new UI.

Huh? I hear you say. Well-known BI columnist Seth Grimes questions “Is Pentaho, founded as a “commercial open source” BI vendor, still defined by open source? Pentaho itself seems unsure.” On the other hand, Julian Hyde, a well-respected BI technologist and the project lead of Mondrian, has a compelling rationale for Pentaho to keep this closed source. He says:

If you release a piece of software open source out of sheer, ‘I love the world!’ altruism, you won’t necessarily see much benefit. Pentaho is a for-profit business, and they are savvy about leveraging the benefits of open source software. And let’s not kid ourselves, there are considerable downsides to releasing something open source. Your competitors can pick up the software and incorporate your hard work into their suite. And your customers may decide that the free version is so good that they aren’t going to give you any of their money.

So given this, is it wrong for Pentaho to call itself a “commercial open source” company? In fact, does Pentaho platform even qualify as an open source platform anymore since a major component is only available in the closed source enterprise edition?

The answers, IMHO, are not straightforward.

The key issue is that the origin of open source was not based on making money, but rather based on sharing and leveraging what’s now called the “wisdom of the crowds”. Linus Torvalds uploaded his build of Linux including the source code not so much to charge fees for commercial license and support, but rather so that other like minded engineers will take the code apart, provide feedback, and better yet, improve and add new parts that make it better. And you can say the same about Apache, Mozilla browser, and many other similar well-known open source projects.

But then came people like us — we loved the open source model of developing and distributing software, AND we also wanted to make a living out of it. Initially, it was getting consulting gigs to integrate or customize your open source software, but that doesn’t scale as well. Enter “commercial open source” — first pioneered by the likes of Red Hat, SuSe, etc. to provide commercial license and support of Linux, this intrigued a lot of other open source projects. So soon you had Compiere for ERP, SugarCRM for salesforce automation, etc. etc. and in BI sector, enter Pentaho and Jaspersoft.

And when you are a commercial business, you have to continuously grow (especially if you have taken institutional investments) — so you look for all possible new ways to create new lines of products and services. For closed source commercial enterprise software, this usually resulted in feature and code bloat. And now for commercial open source companies like us, this means creating new “Freemium” models — i.e. what else can we build around the open source software that we can get paid for.

So, as a business — Pentaho has all the valid reasons to justify not open sourcing the new ClearView based UI for OLAP reporting. It developed (acquired) the technology all on its own, it has resources to continually test/improve it (i.e. doesn’t really need community contribution to succeed), plus there is a reasonable market demand — so, why not charge for it and create a sustainable commercial infrastructure?

The argument then is mostly philosophical of whether Pentaho still qualifies as an “open source software”. Some are calling it “Open Core”, probably more aptly.  The only drawback is that is someone, for example us guys at OpenI, want to collaborate/experiment building on Pentaho platform leveraging the ClearView UI features, we can’t do that in an open source model. We will have to become a Pentaho partner, get a restricted license to the code, and whatever we build on top of it, we can’t redistribute it as open source. How much that affects Pentaho, only time will tell.

There was recently a much publicized debate on a similar topic when Chris Anderson’s book “Free” (first published as a Wired column) came out making a strong case for future belonging to products that are built around a free version, and Malcom Gladwell had a reasonable disagreement where he said:

…Anderson is forced to admit that one of his main case studies, YouTube, “has so far failed to make any money for Google.” Why is that? Because of the very principles of Free that Anderson so energetically celebrates. When you let people upload and download as many videos as they want, lots of them will take you up on the offer. That’s the magic of Free psychology: an estimated seventy-five billion videos will be served up by YouTube this year. Although the magic of Free technology means that the cost of serving up each video is “close enough to free to round down,” “close enough to free” multiplied by seventy-five billion is still a very large number.

Ultimately, “Free”, whether it’s OpenI or Pentaho or Gillette razor, can only succeed if the people making the “Free” have a way to get paid, and a way to scale the business profitably. In the absence of that, the people making the “Free” will not survive, and when they are gone, the “Free” product goes away as well. That is also our rationale for providing commercial support and integration for OpenI — we need to generate revenue in order to continue supporting OpenI, and contrary to popular belief, majority of the open source projects can’t succeed on volunteer contributions alone. So, as much as I’d have wanted Pentaho to open source their ClearView UI, I have to admit that making it a part of paid version will benefit the health of their company, and thus increase the chances of them being around to continue supporting the “Free” model. And these things aren’t set in stone? What’s “Closed” today, can become “Open” tomorrow  — as long as there are other new “Freemiums” to offset the switch.

We just released OpenI 2.0-RC2. Our plan is to promote this RC to 2.0 general release in about 2 weeks, barring any new critical fixes. Big thanks to our team who have done a really great job.

There is also a demo available at http://demo.openi.org/openi (login is openi2/openi2)

And you can download it directly from: http://sourceforge.net/project/platformdownload.php?group_id=142873

Among the many new features and bug fixes in this release, a few stand out. First is the support for Attribute Hierarchy feature of Microsoft SQL Server Analysis Services (SSAS) 2005.  Almost all SSAS 2005 installations make use of this feature to get better performance, but prior versions of OpenI had trouble displaying data from OLAP cubes using feature. With RC2, OpenI fully supports this, which should make our SSAS 2005 users very happy. Also, we’d like to hear from those of you trying to use OpenI with SSAS 2008. We haven’t done much testing with SSAS 2008, and could use some help from our community in that regards.

Next, maximizing screen real estate in detailed analysis view has always been a key issue for data analyst users. With RC2, we have made the left navigator collapsible so that users can “stretch” the detail analysis view to the entire width of the screen. We think this is kind of cool, would love to hear your views on this (and other ideas to maximize screen real estate)

Here’re links to more details on the release:

• Release Notes
• Complete list of downloadable files
• Help and Support Forum
• OpenI Wiki

As always, we look forward to hearing your feedback.

best,

Sandeep
Project Lead, OpenI.Org

Gone are the days when Linus Torvalds could post on a bbs about his open source project and the entire world would flock there.  In this day and age, you need Facebook, Twitter, LinkedIn, and who knows what else is coming down the pipeline

So — dear OpenI community — to get things started, we now have a Facebook page.

If you are already on Facebook, please show your support for OpenI by becoming a “fan” of this page, and invite your “friends” to do the same (as long as they dabble in software and can spell “BI” correctly and not confuse it for animal body parts)

Thanks for sharing the love,

Sandeep

Last week during a client meeting to evaluate a new project, a question came up — “If JPivot does all the MDX generation/parsing,   provides the UI components for charts and grahps and tables — what is it that OpenI does that’s different from JPivot?”

A legitimate question indeed.

First off — this is not attempt to trivialize what JPivot does. We wouldn’t be here without JPivot – period.  This post is more about what OpenI does to improve certain JPivot functionality and what OpenI adds in terms of its own features to deliver OpenI as a complete web application.  Here’s my assessment:

• JPivot is a component (JAR file) that you can embed in a J2EE application, OpenI is a complete deployable web application (WAR). JPivot is one of the many components that OpenI uses
• JPivot provides the following key features:
  • UI components for tables and charts using OLAP data, and specifying reporting parameters
  • MDX query generation based on UI events like drill up/down, filter, sort, etc.
  • Representing the results from an OLAP server in an object model
• OpenI makes the following significant improvements to JPivot
  • JPivot is built for open source OLAP server Mondrian. It CAN NOT communicate with Microsoft OLAP server out-of-the-box. OpenI extends JPivot to enable this feature so users can report on data from both Microsoft Analysis Services (all 3 versions – 2000, 2005, and 2008)
  • IMHO – JPivot’s native UI is not so clean and pretty archaic (See screenshots). OpenI improves on this quite a bit (see OpenI screenshots)
• OpenI adds following key features for a complete BI app that are not in JPivot
  • Security – either via its own user management, or by integrating to existing OLAP or custom authentication. Enabling restrictions to analyses based on user permissions
  • Dashboard – Jpivot doesn’t have one, OpenI has complete dashboard creation and management
  • Create/Save reports– Jpivot doesn’t have a way to persist reports. OpenI provides a well defined XML structure (.analysis files) that works as a report definition language (RDL) to save and manage reports. Also supports the notion of public vs private reports
  • Navigation – OpenI provides a full file-explorer like UI to navigate through multiple analyses and manage them in folders
  • Report customization by dragging/dropping attributes to columns, rows, and filters
  • Tabbed view of tables and charts
  • Provides results of an OLAP drillthrough as a text file dump (JPivot can’t), or publish result set to a custom web API
  • Explore data feature – lets you “eyeball” data in a cube without having to create individual reports, very handy for exploratory analysis
  • Concept of “projects” to enable multi-tenant reporting, i.e. same application can serve multiple clients. An on-demand  can leverages this to have multiple client accounts served separately from a single web application instance
  • Administration UI to manage accounts, application, data sources, and many other tasks that you’d otherwise have to do by hand-editing a configuration file

Dear OpenI Community:

I am very happy to announce that we are finally forming an official commercial structure around OpenI to provide license, support, and integration services.

OpenI will still remain fully open source, and this site and the related platform at sourceforge.net will continue to function just the same way they have always functioned. However, for those businesses and organizations that need a commercial support structure and/or need a dedicated team to work on integrating or customizing OpenI for their internal projects or product development, this commercial structure enables us to provide such services.

Plus it enables those of us who have worked on this project since its inception a way to make a living doing what we love.

When we started this open source project back in 2005, we couldn’t have guessed where we are today. We started OpenI as an open source project at my last company Loyalty Matrix, where we built a commercial marketing analtyics product on top of OpenI. Loyalty Matrix was acquired by Responsys in 2007. I am happy to say that the marketing analytics technology we built at Loyalty Matrix found a way to express itself as Responsys’s own analytics product Interact Insight. It was interesting to see the formal structures it requires in a more established company to release a product — valuable lessons that I’ll surely apply in future product releases. It is also great that Responsys will remain a client of OpenI, so that we can advance this technology in a mutually beneficial fashion (and also that OpenI has a few clients from the get go :- ).

OpenI will partner with Codemandu, a software development company in Kathmandu, Nepal that has provided the engineering help for OpenI to-date. Codemandu will help us deliver support and integration work for our clients. So — if you have software projects in business intelligence, reporting, and/or analytics (or know of someone who does) — we are here for you :- ) Basically, if you are an on-demand company that stores transactional data for your customers, we can help you build an on-demand analytics product based on OpenI — something you can private-label and up-sell to your customers.

So, needless to say — next couple of months are going to be crazy, and pretty exciting. Personally, I have a lot of pent-up ideas on making BI more accessible and actionable, and we will be toying around with these ideas in OpenI. And given the nature of open source, these experimentations will happen in public domain — and so you’ll keep seeing some fun new stuff appear on this site.

The BI landscape has definitely evolved since OpenI started back in 2005. Most of the big guys (Busienss Objects, Hyperion, Cognos, SPSS) have been acquired by even bigger guys (SAP, Oracle, IBM). On the open source BI side, Pentaho and JasperSoft have done a remarkable job in leading the sector. Plus there has been a great deal of movement in on-demand BI as well – with Swivel, GoodData, and PivotLink, and also at desktop level with Tableau. We will definitely give our best shot to stand on the shoulders of these giants and raise the bar a bit differently.

I recall Sting (lead singer of The Police, for the benefit of our younger readers) say this in a Rolling Stone interview once when asked about his unique singing voice — something like “Nobody can sing like me — I’m not saying that I have the best voice in Rock ‘n Roll, it’s more like someone can sing better or worse, but they can’t sing exactly like me”

So, this I can say — OpenI will be unique in its approach to BI. Stay tuned..

cheers,

Sandeep
Project Lead, OpenI.Org

Today, we have the release candidate RC1 of OpenI 2.0 available for download. There is also a demo available at http://demo.openi.org/openi (login is openi2/openi2)

We look forward to hearing your feedback on improving this release as we work on further testing of this version to get to general release. Please note that we are changing the license of OpenI to GPL v2 from this release since we feel that GPL is a much better option for us at the moment as it enables us to include other GPL-based components in our distribution.

Here’re some more details on the release:

Files (available at: https://sourceforge.net/project/showfiles.php?group_id=142873&package_id=287874&release_id=680493):

• openi-2.0-RC1-server.zip
  • This is the complete distribution containing all the components necessary to run OpenI with a single click. This is in response to the feedback from our community about simplifying our installation process. We are quite happy with the result, and would love to hear your feedback.
• openi-2.0-RC1-tomcat.zip contains binary build specific to Tomcat 6.0x
• openi-2.0-RC1-jboss.zip contains binary build specific to Jboss 4.2.2 (and can be used for other j2ee servers as well)
• openi-2.0-RC1-src.zip contains full source code to make your own custom builds

This renews my belief in open source — community is everything!

Mariano García Mattío has put together a pretty detailed soup-to-nuts youtube video tutorial for OpenI (in Spanish) along with MySQL, Tomcat, and Mondrian. I guess we should get our act together and publish the English version soon 🙂

Thanks Mariano.

Please support OpenI by voting for OpenI as the “best enterprise project” in the SourceForge.Net Community Choice Awards.

Thanks!

Dear OpenI Community:

I am very happy to announce that today we released the beta version of OpenI 2.0. I want to thank our entire development team for all the hard work they have put in for this release.

Please download it from sourceforge.net and try it out. We look forward to hearing your feedback on improving this release as we work on further testing of this version to get to general release.

There is also a demo available at http://demo.openi.org/openi (login is openi2/openi2)

New features and enhancements in OpenI 2.0 Beta:

• Create New Project: Create new project option is added in the preferences menu that creates a new project by selecting a new template which can be either the duplicate of the current project or a new template. It also allows the users to define the category, project logo etc. for the project being created.
• Multiple Dashboards: an enhancement in the dashboard user interface which allows the user to create multiple project dashboards. this feature is available for the admin user only.
• Purge Files: this feature allows the admin user to purge the older files, the user is prompted the file type ( i.e file extension ) and the date , the files with that type and older than the given date will be purged

New Features from OpenI 2.0 Alpha:

• Completely re-written based on Spring, Java Server Faces and AJAX
• New enhanced UI layout, completely “ajaxified”
• New Drag and Drop Navigator UI to move attributes across rows, columns, and filters
• Enhanced repository system implemented. Now project contents can be deployed anywhere. No need to have project contents within the “webapps” folder of j2ee servers
• Application can be deployed into any J2EE server
• QA feature added to validate the MDX statements for all analyses within a project with a single command
• Manage Feed feature enhancement – now contains split rows feature and better CSV file parser
• Default analysis for project – you can now specify default analysis for a project which is the first analysis displayed to a user immediately after user login
• Customizable chart series color (for non pie type chart only) – Now you can define custom color palettes for chart
• Excel export enhancement – OpenI now generates excel binary file which embeds chart in file itself (previously it contained a web link to the chart, which could result in broken image links)
• Dashboard UI enhancement – Better UI that enables displaying both table and chart view option
• Better File Manager – shows file in explorer style tree
• User/Role management (requires custom build from source) : now users/roles management can be done from OpenI

Plus there are gobs of bug fixes. Check out the release  notes for more details.

Please pass the word around. And as always, we look forward to hearing from you.

cheers,

Sandeep

Sandeep Giri
Project Lead, OpenI.Org