Installation Single Sign-On (Oracle Internet Directory) & Oracle Web Discoverer 10g on solaris 10 configured with E-Business Suit R12

Discoverer Configuration

Step 1- Check OS Prerequisite on erpdisc

(erpdisc is discoverer Node)

Hostname -hostname

OSVERSION - uname -r

Maintenance level - /etc/release

RAM - /usr/sbin/prtconf | grep -i memory

SWAP - swap -s

Tmp - df -k /tmp

Kernel Parameter- /etc/system

JDK & JRE - /usr/bin/java -version

Ulimit- ulimit -a

Hostname settings- /etc/hosts

OS 64 bit or 32 bit - /bin/isainfo -kv

File Descriptor- /etc/system set rlim_fd_max=65536

Oracle OS Group - /etc/group

Oracle OS Discoverer User – mkuser -disc

OS Packages- pkginfo <package name>

OS Patches- showrev -p <patch_name>

Software Requirement –

which ar

which ld

which make

which X Display Server
Step 2 – Make changes in hosts file

root@erpdisc # more /etc/hosts

# Internet host table

127.0.0.1 localhost.localdomain localhost

xxx.xx.xx.xx hostname.domain_name hostname

Step 3 - Kernel parameters in /etc/system

set rlim_fd_max=65536

set noexec_user_stack=1

set semsys:seminfo_semmni=512

set semsys:seminfo_semmsl=512

set semsys:seminfo_semmns=1024

set shmsys:shminfo_shmmax=4294967295

set shmsys:shminfo_shmmni=512

set shmsys:shminfo_shmmin=1

set shmsys:shminfo_shmseg=512

ulimit Value Settings

The following ‘ulimit’ values:

• time (seconds) = unlimited
• file (blocks) = unlimited
• data (kbytes) = unlimited
• stack (kbytes) = 65536
• memory (kbytes) = unlimited
• coredump (blocks) = unlimited
• nofiles (descriptors) = 65536

Using Discoverer 10.1.2 with Oracle E-Business Suite Release 12

This document contains information for using Oracle Business Intelligence 10g Release 2 (10.1.2) with Oracle E-Business Suite Release 12.

The most current version of this Note is 373634.1 on Oracle MetaLink

There is a change log at the end of this document.

Section 1: Overview

Oracle Business Intelligence 10g Release 2, a key component of Oracle Application Server 10g Release 2, 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 10.1.2 to gain immediate access to information from data marts, data warehouses, and online transaction processing

(OLTP) systems. Discoverer 10.1.2 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.

This document describes how to install Discoverer 10.1.2 into an existing Oracle E-Business Suite Release 12 environment. Installation of Discoverer 10.1.2 into an Oracle E-Business Suite Release 12 environment consists of:

Installation of Discoverer 10.1.2 with Oracle Business Intelligence Server 10g Release 2 on a standalone application tier server node, or in a separate Oracle Business Intelligence Server 10g Release 2 ORACLE_HOME on an existing application tier server node.

The procedures in this document have significant effects on Oracle E-Business Suite Release 12 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.

Section 2: Supported Architectures

Discoverer 10.1.2 must be installed on a standalone server accessing an Oracle E-Business Suite Release 12 database, or in a separate Oracle Business Intelligence Server 10g Release 2 (10.1.2.0.2 or 10.12.2) ORACLE_HOME on an existing application tier server node.

This configuration does not include integration of Oracle Single-Sign-On, Oracle Internet Directory, or Oracle Portal with Oracle E-Business Suite Release 12 (MetaLink Note 376811.1).

Section 3: Release Versions

The following components must be used on the stand-alone instance:

Component Name	Version
Oracle Application Server	10.1.2.3
Oracle Business Intelligence	10.1.2.3

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

Component Name	Version
Oracle E-Business Suite Release 12	12.1.3

Section 4: Pre-installation Tasks:-

According to our requirement, we have need to be installed Oracle Internet Directory (OID 10.1.4.3.0)

Components

Oracle E-Business Suite Release 12

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

Component Name	Release
Oracle E-Business Suite Release 12	12.1.3
Oracle 10g Application Server	10.1.2
Oracle 10g Application Server	10.1.3

Oracle Application Server 10g Enterprise Edition

The following Oracle Application Server 10g Enterprise Edition components must be used on the standalone instance:

Component Name	Release
Oracle Single Sign-On 10g	10.1.4.3.0
Oracle Internet Directory 10g	10.1.4.3.0
Oracle Web Cache 10g (optional)	10.1.2.3.0
Oracle Discoverer 10g (optional)	10.1.2.3.0

Oracle Single Sign-On Installation Steps:-

$ cd 10.1.2.0.2/Disk1/

$ ./ runInstaller

click on Next

Name : enter the name of infrastructure directory (i.e INFRA)

Path : <Home_directory>

click on Next

Select a product to Install Option : Oracle Application Server Infrastructure

click on Next

Select Installation Type : Identity Management and Metadata Repository

click on Next

select configure ports : Automatic

click on Next

Global database name: infra.<domain_name>.com

SID : INFRA

Specify database file location : <Home_Directory>/infradata

click on Next

Specify database schema passwords

select use the same password for all the accounts

Enter Password : xxxxx Confirm Password : xxxxxx

click on next

Administrator User Name: ias_admin

instance Name : infra

ias_admin password : xxxxxxx

confirm password : xxxxxx

click on next

click on Install

Before click on "OK" button

Run the script through root user

# sh /<home_directory>/root.sh

then click on "OK"

ERROR LOG :

Launched configuration assistant 'Internet Directory Configuration Assistant'

Tool type is: Recommended.

The command being spawned is: '<home_directory>/infra/bin/oidca mode=OID

iasinstance=infra. subscriberdn=dc=x,dc=y,dc=z -silent -crypto -debug'

Start output from spawned process:

java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1

ORA-12705: invalid or unknown NLS parameter value specified

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:304)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)

at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOauth(T4CTTIoauthenticate.java:647)

at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:307)

at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:433)

at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:150)

at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:31)

at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:571)

at java.sql.DriverManager.getConnection(DriverManager.java:512)

at java.sql.DriverManager.getConnection(DriverManager.java:140)

at oracle.ldap.oidinstall.backend.SQLConnection.<init>(SQLConnection.java:52)

at oracle.ldap.oidinstall.backend.OIDConfigWrapper.configOID(OIDConfigWrapper.java:208)

at oracle.ldap.oidinstall.OIDCA.doSilent(OIDCA.java:507)

at oracle.ldap.oidinstall.OIDCA.run(OIDCA.java:818)

at oracle.ldap.oidinstall.OIDCA.main(OIDCA.java:957)

Oracle Internet Directory Configuration failed. Please see log file:

/<home_directory>/infra/ldap/log/oidca.log

The $ORACLE_HOME/cfgtoologs/oidca.log contains:

Fri May 05 15:59:21 MEST 2006 OID CA started.

oracle.ldap.oidinstall.backend.OIDCAException: java.sql.SQLException:

Listener refused the connection with the following error:

ORA-12520, TNS:listener could not find available handler for requested type of server

The Connection descriptor used by the client was:

(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=host.domain)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=db.domain)))

at oracle.ldap.oidinstall.backend.OIDConfigWrapper.configOID(OIDConfigWrapper.java:247)

at oracle.ldap.oidinstall.OIDCA.doSilent(OIDCA.java:507)

at oracle.ldap.oidinstall.OIDCA.run(OIDCA.java:818)

at oracle.ldap.oidinstall.OIDCA.main(OIDCA.java:957)

Fri May 05 18:24:37 MEST 2006 OID CA started.

oracle.ldap.oidinstall.backend.OIDCAException: java.sql.SQLException:

ORA-00604: error occurred at recursive SQL level 1

ORA-12705: invalid or unknown NLS parameter value specified

atoracle.ldap.oidinstall.backend.OIDConfigWrapper.configOID(OIDConfigWrapper.java:247)

at oracle.ldap.oidinstall.OIDCA.doSilent(OIDCA.java:507)

at oracle.ldap.oidinstall.OIDCA.run(OIDCA.java:818)

at oracle.ldap.oidinstall.OIDCA.main(OIDCA.java:957)

Cause

Bug: 5248119 OIDCA FAILS WITH ORA-12520 ON NIAGRA ARCHITECTURE

The DBCA creates the seeded database, previous to the other components. When this is done the default parameter processes is set 150.

Given a Niagara architecture in place with 1 cpu with 8 cores and 4 threads.

With this in mind the DBCA sets parallel_max_servers parameter to a value of 135 plus the allocated background processes the value of processes is greater than 150. This is seen in the alert.log file, which warns that some ora_Pxxx procesess could not be started. So when the database instance is created, and when it oidca runs, it cannot find any connection thread to the database because we have reached max processes

Note: This problem has also been shown to occur on other platforms with multi-core/multi-threaded CPU's

Solution

To implement the solution, execute the following steps:

1. Change the Database parameters: alter system set parallel_max_servers=35 scope=spfile;

alter system set processes=400 scope=spfile;

alter system set parallel_max_servers=35 scope=spfile;

alter system set processes=400 scope=spfile;

alter system set sga_target=1200M scope=spfile;

alter system set pga_aggregate_target=300M scope=spfile;

alter system set db_cache_size=300M scope=spfile;

alter system set shared_pool_size=512M scope=spfile;

alter system set java_pool_size=200M scope=spfile;

2. Restart the Database

3. Retry the failed Configuration Assisitant.

On occasion the above has been known to work, but more often than not, it will not, and the full solution is as per below.

If it still fails then:

According to Oracle Doc.ID558296.1

1)Stop all Services .

Infra_home/opmn/bin > opmnctl stopall

2)Backup and clear all the logs under Infra_home/ldap/log and

Infra_home/opmn/logs folders.

3)Try if you can login to the database as the ODS schema user .

sqlplus ODS/<pwd> @<SID>

The ODS schema password would be the same as ur IAS_ADMIN password.

4)Truncate the ODS_PROCESS table

sql> truncate table ODS_PROCESS;

5)check the listener status, if its not running start the listener.

lsnrctl status

6) Check the permissions on the OID binaries

$ORACLE_HOME/bin> ls -l oid*

Expected permissions for the binaries are :

755 (-rwxr-xr-x) oracle/dba – oidadmin, oidca, oidctl, oidprovtool, oidreconcile

4710 (-rws--x---) root/dba – oidldapd

4710 (-rws--x---) oracle/dba – oidmon, oidrepld

510 (-r-x--x---) oracle/dba – oidpasswd

If the file permissions are different from the above mentioned then take a backup of the above files before making any modifications

Steps to change the file permissions
------------------------------------

a).Login as the root user and go to the $ORACLE_HOME/bin directory:

# cd $ORACLE_HOME/bin

b).To change the permissions use chmod. For example:

# chmod 4710 oidldapd

c).To change the group, use chgrp:

# chgrp dba oidldapd

d).To change the ownership, use chown. For example:

# chown root oidldapd

e).Start oidldapd processes using opmnctl as usual.

$infra_home/opmn/bin>opmnctl start

$infra_home/opmn/bin>opmnctl startproc process-type=OID

7)Check whether the OID is started or not by doing an ldapbind with OID SSL and non SSL ports
$infra_home/bin>ldapbind -h <host name> -p <non-ssl port>

$infra_home/bin>ldapbind -h <hostname> -p <ssl port> -U 1

a) if you are able to bind successfully that means that OID is up and running.

b)if the ldapbind is failed please review the latest logs under Infra_home/ldap/log and Infra_home/opmn/logs folders and contact Oracle Support with the latest log

files mentioned under step2.

8)If the ldapbind is successfully please start the OC4J process like below.

$Infra_home/opmn/bin > opmnctl startproc process-type=OC4J_SECURITY

$Infra_home/opmn/bin > opmnctl status

Click on "Retry"

Click on "Exit"

Upgrade the OID 10.1.2.0.2 to 10.1.4.0.1

Name : Orainfra

Path : <Home_directory>/infra

click on Next

Select a Product to install

click on : Oracle Application Server Infrastructure 10g

click on Next

Select Installation Type :

select option : Identity management to metadata repository

click on Next

Click on "OK"

Administrator Username : ias_admin

Instance Name : ias_orainfra or (infra)

Ias_admin Password : xxxxxxx

Confirm Password : xxxxxx

click on Next

Now upgrade to OID 10.1.4.0.1 to 10.1.4.3.0

Apply the patch 10.1.4.3

and then apply database patch 8811442.

Section 5: Installation Tasks

This section outlines steps required to install Oracle Business Intelligence Server 10g Release 2, Discoverer 10.1.2

5.1. Install Oracle Discoverer 10g Release 2 (10.1.2.0.2)

5.1.1. Install Oracle Application Server 10g Release 2 (10.1.2.0.2)

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

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

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

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

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

This installation type includes:

Discoverer Server 10g

Discoverer Plus 10g

Discoverer Viewer 10g

Discoverer installation steps:

# cd 10.1.2.0.2/Disk1/

# ./runInstaller

Name : oradisc (for discoverer )

Path: <Discoverer Home_directory>

Click on ‘next ‘

Select a product to install

Select : Oracle Application Server 10g

click on Next

After complete the installation then follow step 5.2

5.2 Configure Oracle Discoverer 10g Release 2 (10.1.2.0.2)

5.2.1. Apply the latest certified Discoverer Plus and Viewer Patches

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

Certified AS Patchset	Download Location	One-off / Cumulative Patch Details
Oracle Discoverer 10.1.2.3	5983622	Apply Cumulative Patch 1 7111842 or higher for your Discoverer Server node

After applied the patch 5983622

Applied Opatch 7111842.

5.2.2. Copy Database Connection file

Discoverer needs access to the Database Connection (dbc) file for the database you wish to connect to. A dbc file is a text file which stores all the information required to connect to a particular database.

In the Discoverer10g $ORACLE_HOME/opmn/conf/opmn.xml file check the variable for FND_SECURE. This variable specifies the directory where Discoverer is trying to locate dbc files. By default this is set to $ORACLE_HOME/discoverer/secure.

Create the directory

$ORACLE_HOME/discoverer/secure

if it does not exist. Then copy the dbc file from the $FND_SECURE directory of the E-Business Suite Release 12 instance you are setting up Discoverer with to the Discoverer 10.1.2 $ORACLE_HOME/discoverer/secure directory you just created.

Discoverer will attempt to find the dbc file in following order

1. $FND_SECURE/<two_task>.dbc

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

5.2.3. Update tnsnames.ora file

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

5.3. Migrate your existing Discoverer End User Layers to Discoverer 10.1.2.

If you are a new customer, implementing Discoverer for the first time, you do not have an existing Discoverer 4i or 9.0.4 End User Layer. Please skip this step and proceed with Step 5.6.

If you already have an existing Discoverer 10.1.2 End User Layer which is being used with Discoverer 10.1.2, End User Layer migration is not required. Skip this step and proceed with Step 5.7.

You can query the Discoverer version required to connect to an existing Discoverer End User Layer. Use sqlplus to connect to your existing Discoverer End User Layer and execute following query:

sqlplus
eul_us/eul_us@db

SQL> select ver_min_code_ver from eul5_versions;

You must migrate your End User Layer to 10.1.2 if either of the following are true:

If ver_min_code_ver is lower than 10.1.2

If the table eul5_versions does not exist in your End User Layer, but the equivalent table eul4_versions does exist
(this is a Discoverer 4i End User Layer)

Migrate your existing Discoverer 4i or Discoverer 9.0.4 End User Layer to Discoverer 10.1.2 by using the following command on the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed in Step 5.1 .

For SOLARIS:

$ORACLE_HOME/bin/eulapi -CONNECT <EUL User>/<Password>@<db> -AUTO_UPGRADE

5.4. Create new Discoverer 10.1.2 End User Layer

If you do not have an existing Discoverer End User Layer, you must create a new Discoverer 10.1.2 End User Layer. Fresh installations of E-Business Suite Release 12 Production do not contain a pre-installed Discoverer End User Layer. Only the E-Business Suite Release 12 Vision database contains a pre-installed Discoverer 10.1.2 End User Layer.

We recommend that you create a new tablespace to store database objects for the Discoverer 10.1.2 End User Layer in your E-Business Suite Release 12 database.

5.4.1. Set Your Environment

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

[DB_ORACLE_HOME]/<dbname>.env

5.4.2. 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
/NOLOG

SQL> connect sys/<sys_password> as sysdba
SQL> create tablespace DISCOVERER datafile \

     '[DB_ORACLE_HOME]/dbf/discoverer01.dbf' size
200M reuse \

extent management local uniform size 128K;
SQL> /
Statement Processed

5.4.3. Exit SQL*Plus:

SQL> quit

5.4.4. Create the Discoverer End-User Layer

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

$ORACLE_HOME/bin/eulapi \

-CREATE_EUL \

-APPS_MODE \

-CONNECT system/<password>@<db> \

-USER <EUL_User_Prefix>_US \

-PASSWORD <password> \

-DEFAULT_TABLESPACE <default tablespace> \

-TEMPORARY_TABLESPACE <temp tablespace> \

-EUL_LANGUAGE US \

-APPS_GRANT_DETAILS <FNDNAM>/<FNDNAM password>

For example:

$ORACLE_HOME/bin/eulapi -CREATE_EUL -APPS_MODE \

-CONNECT system/manager@cus120 -USER EUL_US -PASSWORD EUL_US \

-DEFAULT_TABLESPACE discoverer -TEMPORARY_TABLESPACE temp \

-EUL_LANGUAGE US -APPS_GRANT_DETAILS apps/apps

Alternatively, you may also use the equivalent Discoverer Administration Edition command line on Windows. Use the following syntax to create the End-User Layer using Discoverer Administration Edition:

%ORACLE_HOME%/bin/dis51adm.exe /CREATE_EUL /APPS_MODE \

/CONNECT system/manager@cus120 /USER EUL_US /PASSWORD EUL_US \

/DEFAULT_TABLESPACE discoverer /TEMPORARY_TABLESPACE temp \

/EUL_LANGUAGE US /APPS_GRANT_DETAILS apps/apps /SHOW_PROGRESS

5.5. Specify Java Virtual Machine for Discoverer Plus

explains how to run Discoverer Plus with different Java Virtual Machines. You must configure OracleBI Discoverer Plus to use the same Plug-in version as being used for E-Business Suite Release 12.

Perform the steps in this section to configure OracleBI Discoverer Plus to use the same Sun Java Plugin as your E-Business Suite Release 12 by default.

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

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

5.5.3. Save Your Changes and Restart Discoverer

Save the updated configuration.xml file

Restart the Discoverer services using opmn.

5.5.4. Testing Your New Configuration

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

http://hostname.domain_name.com:7778/discoverer/plus

5.5.5. Alternative Configurations (Optional)

If 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_name parameter. You can specify values sun or jinitiator.

For example, invoke Discoverer with the following URL to use JInitiator:

http://mybi.company.com:7780/discoverer/plus?_jvm_name=jinitiator

For Discoverer Plus invocation from E-Business Suite Release 12 functions, you can specify the _jvm_name parameter with the profile option

ICX: Discoverer
Parameters

at the Site/App/Resp/User level to selectively use the Sun Plug-in or JInitiator for given user groups

Step 6. 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.

Specify following variable:

	Variable 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://erpdisc.comviva.com:7779/`

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

%
<ADMIN_SCRIPTS_HOME>/adautocfg.sh

6.1. 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_SECURE]
ICX: Discoverer Viewer Launcher	URL that points to Discoverer Viewer Servlet	http://<HTTP Server>:<Port> /discoverer/viewer ?Connect=[APPS_SECURE]
ICX: Discoverer Release	Single number specifying the Discoverer release	10
ICX: Discoverer use Viewer	Specify whether Discoverer Viewer should be launched instead of Discoverer Plus (default).	Yes \| No
ICX: Discoverer Default End User Layer Schema Prefix	The EUL prefix in combination with the Language code make up the EUL owner at runtime. For example EUL owner EUL_US has EUL prefix EUL.	EUL
ICX: Discoverer End User Layer Language Override	Since the End User Layer content is currently available in US English only, it is possible to override the user's general language preference for the Discoverer End User Layer using this profile option. The specified End User Layer language will be used regardless of the individual user's language preferences. This profile does not affect the National Language Support parameters passed to Discoverer. The Discoverer User Interface will still appear according to the users ICX_LANGUAGE and ICX_TERRITORY profiles. The User Interface language will only change for valid combinations of ICX_LANGUAGE and ICX_TERRITORY.	American English
ICX: Discoverer Parameters	This profile can be used to optionally pass additional URL parameters to Discoverer. Compare Note 186120.1 on Oracle MetaLink.	<NULL>
Discoverer 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>

6.2. Run the "Generate Business Views by Application" Concurrent Program

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

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

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

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

6.3. Check for Errors

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

6.4. Recompile APPS objects

Recompile all objects in the APPS schema using adadmin.

6.5. Check Business Intelligence System Views

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

% sqlplus apps/<password>@<db>

SQL> select object_name from user_objects

where object_type = 'VIEW' and

status = 'INVALID' and

( object_name like '%FV_%' or object_name like '%FG_%' or

object_name like '%BV_%' or object_name like '%BG_%' )and

object_name in (select sobj_ext_table from eul_us.eul5_objs);

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

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

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

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

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

Discoverer .eex files are patched to your E-Bussiness Suite Release 12 instance, directory $AU_TOP/discover. Those files must be accessible from the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed.

Please mount your applications tier server node, directory $AU_TOP/discover on your standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed.

If you are unable to mount this directory, you can also zip and ftp the entire $AU_TOP/discover directory. In this case, make sure that you include the directory structure (ie. use zip -r) when you create the zip, and preserve the directory structure when you unzip the file on the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed. The directory structure will include the import shell scripts $AU_TOP/discover/adupdeul.sh, $AU_TOP/discover/adrfseul.sh and the language specific subdirectories containing the set of .eex files.

6.8. Improving the Speed of the Import Process

Performance of the import process greatly depends on:

Network latency between the Oracle Business Intelligence 10g node and the database
Available resources on your Oracle Business Intelligence 10g node

Depending on these factors, the import process may take less than one hour or up to several hours to complete for the entire set of Discoverer baseline .eex files. To minimize overhead from network latency during the import process, it is strongly recommended that Oracle Business Intelligence 10g be installed on a machine that is close to the database server and has a fast network connection.

6.8.1 Start the Import Process

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

Use the following syntax for the

adupdeul.sh

script:

% sh adupdeul.sh \

connect=<APPS admin user>/<password>@<two_task>

resp=<APPS administrator responsibility>

gwyuid=<APPS GWYUID>

fndnam=<APPS FNDNAM>

secgroup=<secgroup>

topdir=<topdir>

language=US

eulprefix=<eulprefix>

iashome=<iashome>

[eultype=<eultype>]

[mode=<mode>]

[driver=<driver>]

[filelist=<filelist>]

[logfile=<logfile>]

[parfile=<parfile>]

Where:

Parameter	Description
secgroup	APPS responsibility security group
topdir	Top level directory where Discoverer files are available
iashome	Oracle Application Server 10g / Business Intelligence 10g Oracle Home directory.
eulprefix	EUL schema prefix. For example, use eulprefix=EUL for schema EUL_US
eultype	OLTP - default, for standard E-Business Suite Release 12 Discoverer content EDW - for Enterprise Data Warehouse Discoverer content Use eultype=OLTP to import the Discoverer 10.1.2 content for Oracle E-Business Suite Release 12
Mode	COMPLETE - import all Discoverer content. DRIVER - default, import specific subset of files FILELIST - import specific subset of files For the initial full import of the Discoverer 10.1.2 baseline files, use mode=complete. This mode will upload all .eex files (*o.eex) from the .../discover/ directory into the Discoverer End User Layer.
driver	Specifies a comma-separated list of driver files to be loaded. This parameter is required if mode=DRIVER
filelist	Specifies the filename of a file containing a list of files to be loaded. This parameter is required if mode=FILELIST
logfile	Log file where the adupdeul.sh script logs the result of the import process. Default filename is adupdeul.log
parfile	Filename of a command-line parameter file containing entries of the form PARAMETER=VALUE. Parameters specified at the command line take precedence over those specified in the parameter file.
Notes: All parameters must be specified on a single command line or in a parameter file. Name-value pairs must not contain spaces. For example: PARAMETER=VALUE is acceptable PARAMETER = VALUE will generate errors

For example:

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

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

Start the full import of all .eex files in topdir/US, where topdir is specified as a parameter

sh adupdeul.sh \

connect=sysadmin/sysadmin-password@db \

resp="System Administrator" \

gwyuid=APPLSYSPUB/PUB \

fndnam=APPS \

secgroup="Standard" \

topdir=/user1/au_top/discover \

language=US \

eulprefix=EUL \

eultype=OLTP \

mode=complete \

iashome=/oracle/iAS/bi \

logfile=import_complete_eul_us_cust120.log

Discoverer Screenshot:

User Name: orcladmin

Password : xxxxxxxx

Enter User Name:

Password:

Database : UAT/PROD

End User Layer : eul_us

Click on ‘ok’

Select Responsibility by drop-down option

Click continue

Oracle Application DBA

Search This Blog