Unified CCMP 8.5(x) - Integration

From DocWiki

Revision as of 23:13, 18 May 2012 by Hoturner (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search



The intention of this section is to call out the two main interfaces that CCMP uses to import data from and provision items in Unified CCE: ConAPI and AXL.

UCCE/ICM Integration

Once you have your CCMP servers built & ready to be integrated into a UCCE solution, you need configure the ConAPI link between Unified CCMP and Unified CCE. This is performed initially on the Unified CCE Primary HDS AW.


- What is ConAPI and CMS? - We will cover what ConAPI/CMS is & how it operates.

CUCM Integration

Connectivity to CUCM is done through AXL. Unified CCMP communicates with the CUCM Publisher over TCP 8443 to read from (Data Importer Service) and write to (Provisioning Service) the CUCM database. The specific methods within AXL that CCMP uses are the executeSQLQuery and executeSQLUpdate methods. Before Unified CCMP 8.0 we used the specific get methods (e.g. getPhone) available in AXL however this proved to be expensive in terms of processing overhead. Using just these two methods means that we only have to handle the data we need thus making reads/updates much faster into CUCM.

Of these two methods only executeSQLUpdate is throttled in CUCM. This throttle limits the total number of changes to 1500 transactions per minute and cannot be changed.


While not strictly necessary to support Unified CCMP, the following links provide you with detailed description of both AXL and its operation. Once reviewed you should have enough of an understanding to troubleshoot issues arising from AXL.

  • Learn Administrative AXL - This PowerPoint slide deck provides a fairly deep dive coverage of AXL and the Direct Database Access (executeSQLQuery and executeSQLUpdate) methods employed by Unified CCMP to provision & import configuration from CUCM.

Rating: 5.0/5 (1 vote cast)

Personal tools