Set up a portal farm
A portal farm refers to a series of identically configured, stand-alone server instances. The number of instances in the farm can be increased or decreased without having to worry about cluster configurations or inter-server awareness.
Portal farms are highly scalable, highly available server environment. Creating the farm requires...
- Content subscriber
- Two or more installed instances of IBM WebSphere Portal
- Web servers for load balancing.
The farm documentation covers only the HTTP server plug-in. However, use any supported web server.
To use managed pages, create a clustered environment. There is a known limitation when we use managed pages in a farm environment.
If we create a farm client with a read-only file system, manually gather logs from the temp directories on the farm members.
99% of Portal environments will want to choose clusters for their architecture. Portal farms are intended to fulfill a specific need. They have limitations associated with them that clusters do not have. One notable limitation - managed pages in a farm is not supported, and generally speaking, customers utilizing IBM Web Content Management (WCM) would not want to choose a farm architecture.
See
TECH-B21 Practical Advice On Deploying Portal as A Farm Choose the type of portal farm to create Set up the HTTP server plug-in on a portal farm Administer a portal farm Maintain a portal farm What about Portal farms?
Parent WebSphere Portal