Step 6.Load members and data into the database.
IV) Hybrid Analysis Tuning
The following parameters are important in regard to Hybrid Analysis, and are set in the ESSBASE.CFG file located in the Essbase/bin directory:
• HAENABLE: Set to TRUE (i.e. HAENABLE TRUE) to enable Hybrid queries to retrieve relational members and data. This is the most important setting, since it enables or disables Hybrid Analysis on the Essbase OLAP Server.
• HAMEMORYCACHESIZE: Size the amount of memory for member caching. This reduces the amount of member lookup SQL, while data lookup still takes the same duration.
• HAMAXNUMCONNECTION: Determine the number of maximum connections per Essbase OLAP multidimensional database.
• HAMAXSQLQUERY: Set the maximum numbers of SQL queries.
• HAMAXQUERYROWS: Set the maximum number of rows returned from your SQL query. • HAMAXQUERYTIME: Set the maximum query time before terminated.
• HARETRIEVENUMROW: Determine the number of rows, resulting from an SQL query, to process at one time.
These parameters will not be effective until we have restarted the Essbase OLAP Server. For these and additional parameter settings information see “Essbase Analytic Services System Administrator’s Guide”
Whether you start Essbase Integration Services from a command prompt (i.e. olapisvr) or from a Windows Desktop Start menu, here are a few settings to optimize. The following parameters can be set in the EIS.CFG file located in the EssIntegration\bin directory.
-N To specify the number of threads Integration Server uses when sending data to Analytic Services during a data load, type –N number_of_threads when you start Integration Server. The default setting is 1 thread.
The -N switch may be used concurrently with the -C switch.
The number of threads allocated to the Integration Server data load optimization process is controlled by the -N switch. For example, to set the number of threads to 3, type olapisvr -N3 In the eis.cfg file, this parameter is specified in the format: [N]=3
-V Disables the validation and speeds up the saving process of model and metaoutline [V] = 0
These parameters will not be effective until you have restarted the Essbase Integration Services. For these and additional parameter settings information see “Essbase XTD Integration Services System Administrator’s Guide” section Integration Server Startup Switches.
V) Advantages:
Designed to work in a mixed-vendor environment and gives high performance access to operational relational data Hybrid Analysis for Hyperion Essbase enables relational storage of business data while preserving the powerful calculation capabilities of Hyperion Essbase. Seamlessly navigate across multi-dimensional and relational data, while maintaining the OLAP-style navigation, point-of-view and calculation logic.
Essbase Integration Services is a suite of graphical tools and scalable data integration services that will dramatically reduce the time and expense required to create, deploy, and manage tailored applications. Analytic Integration Services provides a vital link between tailored-made applications built on the Hyperion BI Platform and detailed data stored in relational databases.
A centralized OLAP Metadata repository simplifies tailored application administration, promotes reusability of dimensions, calculations, and business rules and facilitates delivery of business-focused applications driving insight across the enterprise. Use Analytic Integration Services with Hyperion Essbase to achieve rapid development and deployment of performance management applications that support a wide range of business needs. Built on a flexible, multi-tier architecture, Analytic Integration Services easily scales to accommodate changing requirements.
By using Hybrid Analysis, Integration with our relational data allows for the creation of large complex database to help to analyze our Business Information as well as dramatically reduces the cycle times. It provides environment for rapid development of tailored business performance management solutions and it enables to connect to different types of relational databases which are present on the different flat forms(UNIX, Windows, etc.,)
On demand drill-through to relational detail. Query detail stored in relational sourceswithout SQL programming. Driven by a centralized metadata catalog, drill-through automatically generates optimized SQL to select the required information. There is no maintenance required.
Performance, scalability and reliability at a low cost of ownership. The Metaoutline created in EIS can be reused for building any other cube by doing some changes in it.4) Integration of Oracle Essbase 9.3.1 with OBIEE
Many organizations today use a excess of different Business Intelligence (BI) tools and applications to collect information from a variety of sources, analyze it, and share it with users. However, many of these tools are
(i)
Designed for professional analysts and not business users(ii)
Complex to use and have several functional limitations(iii)
Poorly integrated making it complex to share analyses across different tools;(iv)
have scalability and manageability limitations that make them expensive to maintain as the amount of data, the number of data sources, the number of active users, and the complexity of the analysis being performed grows.The BI environment today is fragmented. As a result it is difficult to get a unified view of the entire enterprise. There are discrepancies in the reports/insight derived from the fragmented systems as every system has its own way of interpreting the data in these disparate systems. So now the trend has started integrating the different BI tools form same/different vendor. BI needs to evolve such that it is no longer about reporting results but about driving business processes.
Now OBIEE 10.1.3.3.1 enable us to user Hyperion Essbase cube as a data source for OBIEE. We also have some added advantage of integrating these BI tools and that will be elaborated a bit in the coming sections.