Connections 2.5 - Step 5 - INSTALL CONNECTIONS!

Right so we should have all the pre-install steps completed. WASND installed, Dmgr running, server1 profile created (unmanaged node, not running), security setup (using LDAP federated repository in this case), DB2 installed, databases created, TDI installed, Profiles database populated.

So now we can install Lotus Connections 2.5

But before we do...one more thing. Sometimes when you install Connections we can get a SOAP time out error. In order to avoid this error we need to increate the time that the server allows for a SOAP request. We need to modify the com.ibm.SOAP.requestTimeout property in the install_root/properties/soap.client.props file. Just open this file in Wordpad, search for "soap.request", and change the value to 300 or 600 (I did 600 just to be sure). Detailed instructions are here.

So now that we are really ready we need to make sure the Deployment Manager is running and the Application Server instance we will use to install Connections (server1) is not running.

Then we run the install.bat file from the extract of file 1 of 12 from the downloads. The Info Center is pretty good for these steps so just follow the prompts as per this document. You can choose to install all the Features onto the one server however I decided to split the features across 3 servers just to spread the load. The Lotus Connections install will automatically create the additional server profiles for you if you decide to do this as well. I guess it would be wise to try and spread the estimated load across all 3 of the servers however it is really dependent on your usage plans as to how you do this.

The install takes a good while but you should be able to just let it run. Once the install is complete it will provide you with a list of the URL's to each feature. You just need to start each of the servers (as long as the nodeagent is running you can start the servers from the Dmgr Integrated Solutions Console) and off you go! Be Social, Explore, Collaborate!

There are some post install tasks (such as testing the database connections, more security, configuring IBM HTTP server etc) that are listed in the Info Center but you should have a Connections system up and running.