Home
Stand-alone deployment
With stand-alone deployments, each server is administered independently. For example...
- Server1 has Lotus Connections features with WAS and IBM HTTP Server installed.
- Server2 hosts the database and Tivoli Directory Integrator (TDI)
- Server3 hosts the LDAP server.
You can locate IBM HTTP Server or TDI on their own servers as well. If TDI is configured to perform synchronizations on a near real-time basis, you might need to move the TDI server processes to a separate server to limit potential resource constraints on the database server.
- Install features on one server instance
- In the standard stand-alone deployment, the WAS Console is available on the default server instance (server1).
This configuration limits the number of active users due to memory constraints.
You can, if necessary, convert this base application server deployment to a clustered, network environment.
- Install features on multiple server instances
- In the advanced stand-alone deployment, you can select an existing server instance or create a new server instance for each feature.
It is not recommended to install all components on a single box unless that box is very powerful.
Pilot deployment
Deployment options
Network deployment
Install a stand-alone deployment
Lotus Connections detailed system requirements