Transcript Customizing the Oracle Business Intelligence

Customizing the Oracle Business Intelligence
User Interface
Copyright © 2009, Oracle. All rights reserved.
Objectives
After completing this lesson, you should be able to:
• Identify and explore cascading style sheets used
by Oracle Business Intelligence
• Modify Interactive Dashboard user interface styles
by using cascading style sheets
• Modify non-dashboard user interface components
by using XML message files
• Make configuration changes by using
instanceconfig.xml
28 - 2
Copyright © 2009, Oracle. All rights reserved.
Cascading Style Sheets
• Enable the style and layout of HTML files to be
separated from their informational content
– Typically linked through an external sheet by using the
HTML <link> tag
• Are made up of style rules that tell a browser how to
present a document:
– Rules are called classes.
– Each class comprises one or more property–value pairs
in the following format: .class { property:value }
• Example:
.TitleLogo {
width: 1%;
vertical-align: bottom;
position: relative;
top: 1px ;
}
28 - 3
Copyright © 2009, Oracle. All rights reserved.
Business Intelligence Cascading Style Sheets
• Define the Oracle BI Interactive Dashboards user
interface
• Can be modified by Web developers with administrator
rights
• Are located at
OracleBI\web\app\res\s_oracle10\b_mozilla_4\
• Should be saved as copies in the
OracleBIData\web\res\ folder to prevent changes
from being overwritten by upgrades
28 - 4
Copyright © 2009, Oracle. All rights reserved.
Modifying Cascading Style Sheets
• The overall look and feel of the dashboards is
controlled by:
– portalbanner.css
– portalcontent.css
• Each Business Intelligence view has its own section in
views.css.
28 - 5
Copyright © 2009, Oracle. All rights reserved.
Sample Style Sheet Entry
This cascading style sheet entry sets the defaults for the
body of the dashboard.
Style class
.PortalBody {
font-family: Verdana, Arial, Sans-serif;
font-size: 9pt;
background-color: #FFFFFF;
margin: 0 0 2 0;
}
Colors in the CSS
files are in
hexadecimal
format.
28 - 6
Copyright © 2009, Oracle. All rights reserved.
XML Message Files
• Message files are used to customize text elements.
• Language-specific XML message files have their own
folder:
– web\msgdb\l_xx\messages (language identifier: l_xx)
– Example: For U.S. English, the identifier is en.
• Template and message sample XML files are stored in
the web\msgdb\messages folder.
• You store customized XML messages in the
customMessages folder.
– If you already have a file in this folder, do not modify,
move, or delete it.
• To make new messages available, you must restart the
Oracle Business Intelligence Server.
28 - 7
Copyright © 2009, Oracle. All rights reserved.
XML Message Structure
• The file name indicates the type of content.
• Each file can contain multiple messages.
• Message format:
<WebMessage name=“messageName”>
Message contents
</WebMessage>
• Example:
<WebMessage name="kmsgChooseReport">
<TEXT>Choose Request</TEXT>
</WebMessage>
28 - 8
Copyright © 2009, Oracle. All rights reserved.
Making Configuration Changes
by Using instanceconfig.xml
Make changes to the instanceconfig.xml message file
to override default parameters.
1
2
3
4
28 - 9
Copyright © 2009, Oracle. All rights reserved.
instanceconfig.xml: Example
• Several entries are present by default:
– Path to Presentation Catalog
– Oracle BI Server ODBC data source name
• Add custom entries as needed.
Data Source Name
Presentation
catalog path
Custom entry
28 - 10
Copyright © 2009, Oracle. All rights reserved.
Sample Configuration Changes
Use instanceconfig.xml to override general default
parameters and internal default settings for Siebel
Analytics Web.
Configuration file path
Remember user name
and password.
Time to expire for idle
connections
Time to log off users
automatically
28 - 11
Copyright © 2009, Oracle. All rights reserved.
Administering Oracle BI Answers
by Using instanceconfig.xml
• Use instanceconfig.xml to override specific default
parameters and internal default settings for Oracle BI
Answers.
• Examples:
– Maximum number of pivot table records
– Maximum number of pivot table populated cells
– Maximum number of table view rows
28 - 12
Copyright © 2009, Oracle. All rights reserved.
Maximum Number of Pivot Table Records
This overrides the maximum number of rows that can be
processed by a pivot table.
• Internal default: 20,000
28 - 13
Copyright © 2009, Oracle. All rights reserved.
Maximum Number of Pivot Table Populated Cells
This overrides the maximum number of populated cells
that Presentation Services allows in a pivot table.
• Internal default: 150,000
28 - 14
Copyright © 2009, Oracle. All rights reserved.
Maximum Number of Table View Rows
This overrides the maximum number of rows that appear in
a table view.
• Internal default: 65,000
28 - 15
Copyright © 2009, Oracle. All rights reserved.
Summary
In this lesson, you should have learned how to:
• Identify and explore cascading style sheets used
by Oracle Business Intelligence
• Modify Interactive Dashboard user interface styles
by using cascading style sheets
• Modify non-dashboard user interface components
by using XML message files
• Make configuration changes by using
instanceconfig.xml
28 - 16
Copyright © 2009, Oracle. All rights reserved.
Practice 28: Overview
This practice covers the following topics:
• Modifying the user interface
• Using cascading style sheets
• Using instanceconfig.xml to administer
Oracle BI Answers
• Using XML message files to administer
Oracle BI Answers
28 - 17
Copyright © 2009, Oracle. All rights reserved.