al-koot discoverer installation

Discoverer Server 10.1.2.0.2

Al-Koot Insurance Company Oracle E-Business Suite 11i

(11.5.10.2)

Author: Mohamed ShakerCreation Date: November 4, 2007Last Updated: November 4, 2007Version: 1.0

Approvals

Mr.

Copy Number _____

Document Control

Change Record

3

Date Author Version

Change Reference

04-Nov-07

Mohamed Shaker 1.0 No previous document

Reviewers

Name Position

Distribution

Copy No.

Name Location

1 Library Master Project Library23

Note to Holders:

If you receive an electronic copy of this document and print it out, please write your name on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover, for document control purposes.

Installation Site Report 2Raya/Al-Koot Confidential - For internal use only

Contents

DOCUMENT CONTROL....................................................................................................................................................... 2PURPOSE OF THIS DOCUMENT............................................................................................................................................ 4INSTALLATION................................................................................................................................................................... 5DISCOVERER COMPONENTS URL’S.................................................................................................................................. 11STARTUP AND SHUTDOWN PROCEDURES.......................................................................................................................... 12

Normal Startup........................................................................................................................................................... 12Normal Shutdown....................................................................................................................................................... 12

DOCUMENTATION AND NOTES USED................................................................................................................................ 13Oracle Documentation:............................................................................................................................................... 13

Installation Site Report 3Raya/Al-Koot Confidential - For internal use only

Purpose of this Document

This document shows the steps applied to install the Oracle Discoverer 10g Release 2 patch-set2 (Discoverer 10.1.2.0.2).The Discoverer 4i is obsolete by Oracle with Oracle Applications E-Business Suit 11.5.8 to 11.5.10, so the upgrade process is done by installation of the Discoverer 10.1.2.0.2 with 11i E-Business suit.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.Discoverer 10.1.2 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 10.1.2 into an existing Oracle E-Business Suite Release 11i environment. Installation of Discoverer 10.1.2 into an Oracle E-Business Suite Release 11i environment consists of:

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

- Creation of the Discoverer 10.1.2 End User Layer (EUL) on a database tier server node. - Import of the Oracle E-Business Suite Release 11i Discoverer content into the Discoverer 10.1.2 End User Layer - Installation of Discoverer Administration Edition 10.1.2 on a Windows-based PC that can be used to customize

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

Installation

This section outlines steps required to install Oracle Business Intelligence Server 10g Release 2, Discoverer 10.1.2 and the Discoverer 10.1.2 End User Layer.

1. Install Oracle Business Intelligence Server 10g Release 2 (10.1.2.0.2)1.1 Install Oracle Business Intelligence Server 10g Release 2 (10.1.2.0.2)You must install Oracle Business Intelligence Server 10g Release 2 (10.1.2.0.2) installation in a separate ORACLE_HOME (biHome) from the previously installed. This installation type includes Discoverer Server 10g, Discoverer Plus 10g, and Discoverer Viewer 10g.

1.2. Copy Database Connection fileIn 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_TOP/secure and the $FND_TOP/secure/PROD_alktsvr02 directories of the 11i instance you are setting up Discoverer with to the Discoverer 10.1.2 $ORACLE_HOME/discoverer/secure directory you just created.

1.3. Update tnsnames.ora fileOn your standalone Oracle Business Intelligence Server 10g Release 2 ORACLE_HOME 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 application tier server (8.0.6) ORACLE_HOME. The database name must match thetwo_task entry in the dbc file. Verify you can establish a connection to your Oracle E-Business Suite Release 11i database using sqlplus.

3. Create new Discoverer 10.1.2 End User LayerThat's because we do not have an existing Discoverer 4i or Discoverer 9.0.4 End User Layer so we must create a new 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 Oracle Applications database.

3.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:. /u01/oracle/proddb\9.2.0\PROD_alktsvr02.env

3.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:SQL> connect / as sysdbaSQL> create tablespace discoverer datafile ‘/u01/oracle/proddata/discoverer01.dbf' size 200M;

3.3. Create the new Discoverer 10.1.2 End User Layer by using the following command, executed on the application server where Oracle Business Intelligence Server 10g Release 2 was installed, use theDiscoverer command line on unix.$ORACLE_HOME/bin/eulapi -CREATE_EUL -APPS_MODE \

Oracle E-Business Suite 11i (11.5.10.2) Installation Raya/Al-Koot Confidential - For internal use only

5

-CONNECT system/manager@prod -USER EUL_US -PASSWORD EUL_US \-DEFAULT_TABLESPACE discoverer -TEMPORARY_TABLESPACE temp \-EUL_LANGUAGE US -APPS_GRANT_DETAILS apps/apps

4. Specify Java Virtual Machine for Discoverer PlusTo configure OracleBI Discoverer Plus to use JInitiator 1.3.1.21 by default:

- Logon to Enterprise Manager on the Oracle Business Intelligence 10g Release 2 ORACLE_HOME using the ias_admin account.

- 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 <jvm name="jinitiator"/>, for example

<jvm name="jinitiator" classid="clsid:CAFECAFE-0013-0001-0022-ABCDEFABCDEF"plugin_setup="http:// alktsvr02.qgpc.net /jinitiator/jinit.exe" version="1.3.1.22"versionie="1,3,1,22" type="application/x-jinit-applet" plugin_page="/PlusPluginPage.uix"disco_archive="disco5i.jar" d4o_archive="d4o_double.jar"/>

- Update the line and specify usage of JInitiator 1.3.1.21, for example<jvm name="jinitiator" classid="clsid:CAFECAFE-0013-0001-0024-ABCDEFABCDEF"plugin_setup="http:// alktsvr02.qgpc.net /jinitiator/jinit13121.exe" version="1.3.1.21"versionie="1,3,1,21" type="application/x-jinit-applet" plugin_page="/PlusPluginPage.uix"disco_archive="disco5i.jar" d4o_archive="d4o_double.jar"/>

- Save the configuration.xml file- Copy the JInitiator 1.3.1.21 executable to the $ORACLE_HOME/jinit directory as

jinit13121.exe.- Restart the Discoverer services using opmn.-

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.Example:http:// alktsvr02.qgpc.net:7778/discoverer/plus?_jvm_name=sunDiscoverer Plus will use the Sun Plug-in.For Discoverer Plus invocation from E-Business Suite 11i 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.


6

Post Installation Tasks

This section describes steps for configuring Oracle E-Business Suite Release 11i to use Discoverer 10.1.2, and for loading the Applications-specific content and workbooks into the Discoverer 10.1.2 End User Layer.

1. Set Applications Profile Options for Discoverer using AutoConfigBy default, AutoConfig configures 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 context file using Oracle Applications Manager, login to Oracle Applications Manager and navigate to Site Map > AutoConfig > Edit Parameters.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

alktsvr02.qgpc.net

Discoverer port s_disco_port Set the value of this parameter to the port on which the HTTP listener is listening for Discoverer requests

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

Disco Version Comma s_disco_ver_comma Disco Version 10,1,2

Discovery EUL prefix s_disco_eul_prefix Discovery EUL prefix EUL

Discovery Service Status s_discostatus Discoverer 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

* You can open the XML file of the context with the word pad and edit those parameters.* 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 /u01/oracle/prodappl/admin/PROD_alktsvr02.xml.Run AutoConfig to generate all configuration files for the APPL_TOP and the ORACLE_HOMEs inits supporting technology stack:/u01/oracle/prodcomn/admin/scripts/PROD_alktsvr02/adautocfg.sh

2. Verify Applications profile options in Oracle Applications


7

Log into Release 11i with the System Administrator responsibilityNavigate to the Profile > System formQuery 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 true*

ICX_DISCOVERER_VIEWER_LAUNCHER URL that points to Discoverer Viewer Servlet alktsvr02.qgpc.net

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

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

3. Regenerate your Business ViewsMost of the Discoverer folders delivered as part of the Oracle E-Business Suite Release 11iDiscoverer content is 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.3.1. Regenerate your Business Views by running the "Generate Business Views byApplication" concurrent program using the Business View Setup responsibility:Logon to Oracle Applications as SYSADMINChoose the "Business Views Setup" responsibilityNavigate to Reports > Run > Pick Single Request > "Generate ALL Business Views"In case you do not have "Business Views Setup" responsibility assigned to SYSADMIN user, please do the following:Logon to Oracle Applications as SYSADMINChoose the "System Administrator" responsibilityNavigate to Security > User > Define and add responsibility "Business Views Setup" to user SYSADMIN.3.2. After regeneration of the Business Views has been completed, check the Business View


8

Generator output file. It should not contain any errors.Recompile all objects in the APPS schema using adadmin.

4. 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.4.1. Grant End User Layer Administration PrivilegesGrant the End User Layer Administration privileges for user SYSADMIN use the Discoverer Administrator to Grant them. 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.4.2. Make sure user SYSADMIN has full security access to all Business AreasThis 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.

5. Access directory AU_TOP/discover on your E-Business Suite 11i instance from your Oracle Business Intelligence 10g BI instanceDiscoverer .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 Business IntelligenceServer 10g Release 2 was installed.Please mount your applications tier server node, directory AU_TOP/discover on your 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. Import Discoverer Content for Release 11i using adupdeul.sh mode=completeIn this step, you will run AD utility adupdeul.sh on the standalone application server where Oracle Business Intelligence Server 10g Release 2 was installed to import the Discoverer loader files (.eex files) for Oracle E-Business Suite Release 11i into the Discoverer End User Layer.6.1. On the application server where Oracle Business Intelligence Server 10g Release 2 was installed, move to the mounted or copied ... \discover\ directory where adupdeul.sh is located6.2. Start the import process of the Discoverer loader files (.eex files) using the shell script

sh adupdeul.sh \ connect=sysadmin/sysadmin@prod \ resp="System Administrator" \ gwyuid=APPLSYSPUB/PUB \ fndnam=APPS \ secgroup="Standard" \ topdir=/u01/oracle/prodappl/au/11.5.0/discover \ language=US \ eulprefix=EUL \ eultype=OLTP \ mode=complete \ iashome=/u01/bi/biHome \ logfile=/u01/bi/import_complete_eul_us_cust115.log


9

6.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 .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.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:<topdir>\<language>\<file>.eex: The import process did not import or modify any dataThis messages provides information that <file>.eex is an empty obsolete file and does not modifyany data during import.<topdir>\<language>\<file>.eex: The identifier for ... contains one or more of the characters ! ~ - * () ' which will be de-supported for use in identifiers in future releases of Discoverer - see release notes for more details.You can safely ignore this message using Discoverer 10.1.2. See release notes for more details.

7. 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 UserLayer 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.7.1. 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.


10

Discoverer Components URL’s

URL Component

http://alktsvr02.qgpc.net:7778/discoverer/plus Discoverer Plushttp://alktsvr02.qgpc.net:7778/discoverer/viewer Discoverer Viewerhttp://alktsvr02.qgpc.net:1156 Enterprise Manager


11

Startup and Shutdown Procedures

The procedures below serve as a quick reference for trained Database Administrators for starting and shutting down an Discoverer Services and Enterprise Manager.

Normal Startup

Database:

1. Log on to the prod server as the user: bi

2. Run the startup command as following:

$ opmnctl startall # Starting the Discoverer Services

$ emctl start iasconsole # Starting the Enterprise Manager

The PATH environment variable for bi must include the path for Database control scripts: /u01/bi/biHome/opmn/bin

Normal Shutdown

Database :

1. Log on to the prod server as the user: bi

2. Run the shutdown command as following:

$ emctl stop iasconsole # Closing the Database

$ opmnctl stopall # Closing the Database Listener

The PATH environment variable for bi must include the path for Database control scripts: /u01/bi/biHome/opmn/bin


12

Documentation and Notes Used

Oracle Documentation:Using Discoverer 10.1.2 with Oracle E-Business Suite 11i - Note:313418.1Oracle Discoverer DocumentationOracle Application Server 10g Release 2 DocumentationOracle Application Server (10gAS) with Oracle E-Business Suite Release 11i Documentation (Note207159.1)Oracle Applications System Administrators Guide


13

al-koot discoverer installation

Documents

business suite 11i

end user layer

business views setup

standalone application server

document control purposes

discoverer loader files

oracle applications manager

path environment variable