Getting Started with AXL and Java

Version 1
    This document was generated from CDN thread

    Created by: Rocco Prielipp on 20-06-2011 07:29:18 AM
    hello,
     
    the topic axl ist very new for me and i dont know where ti begin. Does anyone have an good idea hwo to write or get a simple example, for example getting a username?
     
    greets

    Subject: RE: Getting Started with AXL and Java
    Replied by: Axel Schemberg on 21-06-2011 03:30:58 AM
    Hi,
     
    may be this is a point where you can start: http://www.pcnetzwerke.de/cisco-callmanager/cucm-axl-api.html
    If you find any issues or have suggestions, don't hesitate to tell me.
     
    Greetings
     
    Axel

    Subject: RE: Getting Started with AXL and Java
    Replied by: Gordon Ross on 21-06-2011 03:56:51 AM
    I had a quick look at your page. In it, you say that you're going to describe the parse-as-string and full-WSDL options, and ignoring the XML approach.

    A couple of thoughts.

    I've tried many times to get the "proper" WSDL/SOAP solution working with Java. However, I could never get the WSDLs to work with Apache AXIS (either V1 or V2) From what I've glanced on the forums, people seem to have more luck with other languages and the WSDL approach.

    I have to confess, that I'm not a great fan of the "Parse XML as string" approach - but do what you're happy with.

    I use the XML approach - but not for the every SOAP call. I've written a little library which is hard coded to parse the executeSQL (& updateSQL) SOAP calls. My executeSQL parse takes the SQL SELECT result and turns it into a List<HashMap<String, String>> (so each row is a HashMap<String, String>, and the result set is a List of these HashMaps)

    I find there are several advantages to this.

    Firstly, you can be more specific about the data that is returned. By restricting the data that is returned, your app becomes much more efficient in terms of database access.

    Secondly, you can implement API calls that Cisco don't provide via the official SOAP interface. After having a (very) quick look at the SOAP APIs, it seems they are modeled on the CCMADMIN user interface. All well and good. But really, you probably want to do things that aren't in the CCMADMIN interface. By using the native database tables, you can get much more power and performance out of the sysem.

    GTG

    Subject: RE: Getting Started with AXL and Java
    Replied by: Florian Kroessbacher on 21-06-2011 04:03:10 AM
    Hy Gordon!

    is it possible to share the "little library"

    thnxs

    Subject: RE: Getting Started with AXL and Java
    Replied by: Axel Schemberg on 21-06-2011 04:57:39 AM
    Hi Gordon,
     
    you are absolutly right. Using the String approach has a lot of disadvantages. But if you are not too familar with XML, SOAP etc I think it is very easy to understand starting with strings. From that point you can achieve the xml approach ... if you are familar with.
    If I find enough time I will continue the page. You are welcome to send me a text and I will put it on the page.
     
    Kind regards
     
    Axel

    Subject: RE: Getting Started with AXL and Java
    Replied by: Johannes Krohn on 21-06-2011 05:49:51 AM
    You might want to try the "Using AXL via WSDL and Java,Axis - Wiki" how-to article in the Wiki section. The presentation referenced there explains how to create Java classes using Axis 1.4.
    http://developer.cisco.com/web/axl/wikidocs?p_p_id=1_WAR_wikinavigationportlet_INSTANCE_i9JW&p_p_lifecycle=0&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_count=1&p_r_p_185834411_nodeId=803208&p_r_p_185834411_title=Using+AXL+via+WSDL+and+Java%2cAxis

    Subject: RE: Getting Started with AXL and Java
    Replied by: Rocco Prielipp on 22-06-2011 07:39:39 AM
    thanks for the posts, they helped me a little bit.

    now my problem is, that when we want to update a user we do this with a csv file and a template. (Bulk Administration --> Users --> Update Users)
    then check "Run Immediately" und push submit.

    This process should be done by via the axl api, but i found no function to export the template. does there exist an otherway to solve this?

    greetings