Smart Infrastructure & Smart Applications for the Smart Business – Infrastructure & Application Performance Monitoring
Data Warehouse Automation & Real-time Data – Reducing Time to Value in a Distributed Analytical Environment
Creating Data Products in a Data Mesh, Data Lake or Lakehouse for Use in Analytics (9-10 June 2022, Stockholm)
Just like on the web today where there are hundreds of AJAX frameworks are available in abundance for rapid development there is a strong likelihood that several BI frameworks may well appear inviting end users to leverage BI “composition” tools to rapidly assemble visual BI and non-BI components into custom built rich interactive analytic applications (mashups). If multiple BI frameworks do appear we may well get caught up in the buzz of new technology and trailblaze building BI visual components galore without concern for the bigger picture of how these components all fit together on a page, how they are uniquely identified, how you deal with security when it comes to access them. or how they are managed. If you are building a personal dashboard then it may be OK because you are dealing with one technology but what about building sharable dashboards for the enterprise . In my opinion it depends where the visual components are aggregated into the page and what does this. A portal does this on the server by aggregating portlets to construct a page before serving up the page to the browser. Portlet interoperability is either proprietary to the portal product or standard via JSR 286 (successor to JSR 168 which does not support portlet interoperability) standard portlet interoperability.
If you’re company has multiple BI tools (which is often the norm especially in large enterprises) you may well find business analysts composing BI dashboards without IT even knowing about it. The problem is how to bring it all under the wing of the enterprise when a business user wants to mix and match BI and non-BI visual components that are assembled client side when there are no standards. The portal is certainly not dead as it can handle this. Also AJAX is not an alternative to portals – AJAX components can in fact be integrated into portals as AJAX portlets. For this reason, portal vendors are bundling industry standard (JSR 168/286) portlet containers for free with application servers and not just as part of their portal server products so that you turn AJAX BI components into portlets without the need for a portlet development and still allow rich user interface interactions with portlet interoperability. As far as stand-alone AJAX interoperability is concerned, my suggestion is to watch what happens at the openAJAX consortium. Interesting that apart from the four software giants (IBM, Microsoft, Oracle and SAP) not a single independent BI vendor is a member! Seems to me its about time they joined.