S2: Installing Lotus Connections on node 1

Now that all of the preinstallation steps are completed, the installation of Lotus^® Connections can begin. The wizard installs Lotus Connections on the node 1 machine (node1.example.com) and then federates this node into the cluster controlled by the deployment manager (dmgr.example.com). After this process is complete, the second and third nodes are added using the deployment manager. Therefore, the wizard installs Lotus Connections only on one machine – node 1.

Before running the installation wizard, ensure that the following requirements are met:

Ensure that the JDBC driver for Oracle is copied onto each node in the same location (for example, /opt/IBM/JDBC Drivers). You can copy the required driver from the Oracle server, which is typically located in the /opt/oracle/10gR2/jdbc/lib directory. In this instance, the driver is named ojdbc14.jar.
Use a network shared folder to store the search index and the uploaded content store. This location must be accessible from each of the nodes. In this scenario, this location is available at /mnt/LotusConnections/Data on every node.

To launch the installation wizard, follow these steps:

1. Run install.sh from within the Lotus_Connections_Install subdirectory, located in the Lotus Connections installation directory. Select the language to use.

2. The following welcome screen is displayed. Launch the information center here, if required.

3. Accept the license agreement.

4. Select Install Lotus Connections only or select to create a response file for silent installation in the future.

5. Select Network deployment to set up a cluster environment.

6. Select Install first node of a cluster.

7. Choose the default installation directory or click Browse to specify the directory name where you want to install Lotus Connections.

8. Select which features that you want to install. For example, select all check boxes to install all features,

9. Depending on the features selected in the previous panel, you are prompted to select additional features to install. Again, select all check boxes.

The wizard does not detect where WebSphere Application Server is installed.

10. Select the correct location of the WebSphere Application Server installation.

The installation wizard detects the WebSphere Application Server profile path, profiles, and server instances.

11. Select the WebSphere Application Server profile (AppSrv01) and specify the server instance for each feature. Select @nowiki@1create new server> to specify a new server name as shown below. In this example, the servers are named using the following format @nowiki@2component>Server, For example, activitiesServer, blogsServer, communitiesServer, and so on.

12. The installation wizard checks to see if any features are already installed on any of these servers. After this check is complete, the wizard also checks that WebSphere Application Server security is enabled.

Note: At this stage, you are warned by the installer that application security is not enabled on the node on which you are installing Connections. Click OK. You can ignore this message since application security is enabled on the deployment manager, which is the master configuration after the installation is complete.

13. Ensure that the deployment manager is started before performing this step. Next specify the host name, SOAP port (8879 by default), and credentials of the deployment manager. Then select Next for the wizard to attempt to connect to the deployment manager, This ensures that the connection is established.

Note: To verify the SOAP connector port, on the deployment manager machine, open the SystemOut.log file, located in /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/logs/dmgr. Locate the following line to determine the port number "ADMC0013I: The SOAP connector is available at port 8879 ."

14. Specify the names of the clusters. For ease of use, set the cluster names as follows.

15. Specify your administrator user ID for Lotus Connections. This user must be in LDAP and have administrative rights on the deployment manager as discussed in S2: Configuring WebSphere Application Server profiles.

16. The installation wizard detects the host name. Ensure that it is correct.

17. Select the database type, Oracle Enterprise Edition.

18. Select No. In this case, there are eight separate database instances, which each house a single database.

19. You are prompted to provide the location of the Oracle JDBC driver - ojdbc14.jar. Provide the location where this driver was copied prior to installation. In this instance the location is "/opt/IBM/JDBC Drivers",

20. For each feature database (eight), you are prompted individually for the following data:

Database host name and port number
Database name
Application user ID of account used to access database
Application password of account used to access database

S2: Creating the databases

21. Specify the data directories for all features. Because this is a network deployment, this must be a shared location.

23. Select Yes to specify that there is a mail server. Also select the type of mail server (in this case, DNS MX Records).

24. Specify the properties of the Lotus Domino^® mail server.

25. Select a method to use search for people profiles. Select Profiles database.

26. Review the summary and then click Configure to start the installation. If necessary, click Back to go back and amend any settings.

The time it takes to install depends on the performance of your machines. On high specification machines, as in this scenario, this process should take approximately one hour.

27. After installation is completed, the wizard displays the installation result panel. Review this summary to ensure that the features were installed on the WebSphere Application Server node and that clusters were created successfully. You can launch the lcinstalllog.txt for details on the installation. Click Finish to exit this wizard. The first node is now installed and work on the second and third nodes can begin.

28. Before adding additional nodes, it is advised to check the deployment to ensure that everything is currently working. To do this, log on to the deployment manager console, and navigate to Servers > Clusters. Select the check boxes next to all of the clusters, and click Start.

This should take a few minutes. After each cluster is started, you can attempt to log in to one of the Lotus Connections features, such as Activities, using the following URL:

http://node1.example.com:9084/activities

Note that the port number may be different. To verify that you have the correct URL, view the LotusConnections-config.xml file, located at:

/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/dmgrCell01/LotusConnections-config

This file currently contains the hrefs for accessing Lotus Connections directly.

After you can access a page, such as Activities, log in using one of the LDAP users. Verify that each of the services is working by navigating to them. After this test is successful, make sure that you stop each of the clusters and then go to the next topic in this scenario.

Go to the next topic: