Dynamic clusters

Install WebSphere Portal. Then, start the Configuration Wizard. Select Set Up a Cluster. Then, run the tasks associated with that option. Choose dynamic as the type of cluster to create.

The OnDemand Router (ODR) component provides workload balancing, prioritization, health monitoring, and dynamic operations for dynamic clusters. An ODR can be configured to provide multi-cluster routing, including dynamic clusters in remote cells, and routing to other servers. The ODR can serve as a replacement for the HTTP server plug-in, but in many configurations both components are used. The HTTP server might be in the DMZ to serve static content and to provide an entry point to the private network where the ODR is.

Considerations:

• Internal users can send requests directly to the ODR instead of through a front-end web server. For direct requests, configure the ODR to append a via header to the HTTP requests. Set ODR custom property...
  http.compliance.via = true

  This step is not required if you send user traffic through the web server to the ODR. The web server appends the via header to the HTTP request.

• The ODR can selectively route traffic to clusters based on the incoming URL. We configure IP alias values for the ODR. Then, define routing rules to associate user traffic for each IP alias to the appropriate WebSphere Portal cluster.

• Use the ODR to load balance traffic among identical portal clusters. We configure a Multicluster Routing Policy (MCRP) for the ODR to identify the destination clusters and the type of load balancing. See: Configuring the on-demand router for multi-cluster failover and load balancing routing

  If we route traffic to remote static clusters with Generic Server Cluster definitions, the cell value must be the local cell name where the ODR is.

• We can also use the ODR to route traffic to remote clusters, both static and dynamic. Define a generic server cluster for each target portal cluster. See: Defining generic server clusters for remote ODR cells.

  If we are routing to remote static clusters that use vertical cluster members, complete the optional step at the end. This step defines a server custom property for each port in the generic server cluster.

When applying maintenance, inactivate the deployment manager until both upgrades are complete. If the deployment manager is active before both upgrades are complete, it might detect an incompatible version and remove some required resources from the dynamic cluster.

Parent Cluster considerations