What are the Oracle Business Intelligence Applications (BI Apps)?
It is a complete, end-to-end BI environment covering the BI platform and pre-packaged analytic applications.
The platform includes a server and end user tools such as dashboards, query and analysis, enterprise reporting, disconnected access to the data -- all supported by a unified, model-centric server architecture.
On top of this platform, we have a set of analytic applications consuming the operational data sources and delivering greater insight to larger user communities across the organization via dashboards, query and analysis, and alerts.
What technology components do I need to buy to run the BI Apps?
- A database to host the Datawarehouse
- Oracle BI Suite EE Plus or Oracle BI Suite SE1 (OBIEE)
- ETL component options to OBIEE, either Oracle Data Integrator* or Informatica
- Application content per application
*Oracle Data Integrator (ODI) is currently only available for certain release against a specific release of a source system. Future plans are to have ODI fully available.
What Application content is available for the BI Apps?
How is BI Apps made aware of my source system configurations?
During the configuration of the BI Apps configurations are entered as parameters in the DAC and by completing CSV files that define your source system configs. These CSVs are then picked up during the ETL run and used to populate the warehouse.
I am a multi-country organization and would like to have the ability to display the BI Apps in the local language, is this possible?
Yes, there is the facility to have the OBIEE components displayed in multi-language and the BI Apps can be configured to display the objects in multi-language. To display the data in multi-language is a customisation effort that will require extending the warehouse to include translation tables.
Step:-1
Hardware Requirements
It is a complete, end-to-end BI environment covering the BI platform and pre-packaged analytic applications.
The platform includes a server and end user tools such as dashboards, query and analysis, enterprise reporting, disconnected access to the data -- all supported by a unified, model-centric server architecture.
On top of this platform, we have a set of analytic applications consuming the operational data sources and delivering greater insight to larger user communities across the organization via dashboards, query and analysis, and alerts.
What technology components do I need to buy to run the BI Apps?
- A database to host the Datawarehouse
- Oracle BI Suite EE Plus or Oracle BI Suite SE1 (OBIEE)
- ETL component options to OBIEE, either Oracle Data Integrator* or Informatica
- Application content per application
*Oracle Data Integrator (ODI) is currently only available for certain release against a specific release of a source system. Future plans are to have ODI fully available.
What Application content is available for the BI Apps?
ERP Analytics - Oracle Financial Analytics - Oracle Procurement and Spend Analytics - Oracle Human Resources Analytics - Oracle Supply Chain and Order Management Analytics - Oracle Spend Classification Analytics - Oracle Project Analytics CRM Analytics - Oracle Sales Analytics - Oracle Service Analytics - Oracle Marketing Analytics - Oracle Contact Center Analytics - Oracle Loyalty Analytics - Oracle Price Analytics Industry Applications - Oracle US Federal Financial Analytics Which systems can BI Apps source its data from? Oracle provides pre-built adapters for Oracle eBusiness Suite, People-soft, JD Edwards, SAP and Siebel. In additional to these pre-built adapters Oracle provides the Universal adapters that enable any other source system to be a source for the Data-warehouse. What is the DAC? DAC stands for Data Warehouse Application Console. It is an essential component of Oracle BI application architecture. DAC serves the following purposes: - DAC is a metadata driven administration and deployment tool for ETL and data warehouse objects - It is used by warehouse developers and the ETL Administrator - Manages Application Configuration - Manages the execution of warehouse loads - Provides a monitoring facility I have customized my source system; can I extend the BI Apps for these customizations? Oracle has designed the BI Apps to be extendable, from the source system mappings, the warehouse model, the BI Modelling layer to the Presentation objects. Oracle provides a methodology for extensions in the supplied guides. One of the most common extensions is the inclusion of descriptive flex-fields for eBusiness suite sources. How do I deploy the BI Apps? The BI Apps can be deployed as follows - Standalone mode - Integrated with Portal via JSR-168/WSRP - Embedded with the transaction system within a dashboard view - Embedded with the transaction system contextually within a transactional view Can I have the same security as my transactional system? The BI Apps can be integrated with the source system to enable a smooth transition for users maintaining the user’s security context as they move from the transactional system to BI Apps and back into the transactional system. Does a BI Apps implementation take as long as a traditional Data-warehouse implementation? A traditional Data-warehouse implementation will typically take in the region of 18 months + to deliver, because much of the time consuming effort has already been developed. A BI Apps project will usually have release cycles every 100 days or so. A minimal configuration implementation can have a development system up and running in a few weeks. |
How is BI Apps made aware of my source system configurations?
During the configuration of the BI Apps configurations are entered as parameters in the DAC and by completing CSV files that define your source system configs. These CSVs are then picked up during the ETL run and used to populate the warehouse.
I am a multi-country organization and would like to have the ability to display the BI Apps in the local language, is this possible?
Yes, there is the facility to have the OBIEE components displayed in multi-language and the BI Apps can be configured to display the objects in multi-language. To display the data in multi-language is a customisation effort that will require extending the warehouse to include translation tables.
OBIEE Instalation on OEL 6.5
Step:-1
Hardware Requirements
Hard Disk required around 40 GB (Including installation files etc)
RAM = 4 GB Minimum
Step:-2
Download the installation files
Here is the link used for downloading the OBIEE server installation software:
You will need to download multiple pieces of software.
Oracle database 11G for OEL6.5
Java JDK, 64 bit
Repository Creation Utility (RCU)
Oracle Fusion Middleware / Weblogic
OBIEE 64 bit for OEL6.5
Java JDK, 64 bit
Repository Creation Utility (RCU)
Oracle Fusion Middleware / Weblogic
OBIEE 64 bit for OEL6.5
Libraries for this installation are available from here if any are missing.
http://linux1.fnal.gov/linux/scientific/5x/x86_64/SL/
Step:-4
Creation of Middleware Home Directory
Log in as root and make a new directory as follows,
mkdir -p /MiddlewareHome
chown -R wishtree:oinstall /MiddlewareHome
chmod -R 775 /MiddlewareHome
When installation starts it will run a prerequisite check on the system to make sure all libraries needed for the install are available. You can either use YUM or the above link in the document to download the required libraries identified during the prerequisite check.
Step:-5
Libraries for Linux
If Libraries need to be installed cancel the install – Download and install the libraries using the commands below:
To install: rpm –ivh <package_name>
Step:-6
Ulimits
Set the Ulimit Parameters (Soft and Hard Limits)
set the /etc/security/limits.conf file
oracle soft nofile 4096
oracle hard nofile 65536
If you have set the Ulimits in the conf file above then the Linux instance will need a bounce for the settings to be set on boot up.
To set ulimit, you can execute the below command, log in as root,
Ulimit -n 4096
To see if you have set the ulimit correctly the command to use is :
ulimit –a | grep open
Step:-7
Creating an RCU on Database
As we are running OBIEE on Linux 64 Bit platform, we have to create the RCU from a Windows Machine. We are using windows 7 for this. This utility can be run any time prior to the OBIEE installation and the database user must have sysdba privilege on the required database. Database version we are using is 11.2.0.2.0.
[root@sujeet~]# cd /rcuhome/bin
[root@sujeet bin] # ./rcu
Fill in the relevant details.
This can be found in the tnsnames.ora file for the database that you want install the RCU on.
Click Next.
Ignore the Warning for database supported versions.
Select Create to create a new schema in database.
Click Ok when operation is completed.
Click Oracle Business Intelligence and click Next. Make a note of the Prefix.
Click Ok when operation is completed.
Select Use passwords for all schema. Set the password for both the schema which you are going to create in your database.
Make a note of your schema Owners and Click Next.
Click Ok to confirm the Tablespaces.
Create Ok when operation completed.
Make sure summary is ok and you have taken down all notes and click Create
You will get a completion Summary. Click Close.
That's it. If you login to your database, you will see 2 schemas with their objects have been created ready to support your OBIEE main installation.
Step:-8
OBIEE 11.1.1.7.0 Installation on OEL 6.5
Unzip the installation files on the Linux box
When you issue the first unzip command it will create a bishiphome directory and with increate sub directories for the disks.
If you do not have enough disk space on the Linux box you can keep deleting the installation zip files after you unzip them.
1. Navigate to the following directory on the server.
Initiate the installation by giving the following command on the server,
./runInstaller
[oracle@sujeet ~]# cd bishiphome/Disk1/
[oracle@sujeet Disk1]# ./runInstaller
Specify Inventory directory. (/MiddlewareHome
)
Deselect "Continue installation with local inventory" and then Ok.
Install release notes, etc. Click Next.
Skip Software updates if you want and click Next.
Click Simple install and click Next.
If any prerequisite check fails, then Cancel the installation, make them correct and restart the installer. If succeed, click Next.
Point to Middleware Directory Created earlier on install guide. And Click Next.
Fill in Weblogic and your password. Click Next.
Select components to install. Click Next.
Fill in Database Details related to RCU Created. (For DEV_BIPLATFORM)
The same for MDS and & BIPLATFORM schemas created in RCU Process.
Fill in Database Type : Oracle Database Connect String : Description as above.
BIPLATFORM : Schema as created when creating RCU and password used.
Click Next.
BIPLATFORM : Schema as created when creating RCU and password used.
Click Next.
Click Next for DEV_MDS schema accepting defaults. Click Next.
Deselect Support check box as follows and Click Next.
Click Yes.
Generate a response file (Silent Install File) & summary.
Here you can generate a response file (Silent Install File) Click Save.
You can use this file for another installation if needed.
Click Install.
Install stage of copying files has started, post install scripts and one off patches etc.
Once at 100% the copying is complete.
Installation has started configuring OBIEE.
This is where the Installer is Configuring OBIEE 11.1.1.6 and Weblogic and Fusion Middleware etc. Make sure everything is Success, and then only everything will be working as expected. Click Next.
Installation Result Summary screen.
Save the Completion Summary to the box and copy all the URL’s Needed etc to launch OBIEE.
That’s it for the installation. Run the EM makes sure everything is ok.
Test your URL’s from your completion summary and everything is up and running.
************************************************END*******************************************************
No comments:
Post a Comment