Cluster considerations

Portal instances in a cluster share the same configuration, including...

• database
• applications
• portlets
• site design

Session and cache data can be replicated and kept consistent across all members of the cluster. The cluster provides an application synchronization mechanism to ensure consistent application management (start, stop, updates, etc.) across the cluster.

The HTTP Server plug-in balances user traffic across all members of the cluster. Session affinity ensures that a user remains bound to a specific cluster instance for the duration of their session. In the event a cluster member is down, the workload management features of the plug-in will recognize that the instance is no longer available and will route traffic around it.

It is possible to deploy multiple portal clusters.

See

1. Guidelines
2. Limitations
3. HTTP session failover
4. Set up an IBM i database in a cluster
5. Security options
6. Security Scenarios
7. Use external security managers in a cluster
8. Multiple clusters
9. WebSphere Virtual Enterprise Dynamic Clusters
10. Cluster maintenance

Troubleshoot

If you get error...

[exec] [wsadmin] WASX7017E: Exception received while running file "/opt/IBM/WebSphere/PortalServer/base/wp.services.impl/config/was/wp_ModifyWebDavFile.jacl"; exception information: com.ibm.bsf.BSFException: error while eval'ing Jacl expression:
[exec] [wsadmin] java.lang.reflect.UndeclaredThrowableException
[exec] [wsadmin] while executing
[exec] [wsadmin] "$Portal login $PortalAdminId $PortalAdminPwd"
[exec] [wsadmin] [09/15/13 16:56:31.211 BST] WASX7093I
[exec]
[exec] BUILD FAILED

You may have an issue with how cluster is configured. See Technote: WebSphere Portal v8 ConfigEngine scripts fail with 'java.lang.reflect.UndeclaredThrowableException'

Parent: Plan
Related:
Clustered servers topology
Set up a cluster
Set up a clustered production environment on z/OS