Revision as of 07:22, 13 June 2011

Before You Start

You have to configure the following setting for ZK and Weblogic.

zk.xml

Turn on Serializable UI Factory for ZK, please refer to this documentation.

<zk>
	<system-config>
		<ui-factory-class>org.zkoss.zk.ui.http.SerializableUiFactory</ui-factory-class>
	</system-config>
</zk>

weblogic.xml

Add a weblogic.xml under XXX/WEB-INF folder(XXX is like ZKsandbox in the war file)

For example,

<!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>
  <session-descriptor>
    <session-param>
      <param-name>PersistentStoreType</param-name>
      <param-value>replicated</param-value>
    </session-param>
  </session-descriptor>
</weblogic-web-app>

As mentioned in Weblogic's document

replicated — Same as memory, but session data is replicated across the clustered servers.

Setting up Weblogic Clusters

After those things done above, please follow the official document to set up a Weblogic Cluster Server here.

Version History

Version	Date	Content

Last Update : 2011/06/13

@@ Line 11: / Line 11: @@
 </zk>
 </source>
-* Comment out this, if any. (by default, we use <javadoc>org.zkoss.zk.ui.impl .SessionDesktopCacheProvider</javadoc> and it works well)
-<source lang="xml">
-<system-config>
-    <cache-provider-class>org.zkoss.zk.ui.sys.GlobalDesktopCacheProvider</cache-provider-class>
-</system-config>
-</source>
-'''Note:''' we cannot use GlobaDesktopCacheProvider for Cluster because it is stored at ''ServletContext'' scope not ''Session'' scope. In other words, if one server fails, then the cluster will try to replicate the session across different server, so the data we stored in ''ServletContext'' won't transfer to others.
 == weblogic.xml ==

Anonymous

WebLogic Cluster"

Namespaces

More

Page actions