Oracle9iAS Personalization Administrator's Guide Release 2(v9.0.2) Part Number A95243-03 |
|
This chapter describes issues associated with OP security and internationalization.
Oracle9iAS Personalization follows the Oracle Data Server security policy. OP implements the following measures:
The DBA is responsible for creating database users and setting up proper privileges for them so that they can access OP.
OP controls user access by providing two database roles:
http://<hostname>/OP/Admin/ReportsPage
).
By default, the MOR schema owner (the user named MOR) is the OP administrator, and thus has the full privileges to access the OP product.
For new OP users, the DBA can grant either full privileges (OP_ADMIN) or more limited privileges (OP_REPORT, access only to the OP reports) as follows:
SQL> grant OP_ADMIN to <new_user>;
SQL> grant OP_REPORT to <new_user>;
For existing database users, the DBA must grant one of the two roles to allow the user access to OP product at the appropriate level.
Oracle9iAS Personalization is designed to support many languages and character sets. In addition, the OP UI, the online help for the UI, and all OP messages are translated by Oracle into several European and Asian languages.
When OP is installed, no default value is specified for NLS_LANGUAGE, an MOR configuration parameter. By default, OP uses the same character set as the database character set (for databases of native character sets).
You can specify a value in NLS_LANGUAGE. OP verifies that the value specified is supported and then uses it instead of the database default language for the server code. If neither this value nor the database default indicates one of the supported languages, OP defaults to AMERICAN. This value also specifies the language used for email notification.
Supported languages and their character sets are as follows:
|
Copyright © 2001, 2002 Oracle Corporation. All Rights Reserved. |
|