Home

 

Install the first node of a cluster


Overview

These are instructions for installing the the first node of a network deployment of Lotus Connections.

The Lotus Connections installation wizard supports the creation of new server instances.

The installation wizard automatically detects the name of the node where you are installing Lotus Connections and updates the corresponding attribute in the wkplc.properties file.

(AIX only). If you are downloading the wizard, the TAR program available by default with AIX does not handle path lengths longer than 100 characters. To overcome this restriction, use the GNU file archiving program instead. This program is an open source package that IBM distributes through the AIX Toolbox for Linux Applications at the IBM AIX Toolbox Web site. Download and install the GNU-compatible TAR package. You do not need to install the RPM Package Manager because it is provided with AIX.

After you have installed the GNU-compatible TAR program, change to the directory where you downloaded the Lotus Connections TAR file, and enter the following command to extract the files from it:

gtar -xvf <Lotus_Connections_wizard>_aix.tar

This command creates a named after the wizard.

If you experience a SOAP time-out error during installation, go to this SocketTimeoutException support page and follow the instructions to resolve the potential causes of the error. Alternatively, you can disable the time out by setting the value of the parameter...

You can use the native SQL Server JDBC driver in either the app_server_root/lib directory or the driver from Microsoft. The wizard checks the connection for the Microsoft JDBC driver only. If you are using the native driver, you need to manually test the connection after installation. For more information, see the Testing a database connection topic.

A network deployment supports load balancing and failover, and is synchronized by a WAS dmgr. Run the installation wizard on the system that you plan to use as the first node in the cluster.


Install Lotus Connections on the first node of a cluster in a network deployment

  1. Install prerequisite software, including WAS Network Deployment.

  2. Complete prerequisite tasks.

  3. Check the Release notes for late-breaking issues.

  4. Start WAS Network Deployment manager.

  5. If the WAS instance on which you plan to install Lotus Connections is running, stop it.

  6. To avoid synchronization errors, ensure system clocks on the dmgr system and each clustered node are set to within one minute of each other.

  7. Launch the installation wizard...

    Lotus_Connections_Setup/install.sh

  8. On the Welcome panel, click Launch Information Center

  9. Review and accept the license agreement

  10. On the Response file panel, select one of the options.

    Option Description
    Install Lotus Connections only Install the product without saving a response file.
    Create response file only Create a response file but without installing the product. Select this option if you need to modify the current response file for use in another installation.

    Always use the installation wizard to modify the response file. Manual modifications might cause a new installation to fail.

    Install Lotus Connections and create a response file Install the product and save a response file.

  11. On the Deployment options panel, select the Network deployment option and click Next.

  12. Select the type of cluster member that you want to create.

    Option Description
    Install the first node Create the first node of a Lotus Connections cluster
    Convert stand-alone deployment to network deployment Convert an existing stand-alone installation of Lotus Connections to become the first node of a cluster

  13. Select the directory where you want to install Lotus Connections: you can accept the default directory, enter a new name, or click Browse to select an existing

  14. Select the features that you want to install and click Next.

    Option Description
    Activities Collaborate with colleagues
    Blogs Write personal perspectives about projects
    Communities Discuss projects in the user forums
    Dogear Bookmark important Web sites

    In Lotus Connections 2.5, the Dogear feature in the user interface is renamed as Bookmarks.

    Files Share files among users
    Profiles Find people in the organization
    Wikis Create content for your Web site

  15. Select the extended features that you want to install and click Next. You can select from the following options:

    Option Description
    Home page Access all features from a central point
    Mobile Access Lotus Connections from mobile devices
    Search Search Lotus Connections data
    News repository Stay informed about updates

    The Home page and Mobile features rely on the features that you selected in the previous step. The Search and News features provide services to the features that you selected in the previous step.

  16. Select the WAS installation that will host Lotus Connections and click Next. For example:

      /IBM/WebSphere/AppServer

    After you identify the location of the WAS instance, the installer checks to make sure that security is enabled on that server.

    If the location of the server to use is not displayed, click Cancel to exit the installation wizard, and restart as follows...

    cd Lotus_Connections_Install
    ./install.sh -W inputWasLocation.propertyValue=true

    You are directed to a page where you can manually specify the location of the WAS. Enter the location.

    For Windows, if you made the poor design decision to install into C:\Program Files, you'll have to enter...

      C:\Progra~1\IBM\WebSphere\AppServer

  17. Enter values for the WAS profile and server instance:

    1. Select a WAS profile.

    2. Select an existing server instance from the Server instance list or create a server instance by selecting Create new server (a new panel appears where you can enter the name of the new server instance).

    3. Click Next.

  18. Enter the properties of the WAS dmgr and then click Next:

      Host name

      Name or IP address of the host DM server

      SOAP port

      The SOAP port number

      Administrative ID

      The Administrative ID of the DM

      Password

      The password for the Administrative ID of the DM

    The installation wizard checks the size of the Java™ Virtual Machine (JVM) heap on the dmgr and displays a warning if it is less than 512 MB. If the heap size is less than 512 MB, you are likely to encounter an out-of-memory error. To increase the heap size, go to this Troubleshooting Web page and follow the instructions for your platform.

    After you have increased the heap size of the JVM, stop and restart the dmgr. When that is complete, click OK to continue the installation.

  19. Enter the names of the clusters that you want to create: for each installed feature, select a server instance name; for each selected server instance, enter a cluster name.

    Each server instance is added as the first member of its cluster. For improved performance and administration, add each server instance to its own cluster.

  20. Enter the User ID and Password of the default administrative user for Lotus Connections.

    You must have already created this user ID in your LDAP or in WebSphere Identity Manager. The ID is mapped to an authentication alias called connectionsAdmin. The installed features use this authentication alias for internal administrative roles, including the search-admin, dsx-admin, and widget-admin roles.

    If you plan to use a third-party Single Sign-On solution such as Tivoli Access Manager or SiteMinder, this user ID must exist in your LDAP

    To change the connectionsAdmin alias to use a different user ID, follow the relevant procedures in the Managing stored credentials topic. You also need to update the SIBus references to the user ID. For more information, see the Updating the messaging bus configuration when the connectionsAdmin user ID changes topic.

  21. Enter the host name of the WAS installation and click Next. The wizard retrieves HTTP port values for WAS.

    Use the fully-qualified DNS name or short DNS name for the host server. Do not use the IP address of the host.

  22. Select a database type from one of the following options:

    • DB2 Universal Database
    • Oracle Enterprise Edition
    • SQL Server 2005Enterprise Edition

  23. Specify whether the databases for the features are located on the same server: Select Yes or No and then click Next.

    The substeps that follow provide detailed information about each of these options.

    The installation wizard tests your database connection with the database values that you supplied. You can change the database configuration later in the WAS admin console.

    Option Description
    Yes, the database same server. To enter the database information, complete the following substeps:

    1. Enter the fully-qualified domain name of the database server. For example: appserver.enterprise.example.com.

    2. Enter the port number of the database service. The default values are: 50000 for DB2, 1521 for Oracle, and 1433 for SQL Server.

    3. Enter the location of the JDBC driver library. For example:

        /usr/ibm/WebSphere/AppServer/lib

      Ensure that the following JDBC driver libraries are present in the JDBC directory:

        DB2

        db2jcc.jar and db2jcc_license_cu.jar

        Oracle

        ojdbc14.jar

        SQL Server

        Download the SQL Server 2005 JDBC 1.2 driver from the Microsoft Web site to the WAS lib and enter that name in the JDBC driver library field.

    4. Click Next.

    5. For each feature, enter the Application user password. You specified this password when you created the databases for the features.
    No, different database servers Enter the following database information:

    1. Enter the path to the JDBC driver library.

    2. For each feature, enter the following information:

      1. Enter the Host name of the database server. For example: appserver.enterprise.example.com.

      2. Enter the Port number of the database server. The default values are: 50000 for DB2, 1521 for Oracle, and 1433 for SQL Server.

      3. Enter the database name.

      4. Enter the Application user ID of the account to use toconnect to the database.

      5. Enter the Application user password. You specified this password when you created the databases for the features.

    If your database type is Oracle, connect to the database with the user ID that you used when you created the feature databases.

  24. Set up data directories for the features, using one of the following methods:

    • Specify a data directory for Lotus Connections, using the Universal Naming Convention (UNC) format. The wizard creates a parent with sub-directories for each feature.

    • Specify a data directory for each feature.

    The data directories must reside in a shared repository that allows read-write access to all the nodes. Use one of the following methods:

    • Network-based file shares (for example, UNC, Samba, and so on)

    • Storage area network drives (SAN)

  25. If you selected the option to specify a data directory for each feature, for each feature that you are installing, enter the required information. Enter the file path to a network share using the Universal Naming Convention (UNC) format...

      //server_name/<share_name>

    Specify the same on each node where the feature is installed. Do not specify a path that contains drive letters, such as...

      //server_name/C$/data/


    Data directories for features

    Feature Directory (samples only) Description
    Activities statistics files AIX or Linux:

    //server_name/<share_name>/usr/IBM/LotusConnections/Data/activities/statistic

    Windows

    \\server_name\<share_name>\LotusConnections\Data\activities\statistic

    		Statistics files that store statistics generated by Activities. The file format is CSV
    Activities content files

    • AIX or Linux:

      • //server_name/<share_name>/usr/IBM/LotusConnections/Data/activities/content

    • Windows:

      • \\server_name\<share_name>\LotusConnections\Data\activities\content

    		Content to store files uploaded to Activities by users. This is additional storage space outside the database and stores files such as images.
    Blogs upload files

    • AIX or Linux:

      • //server_name/<share_name>/usr/IBM/LotusConnections/Data/blogs/upload

    • Windows:

      • \\server_name\<share_name>\LotusConnections\Data\blogs\upload

    		File upload for adding files such as images to Blogs.

    These files can become very large. Ensure that the has enough disk space

    Communities statistics files (See Note) Statistics files for Communities.

    The Communities statistics directories are not used in release 2.5. Accept the default location provided by the installation wizard and click Next.

    Communities discussion forum content

    • AIX or Linux:

      • //server_name/<share_name>/usr/IBM/LotusConnections/Data/communties/content

    • Windows:

      • \\server_name\<share_name>\LotusConnections\Data\communties\content

    		Content store for the discussion forums, storing additional content such as images and presentations
    Dogear favicon files

    • AIX or Linux:

      • //server_name/<share_name>/usr/IBM/LotusConnections/Data/dogear/favorite

    • Windows:

      • \\server_name\<share_name>\LotusConnections\Data\dogear\favorite

    		Favicon files directory, used for the favicons (favorite icons) that are generated by Dogear users
    Files

    • AIX or Linux:

      • //server_name/<share_name>/usr/IBM/LotusConnections/Data/files/contentstore

    • Windows:

      • \\server_name\<share_name>\LotusConnections\Data\files\contentstore

    		Files content
    Profiles statistics files

    • AIX or Linux:

      • //server_name/<share_name>/usr/IBM/LotusConnections/Data/profiles/statistic

    • Windows:

      • \\server_name\<share_name>\LotusConnections\Data\profiles\statistic

    		Statistics files, used for storing statistics generated by Profiles. The file format is CSV
    Profiles cache

    • AIX or Linux:

      • //server_name/<share_name>/usr/IBM/LotusConnections/Data/profiles/cache

    • Windows:

      • \\server_name\<share_name>\LotusConnections\Data\profiles\cache

    		Cached files
    Search dictionary

    • AIX or Linux:

      • //server_name/<share_name>/usr/IBM/LotusConnections/Data/search/dictionary

    • Windows:

      • \\server_name\<share_name> \LotusConnections\Data\search\dictionary

    		Search dictionary files
    Search index

    • AIX or Linux:

      • //server_name/<share_name>/usr/IBM/LotusConnections/Data/search/index

    • Windows:

      • \\server_name\<share_name>\LotusConnections\Data\search\index

    		Search index files
    Wikis

    • AIX or Linux:

      • //server_name/<share_name>/usr/IBM/LotusConnections/Data/wikis/contentstore

    • Windows:

      • \\server_name\<share_name>\LotusConnections\Data\wikis\contentstore

    		Wikis content

  26. Decide whether you want to enable e-mail notification. If you click No, the installer skips the next step, and you can configure notification later.

  27. If you decided to enable e-mail notification, you can select one of the following notification options:

    Option Description
    WebSphere Java mail session Use a single mail server for all notifications. Choose this option if you can access an SMTP server directly using the host name.
    DNS MX records Use a DNS server to find an available SMTP messaging server. Choose this option if you need to use a DNS server to access the SMTP server.

    The choice you make in this step determines which of the following two steps you need to complete.

  28. If you selected the Java notification option, specify the properties of the SMTP server and then click Next:

    Fill out the following fields to identify the mail server to use for sending e-mail:

    • Host name of the SMTP messaging server. Enter the host name or IP address of the preferred SMTP mail server if you have a specific SMTP messaging server.

    • Fill out the following fields, if required, to identify the mail server to use for sending e-mail:

      • User ID and Password – Enter these values if the SMTP server requires authentication.

      • Enable SSL – Enable SSL if you wish to encrypt outgoing mail to the SMTP server."

      • Port – Accept the default port of 25, or enter port 465 if you are using SSL.

  29. If you selected DNS MX records as the notification solution, enter the following information and then click Next:

    • Messaging domain name. Enter the name or IP address of the messaging domain.

    • DNS server for the messaging servers. Enter the host name or IP address of the DNS server.

    • DNS port that is used for sending queries over the messaging server.

    • User ID. If SMTP authentication is required, enter the administrator user ID for the SMTP server.

    • Password. If SMTP authentication is required, enter the password for the administrator user of the SMTP server.

    • Encrypt outgoing mail traffic to the SMTP messaging server using SSL. Select the check box to use the SSL when connecting to the SMTP server.

    • Port. Specify the port number to use for the SMTP server connection. The default port number for the SMTP protocol is 25. The default port number for SMTP over SSL is 465.

  30. (Only required if you installed the Profiles feature.) Select a to use when searching for users. You can choose the Profiles database or your LDAP

    If you select the Profiles database, ensure that you have followed the steps in the Populating the Profiles database topic. By selecting this option, you are also enabling the Profiles service extension. This service extension allows other Lotus Connections features to access Profiles data. For more information, please see the Common services topic.

  31. Review the information that you have entered. To revise your selections, click Back. To finalize the installation, click Next.

  32. Review the result of the installation. Click Finish to exit the installation wizard

 

Results

The installation wizard has installed Lotus Connections on the first node of a cluster in a network deployment.

You can always identify the first node because its LC_ROOT contains a version Subsequent nodes do not have a version under the LC_ROOT The lcinstalllog.txt log file that is stored in a temporary is overwritten by subsequent installations. If you plan to install additional features on the same system and want to be able to refer to the log file generated by the installer, change the file name or copy the lcinstalllog.txt file from the following directory:

...into this directory:

These examples assume that you installed Lotus Connections in the default directories. If you selected different installation directories, change the file paths accordingly.

If you installed WAS on Microsoft Windows and configured it to run as a service, change the Log On attribute of the service to ensure that you can access network shares. For more information, see the Accessing network shares topic.

If you are using the bundled SQL Server driver, test the database connection. For more information, see the Testing the SQL Server database connection topic.

 

Related tasks

Install a network deployment
Define IBM HTTP Server for a node
Install the first node
Install a subsequent node
Install a stand-alone deployment
The InstallResponse.txt file

+

Search Tips   |   Advanced Search