Archive for June, 2011

Migrating BusinessObjects Query as a Web Service

BusinessObjects Query as a Web Service started a few years ago as a lab project. It quickly gained traction and with the release of XI 3.x was integrated into the main product tree. This feature offers BusinessObjects metadata (universe) and reports designers the ability to publish reports as web services. If you are not familiar with it, the QaaWS interface is very intuitive and essentially is completely similar to that of a web intelligence report query panel. The difference is, when done designing the report, it is published as web service on the BO server, and provides you the WSDL URL automatically.
QaaWS have many uses for integrating data from your BO system into other applications, and BO itself uses this interface to transfer data to Xcelsius, since it already came with a web services data connection.
While creating a QaaWS is very simple, migrating them takes a couple of maneuvers that you should be aware of, to assure a successful deployment of your QaaWS data driven application from dev to test and prod.
The basic migration is done using the BusinessObjects regular migration tool, the Import Wizard. Use the Import Wizard to select the option to migrate application objects and folders.

These would be your QaaWS objects on the BO system. With this option selected, the Import Wizard will direct you to select the appropriate QaaWS from the applications folder section of the repository, which is not visible in InfoView.
After you complete this portion of the migration, your QaaWS will essentially exist on the destination system, and will be in the same general state you would expect from any migrated BO object, with their CUID retained from the original system so that any links that exist between your QaaWS and other reports or application will continue to work as they did in the original system.
However, the web services URLs have not actually changed during the migration process, and will still be pointing to the original BO system. To reconfigure the recently migrated web services and assure they are pointing to the new target system, you will need to follow one more step.
Using the QaaWS designer application, login to the destination BO server, and open each and every migrated QaaWS. When you open a QaaWS that has a different server URL then the server name they are currently deployed on, the tool will prompt you to change the URL. Make sure you select the NO option to change the URL, and then continue to republish the web service.

Once you complete this step for your QaaWS queries, all your web services will be pointing to the correct system and ready to operate properly and as expected.

Can Cognos fraud detection software detect Cognos fraud?

Published by Ron Keler in BI At Large on June 20th, 2011 | No Comments »

I’ve been following the media coverage of the Cognos bribery case with the Massachusetts speaker of the house, Sal DiMasi, with great curiosity. Dimasi was recently convicted. But, what strike me as being very interesting is how IBM was able to completely avoid what I thought would become a public relations catastrophe. For whatever reasons, almost all the US media coverage of this fraud case focused on the rogue Massachusetts high officers clerks who agreed to award Cognos some $13M in software sales in favor of pocketing tens of thousands of dollars for themselves.

The coverage I followed was primarily on Boston National Public Radio station and the boston.com publication. Dimasi’s name has been all over the coverage, and the $25,000 he was given to award Cognos the contracts is mentioned again and again. However, all this was going down right around the time IBM bought Cognos. It’s quite obvious that a large state wide software deal worth over $13M in software sales alone would have been visible during the purchase of Cognos. How did this kickback scheme elude IBM execs when they were conducting their due-diligence before buying Cognos is not clear. It is also not clear how come the state of Massachusetts is still conducting business as usual with Cognos.

As a BI professional, who is passionate about providing information for individuals and business to help them improve their business and processes, I find it highly disturbing that a company that has such a message carved on its flag would be involved in such unethical and illegal practices. Perhaps this is a bit naïve, but I really thought that that type of corporate scandalous activity is reserved for high flying financial corporations, Enrons and such, and to be associated with an industry that employs these kind of practices is a very sobering fact.

Finally, you have to wonder if the prosecutors used Cognos fraud detection capabilities, as advertised by IBM here to find out about this…

Mobile BI to replace reports push model

Published by Ron Keler in BI At Large on June 17th, 2011 | 2 Comments »

I first published this post on Technorati as Mobile BI to Replace Reports Push Model
BI Content is typically distributed in either a push model or a pull model. In a traditional pull model, content is generated on the BI server, and users are directed to some portal, where they have access to the content. They login (or SSO) into a website where they typically navigate to the location of a certain report they have access to.

This model got a lot of push back from managers and executives who are many times not very technologically savvy (this is something we’ll see gone over the next decade, as a new generation of executives who grew up with computers take on the economy), or don’t have the time to login to the internal portal to view reports. These executives like BI content to be pushed to them, typically via email. “I want you to email me the report automatically every day at 7:00AM, and I’ll look at it when I check email”.

The push model created a significant headache for the BI vendors who now had to integrate into their BI software packages scheduling, bursting and mass emailing capabilities, that are not really part of their core competency. For a while, the competition between the large BI vendors had a lot to do with this capability. Can OBIEE iBots accomplish the same level of bursting that SAP BusinessObjects Publisher can? Can interactive BI applications and dashboard created in the framework be packaged somehow into static emails?

Well, as the evolution of business continues to accelerate around mobility, the push model is evolving as well. Executives who had only email as a tool to consume information in a compact, rapid and mobile manner now have a lot more choices. Cell phone applications, tablets, net books and other technological gizmos now allow executives to stay connected with essential applications in a very streamlined and simple manner. Email is no longer the only option to receive information from the office. In fact, compared to the new BI applications that are rapidly becoming available on cell phone platforms, email seems, well, a bit arcane and cumbersome.

Certainly the investment already made by the BI vendors in their distribution technology will not be retracted, and these capabilities will continue to play an important role in operational BI applications and use cases. However, I expect we will see mobile BI applications address many of the uses business previously saw for report bursting and publishing technologies.

BI applications – the evolution of dashboards and scorecards

Published by Ron Keler in BI At Large on June 11th, 2011 | No Comments »

There’s a lot of “chatter” about mobile BI, and BI in general these days. As the information age matures and explodes, BI is all the rage. Everybody seems to get the premise of delivering information, and the delivery medium that is becoming the standard is the dashboard. The BI vendors have done such a good job increasing the reliability, functionality, and simplicity of use of their BI dashboarding tools, while stretching their capabilities further and further, that the business has started taking notice.

The level of sophistication users now expect to see in their BI solutions is far beyond that of simple reports. They expect interactivity, navigation, drill downs, up and sideways, and a cohesive user experience, the same they would see on a commercial website, or an application. And yet, many continue to describe the BI products as “reports” or “dashboards”. Well, that perceptions can be very misleading as the level of design and effort required to produce this new breed of data driven applications is misunderstood.

Traditional BI projects require a combination of skills that must be carefully combined to achieve success. Strong business sense and understanding of functional requirements, strategic goals and organizational structure must be combined with strong data skills around dimensional modeling, etl techniques and a wide variety of technologies that are used in BI projects. Now add to this long list traditional application design skills.

Today’s “dashboards” are made out of at least 5-6 screens, and on many occasions exceed 20, with complex and highly refined navigation paths, use cases, functionality to hide and show various parts of the application, with different levels of data granularity and presentation and different times based on user interactivity, maintaining drilling contexts across all this, complex security requirements and of course must be graphically stunning. Similar traditional applications written in programming languages such as C, Java or .net can take many months and a team of developers to complete, but “dashboards” roll out on schedules measured in weeks.

Furthermore, as excited business users start using these BI applications, they quickly realize the potential of commercializing them and unleashing them on their own external clients.

This is most certainly the evolution of BI. These new applications are delivered over traditional PCs, mobile devices, on intranets as well as the internet and are being designed to cater to a wide variety of users, from novice technically challenged users, to the savviest business analysts.

The BI applications trend is on a trajectory headed for wide adoption. As more companies learn about the new capabilities of the leading BI tools from SAP, Oracle, IBM, Microsoft and the likes, and data visualization technology continues to improve, I expect to see these applications become the norm in any BI project, taking the place of the more simplistic dashboard or scorecard.

And as this happens, we will surely see more traditional software design methodologies make their way into the BI world.

Open source BI with Pentaho – how far can it stretch?

Published by Ron Keler in Open source BI on June 8th, 2011 | 2 Comments »

Open source BI software is a fascinating topic that deserves a lot more discussion. Since the domain of business intelligence is all about information democracy and “liberating” the data that is locked in the company databases, turning it to meaningful insight, I would argue that the software used to perform this work is still not the key ingredient to achieve BI happiness. Of course, the tools are important, and every BI implementation must include a proper tool selection process in which requirements are aligned with capabilities, as well as price. But as long as the software selected is reasonably adequate to the BI implementation needs, the success becomes all about the implementation and the adoption of the new tools, being deployed to provide transparency and disseminate information throughout the organization. From that perspective, as long as the open source software meets the grade, it makes perfect sense. In fact, since any BI implementation will require a good degree of implementation services, getting the software for free makes a lot of sense. BUT (in all caps), can you find an open source BI platform that meets your needs and follows standard BI architecture? Pentaho could be a good answer to this question.

I remember reviewing Pentaho several years ago. At the time, the technical folks there were doing some pretty impressive things, like integrating Google maps in dashboards. Shortly after I saw that example on the Pentaho web site, I remember seeing the BusinessObjects mashup concept start coming to life, with maps and other web content integrated in webi reports. Coincidence? Maybe.

Today, Pentaho is available as an enterprise grade commercial product and an open source product. The open source “community edition” is targeted for non-enterprise users: college students, developers, small local implementations. But how far can you take the community edition? I will try to find out.

First of all, the breadth of products engulfed under the Pentaho umbrella is impressive. They got much of the BI architecture cornerstone covered. The BI server provides web based centralized access, control, content management, scheduling and security. A metadata management tool allows the creation of reusable data sources for business users. The report designer and analysis view provide good drag and drop type ad-hoc web based functionality. Kettle is a robust ETL tool included in the framework, and Mondrian is Pentaho’s own OLAP engine for cube analysis. The ChartBeans look promising and seem to provide the type of data visualization capability we see from Google and others these days.

I was also impressed with how simple it was to get a simple Pentaho installation going and produce a first “Hello world” report (screenshot below). In a couple of hours or so I had the software downloaded, running and the first report created. Quite painless.

Like any software product, I am sure Pentaho has its strengths and weaknesses, and I will describe some of them over the next weeks as I dig deeper into the platform.

Xcelsius flyout menu

Published by Ron Keler in Xcelsius on June 1st, 2011 | 5 Comments »

One of the most important aspects of dashboard design is navigation. Just like any other application, a dashboard is made out of content, functionality and navigation. The drilling, slicing, dicing, and data exploration are all part of your BI application navigation flow, and you must consider it as part of your designs if you wish to be successful. I explored navigation in other posts as well, such as this one. Since Xcelsius deploys like a website (.swf) and “feels” like a web site, users often expect web site functionality out of it, like fly out menus. I took a stab at building an Xcelsius flyout menu. You can find the xlf here. The mouse over functionality in Xcelsius is descent, but I’m not sure it can really compete with javascript, dhtml, ajax, etc. Also, the lack of true event driven programming makes it difficult to “program” navigation. But in any case, this is a pretty good start for your flyout Xcelsius menu..

© BI HAPPY
CyberChimps