✍ Kashif M ™
☎ +91 9994883085
✉ kashif7222@gmail.com


Saturday, 21 June 2014

Step by Step explaining of OBIEE 11g Architecture

By on June 21, 2014

 Over all stack is an Oracle BI Domain.

1. Made up of three areas WLS Admin server, WLS managed server (Java Components), System components (Non Java Components).

2. Same as in OBIEE 10g but now integrated with Fusion Middleware WLS stack.

3. Java components are installed in managed server and controlled by Fusion Middleware control.

4. Web logic service Admin server used for controlling WLS platform like Startup, shutdown, security, Non-OBIEE specific tables.

5. Fusion Middleware Control (Enterprise Manager) used for managing OBIEE

6. OPMN used for starting and stopping system components.

7. Node manager is used for starting and stopping managed servers.

Role of Fusion Middleware Control (EM):

1. Unified, system wide management of all nodes across BI domain.

2. Patching and upgrading, start and stop system components.

3. Management of rpds and web catalogs.

4. Performance monitoring

5. Replaces(in part, initially) hand editing of config files (nqsconfig.ini)

What hasn't changed since OBIEE 10g:

1. All configuration data still held in text file.

2. System components still need Restart after config change.

3. Still single rpd per BI server.


1. Used for start/stop/Restart services.

2. Process recovery, process ping.

3. Managed via EM or Command line.

4. Used for performance collection(DMS)

5. Standard Fusion Middleware process control tool.

Node Manager:

1. Used for starting and stopping distributed managed servers.

2. Can also restart managed servers that have crashed.

3. The equivalent as OPMN but for Java components.

4. In only installed when managed server installed.

Web logic Domain:

1. Each OBIEE 11g OBIEE domain contains single web logic domain.

2. Contains one Admin server and at the start one managed server.

3. Web logic domain administered through Admin console and WLST (web logic scripting).

4. Managed servers can be started manually or through node manager.

The Bean Browser:

1. The list of OBIEE 11g administration M Beans can be viewed in M Bean browser.

2. Using EM, right click on Admin server --> Farm --> BI Foundation_Domain -->Web logic domain -->bi foundation_domain--> MBean Browser.

3. Key systems management API MBeans include

· Server configuration MBean: u[loaf and register new rpd.

· BI domain MBean: lock, commit and rollback changes to OBIEE config.

· BI instance MBean: start, stop and restart components.

· BI log configuration MBean, Email configuration MBean etc..,

4. Screen: Application defined MBeans: BI Domain

Step1: In Lock Application defined MBeans: BI Domain.BI Instance server configuration

Tab: Operations --> Upload repository.

Step2: Application defined MBeans:Domain config proxy.

Tab: attributes--> Repository Name; Restart Needed

Step3: In EM we press active changes

Operation: Commit

Updates nqsconfig.ini file.

Transfers rpd through biee_dta.zip archive file. Copies rpd password to credential store.

Now we have to restart the system components, capacity management-> Availability.

Step4: Application defined MBeans: OPMN:Instance1 from 4 to 13 all restarts.

mkashu: Step by Step explaining of OBIEE 11g Architecture
Review : Kashif | Kashif
Update: June 21, 2014 | Rating: 4.5

Comment for "Step by Step explaining of OBIEE 11g Architecture"


Post a Comment

Blog Archive