Skip to main content

Fix List and installation instructions for Lotus Connections 2.5.0 Fix Pack 1 (2.5.0.1)

Technote (FAQ)


Question

What issues are addressed by Lotus Connections 2.5.0 Fix Pack 1 (2.5.0.1) ? How do you apply this fix pack to upgrade to a Lotus Connections 2.5.0 Fix Pack 1 level?

Answer

This document contains instructions on how to apply this fix pack to upgrade to a Lotus Connections 2.5.0 Fix Pack 1 level. It includes important notes, fixed defects, prerequisites, and installation instructions.

Table of Contents:

  • Important Notes
  • Defects fixed
  • Prerequisite information
  • Installation instructions for a single-node (stand-alone deployment)
  • Installation instructions for a network environment (cluster deployment)

Important notes:
  • Back up all customization files that you have used with Lotus Connections 2.5.0. They need to be re-applied manually after the fixpack is installed
  • TDI update:
    • The fixpack contains a new TDI property named perform_deletion_for_sync added to the profiles_tdi.properties file to control the delete action when performing the sync task. Please refer to ifix LO46673 for more information:
        sync_updates_show_summary_only=false
        perform_deletion_for_sync=true
        will perform the deletion.

        sync_updates_show_summary_only=false
        perform_deletion_for_sync=false
        will not perform the deletion.

        sync_updates_show_summary_only=true
        perform_deletion_for_sync=true
        will not perform deletion.

        sync_updates_show_summary_only=true
        perform_deletion_for_sync=false
        will not perform deletion.
    • TDI update Install Instruction:
        1. Backup below two files in TDI 2.5 solution first

        2. Unzip LO46673.zip to TDI 2.5 solution directory, and replace the 2 changed files as below:

        <TDI25_Soultion_Home>/lib/profiles_tdi.jar
        <TDI25_Soultion_Home>/profiles_tdi.xml

        3. Open <TDI25_Solution_Home>/profiles_TDI.properties, add this line to the end of the file:
        perform_deletion_for_sync=true
      Note: <TDI25_Soultion_Home> represents your TDI 2.5 solution directory. For example: C:\Wizards\TDIPopulation\TDISOL\win\
Post-Install Instructions:
  • For Wikis SPR DARA7WTMJC:
1. Follow the instructions to check-out the widget-config.xml file.

2. Modify the widget-config.xml file:
a. Uncomment the lines:
<!--
<item name="wikiResourceId" value="wikiResourceId"/>
<item name="wikiFeedUrl" value="{wikisSvcRef}/basic/anonymous/api/userlibrary/{userid}/feed?pagesize=5"/>
-->
This will give you:
<item name="wikiResourceId" value="wikiResourceId"/>
<item name="wikiFeedUrl" value="{wikisSvcRef}/basic/anonymous/api/userlibrary/{userid}/feed?pagesize=5"/>
    b. Modify the value field for <item name="wikiFeedUrl", by changing value="{wikisSvcRef}/basic/anonymous/api/userlibrary/{userid}/feed?pagesize=5"
to value="{wikisSvcRef}/basic/anonymous/api/wikis/person/{userid}/feed?pagesize=5"

3. Follow the instructions from the link above to check-in the widget-config.xml file.
  • For Profiles 2.5.0.1 iFix LO47280 is mandatory
    1. Install Profiles iFix LO47280. Earlier patch (LO46171 integrated into the fixpack) was incorrectly escaping rich text content as if it was text, resulting in html displaying in the About Me page.
      After installing ifix LO47280 , clear out the Websphere Application Server temp directory,
      for example: C:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp\ and restart the server.

Defects fixed:
APAR#SPR#Problem Description
Activities
LO40063DARA7RKNGUFile size restriction messages are not user friendly.
LO45676MHEG7WLRTCActivitiesAPI: Auth challenge issued on HTTP URLs, causing credentials to be sent in clear
LO44561DWIN7TWKZHUpdated dojo 1.2.3 with fix for secure/nonsecure issue.
LO46168JHUG7XETDYUpdated dojo 1.2.3 with fix for secure/nonsecure issue.
SYEE7SXQSPIntermittent NodeNotFoundException (404) error when creating community activities
LO45473 DMCE7U7E7LDeleted activities, by removing the Activities widget in Communities, are still present in search results
LO45940WARE7XHU2WFor community activities, make the corresponding community uuid available to the notification JSPs so that users can customise their mail messages
ASRE7V9PJ2Reads ACF configuration file name from LCC.xml
XNKG7Y4MJVn/a
LO45325DABS7WUQ2XSearching by tag was switched to the common search index, requiring up to 15 minutes to find a recently added tag.
EHCN7Y7AYDCopying entries fails
Blogs
LO44045QWZG7W5BUCData inserted to rolleruser should be rolled backed if a login name conflict is detected
LO45273HHLI7WNLKBWhen a blog is deleted, its entries are still showing up on Homepage due to the site-wide cache and clicking on those entries results in an error
LO46049NKBI7XHML8User name is not shown in header
LO44399DARA7VYMC2Dojo editor causes a Microsoft® Internet Explorer security prompt problem
LO43747JSCR7UGKVRThere is no way to notify the blog owner when a new entry is posted for review.
ASRE7V9PJ2Reads ACF configuration file name from LCC.xm
LO43685HHLI7VBR2AThe default subscription entries feed does not always return the user's primary blog entries
LO43917LLZG7VXE3ENot able to delete uploaded image file if the image is embedded in a opened entry.
QWZG7W5BUCLogin name conflict results in a non-user-friendly error page
YYCG7XQ7QPParameter invalid error on Comments page
Core
LO46162Missing attribute in schema caused error when checking in proxy-config.tpl
JHUG7WTSPRFix to enforce UTF-8 encoding on methods that process footer.html
LO46701MMCE7Y5PP5Footer does not render for the Search application when Homepage is not installed. To fix, the search application is added by name to a list of applications maintained in the NavigationHelper code but the search application name will not display in the header.
LO45732
LO45733 LO45734 LO45735 LO45736		DVYI7WRKRFSecurity issue with group ACL service in search
ASRE7V9PJ2Allow customer to configure the name of the acf config file.
LO43710MAHN7V8KUFWhen WALTZ and the main application are located in the same classloader, Connections throws javax.net.ssl.SSLHandshakeException
LO44559 LO44560 LO44563 LO44564 LO44565 LO44601 LO44649 LO44692 QWZG7W8DDWFixes an issue with lookup of JNDI mail session when some e-mail channels are disabled for a particular notification source.
Communities
LO43716JHUG7V2S8PIncorrect baseURL with LCserver instead of the Confluence wiki server for image and bookmark content
LO43813CWUU7WG73BUpdating a community using the Atom API causes a custom community logo to be lost
LO46084JJPR7X9KBAA deleted reply entry is now showing its deleted reason.
LO45444RAPA7WP3FNNew custom widget does not work with the community edit page
LO44323GPRN7VXJY5Communities: Secure/non-secure ifix
LO44710KRED7VSM33Logos smaller than 15k may have distorted scaling if they are not square
LO45783CWUU7XC836,SYEE7X9PMUCommunity inline business card caused an error and it was missing images
LO46696LYYY7XF5SL"How to bookmark" link generates JSP Processing Error in Communities
ASRE7V9PJ2Reads ACF configuration file name from LCC.xml
LO43746THSE7S7KWHWAR update from Lotus® Quickr team
LO43847JHET7UNQSWConfirmation of actions due to session expiration can cause corruption of text formatting
LO46082JHET7XMQ2RFixes null pointer exception when creating/editing forum content
Bookmarks
LO44489MHEG7W7TA7When you open some APIs over https, even if you have the access=public parameter set, you still need to provide credential information.
LO44545EHET7W4TEHBookmark this: Secure/non-secure ifix.
LO44708ZLDI7W7BPYBookmarks can't start when Websphere Application Server can't access the /temp folder
ASRE7V9PJ2Reads ACF configuration file name from LCC.xml
MCRS7Y2L68Problem with Bookmarks seedlist when performing initial crawl of really large amount of data.
Global Search
LO43994MLES7VXHNHRecommended ifix: Search indexing tasks taking too long
LO43994MLES7VXHNHRecommended ifix: Search indexing tasks taking too long
LO45526GPRN7WZQ3BLocation codes show up in the first search view but not subsequent views
LO46785YGUO7VFRUKSearch in "All Components" with Wikis service not available produces error page.
LO43994MLES7VXHNHRecommended ifix: Search indexing tasks taking too long
LO46225MLES7XNN4QThis fix addresses an intermittent issue that can corrupt search indexes. The fix: 1) Unlock index directories on initialisation of index accessors in UnifiedIndexer. 2) Throw LockObtainFailedException explicitly up to IIndexingProcessImpl on lock error in UnifiedIndexer.initIndexAccessors() and UnifiedIndexer.index()
LO46297MLES7XBEVE /com/ibm/lotus/connections/homepage/search/servlet/AtomGenerator.class /com/ibm/lotus/connections/homepage/search/servlet/SearchAPIServlet.class
LO45772RFIH7WYG8MFixes a rarely seen query parsing issue
ADAA7Y6CDC, ADAA7Y6C97Problems with search in heavy loaded environment in some cases.
LO44490MLES7VPMNZSome legacy code was left in the 2.5 stream which causes errors to appear in the logs when Bookmarks indexing occurred.
LO46341N/AInstall search ifix fails if Activities is not install since it invokes the wrong task in search_update_cfg.xml
THEE7YFFPHMust Fix: Wikis search does not work after login
Homepage
LO43702MAHN7V8K2LNull Pointer Exception when accessing /homepage/auth/login.jsp with a browser with cookies cleared.
LO44823GPRN7VXJY5Homepage: Secure/non-secure ifix
Mobile
LO43637KGUY7V4UHNMandatory iFix: XSS fixes for mobile Activities pages.
LO46028XNKG7XQ8SAA fix for an XSS isssue caused a secondary code path to fail resulting in JSP errors for the tag clouds in the mobile application.
News
LO45588ASPR7X8EB8When using certain version/platform combinations of Oracle with the News service entries displayed in the Home Page Updates tab then new entries may not display correctly, some entries may be missing and inconsistent behavior is seen.
LO45081GPRN7W6PQGIn TAM/Siteminder environment, Home Page Top Updates may not display all status updates from a user.
LO45669LLZG7X3D97When user information in LDAP or the Profiles database changes, such as a change in name, or change in email address, that information is not reflected in new news stories shown on the Lotus Connections Home Page, unless the user subsequently logs into the Home Page.
LO46274N/AInstall news ifix fails if Activities is not installed since it invokes the wrong task in news_update_cfg.xml
Profiles
LO46171JHUG7XBSJLXSS due to unfiltering of displayed input data
LO46673JHUG7Y3T86,JMOE7Y3UA5,JHUG7XUVMH,MAHN7XQHP7Fix sync_all_dns script to compare LDAP/DB records based on configured 'sync_hash' field and Removing secretary field doesn't sync back to Profiles database. The iFix also contains the fix of three PMRs: 47527999760,47528999760,47529999760 ported to TDI 6.1.
LO46706EHET7Y4TESThe default text under find organizational tags input field is not highlighted by default
RAPA7SW5962.5.0.1: resourceId needs to be populated for widget framework
LO45909ZJSG7XN9JYThe custom label does not become effective in jobInformation section.
LO45936MAHN7XGGVXCustom attribute labels for extension attributes not showing up correctly on the search results page.
LO45083ZLUU7UFMNUPhoto Cropper in Microsoft Internet Explorer with scrollbars
LO45001LMUN7WFQMGTag Filtering not functional with all Profiles Advanced Search result sets
LO44426 BOAI7TXPYT,KRED7SQGPC,CWUU7WM3M5,ZJSG7PT72EThis is a combined ifix for Business Card, and fixed 4 issues. 1: Extending business card tabs results in all being on second row. 2: User left the company, Business Card with strange behaviour. 3: No ST awareness with two or more inline business cards on a page. 4:Profiles does not show Sametime status correctly when user is attending a meeting through the MRC.
LO44325 GPRN7VXKDHProfiles: Secure/non-secure ifix
LO45514KCLU7UUQV7Connection person card is not showing up in Quickr Domino 8.2 if Quickr Domino has a Dojo version of 0.4.3. Unfortunately, the new 2.5 business card does not support any Dojo version less than 1.0. We recommend that the customer use the old business card
LO45913EHET7X4PYTIn Microsoft Internet Explorer, board entries default text is not highlighted upon commencing to add an entry or a comment
LO46171JHUG7XBSJLXSS due to unfiltering of displayed input data
KCLU7XWM4LDownload vCard not working in old Business Card
BOAI7XHLUKBusiness Card Fixes
BOAI7XHLUKSametime Status Fixes
CWUU7WM3M5Fix for undefined error in Communities when person left the company
ASRE7V9PJ2Reads ACF configuration file name from LCC.xml
LO44430KCLU7UUQV7Connection person card is not showing up in Quickr Domino 8.2
LO44354SPR #MMCE7V2K9SLO44354 Profiles: Time does not change when time-zone changed to Saskatchewan.
JMGE7XWL5CBusiness card from external applications fails to load
Files
LO46092JMAK7XXRSAFiles: Update ACF filtering process to align with other connections components
LO45700JMAK7XXRNHFiles: Ajax proxy URL always used for business card display
MJAS7XRMG2Files: Filenotfound exception thrown when acf_config_file= not set in LCC.xml
BOAI7XXPHZFiles needs to use 2.5.0.1 Business Card Code
Wikis
LO45356DARA7WTMJCEnable Wiki widget in Profiles causes an error.
LO45344CGAA7WSLUYFix error message positioning in Add Members dialog
LO45698JMAK7XXRDTCorrect ajax proxy URL for business card display and wiki search.
LO46092JMAK7XXRWXWikis: Update ACF filtering process to align with other connections components
BOAI7XXPLCMust Fix: Wikis needs to use 2.5.0.1 Business Card Code
MJAS7XRMGYWiki: Filenotfound exception thrown when acf_config_file= not set in LCC.xml

Prerequisite information:

The WebSphere® Update Installer for Lotus Connections Version 2.5.0.1 is required. (ID: download.updii.2501.multi.00001, File name: LotusConnectionsUpdateInstaller.zip )

Installation instructions for a single-node (stand-alone deployment):
  1. Back up all customization files that you have used with Lotus Connections 2.5.0.
  2. Ensure the logged on user that is running the updateInstaller has full read/write permissions to the files/folders on the system.
  3. Stop all WebSphere application servers for Lotus Connections.
  4. Download the Lotus Connections 2.5.0 Fix Pack 1 package from IBM Fix Central (ID: 2.5.0.1-LC-Multi-FP000001), and copy it to the <lc_root>/update/fixpacks directory.
  5. To initialize the WebSphere environment for the update installer, open a command window, change to the bin directory of the WebSphere Application Server that is associated with Lotus Connections, and enter the following command:


    chmod +x setupCmdLine.sh
    .(space)./setupCmdLine.sh

    Note: When running this command in an AIX shell, be sure to use the syntax .(space)./setupCmdLine.sh. If you do not precede the command with the period and space, the
    Java™ environment is not set properly for the active shell.

    chmod +x setupCmdLine.sh
    source setupCmdLine.sh

    setupCmdLine.bat
  6. Use the update installer to install this fix pack. Enter the following command to run the update installer on the system where Lotus Connections is installed:


    /usr/IBM/WebSphere/LotusConnections/update>
    chmod +x updateLC.sh
    ./updateLC.sh -installDir /usr/IBM/WebSphere/LotusConnections
    -fixpack -install
    -fixpackDir /usr/IBM/WebSphere/LotusConnections/update/fixpacks
    -fixpackID LC2501_Fixpack -wasUserId <AdminUserID >
    -wasPassword <AdminPassword>

    /opt/IBM/WebSphere/LotusConnections/update>
    chmod +x updateLC.sh
    ./updateLC.sh -installDir /opt/IBM/WebSphere/LotusConnections
    -fixpack -install
    -fixpackDir /opt/IBM/WebSphere/LotusConnections/update/fixpacks
    -fixpackID LC2501_Fixpack -wasUserId <AdminUserID >
    -wasPassword <AdminPassword>

    C:\IBM\WebSphere\LotusConnections\update>
    updateLC.bat -installDir C:\IBM\WebSphere\LotusConnections
    -fixpack -install
    -fixpackDir C:\IBM\WebSphere\LotusConnections\update\fixpacks
    -fixpackID LC2501_Fixpack -wasUserId <AdminUserID >
    -wasPassword <AdminPassword>

    where <AdminUserID> is the user ID and <AdminPassword> is the password associated with the WebSphere Application Server administrative user.

    Note: See the updateLC command for information about additional command options.
  7. Ensure that the features were updated properly. To access each feature from the system that hosts the primary node of the features, open a Web browser and type the Web address using the following syntax:

    http://<was_server_host_name>:<port_number>/<feature_name>

    where <port_number> is the port number on the WebSphere Application Server where the feature is available. Refer to the WebSphere Application Server configuration file (serverindex.xml) for the node to find port number assignments. The following Web address opens the Activities feature directly from the WebSphere Application Server: http://appserver.acme.com:9080/activities

    You can also check the logs. One log is created for each feature installed. The files are named <date>_LC2501_Fixpack_<feature_name>_install.log and are stored in the following directory:

    /usr/IBM/WebSphere/LotusConnections/version/log
    /opt/IBM/WebSphere/LotusConnections/version/log
    C:\IBM\WebSphere\LotusConnections\version\log
  8. Start the IBM HTTP Server if you stopped it .
  9. Access the features using their public Web addresses. Click the About links for each feature to ensure that the correct build number is displayed.
  10. Validate the security settings for Lotus Connections. Keep in mind that the update might overwrite any changes made to the settings. For example, the update enables the All Authenticated role by default. If you previously disabled it, you must explicitly disable it again.


Installation instructions for a network environment (cluster deployment):
Use the update installer to install this fix pack, which updates Lotus Connections 2.5.0 to a version 2.5.0 fix pack 1 level in a cluster deployment.

When you update Lotus Connections, you must update the first node of the cluster first. Before you perform the update, determine which system in your deployment is the first node. See Updating a network deployment for more details.

Attention: You must update all the features in a network deployment.

Complete these steps to update a network deployment of Lotus Connections to a version 2.5.0 fix pack 1 level:

  1. The update installer does not currently support 24x7 updates. You must apply the updates at a time when no one is logged into the product. See Preparing Lotus Connections for maintenance for more information.
  2. Make sure all systems are stopped, and then back up the system files. To do so, archive the WebSphere Application Server root directory.

    /usr/IBM/WebSphere/
    /opt/IBM/WebSphere/
    C:\IBM\WebSphere\
  3. To store the update fix pack, create the following directory if it does not already exist:

    /usr/IBM/WebSphere/LotusConnections/update/fixpacks
    /opt/IBM/WebSphere/LotusConnections/update/fixpacks
    C:\IBM\WebSphere\LotusConnections\update\fixpacks
  4. Download the Lotus Connections 2.5.0 Fix Pack 1 package (LC2501_Fixpack.jar) from the IBM Fix Central Web site.
  5. Save the file to the fixpacks directory that you created in step 3.
  6. Start each server that hosts a Lotus Connections feature using the WebSphere Application Server administrative console for the Deployment Manager system.
  7. Check the Deployment Manager to make sure that Automatic synchronization is selected for all nodes. See Synchronizing updated nodes for details.
  8. Install the update on the WebSphere Application Server installation that represents the first node of the cluster. To do so, complete the following steps:
    1. Refer to the list you compiled of first node and secondary cluster members, and then use the Deployment Manager to turn off both automatic and startup synchronization for the secondary nodes. See Synchronizing updated nodes for details.
    2. To initialize the WebSphere environment for the update installer, open a command window, change to the bin directory of the WebSphere Application Server that is associated with Lotus Connections, and enter the following command:


      chmod +x setupCmdLine.sh
      .(space)./setupCmdLine.sh

      Note: When running this command in an AIX® shell, be sure to use the syntax .(space)./setupCmdLine.sh. If you do not precede the command with the period and space, the Java environment is not set properly for the active shell.

      chmod +x setupCmdLine.sh
      source setupCmdLine.sh

      setupCmdLine.bat
    3. To run the update installer on the system hosting the first node, enter the following command:


      /usr/IBM/WebSphere/LotusConnections/update>
      chmod +x updateLC.sh
      ./updateLC.sh -installDir /usr/IBM/WebSphere/LotusConnections
      -fixpack -install
      -fixpackDir /usr/IBM/WebSphere/LotusConnections/update/fixpacks
      -fixpackID LC2501_Fixpack -wasUserId <AdminUserID>
      -wasPassword <AdminPassword>

      /opt/IBM/WebSphere/LotusConnections/update>
      chmod +x updateLC.sh
      ./updateLC.sh -installDir /opt/IBM/WebSphere/LotusConnections
      -fixpack -install
      -fixpackDir /opt/IBM/WebSphere/LotusConnections/update/fixpacks
      -fixpackID LC2501_Fixpack -wasUserId <AdminUserID>
      -wasPassword <AdminPassword>

      C:\IBM\WebSphere\LotusConnections\update>
      updateLC.bat -installDir C:\IBM\WebSphere\LotusConnections
      -fixpack -install
      -fixpackDir C:\IBM\WebSphere\LotusConnections\update\fixpacks
      -fixpackID LC2501_Fixpack -wasUserId <AdminUserID>
      -wasPassword <AdminPassword>

      where <AdminUserID> is the user ID and <AdminPassword> is the password associated with the WebSphere Application Server administrative user.

      Note: See the updateLC command for information about additional command options.
    4. To force the update to be applied to the other members of the cluster, perform a full synchronization. See Synchronizing updated nodes for details.
  9. If a different system serves as the first node of another cluster, repeat step 8 to install the update to the first node and synchronize it to the secondary members. Be sure to first update all systems that serve as first nodes. Do not continue to step 10 until you have done so.
  10. Make sure that the features were updated properly. To access each feature from the system that hosts the first node of the features, open a Web browser and type the Web address using the following syntax:

    <was_server_host_name>:<port_number>/<feature_name>

    where the <port_number> is the port number on the WebSphere Application Server that the feature is available from. Refer to the WebSphere Application Server configuration file (serverindex.xml)
    for the node to find port number assignments. The following Web address opens the Activities feature directly from the WebSphere Application Server:

    http://appserver.acme.com:9080/activities

    You can also check the logs. One log file is created for each feature installed. The files are named <date>_LC2011_Fixpack_<feature_name>_install.log and are stored in the following directory:

    /usr/IBM/WebSphere/LotusConnections/version/log
    /opt/IBM/WebSphere/LotusConnections/version/log
    C:\IBM\WebSphere\LotusConnections\version\log
  11. Start the IBM HTTP Server if you stopped it.
  12. Access the features using their public Web addresses. Click the About links for each feature to make sure that the correct build number is displayed.
  13. Validate the security settings for Lotus Connections. Keep in mind that the update might overwrite any changes made to the settings. For example, the update enables the All Authenticated role by default. If you previously disabled it, you must explicitly disable it again.


Copyright and trademark information

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Document information

IBM Connections

Install

Software version:
2.5

Operating system(s):
AIX, Linux, Mac OS X, Windows

Reference #:
1414801

Modified date:
2010-05-19

Translate my page

Content navigation