Install Portal on the Farm Master and start farm workers
The first server where IBM WebSphere Portal is installed is the basis for the portal farm and is termed the Farm Master.
- Install WebSphere Portal into the mounted file system.
A set of product binary files and a default configuration profile (wp_profile) exist. The binary files are the PortalServer, AppServer, and other directories. Ensure that all installable files go into the shared file system. The installation needs a single-server installation and no cluster.
- Reconfigure the portal instance to use a different TCP/IP host name.
This host name must either be localhost or a host name configured in the local hosts file alias localhost. This placement allows the local instance to always reference itself using the loopback address.
cd WP_PROFILE/bin
./wsadmin.sh -c "\$AdminTask changeHostName {-nodeName node -hostName localhost}; \$AdminConfig save" -conntype NONE
### Propagate the profile changes to the WebSphere Portal configuration
cd WP_PROFILE/ConfigEngine
./ConfigEngine.sh localize-clone -DWasPassword=foo
- Configure this instance to represent the baseline configuration for the entire farm, including configuring databases, and configuring the user registry.
- Enable the server to run in farm mode.
mkdir /var/log/was_tmp
./ConfigEngine.sh enable-farm-mode -DsystemTemp=/var/log/was_tmp -DWasPassword=foo
The systemTemp parameter specifies where directories and files the running portal instance writes to, such as for logging and page-compiling:
- Each server added to the farm is called a Farm Worker.
On each Farm Worker, mount the network accessible file system in the same location as on the Farm Master. This step preserves the installation path configuration.
- From the farm client, to start/stop an instance of WebSphere Portal...
cd WP_PROFILE/PortalServer/bin
./start_WebSphere_Portal.sh
./stop_WebSphere_Portal.sh
- Set up the HTTP server plug-in.