2.Discoverer 10.1.2 must be installed in a separate ORACLE_HOME on an existing application tier server node or on a stand-alone server, accessing an Oracle E-Business Suite Release 11i database.
3.The following components must be used on the stand alone instance.
Oracle application server 10g Release 2 10.1.2
Oracle Business Intelligence 10.1.2
Section 1: Installation Tasks
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.1. Install OracleAS Identity Management Infrastructure 10g (10.1.4.0.1)
You must install OracleAS Identity Management Infrastructure 10g (10.1.4.0.1) on a standalone server or in a separate ORACLE_HOME on an existing application tier server node.
1.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 seperate ORACLE_HOME from the previously installed OracleAS Infrastructure. During installation of Oracle Application Server 10g Release 2 (10.1.2.0.2) type Business Intelligence and Forms you will be prompted for Oracle Internet Directory details. Please provide your Oracle Application Server 10g (10.1.4.0.1) Infrastructure hostname and port number as configured in step 1.1.
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, and Discoverer Viewer 10g. You must install Oracle Application Server 10g Release 2 on a standalone server accessing an Oracle E-Business Suite Release 11i database or in a separate ORACLE_HOME on an existing application tier server node."
1.3. Copy Database Connection file
Discoverer 10.1.2 supports Single Sign-On functionality with Oracle E-Business Suite Release 11i. To support Single Sign-On, Discoverer needs access to the Database Connection (dbc) file for the database you wish to connect to. A dbc file is a text file which stores all the information required to connect to a particular database.
In the 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 directory 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.4. 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 11i database. Use the same entry as exists in the tnsnames.ora file on your Oracle E-Business Suite Release 11i 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 11i database using sqlplus.
2. Apply the latest certified Discoverer Plus and Viewer Patches
AIX Paltform(only for 10.1.2.0.0): Apply patchset 10.1.2.1.0 delivered via patch 4908436 available on Metalink for download.
3. Migrate your existing Discoverer End User Layers to Discoverer 10.1.2.
Upgrade 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 1.
$ORACLE_HOME/bin/eulapi -CONNECT
If you are migrating your Discoverer 4i End User Layer, the upgrade process creates a new Discoverer 10.1.2 End User Layer based the existing Discoverer 4i End User Layer. The existing Discoverer 4i End User Layer remains unchanged. A new schema containing the Discoverer 10.1.2 End User Layer will be created under the same Database User. After migration, the Database User contains functional End-User Layers for both Discoverer 4i and 10g. After verifying that the upgrade was successful, you may drop the 4i End-User Layer.
Section 2 : Postinstallation 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. Apply necessary Oracle Applications interoperability patches using AutoPatch
A) Apply AD patch 5765314
This patch contains utilities for Discoverer End User Layer maintainance.
B) Apply ICX patch 3133021
This patch contains support to invoke Discoverer from E-Business Suite functions.
2. Set Applications Profile Options for Discoverer using AutoConfig
By default, AutoConfig configures profile options for Oracle E-Business Suite Release 11i environments for Discoverer 4i. Proceed with the following steps to allow AutoConfig 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.
3. Set Applications Profile Options for Discoverer using AutoConfig
By default, AutoConfig configures profile options for Oracle E-Business Suite Release 11i environments for Discoverer 4i. Proceed with the following steps to allow AutoConfig 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.
Configure standalone discoverer, Discoverer Machine name, Discoverer port, Discoverer protocol,
Disco version comma discovery eul prefix.
4. After that you have to run autoconfig
-Verify Applications profile options in Oracle Applications
Log into Release 11i with the System Administrator responsibility
Navigate to the Profile > System form
Query the %Discoverer% profile options.
Verify the following ICX profile options in Oracle Applications
ICX_DISCOVERER_LAUNCHER=http://:/discoverer/plus?Connect=[APPS_SECURE]
ICX_DISCOVERER_VIEWER_LAUNCHER=http://:/discoverer/viewer?Connect=[APPS_SECURE]
ICX_DISCOVERER_RELEASE=10
ICX_DISCOVERER_USE_VIEWR=Y N
ICX_DEFAULT_EUL=EUL
ICX_DISCOVERER_EUL_LANGUAGE=US
ICX_DISCOVERER_PARAMETERS=exitURL=http://:/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE
Note:
When you open the discoverer EUL using the Discoverer 10g Desktop/Admin it will ask you if you want to upgrade your EUL and you have to choose yes.
To start/stop the new discoverer do the following:
$Disco_ORACLE_HOME/opmn/bin/opmnctl stopall (to stop).
$Disco_ORACLE_HOME/opmn/bin/opmnctl startall (to start).
No comments:
Post a Comment