Oracle Web Cache and Oracle HTTP Server Process Failures Common Component Node Failures Common Component WebLogic Managed Server Failures

14-4 Oracle Fusion Middleware High Availability Guide ■ Oracle Single Sign-On is Oracles Enterprise authentication mechanism. Oracle Single Sign-On is integrated into Oracle HTTP Server for each of the product components. When a request which requires authentication comes in to the Oracle HTTP Server, it determines whether the user has been authenticated through the Oracle Single Sign-On server. If the user has been authenticated, the request is processed. If however, the user has not been authenticated, the Oracle Single Sign-On server is contacted to gain authorization.

14.1.2 Common Log Files

The following table lists, describes, and provides the location for generic log files used by Oracle Portal, Forms, Reports, and Discoverer:

14.1.3 Common Component Failures and Expected Behaviors

This section describes high availability concepts that apply to Oracle Portal, Forms, Reports, and Discoverer.

14.1.3.1 Oracle Web Cache and Oracle HTTP Server Process Failures

Oracle HTTP Server, Oracle Web Cache, and Oracle Discoverer preference server processes are protected by the Oracle Process Manager and Notification system OPMN. If one of these processes fails, OPMN automatically restarts the process. Oracle WebLogic Managed Servers are started and monitored by Oracle Node Manager. If an Oracle WebLogic Managed Server fails, Oracle Node Manager restarts the process.

14.1.3.2 Common Component Node Failures

If a node that is not fronted by Oracle Web Cache fails, the Load balancer automatically reroutes requests to a surviving node. If Oracle Web Cache fails, the Load Balancer automatically reroutes requests to a surviving web cache node. If a node with Oracle HTTP Server fronted by Oracle Web Cache fails, Oracle Web Cache reroutes the request to a surviving Oracle HTTP Server. File Location Description access_log ORACLE_ INSTANCEdiagnosticslogsO HSohs1 Lists each access to the Oracle HTTP Server and the HTTP Return code ohs1.log ORACLE_ INSTANCEdiagnosticslogsO HSohs1 HTTP Server error log access_log ORACLE_ INSTANCEdiagnosticslogsWe bCacheweb1 Lists each access to Oracle WebCache and the HTTP Return code access_log DOMAIN_HOMEserversWLS_ PORTALlogs Lists access requests being received by the WebLogic Managed Server opmn.log ORACLE_ INSTANCEdiagnosticslogsOP MN OPMN log files Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer 14-5 If Oracle WebLogic Server fails, Oracle HTTP Server reroutes requests to another WebLogic cluster member. Oracle Portal, Forms, Reports and Discoverer requests being processed by the failed node must be restarted.

14.1.3.3 Common Component WebLogic Managed Server Failures

In a high availability configuration, Oracle WebLogic Managed Servers are clustered together. If one of the managed servers fails, mod_wl_ohs automatically redirects requests to one of the surviving cluster members. If the application stores state, state replication is enabled within the cluster, which allows redirected requests access to the same state information.

14.1.3.4 Common Component Database Failures