Oracle WebCenter Protection from Failover and Expected Behavior Monitoring Logging of Application Deployments Oracle WebCenter Cluster-wide Configuration Changes

6-42 Oracle Fusion Middleware High Availability Guide does not show up if the template cache has been initialized in another JVM, unless JOC distributes the data, or an administrator in the second JVM does an explicit refresh where the cache is rebuilt. Documents Service The Documents service uses Java Object Cache to cache provisioning and configuration checks for document services, as applies to Oracle WebCenter Spaces application configuration. For provisioning, cached objects are flagged as distributed. They are replicated by a correctly configured Java Object Cache in a high availability environment, the configuration cached state is kept locally. All cached objects are flagged to expire after one minute. Caching reduces the number of times UCM calls are made to check the state of the UCM Server, as Oracle WebCenter Spaces repeatedly checks provisioning and configuration to control service rendering in the UI. Portlet Consumer The portlet consumer caches portlet mark-up in the Java Object Cache according to the cache headers in the portlet response. The cache can be expires based or validation based. Profile Management caches the lightweight user profile objects in Java Object Cache. If particular profile data is not found, it will queried from the backend and the cache would be populated. The number of objects stored have an upper bound of 1000 and are in the Java Object Cache for one hour. Navigation caches the Navigation Model objects in the Java Object Cache on a per user session basis. These cached objects are destroyed when the HTTP session is destroyed. Recent Activity The list of recent activity results are cached for each user to prevent a requery of results each time the recent activity task flow or RSS feed is viewed. The cache is automatically refreshed every fifteen minutes, or can be manually refreshed using the refresh icon in the recent activity task flow. For Java Object Cache configuration procedures, see Section 6.4.13, Configuring the Java Object Cache.

6.3.2.7 Oracle WebCenter Protection from Failover and Expected Behavior

An Oracle WebLogic cluster provides application high availability. If one member of the cluster is unavailable, any other available member of the cluster is able to handle the request. Session Failover Requirements For seamless failover of an Oracle WebCenter application, the application must meet the following conditions: ■ The application is in a cluster and at least one member of the application cluster is available to serve the request. ■ For stateful applications, state replication is configured correctly as described in Section 6.4.15, Configuring Oracle WebCenter for Replication. ■ If you are using Oracle HTTP Server, the server configuration is configured with the WebLogicCluster directive to balance among all available application instances. ■ If you are using a hardware load balancer, the load balancer is: Configuring High Availability for Oracle ADF and WebCenter Applications 6-43 – Routing traffic to all available instances – Configured correctly with a health monitor to mark unavailable instances – Configured to support persistence of session state

6.3.2.8 Expected Behavior for Application Failover

If the environment has been configured correctly, application users do not notice when an application instance in a cluster becomes unavailable. The sequence of events in an application failover is, for example, as follows:

1. A user makes a request and is routed by a hardware load balancer to instance A of

the application.

2. Instance A of the application becomes unavailable because of node failure, process

failure, or network failure.

3. The hardware load balancer marks instance A as unavailable.

4. The user makes a subsequent request. The request is routed to instance B.

5. Instance B is configured as a replication partner of Instance A and has the users

session state.

6. The application resumes using the session state on Instance B and the user

continues working without interruption. Exceptions to Expected Behavior For Oracle WebCenter, the known exceptions are as follows: ■ Oracle ADF Pop-ups - Open pop-ups close on failover, affecting the following components which otherwise have no exceptions: – Oracle Composer Property Inspector, EL Builder, Task Flow parameter picker, Resource String Editor – Save confirmation dialog box – Lists – Links link deletion pop-up When failover occurs, you must repeat the action that leads to the pop-up to make it reappear. The specific ways in which this appears in WebCenter Spaces and suggested remedies are listed in Table 6–7 . 6-44 Oracle Fusion Middleware High Availability Guide ■ Component Specific Issues - Other issues which are specific to different components in Oracle WebCenter are listed in Table 6–8 . Table 6–7 Oracle WebCenter Troubleshooting Scenarios Action Before Failover After Failover Suggested Remedy Go to any page and click Create Page . Type in a name, select a theme, and click OK. When you select the theme, the page creation pop-up closes. Repeat the operation. Launch Manage Pages. Perform any operation within the pop-up, except for closing the pop-up, for example, click Page Actions. When you perform any operation, the Manage Pages pop-up is closed. Repeat the operation. Launch Manage Pages, click Page Actions against a page, and then the Delete option in the menu. Click OK on the confirmation pop-up. Clicking OK closes the confirmation pop-up and the Manage Pages pop-up. The result of the deletion which may have gone through is not visible among the tabs. Relaunch the Manage Pages pop-up to see if the page is deleted. If not, try deleting once again. Launch Personalize Applications pop-up. Perform any operation that sends a request, other than clicking OK, for example, expand the Applications node. Perform any operation that sends a request, other than clicking OK, for example, expand the Applications node. When you perform any operation that sends a request to the server, the Personalize Applications pop-up is closed. Repeat the operation Launch Preferences. Switch between the Preferences tabs General, Accounts, Messaging, Search. When you switch between the Preference tabs, the Preferences pop-up is closed. Repeat the operation Launch Manage Favorites. Stop the server, perform any operation other than closing the pop-up. For example, expand a folder, click Edit favorite information . Perform any operation other than closing the pop-up, for example, expand a folder, and click Edit favorite information . When you perform any operation, the Manage Favorites pop-up is closed. Relaunch the Manage Favorites pop-up to see if the operation was successful. If not, retry the operation. Choose to edit applications and create a new folder An MDS exception opens. Retry the operation Work in Oracle Composer Customization Manager. Oracle Composer loses the state associated with the Customization Manager Relaunch Customization Manager. Select a component while in Oracle Composer Source View Oracle Composer loses track of the component. Repeat the operation Configuring High Availability for Oracle ADF and WebCenter Applications 6-45

6.3.2.9 Monitoring Logging of Application Deployments

Use Oracle WebLogic Server Administration Console to check the status of the application deployments. You can also use Oracle WebLogic Server infrastructure and Enterprise Manager Fusion Middleware Control for starting stopping, and monitoring Oracle WebCenter processes.

6.3.2.10 Oracle WebCenter Cluster-wide Configuration Changes

For Oracle WebCenter Spaces and Portlet Producers, all configuration data is stored in the MDS repository and Portlet Producers. Additional cluster deployments automatically read the latest configuration upon application startup. For Oracle Discussion Server, the configuration information should be moved over from an existing cluster server. This is done automatically by the packunpack utility of Oracle WebLogic Server. Oracle recommends this procedure.

6.3.2.11 Maintaining Configuration in a Clustered Environment