Java OLAP Interface (JOLAP) is dead?

It looks like JOLAP is dead. The final specification has been approved on June 15th 2004. However, to this day, except for Mondrian and Xelopes, I know of no implementation of JOLAP. According this this thread, Oracle has no intention of ever supporting JOLAP.

On the other hand, Oracle doesn’t support nor does it plan to support MDX or derived technologies such as XML for Analysis (XMLA) and more recent specifications. But, you can get MDX support in Mondrian and in SQL Server standard edition or better. I am pretty sure IBM supports MDX and maybe XMLA, but with recent changes in their OLAP product line, I must admit I’m a bit confused.

This leaves us with no cross-platform OLAP query standard. After all these failed attempts, it is very depressing.

Update: Daniel Guerrero from Ideasoft correctly pointed out to be that the current JOLAP spec. has not been published yet as a Final Release, but only as a Final Draft. The Final Draft has been approved in June 2004 (though IBM abstained), and normally, the Final Draft ought to be a Final Release by now, but this didn’t happen. The difference is significant because, right now, the JOLAP license, granted by Hyperion, is for evaluation purposes only. This means you can’t go out and implement JOLAP without risking legal troubles. We can imagine many scenarios on what is happening, but I’ll vote for an Intellectual Property issue.

2 thoughts on “Java OLAP Interface (JOLAP) is dead?”

  1. Hi,

    I’m not very familiar with Oracle business Intelligence Suite. I’m an Oracle DBA using cognos Business Intelligence Suite… But i did some searches on some oracle Internal sites (metalink, otn…) and the only thing i found is about the JSR-0..69. Oracle was talking about integrating JOLAP in their Oracle 9i OLAP… However i didn’t find any occurence of this word “JOLAP” in the Oracle 10g. I even think that this White paper is out of date šŸ™‚

    I don’t think that JOLAP is dead ( like MDAPI : Several years ago the OLAP Council created MDAPI, an open API for multidimensional databases and OLAP applications. This API never gained acceptance in the market place ) because it’s used by Mandrian which was recently integrated to the Pentaho OLAP Server. This article is in french


    http://www.progilibre.com/Debut-de-consolidation-dans-le-decisionnel-en-open-source-Mondrian-OLAP-Server-rejoint-le-projet-Pentaho_a227.html

    and which is gaining a lot of interest by the industry.

    Personnaly i think there is a serious war between Oracle, IBM…and Microsoft in this field. That’s why there’ll probably never be a Cross-Platform OLAP query Standard šŸ™

    Abdel.

  2. JSR-69 spec doesn’t exist (it is only for evaluation).

    According to JCP 2.1 (the process used for JSR-69) the Specification Final Release will be posted after Final Approval Ballot.

    This never happends. So, the only version of the specification is the last DRAFT, according to it’s license, it only for evaluation.

    I asked people working on JCP but I have no answers.

    Daniel.

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax