WebSphere Portal的cluster搭建日志(一)

写在搭建之前

limations检查列表

You must install and configure WebSphere Portal separately on each node.

Except for the temporary state during the initial setup of the cluster, WebSphere Portal is not supported when running on a managed node that is not part of a clustered environment

Windows: There is a known limitation with many Windows operating systems that limits path names to a maximum length of 259 characters. (short cell name and node name,and shor war name)

Windows and UNIX: Cloudscape, the default database installed with WebSphere Portal, cannot be operated remotely and therefore cannot be used in a cluster environment. When installing WebSphere Portal, you will first install to the default database, then reconfigure WebSphere Portal to point to the common database used for the cluster. Refer to the Configuring databases for more information.(No cloudspace allowed)

In a clustered environment, it is not possible to change portal settings through the Global Settings portlet or the XML configuration interface. These changes must be made by modifying the respective properties in the WebSphere Application Server administrative console, as described in Setting configuration properties.

o support search in a clustered environment, you must install and configure search for remote search service on an application server node that is not part of the cluster. For more information on using search in a cluster, refer to the Portal Search topic.

Administrative actions for WebSphere Portal are immediately visible for the user who performs them. However, another user can be assured of seeing the changes only if the user logs out of WebSphere Portal and then logs back in. This limitation applies to both cluster and non-cluster environments.

If you intend to enable security after creating the cluster by using the enable-security-ldap, enable-security-wmmur-ldap, or enable-security-wmmur-db tasks, you must stop all cluster members before doing so.

When creating a cluster or a cluster member, do not use spaces in the cluster name or the cluster member name.

For the deployment manager and each WebSphere Portal node to be in the cluster, verify that each system clock is set to within 5 minutes of the others or the addNode command will fail.

Guidelines for implementing cluster environments

Windows and UNIX: Selecting a Web server topology diagram and roadmap

Note: Before using the configureweb_server_name script during Web server configuration in a managed cell, change the timeout request period for the Simple Object Access Protocol (SOAP) client on the deployment manager machine. The default, in seconds, is 180. Edit the soap.client.props file in the was_profile_root/properties directory:

Change the line to:

com.ibm.SOAP.requestTimeout=6000

The deployment manager node must be installed separately before the cells and clusters can be 
configured. For more information, refer to 
Installing WebSphere Application Server Network Deployment on the deployment manager machine.

Windows and UNIX: Task overview: Managing HTTP sessions

If you add a node to a cell or change a node's configuration after it has been federated to deployment manager, synchronize the node's configuration. In the administrative console for the deployment manager, select System Administration > Nodes, select the node from the list, and click Full Resynchronize. This helps ensure that there is no mismatch between node and cell configuration after the synchronization is complete.