+

Search Tips   |   Advanced Search

Install Connections 5.0


Overview

If an error occurs during installation, Installation Manager (IIM) 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 wer installation is canceled:

  1. Identify and resolve the error that caused the cancellation.

    After canceling the installation, IIM displays an error message with an error code. We can look up the error code in the Installation error messages topic or check the log files.

  2. Restore the dmgr profile from the backup.

  3. Delete the connections_root directory.

  4. Start the task again.


To install Connections

  1. Obtain part numbers for Connections 5.0

  2. Complete prerequisite tasks

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

  4. Make a backup of dmgr file system, and DBx

  5. Start WAS dmgr.

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

  7. Start the Connections launchpad or run IIM...

    1. Start the Connections launchpad...

        CONNECTIONS_SETUP/launchpad.sh

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

      • Install a web browser.

      • Install Connections in silent mode.

      • Start IIM manually...

          cd Connections_install/IM/OS
          ./install.sh -input response.xml

        ...or...

          /install.sh -input response.xml -dataLocation /opt2/ibm/InstallationManager

        Another option is to add...

        ...to IIM via the preferences option. Once done, you only need to click the Install option on the main screen and IIM should proceed as usual with the installation.

    2. If we already have an IIM, from the IIM directory, start the IIM, and add the repository to it...

        ./IBMIM

      Repository:

        Connections_set-up\Connections\repository.config

      Installation Manager might ask you to upgrade the Installation Manager. The 32-bit Installation Manager only can be upgraded by 32-bit higher version Installation Manager. The 64-bit Installation Manager only can be upgraded by 64-bit higher version Installation Manager. Connections bundles only the 32-bit, version 1.7.1 Installation Manager. If we need related 64-bit Installation Manager, download it from the Installation website separately.

  8. When the launchpad appears, click...

      Install Connections 5.0 | Launch the Connections 5.0 install wizard | Welcome

  9. When IIM is launched, in the window...

      Select packages to install

    ...select the packages to install...

    • Accept the default setting for Show all versions.

    • For an earlier version of IIM than 1.7.1, the 1.7.1 package is selected in this window.

    • To search for updates to IIM, click...

        Check for Other Versions and Extensions

  10. Review and accept the license agreement

  11. Specify location of...

    1. Shared Resources directory.
    2. Installation Manager directory

    The Shared Resources directory stores resources that can be shared by multiple packages. If we used IIM before, the wizard automatically enters this value.

    The Installation Manager directory stores resources that are unique to the packages that we are installing.

  12. For shared and remote network file system requirements, review footnotes in the system requirements.

  13. Choose to either...

    • Use the existing package group
    • Create a new package group

    For the wizard for the first time, the option...

      Use the existing package group option

    ...is not available.

  14. Specify the location of the install directory for Connections.

    We can accept the default directory location, enter a new directory name, or click Browse to select an existing directory. Click Next.

    The path only can consist of letters (a-z, A-Z), numbers (0-9), and an underscore (_).

  15. Confirm the applications to install.

    The wizard always installs...

    • Home page
    • News
    • Search applications

    To use media gallery widgets in the Communities application, install the Files application. Media gallery widgets store photo and video files in the Files database.

    Even if we are not planning to configure Cognos later, install Metrics now so the application data is captured from the moment that IBM Connections is deployed. Metrics captures the deployment data whereas Cognos is used for viewing data reports. If we install Metrics at a later stage, you will not have any data reports for the period before installing Metrics.

    Option Description
    IBM Connections 5.0 Install all 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.
    Connections Content Manager Manage files using advanced sharing and draft review in content management libraries in Communities. Requires the Communities application to be installed. If we choose to install Connections Content Manager, Communities will be selected automatically, because they need to work together.

    Connections Content Manager appears under Add-on.

    Metrics Identify and analyze usage and trends.
    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 the website.

  16. Enter the details of the WAS environment:

    1. Select the WAS installation location containing the dmgr.

      Default path to the WAS installation...

        /usr/IBM/WebSphere/AppServer

    2. Properties of the WAS dmgr:

      dmgr profile Name of the dmgr to use for Connections. The wizard automatically detects any available dmgrs.
      Host name Name of the host dmgr server.
      Administrator ID The administrative ID of the dmgr.

      Set to the connectionsAdmin J2C authentication alias, which is mapped to the following Java EE roles:

      • dsx-admin
      • widget-admin
      • search-admin

      It is also used by the service integration bus.

      To use security management software such as TAM or SiteMinder, the ID specified here must exist in the LDAP directory.

      This user account can be an LDAP or local repository user.

      Administrator Password The password for the administrative ID of the dmgr.
      SOAP port number The SOAP port number of the dmgr. The wizard automatically detects this value.

    3. Click Validate to verify your DM information, and that application security is enabled on WAS.

      If the verification fails, IIM displays an error message.

      (AIX and Linux) The validation process checks the number of open files supported by the system. If the Open File Descriptor limit is too low, a file open error, memory allocation failure, or connection establishment error could occur. If one of these errors occurs, exit the installation wizard and increase the limit before restarting the wizard. To set the file limit, refer to the Installation error messages.and search for error code CLFRP0042E. The recommended value for Connections is 8192.

    4. When the verification test is successful, click Next.

    The wizard records details of the cell, node, and server in file dmInfo.properties

  17. Configure Connections Content Manager deployment option.

    This panel displays if you chose to install the Connections Content Manager feature.

    • Select "Existing Deployment" if you intend to install the FileNet servers (JVMs and clusters) manually:

      1. Enter FileNet Object Store administrator username and password

      2. Enter the HTTP URL for the FileNet Collaboration Services server:

          http://fncs.myco.com:80/dm

      3. Enter the HTTPS URL for the FileNet Collaboration Services server:

          https://fncs.myco.com:443/dm

    • Select "New Deployment" even if you previously installed a new deployment of Connections Content Manager for the 4.5 release.

      We do not need to reinstall the FileNet domain and the object store; only the new server infrastructure (JVMs and WebSphere clusters):

      1. Specify an anonymous user name and password account.

        This account can be a system-type account that is not used by an actual person and should not have any special privileges beyond what is specified in Set up anonymous access for a new FileNet deployment. If this account is not specified, then anonymous access is disabled

      2. Enter FileNet installer packages location.

        The four FileNet installers:

        • Content Platform Engine
        • FileNet Collaboration Services
        • FileNet fix pack
        • Content Platform Engine Client

        ...need to be placed into the same folder. The package names are :

        Content Platform Engine FileNet Fix pack Content Platform Engine Client FileNet Collaboration Services
        AIX: 5.2.0-P8CE-AIX.BIN 5.2.0.3-P8CPE-AIX-FP003.BIN 5.2.0.3-P8CPE-CLIENT-AIX-FP003.BIN 2.0.0.1-FNCS-IF001-AIX.bin
        Linux: 5.2.0-P8CE-LINUX.BIN 5.2.0.3-P8CPE-LINUX-FP003.BIN 5.2.0.3-P8CPE-CLIENT-LINUX-FP003.BIN 2.0.0.1-FNCS-IF001-Linux.bin
        Windows: 5.2.0-P8CE-WIN.EXE 5.2.0.3-P8CPE-WIN-FP003.EXE 5.2.0.3-P8CPE-CLIENT-WIN-FP003.EXE 2.0.0.1-FNCS-IF001-WIN.exe

        For the Linux platform, at least 3 GB of free disk space is needed under the /tmp folder for the Connections 5.0 CCM installation, or else there will be an installation failure.

        We can set up the environment variable IATEMPDIR so the FileNet installer uses that location instead of the system temp directory (/tmp on AIX/Linux, %TEMP% on Windows).

      3. Click Validate to ensure the user account and package locations are configured correctly.

    Refer to Configure IBM Connections Content Manager to find the post-installations tasks perform to get CCM up and running.

  18. Configure the topology.

    If we return to this page from a later page in the installation wizard, the settings are still present but not visible.

    To change any settings, enter all of the information again. To not change the initial settings, click Next.

    The applications for Connections Content Manager will not be shown if you have chosen to use an existing FileNet deployment.

    • Small deployment:

      1. Select the Small deployment topology.

      2. Enter a Cluster name for the topology.

      3. Select a Node.

      4. Click Next.

    • Medium deployment:

      1. Select the Medium deployment topology.

      2. Enter a Cluster name for each application or for groups of applications.

        For example, use Cluster1 for Activities, Communities, and Forums.

        IIM creates servers and clusters when required.

      3. Select a Node for each cluster.

        Accept the predefined node or select a different node.

        These nodes host application server instances that serve Connections applications. We can assign multiple nodes to a cluster, where each node is a server member of that cluster.

      4. Enter a Server member name for the selected node.

        The name must be unique across all nodes in the deployment.

      5. Click Next.

    • Large deployment:

      1. Select the Large deployment topology.

      2. Enter a Cluster name for each application.

        IIM creates servers and clusters when required.

      3. Select a Node for each cluster.

        Accept the predefined node or select a different node.

        These nodes host application server instances that serve Connections applications. We can assign multiple nodes to a cluster, where each node is a server member of that cluster.

      4. Enter a Server member name for the selected node.

        The name must be unique across all nodes in the deployment.

      5. Click Next.

  19. Enter the database information:

    If we return to this page from a later page in the installation wizard, the settings are still present but not visible.

    To change any settings, enter all of the information again. To not change the initial settings, click Next.

    The Connections Content Manager databases will not be shown if you have chosen to use an existing FileNet deployment.

    Database information for Global Configuration Data and Object Store must be set correctly, otherwise installation will fail.

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

      If allowed by the database configuration, we can select multiple database instances as well as different database servers.

    2. Select a database type...

      • IBM DB2 Universal Database
      • Oracle Enterprise Edition
      • Microsoft SQL Server Enterprise Edition

    3. Enter the Database server host name. For example:

        dbserver.enterprise.myco.com

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

    4. Enter the Port number of the database server.

      • 50000 for DB2
      • 1521 for Oracle
      • 1433 for SQL Server

      If wer installed applications use different database servers or instances, enter the port number for each database server or instance.

    5. Enter the JDBC driver location. For example:

        /usr/IBM/WebSphere/AppServer/lib

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

        DB2 db2jcc4.jar and db2jcc_license_cu.jar

        Ensure the user account has the necessary permissions to access the DB2 JDBC files.

        Oracle ojdbc6.jar
        SQL Server Download the SQL Server JDBC 4 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 data source is configured to use the sqljdbc4.jar file, an exception occurs if both files are present in the same directory.

    7. Enter the User ID and Password for each database.

      If each database uses the same user credentials, select the check box...

        Use the same password for all applications

      ...and then enter the user ID and password for the first database in the list.

      If the database type is Oracle, connect to the database with the user ID used when we created the application database.

    8. Click Validate to verify the database settings.

      If the validation fails, check the database settings.

      When the validation succeeds, click Next.

      IIM tests the database connection with the database values that you supplied. We can change the database configuration later in the WAS console.

      Usually we can continue even if the validation failed because we can change the database settings from WAS console afterwards. However, we cannot continue if you have entered incorrect information for the Connections Content Manager database, because there are database operations during installation. Incorrect database information will cause installation to fail. So use correct information for Connections Content Manager database.

  20. Select the Do Later option, and configure Cognos later using the Cognos Wizard.

  21. Specify the locations of the content stores.

    All nodes in a cluster must have read-write access to shared content accessible using the same path from all nodes and from the dmgr. Each content store is represented by a corresponding WebSphere variable that is further defined as shared or local. Local content is node-specific.

    For migrations from IBM Connections 4.5, reuse the existing content stores in 5.0 in order to maintain data integrity.

    1. Enter the location of the Shared content store.

      • Network-based file shares

        • NFS
        • SMB/Samba

      • Storage area network drives (SAN)

      • Windows shared-file systems.

        Specify the file location with UNC format...

          \\server_name\share_name

        If we use Remote Desktop Connection to map shared folder drives, use the same session to start the node agents. Otherwise, the shared drives might be invisible to the nodes.

    2. Enter the location of the Local content store.

    3. Click Validate to verify the account that we are using to install Connections has write access to the content store.

    4. Click Next.

  22. Select a Notification solution.

      Enable Notification only Use notifications but without the ReplyTo capability.
      Enable Notification and ReplyTo With ReplyTo, the mail server receives all replies, and funnels them into a single inbox. Connection connects to the mail server using the IMAP protocol.
      None Do not use a notifications. We can configure notifications after installation.

  23. Select and specify a mail server solution

    • WebSphere Java Mail Session

      Use a single mail server for all notifications. Select if we can access an SMTP server directly using the host name.

      Identify the mail server to use for sending email:

        Host name of SMTP messaging server

        Host name or IP address of the preferred SMTP mail server.

        This SMTP server requires authentication

        Select to force authentication when mail is sent from this server.

        User ID

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

        Password

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

        Encrypt outgoing mail traffic to the SMTP messaging server using SSL

        Select to encrypt outgoing mail to the SMTP server.

        Port

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

    • DNS MX Records

      Use information from DNS to determine which mail servers to use. Select to use a DNS server to access the SMTP messaging server.

        Messaging domain name

        Name or IP address of the messaging domain.

        Choose a specific DNS server

        Select to specify a unique SMTP server.

        DNS server for the messaging servers query

        Host name or IP address of the DNS server.

        DNS port used for the messaging servers query

        Port number used for sending queries using the messaging server.

        This SMTP server requires authentication

        Select to force authentication when notification mail is sent from this 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 to use SSL when connecting to the SMTP server.

        Port

        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.

    • Do not enable Notification

      IIM skips the rest of this step. We can configure notification later.

  24. If we selected the Notification and ReplyTo option, configure the ReplyTo email settings.

    Connections uses a unique ReplyTo address to identify both...

    • The person who replied to a notification
    • The event or item that triggered the notification

    1. Enter a domain name. For example:

        mail.myco.com

      This domain name is used to build the ReplyTo address. The address consists of..

      • The suffix or prefix
      • A unique key
      • The domain name

    2. The reply email address is given a unique ID by the system.

      We can customize the address by adding a prefix or suffix, using a maximum of 28 characters. This extra information is useful if the domain name is already in use for other purposes. Select one of the following options:

      None Use the ID generated by system.
      Prefix Enter a prefix in the Example field.
      Suffix Enter a suffix in the Example field.

      As you select an option, the wizard creates an example of the address, combining the selection with the ID generated by system.

      For example:

      • unique_id@domain
      • prefix_unique_id@domain
      • unique_id_suffix@domain

    3. Specify the details of the mail file to which ReplyTo emails are sent:

      Server The domain where the mail server is located. For example:

        replyTo.mail.myco.com

      User ID User account for the mail server.
      Password Password for the user account.

      Connections will use the credentials to poll the inbox on the mail server, retrieve replies, and process the content. Connections connects to the mail server using IMAP.

    4. Click Next.

    To edit the ReplyTo settings domain name and prefix or suffix after installation, edit news-config.xml.

    To edit server and authentication details, log in to the WAS console and navigate to the Mail Sessions page, where we can edit the configuration.

  25. To revise your selections, click Back.

    To finalize the installation, click Next. The installation begins

  26. Installation Manager displays a status page after installation completes.

    If satisfied, click Finish to exit the installation wizard.

  27. Restart the dmgr:

      cd app_server_root/profiles/Dmgr01/bin
      ./stopManager.sh
      ./startManager.sh command.

  28. For each node, log on and start node agent...

  29. Log in to the WAS console on the dmgr and perform a full synchronization...

      System administration | Nodes | nodes | 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 verify the dmgr has distributed the application EAR files to the nodes, check...

    ...and look for a messages such as...

      ADMA7021I: Distribution of application application_name completed successfully.

  30. Restart the dmgr.

  31. Start all the Connections clusters...

      Servers | Clusters | WebSphere Application server clusters | Connections clusters | Start

  32. If we installed a cluster with multiple Search nodes, create the initial index.

  33. If we are installing a non-English language deployment, enable Search dictionaries.

    The index is ready when the INDEX.READY and CRAWLING_VERSION files are present in the index directory.

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

    If Connections applications are installed on different clusters, the cluster start order should be...

    • News cluster
    • Profiles cluster
    • Search cluster
    • Dogear cluster
    • Communities cluster
    • Activities cluster
    • Blogs cluster
    • Files cluster
    • Forums cluster
    • Wikis cluster
    • Hompage cluster
    • Metrics cluster
    • Mobile cluster
    • Moderation cluster
    • Connections Content Manager cluster

  35. To confirm the installation was successful, open the log files in...

    Each Connections application installed has a log file...

      application_nameInstall.log

    To view the log file for system events that occurred during the installation, open...

      /var/ibm/InstallationManager/logs/date_time.xml

    For non-root user...

      /home/user/var/ibm/Installation Manager/logs


What to do next

Complete post-installation tasks.

If we installed WebSphere Application Server on Windows, and configured it to run as a service, ensure that we can access network shares.


Parent topic:
Install Connections

Related:
Deployment options
Content store migration
Access Windows network shares
IBM Connections system requirements
IIM hangs while being installed on AIX 64-bit systems
Linux libraries
Installation error messages
IIM information center
Troubleshooting Cognos validation problems
Post-installation tasks