IcCube: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
→‎top: bold
not convinced it is notable, but at least match brackets etc.
Line 6: Line 6:
|latest_release_date = {{release date|2021|03|12}}
|latest_release_date = {{release date|2021|03|12}}
|operating_system = [[Cross-platform]] ([[JVM]])
|operating_system = [[Cross-platform]] ([[JVM]])
|genre = [[Online analytical processing]]]
|genre = [[Online analytical processing]]
|website = {{URL |www.iccube.com}}
|website = {{URL |www.iccube.com}}
}}
}}


'''icCube''' is a company founded in Switzerland that provides [[business intelligence]] software of the same name. The software can be fully embedded, can be hosted in a managed environment or installed locally, on premises.
'''icCube''' is a company founded in Switzerland that provides [[business intelligence]] (BI) software of the same name. The software can be fully embedded, can be hosted in a managed environment or installed in a customer's machine on premises.


The BI tool allows end-users to create or edit dashboards themselves and is capable of processing data from multiple sources in real-time. The software distinguishes itself by making the dashboards, the dashboard builder, the schema/cube builder and the server monitoring application accessible from a browser only. No software has to be installed at the device of the end-user.
The BI tool allows end-users to create or edit dashboards themselves and is capable of processing data from multiple sources in real-time. The software makes the dashboards, the dashboard builder, the schema/cube builder and the server monitoring application accessible from a web browser only. No software has to be installed at the device of the end-user.


Next to the browser-based dashboard builder, data can be accessed by running queries directly on the [[OLAP cube]] using MDX, SQL or R.
Next to the browser-based dashboard builder, data can be accessed by running queries directly on the [[OLAP cube]] using MDX, SQL or R.
Line 19: Line 19:
icCube sells an [[online analytical processing]] (OLAP) server.
icCube sells an [[online analytical processing]] (OLAP) server.


Starting in June 2010 with its first public community version (0.9.2). Since then, the company has released new versions multiple times per year.
In June 2010 its first public community version (0.9.2) was released. Since then, the company released versions such as:

{| class="wikitable"
{| class="wikitable"
! Date !! Version !! Event
! Date !! Version !! Event
Line 26: Line 25:
| style="width: 100px;" | June 2010 || 0.9.2 || The very first published version (preview) of the in-memory OLAP server; MDX/XMLA support are the primary objectives.
| style="width: 100px;" | June 2010 || 0.9.2 || The very first published version (preview) of the in-memory OLAP server; MDX/XMLA support are the primary objectives.
|-
|-
| November 2010 || 1 || Building on the feedback of the community this is the first features complete (such as MDX and write back) version. A community (free) version.
| November 2010 || 1 || The first features complete (such as MDX and write back) version. A community (free) version.
|-
|-
| June 2011 || 1.3 || Expanded MDX support and stronger cube modeling features; the first version of the visualization library (GVI).
| June 2011 || 1.3 || Expanded MDX support and stronger cube modeling features; the first version of the visualization library (GVI).
|-
|-
| October 2011 || 2 || First version advertised for business use (vs community).
| October 2011 || 2 || First version advertised for business use (vs. community).
|-
|-
| April 2012 || 2.5 || First version featuring the Web Reporting server.
| April 2012 || 2.5 || First version featuring the Web Reporting server.
Line 59: Line 58:
== Architecture ==
== Architecture ==


icCube is implemented in [[Java programming language|Java]] and follows [[J2ee|J2EE]] standards. For the latter, it embeds both an [[Http|HTTP]] server ([[Jetty (web server)|Jetty]]) and a servlet container to handle all the communication tasks.
icCube is implemented in the [[Java programming language]] and follows [[J2ee]] standards. For the latter, it embeds both an [[Http]] server ([[Jetty (web server)|Jetty]]) and a servlet container to handle all the communication tasks.


Being an in-memory OLAP server, the icCube server does not need to source its data from a RDBMS; any data source that exposes its data in a tabular form can be used; several plugins exists for accessing files, HTTP stream, etc. Accessing datasource that expose JSON objects is also supported (e.g., MongoDB). icCube is then taking care of possibly complex relations (e.g., many-2-many) implied by the JSON structure.
Being an in-memory OLAP server, the icCube server does not need to source its data from a RDBMS; any data source that exposes its data in a tabular form can be used; several plugins exists for accessing files, HTTP stream, etc. Accessing datasource that expose JSON objects is also supported (e.g., MongoDB). icCube is then taking care of possibly complex relations (e.g., many-2-many) implied by the JSON structure.


Accessing icCube (cube modeling, server monitoring, MDX queries, Web reporting and dashboards) is performed through a unique Web interface and a JSON Rest API.
Accessing icCube (cube modeling, server monitoring, MDX queries, Web reporting and dashboards) is performed through a Web interface and a JSON Rest API.


The icCube OLAP server does not use any caching or pre-aggregation mechanism.
The icCube OLAP server does not use any caching or pre-aggregation mechanism.
Line 72: Line 71:
icCube patented an MDX debugger.<ref>{{cite web|url=http://www.google.com.ar/patents/US8533218|title=Debugging system for multidimensional database query expressions on a processing server}}</ref>
icCube patented an MDX debugger.<ref>{{cite web|url=http://www.google.com.ar/patents/US8533218|title=Debugging system for multidimensional database query expressions on a processing server}}</ref>
icCube supports a standard interface and a proprietary one.
icCube supports a standard interface and a proprietary one.
The [[XML for Analysis]] (XMLA protocol can connect to any XMLA compatible reporting tool.
The [[XML for Analysis]] (XMLA) protocol can connect to any compatible reporting tool.


icCube supports its own proprietary protocol called GVI. [[Http|HTTP]] based, it can be extended.
icCube supports its own proprietary protocol called GVI. [[Http|HTTP]] based, it can be extended.
This protocol leverages the Google Visualization wire protocol.<ref>{{cite web|url=https://developers.google.com/chart/interactive/docs/dev/implementing_data_source|title=Implementing the Chart Tools Datasource Protocol (V0.6)}}</ref> Javascript is the primary implementation language and a Java mapping library is also available.
This protocol uses the Google Visualization wire protocol.<ref>{{cite web|url=https://developers.google.com/chart/interactive/docs/dev/implementing_data_source|title=Implementing the Chart Tools Datasource Protocol (V0.6)}}</ref> Javascript is the primary implementation language and a Java mapping library is also available.


Since icCube 6.8.6, the icCube server supports a JSON REST API for a programmatic access.
Since icCube 6.8.6, the icCube server supports a JSON REST API for a programmatic access.

Revision as of 21:21, 21 September 2021

icCube OLAP Server
Developer(s)icCube software Sarl
Stable release
7.10 / March 12, 2021 (2021-03-12)
Operating systemCross-platform (JVM)
TypeOnline analytical processing
Websitewww.iccube.com

icCube is a company founded in Switzerland that provides business intelligence (BI) software of the same name. The software can be fully embedded, can be hosted in a managed environment or installed in a customer's machine on premises.

The BI tool allows end-users to create or edit dashboards themselves and is capable of processing data from multiple sources in real-time. The software makes the dashboards, the dashboard builder, the schema/cube builder and the server monitoring application accessible from a web browser only. No software has to be installed at the device of the end-user.

Next to the browser-based dashboard builder, data can be accessed by running queries directly on the OLAP cube using MDX, SQL or R.

History

icCube sells an online analytical processing (OLAP) server.

In June 2010 its first public community version (0.9.2) was released. Since then, the company released versions such as:

Date Version Event
June 2010 0.9.2 The very first published version (preview) of the in-memory OLAP server; MDX/XMLA support are the primary objectives.
November 2010 1 The first features complete (such as MDX and write back) version. A community (free) version.
June 2011 1.3 Expanded MDX support and stronger cube modeling features; the first version of the visualization library (GVI).
October 2011 2 First version advertised for business use (vs. community).
April 2012 2.5 First version featuring the Web Reporting server.
January 2013 3 Better performance and more features.
June 2013 4 A second generation calculation engine.
January 2015 4.8.2 Improving the 4.x versions (server features and speed, Web Reporting).
May 2015 5.1 Adding extract, transform, load features.
May 2016 5.2 Improving the 5.x versions.
October 2016 6.0 Brand new reporting and new server calculation engine.
July 2017 6.2 Added Google Maps layers for GEO widgets, heat maps, etc
August 2017 6.5 Added dashboard commenting module for collaboration
April 2018 6.6 Improved ETL + Added dashboard discussions/comments can be filtered by current data filters.
April 2019 7.0 New Server UI / New JSON Rest API
January 2020 7.1 Support for Java 11 and onwards

Architecture

icCube is implemented in the Java programming language and follows J2ee standards. For the latter, it embeds both an Http server (Jetty) and a servlet container to handle all the communication tasks.

Being an in-memory OLAP server, the icCube server does not need to source its data from a RDBMS; any data source that exposes its data in a tabular form can be used; several plugins exists for accessing files, HTTP stream, etc. Accessing datasource that expose JSON objects is also supported (e.g., MongoDB). icCube is then taking care of possibly complex relations (e.g., many-2-many) implied by the JSON structure.

Accessing icCube (cube modeling, server monitoring, MDX queries, Web reporting and dashboards) is performed through a Web interface and a JSON Rest API.

The icCube OLAP server does not use any caching or pre-aggregation mechanism.

Interfaces

icCube uses Multidimensional Expressions (MDX) as its query language and several extensions [1] to the original language : function declarations, vector (even at measures level), matrix, objects, Java and R interactions.[2] icCube patented an MDX debugger.[3] icCube supports a standard interface and a proprietary one. The XML for Analysis (XMLA) protocol can connect to any compatible reporting tool.

icCube supports its own proprietary protocol called GVI. HTTP based, it can be extended. This protocol uses the Google Visualization wire protocol.[4] Javascript is the primary implementation language and a Java mapping library is also available.

Since icCube 6.8.6, the icCube server supports a JSON REST API for a programmatic access.

See also

References

  1. ^ "Chris Webb on icCube MDX Declared Functions".
  2. ^ "icCube extends MDX with OO capabilities". Archived from the original on 2013-07-18. Retrieved 2013-07-18.
  3. ^ "Debugging system for multidimensional database query expressions on a processing server".
  4. ^ "Implementing the Chart Tools Datasource Protocol (V0.6)".