Oracle Portal Configuration Information Oracle Portal Logging and Log Configuration Oracle Portal External Dependencies

Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer 14-7 ■ Oracle Portal repository stores metadata, documents, customizations, and personalizations. ■ Oracle Portal has a strong dependency on Oracle Web Cache to process and cache content. ■ Oracle Portal depends on Oracle HTTP server to route traffic to WebLogic Server, service product images, and rewrite URLs.

14.2.1.3 Oracle Portal Startup and Shutdown of Processes and Lifecycle

Oracle Portal does not have any process of its own. It relies on standard Oracle tools and utilities to manage Oracle Web Cache, Oracle HTTP Server, WebLogic Managed Server WLS_PORTAL, and the database. The following lists the configuration and monitoring interfaces for Oracle Portal components: ■ Enterprise Manager for managing Oracle Web Cache, Oracle HTTP Server, Oracle Portal, and WLS_PORTAL ■ Oracle WebLogic Administration Console for managing WLS_PORTAL ■ Oracle WebLogic Scripting Tool WLST for adding or editing Portal-specific configuration parameters ■ The opmnctl command line interface for managing Oracle Web Cache and Oracle HTTP Server

14.2.1.4 Oracle Portal Deployment Artifacts

The Portal application is deployed as a staged application portal.ear to WebLogic Server WLS_PORTAL. The configuration files are available in DOMAIN_ HOMEserversWLS_PORTALstageportalportalconfiguration

14.2.1.5 Oracle Portal Configuration Information

Some of the Portal configuration is stored in the Portal repository. This information includes site details site host and port, Web Cache details webcache host, invalidation port, and invalidation password, and Oracle Internet Directory details Oracle Internet Directory host and port. Such information can be changed by accessing Enterprise Manager or by using WLST commands for any of the containers. The remaining Portal configuration is available in configuration files that are located inside the staged location of the Portal application. Such configuration files are located in DOMAIN_HOMEconfigfmwconfigserversWLS_ PORTALapplicationsportalconfiguration. In the HA environment, if a configuration file is modified, the same change must be repeated on each WLS_ PORTAL instance either by repeating the action on each node or by copying over the configuration files from one node to another. Table 14–1 Portal Configuration Files Configuration File Description appConfig.xml Portal Page Engine configuration 14-8 Oracle Fusion Middleware High Availability Guide

14.2.1.6 Oracle Portal Logging and Log Configuration

Portal log files are generated in the DOMAIN_HOMEserversWLS_PORTALlogs directory. The log file is named WLS_PORTAL-diagnostic.log. Log rotation ensures that older logs are archived with a similar name. The configuration of log files in Portal is controlled by the logging.xml file, which is located in DOMAIN_ HOME configfmwconfigserversWLS_PORTAL.

14.2.1.6.1 Oracle Portal Log Files The following table lists and describes log files used by

Oracle Portal:

14.2.1.7 Oracle Portal External Dependencies

Oracle Portal requires an Oracle HTTP Server to service requests. Optionally these requests may be cached by Oracle Web Cache, in which case it also acts in the capacity of a load balancer. Oracle Portal requires a database to store information. This database is pre-seeded with schemas using the Oracle Repository Creation Assistant.

14.2.2 Oracle Portal Protection from Failures and Expected Behavior