| Oracle Portal Configuration Guide
Part Number A87566-01
The Oracle Portal architecture supports a wide variety of topologies and configuration options. Factors that determine how to configure Oracle Portal depend on the intended purpose, its local network environment, the anticipated load, how it will be accessed by users, and the like.
The basic Oracle Portal configurations covered in this chapter include:
The standalone laptop configuration is very appropriate if you require a very compact and portable installation. For example, you would use this setup if you are demonstrating Oracle Portal without a network connection or if you change your hostname frequently.
In this configuration, the browser, Oracle9i Application Server middle-tier, and Oracle8i database containing the Login Server and Oracle Portal objects, all reside on a single laptop. To set this up, follow these steps:
The HOSTS file is created when you install TCP/IP to include remote host names and their IP addresses for each computer with which you will communicate. Specify only a valid DNS name for your host. If you are unfamiliar with editing your host file, consult your network administrator for assistance.
httpd.conf, specifies the
ServerNameentry as local host. For example, replace <hostname> with localhost as follows:
ssodatanscript as follows:
<ORACLE_HOME>/portal30/admin/plsql/directory where Oracle Portal is installed.
ssodatan -w http://localhost/pls/portal/ -l http://localhost/pls/portal_sso/ -s portal30 -p portal30 -o portal30_sso -c orcl
For parameter descriptions, see "Configuring a New Oracle Portal Instance and Login Server with the ssodatan Script".
In this example, the ORACLE_HOME environment variable is set to the Oracle9i Application Server's home and the connect string `orcl' points to the database containing Oracle Portal and the Login Server schema. The default Oracle Portal schema is assumed to be "portal30" and the Login Server schema is assumed to be "portal30_sso".
For parameter descriptions, see Table B-3, "ssodatan script parameters".
While a standalone laptop configuration is only accessible to the person using the laptop, the integrated server configuration allows any authorized user to access the Oracle Portal installation remotely across a LAN with a browser.
httpd.conf, verify that the ServerName entry is specified with the full domain name of the server containing your Oracle Portal installation. For example:
If the Oracle9i Application Server middle-tier, which includes the Oracle HTTP Server and the Servlet Engine, is installed on a separate machine from Oracle Portal, the traditional three-tier architecture is used. For more information, refer to the "Oracle9i Application Server Overview Guide" in the documentation library.
This architecture is set up the same way as the integrated server configuration with the following exceptions:
The Oracle9i Application Server middle-tier is installed on a separate machine.
This configuration can be used if you want to have multiple Partner Applications accessing a centralized Login Server to leverage Single Sign-On. In this case, Oracle Portal and the Login Server reside on separate database instances.
Since this configuration uses distinct instances for the Login Server and Oracle Portal, a slightly different installation sequence is required. Running the Oracle Universal Installer for Oracle9i Application Server on the middle-tier installs the application server and loads up all the source files and scripts enabling more complex topologies such as this to be configured.
The following is one of several ways to set up this configuration:
For the connect string, specify the hostname that points to the Oracle Portal host.
Upon installation, the middle-tier software such as the PL/SQL Gateway reside in the Oracle9i Application Server host in the following Oracle Home location:
where <ORACLE_HOME> is the location of the Oracle9i Application Server.
<ORACLE_HOME>/network/admin/tnsnames.orafile on the Oracle9i Application Server.
linstallscript located in <
ORACLE_HOME>/portal30/admin/plsqlto install a standalone Login Server on the Login Server host, by specifying the connect string to the Login Server database instance.
The success URL should be similar to:
ssodataxscript on Oracle Portal.
<ORACLE_HOME>/portal30/admin/plsqllocation, run the
ssodatax <-w portal_url> <-l login_server_url> <-s portal_schema> <-p portal_password> <-o sso_schema> <-d sso_password> <-e pstore_schema> <-c portal_connect_string>
Specify the site id, site token, and encryption key obtained in step 4 above. For the other parameters, enter as follows:
ssodatax -i 1234 -t A1B2C3 -k X9Y8Z7 -w http://server.oracle.com:3000/pls/portal30/ -l http://server.oracle.com:3000/pls/portal30_sso/ -s portal30 -v v1.0 -o portal30_sso -c orcl
For parameter descriptions, see "Updating an Existing Portal Instance with the ssodatax Script".
For the connect string (-c parameter), enter the TNS entry for the Oracle Portal database connection.
ssodatax is run, it only updates information in the specified database connection. Furthermore, it does not clear any information that may be in the enabler configuration table unless the host or port specified in the URL prefix for the -w parameter matches one that is already in the table. In this case, the newly-provided information replaces the previous values.
This chapter discussed basic Oracle Portal configurations. For topologies with several database providers or multiple content areas, each residing on a separate Oracle Portal node, consider a distributed Oracle Portal configuration to aggregate these into a single Oracle Portal instance which is covered in Chapter 4, "Distributed Oracle Portal Installations".