B Using the OracleAS Portal Configuration Assistant Command Line Utility

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:

The OracleAS Metadata Repository installation option of the Oracle Application Server Infrastructure installation type includes a database with an OracleAS Portal schema. The OracleAS Portal schema can also be installed in an existing database through the Oracle Application Server Repository Creation Assistant (OracleAS RepCA).

See Also:
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.
The Oracle Application Server (middle-tier) installation type performs the required configuration for the middle-tier components, so they can use the OracleAS Metadata Repository.

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:

B.1 Using ptlasst

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:

On Windows NT/2000:

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}

On UNIX:

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}

Usage Notes:

Mode names, like for example, MIDTIER, or LANGUAGE, must be passed to 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.
The file ptlasst.README, located in the directory ORACLE_HOME/assistants/opca contains the usage information for ptlasst, also listed in this appendix.
To obtain schema password information, needed to run some of the 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:

Example B-1 Obtaining the PORTAL Schema Password

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.

B.2 ptlasst Modes

The following table contains a description of the different modes:

Table B-1 ptlasst Modes

Mode	Description
PORTAL	Installs the OracleAS Portal schema in the target database. You must run this mode from the Oracle Application Server Repository Creation Assistant CD.
MIDTIER	Configures the OracleAS Portal middle-tier to use an existing or newly installed OracleAS Portal schema.
LANGUAGE	Installs the strings for a specific language in the OracleAS Metadata Repository.
SYSOBJECTS	Installs the SYS schema dependencies, required for OracleAS Portal and OracleAS Single Sign-On. This mode only needs to be run once for every database.
DEINSTALL	Drops the OracleAS Portal schema, as well as the OracleAS Portal Oracle Internet Directory entries.

Usage Note:

This appendix uses the following conventions:

[] indicates an optional parameter

{option1 | option2} indicates a choice between option 1, or option 2 can be made.

B.2.1 PORTAL

Action

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.

Environment

OracleAS Portal sources for the repository installation are available only on the Oracle Application Server Repository Creation Assistant (RepCA) CD.
The PORTAL mode can only be run from the OracleAS RepCA CD, and not from the MID_TIER_ORACLE_HOME in which OracleAS Portal is installed.

Set the ORACLE_HOME environment variable to the Database Oracle home.

Note:

The prerequisites for running the OracleAS Metadata Repository installation, using the ptlasst script are:

PL/SQL LDAP packages must be installed in the database.
JVM option of the database must be configured.
Intermedia option of the database must be configured.
DB block size is at least 8 KB.
Shared pool size must be at least 100 MB.
Java pool size must be at least 64 MB.

It is recommended to install the OracleAS Metadata Repository through the OracleAS RepCA tool, because the prerequisites are automatically checked during the installation.

Usage

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.

Table B-2 List of Supported Parameters for the PORTAL Mode

Parameter	Description
`-s`	Portal schema name (in the OracleAS Metadata Repository). Default: `portal`
`-c`	Connect string to the target database. The format should be `DbHostName:DbPortNumber:DbServiceName`.
`-p`	SYS password for the target database.
`-u`	User tablespace. The user tablespace selected should have at least 75 MB of free available space and should have autoextend on. Default: `users`
`-t`	Temporary tablespace. The temporary tablespace selected should have at least 20 MB of free available space and should have autoextend on. Default: `temp`
`-d`	Document tablespace. The document tablespace selected should have at least 4 MB of free available space and should have autoextend on. Default: Tablespace selected for the User tablespace
`-l`	Logging tablespace. The Logging tablespace selected should have at least 4 MB of free available space and should have autoextend on. DEFAULT: Tablespace selected for the User tablespace.
`-in`	Index tablespace. The Index tablespace selected should have at least 20 MB of free available space and should have autoextend on. Default: Tablespace selected for the User tablespace.
`-demo`	Installs the portlet builder demo components.
`-voh`	Oracle home location of the OracleAS Portal sources (OracleAS RepCA Home).
`-oh`	Oracle home of the database.
`-log`	Log directory location. This directory should have write permissions.
`-owa`	This parameter installs the PL/SQL Web Toolkit and other SYS schema packages. This is installed just once in the database.

Usage Example

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

Note:

Starting with the Oracle Application Server release 10g (9.0.4), the OracleAS Portal sources required for the repository installation will be available on the Oracle Application Server Repository Creation Assistant (RepCA) CD. The PORTAL OPCA mode can only be run directly from the OracleAS RepCA CD.

B.2.2 MIDTIER

Action

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:

OID Type - Configures OracleAS Portal to work with Oracle Internet Directory. This type is used if configuration changes are required in OracleAS Portal due to changes in the Oracle Internet Directory component. For example, changes in the Oracle Internet Directory host, port, or protocol.
SSO Type - Configures OracleAS Portal to work with OracleAS Single Sign-On. This type is used if configuration changes are required in OracleAS Portal due to changes in the OracleAS Portal published host, port, or protocol, as registered with Oracle Application Server Single Sign-On. Typically, the published host, port, and protocol, are that of OracleAS Web Cache, except in the case of a configuration where a load balancing router, or reverse proxy server is front-ending OracleAS Web Cache, or when using virtual hosts.
WEBCACHE Type - Configures OracleAS Portal to work with Oracle Application Server Web Cache. This type is used if configuration changes are required in OracleAS Portal due to changes in the OracleAS Web Cache component. For example, changes in the OracleAS Web Cache hostname, listening port, invalidation port, invalidation password, or administration port.
OHS Type - The OHS type is a superset of the SSO and WEBCACHE types. It configures OracleAS Portal to work with the Oracle HTTP Server, and to use the provider user interface and the provider group. This type is used if configuration changes are required in OracleAS Portal due to changes in the Oracle HTTP Server component. For example, changes in the HTTP server host, port, or protocol.
ALL Type - Configures all of middle-tier components to work with the OracleAS Portal schema. The ALL type is a superset of the OID, SSO, WEBCACHE, and OHS types. This type is typically used to configure the OracleAS Portal middle-tier to use a new OracleAS Metadata Repository.
DIPREG Type - Creates the provisioning profiles in Oracle Internet Directory.

DIPUNREG Type - Deletes the provisioning profiles in Oracle Internet Directory.

Note:

If possible, use the Portal Dependency Settings file and tool to perform middle-tier configuration. If you use 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.

After you update the iasconfig.xml, you must run the Portal Dependency Settings tool (ptlconfig) to update the OracleAS Metadata Repository with the configuration settings in iasconfig.xml.

Shown subsequently is a mapping of various ptlasst MIDTIER types and their Portal Dependency Settings tool (ptlconfig) counterparts:

Instead of the WEBCACHE type, you can use ptlconfig -dad <dad> -wc.
Instead of the OID type, you can use ptlconfig -dad <dad> -oid.
Instead of the OHS type, you can use ptlconfig -dad <dad> -site.

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

Environment

Set the ORACLE_HOME environment variable to the MID_TIER_ORACLE_HOME in which OracleAS Portal is installed.
The MIDTIER mode should be run from MID_TIER_ORACLE_HOME in which OracleAS Portal is installed.

Assumptions

OracleAS Portal and OracleAS Single Sign-On server are already installed.
Oracle Internet Directory, OracleAS Web Cache, and Oracle HTTP Server are up and running.

Note:
The MIDTIER mode is also used to synchronize or resynchronize OracleAS Portal users and groups with Oracle Internet Directory.

Usage

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.

Table B-3 List of Supported Parameters for the MIDTIER Mode

Parameter	Description
`-i`	Installation type. 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: `typical`
`-type`	Middle-tier type. The available options are ALL, OID, SSO, WEBCACHE, DIPREG, and DIPUNREG. Default: `ALL`
`-s`	OracleAS Portal schema name. Default: `portal`
`-sp`	OracleAS Portal schema password.
`-c`	Connect string to the target OracleAS Portal database. The format should `DbHostName:DbPortNumber:DbServiceName`.
`-sdad`	OracleAS Portal schema (in the OracleAS Metadata Repository) DAD name. Default: `portal`
`-o`	OracleAS Single Sign-On schema name. Default: `orasso`
`-op`	OracleAS Single Sign-On password. Default: `orasso`
`-odad`	OracleAS Single Sign-On DAD name. Default: `orasso`
`-host`	HTTP server hostname used for OracleAS Portal.
`-port`	HTTP server port number used for OracleAS Portal.
`-chost`	OracleAS Web Cache host. Default: HTTP Server hostname.
`-cport_i`	OracleAS Web Cache invalidation port.
`-cport_a`	OracleAS Web Cache administration port.
`-wc`	OracleAS Web Cache ON/OFF flag to enable or disable Web Cache within OracleAS Portal. Default: `ON` If set to `OFF`, OracleAS Portal would not use Web Cache though OracleAS Web Cache may be up and running.
`-ldap_h`	Hostname of the Oracle Internet Directory server.
`-ldap_p`	Port number of the Oracle Internet Directory server.
`-ldap_d`	Administration DN. Default: `cn=orcladmin`
`-ldap_w`	Password for DN.
`-pwd`	Initial password for OracleAS Portal seeded users (PORTAL and PORTAL_ADMIN) in Oracle Internet Directory.
`-sso_c`	Connect string for the OracleAS Single Sign-On database. The format should be `DbHostName:DbPortNumber:DbServiceName`.
`-ps`	Password Store schema name. Default: `orasso_ps`
`-pp`	Password Store schema password.
`-pa`	Partner application schema name. Default: `orasso_pa`
`-pap`	Partner application password.
`-wc_i_pwd`	OracleAS Web Cache invalidator password. Default: Password of the Oracle Application Server instance (ias_admin password).
`-ldaps`	Flag to indicate that Oracle Internet Directory is SSL enabled.
`-ultrasearch`	Configure Oracle Ultra Search.
`-syndication`	Configure Syndication server and UDDI.
`-ssl`	Flag to indicate that OracleAS Portal needs to be SSL enabled.
`-emport`	Oracle Enterprise Manager Application Server Control port.
`-iasname`	Oracle Application Server instance name.

B.2.2.1 OID Type

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]

Usage example

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

Usage example

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

Note:

If you are unsure whether to use Typical or Custom, use the Custom installation type.

B.2.2.2 SSO Type

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.

Note:

OracleAS Single Sign-On and OracleAS Portal from different versions cannot interoperate.

Due to the interdependency of the OracleAS Single Sign-On and OracleAS Portal with Oracle Internet Directory in Oracle Application Server 10g (9.0.4), you must not configure OracleAS Portal 10g (9.0.4) to use an OracleAS Single Sign-On Server (Login Server) from Oracle9iAS Release 1 (1.0.2.2) or earlier. Similarly, you must not configure Release 1-based versions of OracleAS Portal to use the current release of OracleAS Single Sign-On. The exception to this rule is that Portal version 3.0.9.8.4 and later can be configured to use a 9.0.x SSO server.

See Also:

The Upgrades page on Portal Center, http://portalcenter.oracle.com/upgrades/.
Oracle Application Server 10g Migrating from Oracle Application Server

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.

Usage example

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

Usage example

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

Note:

If you are unsure whether to use Typical or Custom, use the Custom installation type.

B.2.2.3 WEBCACHE Type

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]

Usage example

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

Usage example

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

Note:

If you are unsure of the Typical/Custom categorization, use the Custom installation type.

B.2.2.4 OHS Type

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]

Usage example

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

Usage example

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

Note:

If you are unsure whether to use Typical or Custom, use the Custom installation type.

B.2.2.5 ALL Type

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]

Note:

The -ultrasearch and -syndication options can only be used with the typical install option (-i typical).

Usage example

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

Usage example

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

Note:

If you are unsure whether to use Typical or Custom, use the Custom installation type.

B.2.2.6 DIPREG Type

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]

Usage example

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

Usage example

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

Notes:

If you are unsure whether to use Typical or Custom, use the Custom installation type.
The DIPREG install type can also be used to create the provisioning profile for a 9.0.2 repository.

B.2.2.7 DIPUNREG Type

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]

Usage example

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

Usage example

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

Note:

If you are unsure whether to use Typical or Custom, use the Custom installation type.

B.2.3 LANGUAGE

Action

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.

Table B-4 OracleAS Portal Languages

Language	Language Abbreviation
Arabic	ar (ARABIC_UNITED ARAB EMIRATES.AR8MSWIN1256)
Czech	cs (CZECH_CZECH REPUBLIC.EE8MSWIN1250)
German	d (GERMAN_GERMANY.WE8MSWIN1252)
Danish	dk (DANISH_DENMARK.WE8MSWIN1252)
Spanish	e (SPANISH_SPAIN.WE8MSWIN1252)
Greek	el (GREEK_GREECE.EL8MSWIN1253)
Latin American Spanish	esa (SPANISH_SPAIN.WE8MSWIN1252)
French	f (FRENCH_FRANCE.WE8MSWIN1252)
Canadian French	frc (FRENCH_FRANCE.WE8MSWIN1252)
Hebrew	iw (HEBREW_ISRAEL.IW8MSWIN1255)
Hungarian	hu (HUNGARIAN_HUNGARY.EE8MSWIN1250)
Italian	i (ITALIAN_ITALY.WE8MSWIN1252)
Japanese	ja (JAPANESE_JAPAN.JA16SJIS)
Korean	ko (KOREAN_KOREA.KO16KSC5601)
Norwegian	n (NORWEGIAN_NORWAY.WE8MSWIN1252)
Dutch	nl (DUTCH_THE NETHERLANDS.WE8MSWIN1252)
Polish	pl (POLISH_POLAND.EE8MSWIN1250)
Portuguese	pt (PORTUGUESE_PORTUGAL.WE8MSWIN1252)
Brazilian Portuguese	ptb (BRAZILIAN PORTUGUESE_BRAZIL.WE8MSWIN1252)
Romanian	ro (ROMANIAN_ROMANIA.EE8MSWIN1250)
Russian	ru (RUSSIAN_CIS.CL8MSWIN1251)
Swedish	s (SWEDISH_SWEDEN.WE8MSWIN1252)
Finnish	sf (FINNISH_FINLAND.WE8MSWIN1252)
Slovak	sk (SLOVAK_SLOVAKIA.EE8MSWIN1250)
Turkish	tr (TURKISH_TURKEY.TR8MSWIN1254)
Thai	th (THAI_THAILAND.TH8TISASCII)
Simplified Chinese	zhs (SIMPLIFIED CHINESE_CHINA.ZHS16GBK)
Traditional Chinese	zht (TRADITIONAL CHINESE_TAIWAN.ZHT16BIG5)

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.

Caution:

During login operations, information is sent to OracleAS Single Sign-On. The language used in the authentication request is sent back to OracleAS Portal. OracleAS Single Sign-On must have all languages installed that exist on the OracleAS Portal, so that the selected language is recognized. If OracleAS Single Sign-On does not have the selected language installed, it will default to US English. This is the language that would be asserted to any OracleAS Portal that requested authentication in a language that is not available on the OracleAS Single Sign-On server.

The Set Language portlet in OracleAS Portal sets a language and a Persistent Language cookie on the OracleAS Single Sign-On server and OracleAS Portal.

If there are multiple portals configured to use the same OracleAS Single Sign-On, and the portals have different languages installed, all the combined languages must exist on the OracleAS Single Sign-On to accommodate a Set Language request from any of the portals.

Environment

Set the ORACLE_HOME environment variable to the MID_TIER_ORACLE_HOME in which OracleAS Portal is installed.
The LANGUAGE mode must be run from the MID_TIER_ORACLE_HOME in which OracleAS Portal is installed.

Assumptions

OracleAS Metadata Repository is already installed, and the respective databases are up.

Usage

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.

Table B-5 List of Supported Parameters for the LANGUAGE Mode

Parameter	Definition
`-i`	Installation type. 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: `typical`
`-s`	OracleAS Portal schema name. Default: `portal`
`-sp`	OracleAS Portal schema password.
`-c`	Connect string to the target database where OracleAS Metadata Repository is installed. The format must be `DbHostName:DbPortNumber:DbServiceName`.
`-lang`	Abbreviation for the language to install. Refer to Table B-4, " OracleAS Portal Languages" for a list of all the supported abbreviations. Default: `f`
`-available`	Sets whether the language will be available for user translation.

Usage example

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

Usage example

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 mod_plsql must be the same as the customer database character set. Refer to the Oracle Application Server 10g mod_plsql User's Guide for more information.

B.2.4 SYSOBJECTS

Action

Installs OracleAS Portal and OracleAS Single Sign-On required SYS schema dependencies as follows:

Installs PL/SQL Web Toolkit (OWA) packages

Installs VPD Context packages

Note:

This mode has to be run only once for every database.
The -owa option in the PORTAL, and SSO modes provide the same functionality.
For information on obtaining the OWA package version, refer to the Frequently Asked Questions section of the Oracle Application Server 10g mod_plsql User's Guide.

Environment

Sources for the SYSOBJECTS mode are only available in the OracleAS RepCA CD.
The SYSOBJECTS mode can only be run from the OracleAS RepCA CD. This mode cannot be run from the MID_TIER_ORACLE_HOME on which OracleAS Portal is installed.
Set the ORACLE_HOME environment variable to the Database ORACLE_HOME.

Usage

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.

Table B-6 List of Supported Parameters for the SYSOBJECTS Mode

Parameter	Description
`-c`	Connect string to the target database. The format should be `DbHostName:DbPortNumber:DbServiceName`.
`-p`	SYS schema password for the target database.
`-voh`	Oracle home location of the sources (OracleAS RepCA Home).

Usage example

ptlasst.csh -mode SYSOBJECTS -c myDBhost.domain.com:1521:dbServiceName -p 
change_on_install -voh /private1/repca

B.2.5 DEINSTALL

Action

Drops the OracleAS Portal schema, as well as the OracleAS Portal Oracle Internet Directory entries.

Environment

The ORACLE_HOME environment variable is set to the MID_TIER_ORACLE_HOME in which OracleAS Portal is installed.
DEINSTALL mode should be run from the MID_TIER_ORACLE_HOME in which OracleAS Portal is installed.
OracleAS Metadata Repository already exists and the respective databases are up.
Oracle Internet Directory is up and running.

Usage

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.

Table B-7 List of Supported Parameters for the DEINSTALL Mode

Parameter	Description
`-i`	Installation type. 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: `typical`.
`-s`	OracleAS Portal schema name. Default: `portal`
`-c`	Connect string to the target database. The format should be `DbHostName:DbPortNumber:DbServiceName`.
`-p`	SYS schema password of the target database.
`-ldap_h`	Hostname of the Oracle Internet Directory server.
`-ldap_p`	Port number of the Oracle Internet Directory server.
`-ldap_w`	Password of the Administration DN.

Usage example

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

Usage example

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