2
Post-installation and Configuration Tasks

This chapter provides information about Oracle Portal after installation and the configuration tasks that you can perform.

See: For information about installing Oracle Portal with Oracle9i Application Server, see the "Oracle9i Application Server Installation Guide".

Specific topics covered include:

• Default Schemas Created

• Default Oracle Portal Accounts Created

• Default Groups Created

• Accessing Oracle Portal in your Browser

• Deinstalling Oracle Portal

• Enabling Secure Socket Layer (SSL)

2.1 Default Schemas Created

Oracle Portal is installed primarily in the Oracle8i database, with some supporting components installed on the middle tier in Oracle9i Application Server.

If you install Oracle Portal in the default mode, five schemas are created. The default base schema name is portal30 which you can change at installation time.

Table 2-1 Default Oracle Portal schemas created

Schema	Description
portal30	This is the product schema for Oracle Portal and contains the installed portal database objects.
portal30_public	This is the schema that the portal users map to when executing procedures in the Oracle Portal product schema. The schema name is constructed from the base schema with "_public" appended to it.
portal30_sso	This is the product schema for the Login Server. This schema can be renamed in the installer. If not specified, it defaults to the base schema name with "_sso" appended to it.
portal30_sso_public	This is the schema that the portal users map to when executing procedures in the Login Server product schema. This name is constructed from the Login Server schema name with "_public" appended to it.
portal30_demo	This is a schema which is installed with some Oracle Portal demonstration code. The name of this schema is the base schema name with "_demo" appended to it. See also: Oracle Portal Release 3.0: Building Advanced Portals (A86183-02) Oracle Portal Release 3.0: Tutorial (A86188-02)

Note: The portal30 and the portal30_sso schemas are highly privileged database schemas. For more information, see the "Using the PL/SQL Gateway" guide provided with Oracle9i Application Server.

2.2 Default Oracle Portal Accounts Created

With each Oracle Portal installation, a default set of accounts is created. Assuming that the product is installed in a schema named portal30, the following default accounts are created:

Table 2-2 Default Oracle Portal accounts created

Schema	Description
portal30	This account is created for the Database Administrator (DBA) with the highest privileges in Oracle Portal.
portal30_admin	This is the account created for the portal administrator (ADMIN). This account is similar to the DBA account, however, it does not have privileges that provide access to database administration features, such as creating and managing schemas and other database objects.
portal30_public	This account is created for public users for unauthenticated sessions. This is the account that all sessions are associated with prior to authentication.
portal30_SSO	This account is created for the Login Server application. Since the Login Server is implemented with significant reuse of Oracle Portal infrastructure code, this user account is created as a result of this reuse.
portal30_SSO_public	This account is for non-authenticated sessions by the Login Server application.

Note: Make sure that all the passwords for these accounts are changed after initial login. By default, the password is set to the user name. You can change the password by logging on to the Login Server and editing the appropriate user accounts and changing their passwords.

See also: Task topics in the "Working with Users" folder from the Oracle Portal Online Help content area.

2.3 Default Groups Created

The following groups are created at installation time:

Table 2-3 Default Oracle Portal groups created

Group	Description
DBA	This group is defined with the maximum privilege levels in the system. All global privileges are granted to this group. When this group is installed, it has only one member - the user with the name of the product schema, for example, portal30.
PORTAL_ADMINISTRATORS	This group is also a highly privileged group. It has most of the global privileges, except it does not have the database related privileges ANY_SCHEMA/MANAGE and ANY_SHARED_COMPONENT/MANAGE. This group is seeded with the admin user, portal30_admin, and includes the dba group.
PORTAL_DEVELOPERS	This group has privileges to build and manage Oracle Portal components and applications.
PORTLET_PUBLISHERS	This group has the privilege of publishing portlets. This means that members of this group will be able to create components in the system such as folders, charts, calendars, etc. This group is initially composed of the portal_administrators group who can then decide which users or groups should be added to this group.
AUTHENTICATED_USERS	All users that log on to the Oracle Portal are added to this group. This is a convenient mechanism to allow logged on users to perform privileged actions. Specified privileges are granted to this group and group membership cannot be changed.

See also: Task topics in the "Understanding Users" folder from the Oracle Portal Online Help content area.

2.4 Accessing Oracle Portal in your Browser

After you have successfully installed Oracle Portal, you can access it by entering the following in your browser:

http://<hostname>:<portnumber>/pls/<dad>

Table 2-4 URL to enter in browser to access Oracle Portal

Parameter	Description
hostname	Defines the machine on which you installed Oracle Portal. Important: You must enter both the hostname and the fully-qualified domain name. For example, enter host.domain.com. This name must also match the ServerName parameter in the Apache configuration file, httpd.conf, located in:    <ORACLE_HOME>/Apache/Apache/conf
portnumber	Defines the port number you specified earlier to access Oracle Portal.
pls	Defines the virtual path and indicates that the request is for a PL/SQL procedure which alerts the Oracle HTTP Server powered by Apache to reroute the request appropriately to the PL/SQL Gateway.
dad	Defines the Database Access Descriptor (DAD) you specified earlier for your Oracle Portal installation. The DAD contains information on how to connect to the database. See the Apache Listener Configuration for Oracle Portal DAD window (Oracle HTTP Server powered by Apache).

You will be prompted to enter the Single Sign-On (SS0) username and password before gaining access to Oracle Portal. The defaults are as follows:

Username: portal30

Password: portal30

See also: Section 2.2, "Default Oracle Portal Accounts Created".

2.4.1 Installing language support in Oracle Portal

You can choose to install and display the Oracle Portal user interface in any of the 24 supported languages from your browser. To install support for a given language, you must run the wwvseedus.sql and langinst.csh scripts. Once the language is installed you use the Set Language portlet to choose which language Oracle Portal should use.

The supported languages and their abbreviations are listed in the following table:

Table 2-5 Supported languages and abbreviations

Language	Abbreviation
Czech	cs
German	d
Danish	dk
Spanish	e
Greek	el
French	f
Hungarian	hu
Italian	i
Japanese	ja
Korean	ko
Norwegian	n
Dutch	nl
Polish	pl
Portuguese	pt
Brazilan Portuguese	ptb
Romanian	ro
Russian	ru
Swedish	s
Finnish	sf
Slovak	sk
Thai	th
Turkish	tr
Simplified Chinese	zhs
Traditional Chinese	zht

To install support for a given language in Oracle Portal:

1. Start a command line prompt.

2. Change to the ORACLE_HOME/portal30/admin/plsql/nlsres/ctl/us directory.

3. Start SQL*Plus and login to the database where Oracle Portal is installed.

4. From SQL*Plus, run the wwvseedus.sql script against the PORTAL schema.

5. Change to the ORACLE_HOME/portal30/admin/plsql directory.

6. Enter one of the following commands, depending upon your operating system:

UNIX

langinst.csh <-s portal_schema> <-p portal_password> <-o sso_schema> <-d sso_
password> <-c portal_connect_string> 

-l <language> -available 

Windows NT

langinst.cmd <-s portal_schema> <-p portal_password> <-o sso_schema> <-d sso_
password> <-c portal_connect_string> -l <language> -available 

Example

langinst.csh -s portal30 -p portal30 -o portal30_sso -d portal30_sso -c orcl 

   -l cs -available 

where

Table 2-6 Language script parameters (langinst)

Parameter	Description
-s portal_schema	The database schema for the Oracle Portal database objects. Default = PORTAL30
-p portal_password	The Oracle database password for the Oracle Portal schema. Default = <portal_schema>
-o sso_schema	The Oracle database schema for Login Server objects. Default = <portal_schema>_SSO
-d sso_password	The Oracle database password for Login Server schema. Default = <sso_schema>
-c connect_string	The connect string for the database in which the Oracle Portal schema is installed. You need to provide the connect string only if the schema is located on a remote database.
-l language	The abbreviation for the language you want to install. See Table 2-5, "Supported languages and abbreviations" above.
-available	(Required) Ensures that the tabs are translated.

7. Repeat step 6 for each language for which support is desired in Oracle Portal.

8. To enable users to choose their desired language, you add the Set Language portlet to a portal page. This portlet will display all of the languages currently installed and users can select the language of their choice.

   Typically, it makes sense to add the Set Language portlet to your content area home page, but you could add it to any page. The Set Language portlet can be added to a page just like any other portlet. Refer to the Oracle Portal online help content area for instructions on how to add portlets to pages.

   Notes:

   • In previous releases, Oracle Portal's language support depended upon the setting of your browser's language preference. With the Set Language portlet, this is no longer the case.

   • The Login Server's language is set separately from that of Oracle Portal. The Login Server will automatically display a list of installed languages on its login page, which will determine the language used for the Login Server regardless of what you set in the Set Language portlet.

2.5 Deinstalling Oracle Portal

This section describes how to use Oracle Universal Installer to deinstall Oracle products (which deinstalls them from the Oracle Universal Installer inventory) instead of removing them manually.

To deinstall Oracle Portal:

1. Launch the Oracle Universal Installer.
   • On UNIX, enter ./runInstaller

   • On Windows NT, choose Start > Programs > Oracle Installation Products > Universal Installer.

   The Welcome window for Oracle Universal Installer appears.

2. Click Deinstall Products.

   The Inventory dialog box appears.

3. Expand the tree of installed products until you find the products to deinstall. In this case, choose Oracle Portal.

4. Check the boxes of products to deinstall.

5. Click Remove.

   The Inventory Confirmation window appears.

6. Click Yes to deinstall the selected products.

   Note: A message may display indicating that removing some products may cause other products to function improperly.

The products are deinstalled from your computer. The Inventory dialog box appears without the deinstalled products.

Click Close to close the Inventory dialog box.

Click Exit to exit Oracle Universal Installer.

2.5.1 Deinstalling a single Oracle Portal schema or the Login Server

If you need to delete a single Oracle Portal schema or the Login Server, you can do so from the Oracle Portal Configuration Assistant - Step 1 of 6: Installation Options.

To deinstall an Oracle Portal schema or the Login Server:

1. Launch the Oracle Portal Configuration Assistant:

   Windows NT

   • Choose Start > Programs > Oracle Home > Oracle Portal Configuration Assistant

   UNIX

   • Go to the $OH/assistants/opca directory and run the launch.sh script

2. The Step 1 of 6: Installation Options window appears.

   Click the option to Deinstall Oracle Portal or the Login Server.

3. Follow the instructions on the remaining screens to complete this task.

See also: "Oracle9i Application Server Installation Guide"

2.6 Enabling Secure Socket Layer (SSL)

Notes: You must be the portal administrator to enable or disable Secure Socket Layer (SSL) in Oracle Portal and on the Login Server. See also: "Oracle9i Application Server Installation Guide" for enabling SSL on the server.

Oracle Portal and the Login Server can be configured to run in HTTPS mode if your portal requires increased security. For optimal performance, you can also choose to have a mixed configuration where Oracle Portal is run in HTTP mode and the Login Server is run in HTTPS mode.

The Secure Socket Layer (SSL) is responsible for securing Web HTTP communication between a browser and a Web server in plain HTTP over SSL (named HTTPS). Enabling SSL to work with the Oracle HTTP Server is handled by the mod_ssl package which is provided with the Apache Web server. It uses the URL scheme HTTPS rather than HTTP and a different server port.

2.6.1 SSL in Apache

For more information about enabling and disabling SSL, visit the Apache interface to mod_SSL at the following location:

http://www.modssl.org

2.6.2 SSL in Login Server

In the Login Server, if you need to specify URL prefixes and ports, for example, if you are working with the ssodatan script (which configures your login via the Single Sign-On server) or ssodatax script, or running the Oracle Universal Installer, you would specify https:// and an https port; instead of specifying an http:// and an http port.

When configuring the Login Server for HTTPS, Oracle Portal still requires access to an HTTP port to use UTL_HTTP to connect to the Login Server for some of the communication that it requires. You can specify an available HTTP port from the Global Settings page in the Services portlet.

Figure 2-1 Login Server Settings in Oracle Portal

Text description of the illustration logssl.gif

In the Query Path URL Prefix field, enter the URL prefix which is used to construct the URLs for these internal connections to the Login Server. You must specify an available HTTP port for this URL prefix.

For increased security, refer to the Apache documentation for information on restricting access to the HTTP ports to the portal so that only HTTPS connections from Oracle Portal database's IP address (which is performing a UTL_HTTP callout) is accepted.

See also: "Step 4: Associate nodes with the same Login Server".

2.6.3 Using certificates and HTTPS

With HTTPS, you must use certificates for increased security in Oracle Portal. In this case, the Parallel Servlet must be aware of which port(s) are operating under HTTPS. To set this up, you must edit the zone.properties file which is located in the following location by default:

Table 2-7 zone.properties file location

Operating System	Location
Windows NT	<ORACLE_HOME>\Apache\Jserv\servlets\zone.properties
UNIX	<ORACLE_HOME>/Apache/Jserv/etc/zone.properties

Add the following line to the zone.properties file:

servlet.page.initArgs=httpsports=<port1>:<port2>:. . . :<portn> 

Each port in this list will operate using the HTTPS protocol, and must have a certificate created on the Oracle HTTP Server powered by Apache on that port.

See also: Oracle9i Application Server documentation for further configuration information. "Configuring the Login Server for LDAP user authentication" topic in the Oracle Portal Online Help content area.