Home
Install a network deployment
Install Lotus Connections on a network deployment provides better performance and improved availability of features. A Lotus Connections network deployment consists of the following components:
- WebSphere Application Server nodes
- One node with IBM WebSphere Application Server Network dmgr (DM) installed.
- One WebSphere Application Server node on which Lotus Connections has been installed. This node is referred to as the first node in this documentation and serves as a template for subsequent nodes. This node must not be a managed node.
- More WebSphere Application Server nodes that can be federated into the DM cell if required. These nodes are hosts for cluster members. and are referred to as subsequent nodes in this documentation.
- A system with a database server installed
- A system with IBM HTTP Server installed
Important considerations
Before creating a cluster, note the following considerations:
- If you are changing to a network deployment from a stand-alone deployment of Lotus Connections, review the possible configurations of WebSphere Application Server profiles and server processes. See Planning a product installation.
- You cannot use an existing network deployment if the databases that you used in the deployment are not robust enough to support a network deployment. You should upgrade the databases before you run the installation wizard.
- You cannot install Lotus Connections on a managed node.
- Make sure that the clock time on the nodes that you plan to add to a cluster are set to within one minute of each other.
Links
- Install the first node of a cluster
Install the first node of a network deployment of Lotus Connections.- Add subsequent nodes to a cluster
Add more nodes to an existing cluster.- Convert a stand-alone deployment
Convert a stand-alone deployment of Lotus Connections to a node in a network deployment.- Convert data directories manually
If the paths to your Lotus Connections data directories use local directories instead of network shares, convert the paths by updating the WebSphere Variables environment variables on your system.
Related tasks
Install a stand-alone deployment
Running the installation wizard from a console