Roadmap: Multiple clusters
Add a IBM® WebSphere® Portal cluster to an existing cluster.
Read Planning for multiple clusters before you start to create your multiple clusters.
Add a IBM® WebSphere® Portal cluster to an existing cluster.
Read Planning for multiple clusters before you start to create your multiple clusters.
A network load balance directs incoming traffic between the two web servers. Each cluster has a web server. However, a single on-demand router might be used instead.
Gather information and software before you install WebSphere Portal.
You can use existing prerequisite software installations. Verify that your existing version is supported. If it is not, upgrade to the appropriate version. Otherwise, install a web server, database server, and user registry server. Typically the database and user registry servers are already installed and configured. However, there might be specific configuration steps that are required to integrate them with the portal server.
Installing WebSphere Portal involves preparing your operating system, installing or upgrading the installation manager, and running the installation program.
Documentation resource: Installing the digital experience software
Portal maintenance is delivered through two mechanisms: individual fixes (iFixes) and combined cumulative fixes. iFixes are provided, when necessary, for severe or security-related bugs. Combined cumulative fixes are delivered on a regular schedule. They provide a mechanism to deliver fixes faster, improve existing features, deliver new features, update documentation, and provide new documentation on a frequent basis. To deliver continuous improvements for your digital experience software, it is recommended that you apply the latest Combined Cumulative Fix to your environment.
Documentation resource: Roadmap: Applying maintenance
Create your first cluster, including the database transfer, augmenting the Deployment Manager, creating a cluster node, enabling security, and creating additional horizontal cluster nodes. These instructions are for a horizontal cluster only. For information on setting up a vertical cluster, see Setting up a Cluster in the Configuring section of the documentation.
http://hostname.example.com:10039/wps/portal,
where hostname.example.com is the fully qualified
host name of the server where Portal is running and 10039 is
the default transport port that is created by WebSphere Application Server. The port
number might be different for your environment.
Install WebSphere Portal. Then, use the Configuration Wizard to deploy a stand-alone portal.
http://hostname.example.com:10039/wps/portal,
where hostname.example.com is the fully qualified
host name of the server where Portal is running and 10039 is
the default transport port that is created by WebSphere Application Server. The port
number might be different for your environment.
After you create cluster A and portal B, run the various tasks to create the multiple cluster.
Tuning the servers is important to the performance of your portal environment. WebSphere Portal is not tuned for a production environment after installation and deployment. Your database needs tuning for improved performance. You can organize your database now or soon after you finish your configuration. You need to tune and maintain your database on a regular basis.
Configure the remote search service to offload and balance system load.