Oracle® Application Server Portal Configuration Guide 10g (9.0.4) Part Number B10356-01 |
|
OracleAS Portal Configuration Assistant (OPCA) is a Java-based configuration tool for installing and configuring the OracleAS Portal schema in the Oracle Application Server Metadata Repository.
In a typical Oracle Application Server installation, the Oracle Universal Installer (OUI) automatically invokes OPCA in the post-installation phase. OPCA can also be invoked standalone.
In an Oracle Application Server installation, the OracleAS Portal installation is performed in two phases:
Section 3.1, "How Does the Installation Process Work?" for more information on installing OracleAS Portal, and installing the portal repository in an existing database.
See Also:
OracleAS Portal provides the command line script ptlasst
to invoke OPCA in standalone mode. This appendix describes the usage of ptlasst
, and the configuration options available in standalone mode. Specific topics covered include:
The scripts ptlasst.csh
(UNIX) and ptlasst.bat
(Windows NT/2000) are located in the ORACLE_HOME
/assistants
directory and can be used to run the OPCA standalone in different modes. To use ptlasst
, perform the following steps:
First, set the ORACLE_HOME
environment variable to the Oracle Application Server Home. You can then start the OPCA from the command line by navigating to the ORACLE_HOME
/assistants/opca
directory and using the command:
ptlasst.bat -mode {PORTAL | SSO | MIDTIER | LANGUAGE | SYSOBJECTS | DEINSTALL } {mode-dependent-parameters}
First set the ORACLE_HOME
environment variable to the Oracle Application Server Home. You can start the OPCA from the command line by navigating to the ORACLE_HOME
/assistants/opca
directory and using the command:
ptlasst.csh -mode {PORTAL | SSO | MIDTIER | LANGUAGE | SYSOBJECTS | DEINSTALL } {mode-dependent-parameters}
ptlasst
in upper case.
ptlasst
generates a log file each time it is run. The log file generated is named portal_schema_name
.log
, and it is located in the directory ORACLE_HOME
/assistants/opca
.
ptlasst.README
, located in the directory ORACLE_HOME
/assistants/opca
contains the usage information for ptlasst
, also listed in this appendix.
ptlasst
commands, like the portal, or OracleAS Single Sign-On partner application schema password, issue the following LDAP command:
ldapsearch -h directory_host_name -p directory_port -D directory_bind_dn -w directory_bind_dn_password -b "orclReferenceName=infrastructure_database" "orclresourcename=<schema_name>" orclpasswordattribute
Where <schema_name>
is the name of the schema. For example, PORTAL
, ORASSO_PA
, or ORASSO_PS
, as shown in Example B-1:
ldapsearch -h m1.abc.com -p 389 -D "cn=orcladmin" -w welcome1 -b "orclReferenceName=portal.abc.com,cn=IAS Infrastructure Databases,cn=IAS,cn=Products,cn=oraclecontext" "orclresourcename=PORTAL" orclpasswordattribute
Alternatively, you can use Oracle Directory Manager to obtain the password information. Drill down to orclResourceName=schema_name, where schema_name is the name of the schema for which you want to obtain the password. Click the entry and look for the orclpasswordattribute
attribute value on the right panel. This value is the password for the selected schema.
See Also:
Oracle Internet Directory Administrator's Guide for information on how to use Oracle Directory Manager. |
The following table contains a description of the different modes:
This mode installs the OracleAS Metadata Repository in the target database. No information from the middle-tier is required. It should be used for the OracleAS Portal seed database creation.
MID_TIER_ORACLE_HOME
in which OracleAS Portal is installed.
ptlasst.csh -mode PORTAL -c connect_string -p sys_password -voh source_home -oh oracle_home -log log_dir [-s portal_schema] [-u user_tablespace] [-t temp_ tablespace] [-d doc_tablespace] [-l logging_tablespace] [-in index_tablespace] [-demo] [-owa]
Table B-2 lists and describes parameters supported for the PORTAL mode.
ptlasst.csh -mode PORTAL -s portal -c myDBhost.domain.com:1521:dbServiceName -p change_on_install -u users -t temp -d users -l users -in users -demo -owa -voh /private1/repca -log /private1/log -oh /private1/dbhome
Configures OracleAS Portal middle-tier to use an existing OracleAS Portal schema.
The MIDTIER mode uses the option -type
to determine which components to configure. The different types that are supported in the MIDTIER mode are:
If possible, use the Portal Dependency Settings file and tool to perform middle-tier configuration. If you use
After you update the
Shown subsequently is a mapping of various
There are, however, some cases in which you do need to use OPCA in the MIDTIER mode. For example, in the scenario where your published hostname is different from the hostname used for OracleAS Web Cache invalidation, you cannot use the Portal Dependency Settings file, to establish this configuration.
For more information about the Portal Dependency Settings file, and tool, refer to Appendix A, "Using the Portal Dependency Settings File".
Note:
ptlasst
, the Portal Dependency Settings file (iasconfig.xml
) does not get updated, and using iasconfig.xml
for subsequent configurations may cause your site to be misconfigured.
iasconfig.xml
, you must run the Portal Dependency Settings tool (ptlconfig
) to update the OracleAS Metadata Repository with the configuration settings in iasconfig.xml
.
ptlasst
MIDTIER types and their Portal Dependency Settings tool (ptlconfig
) counterparts:
ptlconfig -dad <dad> -wc.
ptlconfig -dad <dad> -oid.
ptlconfig -dad <dad> -site
.
MID_TIER_ORACLE_HOME
in which OracleAS Portal is installed.
MID_TIER_ORACLE_HOME
in which OracleAS Portal is installed.
ptlasst.csh -mode MIDTIER [ -type {ALL | OID | SSO | OHS | WEBCACHE | DIPREG | DIPUNREG} ] {type-dependent-parameters}
Table B-3 lists and describes parameters supported for the MIDTIER mode.
ptlasst.csh -mode MIDTIER -type OID -ldap_w orcladmin_password -pwd ias_admin_ password [-i install_type] [ -s portal_schema] [-sp portal_schema_password] [-c portal_db_connect_string] [-ldap_h oid_host_name] [-ldap_p oid_port_number] [-ldap_d oid_admin_user] [-ldaps]
Typical installation (-i typical)
Uses the repository access APIs to get the details of Oracle Internet Directory, and the OracleAS Portal schema in the configured OracleAS Metadata Repository.
ptlasst.csh -mode MIDTIER -type OID -ldap_w welcome1 -pwd welcome1
Custom installation (-i custom)
This example takes the input provided on the command line.
ptlasst.csh -mode MIDTIER -type ALL -i custom -ldap_w welcome1 -pwd welcome1 -s portal -sp portal -c myDBhost.domain.com:1521:dbServiceName -ldap_h myOID.domain.com -ldap_p 389
ptlasst.csh -mode MIDTIER -type SSO -host portal_site_name -port portal_site_ port [-i install_type] [ -s portal_schema] [-sp portal_schema_password] [-sdad portal_dad] [-c portal_db_connect_string] [-sso_c sso_db_connect_string] [-pap partner_application_password] [-pp password_store_password]
OracleAS Portal is a partner application to the Oracle Application Server Single Sign-On. As such, it must be configured to use an OracleAS Single Sign-On for authentication services. When OracleAS Portal is installed, it is automatically configured to use the OracleAS Single Sign-On installed during the infrastructure installation.
See Also:
|
What was called the ssodatax
script, in versions 3.0.x of OracleAS Portal, has been obsoleted and replaced by running the OracleAS Portal Configuration Assistant in -mode MIDTIER -type SSO. When you install OracleAS Portal, the step previously done by ssodatan
, is done automatically. However, after installation, there may be various reasons for configuring OracleAS Portal to use a different OracleAS Single Sign-On, or needing to re-run the configuration, because of a change in the hostname, port or protocol of the Oracle Application Server Single Sign-On.
Whereas the old ssodatax
required you to set up the partner application entry in the SSO server and then invoke the script with the site_id
, site_token
, and encryption_key
obtained from partner application registration, the -mode MIDTIER -type SSO mode of ptlasst.csh
(OPCA) no longer requires partner application registration to be a two-step process.
The OracleAS Single Sign-On now provides a schema ORASSO_PA (default) for accessing the partner application registration procedure. You will need to get the password to this schema and an appropriate connect string to the OracleAS Single Sign-On instance to register the OracleAS Portal entry.
Typical installation (-i typical)
Uses the repository access APIs to get the details of OracleAS Single Sign-On, and the OracleAS Portal schema in the configured OracleAS Metadata Repository.
ptlasst.csh -mode MIDTIER -type SSO -host mySite.domain.com -port 7777 -sdad portal
Custom installation (-i custom)
This example takes the input provided on the command line.
ptlasst.csh -mode MIDTIER -type SSO -i custom -host mySite.domain.com -port 7777 -s portal -sp portal -sdad portal -c myDBhost.domain.com:1521:dbServiceName -sso_c myDBhost.domain.com:1521:dbServiceName -pap orasso_pa -pp orasso_ps
ptlasst.csh -mode MIDTIER -type WEBCACHE -host portal_site_name -port portal_ site_port -cport_i webcache_invalidation_port -cport_a webcache_administration_ port -wc_i_pwd webcache_invalidator_password [-chost webcache_hostname] [-i install_type] [ -s portal_schema] [-sp portal_schema_password] [-sdad portal_ dad] [-c portal_db_connect_string] [-wc webcache_on_off_flag]
Typical installation (-i typical)
Uses the repository access APIs to get the details of the OracleAS Portal schema in the configured OracleAS Metadata Repository.
ptlasst.csh -mode MIDTIER -type WEBCACHE -host mySite.domain.com -port 7777 -cport_i 4001 -cport_a 4001 -wc_i_pwd webcache_invalidator_password
Custom installation (-i custom)
This example takes the input provided on the command line.
ptlasst.csh -mode MIDTIER -type WEBCACHE -i custom -host mySite.domain.com -port 7777 -cport_i 4001 -cport_a 4001 -s portal -sp portal -sdad portal -c myDBhost.domain.com:1521:dbServiceName -wc_i_pwd webcache_invalidator_password
ptlasst.csh -mode MIDTIER -type OHS -host portal_site_name -port portal_site_ port -cport_i webcache_invalidation_port -cport_a webcache_administration_port -wc_i_pwd webcache_invalidator_password [-chost webcache_hostname] [-i install_ type] [ -s portal_schema] [-sp portal_schema_password] [-sdad portal_dad] [-c portal_db_connect_string] [-sso_c sso_db_connect_string] [-pap partner_ application_password] [-pp password_store_password] [-wc webcache_on_off_flag] [-ssl]
Typical installation (-i typical)
Uses the repository access APIs to get the details of the OracleAS Portal schema in the configured OracleAS Metadata Repository.
ptlasst.csh -mode MIDTIER -type OHS -host mySite.domain.com -port 7777 -cport_i 4001 -cport_a 4001 -wc_i_pwd webcache_invalidator_password
Custom installation (-i custom)
This example takes the input provided on the command line.
ptlasst.csh -mode MIDTIER -type OHS -i custom -host mySite.domain.com -port 7777 -cport_i 4001 -cport_a 4001 -s portal -sp portal -sdad portal -c myDBhost.domain.com:1521:dbServiceName -sso_c myDBhost.domain.com:1521:dbServiceName -pap orasso_pa -pp orasso_ps -wc_i_pwd webcache_invalidator_password
ptlasst.csh -mode MIDTIER -type ALL -host portal_site_name -port portal_site_ port -cport_i webcache_invalidation_port -cport_a webcache_administration_port -ldap_w orcladmin_password -pwd ias_admin_password -emport em_port_number -wc_ i_pwd webcache_invalidator_password -iasname ias_instance [-chost webcache_ hostname] [-i install_type] [ -s portal_schema] [-sp portal_schema_password] [-sdad portal_dad] [-c portal_db_connect_string] [-sso_c sso_db_connect_string] [-pap partner_application_password] [-pp password_store_password] [-wc webcache_ on_off_flag] [-ldap_h oid_host_name] [-ldap_p oid_port_number] [-ldap_d oid_ admin_user] [-ldaps] [-ultrasearch] [-syndication] [-ssl]
Typical installation (-i typical)
Uses the repository access APIs to get the details of Oracle Internet Directory, OracleAS Single Sign-On, and the OracleAS Portal schema in the configured OracleAS Metadata Repository.
ptlasst.csh -mode MIDTIER -type ALL -host mySite.domain.com -port 7777 -cport_i 4001 -cport_a 4001 -ldap_w welcome1 -pwd welcome1 -wc_i_pwd webcache_ invalidator_password -emport 1812 -iasname as_midtier
Custom installation (-i custom)
This example takes all the input provided on the command line. This should be used if the configuration is performed on an OracleAS Portal instance other than the out-of-the-box installation.
ptlasst.csh -mode MIDTIER -type ALL -i custom -host mySite.domain.com -port 7777 -cport_i 4001 -cport_a 4001 -ldap_w welcome1 -pwd welcome1 -s portal -sp portal -sdad portal -c myDBhost.domain.com:1521:dbServiceName -sso_c myDBhost.domain.com:1521:dbServiceName -pap orasso_pa -pp orasso_ps -wc_i_pwd webcache_invalidator_password -ldap_h myOID.domain.com -ldap_p 389 -emport 1812 -iasname as_midtier
This type should be used to create the provisioning profiles in Oracle Internet Directory. Refer to Section 6.1.6.3, "Relationship Between OracleAS Portal and Oracle Internet Directory" for more information about provisioning profiles.
ptlasst.csh -mode MIDTIER -type DIPREG -ldap_w orcladmin_password [-i install_ type] [ -s portal_schema] [-sp portal_schema_password] [-c portal_db_connect_ string] [-ldap_h oid_host_name] [-ldap_p oid_port_number] [-ldap_d oid_admin_ user]
Typical installation (-i typical)
Uses the repository access APIs to get the details of Oracle Internet Directory, and the OracleAS Portal schema in the configured OracleAS Metadata Repository.
ptlasst.csh -mode MIDTIER -type DIPREG -ldap_w welcome1
Custom installation (-i custom)
This example takes the input provided on the command line.
ptlasst.csh -mode MIDTIER -type DIPREG -i custom -ldap_w welcome1 -s portal -sp portal -c myDBhost.domain.com:1521:dbServiceName -ldap_h myOID.domain.com -ldap_ p 389
This type should be used to delete the provisioning profiles in Oracle Internet Directory of the OracleAS Portal instance. Refer to Section 6.1.6.3, "Relationship Between OracleAS Portal and Oracle Internet Directory" for more information about provisioning profiles.
ptlasst.csh -mode MIDTIER -type DIPUNREG -ldap_w orcladmin_password [-i install_ type] [ -s portal_schema] [-sp portal_schema_password] [-c portal_db_connect_ string] [-ldap_h oid_host_name] [-ldap_p oid_port_number] [-ldap_d oid_admin_ user]
Typical installation (-i typical)
Uses the repository access APIs to get the details of Oracle Internet Directory, and the OracleAS Portal schema in the configured OracleAS Metadata Repository.
ptlasst.csh -mode MIDTIER -type DIPUNREG -ldap_w welcome1
Custom installation (-i custom)
This example takes the input provided on the command line.
ptlasst.csh -mode MIDTIER -type DIPUNREG -i custom -ldap_w welcome1 -s portal -sp portal -c myDBhost.domain.com:1521:dbServiceName -ldap_h myOID.domain.com -ldap_p 389
Installs the strings for a specific language in the OracleAS Portal schema.
OracleAS Portal is designed to allow application development and deployment in different languages. This allows developers to work in their own language when they build portals. In addition, the self-service content management supports multiple languages so that end users can provide documents and other content in different languages.
OracleAS Portal is configured with the languages that are selected in the Oracle Universal Installer (OUI) during the Oracle Application Server middle-tier installation. Languages that are configured show up in the Set Language portlet. You can use OracleAS Portal in the language that corresponds to the language setting in the browser, or to the language you have selected in the Set Language portlet. To configure additional languages after installation, the OracleAS Portal Configuration Assistant (OPCA) must be used in LANGUAGE mode.
Table B-4 shows the languages that are available for OracleAS Portal.
To install languages, after you have installed OracleAS Portal, run ptlasst
in the LANGUAGE mode. You must run ptlasst
with -mode LANGUAGE
for each language that you want OracleAS Portal to support.
MID_TIER_ORACLE_HOME
in which OracleAS Portal is installed.
MID_TIER_ORACLE_HOME
in which OracleAS Portal is installed.
OracleAS Metadata Repository is already installed, and the respective databases are up.
ptlasst.csh -mode LANGUAGE -lang lang_code [-i install_type] [ -s portal_ schema] [-sp portal_schema_password] [-c portal_db_connect_string] [-available]
Table B-5 lists and describes parameters supported for the LANGUAGE mode.
Parameter | Definition |
---|---|
|
This can be set to typical and custom. In the typical mode, the repository access APIs are used to get the details of Oracle Internet Directory, OracleAS Single Sign-On, and the OracleAS Portal schema in the configured OracleAS Metadata Repository. The repository access APIs provide infrastructure access details to the middle-tier component that it needs for its configuration. In the custom mode, the input provided on the command line is used for the configuration.
Default: |
|
Default: |
|
OracleAS Portal schema password. |
|
Connect string to the target database where OracleAS Metadata Repository is installed. The format must be |
|
Abbreviation for the language to install. Refer to Table B-4, " OracleAS Portal Languages" for a list of all the supported abbreviations.
Default: |
|
Sets whether the language will be available for user translation. |
Typical installation (-i typical)
Uses the repository access APIs to get the details of the OracleAS Portal schema in the configured OracleAS Metadata Repository. The following example loads the Dutch language strings into the OracleAS Metadata Repository.
ptlasst.csh -mode LANGUAGE -lang nl -available
Custom installation (-i custom)
This example passes in the input provided on the command line. The example loads the Dutch language strings into the OracleAS Metadata Repository.
ptlasst.csh -mode LANGUAGE -i custom -s portal -sp portal -c myDBhost.domain.com:1521:dbServiceName -lang nl -available
Note:
The character set for |
Installs OracleAS Portal and OracleAS Single Sign-On required SYS schema dependencies as follows:
Note:
-owa
option in the PORTAL, and SSO modes provide the same functionality.
MID_TIER_ORACLE_HOME
on which OracleAS Portal is installed.
ORACLE_HOME
.
ptlasst.csh -mode SYSOBJECTS -c connect_string -p sys_password -voh source_home
Table B-6 lists and describes parameters supported for the SYSOBJECTS mode.
ptlasst.csh -mode SYSOBJECTS -c myDBhost.domain.com:1521:dbServiceName -p change_on_install -voh /private1/repca
Drops the OracleAS Portal schema, as well as the OracleAS Portal Oracle Internet Directory entries.
MID_TIER_ORACLE_HOME
in which OracleAS Portal is installed.
MID_TIER_ORACLE_HOME
in which OracleAS Portal is installed.
ptlasst.csh -mode DEINSTALL -ldap_w orcladmin_password [-i install_type] [ -s portal_schema] [-p portal_schema_password] [-c portal_db_connect_string] [-ldap_h oid_host_name] [-ldap_p oid_port_number] [-ldap_d oid_admin_user]
Table B-7 lists and describes parameters supported for the DEINSTALL mode.
Typical deinstall (-i typical)
Uses the repository access APIs to get the details of Oracle Internet Directory, and the OracleAS Portal schema in the configured OracleAS Metadata Repository.
ptlasst.csh -mode DEINSTALL -ldap_w welcome1
Custom deinstall (-i custom)
This example takes the inputs provided on the command line.
ptlasst.csh -mode DEINSTALL -i custom -s portal -p change_on_install -c myDBhost.domain.com:1521:dbServiceName -ldap_h myOID.domain.com -ldap_p 389 -ldap_w welcome1
|
![]() Copyright © 2002, 2003 Oracle Corporation. All Rights Reserved. |
|