Oracle Business Intelligence Application (Part II)

In the first section, we discuss what a business intelligence application is and why it is needed. In the second part, we will focus more on your close relationships with business intelligence applications.

A common misconception

Before I begin to introduce some of the objections to purchasing decisions, I would like to discuss some general misconceptions.

It is used only for pre-established data sources:

Oracle Business intelligence applications are fully designed to add new data sources to business intelligence applications with much less effort than in a single development scenario. Using a publish-subscribe model, data can be extracted from any source application that matches an existing object in a business intelligence application. After extraction, a feature called Universal adapters uses the data and continues to transform and load it into the target business application.

I will be limited by the applications I purchase:

Business intelligence applications are built on a very open platform; there is nothing that cannot be expanded. Do you have report requirements for some data that doesn't have anything to do with the business intelligence application you're buying? So just as you normally do-simply develop these mappings and insert them into a powerful infrastructure as another workflow.

The key here is that they don't tie you to the code you buy in any way or form. In fact, you can buy a business intelligence application, remove all the special code for your business intelligence application, and use this platform and infrastructure to build a custom data warehouse. This creates repetitive work: you can simply build the platform as a pre-built foundation and do whatever you want to do with it (assuming you have the right license). As mentioned in the first section, the ETL infrastructure is often overlooked when building a new data warehouse.

In fact, most business intelligence application deployments bring other data from other sources, such as other ERP, external data, spreadsheets, or custom-developed internal applications. If complexity is the focus of the first concern, you can look at a business intelligence application as a starting point, and the final direction is determined by the content and requirements of non-commercial intelligent applications.

Application vendors ' business intelligence applications are lightweight:

This is true for many business intelligence applications. In fact Oracle did it itself before the advent of its business intelligence application 7.9. However, Oracle now offers a business intelligence application that goes well beyond the lightweight range. These applications are built on the same broad relational platform as the scope and database can handle using industry best practices.

Unlike prepackaged business intelligence applications taken from other vendors, Oracle uses the same design techniques, tools, and platforms that you initially wanted to use. If you feel good about relational databases, dimension models, and Informatica, you'll also find business applications very good. For all the things you want to do with your own development environment, you can do all of the Oracle Business intelligence applications you buy. In addition, Oracle adds some features that Informatica does not have, called the ETL orchestration (in the form of the Data Warehouse management console-"DAC").

There is a complex example that you can build into your business intelligence application system if necessary, for example, a multinational corporation has two different types of ERP, each of which is placed in 6 data centers around the world. In addition, there is more customer data in smaller applications around the world. All 12 ERP instances need to be successfully integrated into a data warehouse and overcome potential data problems, such as randomly displaying data on more than one ERP, linking records among ERP, and a complex security model. The real scenario is to extend and customize business intelligence applications appropriately to handle more logic. Many user requirements are very different from the upfront code and configuration, but business intelligence applications can be tuned to handle very complex requirements.

For the complexity of business intelligence applications, there is a point to discuss about relational OLAP vs multidimensional OLAP (cubes). To add a new dimension to the Business intelligence application for metric analysis, you can add a new dimension to the existing fact table, which can handle many rich dimensions. Cube based systems are generally not operated in this manner; there are limits to the dimension attributes that you can add to a cube before it is determined, and to delete something else. The Enterprise-class ROLAP engine is not like Obi EE.

Finally, with the functionality of Obi EE, obi applications have received wide attention. When CRM announces the customer's 360-degree view, the mantra is once again on the business intelligence application. 360-degree viewing means depth and breadth, and extensive and in-depth analytics on the Obi EE platform and leveraged in business intelligence applications. In fact, this makes it possible to analyze different metrics, each from a different source, and simultaneously analyze different processes. This is a critical lack of capability in business intelligence applications due to the limitations of the technology platform or their application vulnerabilities. In addition, this ability of the OBI EE platform is the reason for this article.