AXL-Serviceability API Best practice ?

Version 1
    This document was generated from CDN thread

    Created by: Joe Rossi on 13-04-2009 07:23:04 PM
    Hi,
    I am looking at the 7.0(1) Cisco Unified Communications Manager XML Developer Guide at:
        http://developer.cisco.com/c/document_library/get_file?folderId=192390&name=DLFE-11526.pdf&redirect=http%3A%2F%2Fdeveloper.cisco.com%2Fweb%2Faxl%2Fdocs%3Fp_p_id%3Ddoc_library_summary_portlet_WAR_doclibrarysummaryportlet_INSTANCE_DXka%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-1%26p_p_col_count%3D3
    There is a section "AXL Serviceability Application Design Guidelines and Best Practices".
    In it, it states:
        Number of Nodes in the cluster
        In large cluster, configure your application to point SOAP clients to individual servers that have server specific Perfmon counters.
    There is a lot of leeway, but what it implies to me is that, for larger clusters, I should gather perfmon stats directly from the
    subscribers instead of getting them all from the publisher. This also implies the AXL Web Service needs to be running on each subscriber.
    Is this Cisco's best practice for ALL version of UCM (i.e. 3.3 - 7.0), of is this something new for UCM 7.0 only.
    The UCM 7.0 help for service activation states: "Cisco AXL Web Service - Activate on the first node only. Failing to activate this service causes the inability to update Cisco Unified Communications Manager from client-based applications that use AXL."
    A clear contradiction to what they tell developers.