1-14 Upgrade Guide for Oracle Business Intelligence
so that the Oracle BI Server can retrieve the password to load the repository. See Changing the Repository Password in Oracle Fusion Middleware Metadata
Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for more information.
Note that a blank repository password is not allowed in 11g.
– Groups no longer exist in the repository as objects. Instead, you implement
data access security based on the application roles to which a user belongs. Application roles are managed in an external policy store. Application role
objects exist in the repository, but these objects are pointers references to the externally managed roles.
– Users are managed in an external authentication provider and are no longer
managed in the repository. User objects exist in the repository, but these objects are pointers references to the externally managed users.
See Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for information about these and other security changes. See Applying
Data Access Security to Repository Objects in Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for more
information.
1.2.2.3 Changes Related to ODBC DSN
The connection parameters in the default ODBC DSN for the Oracle BI Server are now centrally managed by Fusion Middleware Control and cannot be manually changed.
In addition, Oracle BI EE is now deployed in a clustered configuration by default. Because of this, the default ODBC DSN for the Oracle BI Server points to the Cluster
Controller by default, rather than to the Oracle BI Server.
See Integrating Other Clients with Oracle Business Intelligence in Oracle Fusion Middleware Integrators Guide for Oracle Business Intelligence Enterprise Edition for more
information about ODBC DSNs for the Oracle BI Server.
1.2.2.4 Changes Related to the Dependencies for a Running System
Oracle BI EE 11g has additional dependencies for a running system, including:
■
The relational database that was specified upon installation must be running. This database must contain required Oracle BI EE schemas loaded using the Repository
Creation Utility RCU.
■
If you selected the Simple Installation option for the 11g installation, then the Administration Server in Oracle WebLogic Server must be running before you
start Upgrade Assistant. If you selected the Enterprise Installation option, then the Administration Server and any Managed Servers must be running before you start
Upgrade Assistant.
1.2.2.5 Changes Related to Running Command-Line Utilities
Before you can run any of the Oracle BI Server command-line utilities, you must run bi-init.cmd or bi-init.sh on UNIX to launch a command prompt or shell window that
is initialized to the Oracle instance.
You can find this utility in: ORACLE_INSTANCEbifoundationOracleBIApplicationcoreapplicationsetup
Planning to Upgrade from Oracle BI 10g to BI 11g 1-15
For more information, see Running bi-init to Launch a Shell Window Initialized to Your Oracle Instance in Oracle Fusion Middleware Metadata Repository Builders Guide for
Oracle Business Intelligence Enterprise Edition.
1.2.2.6 Changes Related to Data Source Connectivity
This section describes changes to data source connectivity in 11g.
Setting Up Oracle Database Data Sources If you want to use a net service name in a
connection pool for an Oracle Database data source, you must set up a tnsnames.ora file in the following location within the Oracle BI EE environment, so that the Oracle
BI Server can locate the entry:
ORACLE_HOMEnetworkadmin
Setting Up Essbase Data Sources The recommended client version for Essbase
connectivity in 11g is the 11.1.2.x client bundled with Oracle BI EE in ORACLE_ HOMEclientsepmEssbaseEssbaseRTC.
See Oracle Fusion Middleware Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition for additional configuration steps, such as adding Essbase
variables to bi-init.cmd for Administration Tool connectivity.
Setting Up Teradata Data Sources For connectivity to Teradata on Windows, you
must manually edit opmn.xml to include required Teradata variables. See Oracle Fusion Middleware Release Notes for more information.
1.2.2.7 Administration Tool Changes
Note the following changes in Oracle BI 11g related to the Administration Tool:
■
You can no longer open the Administration Tool by double-clicking a repository file. The resulting Administration Tool window is not initialized to the Oracle
instance, and errors result later in your session. Instead, always use the Start menu to open the Administration Tool, or launch the Administration Tool from the
command line using bi-init.cmd. For information, see Opening the Administration Tool in Oracle Fusion Middleware Metadata Repository Builders
Guide for Oracle Business Intelligence Enterprise Edition.
■
Joins in the Physical and Business Model Diagrams are represented by a line with an arrow at the one end of the join, rather than the line with crow’s feet at the
many end of the join that was used in previous releases.
For example, the following image shows a join in the diagram as it was represented in previous releases:
This join is represented as follows in 11g Release 1 11.1.1.5:
■
When creating joins in the Physical and Business Model Diagrams, you now select the many end of the join first, and then select the one end of the join. In
previous releases, joins in the diagrams were created by selecting the one end of the join first.
