IBM WebSphere Presence Server, Version 7.0 FixPack 2 Readme

© Copyright International Business Machines Corporation 2009, 2012. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

 

About this fix pack

This fix pack applies to the IBM® WebSphere® Presence Server version 7.0 base product or Fixpack 1.

IBM® WebSphere® Presence Server version 7.0 Fixpack 2

fixpack includes the following features:

  • Publish Expiration Configuration

    • The publish expiration configuration has been extended to include an in-memory publish option. that is suitable only for transient presence data that expires in a very short time (for example in less than 30 seconds). To enable the in-memory publish option, add the "enableInMemoryProcessing" parameter to the Presence Server system configuration as shown below:

      publishExpiration default="60" maximum="144000" minimum="1" enableInMemoryProcessing="true"

    • If the in-memory publish is enabled, then Presence Server accepts the publish messages which have an expiry period between 1 second and the minimum expiry(set to 1 minute in the above example) and processes them in-memory. For all in-memory publish operations, the current set of subscribers receive a notification. Note the following details for in-memory publish operations:
      • The presence document is not persisted into the PUBLISH table and FULLDOC table. So only the current subscribers receive a notification
      • Presence fetch is not supported with in-memory publish operation
      • Empty initial notifications are sent out for publishers subscribing to only in-memory publish operations
      • Refresh publish or unpublish operations are not supported on top of in-memory publish operation

      The following configuration options are recommended when the in-memory publish is enabled:

      • Use the following value for an in-memory publish operation. If not, an empty notification is sent out.    documentChangeJMS includeFullDocument="true"
      • Disable throttling, when subscribing to presentities that use in-memory publish option with very short duration. If throttling is enabled, the notification might expire before the throttling interval. Throttling can be disabled for each subscription by using the event header as follows: Event: presence;throttle=0 where "presence" is the event type, which can be replaced by the current event type

  • Publish Timer Configuration

    The publish timer configuration has been extended as follows:

    publishTimer interval="15" maxRecords="15000" deleteBatchSize="0"

    The changes are described below:

    • The minimum acceptable value of publish timer interval is changed from 60 seconds to 15 seconds.
    • A new attribute called "maxRecords" is added to the publish timer. This attribute specifies the maximum number of records that are cleaned up during any iteration of the publish cleaner task. Suggested value is maximum inbound publish operations per second multiplied by the publish timer interval. For example, if the peak throughput expected is 1000 publishes per second and the interval is set to 15 seconds, then the "maxRecords" value should be set to 15000.
    • A new attribute called the "deleteBatchSize" is added to the publish timer. This attribute determines the size of a JDBC batch size when update SQL operations are performed on the FULLDOC table and resulting notifications are sent out during a cleanup operation on the PUBLISH table. Recommended value is 0. Allowed values are between 20 to 5000.

  • Presence Server Initialization

    • The delay in Presence Server initialization has been reduced.

  • Logs and traces

    • Publish and FullDoc cleanup start and end timestamp details are logged into the trace file when the tracing level is set to FINE.
    • Statements are added to the log file to capture the details of the record that failed with unique constraints. The records are identified with the respective presenceId and presenceType

    Fix and update history

    This fix pack includes the following fixes and APARs.

    Interim Fix 001

    ·         APAR LI75945 - Supports MWI events in REST API

     Note: An additional 'Event' header has been added to HTTP requests to allow clients to specify a desired event package. If the request does not have an 'Event' header, Presence Server interprets that the request is for 'presence'.

    Interim Fix 002

    ·         APAR LI76033 - Maintains the event type in GET request instead of using the default presence event type

    ·         APAR LI76042 - Returns "404 Not Found" response instead of "200 OK" response when the document is not found using the GET request in REST API

    Interim Fix 003

    ·         APAR LI76166 - Provides an alternative algorithm for entity tag generation

     Note: A new system configuration attribute <customEtagGenerator enable="true"/> has been added to the SystemConfiguration.xml file to enable the new algorithm for entity tag generation. If this attribute is set to false, Presence Server keeps generating the entity tag as before.

    Interim Fix 004

    ·         APAR LI76170 - Configures Presence Server behavior when a publish expires

     Note: A new system configuration attribute <notifyOnExpiredDocument enable="true"/> has been added to the SystemConfiguration.xml file to enable Presence Server to send notifications on expired documents. If this attribute is set to false, Presence Server suppresses the notifications. The default value is true.

     It is recommended to modify the following system configuration attributes in the SystemConfiguration.xml file:
    ·         <fullDocTimer interval="60"/> can be added to the SystemConfiguration.xml file to edit the default clean-up time interval to remove expired elements from the FULLDOC table. It is recommended to decrease the clean-up time interval and adjust it according to the expiry time. The value should be set in minutes. If this attribute is not set, Presence Server cleans up the FULLDOC table once in 60 minutes.
    ·         <documentCache enable="true"/> can be set to false to disable cache in Presence Server. The default value is true.

    Interim Fix 005

    ·         APAR LI76249 - Sends out duplicate notifications when one of the servers goes down

     Note: A new system configuration attribute <notifyActivatedSesssions enable="true"/> has been added to the SystemConfiguration.xml file to enable Presence Server to send notifications on activated subscriptions. If this attribute is set to false, Presence Server suppresses the notifications. The default value is true.

    ·         APAR LI76289 - Escapes XML reserved characters on presence documents generation

    Interim Fix 006

    ·         APAR LI76487 - Provides the fix for NullPointerException when handling expired published data

    Interim Fix 007

    ·         APAR LI76514 - Resolves performance issue with MWI initial publish

    ·         APAR LI76516 - Database optimization: Provides cluster-level EJB timer settings for FULLDOC table cleanup

    Interim Fix 008

    ·         APAR LI76614 - Provides the fix for NullPointerException in FULLDOC ejbTimer.

    ·         APAR LI76627 - Enhances Presence Server performance with Oracle database, when running at high TPS rate.

    ·         APAR LI76687 - (a) Provides in-memory publish option for presence events with short expiry period. (b) Supports batch update operation to work with DB2 database

    Software compatibility

    The supported software products and version numbers for WebSphere Presence Server are documented in the Information Center. This fix pack runs with the same software except as noted below:

    ·         Operating Systems: Same as Presence Server version 7.0.0.1

    ·         Application Server: This fix pack has been tested on WebSphere Application Server Fix Packs 6.1.0.23 and 7.0.0.21.

    ·         Java™: Same as Presence Server version 7.0.0.1

    ·         Databases: Same as Presence Server version 7.0.0.1 

    Installation requirement

    Hardware requirements

    Hardware requirements for Presence Server are included in the Information Center and have not changed since version 7.0.0.1. For more information, see Hardware requirements.

    Software requirements

    Software requirements for Presence Server are included in the Information Center. For more information, see Software requirements.

    Required fixes for WebSphere Application Server Network Deployment (WAS)

    Before installing this fix pack, ensure that the following fixes have been installed for the WAS version:

    Required iFixes when installing the fix pack on systems running WAS version 6.1.0.23:

    APAR

    File Name

    PK89010

    6.1.0.23-WS-WAS-IFPK89010.pak

    PK91317

    6.1.0.23-WS-WAS-IFPK91317.pak

    Required iFixes when installing the fix pack on systems running WAS version 7.0.0.9:

    APAR

    File Name

    PM13895

    7.0.0.9-WS-WAS-IFPM13895.pak

    PM13932

    7.0.0.7-WS-WAS-IFPM13932.pak

    Installation instructions

    Before you begin, ensure that:

    ·         IBM WebSphere Presence Server version 7.0 Fix Pack 1 is installed.

    ·         IBM WebSphere WebSphere Application Server (WAS) version 6.1.0.23 or 7.0.0.21 is installed along with the appropriate fixes.

    ·         WAS Update Installer 6.1 or 7.0 is installed on the application server.

    ·         WebSphere software for Telecom Update Installer plug-in is installed on the WAS Update Installer.
    Note: If, after applying the WebSphere software for Telecom Update Installer plug-in, you upgraded or installed a new version of the WAS Update Installer (UPDI), you will have to run a reset script before you apply this fix pack. You can download the reset script from the IBM Support download site. For details, see WebSphere software for Telecom Update Installer.

    ·         You are logged in to the operating system as the actual root user in a UNIX® environment.  

    To apply the fix pack, complete the following steps:

    1.      Download the Presence Server update installer package 7.0.0.2-WS-WAS-IMS-Presence-Server-FP000002.pak into the was_root/updateInstaller/maintenance directory.
    Note: If you are updating a cluster, you must perform this step on every node in the cluster.

    2.      Start the update installer as described by WebSphere and select the Presence Server fix pack to be installed. The update installer will update the was_root/installableApps/presence directory with the IBMWebSpherePresenceServer.ear file.

    3.      Start WebSphere Application Server where Presence Server is installed.

    4.      Open the Integrated Solutions Console and log in.

    5.      Click Applications >Application Types >WebSphere Enterprise Applications.
    Note: If you are using WebSphere Application Server version 6.1.0.23, click Applications >Enterprise Applications.

    6.      Select the check box for the Presence Server application and click Update.

    7.      Click Browse to search for the IBMWebSpherePresenceServer.ear file.

    8.      Select the was_root /installableApps/presence/IBMWebSpherePresenceServer.ear file.

    9.      Click Next on the following screens, and click Finish in the summary screen.

    10.  Save the changes.

    11.  Click Applications > Application Types > WebSphere Enterprise Applications > Presence Server > Environment Entries for Web Modules. Update the first entry (Presence Server Address) with the host name and port number of the appropriate SIP Proxy server.

    12.  Restart the deployment manager, node agents, and application servers. For more information, see Stopping and starting the server.

    Updates, limitations, and known problems

    Updates, limitations, and known problems about Presence Server are documented in technotes on the IBM Software Support website:

    http://www.ibm.com/software/pervasive/presenceserver/support/

    As limitations and problems are discovered and resolved, the IBM Software Support team updates the knowledge base. By searching the knowledge base, you can quickly find workarounds or solutions to problems that you experience. Each of the following links launches a customized query of the live Support knowledge base. To create your own query, go to the Advanced search page.

    Trademarks

    The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: IBM, WebSphere.

    UNIX is a registered trademark of The Open Group in the United States and other countries.

    Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States , other countries, or both.

    Other company, product, or service names may be trademarks or service marks of others.