Follow the steps in this topic to prepare for your high
availability system installation with WebSphere® Premises Server.
Before you begin
Remember: Setting
up a high availability system requires a WebSphere Premises Server Central
Site Server license.
Procedure
- Install WebSphere Premises Server on
a central server.
Be sure to verify that your installation
is successful, and that your environment is set up for remote Data Capture and Delivery controllers.
See Planning your high availability topology and Installing a remote Data Capture and Delivery controller for more information.
You
can install WebSphere Premises Server with Location Awareness Services for WebSphere Premises Server on
your central server, but the Location Awareness Services for WebSphere Premises Server applications
will not run in a cluster.
- Create a deployment manager profile on your WebSphere Premises Server central
server. For details on how to do this, see Creating a deployment manager profile.
Note: Do
not federate your WebSphere Premises Server into
the network deployment environment.
- On a cluster node server, install the
following prerequisite software:
- WebSphere Application Server 6.1.0.17
- a database client, either DB2® for Linux®, UNIX®, and Windows® or Oracle.
See the WebSphere Premises Server software
requirements for more information.
- a WebSphere MQ 6.0.2.3
client. To install this, copy the contents of the MQ_INSTALL_ROOT\java\lib\ directory
from your central server to same path on your node server. MQ_INSTALL_ROOT is
the installation path for WebSphere MQ.
Important: - All
servers in the high availability system must run the same operating system.
- A high availability WebSphere Premises Server topology
is not supported on SUSE Linux Enterprise
Server V9.3.
- All cluster members must have the prerequisite software
installed in the same path as the central server.
- You cannot have duplicate node names in the same cell. For example,
the central server is called PremisesNode, so none of the cluster
members can have that same node name. If you have two servers with
the same node name, then you will need to drop the WebSphere Application Server profile
and recreate it with a new name to continue with the high availability
topology.
For more detailed information on clustering, see Creating clusters.
- On the cluster node server,
federate the WebSphere Application Server nodes
to WebSphere Application Server Network Deployment (deployment
manager) running on the central server. To do this, run the addNode command:
addNode WASND_host WASND_SOAP_port
Tip: Make sure the deployment manager has been started on the
central server before trying to federate the nodes.
- Optional: Delete servers from WebSphere Application Server Network Deployment.
- Open the WebSphere Application Server Network Deployment administrative
console.
- Navigate to . You
will see all servers from each cluster node.
- Select all servers and delete them.
- Save the master configuration.
- If you have WebSphere Application Server security
enabled, disable it. The installer cannot run properly
with security enabled.
- Restart the deployment manager, all node agents, and all
servers.