Planning
* Determine cluster architecture: basic or multi-tier, load balancer or proxy, firewalls.
* Consider network and security topologies.
* Choose machines.
* Identify names and addresses.
– Choose DNS names over IP addresses.
– Choose blank rather than Localhost (choose localhost limits access from localhost only).
* Assign names to WebLogic server resources.
* Identify Admin Server address and port.
* Identify Managed server addresses and listen ports.
* Identify multicast address and port.
– A multicast address is between 224.0.0.0 and 239.255.255.2555
– Defaults to 239.192.0.0
– Do not use multicast address ending with 0.0.1
– Mutlicast address is used to announce services and heartbeats.
– If use firewalls between clusters, each cluster needs its own multicast address.
* Cluster address
– Used in entity and stateless beans to construct the host name portion of request URLs.
– Let WebLogic server dynamically generates the cluster address for each new request.
Cluster Implementation Procedures
* Install WebLogic Server:
– Install same version of WebLogic Server on each machine.
– Each machine:
~ Must have dedicated IP addresses.
~ Must be accessible to clients.
~ Must be located on the same LAN and reachable via IP multicast.
~ Do not use shared file system to run multiple server instance (IO contention).
* Create a clustered domain.
– Use Configuration Wizard
– Use Admin Console
* Start cluster.
* Configure node manager.
* Configure load balancing method for EJBs and RMIs.
– Defaults to round robin.
– Change via Admin Console on cluster’s Configuration > General > Default Load Algorithm tab.
* Specify a timeout value for RMIs.
– You can enable a timeout option when making calls to the ReplicationManager by setting the ReplicationTimeoutEnabled in the ClusterMBean to true.
– The timeout value is equal to the multicast heartbeat timeout.
– ReplicationManager timeout cannot be changed.
* Configure server affinity for distributed JMS destinations.
* If using load balancer, configure load balancer that support passive cookie persistence.
* If using proxy plug-ins, configure proxy plug-ins.
– Setup HttpClusterServlet.
* Configure replication groups.
* Configure migratable targets for pinned services.
* Configure clustered JDBC.
* Package applications for deployment.
* Deploy applications.
– use cluster name as deployment target.
* Deploying, Activating, and Migrating Migratable Services
* Configure In-Memory HTTP Replication
– Set in domain_directory/applications/application_directory/WEB-INF/weblogic.xml file:
<session-descriptor> <persistent-store-type>replicated</persistent-store-type> </session-descriptor>
* Additional Configuration Topics
– Configure IP sockets on server’s Tuning tab.
– If use multicat:
~ Configure Multicast Time-To-Live (TTL) which sets the number of network hops a multicast message makes before the packet can be discarded.
~ Configure Multicast Buffer Size.
~ Configure Multicast Data Encryption.
– Configure Machine Names.
– Configuration Notes for Multi-Tier Architecture.
– Enable URL Rewriting.