Installing CR5 for IBM Connections 6.0

Install a Cumulative Refresh (CR) for IBM® Connections 6.0.

Before you begin

Complete the following tasks before attempting to install the CR5 update:

  1. On the system where the Deployment Manager is installed, prepare the supporting software for the update:
    • Download and extract the CR5 update installation package 6.0.0.0-IC-Multi-CR05-LO94188. For more information, see Downloading the latest Cumulative Refresh (CR) and related updates.
    • Verify that you are running IBM® Installation Manager 1.8.5 64-bit or higher.
    • WAS 8.5.5.15 is now supported but requires an iFix for APAR IFPH09407 which can be download from Fix Central, 8.5.5.15-WS-WASProd-IFPH09407
    • Verify that you have installed WebSphere® Application Server 8.5.5.12 - 8.5.5.14 and supplemental software, and have updated IBM® HTTP Server 8.5 and Web Server Plug-ins for IBM® WebSphere® Application Server 8.5.
      Note:
    • In the soap.client.props file, change the SOAP Request Timeout to com.ibm.SOAP.requestTimeout=0 to ensure that no requests time out during the Cumulative Refresh installation.
    • Restart the Deployment Manager and start the HTTP services: IBM® HTTP Administration for WebSphere® Application Server V8.5 and IBM® HTTP Server V8.5.

About this task

If you are updating a newly installed or migrated deployment, you only need to update with the newest Cumulative Refresh, because it contains all of the updates from previous refreshes.

Attention:

As of the release of IBM Connections 6.0 CR3 or higher, Communities integrates a subset of IBM Connections Engagement Center features, collectively known as the "Highlights app." This app can be customized to retrieve community content and present it to fit the needs of your community. To make this possible, CR3 or higher installs the Highlights app on the same cluster as the Communities app. If ICEC was previously deployed on a different server, the CR3 or higher install will move it to the Communities cluster to ensure that the Highlights app functions properly.

To add widgets within the new Highlights app, users must access the server using HTTPS protocol over a secure connection. For more information on setting up an encrypted connection, see Configuring IBM HTTP Server for an encrypted connection and Forcing traffic to be sent over an encrypted connection.

If you do not want to enable TLS/SSL for your deployment, you can disable the Highlights app as explained in (Optional) Disabling the Highlights app.

Procedure

  1. Update databases for Connections as explained in Updating IBM Connections databases for V6.0 CR4.
  2. Remove the <loginRedirectWhitelist> setting from the LotusConnectionConfig.xml file.
    • If you are updating from CR2, you will have this setting but should not remove it. Skip to step 3.
    • If you are updating from V6.0, you will not have this setting. Skip to step 3.
    • If you are updating from IFR1/CR1, you might have this setting and will need to remove it if so. Check the LotusConnections-config.xml to see if it contains this setting. If the setting exists, complete the following steps to remove it.

      If you installed IFR1/CR1, then you might have added the <loginRedirectWhitelist> setting as instructed by the technote IBM Connections Security Refresh (CVE-2017-1748) for Connections 6.0 CR1. This setting will prevent CR3 or higher from installing correctly, so you must remove it temporarily.

    1. Open the LotusConnections-config.xml for editing as explained in Editing configuration files.
      The file can be found in the following location: 
      IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\Cell_Name\LotusConnections-config
    2. If your file contains one or more domain names instead of admin_replace.com, then remove the setting: 
      <loginRedirectWhitelist enabled="false">
<domain>admin_replace.com</domain>
</loginRedirectWhitelist>
    3. Save and close the file.
  3. If you use IBM Security Access Manager (ISAM), ensure that it support the new Highlights app by configuring Security Access Manager to include host information in the HTTP header.
    1. Note: Completed as part of CR3 or higher install.

    2. Edit the webseald-server-name.conf file.
    3. In the [header-names] stanza, add the following line:

      httphdr{host} = X-Forwarded-Host

      For more information about configuring Security Access Manager, see Enabling single sign-on for IBM Security Access Manager.

    4. Stop and restart your WebSEAL instance.
  4. Stop all clusters and node agents in your deployment but leave the Deployment Manager running.
  5. Start IBM® Installation Manager.
  6. From the IBM® Installation Manager menu, click File > Preferences.
    Note: Be sure that the Search service repositories during installation and updates option is deselected.
  7. Click Repositories > Add Repository.
  8. Enter the full path to the Cumulative Refresh package that you downloaded and then click OK.

    For example: C:\IBM\CONNECTIONS-CR\IC-CR5\6.0.0.0-IC-Multi-CR05-LO94188\Updates\repository.config.

    Verify that IBM® Installation Manager can connect to the repository.
  9. Click OK.
  10. Click Update.
  11. Select IBM Connections 6.0 and click Next.
  12. Verify that the correct Cumulative Refresh version is displayed and click Next.
  13. Review and accept the license agreement by clicking I accept terms in the license agreements and then click Next.
  14. Ensure that all the IBM® Connections applications are selected and click Next.
    Note: All of the installed applications are selected by default. If you add any of the non-selected applications, those applications will be installed. If you clear any of the selected applications, those applications will be uninstalled.
  15. Enter the administrative ID and password of the Deployment Manager and click Validate.
    Note: This ID is set to the connectionsAdmin J2C authentication alias, which is mapped to the following Java™ EE roles: dsx-admin, widget-admin, and search-admin. It is also used 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. For more information, see the Switching to unique administrator IDs for system level communication topic.
  16. Note: When upgrading from IC6.0 CR3 or higher, Step 16 is not required and the screen will not appear. You can advance to Step 17.
    Enter the database information for the XCC (Highlights app) database.
    Note: The user name and password that you provide must match the user name and password in the script that was used to create the XCC database.
  17. Click OK > Next > Update > Finish.
  18. Close Installation Manager.
  19. When the installation is complete, start the node agent to deploy the updated IBM® Connections applications.
  20. Note: When upgrading from IC6.0 CR3 or higher, Steps 20 and 21 are not required. You can advance to Step 22.
    Verify that "xcc" (the new Highlights app) is assigned to both ICCluster and Webserver:
    1. Open the WebSphere Integrated Solutions Console and click Applications > All applications > ICEC > Manage modules to view the list of modules.
    2. In the Clusters and servers list, select both the Connections cluster and the Webserver.
    3. In the table, select the xcc module.
    4. Click OK.
    5. Update the master configuration by clicking Save in the "Messages" box.
  21. Generate a new plug-in (to include the new Highlights app) by completing the following steps.
    1. Still in the Integrated Solutions Console, click Servers > Server Types > Webservers.
    2. Select the Webserver, click Generate Plug-in, and wait for the plug-in to be generated.
    3. Select the Webserver again and click Propagate Plug-in.
  22. Stop the node agent so the temp directory can be cleaned out in the next step.
  23. Delete the contents of the cache under the App Server (for example, C:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp).
  24. Start the node agents, then perform a full synchronization to push the update to all nodes.

    Check the SystemOut.log of each nodeagent to ensure synchronization completed successfully.

  25. If you temporarily removed any settings from the LotusConnectionConfig.xml file in step 2, replace them now.
  26. Note: When upgrading from IC6.0 CR3 or higher, Step 26 is not required.
    Review the security roles for the Highlights app; for more information, see the Connections Engagement Center topic, Mapping security roles.

Results

Your IBM® Connections deployment has been updated. To check the logs, go to the connections_root/logs directory and open the applicationUpdate.log file, where application is the name of an IBM® Connections application. If you added new applications, check the applicationInstall.log file as well.

What to do next

If you previously installed Solr to support type-ahead search: .