
By now you have probably heard about Web 2.0, the next generation of web focus in the post dot com era. Like most technology terms, Web 2.0 is loosely termed, but it basically boils down to making a distinction that while much of the technology that drove the dot com era was dramatically new and novel, it is now a ubiquitous commodity.
On that same evolution, Business Intelligence is now in similar maturing stage, causing its own term – BI 2.0. This reflects the level of commodity and default expectation that BI now enjoys universally, like de-silo’ed access to information via canned reports. But in BI 2.0 we are now seeing the next level were users go beyond the “canned report” that simply informs to real analytics that allow them to analyze and interact with the data to gain intelligence.
This also means the number of tools one can choose to build solutions have increased. Look for more on that in an upcoming newsletter.
Microsoft is gaining ground in business performance management (BPM) by stealthily buying up vendors that would eventually comprise a full end-to-end BPM suite. So far, they have acquired Budgeting & Planning and Consolidation packages from FRx Software; they have also acquired Analytics & Business Intelligence product sets from ProClarity. SQL Server 2005 is evolving to a powerful database and they are also doing well in the Portal business. So before you know it, they will have an integrated BPM offering for all sizes of companies.
So if history repeats, they might bring out MS BPM 1.0 and we will all pour scorn at their initial efforts and wonder what is going on out there in Redmond. Then they might release MS BPM 2.0 and annihilate all comers, and we will shake our heads and marvel at how this happened. You’ve got to love these guys!
Impacts to BusinessObjects XI R2 and BusinessObjects XI R1
Below are the three ways unpatched BusinessObjects XI Rx products will be affected if the patch for the change in Daylight Saving Time (DST) is not applied.
- In clustered deployments it is important to ensure that all central management server (CMS) clusters have the same patches applied. If a CMS cluster has one CMS with a patched operating system (OS), and another CMS is running on a non-patched OS, the time difference will be greater than one hour. This time difference will prevent the cluster from forming when one CMS is in DST while the other is not.
- In instances where the web component server (WCS) is running on a machine with a patched OS and the CMS is running on an unpatched OS a "Run Now" command will be delayed by one hour during DST.
- Scheduled tasks will run an hour later during the extended Daylight Saving Time period.
http://support.businessobjects.com/downloads/daylight_savings_faq.asp
Daylight Savings and Microsoft
Details of the updates for Microsoft Windows and affected Microsoft applications, how you can acquire them and when they will be available can be found on the Microsoft website at http://support.microsoft.com/gp/cp_dst. Corresponding Technical Knowledge Base Articles can be linked to from this website as well. |