Install IBM Connections 3.0.1 for migration 

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

  2. Complete pre-installation tasks.

    If you are migrating from IBM Lotus Connections 2.5, complete only the following tasks:

    Do not complete the Pre-installation tasks for creating databases or populating the Profiles database. The migration process handles those tasks separately.

  3. Install WAS Network Deployment (Application Server option) on each node.

    IBM Connections will be installed on the system where IBM WAS dmgr is installed.

  4. Configure WAS Network Deployment to communicate with the LDAP directory.

  5. Ensure that the system clocks on the dmgr system and on the nodes in a cluster are set to within one minute of each other.

    If these system clocks are further than one minute apart, you might experience synchronization errors.

  6. IBM Installation Manager presents three options for the type of deployment that you can install.

  7. The IBM Connections installation process supports the creation of new server instances and clusters. Do not use existing clusters to deploy IBM Connections.

  8. If you have already installed IBM Rational Installation Manager, update it to V1.3.3 or higher.

  9. (AIX only) If you are downloading IBM Installation Manager, 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 website. 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 IBM 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 directory named after IBM Installation Manager.

      (Linux only) Ensure that the GTK library is available on your system.

      If you are installing on a 64-bit system, you also need the 32-bit version of the GTK library.

  10. (Microsoft Windows) You must use an administrator account to install IBM Connections on Windows. If you are installing on Windows Server 2008, use a local administrator account. The installation could fail if you use a domain administrator account.

  11. You can install on the AIX and Linux operating systems with root or non-root accounts.

  12. (AIX and Linux) Ensure that any directory paths that you enter contain no spaces.

  13. Copy the JDBC files for your database type from the dmgr to each node.

    Place the copied files in the same location as their location on the dmgr. If, for example, you copied the db2jcc.jar file from the C:\IBM\SQLLIB directory on the dmgr, place the copy in the C:\IBM\SQLLIB directory on each node. See the following table to determine which files to copy:

      Table 1. JDBC files
      Database type JDBC files
      DB2 db2jcc.jar
      db2jcc_license_cu.jar
      Oracle ojdbc6.jar
      SQL Server sqljdbc4.jar

  14. Start WAS Network dmgr.

  15. Copy the installation files to the system hosting the dmgr.

  16. From the Lotus_Connections set-up directory, run the file to start the IBM Connections launchpad:

    • AIX or Linux: <Lotus_Connections set-up>/launchpad.sh

    • Windows:<Lotus_Connections set-up>\launchpad.exe

    The launchpad needs a web browser to run. If your system does not have a web browser, take one of the following actions:

    • Install a web browser.

    • Install IBM Connections in silent mode. For more information, see the Install in silent mode topic.

    • Start IBM Installation Manager manually:

      1. Open a command prompt.

      2. Change to the Lotus_Connections_install/IM/<OS> directory, where <OS> is your operating system.

      3. Enter ./install.sh -input response.xml.

  17. In the left pane of the launchpad, click Install IBM Connections 3.0.1 and then click Launch the IBM Connections 3.0.1 install wizard in the right pane.

  18. In IBM Installation Manager, select the packages that you want to install and then click Next to continue.

    If you have previously installed IBM Installation Manager, the option to select that package is disabled.

  19. Accept the default settings for Show all versions and Check for Other Versions and Extensions.

  20. Review and accept the license agreement by clicking I accept the terms in these license agreements. Click Next.

  21. Specify the location of the installation directory for IBM Installation Manager. This page appears only if you have not installed IBM Installation Manager before. Select the option to Use the existing package group or Create a new package group and then enter the location of the Installation Directory. Click Next.

    The Shared Resources directory stores resources that can be shared by multiple packages. If you used IBM Installation Manager before, this value is automatically entered.

  22. The installation directory stores resources that are unique to the packages that you are installing.

  23. Specify the location of the installation directory for IBM Connections. Select the option to Use the existing package group or Create a new package group and then enter the location of the Installation Directory. You can accept the default directory location, enter a new directory name, or click Browse to select an existing directory. Click Next.

  24. Select the applications that you want to install and click Next. Select from the following options:

    Option Description
    All applications Install all IBM Connections applications.
    Activities Collaborate with colleagues.
    Blogs Write personal perspectives about projects.
    Communities Interact with people on shared projects.
    Bookmarks Bookmark important web sites.
    Files Share files among users.
    Forums Discuss projects and exchange information.
    Home page View the latest updates in IBM Connections.
    Mobile Access IBM Connections from mobile devices.
    Moderation Forum and community owners can moderate the content of forums.
    Profiles Find people in the organization.
    Wikis Create content for your web site.

      The product always installs the Home page, News, and Search applications.

  25. Enter the details of your WAS environment:

    1. Select the WAS installation that contains the dmgr.

        After you identify the location of the WAS instance, IBM Installation Manager checks that security is enabled on that server.

        Note the default path to the WAS installation:

        • AIX: /usr/IBM/WebSphere/AppServer

        • Linux: /opt/IBM/WebSphere/AppServer

        • Windows: C:\IBM\WebSphere\AppServer

    2. Enter the properties of the WAS dmgr:

        dmgr

          Name of the dmgr to use for IBM Connections

        Host name

          Name of the host dmgr server

        dmgr Admin

          The administrative ID of the dmgr

          Note: This ID is set to the connectionsAdmin J2C authentication alias, which is mapped to the following J2EE roles: dsx-admin, widget-admin, and search-admin. It is also used to by the service integration bus. If you plan to use security management software such as Tivoli Access Manager or SiteMinder, the ID that you specify here must exist in the LDAP directory so that it can be recognized by that software. For more information, see the Switching to unique administrator IDs for system level communication topic.

        dmgr Password

          The password for the administrative ID of the dmgr

        dmgr port

          The SOAP port number of the dmgr

        Click Validate to verify the dmgr information entered. If the verification fails, IBM Installation Manager displays an error message. When the verification test is successful, click Next.

  26. Configure your topology:

    1. Select a topology solution.

    2. Enter the application cluster name for each application.

        Note: IBM Installation Manager creates servers and clusters when required.

    3. Accept the predefined node selection or select a different node.

        Note: These nodes host application server instances that host IBM Connections applications. You can assign multiple nodes to a cluster, where each node is a server member of that cluster.

    4. Enter the server member name for the selected node. Choose the default or enter a custom name.

        Note: If you enter a custom server member name, the name must be unique across all nodes in your deployment.

  27. Enter the database information:

    1. Specify whether the installed applications use the same database server or instance: Select Yes or No.

        Note: If allowed by your database configuration, you can select multiple database instances as well as different database servers.

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

      • IBM DB2 Universal Database™

      • Oracle Enterprise Edition

      • Microsoft SQL Server Enterprise Edition

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

      • AIX:

          /usr/IBM/WebSphere/AppServer/lib

      • Linux:

          /opt/IBM/WebSphere/AppServer/lib

      • Windows:

          C:\IBM\WebSphere\Appserver\lib

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

        DB2

          db2jcc.jar and db2jcc_license_cu.jar

        Oracle

          ojdbc6.jar

        SQL Server

          Download the SQL Server JDBC 2 driver from the Microsoft website to a local directory and enter that directory name in the JDBC driver library field.

          The directory must not contain the sqljdbc.jar file, only the sqljdbc4.jar file. Even though the datasource is configured to use the sqljdbc4.jar file, an exception occurs if both files are present in the same directory.

          IBM recommends that you obtain this Microsoft hotfix for the JDBC 2 driver for production deployments.

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

        If your installed applications use different database servers, enter the database host name for each application.

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

        If your installed applications use different database servers or instances, enter the database port for each application.

    7. Enter the database user ID and password for each application.

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

    8. Click Validate to verify your database settings. If the validation fails, check your database settings. When the validation succeeds, click Next.

        IBM Installation Manager tests your database connection with the database values that you supplied. You can change the database configuration later in the WAS admin console.

  28. Specify the locations of the content stores. Shared content must be read/write accessible by all nodes in a cluster. Both shared and local content stores must be accessible using the same path from all nodes and the dmgr. Local content is node-specific. Each content store is represented by a corresponding WebSphere variable that is further defined as shared or local.

    1. Enter the location of the Shared content store.

        The shared content store usually resides in a shared repository that grants read-write access to the dmgr and all the nodes. Use one of the following methods to create a shared data directory:

        • Network-based file shares (for example: NFS, SMB/Samba, and so on)

        • Storage area network drives (SAN)

        • If you are using a shared-file system on Microsoft Windows, specify the file location using the Universal Naming Convention (UNC) format. For example: \\server_name\share_name.

    2. Enter the location of the Local content store.

      (Windows only) If you use Remote Desktop Connection to map shared folder drives, ensure that the same session is used to start node agents. Otherwise, the shared drives might be invisible to the nodes.

  29. Select a notification solution and then click Next.

    • WebSphere Java™ Mail Session: Use a single mail server for all notifications. Select this option if you can access an SMTP server directly using the host name.

        Complete the following fields to identify the mail server to use for sending email:

        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.

        This SMTP server requires authentication

          Select the check box to force authentication when notification mail is sent from this server.

        User ID

          If the SMTP server requires authentication, enter the user ID.

        Password

          Enter the user password if the SMTP server requires authentication.

        Encrypt outgoing mail traffic to the SMTP messaging server using SSL

          Select this check box if you want to encrypt outgoing mail to the SMTP server.

        Port

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

    • DNS MX Records: Use information from DNS to determine which mail servers to use. Select this option if you use a Domain Name System (DNS) server to access the SMTP messaging server.

        Messaging domain name

          Enter the name or IP address of the messaging domain.

        Choose a specific DNS server

          Select this check box if you want to use a specify a unique SMTP server.

        DNS server for the messaging server's query

          Enter the host name or IP address of the DNS server.

        DNS port used for the messaging server's query

          Enter the port number that is used for sending queries using the messaging server.

        User ID

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

        This SMTP server requires authentication

          Select the check box to force authentication when notification mail is sent from this 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 if you want to use the Secure Sockets Layer (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.

    • If you click Do not enable notification, IBM Installation Manager skips the rest of this step, and you can configure notification later.

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

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

  32. If an error occurs during installation, IBM Installation Manager cancels the installation and rolls back the installation files. Installation errors are usually caused by environment problems such as insufficient disk space, privilege issues, or corruption of a WebSphere profile. If your installation is cancelled...

    1. Identify and resolve the error that caused the cancellation. After cancelling the installation, IBM Installation Manager displays an error message with an error code. You can look up the error code in the Installation error messages topic or check the log files.

    2. Restore the dmgr profile to a clean one.

    3. Delete the lotus_connections_root directory.

    4. Start this task again.

  33. On each node, stop any running instances of WAS and of WebSphere node agents.

  34. Restart the dmgr:

    • AIX or Linux: Open a command prompt and change to the profile_root/Dmgr01/bin directory. Enter the ./stopManager.sh command and then enter the ./startManager.sh command.

    • Windows: Stop and restart the dmgr service.

  35. Start all the federated nodes and enter the startNode command. Repeat these steps for each node:

    1. Log in to a node.

    2. From a command line, change to the profile_root/bin directory.

    3. Open the startNode file for your operating system:

      • AIX or Linux: startNode.sh

      • Windows: startNode.bat

  36. Log in to the Integrated Solutions Console on the dmgr to perform a full synchronization of all nodes.

    1. Go to System administration -> Nodes .

    2. Select the nodes and click Full Resynchronize.

    Wait until the dmgr copies all the application EAR files to the installedApps directory on each of the nodes. This process can take up to 30 minutes. To find out if the process is complete, log into each node and go to the installedApps directory and check all the application EAR files have been fully extracted. The default path is . e.g. app_server_root/profiles/AppSrv01/installedApps.

  37. Restart the dmgr.

  38. Start all the IBM Connections clusters:

    1. Log in to the Integrated Solutions Console on the dmgr

    2. Go to Servers -> Clusters -> WebSphere Application server clusters.

    3. Select the IBM Connections clusters and click Start.

    If you installed a cluster with multiple Search nodes, create the initial index before starting all the nodes.

    1. If you are installing a non-English language deployment, enable Search dictionaries.

    2. Start only one node in the cluster and wait until the Search index has been built. The index is ready when the INDEX.READY and CRAWLING_VERSION files are present in the index directory.

    3. Copy the new search index from the initial node to the other Search nodes

    4. Start the other nodes in the cluster.

    If some applications do not start, the file copying process might not have completed. Wait a few minutes and start the applications.

Results

The installation wizard has installed IBM Connections in a network deployment.

To check the details of the installation, open the log files in the lotus_connections_root/logs directory. Each IBM Connections application that you installed has a log file, using the following naming format: <application_name>Install.log, where <application_name> is the name of an IBM Connections application.

To view the log file for system events that occurred during the installation, open the <date_time>.xml file, where <date_time> represents the date and time of the installation. The file is located by default in the following directory:


What to do next

Complete the post-installation tasks that are relevant to your installation.

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

Windows 2003:

If you installed IBM Connections on Windows 2003 Server, you might encounter problems when the system tries to access a shared content store. This is an operating system defect. To work around this problem...

  1. Change the Windows 2003 network duplex setting to Auto.

  2. Change the default WINS settings to Use NetBIOS over TCP/IP.


Parent topic

Migrating to IBM Connections 3.0.1 from version 2.5

Related concepts
Deployment options
Pre-installation tasks


Related tasks


Install as a non-root user
Install in silent mode
Modifying the installation in interactive mode
Modifying the installation in silent mode
Switching to unique administrator IDs for system level communication
Access Windows network shares
Create an initial or new Search index
Setting up federated repositories
Install IBM WAS
Change server names

Related reference
Post-installation tasks
IBM Connections system requirements
Installation error messages
SQL Server 2005 JDBC 2 driver
Microsoft hotfix for the JDBC 2 driver
IBM Installation Manager information center