S2: 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 three 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 In this scenario WebSphere Application Server must have the following fix packs applied: - 6.1.0-WS-WAS-LinuxX32-FP0000023.pak - 6.1.0-WS-WASSDK-LinuxX32-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 four 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 Node 3 node3.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 Lotus 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 N3 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 activitiesServer_n3 blogsServer_n3 communitiesServer_n3 dogearServer_n3 profilesServer_n3 homepageServer_n3 wikisServer_n3 filesServer_n3 mobileServer_n3 searchServer_n3 newsServer_n3 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-LinuxX32-FP0000023.pak - 6.1.0-WS-PLG-LinuxX32-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 Oracle 10.0.4.0 database 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 named after each component (for example, activities, blogs, communities, and so on). Eight instances are used to ensure each instance has enough resources to properly scale. In a smaller deployment, fewer instances may be used. IBM Tivoli Directory Server should be up and running with user populated data. IBM Tivoli Directory Integrator 6.1.1, including fix pack 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 should be installed and configured prior to following this deployment scenario. For more information, see the Lotus Quickr Information Center at: http://publib.boulder.ibm.com/infocenter/lqkrhelp/v8r0/index.jsp The Domino mail server and Sametime server should also be installed and ready at this stage. For more information, see the relevant information centers at: http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp http://publib.boulder.ibm.com/infocenter/sametime/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, or the Sametime server may already exist. It is recommended that you consult with the administrator of these systems if you are uncertain if any action needs to be taken. 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