WebSphere brand IBM WebSphere Presence Server, Version 7.0

What's new in Presence Server version 7.0

IBM® WebSphere® Presence Server version 7.0 includes new functionality.

Notification throttling

Presence Server implements the notification throttling mechanism as specified in IETF draft-niemi-sipping-event-throttle-06. This feature can help improve performance by limiting the rate of SIP event notifications for one or more event packages.

Presence Server REST interface

Presence Server exposes a representational state transfer (REST) interface for presence operations over HTTP, allowing for fetch and publish presence operations using a Web client.

The REST interface permits Web clients to perform HTTP GET, PUT, POST, and DELETE requests.

With this feature it is possible for SIP clients and clients that use the REST interface to operate together, when all of the clients are connected to the same server. In particular, presence authorization rules are respected and applied both for fetch operations by HTTP clients and for information published by HTTP clients.

Public identity mapping

Using public identity mapping, Presence Server can tie together presence information from disparate sources that relate to the same person or presentity but use different, non-correlated identifiers. With identity mapping, presence information from different IDs for the same user are presented as a single aggregated presence document. When a subscriber subscribes to any one of these identities, the subscriber receives the aggregated document.

Support for local lists

To facilitate integration with the IBM XDMS product, Presence Server supports the use of <rls-services> documents–in particular, local lists in RLS services documents, as specified in RFC 4826.

Subscriber based partitioning and RLS (Presence Server entry point)

The Presence Server entry point provides ways for handling incoming PUBLISH and SUBSCRIBES more efficiently.

You can deploy several Presence Server clusters, each of which handles SIP requests for a specified subset of users. This facilitates scaling so that you can support a large number of users. Presence Server contains a routing component that routes each request to the correct cluster.

You can also designate a separate resource list server (RLS) component to handle all subscriptions on Presence lists, as described in the standard OMA-TS-Presence_SIMPLE-V1_1-20080627-A, chapter 5.5. This use of the RLS is designed to reduce network traffic and improve performance by reducing the number of subscriptions that have to be established between the RLS cluster and the Presence Server clusters.

Presence data model

Presence Server conforms to the Presence data model as specified in RFC 4479. The data model stipulates that each presentity should have only one document, and–if possible–each document should have only one <person> element. It also stipulates that the watcher, not the presence composer, should resolve ambiguities when merging information from multiple sources.

Content indirection

Presence Server supports content indirection as described in RFC 4483, allowing a SIP message to contain an indirect reference to the desired content. The receiving party then uses this indirect reference to retrieve the content by means of a non-SIP transfer channel such as HTTP. An alternative transport mechanism is provided for SIP body parts.

Interactive installation

A simplified, interactive process is provided for installing the Presence Server product. The installation package supports silent installation using a response file, and it can also be used for uninstalling and reinstalling the product. The installation package can be used for all of the supported hardware topologies.




Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.