Fix List and installation instructions for Lotus Connections 2.5.0 Fix Pack 2 (2.5.0.2)

Technote (FAQ)


Question

What issues are addressed by Lotus Connections 2.5.0 Fix Pack 2 (2.5.0.2)? How do I apply this fix pack to upgrade to a Lotus Connections 2.5.0 Fix Pack 2 level?

Answer

This document contains instructions on how to apply this fix pack to upgrade to a Lotus Connections 2.5.0 Fix Pack 2 level. Fix Pack 2 supports an upgrade from either Lotus Connections 2.5.0 or a 2.5.0 Fix Pack 1 level with exception to zLinux platform which supports upgrade from 2.5.0 Fixpack 1 level only. This document includes important notes, fixed defects, prerequisites, and installation instructions.

Table of Contents:


Important notes:

  • Back up all customization files that you have used with Lotus Connections 2.5.0 or 2.5.0 Fix Pack 1. They must be re-applied manually after the fix pack is installed.
  • Tivoli Directory Integrator (TDI) update:
    • Mandatory iFix for TDI is published in a separate iFix package - LO52087. Back up your current TDI scripts and follow the LO52087 install instruction to refresh your current TDI scripts. If you are upgrading from a 2.5.0 level, refer to the Important Notes section in 2.5.0.1 fix pack level 1 Readme file and add additional parameters supporting synchronization without deletion.
  • LO47704 - iFix for the Confluence connector: If you have Confluence configured, download the new 2502 iFix from Fix Central and install it after you deploy this fix pack.
  • If you are upgrading from Lotus Connections 2.5.0 Fixpack 1 and have not installed 2.5.0.1 iFix LO48007 before upgrading to Fixpack 2, you might be getting this error while running the upgrade in silent mode. It is safe to ignore this error:

    org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.
    Post-Installation Instructions:
    • LO46757 - Adding support for Lotus Connections 2.5 Business Card for QuickrJ 8.5 requiring Hot fix from WebSphere Portal 6.1.5: APAR PM02565
    • LO48424 - If you are integrating the business card with Lotus Quickr 8.2, apply Quickr Fix Pack 8.2.0.10-003a or later for some javascript errors that were thrown by Quickr code expecting to initialize the business card
    • The default proxy-config.tpl file contains the following policy:

      <!-- This is the default policy, which applies to all URLs not explicitly listed in an earlier policy.
      This policy allows only HTTP GET actions, and allows no cookies or headers to pass through. This policy should always be last in the list. -->

      <proxy:policy url="*" acf="none">
      <proxy:actions>
      <proxy:method>GET</proxy:method>
      </proxy:actions>
      <proxy:headers/>
      <proxy:cookies/>
      </proxy:policy>
      Above policy should be removed from the file on extranet deployments. Any feeds or third-party widgets that the administrator wants to enable for the users of the site must be explicitly added.

      For example, to allow users to add feeds from my.rss.com, the administrator would add the following policy:

      <proxy:policy url="my.rss.com/*" acf="none">
    <proxy:actions>
    <proxy:method>GET</proxy:method>
    </proxy:actions>
    <proxy:headers/>
    <proxy:cookies/>
    </proxy:policy>

    NOTE: policy url value must be preceded by the protocol.

    For more detail on how to configure the AJAX Proxy to permit access to feeds and widgets, see the topic "Configuring the AJAX Proxy" in the Lotus Connections 2.5 Information Center.
    • LO50171; LO50222; LO50231; LO50281; LO50282; LO50628; LO50629 - Within notification-config.xml you can set the alwaysUseGlobalSender property to true to force all emails to be sent by the global email address (already specified in notification-config.xml).

      Additionally, you can set the following optional properties if alwaysUseGlobalSender is set (if it is not, or is false, these properties are ignored):

      globalSenderName - Sets the Display name (e.g. "Connections admin") and will be visible in received emails.
      includeOriginalSenderAsReplyTo - Indicates if the original sender should be identified in the replyto field of the email. The default value is true.

      Example configuration:

      <properties>
      <property name="alwaysUseGlobalSender">true</property>
      <property name="globalSenderName">Connections Administrator</property>
      <property name="globalSenderEmailAddress">admin@foo.com</property>
      <property name="includeOriginalSenderAsReplyTo">false</property>
      </properties>
    • The default ACF configuration file provided with Connections 2.5.0.2 improperly strips out styles from Blogs and Wikis entries. This instruction describes manual changes the customer can make to the Connections configuration to correct the problem.

      Following the instructions in the Connections info center, check out the LotusConnections-config.xml file and open it in a text editor.
      http://publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/topic/com.ibm.connections.25.help/t_admin_common_changing_config.html

      Locate the serviceReference element for the Blogs service, which will look something like this:

      <sloc:serviceReference enabled="false" person_card_service_name_js_eval="generalrs.label_personcard_blogslink" person_card_service_url_pattern="/roller-ui/blog/{userid}" serviceName="blogs" ssl_enabled="false">
      <sloc:href>
      <sloc:hrefPathPrefix>/blogs</sloc:hrefPathPrefix>
      <sloc:static href="admin_replace" ssl_href="admin_replace"/>
      <sloc:interService href="admin_replace"/>
      </sloc:href>
      </sloc:serviceReference>

      Insert the following into the element after "sloc:serviceReference"
      acf_config_file="acf-config-flash.xml"

      The modified line should look like this:
      <sloc:serviceReference acf_config_file="acf-config-flash.xml" enabled="false" person_card_service_name_js_eval=.....>
      ....
      </sloc:serviceReference>

      Locate the serviceReference element for the Wikis service and make the same change. Save the file and, following the instructions in the Connections info center, check the LotusConnections-config.xml file back into the system.
    • This fixpack contains several APARs that require the search index to be rebuilt. To ensure the search index is accurate, delete and rebuild the index by following the instructions on the InfoCenter: http://publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/index.jsp?topic=/com.ibm.connections.25.help/t_admin_search_delete_index.html
    • If you are upgrading from Lotus Connections 2.5 directly, please perform following post installation steps for Wikis SPR DARA7WTMJC ( Enable Wiki widget in Profiles causes an error. ) fixed in 2.5.0 fixpack 1:
      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.

    Defects fixed:


    APAR# SPR# Problem Description
    Activities
    AROK7YTJYL LO47375 Activity downloads open a new, blank, window
    AROK848J2J THSE83264A Fix for two issues with Quickr picker and QuickrJ 8.5 as well as a QuickD issue.
    CWUU83M55K LO49609 Quickr picker won't display in Hebrew locale
    DABS7YRREK LO47130 Activity node uuid be made available to the notification JSPs so that they can customize their mail messages
    DWIN7WFQVL LO46969 Un-handled exception when reading statistic files
    FLUU7XEPF4 File size restrictions
    MBAS7YHRJP LO46790 IE7 scrolls down when To-do list is selected.
    PDIK82XL7N LO49342 Activities API: To-do updates lose data when assignedTo and duedate are specified.
    SYEE829PYZ LO48472 When synchronizing users with the LDAP bad data (a user with duplicate data) causes a database error that needs to be handled
    TBEN83SR7D LO50833-A LO50849-B LO50856-C LO50896-D LO50932-P LO50958-HP LO50994-Search Dojo security patch affecting Dojo 1.1.1, 1.1.0 and 1.2.3
    WARE82XVMR LO48959 Create an entry in Activities and attach a file with the extension .eml (or .msg). Save - fails.
    Blogs
    DABS7YTKN5 LO47213 Provide weblog handle, entry ID and entry anchor attributes for Blogs email templates customization.
    DAMC7YXMFS LO47442 Default timezone does not match client machine's timezone when DST is enabled.
    DAMC83MJ5E LO49873 Language of Blog tab in Edit Community page does not change when user changes Connections UI language.
    DARA7YSRWM LO47314 To display comment author name in comment management page
    FYLI7XNJU4 LO47240 Editing the blog entries of other people
    GPRN82XQZ2 LO49153 Reset Hit count in Blogs resets the hit count in all of Connections
    JHUG7YHT5E LO47078 Blogs comment with spaces in Oracle
    JHUG7ZV3KX LO48722,
    LO50909
    Adding links using the Add Link button in a blog post does not work well.
    JHUG82BTQV LO51620 Blog and comment editor does not maintain line spaces in FF 3.5.7
    JHUG82H4S7 LO48802 Secure non secure message when accessing Blogs demo page from IE
    JSMI7YTQZF LO51620 Blank lines in blog RTE failed
    MHEG7YCUPB LO47111 The URL blogs/serviceconfigs is not protected when force authentication is turned on,
    TBEN83SR7D LO50833-A LO50849-B LO50856-C LO50896-D LO50932-P LO50958-HP LO50994-Search Dojo security patch affecting Dojo 1.1.1, 1.1.0 and 1.2.3
    XSHN83T4TU LO50438 Content cannot be removed in Edit mode in RTE in FF 3.5.
    YYCG7PZ8CX LO46877 Future published entry is displayed on HOMEPAGE.
    Core
    ASPR843EV3 LO50171,
    LO50222,
    LO50231,
    LO50281,
    LO50282,
    LO50628,
    LO50629
    Notifications sent by Lotus Connections cannot be configured to always be sent from a single global administrator email address without configuring the whole product to hide email addresses.
    ASRE83KPKC Configuration files allowing customers to customize certain aspects of the ACF.
    DABS7U2J36 LO47754,
    LO47747,
    LO47837,
    LO47838,
    LO47839,
    LO47840,
    LO47841,
    LO47842
    Language selector order is random and not the order specified in the config file.
    JHUG7ZV3KX The Dojo upgrade to version 1.2.3-20100127 is needed for two Blogs PMRs.
    TBEN83SR7D LO50833-A LO50849-B LO50856-C LO50896-D LO50932-P LO50958-HP LO50994-Search Dojo security patch affecting Dojo 1.1.1, 1.1.0 and 1.2.3
    Communities
    AKON7YXKF2 LO47631 Community name in forum notifications not being updated when title changes
    AKUR7YR6PU LO48088 The ATOM Generator that is used in Communities servlet needs this update, so that it can properly escape certain characters in the URL links in the ATOM Feed, when generating that ATOM Feed.
    ASRE7YSKX3 LO47214 XSS for community create and edit form validation errors
    CPRE826SBX LO49254 Double slash // used in URL requesting blank.gif when adding widget to communities bad url attempting to download blank.gif in communities when you click on customize.
    CWUU834JG5 LO46714 Communities pages contain URLs for internal cluster servers
    CWUU835QP9 LO48704 Change community member management to use invites.
    DAMC7YYL7K LO46968,
    LO46976,
    LO47035,
    LO47048,
    LO47059,
    LO47060,
    LO47070
    Community inline card will include images for community privacy
    JHET82HKJZ LO48499 All communities feed not returning restricted communities for super user
    JHET849PF6 LO50528 Two owners removing the same person lowers the member count twice
    JHUG7X7NGA LO47893 Honor forceConfidentialCommunications settings for URLs in Communities mail
    JHUG835VA3 Getting a mixed content warning when accessing the Community demo page.
    KRED82DEK9 LO48796 Mailing multiple owners using favorite mail client broken
    TBEN83SR7D LO50833-A LO50849-B LO50856-C LO50896-D LO50932-P LO50958-HP LO50994-Search Dojo security patch affecting Dojo 1.1.1, 1.1.0 AND 1.2.3
    LO49976 Leaving a restricted community may generate an AuthorizationException
    Discussion Forum
    CWUU82GLHB LO48264 A correct replies feed is returned when "if-modified-since" request header is set.
    EHET835TNK LO49356 When users aren't logged in, forum links will now work as intended.
    JHUG7X9TPW LO47920 Honor forceConfidentialCommunications settings for URLs in Discussion Forums notifications
    LCUN82BQ83 LO48628 LO49917 When synchronizing users with the LDAP bad data (a user with duplicate data) causes a database error that needs to be handled
    Bookmarks
    ASRE7YTKVU LO47921 XSS in "verbiage" variable.
    CWUU834TJN LO47429,LO47496,LO47501,LO47610,LO47642,LO47669 The bookmarklet pop-up is still using HTTP when force SSL is enabled.
    JHUG7X7NEA LO47918 Fix for Dogear mail notification by checking the forceConfidentialCommunication property in LCC.xml
    JHUG835VD5 When opening the demo page in HTTPS, IE6 will report a "secure/nonsecure" warning box.
    TBEN83SR7D LO50833-A LO50849-B LO50856-C LO50896-D LO50932-P LO50958-HP LO50994-Search Dojo security patch affecting Dojo 1.1.1, 1.1.0 AND 1.2.3
    XSHN7US5BB LO47950 Fix the bug in Bookmarks metrics
    Global Search
    DVYI842HQS LO50429 Search: Oops with Keyword wildcard search
    RFIH7YHMTG LO47471 Wrong locale being used to load languageware session.
    RFIH82WERP LO49374
    LO49375
    Term attribute missing for ACL category in search API
    Homepage
    ASPR82WSSS LO49250 When running HomepageMemberService.syncBatchMemberExtIdsByEmail() errors encountered for a given user in the batch input stop execution of the command against the remaining users.
    ASPR84SLXG LO51217 Unescaped strings causing JavaScript errors in administration page
    DVYI7ZWF9Z LO48325 Homepage: Links in Top Updates are going out as http even though forced SSL is enabled in lotus connections config.
    DVYI82KJMX LO48947 Homepage: widgets are not loading on second node
    DVYI83ELJB LO49654 Homepage: issue with language selector
    DVYI84GH9P LO50881 An empty <p> tag is causing a margin of 2 pixels at the top of the My Page page.
    TBEN83SR7D LO50833-A LO50849-B LO50856-C LO50896-D LO50932-P LO50958-HP LO50994-Search Dojo security patch affecting Dojo 1.1.1, 1.1.0 and 1.2.3
    Install
    CWUU834TPF LO48007 There are some exceptions thrown in command line when installing 2501 iFix with silent mode
    NKBI7ZZ6GV Application Security permissions reset after installing/uninstalling the iFix
    Mobile
    ASRE7YULWT LO47362 These changes fix two XSS issues in the mobile Blogs component.
    ASRE7YUMAB LO47948 This iFix updates the Mobile code to require NONCE values for all actions which modify data.
    ASRE83PPVH The changes cause the mobile edit actions to build a relative redirect url based on passed parameters rather than use a passed parameter directly for the redirect location. The intent of the change is to resolve a security vulnerability by ensuring that all links presented in the mobile pages are relative to the application server.
    News
    ASPR844JEW LO50508 News API usage can drive excessive load on the HOMEPAGE database due to the use of queries to determine feed pagination. This fix optimizes the code to not require these queries
    Plug-in - Microsoft Office
    ASPR84SLXG LO51217 Unescaped strings causing JavaScript errors in administration page
    Profiles
    ALEE7UF9KC LO48002 The business card appears in two languages.
    BOAI7YSMA LO49753 Allow Sametime awareness in Profile page
    BOAI7YSMAG LO47138 MS IE Hang when rendering the user profiles page
    BOAI82YNFJ LO49248,
    LO49837
    Missing font declaration for standalone business card
    BOAI835K8Z LO48424 Allow multiple versions of dojo on the page
    CWUU7ZU4QT LO47922 TDI: In certain cases sync process even though no data in the Profile ended up being changed. This does not harm the system but will result in slow sync_all_dns processes.
    CWUU834K48 LO46757 Adding support for LC 2.5 bizcard for QuickrJ 8.5
    CWUU83S699 LO49948 Error when creating an empty status message on Oracle
    CWUU84H4UV LO50571 Performance improvements for board queries
    DAMC826R8S LO48384 TDI: When the 'uid' column is mapped to a value other 'uid' then TDI tries to read the user to the Profiles DB multiple times.
    GAKI832KQC LO50233 Use of double quotes " " in Profiles breaks business card functionality
    GPRN7ZPHW3 When there are no attributes in the <contactInformation> the 'view-profile' page will fail to load
    GVRH84YB8V Fix to board regression due to iFix for performance. Issue only manifests when not using performance setting.
    JHUG7X7LQS LO47917 Profiles setting the source URL in the notification object to be http:// when forceConfidentialCommunications is true.
    JHUG7X7LQS LO50765 The board notification URL didn't honor the configuration for ssl enforcement defined in LCC.xml: <forceConfidentialCommunications enabled="true"/>
    JHUG7XBSJL LO47280 Earlier patch (LO46171) was incorrectly escaping rich text content as if it was text content. Added logic to respect difference between rich text and non-rich text attribute types.
    JHUG82H4QE Mixed content warning when accessing profiles demo page
    JHUG82HU3U LO48685 Long names wrap in report chain widget
    JMGE7ZEST7 LO47175 This is to support displaying search results by 'Last name' through configuration.
    JMGE7ZFKSL LO47749 When a tag is typed into the box, pressing Enter does not save the tag
    KRED82YDW3 LO49176 Layout bug in Connections Profiles Tags widget
    KRED838LHS LO49486 Photo cropper grows past picture frame when dragged to the edge in IE
    MAHN7VQLBJ LO46073 When the 'reader' role is mapped to all authenticated the ATOM API is broken.
    MHEG7YBT88 LO48367 The API call {profiles}/atom/search.do?organization=abc generates an exception.
    RAPA7SW596 LO47307 'resourceOwnerWidget' is not correctly supported by Profiles as specified in the information center: http://publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/index.jsp?topic=/com.ibm.connections.25.help/t_admin_profiles_develop_custom_widgets.html
    TBEN83SR7D LO50833-A LO50849-B LO50856-C LO50896-D LO50932-P LO50958-HP LO50994-Search Dojo security patch affecting Dojo 1.1.1, 1.1.0 and 1.2.3
    THSE7XVR5A IE js error on second attempt of biz card pop-up
    THSE7ZUKAG LO48964,
    LO49008,
    LO49011,
    LO49086,
    LO49094,
    LO49103,
    LO49148
    Do not initialize profiles/communities business card if profiles/communities is not enabled.
    VBUT7ZPH24 LO49581 Memory Leak with IE7
    XYCN83MEYR TDI: Fix populate_from_xml_file.bat script can't work on Oracle.
    XYCN83N3YB This iFix fixes the process_tds_changes script can't work because of the LDAP connector Return Attributes setting missing.
    Fix the log error that when Photo/Pronunciation table contains orphaned data.
    Files
    LMUN7XQJ26
    CMVC Defect: LO46241
    LO46241 Files login causes 100% CPU Usage.

    CPRE7YRJ8A
    CMVC Defect: LO47247
    LO47247 Header and footer URLs incorrectly displayed with HTTP instead of HTTPS when using a reverse proxy

    JMAK837L6N
    CMVC Defect: LO46889
    LO46889 User name not displayed correctly with apostrophe

    JMAK837M75
    CMVC Defect: LO46930
    LO46930 User cannot log-in to files due to If-Match comparison

    JMAK836T6X
    CMVC Defect: LO46584
    LO46584 Uploads longer than 20 minutes may fail.

    JBOD7W6FQ5
    CMVC Defect: LO46468
    LO46468 Interservice URLs not used when indexing file content

    JMAK837MNJ
    CMVC Defect: LO46830
    LO46830 Ampersands not properly encoded/decoded in files community widget

    DAMC7YSFZ3
    CMVC Defect: LO47294
    LO47294 Ampersand not properly displayed in Files upload message

    JMAK836SRW
    CMVC Defect: LO48104
    LO48104 Enable configurable language selection in the LotusConnections-config

    JMAK837Q5X
    CMVC Defect: LO47688
    LO47688 Third party search enablement for 2.5.x.x

    JMAK837N7G
    CMVC Defect: LO47296
    LO47296 Add image for private communities to Business Card
    TBEN83SR7D LO50833-A LO50849-B LO50856-C LO50896-D LO50932-P LO50958-HP LO50994-Search Dojo security patch affecting Dojo 1.1.1, 1.1.0 and 1.2.3
    Wikis
    BBEM7ZXKQP LO47923 See all entries link in recent posts, Widget wiki's tab does not work.
    TBEN83SR7D LO50833-A LO50849-B LO50856-C LO50896-D LO50932-P LO50958-HP LO50994-Search Dojo security patch affecting Dojo 1.1.1, 1.1.0 and 1.2.3
    BBEM7ZXKQP LO47923 See all entries link in recent posts, Widget wiki's tab does not work.
    JMAK836QTU
    CMVC Defect: LO46175
    LO46175

    Profile name with alias in search for wiki, returns no results
    AKUR7XPSXL
    CMVC Defect: LO46222
    LO46222 500 error when using API to get a page with attachment links
    JMAK836QYS
    CMVC Defect: LO46290
    LO46290
    Wiki redirected to Public Wikis page when anchor link selected
    EHET7Y4R26
    CMVC Defect: LO46737
    LO46737
    Name not displayed correctly with apostrophe in Wikis
    KRED7YDKCM
    CMVC Defect: LO46889
    LO46889
    User cannot log-in to wikis due to If-Match comparison
    BBEM7YEP3D
    CMVC Defect: LO46965
    LO46965
    Wiki redirected using fragment identifier
    JMAK836S98
    CMVC Defect: LO47527
    LO47527

    Moving wiki pages can fail for DB2 9.1 and Oracle 10
    JMAK836RZP
    CMVC Defect: LO47355
    LO47355
    Searching in wikis returns an "Oops!" error message
    SIBN7ZQFJN
    CMVC Defect: LO47848
    LO47848
    Back button in IE needs to be pressed twice after loading wikis.
    JMAK836SD9
    CMVC Defect: LO47847
    LO47847

    ID attribute is rewritten by href attribute in wiki editor
    KRED7ZPLJ7
    CMVC Defect: LO47888
    LO47888
    Wiki markup can become corrupted
    SIBN7ZQFJN
    CMVC Defect: LO47930
    LO47930
    IE does not recognize navigation changes for wikis immediately after login
    JMAK836SRW
    CMVC Defect: LO48107
    LO48107
    Enable configurable language selection in the LotusConnections-config
    BHAM7Y7KWH
    CMVC Defect: LO46691
    LO46691
    Tag count is incorrect when using Oracle
    APEE7YJNKC
    CMVC Defect: LO47029
    LO47029
    Wikis seedlist is omitting certain data
    JMAK837QA8
    CMVC Defect: LO47688
    LO47688
    Third party search enablement for 2.5.x.x
    JMAK836T3J
    CMVC Defect: LO47297
    LO47297 Add image for private communities to Business Card

    Prerequisite information:


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

    Instal

    lation instructions for a single-node (stand-alone deployment):
    1. Back up all customization files that you have used with Lotus Connections 2.5.0 or 2.5.0.1.
    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 2 package from IBM Fix Central (ID: 2.5.0.2-LC-Multi-FP000002), 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 LC2502_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 LC2502_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 LC2502_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. Clear out all of the WebSphere's temp directory, typically located at: C:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp\
    8. Restart all applications servers.
    9. 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: appserver.serverhostname.com:9080/activities

      You can also check the logs. One log is created for each feature installed. The files are named <date>_LC2502_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
    10. Start the IBM HTTP Server if you stopped it .
    11. Access the features using their public Web addresses. Click the About links for each feature to ensure that the correct build number is displayed.
    12. 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.

    Install

    ation instructions for a network environment (cluster deployment):
    Use the update installer to install this fix pack, which updates Lotus Connections 2.5.0 or 2.5.0.1 to a version 2.5.0 fix pack 2 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 2 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 2 package (ID: 2.5.0.2-LC-Multi-FP000002) 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 LC2502_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 LC2502_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 LC2502_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. Clear out all of the WebSphere's temp directory, typically located at: C:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp\
    11. Restart all applications servers.
    12. 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:

      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>_LC2502_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
    13. Start the IBM HTTP Server if you stopped it.
    14. 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.
    15. 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.

    Rate this page:

    (0 users)Average rating

    Add comments

    Document information


    More support for:

    IBM Connections

    Software version:

    2.5, 2.5.0.1

    Operating system(s):

    AIX, Linux, Linux zSeries, Mac OS X, Windows

    Reference #:

    1431472

    Modified date:

    2010-06-25

    Translate my page

    Machine Translation

    Content navigation