Set up a production environment on Linux
In a production environment, you can install and configure IBM WebSphere Portal on a single (primary) node and then add additional nodes in the future as your company's needs grow. You can also deploy a high availability production environment by creating and configuring clustered deployments of multiple servers running WebSphere Portal managed by IBM WAS ND.
To set up your production environment on Linux:
- Prepare prerequisite and corequisite software on Linux
Before creating your high availability production environment, prepare your database, your user registry, your deployment manager, and your remote Web server.- Prepare the Linux operating system
This section includes information for setting up your operating system for IBM WebSphere Portal. Other components might require additional steps; see WebSphere Portal documentation for the specific components you want to install for information.- Prepare the primary node on Linux
Before creating your high availability environment, install IBM WebSphere Portal on your primary node and then configure your database, your user registry, and your network deployment manager.- Choose the type of cluster to create on Linux
If you installed a IBM WAS ND, create a static cluster to handle failover requests. If you installed a IBM WebSphere Extended Deployment, create a dynamic cluster to balance member workloads.- Configure WebSphere Portal to use a user registry on Linux
Configure user registry security on IBM WebSphere Portal to protect your server from unauthorized users. You can configure a stand-alone
LDAP user registry or you can add LDAP user registries and/or database user registries to the default federated repository. After configuring your 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 Linux
After installing and configuring your primary node, you can create your secondary nodes. You must install IBM WebSphere Portal on each node and then configure the node to access the database and user registry before adding it to the cluster.- Set up multiple clusters on Linux
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 IBM 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 carried with the new profile, 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 clustered production environment