Microsoft and Redhat announced a couple of weeks ago that they had signed an agreement to support each other’s OS on their respective virualization platforms. Complete details here.
A lot of people were skeptical of this deal and in the article a reference is made to the Microsoft-Novell agreement which seems to be far more comprehensive than the current one. But I think I figured out what the real deal is…
As part of the migration series, now we come to the migration of the reports. The report development studio in Hyperion Reporting & Analysis Suite isn’t robust or comprehensive enough to handle the migration (export/import) of reports. I am focusing my post to the Hyperion Financial Reporting Studio and it doesn’t even support saving the report to a local drive. To manage the reports, the web-based Workspace is used.
People are still confused when it comes to attributing what constitutes an OLTP or an OLAP system. The basic differentiation is based on the type of use and the function that the system will perform. The underlying technology or platform can be the same for both OLTP and OLAP systems, but the true differentiating factor is the logical function of the system itself.
If the system is continuously supporting the day-to-day requirements of the business (ATM’s, Checkout Systems, Order Processing, e-Commerce are all examples of OLTP systems.
OLAP systems are primarily the domain of business users who want to analyse the dynamics of the business in unique and innovative ways supported by the rich base of data that the organisation has accumulated through its OLTP systems. This can be analysis of customer usage patterns of the services offered by the company or it can be sales patterns of products based on marketing campaigns.
OLAP usage results in fewer transactions (database queries/transactions) but process huge volumes of data. OLTP systems typically process millions of transactions but process a microscopic amount of data.
Migrating an application across different environments is something one must do in any implementation. In the “Migration” series I intend to highlight how each of the key components of an Essbase/Hyperion application need to be migrated.
I cannot stress enough the need for logging. When everything is going well, there is absolutely no need to look at the logs. This is why most people forget to enable logging. It is always a good practice to enable as much logging as possible. Disk space is nothing to be stingy about and I wouldn’t be particularly concerned if the logs took up some space, but in the event of something failing they can be a lifesaver.
In any typical implementation, there are multiple environments – typically development, testing and production. Having multiple environments obviously involves migrating work from one environment to the other.