Configuring Transfer Mode for mod_plsql Runtime
The transfer mode of each database access descriptor (DAD) of themod_plsql runtime enables PL/SQL to construct HTML content and process HTML form input in different character sets. You must set the transfer mode with the appropriate value.
It is important to configure the transfer mode for themod_plsql module in the
$ORACLE_HOME/Apache/modplsql/cfg/dads.conf file where the DADs are specified.
Themod_plsql module supports two transfer modes that you can configure in a DAD:
■ CHAR mode: This is a default mode where dynamic HTML content is sent as VARCHAR2 data from the database tomod_plsql. In this mode, theNLS_LANG character set must be the same as that of the backend database character set.
■ RAW mode: Dynamic HTML content is sent asRAW data from the database to mod_plsql and is subject to character set conversion in the database server where the PL/SQL procedures and PSPs run. Character set conversion happens only when the HTML page encoding is specified, either by theNLS_LANG character set or by thecharset parameter specified in theOWA_UTIL.MIME_
HEADER() function call.
You should turn on theRAW transfer mode in a DAD for both monolingual and multilingual Internet applications as follows:
<Location /pls/scott>
SetHandler pls_handler Order deny,allow Allow from all
PlsqlDatabasePassword tiger PlsqlDatabaseUsername scott PlsqlDatabaseConnectString local
PlsqlDocumentPath docs
PlsqlEnableConnectionPooling On
PlsqlNlxLanguage AMERICAN_AMERICA.UTF8
PlsqlTransferMode RAW
</Location>
Configuring Oracle9iAS Portal for Multilingual Support
Oracle9iAS Portal is translated into 29 different languages. This allows developers to work in their own language when they build portals. In addition, the self-service
Configuring Oracle9iAS Portal for Multilingual Support
content management supports multiple languages so that end users can provide documents and other content in different languages. Those who view the content can see the version that corresponds to the language setting in the browser or to the language they have selected in the set language portlet. SeeAppendix A for a list of languages and abbreviations that are available for Oracle9iAS Portal.
To install languages when you install Oracle9iAS Portal, run theptlasst.csh script with-mode LANGUAGE for each language that you want Oracle9iAS Portal to support. Theptlasst.csh script is located in the following directory:
$ORACLE_HOME/ora9ias/assistants/opca dir
Running theptlasst.csh script with-mode LANGUAGE invokes the Oracle Portal Configuration Assistant (OPCA) in the silent mode to install the language.
Usage information on theptlasst.csh script is generated by running the script without any parameters.
Table 3–2 showsptlasst.csh script usage examples for different language requirement scenarios.
Table 3–3 lists the supported parameters for theptlasst.csh script inLANGUAGE mode (-mode LANGUAGE).
Table 3–2 Option Usage with the ptlasst.csh Script
Scenario Usage
Full usage ptlasst.csh -mode LANGUAGE -sportal -sp portal -oorasso -op orasso -c
myhost.domain.com:1521:mySID -lang us -available-silent-verbose-sso_c myhost.domain.com:1521:mySID Portal and SSO are
installed on the same database
ptlasst.csh -mode LANGUAGE -s portal -sp portal -oorasso -op orasso -c
myhost.domain.com:1521:mySID -lang us -available-silent-verbose
Language requirement is only for the Portal Repository
ptlasst.csh -mode LANGUAGE -sportal -sp portal -cmyhost.domain.com:1521:mySID -lang us
-available -silent -mportal -verbose Language requirement is
only for the SSO Repository
ptlasst.csh-mode LANGUAGE -o orasso -op orasso -sso_cmyhost.domain.com:1521:mySID -lang us -available -silent -msso -verbose
Configuring Oracle9iAS Portal for Multilingual Support
The character set for themod_plsql gateway must be the same as the customer database character set.
Table 3–3 Supported Parameters for ptlasst.csh in LANGUAGE Mode
Parameter Definition
-s Portal schema name. The default isportal.
-sp Portal schema password. The default isportal.
-c Connect string to the target database. The format should be hostname:port:sid.
-o SSO schema name. The default isorasso.
-op SSO password. The default isorasso.
-sso_c Connect string to the target database where SSO is installed.
The format should behostname:port:sid.
Note: If the Portal and SSO use the same database, argument -c would take care of both the Portal and SSO connections.
-lang Abbreviation for the language to install. The default isus.
-m Ifsso, translations are only for SSO repository. Ifportal, translations are only for Portal repository. If not specified, translations are installed for both. The default is not specified.
-available Sets whether the language will be available for user translation.
-silent Runs the OPCA in the silent mode. The default isTRUE.
-verbose Enables the logging in detail mode. Even if there are errors in the log file, the OPCA install would continue.
If this parameter is not set, logging information is in brief and OPCA aborts the instal if it encounters any error of kind ORA-, PLS-, or SP2. The default isTRUE.
Note: When you configure bidirectional languages (Arabic and Hebrew), you must also execute the $ORACLE_
HOME/ora9ias/portal30/admin/plsql/nlsres/imginst.
sql script as the Portal schema owner.
See Also: Oracle9iAS Portal Configuration Guide