понедельник, 1 марта 2010 г.

Oracle Discoverer 10g Installation with Oracle E-Business Suite Release 11i

E-Business Suite 11i Host: app.myhost.com
Discoverer 10g Host:
app2.myhost.com

Step 1:

We must install Oracle Business Intelligence 10g Release 2 in a seperate ORACLE_HOME from the previously installed Oracle E-Business Suite Infrastructure.
Using Custom Port Numbers, until installation if necessary.
Ex: cd $ORACLE_HOME
touch staticports.ini
vim staticports.ini
Oracle HTTP Server port = 17380
Oracle HTTP Server Listen port = 17380
Discoverer Preference port = 17381

Step 2:
Configuration with E-Business Suite 11i
In New Discoverer 10g home Create a directory with name ‘secure’
$ORACLE_HOME/discoverer> mkdir secure
Then copy ‘hostname_sid.dbc’ file from FND_TOP/secure of application tier
Ex: FND_TOP/secure > cp –rp app_pr.dbc
/discoverer/secure
Change the owner and group to dbc file.
Ex: chown discouser:dba app_pr.dbc

Step 3:
Include the tnsnames entry to connect to Oracle E-Business Suite11i database.

Ex:

Copy TNS entry for app2 from (11itns_admin) to discoverer’s
/network/admin/tnsnames.ora

Step 4:

Configure JInitiator
Specify Java Virtual Machine for Discoverer Plus, On the Oracle Business
Intelligence 10g file system.

Ex:

  • http://app2.myhost.com:1156/emd
  • 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 , for example
    CAFECAFE-0013-0001-0022-ABCDEFABCDEF" plugin_setup="http://app2.myhost.com:7780/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.24, for example
    CAFECAFE-0013-0001-0024-ABCDEFABCDEF" plugin_setup="http://app2.myhost.com:7780/jinitiator/jinit13124.exe" version="1.3.1.24" versionie="1,3,1,24" 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.24 executable to the $ORACLE_HOME/jinit directory as jinit13124.exe.
  • Restart the Discoverer services using opmn.
  • Verify that Discoverer Plus is now using JInitiator 1.3.1.24:
    http://app2.myhost.com:7780/discoverer/plus
Step 5:
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 below:

s_disco_standalone True
s_disco_machine ex:app2.myhost.com
s_disco_port 7778
s_disco_protocol http
s_disco_ver_comma 10,1,2
s_disco_eul_prefix EUL
s_discostatus disabled

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

Ex: % /admin/scripts//adautocfg.sh

Step 6:

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

ICX_DISCOVERER_VIEWER_LAUNCHER Ex: http://app2.myhost.com:7778/discoverer
/viewer?Connect=[APPS_SECURE]

ICX_DISCOVERER_RELEASE Ex: 10

ICX_DISCOVERER_USE_VIEWER Ex: Yes

ICX_DEFAULT_EUL Ex: EUL5

ICX_DISCOVERER_EUL_LANGUAGE Ex: US

ICX_DISCOVERER_PARAMETERS Ex: exitURL=http://app2.myhost.com:8038/OA_HTM/OA.jsp?OAFunc=OAHOMEPAGE


Step 7:

Increase the timeout value in httpd.conf to 3600
# Change $ORACLE_HOME/discoverer/discwb.sh
# FND_TOP=$OH/discoverer
FND_TOP= fnd top of middle tier


Step 8:

Managed SQL*Net Access from Hosts

Oracle Applications Manager provides a wizard to restrict SQL*Net access to the database from your middle-tier hosts. If you enable the SQL*Net Access security option, you can select which hosts have SQL*Net access to the database. (Navigation: Oracle Applications Manager=>Applications Dashboard=>Security=>Manage Security Options)

Using this wizard you can specify a list of hosts that can access the Oracle Applications Database via SQL*Net. To do so, you need to complete the following tasks.

  1. Run this wizard.
  2. Run AutoConfig on Database Tier.
  3. Bounce the TNS Listener for the new settings to take effect

Note: All virtual hosts will have to be manually reconciled with the appropriate physical mapping i.e. individual physical machines will have to be registered. You cannot specify subnet masks. You can only register a resolvable network address.

Step 9:

Check SESSION COOKIE DOMAIN

select SESSION_COOKIE_DOMAIN from apps.icx_parameters;

If is wrong then

update apps.ICX_PARAMETERS set SESSION_COOKIE_DOMAIN='.yourdomain.com';
commit;









Комментариев нет:

Отправить комментарий