Professional Documents
Culture Documents
This document describes how to install Discoverer 10.1.2 into an existing Oracle E-Business
Suite Release 12 environment. Installation of Discoverer 10.1.2 into an Oracle E-Business Suite
Release 12 environment consists of:
Installation of Discoverer 10.1.2 with Oracle Business Intelligence Server 10g Release 2
on a standalone application tier server node, or in a separate Oracle Business
Intelligence Server 10g Release 2 ORACLE_HOME on an existing application tier server
node.
Creation of the Discoverer 10.1.2 End User Layer (EUL) on a database tier server node
Import of the Oracle E-Business Suite Release 12 Discoverer content into the Discoverer
10.1.2 End User Layer
(Optional) Installation of Discoverer Administration Edition 10.1.2 on a Windows-based
PC that can be used to customize Discoverer
Supported Architectures
Discoverer 10.1.2 must be installed on a standalone server accessing an Oracle E-Business
Suite Release 12 database, or in a separate Oracle Business Intelligence Server 10g Release 2
(10.1.2.0.2 or 10.12.2) ORACLE_HOME on an existing application tier server node.
Release Versions
The following components must be used on the stand-alone instance:
The following components must be used on the Oracle E-Business Suite Release 12 instance:
Preinstallation Tasks
Read Discoverer 10.1.2 Configuration Guide
Obtain Oracle Discoverer 10g Release 2 (10.1.2.1, including 10.1.2.0.2, 10.1.2.1, 10.1.2.2) from
the Oracle Technology Network. Note that Oracle Application Server Release 2 (10.1.2.0.2)
installation will install component version OracleBI Discoverer 10.1.2.1 as visible in the Help-
>About dialog. Documentation is labeled Oracle Discoverer 10g Release 2 (10.1.2.1).
Installation Tasks
This section outlines steps required to install Oracle Business Intelligence Server 10g Release 2,
Discoverer 10.1.2, and the Discoverer 10.1.2 End User Layer. See Section 8: Conventions and
Important Directory Locations for important information about entering commands listed in this
section.
Option A Option B ok
Install OracleAS Identity Install Oracle Business Intelligence
Management Infrastructure 10g Server 10g Release 2 (10.1.2.0.2)
(10.1.4.0.1) and Oracle Application
Server 10g Release 2 (10.1.2.0.2)
type Business Intelligence and Forms
Step A.1 Install OracleAS Identity If you are not planning to use
Management Infrastructure 10g features Discoverer Connection
(10.1.4.0.1) Management, Discoverer Portlet
Provider, and Oracle SSO, you can
Step A.2. Install Oracle Application
choose to install Oracle Business
Server 10g Release 2 (10.1.2.0.2)
Intelligence Server 10g Release 2
type Business Intelligence and Forms
(10.1.2.0.2). This installation type
does not require installation and
You must install Oracle Application association to OracleAS Identity
Server 10g Release 2 (10.1.2.0.2) Management Infrastructure 10g
installation type Business Intelligence (10.1.4.0.1).
and Forms in a separate
ORACLE_HOME from the previously
Oracle Business Intelligence Server
installed OracleAS Infrastructure. The
Option A Option B ok
Oracle E-Business Suite Release 12 is certified with the Application Server Patch Sets
listed in the table below:
Apply Cumulative Patch 5 For ALL Operating Systems Except Windows and
Oracle Discoverer
10.1.2.2 4960210 6472361 or higher for your before applying one-off patches, install the patch, 58
Discoverer Server node Oracle 10gApplication Server Patch set 2 (10.1.2.2).
Note: 413788.1 for more details.
Discoverer needs access to the Database Connection (dbc) file for the database you wish to
connect to. A dbc file is a text file which stores all the information required to connect to a
particular database.
In the Discoverer10g $ORACLE_HOME/opmn/conf/opmn.xml file check the variable for
FND_SECURE. This variable specifies the directory where Discoverer is trying to locate dbc files.
By default this is set to $ORACLE_HOME/discoverer/secure.
Create the directory $ORACLE_HOME/discoverer/secure if it does not exist. Then copy the
dbc file from the $FND_SECURE directory of the E-Business Suite Release 12 instance you are
setting up Discoverer with to the Discoverer 10.1.2 $ORACLE_HOME/discoverer/secure
directory you just created.
The default naming convention for the .dbc file for Oracle E-Business Suite Release 12 is
<two_task>.dbc
If you are getting error "Could not locate or parse the .dbc file corresponding to the given Oracle
Applications instance" when trying to connect to your E-Business Suite Release 12 instance from
the OracleBI Discoverer Connections Page, please verify the filename of your dbc file. If your dbc
file name does not match above default naming convention due to using virtual names, make a
copy of your dbc file on your OracleBI Discoverer node $FND_SECURE directory and rename the
file to match above default naming convention.
1. $FND_SECURE/<two_task>.dbc
2. $FND_SECURE/<database host name>_<two_task>.dbc
Note: If your E-Business Suite is SSL Enabled you must also enable SSL for Discoverer.
Please refer to the following documentation:
Oracle® Business Intelligence Discoverer Configuration Guide
and for simplified steps:
Metalink Note 339448.1 - Quick Start to Configure Discoverer Plus/Viewer/Portlet Provider
10.1.2.0.2 in SSL + SSO
Oracle E-Business Suite Release 12 is certified with the Application Server Patch Sets
listed in the table below:
Download Additional
Certified AS Patchset One-off Patch
Location Patches
Oracle Discoverer 10.1.2.2 4960210 5985072 --
Oracle Discoverer 10.1.2.3 ok 5983622
Follow the installation instructions provided in the patch README to install the patch on your
Discoverer Administration Edition Server.
Oracle always recommends latest certified AS patchset for E-Business Suite customers.
This step contains information about modifying the Microsoft Windows registry. Before you modify
the Windows registry, back it up and make sure that you understand how to restore it if a problem
occurs. For information about how to back up, restore, and edit the registry, see the following
article in the Microsoft Knowledge Base:
Open the Windows Registry editor and create or update the following registry
keys:
DataTyp Valu
Registry Key
e e
HKEY_CURRENT_USER\Software\Oracle\Discover REG_DWO
1
er 10\Database\EnableTriggers RD
HKEY_CURRENT_USER\Software\Oracle\Discover
er REG_DWO
1
10\Database\DefaultPreserveDisplayProperty RD
ForRefresh
Copy Database Connection file
On your Discoverer 10.1.2 Administration Edition node, create a directory where you will copy the
dbc files of one or more E-Business Suite Release 12 instances you are setting up Discoverer
with, for example D:\secure. Copy the dbc file from the $FND_SECURE directory of the E-
Business Suite Release 12 instance you are setting up Discoverer with to the directory you just
created. Then create a Windows System Variable FND_SECURE to specify the directory you just
created, for example D:\secure.
If you do not have an existing Discoverer End User Layer, you must create a new Discoverer
10.1.2 End User Layer. Fresh installations of E-Business Suite Release 12 Production does not
contain a pre-installed Discoverer End User Layer. Only the E-Business Suite Release 12 Vision
database contains a pre-installed Discoverer 10.1.2 End User Layer.
We recommend that you create a new tablespace to store database objects for the Discoverer
10.1.2 End User Layer in your E-Business Suite Release 12 database.
[DB_ORACLE_HOME]/<dbname>.env
% sqlplus /NOLOG
SQL> connect sys/<sys_password> as sysdba
SQL> create tablespace DISCOVERER datafile \
'[DB_ORACLE_HOME]/dbf/discoverer01.dbf' size 200M reuse \
extent management local uniform size 128K;
SQL> /
Statement Processed
Exit SQL*Plus:
SQL> quit
$ORACLE_HOME/bin/eulapi \
-CREATE_EUL \
-APPS_MODE \
-CONNECT system/<password>@<db> \
-USER <EUL_User_Prefix>_US \
-PASSWORD <password> \
-DEFAULT_TABLESPACE <default tablespace> \
-TEMPORARY_TABLESPACE <temp tablespace> \
-EUL_LANGUAGE US \
-APPS_GRANT_DETAILS <FNDNAM>/<FNDNAM password>
For example:
Alternatively, you may also use the equivalent Discoverer Administration Edition command line on
Windows. Use the following syntax to create the End-User Layer using Discoverer Administration
Edition:
Chapter 5.9 of the Oracle Business Intelligence Discoverer Configuration Guide 10g
(10.1.2) explains how to run Discoverer Plus with different Java Virtual Machines. You must
configure OracleBI Discoverer Plus to use the same Plug-in version as being used for E-Business
Suite Release 12.
Perform the steps in this section to configure OracleBI Discoverer Plus to use the same Sun Java
Plugin as your E-Business Suite Release 12 by default.
and save the executable to your Oracle Business Intelligence 10g Release 2 filesystem as:
$ORACLE_HOME/jpi/bin/oaj2se.exe.
Find the plugin attribute within the <plus> element. This will show possible values "sun" or
"jinitiator". Set the value to "sun":
Where:
http://mybi.company.com:7780/discoverer/plus
Post-Installation Tasks:
Follow MetaLink Note 387859.1 titled Using AutoConfig to Manage System Configurations with
Oracle E-Business Suite Release 12 and apply the latest available AutoConfig Patch to your
system.
Download the Patch 6459796 from Oracle Metalink. Follow the instructions in the README to
apply the patch.
Proceed with the following steps to allow AutoConfig to switch profile options for your remote,
standalone Oracle Business Intelligence 10g Release 2 server.
Login to Oracle Applications Manager and navigate to Site Map > AutoConfig > Edit Parameters.
Variable
Title Description Value
Name
Discoverer s_disco_url Set the <protocol>://
URL value of this <machine.domain>:<port>
variable to for example:
the base http://mybi.company.com:778
URL where 0
Discoverer
is available.
Run AutoConfig to generate all configuration files for the APPL_TOP and the ORACLE_HOMEs in
its supporting technology stack:
% <ADMIN_SCRIPTS_HOME>/adautocfg.sh
Log into E-Business Suite Release 12 with the System Administrator responsibility
Ensure the following ICX profile options in Oracle E-Business Suite are set to:
You may switch the ICX_DEFAULT_EUL profile at the responsibility level if you are planning to
implement multiple End User Layers. For example:
Then you can set ICX_DEFAULT_EUL to EULEDW for Embedded Data Warehouse responsibilities
like "Financials Intelligence - Enterprise Data Warehouse". Those responsibilities will then use the
Embedded Data Warehouse End User Layer.
Regenerate your Business Views by running the "Generate Business Views by Application"
concurrent program using the Business View Setup responsibility:
In case you don't have "Business Views Setup" responsibility assigned to SYSADMIN user,
please do the following:
% sqlplus apps/<password>@<db>
SQL> select object_name from user_objects
where object_type = 'VIEW' and
status = 'INVALID' and
( object_name like '%FV_%' or object_name like '%FG_%' or
object_name like '%BV_%' or object_name like '%BG_%' )and
object_name in (select sobj_ext_table from eul_us.eul5_objs);
If necessary, recompile those objects so that all views are valid. The Discoverer refresh process
may stop if a select statement from a invalid Business Intelligence System View causes the
following error:
All invalid objects and errors must be resolved before you can proceed with the next steps,
including import and refresh of the Discoverer End User Layer. Discoverer Administration Edition
will drop End User Layer objects with dependencies on invalid E-Business Suite objects during
the refresh process.
The E-Business Suite Release 12 System Administrator account must be granted permission to
update and alter Discoverer 10.1.2 content.
Grant the End User Layer Administration privileges for user SYSADMIN using the following
command, executed on the standalone application server where Oracle Business Intelligence
Server 10g Release 2 was installed in Step 5.1 .
$ORACLE_HOME/bin/eulapi \
-CONNECT <EUL schema>/<password>@<db> \
-GRANT_PRIVILEGE \
-USER SYSADMIN \
-PRIVILEGE administration \
-PRIVILEGE all_admin_privs \
-LOG <log file name>
For all further End User Layer Administration activities you must use the Oracle E-Business Suite
User with the System Administrator responsibility (e.g. SYSADMIN). This E-Business Suite user
must import and own the Workbooks and Business Areas of all future Discoverer patches and
share them as applicable with other E-Business Suite users and responsibilities.
Make sure user SYSADMIN has full security access to all Business
Areas
This step is not necessary for the first import into a new End User Layer because the End User
Layer does not contain any Business Areas at this point. But for all subsequent future imports,
ensure that the user SYSADMIN has full access to all Business Areas.
Execute the following command on the standalone application server where Oracle Business
Intelligence Server 10g Release 2 was installed in Step 5.1 .
$ORACLE_HOME/bin/eulapi \
-CONNECT <EUL schema>/<password>@<db> \
-GRANT_PRIVILEGE \
-USER SYSADMIN \
-BUSINESS_AREA_ADMIN_ACCESS % \
-WILDCARD \
-LOG <log file name>
Discoverer .eex files are patched to your E-Bussiness Suite Release 12 instance, directory
$AU_TOP/discover. Those files must be accessible from the standalone application server
where Oracle Business Intelligence Server 10g Release 2 was installed.
Please mount your applications tier server node, directory $AU_TOP/discover on your
standalone application server where Oracle Business Intelligence Server 10g Release 2 was
installed.
If you are unable to mount this directory, you can also zip and ftp the entire $AU_TOP/discover
directory. In this case, make sure that you include the directory structure (ie. use zip -r) when you
create the zip, and preserve the directory structure when you unzip the file on the standalone
application server where Oracle Business Intelligence Server 10g Release 2 was installed. The
directory structure will include the import shell scripts $AU_TOP/discover/adupdeul.sh,
$AU_TOP/discover/adrfseul.sh and the language specific subdirectories containing the set
of .eex files.
Create a windows system variable FND_SECURE with value as per Section 5, Step 5.2.2,
before executing AD utility scripts you just accessed from your E-Business Suite Release 12
instance, ie. $AU_TOP/discover/adupdeul.sh, $AU_TOP/discover/adrfseul.sh
In this step, you will run AD utility adupdeul.sh on the standalone application server where
Oracle Business Intelligence Server 10g Release 2 was installed to import the Discoverer loader
files (.eex files) for Oracle E-Business Suite Release 12 into the Discoverer End User Layer. If
you are using a E-Business Suite Release 12 Vision database, you can skip this step. E-Business
Suite Release 12 Vision database already contains a pre-installed Discoverer 10.1.2 End User
Layer.
Network latency between the Oracle Business Intelligence 10g node and the database
Available resources on your Oracle Business Intelligence 10g node
Depending on these factors, the import process may take less than one hour or up to several
hours to complete for the entire set of Discoverer baseline .eex files. To minimize overhead from
network latency during the import process, it is strongly recommended that Oracle Business
Intelligence 10g be installed on a machine that is close to the database server and has a fast
network connection.
% sh adupdeul.sh \
connect=<APPS admin user>/<password>@<two_task>
resp=<APPS administrator responsibility>
gwyuid=<APPS GWYUID>
fndnam=<APPS FNDNAM>
secgroup=<secgroup>
topdir=<topdir>
language=US
eulprefix=<eulprefix>
iashome=<iashome>
[eultype=<eultype>]
[mode=<mode>]
[driver=<driver>]
[filelist=<filelist>]
[logfile=<logfile>]
[parfile=<parfile>]
Where:
Parameter Description
secgroup APPS responsibility security group
topdir Top level directory where Discoverer files are available
iashome Oracle Application Server 10g / Business Intelligence 10g
Oracle Home directory.
eulprefix
EUL schema prefix. For example, use eulprefix=EUL for
schema EUL_US
eultype OLTP - default, for standard E-Business Suite Release 12
Discoverer content
EDW - for Enterprise Data Warehouse Discoverer content
For the initial full import of the Discoverer 10.1.2 baseline files,
use mode=complete. This mode will upload all .eex files
(*o.eex) from the .../discover/ directory into the
Discoverer End User Layer.
driver Specifies a comma-separated list of driver files to be loaded.
This parameter is required if mode=DRIVER
filelist Specifies the filename of a file containing a list of files to be
loaded. This parameter is required if mode=FILELIST
logfile Log file where the adupdeul.sh script logs the result of the
import process. Default filename is adupdeul.log
parfile Filename of a command-line parameter file containing entries
of the form PARAMETER=VALUE. Parameters specified at the
command line take precedence over those specified in the
parameter file.
Notes:
PARAMETER=VALUE is acceptable
For example:
Start the full import of all .eex files in topdir/US, where topdir is specified as a parameter
sh adupdeul.sh \
connect=sysadmin/sysadmin-password@db \
resp="System Administrator" \
gwyuid=APPLSYSPUB/PUB \
fndnam=APPS \
secgroup="Standard" \
topdir=/user1/au_top/discover \
language=US \
eulprefix=EUL \
eultype=OLTP \
mode=complete \
iashome=/oracle/iAS/bi \
logfile=import_complete_eul_us_cust120.log
You can safely ignore the following messages in the import log:
<topdir>\<language>\<file>.eex: The import process did not import or modify any data.
This messages provides information that <file>.eex is an empty obsolete file and does not
modify any data during import.
Where:
Parameter Description
eulschema
Full EUL schema name, for example eulschema=EUL_US
eulpassword EUL schema password.
twotask Database name as specified in your tnsnames.ora file.
iashome Oracle Application Server 10g / Business Intelligence 10g
Oracle Home directory.
logfile Log file where the adupdeul.sh script logs the result of
the import process. Default filename is adrfseul.log
parfile Filename of a command-line parameter file containing
entries of the form PARAMETER=VALUE. Parameters
specified at the command line take precedence over those
specified in the parameter file.
Notes:
PARAMETER=VALUE is acceptable
cd /user1/au_top/discover
Start the refresh process of all existing eul folders against the database
sh adrfseul.sh \
connect=sysadmin/sysadmin-password@mydb \
resp="System Administrator" \
gwyuid=APPLSYSPUB/PUB \
fndnam=APPS \
secgroup="Standard" \
eulschema=EUL_US \
eulpassword=EUL123 \
twotask=mydb \
iashome=/oracle/iAS/bi \
logfile=refresh_eul_us_mydb.log
Expect several hours for the refresh process for all Business Areas to complete, depending on
your flex structure. The refresh utility will refresh all folders in your End User Layer one by one
and should exit with status 0.
Once completed, your End User Layer is now refreshed. Flex columns have been pulled in to the
folders using the flex prompts in the language of the End User Layer as Item Display Names.
You may use the Discoverer 10.1.2 eulapi command line utility on the standalone application
server where Oracle Business Intelligence Server 10g Release 2 was installed in Step 5.1 to
grant privileges, business area security and workbook access.
Example 1: Grant Discoverer User privileges to responsibility "Human Resources Intelligence -
Administrator (OLTP)"
$ORACLE_HOME/bin/eulapi \
-CONNECT <EUL schema>/<password>@<db> \
-GRANT_PRIVILEGE \
-ROLE "Human Resources Intelligence - Administrator (OLTP)" \
-PRIVILEGE all_user_privs
Example 2: Grant security access for business area "General Ledger" to responsibility "Human
Resources Intelligence - Administrator (OLTP)"
$ORACLE_HOME/bin/eulapi
-CONNECT <EUL schema>/<password>@<db> \
-GRANT_PRIVILEGE \
-ROLE "Human Resources Intelligence - Administrator (OLTP)" \
-BUSINESS_AREA_ACCESS "Oracle iRecruitment"
Grant Security and Privileges using Discoverer Administration
Edition on Windows
If you have already granted security and privileges using the Discoverer 10.1.2 eulapi
command-line utility, you may skip this step.
Log in to the Discoverer Administration Edition 10.1.2 as the E-Business Suite User which was
granted full Administration Privileges and Security:
Use the Help -> About Discoverer... dialog to make sure you are connected to the
correct End User Layer (<EULprefix>_<Lang>; compare the import options used above). You
can change the EUL in the dialog Tools -> Options -> Default EUL.
Check "User Edition" privileges for all E-Business Suite Users and Responsibilities who
should be allowed to open workbooks.
Grant Business Area access to E-Business Suite Users and Responsibilities who should be
allowed to query the various Business Areas.