Guest post by
Karan Chadha, Associate Consultant, Infosys
OBIEE 11g was launched amidst much fanfare in mid 2010 and the feedback since then has been fairly positive. Owing to this success, the market is seeing a lot of traction towards OBIEE 11g upgrade. I was a part of one such upgrade project and based on my understanding I am sharing a few key considerations:
- Why should an organization upgrade to OBIEE 11g?
- How automated is the upgrade and how much of manual effort is involved?
- What would be the tentative timelines to complete the upgrade?
Why should an organization upgrade to OBIEE 11g?
The superiority of OBIEE 11g is primarily on three accounts. First, it has a more robust architecture employing Web Logic Server and Fusion Middleware Control leading to improved scalability, performance and administrative ease. Second, it offers a host of powerful features like Scorecards, Action Framework, Geospatial Analytics and integration with iPad/iPhone making it one of the most comprehensive BI suites in the market. Third, it offers richer and enhanced visualizations leading to better user experience.
Despite a long list of benefits that OBIEE 11g has on offer, it is critical not to jump to an upgrade. The key is to have a thorough evaluation of the new features of 11g against the strategic objectives and BI usage patterns of the organization. This will help in determining the benefits that business could expect out of an upgrade. With OBIEE 11g upgrade being effort and cost intensive, this evaluation will ensure that a valid business case is proposed and an organization's return on its BI investment is maximized. OBIEE 11g upgrade may be inevitable at some stage but not obvious right away.
How automated is the upgrade and how much of manual effort is involved?
The upgrade utility that Oracle provides upgrades the RPD and the Web Catalog automatically. Anything lying beyond these two components requires a manual upgrade. Some key components which fall under this category are:
- UI Components like Banner, Logo, Brand line and font to name a few are driven by CSS and HTML files which lie beyond the RPD and Web Catalog. Copying the content of these files from one version to another is also not feasible since the structure of these files is different across versions.
- Various Configuration Tags in InstanceConfig and NQSConfig files are also required to be manually added or modified and copying the content across versions is not feasible, again, due to the difference in structure of these files in both versions.
- Other Miscellaneous Components like Clustering, Scheduler Schema (requires configuration in Enterprise Manager), and Custom Messages also require manual intervention.
Prima facie, it might seem that the upgrade is predominantly automated. But the seemingly automated portion involves a lot of manual effort primarily due to two reasons. First, OBIEE 11g being structurally different to 10g leads to certain aberrations (for instance, the new charting engine employed by 11g necessitating rework on several graphs or certain metadata warnings in 10g becoming errors in 11g). Second, the upgrade process is far from perfect resulting in defects and anomalies. The corollary of the second point is that extensive testing is required to ensure all objects are working the way they should. Taking these factors into consideration, a lot of manual effort is required especially to upgrade a complex environment.
What would be the tentative timelines to complete the upgrade?
The timelines could vary from just a couple of days to 10-12 weeks depending upon the complexity and size of the environment. While upgrading a vanilla 10g environment with the default 'Paint' RPD may take only 1-2 days, upgrading a complex environment could be a 10-12 weeks job (considering a 3-4 member team). To sum it up, the timelines will depend on the number of subject areas, reports and dashboards, number of new features configured, level of UI customizations, and the overall complexity of the environment. A 2-3 day assessment exercise of the environment should give us the answer.