S1: Prerequisites 

The following prerequisites must be completed prior to following this deployment scenario article. These prerequisites are as follows:

• Installation and configuration of WebSphere Application Server 6.1 Network Deployment (ND)
  
  WebSphere Application Server 6.1 ND should be installed on the two node machines and on the deployment manager machine. For more information, see the WebSphere Application Server information center at:
  
  http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp
  
  When you install WebSphere Application Server, you will be prompted to enable administrative security, which you must do in order to install Lotus Connections. You must also enable application server security in the WebSphere Application Server Integrated Solutions Console.
  Note: You do not need to enable application server security on the application server nodes as they will become part of the federated cell controlled by the Deployment Manager. However, if you do not enable application server security on node 1, you will get a warning while running the install wizard. You can ignore this warning.
  
  In this scenario WebSphere Application Server must have the following fix packs applied:
  
  - 6.1.0-WS-WAS-WinX32-FP0000023.pak
  - 6.1.0-WS-WASSDK-WinX32-FP0000023.pak
  - 6.1.0.23-WS-WAS-IFPK78743.pak
  
  These fix packs can be downloaded from IBM Fix Central at:
  http://www.ibm.com/support/fixcentral
  
  The three WebSphere Application Server machines discussed in this document are assumed to have the following names:
  
  

Purpose	Host Name
Node 1	node1.example.com
Node 2	node2.example.com
Deployment Manager	dmgr.example.com

• WebSphere Application Server names
  
  The following naming scheme is used for all of the servers and clusters created throughout this installation. These clusters/servers are created during the installation of Connections, but are displayed here to make the reader familiar with the terminology used in this scenario.
  
  
  

Cluster Names	N1 Server Names	N2 Server Names
activitiesCluster blogsCluster communitiesCluster dogearCluster profilesCluster homepageCluster wikisCluster filesCluster mobileCluster searchCluster newsCluster	activitiesServer blogsServer communitiesServer dogearServer profilesServer homepageServer wikisServer filesServer mobileServer searchServer newsServer	activitiesServer_n2 blogsServer_n2 communitiesServer_n2 dogearServer_n2 profilesServer_n2 homepageServer_n2 wikisServer_n2 filesServer_n2 mobileServer_n2 searchServer_n2 newsServer_n2

• IBM HTTP Server (IHS) 6.1.0.23, including plug-ins
  
  IHS must be installed and patched to a fix pack 23 level. The plug-ins for WebSphere Application Server 6.1 should also be installed and patched to the fix pack 23 level. Required fix packs are as follows:
  
  - 6.1.0-WS-IHS-WinX32-FP0000023.pak
  - 6.1.0-WS-PLG-WinX32-FP0000023.pak
  - 6.1.0-WS-WASSDK-LinuxX32-FP0000023.pak
  
  These fix packs can be downloaded from IBM Fix Central:
  http://www.ibm.com/support/fixcentral
  
  IHS should be configured to enable SSL prior to configuring it to be used with Lotus Connections. For more information about IHS, see:
  http://www.ibm.com/software/webservers/httpservers/library/v61.html
  
  The Web server host name is used to access Lotus Connections. Therefore, it is suggested that you give this machine the host name “connections" (for example, “connections.example.com”).Then when Lotus Connections is configured, it can be accessed via connections.example.com/
  
  To enable the IBM HTTP Server for SSL, use the following guide:
  http://publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/topic/com.ibm.connections.25.help/t_configure_ihs.html
  

• Microsoft SQL Server 2005 Enterprise Edition
  
  MS SQL Server should be installed and configured with eight individual instances to host each of the databases for each component. For ease of use the instances should be called after each component – e.g. activities, blogs, communities, etc. These eight instances are used to ensure that each instance has enough resources to properly scale. In a smaller deployment, fewer instances may be used.
  
  
• Microsoft Active Directory Server 2003 SP2
  Active Directory should be up and running with user populated data.
  
  
• IBM Tivoli Directory Integrator 6.1.1 including fixpack 6 should be installed on the same machine as the database server. Download fix pack 6 at:
  http://www-01.ibm.com/support/docview.wss?rs=697&context=SSCQGF&dc=D400&uid=swg24022497
  
  
• Lotus Quickr services for WebSphere Portal 8.1.1 must be installed and configured. For more information, see the Lotus Quickr information center at: http://publib.boulder.ibm.com/infocenter/lqkrhelp/v8r0/index.jsp
  
  
• Lotus Connections Connector for Lotus Quickr should be downloaded from the following location:
  http://www-01.ibm.com/software/brandcatalog/portal/lotusconnections/details?catalog.label=1WP1002AO
  
  
• The Lotus Domino mail server must be installed and ready at this stage. For more information, see the Lotus Domino information center at:
  http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp
  
  

Note: Some of the tasks listed may be the responsibility of an external administrator. Therefore, no action may be required by the deployer of Lotus Connections. For example, LDAP might already be set up and configured for use with other products within a corporation. It is recommended that you consult with the administrator of these systems if you are uncertain.

Go to the next topic: S1: Scenario environment  S1: Prerequisites  S1: Configuration diagrams S1: Machine details S1: Installing Lotus Connections in a network scenario S1: Starting Lotus Connections S1: Integrating Lotus Connections with Lotus Quickr for WebSphere Portal S1: Setting up the Tivoli Access Manager server S1: Troubleshooting Table of Contents: Lotus Connections 2.5 network deployment scenario