|
|
*************************************************************
This article is being delivered in Draft form and may contain
errors. Please use the MetaLink "Feedback" button to advise
Oracle of any issues related to this article.
*************************************************************
PURPOSE
-------
The purpose of this document is to provide step-by-step instructions on
Installing Portal 9.0.2.x in a remote database
SCOPE & APPLICATION
-------------------
This document is intended for users trying to configure Portal 9.0.2.x in a
separate database and would use the existing R2 midtier to install and access
this Portal repository.
Installing Portal 9.0.2.x in a Remote Database
----------------------------------------------
Configuring Portal in a separate database cannot be performed using the default
"out-of-box" iAS R2 installation. Setting this up would require post
installation tasks which are mentioned below. The assumption here is that the
user is trying to configure Portal in a separate database and would use the
existing R2 midtier to install and access this Portal repository.
1. Setting up the target database
=================================
(a) The minimum requirement of the database version is 9.0.1.3 + the RDBMS
bundle patch required by iAS 9.0.2.
(b) The database should be configured with Java and Intermedia options.
(c) The minimum database resources required are :
db_block_size=8192
db_cache_size=50331648
java_pool_size=58720256
large_pool_size=0
shared_pool_size=109051904
job_queue_process (should be set and the value should
be greater than 1) @bug 2165131
The above are install time requirements for Portal. Once installed
these resources could be reduced during the runtime access.
To check your settings, do the foll:
From SQL*PLUS as SYS user, run the foll. query:
select name, value from V$parameter
where lower(name) in ('java_pool_size', 'large_pool_size',
'shared_pool_size', '_system_trig_enabled', 'db_block_size',
'db_cache_size', 'open_cursors', 'max_enabled_roles',
'mts_dispatchers', 'sessions', 'processes', 'job_queue_process')
order by name;
(d) The tablespace requirements are :
i) The SYSTEM tablespace should have atleast 150 MB of available free
space during the Portal installation.
ii) The tablespace to be selected for Portal should have initial storage
of atleast 75 MB.
iii) The index tablespace to be selected for Portal should have initial
storage of atleast 20 MB.
iv) The Document tablespace and Logging tablespace to be selected for
Portal should have initial storage of atleast 4 MB.
v) The Temporary tablespace to be selected for Portal should have
initial storage of atleast 20 MB.
(e) The PL/SQL LDAP API's (DBMS_LDAP_UTL) must be installed in the database.
These are not installed by default on fresh database. The
$OH/rdbms/admin/catldap.sql should be run for installing PL/SQL
LDAP API's.
2. Installing the 9iAS midtier
==============================
You must install Oracle9iAS 9.0.2.0.1. During the install, you MUST check
the checkbox for Configuring Portal.
If you have multiple Portal repositories or midtier involved in your setup,
you MUST have the one-off's 2513540 and 2465409 patches applied
3. Installing Portal repository
===============================
Note
====
There is a restriction in 9.0.2 where two Portal schemas named 'portal'
cannot share the same OID instance. Basically you cannot have multiple
Portal schemas having the same name in different databases and share
the same OID instance. There is an internal bug filed on the issue.
@bug 2365105
If the database is 9.2.0.1.0, you must apply one-off patch 2430504 or patchset
to go to DB 9.2.0.2.0. This one-off patch 2430504 is only available for UNIX
platforms. For windows, you have to be on DB 9.2.0.2.0
The script $ORACLE_HOME/assistants/opca/ptlasst.csh ( ptlasst.bat on Windows)
should be used for installing and configuring Portal. This script supports
several modes for different requirements and this internally calls the
Oracle Portal Configuration Assistant (OPCA) with all the required parameters
The ptlasst.csh is a c shell script and it is recommended to run this in a
tcsh or csh shell environment.
An example usage for installing Portal repository :
ptlasst.csh -i typical -mode PORTAL -s portal -c ids-pc:1521:m10
-p change_on_install -u portal -t portal_tmp -d portal_doc -l portal_log
-in portal_idx -demo -silent -verbose -report -owa
where :
-s : Portal schema name
-c : Database connect string in the host:port:sid format
-p : SYS password
-u : Default tablespace
-t : Temporary tablespace
-d : Document tablespace
-l : Logging tablespace
-in : Index tablespace
-demo : Portlet builder demo components would be installed.
-silent : Silent installation. (UI is not supported for most of the modes in R2)
-verbose : This parameter would enable the logging in detail mode. Recommended.
-report : This parameter enables the Oracle Reports integration with Portal.
-owa : This parameter installs the PL/SQL Web Toolkit and other SYS schema
packages. This need to be installed just once in the database.
This option has the same functionality as the -mode SYSOBJECTS mode.
Note
====
If you are running this in a Linux box, please read the following :
The OPCA uses shell scripts named runimp.csh located at the
$OH/assistants/opca dir during the Portal repository installation. These
shell scripts start with ":" to indicate that it a shell script but in the
Linux platform it is not able to resolve this directive. Replace
the ":" with "#!/bin/sh" in the above mentioned script file and run the
Portal repository installation.
This script file would generate a <portal_schema>.log in the
$ORACLE_HOME/assistants/opca dir where <portal_schema> is the Portal schema
name.
Check for errors like ORA-, PLS-, SP2-, ERROR: in the log file.
In Unix flavors, the following command should do the search :
egrep -n '^ERROR|ERROR:|ORA-|PLS-|SP2-|IMP-' $log_file
Note
====
There should not be any errors before you proceed to the step (4).
4. Wiring the Midtier with the installed Portal repository
==========================================================
(a) Create a new DAD in the midtier for accessing this Portal repository.
i) Access the Midtier node in the OEM
ii) Click on the HTTP server link
iii) Click on the PLSQL Properties link
iv) Create the DAD with all the information asked in this page.
v) Restart the HTTP server.
(b) Wire the midtier with the Portal repository.
An example usage of wiring this Portal repository with an existing SSO and
OID of the Infrastructure database is :
ptlasst.csh -i custom -mode MIDTIER -s portal -sp portal
-c myhost.domain.com:1521:mySID -sdad portal -o orasso -op orasso
-odad orasso -host myApache.domain.com -port 7777 -chost myApache.domain.com
-cport_a 4000 -cport_i 4001 -silent -verbose -ldap_h myOID.domain.com
-ldap_p 4032 -ldap_d cn=orcladmin -ldap_w welcome -pwd portal902 -portal_only
-sso_c myhost.domain.com:1521:mySID -sso_h myApache.domain.com -sso_p 7777
-mi true -pa orasso_pa -pap orasso_pa -ps orasso_ps -pp orasso_ps
-pd portal_dblink -p_tns orasso_ps -s_tns portal
where :
-i : Installation type. Use 'custom' in this case.
-s : Portal schema name
-sp : Portal schema password
-c : Connect string in the format host:port:sid to the database where
Portal repository is installed.
-sdad : Portal DAD
-o : SSO schema name (orasso)
-op : SSO schema password
-odad : SSO DAD name (orasso)
-host : HTTP server host name (with domain) of the midtier
-port : HTTP server port of the midtier
-chost : webcache hostname
-cport_a : webcache administration port
-cport_i : webcache invalidation port
-silent : Silent installation.(UI is not supported for most of the modes in R2)
-verbose : This parameter would enable the logging in detail mode. Recommended.
-ldap_h : OID host name (with domain) of the Infrastructure install
-ldap_p : OID Port of the Infrastructure install
-ldap_d : Administration DN
-ldap_w : Password of the Administration DN. (iAS instance password of the
Infrastructure install)
-pwd : Password of the portal user user for logging in to portal.
-portal_only : Specifies Portal only midtier configuration
-sso_c : Connect string in the format host:port:sid to the database where
SSO repository is installed. (Infrastructure)
-sso_h : HTTP server host name ( with domain) of the Infrastructure.
-sso_p : HTTP server port of the Infrastructure.
-mi : Midtier install. Set it to "true" in this case.
-pa : SSO Partner application schema name of the Infrastructure.(orasso_pa)
-pap : SSO Partner application schema password of the Infrastructure
-ps : SSO Password store schema name of the Infrastructure. (orasso_ps)
-pp : SSO Password store password of the Infrastructure.
-pd : Name of the database link for connecting from Portal schema to orasso
password store across database instances.
-p_tns : TNS connect string to Password Store. The tns alias should be created
in the m/c where Portal database is installed.
-s_tns : TNS connect string to Portal. The tns alias should be created in
the m/c where Infrastructure is installed.
This script file would generate a <portal_schema>.log in the
$ORACLE_HOME/assistants/opca dir where <portal_schema> is the Portal
schema name.
Check for errors like ORA-, PLS-, SP2- , ERROR: in the log file.
In Unix flavors, the following command should do the search :
egrep -n '^ERROR|ERROR:|ORA-|PLS-|SP2-|IMP-' $log_file
Note
====
There should not be any errors in the log file before you try to access
the Portal.
5. Synchronize the OID
========================
Run the scripts "secrmoid.sql" and "secoidd.sql" to synchronize the
Portal schema in OID.
Run them on the middle-tier server as portal schema owner (portal)
The scripts reside in ORACLE_HOME/portal/admin/plsql/wwc
secrmoid <oid-hostname> <oid-port> <oid-admin DN> <oid-password> PORTAL
<schema name> <subscriber id>
secoidd <oid-hostname> <oid-port> <oid-admin DN> <oid-password> Y <init pwd>
For example:
============
sqlplus portal/Q3AbLjLs@iasdb
SQL> @secrmoid ias2_oid.us.oracle.com 4032 cn=orcladmin welcome1 portal portal 1
SQL> @secoidd ias2_oid.us.oracle.com 4032 cn=orcladmin welcome1 Y welcome1
6. Edit the DAD pointing to customer database
==============================================
Please follow note 208598.1 available on metalink
References
----------
note 198800.1 How to get the Portal schema password of the Infrastructure DB
note 208598.1 ERROR: VARIABLES IN FORM NOT IN PROCEDURE: P_PATH when
using Direct Access URL for Portal 9.0.2 in customer database