April 2005
Availability
Oracle E-Business Suite Release 11i is certified for integration with Oracle Discoverer 10g (9.0.4). Discoverer 9.0.4 must be installed in a separate Oracle Application Server 10g ORACLE_HOME on an existing application tier server node or on a standalone server, accessing an Oracle E-Business Suite Release 11i database.
Althought this Metalink Note will continue to be published for reference purposes, Oracle strongly recommends that customers interested in using Discoverer with the E-Business Suite use the latest certified version: Discoverer 10.1.2.. See MetaLink Note 313418.1 titled, Using Discoverer 10.1.2 with Oracle E-Business Suite 11i.
Usage of additional Oracle Application Server 10g components Oracle Single Sign-On, Oracle Internet Directory and Oracle Portal for integration with Oracle E-Business Suite Release 11i is documented in MetaLink Note 233436.1 titled, Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i.
________________________________________
This document contains information for using OracleAS Discoverer 10g (9.0.4) from Oracle Application Server 10g with Oracle Applications 11i. You should read and understand all content described here before you begin using this feature. The most current version of these notes is 257798.1 on OracleMetaLink. There is a change log at the end of this document.
• Section 1: Overview
• Section 2: Supported Architectures
• Section 3: Release Versions
• Section 4: Preinstallation Tasks
• Section 5: Installation Tasks
• Section 6: Postinstallation Tasks
• Section 7: Available Documentation
• Section 8: Conventions and Important Directory Locations
• Section 9: Installation of Additional Discoverer End User Layer patches
• Section 10: Known Issues and Limitations
________________________________________
Section 1: Overview
OracleAS Discoverer 10g, a key component of Oracle Application Server 10g, is an integrated business intelligence solution supporting intuitive ad hoc query, reporting, analysis, and web publishing. Business users at all levels of the organization can use Discoverer 10g to gain immediate access to information from data marts, data warehouses, and online transaction processing (OLTP) systems. Discoverer 10g enables report builders and analysts to create, modify, and execute ad hoc queries and reports. Casual users can view and navigate through predefined reports and graphs through business views that hide the complexity of the underlying data structures being reported upon.
Discoverer 10g is tightly integrated with Oracle E-Business Suite Release 11i. Release 11i users can use Discoverer to analyze data from selected business areas in Financials, Operations, Human Resources, Purchasing, Process Manufacturing, Activity Based Management, and more.
This document describes how to install Discoverer 10g into an existing Oracle E-Business Suite Release 11i environment. Installation of Discoverer 10g into an Oracle E-Business Suite Release 11i environment consists of:
• Installation of Discoverer 10g with Oracle Application Server 10g on a standalone application tier server node
• Creation of the Discoverer 10g End User Layer (EUL) on a database tier server node
• Import of the Oracle E-Business Suite Release 11i Discoverer content into the Discoverer 10g End User Layer
• (Optional) Installation of Discoverer Administration Edition on a Windows-based PC that can be used to customize Discoverer
For current Discoverer users, it also describes how to upgrade an existing Discoverer End User Layer from Discoverer 3i or 4i to Discoverer 10g.
The procedures in this document have significant effects on Oracle E-Business Suite Release 11i environments and should be executed only by skilled Oracle E-Business Suite database or systems administrators. Users are strongly advised to make backups of their environments before executing any of the procedures noted, and to test their environments before executing these procedures in production environments. Users must log off the system while these changes are being applied.
Availability of Translations
Discoverer content for Oracle E-Business Suite Release 11i includes workbooks and the End User Layer for both regular Applications modules as well as Business Intelligence System (BIS) products such as Financials Intelligence and Purchasing Intelligence. This content is available only in US English, and there are no translations planned for other languages.
________________________________________
Section 2: Supported Architectures
Discoverer 10g must be installed in a separate ORACLE_HOME on an existing application tier server node or on a stand-alone server, accessing an Oracle E-Business Suite Release 11i database.
________________________________________
Section 3: Release Versions
The following components must be used on the stand-alone instance:
Component Name Version
Oracle Application Server Enterprise Edition 10g
The following components must be used on the Oracle E-Business Suite Release 11i instance:
Component Name Version
Oracle E-Business Suite Release 11i 11.5.8 to 11.5.10
________________________________________
Section 4: Preinstallation Tasks
1. Read Discoverer 10g Configuration Guide
Chapter 1 of the Oracle Application Server Discoverer Configuration Guide 10g (9.0.4) explains how to run, maintain and support OracleAS Discoverer. At minimum, review this chapter before proceeding further.
2. Preserve Discoverer 3i Customizations (optional)
Skip this step if you are upgrading an existing Discoverer 4i End User Layer or if you are installing a Discoverer End User Layer for the first time.
If you are upgrading from Discoverer 3i to Discoverer 10g, you may wish to preserve your existing custom workbooks and business areas. Custom business areas built in Discoverer 3.1 may be migrated to the new Discoverer 10g End User Layer if:
They do not reference any Oracle delivered content
They use only Display Names which do not conflict with the Oracle delivered content, for example, by using a custom prefix
Migration of Discoverer 3i content to Discoverer 10g is a two-step process:
2.1 Migrate Discoverer 3i End User Layer customizations to Discoverer 4i
Refer to Note 139516.1 on OracleMetaLink for migration of Discoverer 3i customizations to Discoverer 4i.
2.2 Migrate Discoverer 4i End User Layer to Discoverer 10g
Continue with migration of your existing Discoverer 4i End User Layer to Discoverer 10g as detailed below.
________________________________________
Section 5: Installation Tasks
This section outlines steps required to install Oracle Application Server 10g, Discoverer 10g, and the Discoverer 10g End User Layer. See Section 8: Conventions and Important Directory Locations for important information about entering commands listed in this section.
1. Install Oracle Application Server 10g Enterprise Edition
Oracle Application Server 10g Enterprise Edition includes Discoverer Server 10g, Discoverer Plus 10g, and Discoverer Viewer 10g. You must install OracleAS 10g Infrastructure and OracleAS 10g Business Intelligence and Forms middle tier in separate ORACLE_HOMES on an existing application tier server node, or on a standalone server accessing an Oracle E-Business Suite Release 11i database.
You must install Oracle10g Application Server Enterprise Edition by following the instructions in the Oracle Application Server 10g Installation Guide for your operating system platform. In particular for details on the OracleAS 10g topology and installation sequence please refer to section 11.3 in the Oracle Application Server 10g Installation Guide.
Note
If you already have an existing integrated AS Discoverer 10g (9.0.4) instance you can upgrade this instance to the latest certified patch level following Step 2 below.
2. Apply the latest certified Oracle Application Server 10g Discoverer patches
2.1 Apply Oracle Application Server 10g Patchset 9.0.4.1
Download patch 3784229 ORACLE AS 10G (9.0.4) PATCH SET (9.0.4.1.0) for your appropriate Discoverer Server node platform from Oracle Metalink.
Follow the installation instructions provided in the patch README to install the patch on your Discoverer Server node.
2.2 Apply MLR Patch on top of 9.0.4.1
Download the appropriate platform-specific one-off patch for your Discoverer Server node from Oracle Metalink.
Operating System Platform
Sun Solaris (SPARC) Microsoft
Windows HP HP/UX 11.0 IBM AIX Linux
3700386
3700386
3952149
4034160
3891698
Follow the installation instructions provided in the patch README to install the patch on your Discoverer Server node.
3. Install Internet Developer Suite 10g (Optional)
3.1. Install Internet Developer Suite 10g on a Windows PC
If you wish to use Discoverer Administration Edition to customize your Discoverer End User Layer, install Internet Developer Suite 10g containing Discoverer 10g Administration Edition on a Windows PC.
3.2. Apply the latest certified Discoverer Administration Edition Patchset
Download patch 3628736 DEVELOPER SUITE 10G (9.0.4) PATCH SET 1 (9.0.4.1.0) from Oracle Metalink and follow the installation instructions provided in the patch README to install the patch on your Discoverer Administration Edition Server.
3.3. 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.
Attention
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 number in the Microsoft Knowledge Base :
Q256986 Description of the Microsoft Windows Registry
On the Windows PC running Discoverer 10g Administration Edition:
3.3.1 Back up your current Microsoft Windows Registry
3.3.2 Open the Windows Registry editor and create or update the following registry keys:
Registry Key DataType Value
HKEY_CURRENT_USER\Software\Oracle\Discoverer 9\
Database\EnableTriggers REG_DWORD 1
HKEY_CURRENT_USER\Software\Oracle\Discoverer 9\
Database\DefaultPreserveDisplayPropertyForRefresh REG_DWORD 1
4. Specify Connect Dialog for Oracle Applications Users
If you use the Discoverer 10g Connection Management pages for direct login using Oracle Applications User/Password authentication, you must set up the Connect dialog to display the Applications User checkbox.
4.1. Open the file
4.2. Set the DefaultUserTypeIsApps preference to "1"
4.3. Set the ShowUserTypeChoice preference to "1"
4.4. Save the updated pref.txt file.
4.5. On UNIX, run the script
4.6. Stop and restart the OracleDiscoverer10g service to refresh the environment with the updated preferences
For details about other options that may be set for direct login, please refer to Chapter 13 of the Oracle Application Server Discoverer Configuration Guide 10g (9.0.4)
Note
Users may enter their user ID and Applications responsibility in the Connect dialog using the format:
UserID:
If you append a colon : immediately after the user in the Discoverer Connect dialog without specifying a responsibility after the colon, Discoverer will always try to establish a connection as an Oracle Applications user and pop up a list of valid Applications responsibilities for this Applications user.
5. Migrate your existing Discoverer 4i End User Layers to Discoverer 10g.
If you do not have an existing Discoverer 4i End User Layer, skip this step and proceed with Step 6 .
Upgrade your existing Discoverer 4i End User Layer to Discoverer 10g by using the following command on the standalone application server where Oracle Application Server 10g and Discoverer 10g were installed in Step 1 .
$ORACLE_HOME/bin/eulapi -CONNECT
The upgrade process creates a new Discoverer 10g End User Layer based the existing Discoverer 4i End User Layer. The existing Discoverer 4i End User Layer remains unchanged. A new schema containing the Discoverer 10g End User Layer will be created under the same Database User. After migration, the Database User contains both functional 4i and 10g euls. After verification of successful upgrade, you should drop the 4i eul.
6. Create new Discoverer 10g End User Layer
You must create a new Discoverer 10g End User Layer if you do not have an existing Discoverer 4i End User Layer.
We recommend that you create a new tablespace to store database objects for the Discoverer 10g End User Layer in your Oracle Applications database.
6.1. 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]/
6.2. 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 /NOLOG
SQL> connect sys/
SQL> create tablespace DISCOVERER datafile \
'[DB_ORACLE_HOME]/dbf/discoverer01.dbf' size 200M reuse \
extent management local uniform size 128K;
SQL> /
Statement Processed
6.3. Exit SQL*Plus:
SQL> quit
6.4. Create the new Discoverer 10g End User Layer by using the following command, executed on the standalone application server where Oracle Application Server 10g and Discoverer 10g were installed in Step 1 .
$ORACLE_HOME/bin/eulapi
-CREATE_EUL
-APPS_MODE
-CONNECT system/
-USER
-PASSWORD
-DEFAULT_TABLESPACE
-TEMPORARY_TABLESPACE
-EUL_LANGUAGE US
-APPS_GRANT_DETAILS
This command should be entered on a single command line -- it is shown above on separate lines with extra spaces for ease of reference only.
For example:
$ORACLE_HOME/bin/eulapi -CREATE_EUL -APPS_MODE \
-CONNECT system/manager@cus115 -USER EUL_US -PASSWORD EUL_US \
-DEFAULT_TABLESPACE discoverer -TEMPORARY_TABLESPACE temp \
-EUL_LANGUAGE US -APPS_GRANT_DETAILS apps/apps
Note for Windows
%ORACLE_HOME%\bin\eulapi is not available with AS 10g Discoverer Version 9.0.4 on Windows. Please use following syntax instead:
%ORACLE_HOME%\jdk\bin\java -jar %ORACLE_HOME%\discoverer\lib\eulbuilder.jar
Alternatively you may also use the equivalent Discoverer Administration Edition command line on Windows. Use the following syntax to create the eul using Discoverer Administration Edition:
%ORACLE_HOME%/bin/dis51adm.exe /CREATE_EUL /APPS_MODE \
/CONNECT system/manager@cus115 /USER EUL_US /PASSWORD EUL_US \
/DEFAULT_TABLESPACE discoverer /TEMPORARY_TABLESPACE temp \
/EUL_LANGUAGE US /APPS_GRANT_DETAILS apps/apps /SHOW_PROGRESS
6.5 Check max_extents for default rollback segments
The import and the refresh processes for the entire Applications 11i End User Layer - the complete set of .eex files - are large database transactions. Check that the default rollback segment where the Discoverer End User Layer is to be installed is large enough to support rolling back a 70 MB transaction at minimum:
6.5.1. Log on to SQL*Plus:
% sqlplus system/
6.5.2. Issue the following SQL command:
SQL> select SEGMENT_NAME, TABLESPACE_NAME, BYTES, BLOCKS, EXTENTS \
from DBA_SEGMENTS where SEGMENT_TYPE = 'ROLLBACK';
6.5.3. If the rollback segment for the tablespace where you plan to install the Discoverer End User Layer is less than 70 MB, you must either alter it or create a new rollback segment. Procedures for accomplishing this will vary depending upon your database configuration; see the Administrator's Guide for your Oracle database for more details.
7. Verify Java Virtual Machine for Discoverer Plus
Chapter 4.12 of the Oracle Application Server Discoverer Configuration Guide 10g (9.0.4) explains how to run Discoverer Plus with different Java Virtual Machines. Please note that Discoverer 10g is not supported to run with JInitiator 1.1.8. You must use JInitiator 1.3.
For more information on JInitiator please refer to MetaLink Note 124606.1 titled "Upgrading Oracle JInitiator with Oracle Applications 11i".
________________________________________
Section 6: Postinstallation Tasks
This section describes steps for configuring Oracle E-Business Suite Release 11i to use Discoverer 10g, and for loading the Applications-specific content and workbooks into the Discoverer 10g End User Layer.
1. Apply necessary Oracle Applications interoperability patches using AutoPatch
Note
If your environment was created using Oracle E-Business Suite Release 11.5.10 Rapid Install you can skip this step and proceed with Step 2. Oracle Applications interoperability patches are installed by default in Oracle E-Business Suite Release 11.5.10 Rapid Install.
1.1 Apply AD patch 3440628
This patch contains utilities for Discoverer End User Layer maintainance.
Download patch 3440628 from Oracle Metalink.
Follow the instructions in the README to apply the patch
1.2 Apply ICX patch 3133021
This patch contains support to invoke Discoverer from E-Business Suite functions.
Download patch 3133021 from Oracle Metalink.
Follow the instructions in the README to apply the patch
1.3 Apply the latest AutoConfig patch
Follow MetaLink Note 165195.1 titled "Using AutoConfig to Manage System Configurations with Oracle Applications 11i" and apply the latest available AutoConfig Patch to your system.
2. Set Applications Profile Options for Discoverer using AutoConfig
By default, AutoConfig configures profile options for Oracle E-Business Suite Release 11i environments for Discoverer 4i. Proceed with the following steps to allow AutoConfig switch profile options for your remote, standalone OracleAS Discoverer 10g server:
Edit the AutoConfig context file.
If you are currently using E-Business Suite level 11.5.9 or above, or have applied FND.G patchset (or above), you will use Oracle Applications Manager to edit your context file. For all previous versions, you will use the AutoConfig Context Editor tool.
To edit the context file using Oracle Applications Manager, login to Oracle Applications Manager and navigate to Site Map > AutoConfig > Edit Parameters.
To edit the context file using the AutoConfig Context Editor tool, enter the following commands:
% cd [COMMON_TOP]/util/editcontext/
% ./editcontext
Specify variables as listed in the table below:
Title Variable Name Description Value
Configure standalone discoverer s_disco_standalone Set the value of this variable to 'true' if E-business suite 11i is configured to use a standalone discoverer server true
Discoverer machine name s_disco_machine Set the value of this variable to the machine configured to run discoverer services
for example: ap6162rt.us.oracle.com
Discoverer port s_disco_port Set the value of this parameter to the port on which the http listener is listening for discoverer requests
for example: 7778
Discoverer protocol s_disco_protocol Set the value of this variable to the appropriate protocol used for accessing discoverer. Acceptable values for this parameter are http or https http|https
Disco Version Comma s_disco_ver_comma Disco Version 10
Discovery EUL prefix s_disco_eul_prefix Discovery EUL prefix EUL
Note
Other Discoverer related AutoConfig parameters are not relevant for Discoverer 10g configuration because AutoConfig does not control configuration of the remote, standalone OracleAS Discoverer 10g server node.
The changes will be saved in your Applications Context File
Run AutoConfig to generate all configuration files for the APPL_TOP and the ORACLE_HOMEs in its supporting technology stack:
For further information about AutoConfig please refer to MetaLink Note 165195.1 titled "Using AutoConfig to Manage System Configurations with Oracle Applications 11i".
3. Verify Applications profile options in Oracle Applications
• Log into Release 11i with the System Administrator responsibility
• Navigate to the Profile > System form
• Query the %Discoverer% profile options.
• Verify the following ICX profile options in Oracle Applications:
Profile Description Value
ICX_DISCOVERER_LAUNCHER URL that points to Discoverer Server Launch page http://
/discoverer/plus
?Connect=[APPS_SECURE]
ICX_DISCOVERER_VIEWER_LAUNCHER URL that points to Discoverer Viewer Servlet http://
/discoverer/viewer
?Connect=[APPS_SECURE]
ICX_DISCOVERER_RELEASE 1 digit number specifying the Discoverer release 10
ICX_DISCOVERER_USE_VIEWER Specify whether Discoverer Viewer should be launched instead of Discoverer Plus (default). Y | N
ICX_DEFAULT_EUL ICX: Discoverer End User Layer Schema Prefix
This is the EULprefix. The EULprefix in combination with the Language code make up the EUL owner at runtime. EUL
ICX_DISCOVERER_EUL_LANGUAGE 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. US
ICX_DISCOVERER_PARAMETERS ICX: Discoverer Parameters
This profile may be used to optionally pass additional URL parameters to Discoverer. Compare Note 186120.1 on Oracle MetaLink.
Note
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.
4. Verify Location of Database Connection file
Discoverer 10g supports Single Sign-On functionality with Oracle E-Business Suite Release 11i. To support Single Sign-On, 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 10g Discoverer
Note
The naming convention for the .dbc file for Oracle E-Business Suite Release 11.5.1 to 11.5.9 is
The name is derived from:
select lower(host_name) || '_' || lower(instance_name) from v$instance;
The naming convention for the .dbc file for Oracle E-Business Suite Release 11.5.10 is
Discoverer will attempt to find the dbc file in following order
1. $FND_TOP/secure/
2. $FND_TOP/secure/
Make sure $FND_TOP is set correctly for the user who starts the Discoverer service.
On Solaris variable FND_TOP is set in the environment script
On Windows NT, make sure the FND_TOP variable is set as a Windows System Variable.
For more information about dbc files see Appendix 'Setting up and maintaining Oracle Applications' of the Oracle Applications System Administrators Guide .
5. Update tnsnames.ora file
On your standalone Oracle Application Server 10g node, update file $ORACLE_HOME/network/admin/tnsnames.ora and include the tnsnames entry to connect to your Oracle E-Business Suite Release 11i database. Use the same entry as exists in the tnsnames.ora file on your Oracle E-Business Suite Release 11i mid 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 11i database using sqlplus.
________________________________________
The remaining steps include patching your End User Layer to the latest level and are required only if you received new eex files, for example if you migrate to Discoverer 10g as part of uptaking a E-Business Suite 11i Maintainance Pack release, or if you implement the Discoverer End User Layer for the first time.
If you have only migrated your existing 4i End User Layers to Discoverer 10g without patching new eex files, you can skip the remaining steps in this section and proceed with Section 7.
________________________________________
6. Regenerate your Business Views
Most of the Discoverer folders delivered as part of the Oracle E-Business Suite Release 11i Discoverer content are based on Business Views. Business Views hide the complexity of the underlying Release 11i data model from non-technical users. Before you import or refresh the Discoverer .eex files you must regenerate all Business Views. This will enable the Discoverer import and refresh process to pull in the translated prompts for Key and Descriptive Flex Fields of your Business Views into your End User Layer. Make sure that every flexfield structure has at least one valid segment, and that all flexfields are frozen and compiled.
6.1. Apply Business View Generator patch patch 2921686 using AutoPatch.
6.1.1. Download the Business View Generator patch 2921686 from Oracle Metalink
6.1.2. Follow the instructions in the README to apply the patch.
6.2. Regenerate your Business Views by running the "Generate Business Views by Application" concurrent program using the Business View Setup responsibility:
Logon to Oracle Applications as SYSADMIN
Choose the "Business Views Setup" responsibility
Navigate to Reports > Run > Pick Single Request > "Generate ALL Business Views"
For additional details and background, refer to the Oracle Applications Flexfields Guide .
6.3. After regeneration of the Business Views has been completed, check the Business View Generator output file. It should not contain any errors.
6.4. Recompile all objects in the APPS schema using adadmin.
6.5. 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/
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_%' );
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.
Attention
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 Applications objects during the refresh process.
7. Set up Applications User/Responsibility for EUL Administration: SYSADMIN/System Administrator
The Release 11i System Administrator account must be granted permission to update and alter Discoverer 10g content.
7.1. 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 Application Server 10g and Discoverer 10g were installed in Step 1 .
$ORACLE_HOME/bin/eulapi \
-CONNECT
-GRANT_PRIVILEGE \
-USER SYSADMIN \
-PRIVILEGE administration \
-PRIVILEGE all_admin_privs \
-LOG
For all further End User Layer Administration activities you must use the Oracle Applications User with the System Administrator responsibility (e.g. SYSADMIN). This Applications user must import and own the Workbooks and Business Areas of all future Discoverer patches and share them as applicable with other Applications users and responsibilities.
7.2. 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 Application Server 10g and Discoverer 10g were installed in Step 1 .
$ORACLE_HOME/bin/eulapi \
-CONNECT
-GRANT_PRIVILEGE \
-USER SYSADMIN \
-BUSINESS_AREA_ADMIN_ACCESS % \
-WILDCARD \
-LOG
Note for Windows
%ORACLE_HOME%\bin\eulapi is not available with AS 10g Discoverer Version 9.0.4 on Windows. Please use following syntax instead:
%ORACLE_HOME%\jdk\bin\java -jar %ORACLE_HOME%\discoverer\lib\eulbuilder.jar
8. Mount Application Tier Server Node $AU_TOP/discover to Oracle10gAS BI instance
Discoverer .eex files are patched to your application tier server node, directory $AU_TOP/discover . Those files must be accessible from the standalone application server where Oracle Application Server 10g and Discoverer 10g were installed.
Please mount your applications tier server node, directory $AU_TOP/discover on your standalone application server where Oracle Application Server 10g and Discoverer 10g were 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 Application Server 10g and Discoverer 10g were 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.
9. Import Discoverer Content for Release 11i using adupdeul.sh mode=complete
In this step, you will run AD utility adupdeul.sh on the standalone application server where Oracle Application Server 10g and Discoverer 10g were installed to import the Discoverer loader files (.eex files) for Oracle E-Business Suite Release 11i into the Discoverer End User Layer.
9.1. On the standalone application server where Oracle Application Server 10g and Discoverer 10g were installed, move to the mounted or copied ... /discover/ directory where adupdeul.sh is located
9.2. Start the import process of the Discoverer loader files (.eex files) using the shell script adupdeul.sh.
Syntax for the adupdeul.sh script:
% sh adupdeul.sh
connect=
resp=
gwyuid=
fndnam=
secgroup=
topdir=
language=US
eulprefix=
[iashome=
[exedir=
[eultype=
[mode=
[driver=
[filelist=
[logfile=
[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 node Oracle Home directory
Required on UNIX platforms
exedir Directory where Discoverer executables are located
Required on Windows platforms
eulprefix EUL schema prefix, for example use Use eulprefix=EUL for schema EUL_US
eultype OLTP - default, for standard Applications 11i Discoverer content
EDW - for Enterprise Data Warehouse Discoverer content
Use eultype=OLTP to import the Discoverer 10g content for Oracle E-Business Suite Release 11i
mode COMPLETE - import all Discoverer content.
DRIVER - default, import specific subset of files
FILELIST - import specific subset of files
For the initial full import of the Discoverer 10g baseline files delivered by patch 1834171 , 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
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_cust115.log
The above example is displayed on multiple lines for clarity; do not type the backslash.
9.3. Performance of the import process greatly depends on network latency between the Oracle10gAS node and the database, and on available resources on your Oracle10gAS 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 Oracle10gAS be installed on a machine that is close to the database server and has a fast network connection.
9.4. 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:
This messages provides information that
You can safely ignore this message using Discoverer 10g. See release notes for more details.
9.5. As Release 11i products continually update and improve support for Discoverer in subsequent releases, it will be necessary to install additional Discoverer loader files after this initial installation. Please refer to Section 9 for details on importing subsequent patches using mode=driver.
10. Refresh the Discoverer 10g End User Layer
After the Discoverer 10g content for Release 11i has been imported into the Discoverer End User Layer on the database tier, the End User Layer must be refreshed against the Release 11i data model. This ensures that all references between business areas, folders, workbooks, business views, flexfields, and Release 11i database objects are valid.
On Unix platforms you may run the refresh process on the standalone application server where Oracle Application Server 10g and Discoverer 10g were installed.
Alternatively on Windows platforms you may run the refresh process on the machine where Discoverer Administration Edition is installed.
10.1. Move to the ... /discover/ directory where adrfseul.sh is located.
10.2. Start the refresh process against the database using the shell script adrfseul.sh.
Syntax for the adrfseul.sh script:
% sh adrfseul.sh
connect=
resp=
gwyuid=
fndnam=
secgroup=
eulschema=
eulpassword=
twotask=
[iashome=
[exedir=
[logfile=
[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 node Oracle Home directory
Required on UNIX platforms
exedir Directory where Discoverer executables are located
Required on Windows platforms
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
Example:
cd /user1/au_top/discover (where adrfseul.sh is located)
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
The above example is displayed on multiple lines for clarity; do not type the backslash.
Note
For the refresh process you must use the Applications User/Responsibility SYSADMIN:System Administrator to logon rather than the End User Layer database schema owner. The End User Layer database schema owner doesn't have the necessary grants for the APPS schema and the refresh process would drop Discoverer folders! Using adrfseul.sh for the refresh enforces using Applications User/Responsibility in the connect string.
For all Business Areas expect several hours for the refresh process to complete, depending on your flex structure. 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.
11. Grant Access to Responsibilities, Users, and Workbooks (optional)
Individual Discoverer users may be granted access to specific Release 11i responsibilities, which in turn provide access to Discoverer business areas and workbooks. Either the Discoverer 10g eulapi UNIX command-line utility or Discoverer 10g Administration Edition can be used to associate business area access with Release 11i responsibilities, and to identify workbook access privileges for responsibilities and users.
The procedures described in this step may be used as guidelines for planning your Discoverer reporting security. Your Discoverer reporting strategy may be defined to reflect your corporate data security strategy, policies, and business requirements. Discoverer security is flexible and highly granular, and you may wish to provide broader access for specific individuals who need to be able to see data enterprise-wide, i.e. across organizational boundaries.
Example: You may wish some Financial analysts to have access to all of the Financials Intelligence business areas, such as the Accounts Payables and Accounts Receivables. To do this, grant access to all of the Financials Intelligence business areas to the Financials Intelligence responsibility. The Financials Intelligence responsibility may then be granted to the individual Financial analysts who should have access to those areas.
Note
If you have upgraded to the Oracle Applications 11.5.8 Maintenance Pack or later Maintenance Pack releases, you can skip this step.
The 11.5.8 Maintainance Pack and later Maintenance Pack releases already include all necessary security grants and workbook sharing for the pre-seeded Oracle Applications responsibilities. If you wish to grant security access for Business Areas to Oracle Application users and responsibilities in addition to the grants that are provided with the 11.5.8 Maintenance Pack and higher, you may optionally follow the procedures listed in this step.
11.1 Grant Privileges, Security and Workbook Access on Unix
For information about delivered Business Areas with Oracle E-Business Intelligence Suite please refer to Chapter 4 of the Oracle Business Intelligence System Implementation Guide . You must grant security access to the Oracle Applications responsibilities you would like to use for each Business Area.
You may use the Discoverer 10g eulapi command line utility on the standalone application server where Oracle Application Server 10g and Discoverer 10g were installed in Step 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 "Financials Intelligence"
$ORACLE_HOME/bin/eulapi \
-CONNECT
-GRANT_PRIVILEGE \
-ROLE "Financials Intelligence" \
-PRIVILEGE all_user_privs
Example 2:
Grant security access for business area "General Ledger" to responsibility "Financials Intelligence"
$ORACLE_HOME/bin/eulapi
-CONNECT
-GRANT_PRIVILEGE \
-ROLE "Financials Intelligence" \
-BUSINESS_AREA_ACCESS "General Ledger"
11.2. Grant Security and Privileges using Discoverer Administration Edition on Windows
If you have already granted security and privileges using the Discoverer 10g eulapi command-line utility, you may skip this step.
Log in to the Discoverer Administration Edition 9.0.4 as the Applications 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 (
Using Tools -> Privileges
Check "User Edition" privileges for all Applications Users and Responsibilities who should be allowed to open workbooks.
Using Tools -> Security
Grant Business Area access to Applications Users and Responsibilities who should be allowed to query the various Business Areas.
11.3 Share Workbooks using Discoverer Plus Edition
You must grant shared workbook access to the Oracle Applications responsibilities to be used for workbook analysis.
1. Log in to the Discoverer User Edition 9.0.4 as the Applications Administration user who imported the eex files in Section 6, Step 8 .
2. Use the Help -> About Discoverer... dialog to confirm that you are connected to the correct End User Layer (
3. Using the File -> Manage Workbooks... -> Sharing... dialog
Share the workbooks to the Applications Users and Responsibilities that should be allowed to open the various workbooks.
11.4. Test Discoverer Responsibilities and Workbooks
Log in to Oracle E-Business Suite Release 11i with a userid that has been granted one of the responsibilities defined above.
Open the Release 11 workbooks assigned to that responsibility and verify that they can retrieve and display data.
Repeat for each responsibility that has been defined.
Congratulations!
You have completed your Discoverer 10g implementation and your Discoverer content for Oracle E-Business Suite Release 11i products is ready for use.
________________________________________
Section 7: Available Documentation
For a summary of installation and configuration documentation for Oracle Application Server 10g and its associated components, see the following Note on Oracle Metalink :
Oracle Application Server (10gAS) with Oracle E-Business Suite Release 11i Documentation (Note 207159.1)
________________________________________
Section 8: Conventions and Important Directory Locations
Conventions
The following typographical conventions are used in this document:
Convention Meaning
\ In examples of commands you type online, a backward slash at the end of a line signifies that you must type the entire command on one line. Do not type the backslash.
Mono space text Represents command line text. Type this text exactly as shown.
<> or [] Text enclosed in angled or square brackets represents a variable. Substitute an appropriate value for the variable text. Do not type the brackets.
Directory Paths Directory paths in this document are relative to the top level installation directory for the Oracle E-Business Suite. e.g. if you installed the Oracle E-Business Suite under a directory named /my/appsinstall and are pointing to an Oracle E-Business Suite Release 11i database named mytestdb, then
No comments:
Post a Comment