Dsicoverer Documentation

• Install following components on Application Node both in separate ORACLE_HOMES. For this you need to have OracleAS10g

• OracleAS Identity Management Infrastructure 10g (10.1.4.0.1)

• Oracle Application Server 10g Release 2 (10.1.2.0.2) type Business Intelligence and Forms

• Applying the 10.1.2.2 patch (4960210) to BI home.

• Before applying one-off patches, install the Patch (5861907) to BI home.

• IAS 10.1.2.2 PATCHSET UPDATES ORACLEHOMEPROPERTIES.XML WITH WRONG ARU_ID & ARU_I

• Steps for applying the patch :• ----------------------------• 1) Shutdown the iAS instance.• 2) Backup the

$ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml file.• 3) Copy the patch oraclehomeproperties.xml to

$ORACLE_HOME/inventory/ContentsXML.

• Applying a one-off specific fix patch (7306816) to BI home.

• This is a CP-8 patch if any prior CP patch is already applied on your instance then this patch will show a conflict and say if you continue previous patch will be rolled back. Respond with Yes/Y

• You have to apply this patch using Opatch utility.• You have to set the environment pointing to BI home.• Opatch directory should be in the environment variable $PATH

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 12instance 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.

Update tnsnames.ora file

On your standalone Oracle Business Intelligence Server 10g Release 2 node, update fileORACLE_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.

• .

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

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

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

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>

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"/>

Update the line as follows to specify usage of Sun Plugin Version as per your E-Business Suite settings:

<jvm name="sun" classid="clsid:<s_sun_clsid>" plugin_setup="http://mybi.company.com:7780/jpi/oaj2se.exe" version="<s_major_version>" versionie="<s_sun_plugin_ver>,mn" type="application/x-java-applet" plugin_page="http://mybi.company.com:7780/jpi/oaj2se.exe" 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.

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:

TitleVariable Name

Description

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

:7780

Run AutoConfig to generate all configuration files for the APPL_TOP and the ORACLE_HOMEs in its supporting technology stack:

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: Discoverer Launcher

URL that points to Discoverer Plus Servlet.

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

?Connect=[APPS_SECU

RE]

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 usersICX_LANGUAGE andICX_TERRITORY profiles. The User Interface language will only change for valid combinations ofICX_LANGUAGE andICX_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 DBC filename override

This profile can be used to 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.

<NULL>

Now Install Discoverer Administration 10 on your PC and perform the following steps.

1. Registry Settings

Registry KeyDataType

Value

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

REG_DWORD

1

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

REG_DWORD

1

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

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

  Open the file <ORACLE_HOME>/discoverer/util/pref.txt in a text editor  

Add following preference setting to the Database section of the pref.txt file:

[Database]

SQLType = 3

  Save the updated pref.txt file.

  Run the script <ORACLE_HOME>/discoverer/util/applypreferences.sh

Complete the following Create EUL Wizard: Step 1 screen as follows:

• Click Select an existing user

• Check Grant access to PUBLIC

• Check New EUL is for use by Oracle Applications ONLY

• Click Select

On the Select User screen, locate the user called EUL_10G_US, or whatever user you used to connect to Discoverer Admin. After you have selected the user, click OK

You will now be returned to the Create EUL Wizard: Step 1 but this time you will notice that the User details have now been filled in and that the Next button has been activated. When ready, click Next

Complete the following Create EUL Wizard: Step 2 screen as follows:

• Schema - enter APPS

• Password - enter the APPS password

• Click Finish

Discoverer now begins the install of the EUL. As the install progresses you will see the following screens:

• Creating Tables and Views

• Populating tables with default data

• Granting access on EUL tables

Finally, you will see the following completion screen. When done, click OK

Having successfully installed the EUL, you will now be returned to the EUL Manager screen from where you should click Close

You will now see the following Load Wizard: Step 1

Because we have not completed the setup that will allow the EUL to operate in Oracle Apps mode, we will not create any business areas at this time. When done, click Cancel

Congratulations, you have successfully installed Discoverer in Apps mode. Next we need to set up the Apps mode privileges

Set up Discoverer Apps mode privileges

Having successfully created an Apps mode EUL, the next step is to set up the Apps mode privileges

To set up Apps mode privileges, use the following workflow:

1. If not already logged in, launch the Discoverer Administrator tool and connect as the owner of the EUL, in this case EUL_10G_US

2. If you are in the Load Wizard, click Cancel

3. From the menu bar, select Tools | Options

4. Click the Connection tab

As you can see in the above illustration, the Connection tab has three radio buttons and an area called Applications EUL Settings. The three radio buttons are:

• Connect to standard EULs - check this if your organization will only ever be using Discoverer in standard mode

• Connect to applications EULs - check this if your organization will only ever be using Discoverer in Apps mode

• Connect to both standard and applications EULs - check this if your organization will be using Discoverer in both Apps and standard modes. If you are wondering how this can be, let us explain. Some organizations use Discoverer in Apps mode against their Oracle Apps database but use it in standard mode against another database, such as a Data Warehouse. Because there is only one Administrator tool, the same tool needs to be able to administer Discoverer in both modes, hence the third option on the screen

Having enabled Discoverer in Apps mode, and specified whether you will only be administering Apps EULs or a combination of standard and Apps EULs, complete the Connection tab as follows:

• Click Connect to both standard and applications EULs

• Gateway User ID / password - enter applysyspub/pub

• Foundation Name - enter apps or whichever user your organization is using for the ownership of the Apps foundation tables

• Click OK

5. From the menu bar, select Tools | Privileges

6. Click the Privileges tab and then click Select

7. On the Select User/Responsibility screen, pick the Responsibility or Apps user that you want to use for managing Discoverer

8. Assign all of the following privileges and then click OK

9. Now that you have assigned privileges to the SYSADMIN user or responsibility you now need to re-connect using SYSADMIN or a user that has the responsibility that you granted admin rights to

10. From the menu bar, select File | Connect.

11. The Discoverer Administrator login screen will be displayed once more but this time you should reconnect as the SYSADMIN user. You will of course need to know the SYSADMIN password. As shown in the following illustration you will notice that there is now an additional checkbox called Oracle Applications User. In order to connect properly you will need to check this box.

12. Complete the above dialog box as follows:

• User name - enter sysadmin (case is unimportant)

• Password - enter the password

• Connect - enter the database (case is unimportant)

• Make sure Oracle Applications User is checked

• Click Connect

13. Discoverer will now authenticate the SYSADMIN user against the Oracle Applications E-Business Suite. If the credentials are correct, you will be presented with the following Choose a Responsibility Screen.

14. Select the System Administrator responsibility and click OK

15. From here on, you should only log in to the Administrator tool as the Apps SYSADMIN use. After you have done this the Load Wizard will be prompted.

References:

Using Discoverer 10.1.2 with Oracle E-Business Suite Release 12 [ID 373634.1]

Prepared By: Zulfiqar Ali Chaudhry