Using Discoverer 10

Using Discoverer 10.1.2 with Oracle E-Business Suite 11i

Section 1: Preinstallation Tasks

Step 1: Download Aplication 10.1.2 software.

as_linux_x86_bi_101202_disk1.cpio

as_linux_x86_bi_101202_disk2.cpio

Step 2: extract the s/w using the following command.

cat as_linux_x86_bi_101202_disk1.cpio |cpio idmvcat as_linux_x86_bi_101202_disk2.cpio |cpio idmv

Step 3: Check the operating system requirements (vi /etc/sysctl.conf). and change accordingly in sysctl.conf file and save it (take the backup of the file).#vi /etc/sysctl.conf

net.ipv4.ip_forward = 0

net.ipv4.conf.default.rp_filter = 1

net.ipv4.conf.default.accept_source_route = 0

kernel.sysrq = 0

kernel.core_uses_pid = 1

kernel.shmall = 2097152

kernel.shmmax = 4294967295

kernel.shmmni=4096

kernel.msgmni = 2878

kernel.msgmax = 8192

kernel.msgmnb = 65535

fs.file-max = 206173

net.ipv4.ip_local_port_range = 10000 65000

net.core.rmem_default = 1048576

net.core.rmem_max = 1048576

net.core.wmem_default = 262144

net.core.wmem_max=262144

kernel.sem = 256 32000 100 142

kernel.hostname = aqherptestdb

kernel.domainname = qudrah.com and follow the README.txt instruction from under this directory

Disk1/utils/3167528 ( where you extracted the s/w.Step 4: create one folder Discoverer. (Name is Optional, here I created erpdisk under /s03/ERP)

$cd /s03/ERP$mkdir erpdiskSection2: Installation Task.Step 1: Install Discoverer.

1. goto Disk1 and execute the ./runInstaller command

2. it will open the Installer Dialog box. Select Next

3. Select appropriate Path by Clicking the Browse button (ex:- /s03/ERP/erpdisk) and Click Next.

4. it will check the Operating system requirements, all should meet the requirements then only proceed to Next.

5. Select Language and click on Next.

6. Select automatic and click on Next.

7. Give the SMTP server address in my case it is (aqre-owa.qudrare.ae). and click on Next.

8. give the name of the Instance (ex:- ERP) and enter the ias_admin password, And Click Next.

9. Click on Install button.

10. It will start the installation process.

11. End of the installation it will ask you to run the root.sh file from the user as seen in the dialog box.In my case it is (/s03/ERP/erpdisk/root.sh). run the file from root and click ok.

12. Then it will do configuration wait till it completes and click on NEXT.

13. Copy the links from the end of installation Dialog box and click on Exit.

14. Open the URL which you copied in Internet Explorer using ias_admin user and the Password which you have given in previously, from here you can start and stop all the services of the discoverer.

Step 2: set the environment for Discoverer in .bash_profileEx:-export LD_ASSUME_KERNEL=2.4.19

export ORACLE_BASE=/s03/ERP

export ORACLE_SID=ERP

export ORACLE_TERM=xterm

export NLS_LANG=AMERICAN

export ORACLE_HOME=$ORACLE_BASE/erpdisk

export OPATCH=$ORACLE_HOME/OPatch

export TNS_ADMIN=/s03/ERP/erpdisk/network/admin

PATH=$PATH:$HOME/bin:$ORACLE_HOME:$ORACLE_HOME/bin:$TNS_ADMINStep 3 : Copy Database Connection file.In the Discoverer10g$ORACLE_HOME/opmn/conf/opmn.xmlfile check the variable forFND_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/secureif it does not exist. Then copy the dbc file from the$FND_TOP/securedirectory of the 11i instance you are setting up Discoverer with to the Discoverer 10.1.2$ORACLE_HOME/discoverer/securedirectory you just created.

Step 4: Update tnsnames.ora file

On your standalone Oracle Business Intelligence Server 10g Release 2 node, update file$ORACLE_HOME/network/admin/tnsnames.oraand include thetnsnamesentry to connect to your Oracle E-Business Suite Release 11i database. Use the same entry as exists in thetnsnames.orafile on your Oracle E-Business Suite Release 11i application tier server node. The database name must match thetwo_taskentry in the dbc file. Verify you can establish a connection to your Oracle E-Business Suite Release 11i database usingsqlplus.

Step 5: create tablespace for the Discoverer in your 11iApplication Database.

$sqlplus /NOLOGSQL> connect sys/ as sysdbaSQL> create tablespace DISCOVERER datafile \ '[DB_ORACLE_HOME]/dbf/discoverer01.dbf' size 200M reuse \ extent management local uniform size 128K;SQL> /Statement ProcessedStep 6: Stop the opmn services.

Goto $DISCOVERER ORACLE_HOME.

Ex:-

$cd /s03/ERP/erpdisk/opmn/bin

$ ./opmnctl stopall ( it will stop all the services. Either ypu can use with the Discoverer link.

Step 7: Apply the latest certified Discoverer Plus and Viewer Patches.5983622 - Oracle Discoverer 10.1.2.3. ( Apply this patch on the top of the Oracle Discoverer folder

(ex:- /s03/ERP/erpdisk), while running this patch it will ask for the path where you installed the Discoverer 10.1.2 then we need to mention the path then it will upgrade the version to 10.1.3.

7111842 - Apply Cumulative Patch.Step 8: Create new Discoverer 10.1.2 End User Layer.Create the new Discoverer 10.1.2 End User Layer by using the following command, executed on the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed.

$ORACLE_HOME/bin/eulapi-CREATE_EUL-APPS_MODE-CONNECT system/@-USER _US-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

In Mycase I executed as follows

$ORACLE_HOME/bin/eulapi

-CREATE_EUL

-APPS_MODE

-CONNECT system/manager@ERP

-USER EUL_US

-PASSWORD EUL_US

-DEFAULT_TABLESPACE discoverer

-TEMPORARY_TABLESPACE temp

-EUL_LANGUAGE US

-APPS_GRANT_DETAILS apps/apps

Step 9: Specify Java Virtual Machine for Discoverer Plus

You can choose to run OracleBI Discoverer Plus with either the Sun Java 1.4 Plug-in or Oracle JInitiator 1.3.x. Chapter5.9 of theOracle Business Intelligence Discoverer Configuration Guide 10g (10.1.2)explains how to run Discoverer Plus with different Java Virtual Machines. If you are using JInitiator, please note that Discoverer 10.1.2 is not supported to run with JInitiator 1.1.8. You must use JInitiator 1.3.

Example: To configure OracleBI Discoverer Plus to use JInitiator 1.3.1.24 by default:

Logon to Enterprise Manager on the Oracle Business Intelligence 10g Release 2ORACLE_HOMEusing theias_adminaccount.

Select the "Oracle Business Intelligence 10g Release 2 Oracle Home" Instance

Select "Discoverer"

Select "Discoverer Plus"

Select "Configuration Java Plugin"

In the "Java Plugin" section switch the drop-down list from "Sun Java Plugin (1.4)" to "Oracle JInitiator".

Press "OK" to apply the changes.

On the Oracle Business Intelligence 10g Release 2 filesystem, open the file$ORACLE_HOME/discoverer/config/configuration.xml Find the line with the tag, for example

Update the line and specify usage of JInitiator 1.3.1.24, for example

Save theconfiguration.xmlfile

Copy the JInitiator 1.3.1.24 executable to the$ORACLE_HOME/jinitdirectory asjinit13124.exe.

Restart the Discoverer services usingopmn.

Verify that Discoverer Plus is now using JInitiator 1.3.1.24:http://mybi.company.com:7780/discoverer/plusIf you wish to selectively use either the Sun Plug-in or JInitiator for different users or groups, Discoverer supports specifying the desired Java Virtual Machine on the URL using the_jvm_nameparameter. You can specify valuessunorjinitiator.

Example:

http://mybi.company.com:7780/discoverer/plus?_jvm_name=sunDiscoverer Plus will use the Sun Plug-in.

For Discoverer Plus invocation from E-Business Suite Release 11i functions, you can specify the_jvm_nameparameter with the profile optionICX: Discoverer Parametersat the Site/App/Resp/User level to selectively use the Sun Plug-in or JInitiator for given user groups.

For more information on JInitiator, see MetaLink Note124606.1titled "Upgrading Oracle JInitiator with Oracle Applications 11i".

Section 3: Postinstallation Tasks

Step1 : Apply necessary Oracle Applications interoperability patches using AutoPatch.1.1Apply AD patches 5765314 and

These patches contains utilities for Discoverer End User Layer maintainance.

Download patch5765314from OracleMetalink.Follow the instructions in the README to apply the patch

Download patch6459796from OracleMetalink.Follow the instructions in the README to apply the patch

1.2Apply ICX patch 3133021This patch contains support to invoke Discoverer from E-Business Suite functions.

Download patch3133021from OracleMetalink.Follow the instructions in the README to apply the patch

1.3Apply AOL patch 6430269.Download patch6430269from OracleMetalink.Follow the instructions in the README to apply the patch

1.4Apply the latest AutoConfig patch

Follow MetaLink Note 165195.1 titledUsing AutoConfig to Manage System Configurations with Oracle E-Business Suite 11iand apply the latest available AutoConfig Patch to your system.

Step2. Set Applications Profile Options for Discoverer using AutoConfigBy default,AutoConfigconfigures profile options for Oracle E-Business Suite Release 11i environments for Discoverer 4i. Proceed with the following steps to allow AutoConfig to switch profile options for your remote, standalone Oracle Business Intelligence 10g Release 2 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/% ./editcontextSpecify variables as listed in the table below:

TitleVariable NameDescriptionValue

Configure standalone discoverers_disco_standaloneSet the value of this variable to 'true' if E-business suite 11i is configured to use a standalone discoverer servertrue*

Discoverer machine names_disco_machineSet the value of this variable to the machine configured to run Discoverer servicesfor example:ap6162rt.us.oracle.com

Discoverer ports_disco_portSet the value of this parameter to the port on which the HTTP listener is listening for Discoverer requestsfor example:7778

Discoverer protocols_disco_protocolSet the value of this variable to the appropriate protocol used for accessing discoverer. Acceptable values for this parameter arehttporhttpshttp | https

Disco Version Commas_disco_ver_commaDisco Version10,1,2

Discovery EUL prefixs_disco_eul_prefixDiscovery EUL prefixEUL

Discovery Service Statuss_discostatusDiscoverer 10.1.2 is being installed in a new standalone Oracle Application Server 10g OracleHome and replaces the Discoverer 4i service embedded in the iAS 1.0.2.2 based 11i OracleHome. This option disables the Discoverer 4i service.disabled

Note

* When s_disco_standalone is set to 'false', AutoConfig will configure Discoverer machine, port, protocol, version to use the Discoverer version installed in the Oracle Apps Rapid Install mid tier server node.* When s_disco_standalone is set to 'true', AutoConfig will use specified AutoConfig variables Discoverer machine, port, protocol, version.

Other Discoverer related AutoConfig parameters are not relevant for Discoverer 10.1.2 configuration because AutoConfig does not control configuration of the remote, standalone Oracle Business Intelligence 10g Release 2 server node.

The changes will be saved in your Applications Context File/admin/.xml.

Run AutoConfig to generate all configuration files for theAPPL_TOPand theORACLE_HOMEs in its supporting technology stack:

% /admin/scripts//adautocfg.shFor further information about AutoConfig please refer to MetaLink Note165195.1titled "Using AutoConfig to Manage System Configurations with Oracle Applications 11i".

Step3. Verify Applications profile options in Oracle ApplicationsLog 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:

ProfileDescriptionValue

ICX_DISCOVERER_LAUNCHERURL that points to Discoverer Server Launch pagehttp://:/discoverer/plus?Connect=[APPS_SECURE]

ICX_DISCOVERER_VIEWER_LAUNCHERURL that points to Discoverer Viewer Servlethttp://:/discoverer/viewer?Connect=[APPS_SECURE]

ICX_DISCOVERER_RELEASE1 digit number specifying the Discoverer release10

ICX_DISCOVERER_USE_VIEWERSpecify whether Discoverer Viewer should be launched instead of Discoverer Plus (default).Y | N

ICX_DEFAULT_EULICX: Discoverer End User Layer Schema Prefix

This is theEULprefix. TheEULprefixin combination with the Language code make up the EUL owner at runtime.EUL

ICX_DISCOVERER_EUL_LANGUAGEICX: 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 usersICX_LANGUAGEandICX_TERRITORYprofiles. The User Interface language will only change for valid combinations ofICX_LANGUAGEandICX_TERRITORY.US

ICX_DISCOVERER_PARAMETERSICX: Discoverer Parameters

This profile can be used to configure the Exit URL.

In addition to that it may be used to optionally pass additional URL parameters to Discoverer. Compare Note186120.1on Oracle MetaLink.exitURL=

for example

exitURL=http://:/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE

Note

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

EUL_USfor Business Intelligence System content

EULEDW_USfor Embedded Data Warehouse content

Then you can setICX_DEFAULT_EULtoEULEDWfor Embedded Data Warehouse responsibilities like "Financials Intelligence - Enterprise Data Warehouse". Those responsibilities will then use the Embedded Data Warehouse End User Layer.

The remaining steps include patching your End User Layer to the latest level and are requiredonlyif you received new.eexfiles, for example if you migrate to Discoverer 10.1.2 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.Step4. Regenerate your Business ViewsMost 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.eexfiles 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.

4.1.Apply Business View Generator patch patch2921686using AutoPatch.

Note

If you are on Oracle E-Business Suite11.5.10 or aboveyou can skip this step and proceed withStep 4.2.This Patch is included in Oracle E-Business Suite11.5.10 and above.

4.1.1.Download the Business View Generator patch2921686from OracleMetalink4.1.2.Follow the instructions in the README to apply the patch.

4.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"

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

Logon to Oracle Applications as SYSADMIN

Choose the "System Administrator" responsibility

Navigate to Security > User > Define and add responsibility "Business Views Setup" to user SYSADMIN.

For additional details and background, refer to theOracle Applications Flexfields Guide.

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

4.4.Recompile all objects in the APPS schema usingadadmin.

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

Step 5. Set up Applications User/Responsibility for EUL Administration: SYSADMIN/System AdministratorThe Release 11i System Administrator account must be granted permission to update and alter Discoverer 10.1.2 content.

5.1.Grant End User Layer Administration Privileges

Grant the End User Layer Administration privileges for userSYSADMINusing the following command, executed on the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed

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

5.2.Make sure userSYSADMINhas 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 userSYSADMINhas 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 inStep 1$ORACLE_HOME/bin/eulapi \-CONNECT /@ \-GRANT_PRIVILEGE \-USER SYSADMIN \-BUSINESS_AREA_ADMIN_ACCESS % \-WILDCARD \-LOG

Step6.Access directory $AU_TOP/discover on your E-Business Suite 11i instance from your Oracle Business Intelligence 10g BI instanceDiscoverer.eexfiles are patched to your application tier server node, 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/discoveron 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/discoverdirectory. 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.shand the language specific subdirectories containing the set of.eexfiles.

Note

Linux Users only :Replace the lineLD_ASSUME_KERNEL=2.4.19with following lines in $ORACLE_HOME/discoverer/discwb.sh before import/refresh 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.21fiNote :Do not set LD_ASSUME_KERNEL for Operating Systems RHEL5,OEL5,SLES10. And for RHAS 2.1 set its value as 2.2.5

Note

Windows Users only :Create a windows system variable FND_SECURE with value as perSection 5, Step 1.4, before executing AD utility scripts you just accessed from your E-Business Suite Release 11i instance, ie. $AU_TOP/discover/adupdeul.sh, $AU_TOP/discover/adrfseul.sh

Step 7.Import Discoverer Content for Release 11i using adupdeul.sh mode=completeIn this step, you will run AD utilityadupdeul.shon the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed to import the Discoverer loader files (.eexfiles) for Oracle E-Business Suite Release 11i into the Discoverer End User Layer.

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

7.2.Start the import process of the Discoverer loader files (.eexfiles) using the shell scriptadupdeul.sh.

Syntax for theadupdeul.shscript: % sh adupdeul.shconnect=/@resp=gwyuid=fndnam=secgroup=topdir=language=USeulprefix=iashome=[eultype=][mode=][driver=][filelist=][logfile=][parfile=]Where:ParameterDescription

secgroupAPPS responsibility security group

topdirTop level directory where Discoverer files are available

iashomeOracle Application Server 10g / Business Intelligence 10g Oracle Home directory

eulprefixEUL schema prefix. For example, useeulprefix=EULfor schema EUL_US

eultypeOLTP- default, for standard Applications 11i Discoverer contentEDW- for Enterprise Data Warehouse Discoverer content

Useeultype=OLTPto import the Discoverer 10.1.2 content for Oracle E-Business Suite Release 11i

modeCOMPLETE-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 delivered by patch1834171, usemode=complete. This mode will upload all.eexfiles (*o.eex) from the.../discover/ directoryinto the Discoverer End User Layer.

driverSpecifies a comma-separated list of driver files to be loaded. This parameter is required ifmode=DRIVER

filelistSpecifies the filename of a file containing a list of files to be loaded. This parameter is required ifmode=FILELIST

logfileLog file where theadupdeul.shscript logs the result of the import process. Default filename isadupdeul.log

parfileFilename of a command-line parameter file containing entries of the formPARAMETER=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/discoveras/user1/au_top/discovercd /user1/au_top/discover(whereadupdeul.shis located)

Start the full import of all.eexfiles intopdir/US, wheretopdiris 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.

7.3.Performance of the import process greatly depends on network latency between the Oracle Business Intelligence 10g node and the database, and on 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.eexfiles. 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.

7.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 messageImport completed successfully.

You can safely ignore the following messages in the import log:

\\.eex: The import process did not import or modify any dataThis messages provides information that.eexis an empty obsolete file and does not modify any data during import.

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

You can safely ignore this message using Discoverer 10.1.2. See release notes for more details.

7.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 toSection 9for details on importing subsequent patches usingmode=driver.Step 8.Refresh the Discoverer 10.1.2 End User LayerAfter the Discoverer 10.1.2 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 Business Intelligence Server 10g Release 2 was installed.

Alternatively on Windows platforms you may run the refresh process on the machine where Discoverer Administration Edition is installed.

8.1.Move to the... /discover/directory whereadrfseul.shis located.

8.2.Start the refresh process against the database using the shell scriptadrfseul.sh.

Syntax for theadrfseul.shscript: % sh adrfseul.shconnect=/@resp=gwyuid=fndnam=secgroup=eulschema=eulpassword=twotask=iashome=[logfile=][parfile=]Where:ParameterDescription

eulschemaFull EUL schema name, for exampleeulschema=EUL_US

eulpasswordEUL schema password

twotaskDatabase name as specified in your tnsnames.ora file

iashomeOracle Application Server 10g / Business Intelligence 10g Oracle Home directory

logfileLog file where theadupdeul.shscript logs the result of the import process. Default filename isadrfseul.log

parfileFilename of a command-line parameter file containing entries of the formPARAMETER=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(whereadrfseul.shis 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.

Warning

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.

Step 9.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 10.1.2eulapicommand-line utility or Discoverer 10.1.2 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.

9.1 Grant Privileges, Security and Workbook Access on UnixFor information about delivered Business Areas with Oracle E-Business Intelligence Suite please refer toChapter 5 of theOracle 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 10.1.2eulapicommand line utility on the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed inStep 1to grant privileges, business area security and workbook access.

For help on usage of theeulapicommand-line utility, type:

$ORACLE_HOME/bin/eulapi -help grant_privilegeExample 1:Grant Discoverer User privileges to responsibility "Financials Intelligence"

$ORACLE_HOME/bin/eulapi \-CONNECT /@ \-GRANT_PRIVILEGE \-ROLE "Financials Intelligence" \-PRIVILEGE all_user_privsExample 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"9.2.Grant Security and Privileges using Discoverer Administration Edition on WindowsIf you have already granted security and privileges using the Discoverer 10.1.2eulapicommand-line utility, you may skip this step.

Log in to the Discoverer Administration Edition 10.1.2 as the Applications User which was granted full Administration Privileges and Security:\bin\dis5adm.exe /CONNECT "SYSADMIN:System Administrator/@" /EUL _Use theHelp -> About Discoverer...dialog to make sure you are connected to the correct End User Layer (_; compare the import options used above). You can change the EUL in the dialogTools -> Options -> Default EUL.UsingTools -> PrivilegesCheck"Desktop and Plus Privilege"privileges for all Applications Users and Responsibilities who should be allowed to open workbooks.

UsingTools -> SecurityGrant Business Area access to Applications Users and Responsibilities who should be allowed to query the various Business Areas.

9.3 Share Workbooks using Discoverer Plus EditionYou must grant shared workbook access to the Oracle Applications responsibilities to be used for workbook analysis.

Log in to the Discoverer User Edition 10.1.2 as the Applications Administration user who imported theeexfiles inSection 6, Step 7.\bin\dis5usr.exe /APPS_USER /CONNECT "SYSADMIN:System Administrator/@" /EUL _Use theHelp -> About Discoverer...dialog to confirm that you are connected to the correct End User Layer (_; compare the import options used in above). You can change the End User Layer in the dialogTools -> Options -> Default EUL.Using theFile -> Manage Workbooks... -> Sharing...dialogShare the workbooks to the Applications Users and Responsibilities that should be allowed to open the various workbooks.

9.4. Test Discoverer Responsibilities and WorkbooksLog 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 10.1.2 implementation and your Discoverer content for Oracle E-Business Suite Release 11i is ready for use.

Reference:Subject:Using Discoverer 10.1.2 with Oracle E-Business Suite 11i

Doc ID:313418.1Type:WHITE PAPER

Modified Date :25-MAY-2009Status:PUBLISHED