WebSphere brand IBM WebSphere XML Document Management Server, Version 7.0

Introducing the IBM WebSphere XML Document Management Server Component

The IBM® WebSphere® XML Document Management Server Component (XDMS) provides storage, management and subscription to documents that are owned by entities within your IMS-based solution.

IBM XDMS is based on the Open Mobile Alliance (OMA) standards for the OMA XDM v2.0 specification. The OMA XDMS specification defines the use of two IETF-based network specifications for interaction with the XDMS:
XML Configuration Access Protocol (XCAP)
XCAP protocol is used to retrieve, delete, and manipulate XML documents over HTTP.
Session Initiation Protocol (SIP)
SIP allows clients to subscribe and receive notifications when a document is added, deleted, or updated.
The following figure illustrates the way in which data flows through the IBM XDMS product.
Figure 1. Data flow through the IBM XDMS productIBM XDMS solution high level overview, showing data flows and deployed applications
The following figure illustrates the way in which IBM XDMS components interact with each other. In this example, separate enablers are deployed for SharedList XDMS and Presence Rules. Additional enablers can be added as well.
Interactions among IBM XDMS components, showing an example in which two enablers are deployed: SharedList XDMS and Presence Rules
OMA 2.0 enablers are provided that enable applications to store XML content based on the application usages as described for IBM XDMS:

An Aggregation Proxy is provided to route requests based on the application usage to the corresponding IBM XDMS enablers. It can also aggregate capabilities and directory information from multiple IBM XDMS enablers. The Aggregation Proxy is considered the client facing service that is a single point of entry to access all IBM XDMS enablers.

The XDM client authenticates by means of digest authentication against the Aggregation Proxy (HTTP) and the IMS Core (SIP). (In digest authentication, encryption is used so that a user's credentials can be established without the need to transmit a password in plaintext over the network.) Asserted identities are then used to forward requests with the identities within the trusted environment. The Aggregation Proxy can be configured to forward requests to an external aggregation proxy. The external aggregation proxy is simply treated as another enabler

The IBM XDMS product can be customized through the development of custom XDMS enablers allowing third parties to develop custom code that provide constraints for specific needs. Additionally, system administrators are given highly-granular control of enablers through configurable properties. This flexibility allows the IBM XDMS to be tailored for the specific needs required in various telecommunication environments.

Digest authentication using a WebSphere Trust Association Interceptor (TAI) and standard support for Transport Layer Security (TLS) are provided to enhance security when accessing the Aggregation Proxy.




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