Advanced routing uses domain partitioning and matching to determine the routing of XCAP requests.
Basic routing is simply based on the Application Unique Identity Descriptor (AUID) in order to determine the unique IBM® XDMS enabler that the request is routed to. However, there may be situations where the user population is too large for a single IBM XDMS enabler to support or where there are security requirements to partition the users. Therefore, besides defining the default IBM XDMS enablers, an administrator may choose to define additional IBM XDMS enablers that support the same AUID but for different domains.
During the installation and configuration of the Aggregation Proxy, the list of IBM XDMS enablers for a specific domain is configured in the Resource Environment Provider (REP) property XDMS_URI!<domain> where the <domain> portion of the name defines the domain for which the list of IBM XDMS enablers is supported. The implication here is that two IBM XDMS enablers supporting the same AUID can be defined in the Aggregation Proxy if they reside in different domains. If for each AUID and domain combination, the request matches only one IBM XDMS enabler, then there is no ambiguity in routing.
The portion of the request that is used for domain matching is found in the XML Configuration Access Protocol (XCAP) User Identifier (XUI). The XUI is typically a URI such as a Session Initiation Protocol (SIP) URI. The URI may contain a domain which is parsed and then used to match on the appropriately configured XDMS enabler to route the request to. Matching is done first by the most qualified domain towards least qualified. If no domain is matched, then the default XDMS enabler is used as specified during basic routing configuration. If the XCAP request is for a global document (no XUI), then no domain is specified and consequently the request is routed to the default XDMS.
These examples illustrate the various routes given the domain and AUID matching done by the Aggregation Proxy.
The SharedList IBM XDMS enablers sharedlist1.com and sharedlist2.com both support the AUID resource-lists. The PresenceRules IBM XDMS enabler presrules1.com supports the AUID org.openmobilealliance.pres-rules.
The Aggregation Proxy routes to the domain us.example.com because it matches the XUI in the request.
The Aggregation Proxy routes to the us.example.com domain because it most closely matches the XUI in the request.
The Aggregation Proxy routes all global requests to the default XCAP URI.