S2: Scenario environment 

The scenario described in this article is that of a customer deploying Lotus Connections 2.5 at an Enterprise level. In this case, there are clusters on three nodes for each application to support high volumes of users and to provide failover.


The following properties describe the environment in more detail:

• Operating System: Red Hat Linux Enterprise Server Version 4u7 is installed on all machines.
  
• Database Server: Oracle Database Server 10.4 is used as the backend database to Lotus Connections. In this scenario, there are individual database instances for each of the eight databases required for Lotus Connections to run.
  
• User Directory: The LDAP server being used is IBM Tivoli Directory Server 6.1.
  
• Plug-ins supported: All plug-ins are supported in this environment.
  
• Individual Java™ Virtual Machine's (JVM's): There are individual server instances used for each component; therefore, there are 11 separate servers on each node.
  
• Secure Sockets Layer (SSL): SSL is enabled throughout the entire configuration making the Lotus Connections environment secure.
  
• Integration: Lotus Connections is integrated with Lotus Quickr services for WebSphere Portal 8.1.1 and Lotus Sametime 8.0 (which are both assumed to be hosted on systems running Microsoft Windows Server 2003).
  
• Mail Integration: A Domino^® mail server is used to enable notifications on Lotus Connections.

Go to the next topic: S2: Scenario environment S2: Prerequisites   S2: Configuration diagrams S2: Machine details S2: Installing Lotus Connections in an Enterprise level deployment S2: Starting Lotus Connections S2: Configuring an administrative user for Blogs S2: Integrating Lotus Connections with Lotus Quickr for WebSphere Portal S2: Enabling Sametime awareness on Lotus Connections S2: Troubleshooting Table of Contents: Lotus Connections 2.5 Enterprise level deployment scenario