Let's look at the big picture

Going right for the guts of the platform, it is best to understand how the Oracle BI 12c system is laid out by looking at the logical interoperability of the architectural components. Oracle BI 12c is a combination of several core technologies, which reside as common software components within the Oracle Fusion Middleware (FMW) stack inside the Oracle software eco-system.

The following illustration shows some of Oracle BI 12c's logical architecture components. Users of Oracle BI 11g will find some of this topology familiar, yet clearly different in many ways:

• Oracle BI Domain: This is the core architecture of Oracle BI 12c
• WebLogic Server: This is the chosen application server for Oracle BI 12c
• Service Instance: The structural housing for all critical Oracle BI artifacts (metadata) that would allow delineated movement from one environment to another (also multi-tenancy in future releases)
• Javacomponents: These are the components which have been written in Java for Oracle BI 12c. They are deployed to the application server and WebLogic Server
• BI System Components: These are the components which have been written mainly in C++ for Oracle BI 12c
• Oracle BI relational repository: This is a set of database schemas (BIPLATFORM and MDS) that store metadata related to a specific Oracle BI 12c instance
• Oracle BI filesystem: This is the instructional set of physical files and directories containing configuration, logs, and metadata concerning the Oracle BI 12c instance

Similar to the Oracle BI 11g environment, once the software has been installed, all of the components in the architecture topology shown will exist. These components are transparent to the end users (that is, users in the organization who will view dashboards, reports, receive alerts, and so on). However, for the Oracle BI 12c administrators, and those that need to work with the technical aspect of the system, each of these areas of the Oracle BI 12c architecture is very important.