Set up a cluster on Solaris
Prerequisites
- Technotes for installation and configuration issues
To set up your production environment on Solaris:
- Prepare prerequisite and corequisite software on Solaris
Before creating your high availability production environment, prepare your database, the user registry, your deployment manager, and your remote Web server.
- Prepare the Solaris operating system
View information on setting up your operating system for WebSphere Portal. Other components might require additional steps; see the product documentation for the specific components you want to install.
- Prepare the primary node on Solaris
Before creating your high availability environment, install WebSphere Portal on the primary node and then configure your database and your network deployment manager.
- Choose the type of cluster to create on Solaris
If installed a IBM WAS Network Deployment, create a static cluster to handle failover requests. If installed a WebSphere Virtual Enterprise, create a dynamic cluster to balance member workloads.
- Prepare a remote Web server when portal is installed on Solaris
Configure the Web server plug-in, bundled with IBM WAS, to set up your Web server to communicate with WebSphere Portal.
- Configure WebSphere Portal to use a user registry on Solaris in a clustered environment
You can configure a stand-alone LDAP user registry or you can add LDAP and database user registries to the default federated repository. After configuring the user registry, you can add realms for Virtual Portals or a lookaside database to store attributes that cannot be stored in the LDAP user registry.
- Prepare additional nodes on Solaris
After installing and configuring the primary node, you can create your secondary nodes. You must install WebSphere Portal on each node and then configure the node to access the database and user registry before adding it to the cluster.
- Tune your servers
WebSphere Portal is not tuned for a production environment out of the box, so to ensure optimal performance, review and complete the steps in the WebSphere Portal Tuning Guide. Even if a tuning guide is not available for the current release of WebSphere Portal, the tuning guide for the previous product version should be used.
- Configure search in a cluster on Solaris
WebSphere Portal provides two distinct search capabilities. You can utilize both types of search capabilities in a clustered environment.
- Set up multiple clusters on Solaris
The majority of the steps to build another cluster are the same as when building the first cluster in the same cell, with a few exceptions. Basically, the new profile will be designated as the primary profile, using WebSphere Portal clustering terminology, and will then be used as the basis for the new cluster definition.
This duplicates the build process of the first cluster in the cell. During the federation process, if any applications on this new node already exist in the cell (because they are in use by the first cluster), then Deployment Manager will not allow them to be added. After federation, the applications that already exist in the cell are not mapped to the WebSphere_Portal server on the newly federated node, and thus the existing applications must be remapped to this newly federated server to restore its application list. Therefore, depending on the configuration of the new profile, there will likely be some combination of applications shared with the other existing cluster, and some applications unique to this new profile.
Parent topic:
Set up a cluster