Install Discoverer 10.1.2 _ ID 373634.1

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:

Component Name VersionOracle Application Server 10.1.2.3Oracle Business Intelligence 10.1.2.3

The following components must be used on the Oracle E-Business Suite Release 12 instance:

Component Name Version

Oracle E-Business Suite Release 12  12.0.x to 12.1.1.x

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).

The Oracle Business Intelligence Discoverer Configuration Guide 10g Release 2 (10.1.2) explains how to run, maintain and support Oracle BI Discoverer. Review this guide before proceeding further.

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.

Install Oracle Discoverer 10g Release 2 (10.1.2.0.2)

Install Oracle Application Server 10g Release 2 (10.1.2.0.2)

You must install Oracle Application Server 10g Release 2 components on a standalone server accessing an Oracle E-Business Suite Release 12 database or in a separate ORACLE_HOME on an existing application tier server node.  Choose one of the following installation options:

Option A Option B ok

 Install OracleAS Identity Management Infrastructure 10g (10.1.4.0.1) and Oracle Application Server 10g Release 2 (10.1.2.0.2) type Business Intelligence and Forms

 Install Oracle Business Intelligence Server 10g Release 2 (10.1.2.0.2)

Step A.1 Install OracleAS Identity Management Infrastructure 10g (10.1.4.0.1)

If you are not planning to use features Discoverer Connection Management, Discoverer Portlet Provider, and Oracle SSO, you can choose to install Oracle Business Intelligence Server 10g Release 2 (10.1.2.0.2). This installation type does not require installation and association to OracleAS Identity Management Infrastructure 10g (10.1.4.0.1).

Oracle Business Intelligence Server 10g Release 2 (10.1.2.0.2) is available on a separate standalone CD and includes:

Discoverer Server 10g Discoverer Plus 10g

Step A.2. Install Oracle Application Server 10g Release 2 (10.1.2.0.2) type Business Intelligence and Forms

You must install Oracle Application Server 10g Release 2 (10.1.2.0.2) installation type Business Intelligence and Forms in a separate ORACLE_HOME from the previously installed OracleAS Infrastructure. The Business Intelligence and Forms type installation is associated with an OracleAS Infrastructure during installation. The OracleAS Infrastructure might be on the same machine as the Business Intelligence and Forms type installation or on a

Option A Option B ok

different machine.

This installation type includes:

Discoverer Server 10g

Discoverer Plus 10g

Discoverer Viewer 10g

It is possible to associate the Oracle Business Intelligence Server 10g installation to Infrastructure at a later point in time, using Oracle Enterprise Manager.  Please refer to section 2.2 How to associate an OracleBI installation with an OracleAS Infrastructure in the Discoverer Configuration Guide 10g Release 2.

Apply the latest certified Discoverer Plus and Viewer Patches

Oracle E-Business Suite Release 12 is certified with the Application Server Patch Sets listed in the table below:

Certified AS Patchset

Download Location

One-off / Cumulative Patch Details

Additional Information

Oracle Discoverer 10.1.2.2 4960210

Apply Cumulative Patch 5 6472361 or higher for your Discoverer Server node

For ALL Operating Systems Except Windows and Sparc Solarisbefore applying one-off patches, install the patch, 5861907Oracle 10gApplication Server Patch set 2 (10.1.2.2). Refer Oracle Metalink Note: 413788.1 for more details.

Oracle Discoverer 10.1.2.3 ok 5983622 Apply Cumulative Patch 1

7111842 or higher for your Discoverer Server node.

Copy Database Connection file

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.

Save the dbc file in lowercase.

About DBC Files

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.

Discoverer will attempt to find the dbc file in following order

1. $FND_SECURE/<two_task>.dbc 2. $FND_SECURE/<database host name>_<two_task>.dbc

Update tnsnames.ora file

On your standalone Oracle Business Intelligence Server 10g Release 2 node, update file ORACLE_HOME/network/admin/tnsnames.ora and include the tnsnames entry to connect to your Oracle E-Business Suite Release 12 database. Use the same entry as exists in the tnsnames.ora file on your Oracle E-Business Suite Release 12 application tier server node. The database name must match the two_task entry in the dbc file. Verify you can establish a connection to your Oracle E-Business Suite Release 12 database using sqlplus.

Enable access to the Oracle E-Business Suite Release 12 Database

If SQL*Net Access security is enabled in the E-Business Suite Release 12 database, you need to authorize the Oracle Business Intelligence Server 10g Release 2 node to access the E-Business Suite Release 12 database through SQL*Net. Refer to step "Enable SQL*Net Access to the E-Business Suite Database for OracleAS 10g Hosts" in Note 376811.1 on Oracle MetaLink.

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 Guideand for simplified steps:Metalink Note 339448.1 - Quick Start to Configure Discoverer Plus/Viewer/Portlet Provider 10.1.2.0.2 in SSL + SSO

Apply the latest certified Discoverer Administration Edition Patch- client machine

Oracle E-Business Suite Release 12 is certified with the Application Server Patch Sets listed in the table below:

Certified AS PatchsetDownload Location

One-off Patch Additional 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.

Set Windows Registry Settings

If you are using Discoverer Administration Edition on Windows to refresh your End User Layer, please follow the steps below to set necessary registry settings.

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:

Q256986 Description of the Microsoft Windows Registry

On the Windows PC running Discoverer 10.1.2 Administration Edition:

Back up your current Microsoft Windows Registry

Open the Windows Registry editor and create or update the following registry keys:

Registry KeyDataTyp

eValu

e

HKEY_CURRENT_USER\Software\Oracle\Discoverer 10\Database\EnableTriggers

REG_DWORD

1

HKEY_CURRENT_USER\Software\Oracle\Discoverer 10\Database\DefaultPreserveDisplayPropertyForRefresh

REG_DWORD 1

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.

Update tnsnames.ora file

On your Discoverer 10.1.2 Administration Edition node, update file %ORACLE_HOME%/network/admin/tnsnames.ora and include the tnsnames entry to connect to your Oracle E-Business Suite Release 12 database. Use the same entry as exists in the tnsnames.ora file on your Oracle E-Business Suite Release 12 application tier server node. The database name must match the two_task entry in the dbc file.

Create new Discoverer 10.1.2 End User Layer

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.

Set Your Environment

Execute this step on your database tier with your environment pointing to your database ORACLE_HOME.  To set the environment correctly, source the file:

[DB_ORACLE_HOME]/<dbname>.env

Create the Discoverer Tablespace

Start SQL*Plus and create a tablespace named 'DISCOVERER' with an initial size of 200 megabytes, using the absolute path to the subdirectory where your datafiles are located:

% sqlplus /NOLOGSQL> connect sys/<sys_password> as sysdbaSQL> 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

Create the Discoverer End-User Layer

Create the new Discoverer 10.1.2 End User Layer by using the following command syntax, executed on the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed in Step 5.1.

$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:

$ORACLE_HOME/bin/eulapi -CREATE_EUL -APPS_MODE \-CONNECT system/manager@cus120 -USER EUL_US -PASSWORD EUL_US \-DEFAULT_TABLESPACE discoverer -TEMPORARY_TABLESPACE temp \-EUL_LANGUAGE US -APPS_GRANT_DETAILS apps/apps

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:

%ORACLE_HOME%/bin/dis51adm.exe /CREATE_EUL /APPS_MODE \/CONNECT system/manager@cus120 /USER EUL_US /PASSWORD EUL_US \/DEFAULT_TABLESPACE discoverer /TEMPORARY_TABLESPACE temp \/EUL_LANGUAGE US /APPS_GRANT_DETAILS apps/apps /SHOW_PROGRESS

Specify Java Virtual Machine for Discoverer Plus

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.

Copy the Sun Java Plug-in

Copy the Sun Java Plug-in executable from your E-Business Suite Release 12 instance at location:

http://machine.domain:port/OA_HTML/oaj2se.exe

and save the executable to your Oracle Business Intelligence 10g Release 2 filesystem as:

$ORACLE_HOME/jpi/bin/oaj2se.exe.

Edit the Discoverer Configuration File

On the Oracle Business Intelligence 10g Release 2 filesystem, open the file $ORACLE_HOME/discoverer/config/configuration.xml

Find the plugin attribute within the <plus> element. This will show possible values "sun" or "jinitiator". Set the value to "sun":

<plus laf="plastic" lafJar="" lafClass="" logLevel="error" plugin="sun" helpSet="help">

Find the line with the tag <jvm name="sun"/>

<jvm name="sun" classid="clsid:CAFEEFAC-0014-0002-0006-ABCDEFFEDCBA" plugin_setup="http://mybi.company.com:7780/jpi/j2re.exe" version="1.4.2" versionie="1,4,2,mn" type="application/x-java-applet" plugin_page="http://java.sun.com/products/archive/j2se/1.4.2_06/index.html" disco_archive="disco5i.jarjar" d4o_archive="d4o_double.jarjar"/>

Where:

s_sun_clsid - Value of s_sun_clsid in E-Business Suite Context File s_major_version - Get s_sun_plugin_ver from your E-Business Suite Context File, the 1st and 2nd number combinely form s_major_version. e.g if s_sun_plugin_ver = 1.6.0_07, value of s_major_version would be 1.6 s_sun_plugin_ver - Get s_sun_plugin_ver from your E-Business Suite Context File, replace the dots with commas. e.g if s_sun_plugin_ver = 1.6.0_07, value of s_major_version would be 1,6,0_07

Save Your Changes and Restart Discoverer Save the updated configuration.xml file Restart the Discoverer services using opmn.

Testing Your New Configuration

Verify that Discoverer Plus is now using the same Sun Java Plugin as your E-Business Suite Release 12 by navigating to the following URL:

http://mybi.company.com:7780/discoverer/plus

Post-Installation Tasks:

Apply the latest AutoConfig patch in apps

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.

Apply AD Patch 6459796

This patch contains the latest version for adrfseul.sh.

Download the Patch 6459796 from Oracle Metalink. Follow the instructions in the README to apply the patch.

Set Applications Profile Options for Discoverer using AutoConfig

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.

Specify following variable:

Title Variable

NameDescription Value

Discoverer URL

s_disco_url Set the value of this variable to the base URL where Discoverer is available.

<protocol>:// <machine.domain>:<port>

for example: http://mybi.company.com:778

0

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

Set Applications profile options in Oracle E-Business Suite

Log into E-Business Suite Release 12 with the System Administrator responsibility

Navigate to the Profile > System form

Query the %Discoverer% profile options.

Ensure the following ICX profile options in Oracle E-Business Suite are set to:

Profile Description Value

ICX: URL that points to Discoverer

http://<HTTP Server>:<Port>

Discoverer Launcher

Plus Servlet./discoverer/plus

?Connect=[APPS_SECURE]

ICX: Discoverer Viewer Launcher

URL that points to Discoverer Viewer Servlet

http://<HTTP Server>:<Port>

/discoverer/viewer?Connect=[APPS_SECURE]

ICX: Discoverer Release

Single number specifying the Discoverer release

10

ICX: Discoverer use Viewer

Specify whether Discoverer Viewer should be launched instead of Discoverer Plus (default).

Yes | No

ICX: Discoverer Default End User Layer Schema Prefix

The EUL prefix in combination with the Language code make up the EUL owner at runtime. For example EUL owner EUL_US has EUL prefix EUL.

EUL

ICX: Discoverer End User Layer Language Override

Since the End User Layer content is currently available in US English only, it is possible to override the user's general language preference for the Discoverer End User Layer using this profile option. The specified End User Layer language will be used regardless of the individual user's language preferences.

This profile does not affect the National Language Support parameters passed to Discoverer. The Discoverer User Interface will still appear according to the users ICX_LANGUAGE and ICX_TERRITORY profiles. The User Interface language will only change for valid combinations of ICX_LANGUAGE and ICX_TERRITORY.

American English

ICX: Discoverer Parameters

This profile can be used to optionally pass additional URL parameters to Discoverer. Compare Note 186120.1 on Oracle MetaLink.

<NULL>

Discoverer This profile can be used to <NULL>

DBC filename override

specify the DBC Filename Discoverer should be using to connect to the E-Business Suite database.

By default, this profile should remain NULL, in which case Discoverer will use the default dbc file for your E-Business Suite database.

You may switch the ICX_DEFAULT_EUL profile at the responsibility level if you are planning to implement multiple End User Layers. For example:

EUL_US for Business Intelligence System content EULEDW_US for Embedded Data Warehouse content

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.

Run the "Generate Business Views by Application" Concurrent Program

Regenerate your Business Views by running the "Generate Business Views by Application" concurrent program using the Business View Setup responsibility:

Logon to Oracle E-Business Suite as SYSADMIN Choose the "Business Views Setup" responsibility Navigate to Reports > Run >  Pick Single Request > "Generate ALL Business Views"

In case you don't have "Business Views Setup" responsibility assigned to SYSADMIN user, please do the following:

Logon to Oracle E-Business Suite as SYSADMIN Choose the "System Administrator" responsibility. Navigate to Security > User > Define and add responsibility "Business Views Setup" to

user SYSADMIN.

Check for Errors

After regeneration of the Business Views has been completed, check the Business View Generator output file. It should not contain any errors.

Recompile APPS objects

Recompile all objects in the APPS schema using adadmin.

Check Business Intelligence System Views

Ensure that the Business Intelligence System views exist and all Business Intelligence System views are valid by issuing the following command in SQL*Plus:

% sqlplus apps/<password>@<db>SQL> select object_name from user_objectswhere object_type = 'VIEW' andstatus = 'INVALID' and( object_name like '%FV_%' or object_name like '%FG_%' orobject_name like '%BV_%' or object_name like '%BG_%' )and object_name in (select sobj_ext_table from eul_us.eul5_objs);

Replace "eul_us" with the actual eul schema being used.

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:

ORA-04063: view "APPS.<View Name>"

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.

Set up E-Business Suite User/Responsibility for EUL Administration: SYSADMIN/System Administrator

The E-Business Suite Release 12 System Administrator account must be granted permission to update and alter Discoverer 10.1.2 content. 

Grant End User Layer Administration Privileges

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>

Access directory $AU_TOP/discover on your E-Business Suite Release 12 instance from your Oracle Business Intelligence 10g BI instance

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.

Linux users Only:

Replace the line LD_ASSUME_KERNEL= 2.4.19 with following lines in $ORACLE_HOME/discoverer/discwb.sh before Import/Refreshing the EUL.

KERNEL_VERSION=`/bin/uname -r | cut -d "-" -f1`

if [ $KERNEL_VERSION != 2.4.21 ]; thenexport LD_ASSUME_KERNEL=2.4.19elseexport LD_ASSUME_KERNEL=2.4.21fi

Note: Do not set LD_ASSUME_KERNEL for Operating Systems RHEL5,OEL5,SLES10. And for RHAS 2.1 set its value as 2.2.5

Windows users Only:

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

Import Discoverer Content for E-Business Suite Release 12 using adupdeul.sh mode=complete

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.

Check Your Location

On the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed, move to the mounted or copied ... /discover/ directory where adupdeul.sh is located

Improving the Speed of the Import Process

Performance of the import process greatly depends on:

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.

Start the Import Process

Start the import process of the Discoverer loader files (.eex files) using the shell script adupdeul.sh.

Use the following syntax for the  adupdeul.sh script:

% 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=USeulprefix=<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 contentEDW - for Enterprise Data Warehouse Discoverer content

Use eultype=OLTP to import the Discoverer 10.1.2 content for Oracle E-Business Suite Release 12

mode COMPLETE - import all Discoverer content. DRIVER - default, import specific subset of filesFILELIST - import specific subset of files

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:

All parameters must be specified on a single command line or in a parameter file. Name-value pairs must not contain spaces.  For example:

PARAMETER=VALUE  is acceptable

PARAMETER  =  VALUE  will generate errors

For example:

Mount or copy the directory $AU_TOP/discover as /user1/au_top/discover

cd /user1/au_top/discover (where adupdeul.sh is located)

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 

Check for Import Errors

Check the logfile after import. This should be a clean import logfile. You should be able to see that the import utility exited with status 0 and the logfile contains the message Import completed successfully.

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.

<topdir>\<language>\<file>.eex: The identifier for ... contains one or more of the characters ! ~ - * ( ) ' which will be de-supported for use in identifiers in future releases of Discoverer - see release notes for more details.

Check Your Location

Move to the ... /discover/ directory where adrfseul.sh is located.

Start the Refresh Process

Syntax for the  adrfseul.sh script:

% sh adrfseul.sh connect=<APPS admin user>/<password>@<twotask>resp=<APPS administrator responsibility>gwyuid=<APPS GWYUID>fndnam=<APPS FNDNAM>secgroup=<APPS security group>eulschema=<eul schema>eulpassword=<eulpassword>twotask=<twotask>iashome=<iashome>[logfile=<logfile>][parfile=<parfile>]

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:

All parameters must be specified on a single command line or in a parameter file. Name-value pairs must not contain spaces.  For example:

PARAMETER=VALUE  is acceptable

PARAMETER  =  VALUE  will generate errors

For example, change your directory to the location of adrfseul.sh:

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.

Grant Privileges, Security and Workbook Access on Unix

You must grant security access to the Oracle E-Business Suite Release 12 responsibilities you would like to use for each Business Area.

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.

For help on usage of the eulapi command-line utility, type:

$ORACLE_HOME/bin/eulapi -help grant_privilege

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:

<OracleHome>\bin\dis5adm.exe /CONNECT "SYSADMIN:System Administrator/<password>@<db>" /EUL <EULprefix>_<Lang>

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.

Using Tools -> Privileges

Check "User Edition" privileges for all E-Business Suite Users and Responsibilities who should be allowed to open workbooks.

Using Tools -> Security

Grant Business Area access to E-Business Suite Users and Responsibilities who should be allowed to query the various Business Areas.