Configure a shared file system for a portal farm
Mount the shared file system before installing the first farm member. Tune the file system. Slow access to the files impacts performance. All farm members access the file system concurrently.
GPFS configuration is supported on AIX, Linux, and Windows
WAS, portal, and the portal profile form a set of files that need to be consistent. Place all of these parts into the same shared file system. Typically...
- AIX: /usr/IBM/WebSphere
- Linux: /opt/IBM/WebSphere
- IBM i: /QIBM/IBM/WebSphere
- Windows: C:\IBM\WebSphere
Create an empty file system on a central file server with enough capacity for a full installation. Then, mount it on the Farm Master as a writeable file system in the location where we would install WebSphere Portal. The mount point on the Farm Master is fixed after WebSphere Portal is installed. All other Farm members and workers need to use the same mount point.
If we are using GPFS as the shared file system:
- Install and configure the file system on each of the farm clients and farm master servers.
- On the farm master server, create the following two file systems with a minimum of 40 gigabytes of space that have read/write access:
- Mount /dev/gpfs1nsd on /apps
- Mount /dev/gpfs3nsd on /profiles
- Verify the file system inodes limit is set to 250000 or higher:
- mmchfs /dev/gpfs1nsd -F 250000
- mmchfs /dev/gpfs3nsd -F 250000