Sun Java System Portal Server 7.1 Configuration Guide

ProcedureTo Set up Portlet Session Failover on BEA WebLogic 8.1 Service Pack 5

Before You Begin

Two or more portal instances should already be clustered. To cluster Portal Server instances, refer to Clustering in Portal Server 7.1 on BEA WebLogic 8.1 Service Pack 4 and Service Pack 5.

  1. Undeploy the portal.war from the managed servers using the WebLogic administrator console.

  2. Add the following into the weblogic.xml file of portal.war:


    <session-descriptor>
    <session-param>
    <param-name>PersistentStoreType</param-name>
    <param-value>replicated</param-value>
    </session-param>
    </session-descriptor>

    Both portal.war and the portlet which is used for session failover should have the session-descriptor set in the weblogic.xml file.

    After the modification, the content of the weblogic.xml file of portal.war is as follows:


    <!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1 
    //EN" "http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
    <weblogic-web-app>
    <reference-descriptor>
    <resource-description>
    <res-ref-name>jdbc/communitymc</res-ref-name>
    <jndi-name>jdbc/communitymc</jndi-name>
    </resource-description>
    </reference-descriptor>
    <session-descriptor>
    <session-param>
    <param-name>PersistentStoreType</param-name>
    <param-value>replicated</param-value>
    </session-param>
    </session-descriptor>
    <virtual-directory-mapping>
    <local-path>/opt/SUNWam/public_html</local-path>
    <url-pattern>/online_help/*</url-pattern>
    </virtual-directory-mapping>
    </weblogic-web-app>
  3. Deploy the portal.war onto the Portal Server instance using the BEA WebLogic administrator console.

  4. Add the same session-descriptor into the weblogic.xml file of the portlet to be used for session failover.


    Note –

    If the weblogic.xml file does not exist, create it under WEB-INF.


  5. Deploy the portlet through the psconsole and add the portlet to the desktop.

  6. Set session variables in the portlet and bring down the Portal Server instance which it uses to access the desktop.

    The session variables will be retained after you start accessing another Portal Server instance.