Basic routing uses the list of IBM® XDMS enablers configured in the resource environment providers to route requests to specific Application Unique Identity Descriptors (AUIDs).
The Aggregation Proxy provides a single point of entry to access multiple IBM XDMS enablers that are configured in the backend. Therefore, it can be considered to have the superset of capabilities for all IBM XDMS enablers. This simplifies the client configuration in that all XML Configuration Access Protocol (XCAP) communication is sent to a single entity, which is the Aggregation Proxy.
During the installation and configuration of the Aggregation Proxy, the list of IBM XDMS enablers is configured in the Resource Environment Provider (REP) property called XDMS_URI. The list must contain a unique set of IBM XDMS enablers in that no two XDMS enablers can support the same AUID (except for two common AUIDs, xcap-caps and org.openmobilealliance.xcap-directory, which all IBM XDMS enablers must implement). This is required so that for each AUID, there is a unique route to a specific IBM XDMS enabler. If two IBM XDMS enablers are defined to support the same AUID, then the Aggregation Proxy cannot determine which IBM XDMS enabler to forward requests to. The AUID, therefore, is rendered unserviceable.
Typically, the IBM XDMS enablers in the backend are secured by a firewall and should be considered trusted. However, if higher security is required and HTTPS is enabled for the IBM XDMS enablers, then you can set the REP property HTTPS_PROXY_XDMS to true, which indicates the use of encryption. Then, instead of defining your list of IBM XDMS enablers in the REP property XDMS_URI, define the list of XDMS enablers in the REP property XDMS_URI_HTTPS.
Optionally, the advanced routing topic discusses usage of domain partitioning to support multiple XDMS enablers with the same AUID but separated by domain. This allows the segregation of certain client populations to be routed to a specific IBM XDMS enabler for a specific domain. See the topic Advanced Aggregation Proxy routing for more information.
The following Aggregation Proxy REP configuration is used for the examples in this topic: