Task Performed by Oracle Fusion Middleware (EM) in OBIEE 11g
Fusion
Middleware Control:
The version 11g
permits now to change some configuration with FMW control > Farm_Bi_Foundation >
Business Intelligence > Coreapplication.
The Fusion Middleware Control console is used to monitor and start/stop
various
OBI components. It is located on the application server at
http://localhost:7001/em. Much of the configuration of OBI that used to
be done
in the NQSConfig.ini files can now be done using this front end console,
which
in turns updates the NQSConfig.ini file. Things in the NQSConfig.ini
file that
are set by EM are noted in the file with '# This Configuration setting
is
managed by Oracle Business Intelligence Enterprise Manager'. However
some sections still need to be setup manually in the NQSConfig.ini file
are:
Usage Tracking
Dynamic Libraries
Query Optimization Flags
MDX Member Name Cache Section (SAP BW)
More specific General Settings where EM doesn't contain the level of detail required
Dynamic Libraries
Query Optimization Flags
MDX Member Name Cache Section (SAP BW)
More specific General Settings where EM doesn't contain the level of detail required
The Fusion Middleware Control EM console has five tabs to manage the
application. From the domain tree, expand Business Intelligence and click
coreapplication as shown below.
Overview:
This view shows system status, and allows you to start/stop/restart BI Components. The other tabs allow you to further configure the application.
This view shows system status, and allows you to start/stop/restart BI Components. The other tabs allow you to further configure the application.
Capacity Management:
This view has four tabs:
-Metrics: This gives metrics on request response time, load and query errors. You once might have looked at Usage Tracking for this information.
-Availability: Shows current availability of all components, allowing you to start/stop them. Also includes 'Point of Failure' analysis which shows areas in the infrastructure likely to fail when a hardware/software failure occurs.
This view has four tabs:
-Metrics: This gives metrics on request response time, load and query errors. You once might have looked at Usage Tracking for this information.
-Availability: Shows current availability of all components, allowing you to start/stop them. Also includes 'Point of Failure' analysis which shows areas in the infrastructure likely to fail when a hardware/software failure occurs.
-Scalability: This tab lets you
enable Vertical Clustering, increasing the amount of instances of OBI on a
server.
-Performance: Used for cache management, including settings that would have been set in NQSConfig.ini in 10g. It manages user query response time and max rows returned settings that were set in InstanceConfig.xml.
-Performance: Used for cache management, including settings that would have been set in NQSConfig.ini in 10g. It manages user query response time and max rows returned settings that were set in InstanceConfig.xml.
Diagnostics:
This view has 2 tabs. One for server log messages and the other for log file settings. These used to be kept in the RPD and the NQSServer.log.
This view has 2 tabs. One for server log messages and the other for log file settings. These used to be kept in the RPD and the NQSServer.log.
Security:
This view allows you to enable SSO. Also links to Weblogic Admin Console Security realm to manage Weblogic security.
This view allows you to enable SSO. Also links to Weblogic Admin Console Security realm to manage Weblogic security.
Deployment:
This section is for managing the deployment of various aspects of OBI 11G.
-Presentation: Contains a few settings for Dashboard and Analysis defaults. These used to be managed on a less global scale through Manage Privileges.
-Repository: This is where the RPD and Presentation Services are managed, and shared between servers for horizontal clustering.
-Presentation: Contains a few settings for Dashboard and Analysis defaults. These used to be managed on a less global scale through Manage Privileges.
-Repository: This is where the RPD and Presentation Services are managed, and shared between servers for horizontal clustering.
-Scheduler: Schema connection information for the scheduler tables
-Marketing: For Siebel Marketing connection
-Mail: Scheduler mail server connection information
-Marketing: For Siebel Marketing connection
-Mail: Scheduler mail server connection information





No comments:
Post a Comment