<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Reporting API .Net client environment info</title>
  <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id=" />
  <subtitle>Reporting API .Net client environment info</subtitle>
  <id>http://developer.cisco.com/c/message_boards/find_recent_posts?p_l_id=</id>
  <updated>2013-05-20T20:22:23Z</updated>
  <dc:date>2013-05-20T20:22:23Z</dc:date>
  <entry>
    <title>RE: WSDL import fails</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=4324147" />
    <author>
      <name>Arpit Desai</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=4324147</id>
    <updated>2011-08-05T15:58:38Z</updated>
    <published>2011-08-05T15:58:38Z</published>
    <summary type="html">Reporting API support Java 1.5 and Axis 1.3 version. Please use compatible environment. Also, these questions are implementation details and should be worked out at client end.
 
[quote]In the API reference a WSDL file is included. I have copied and pasted this and I can confirm that I can create Java stubs from it using Axis 1.4. However I would prefer to use an IDE to develop with ¿ I currently have Netbeans 7.0.1 on my PC. The API reference suggests importing the WSDL into an IDE such as this should be possible ¿ however it fails when I attempt this. I¿ve taken a screenshot which shows the error messages I am seeing.  Any ideas on what the issue could be?[/quote]</summary>
    <dc:creator>Arpit Desai</dc:creator>
    <dc:date>2011-08-05T15:58:38Z</dc:date>
  </entry>
  <entry>
    <title>RE: Clarity on initializing the API</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=4322730" />
    <author>
      <name>Arpit Desai</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=4322730</id>
    <updated>2011-08-04T21:22:12Z</updated>
    <published>2011-08-04T21:22:12Z</published>
    <summary type="html">Reporting API document clearly states that CTS Man authenticates using Basic Authentication scheme. This is widely used scheme in Web-service world. 

You can refer to the sample client to find more details 
http://developer.cisco.com/web/tra/wikidocs/-/wiki/Main/Sample+Code</summary>
    <dc:creator>Arpit Desai</dc:creator>
    <dc:date>2011-08-04T21:22:12Z</dc:date>
  </entry>
  <entry>
    <title>RE: Clarity on Java Libraries</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=4322727" />
    <author>
      <name>Arpit Desai</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=4322727</id>
    <updated>2011-08-04T21:20:02Z</updated>
    <published>2011-08-04T21:20:02Z</published>
    <summary type="html">The client libraries listed in the document are what are required for a normal client. You can refer to sample client code for more details
http://developer.cisco.com/web/tra/wikidocs/-/wiki/Main/Sample+Code

You can bring in these libraries from any source JDK or Axis.</summary>
    <dc:creator>Arpit Desai</dc:creator>
    <dc:date>2011-08-04T21:20:02Z</dc:date>
  </entry>
  <entry>
    <title>RE: Sample Code</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=4322702" />
    <author>
      <name>Arpit Desai</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=4322702</id>
    <updated>2011-08-04T21:16:02Z</updated>
    <published>2011-08-04T21:16:02Z</published>
    <summary type="html">Hello Brian,

Please find the link to sample client code for accessing CTS Manager Reporting APIs. 
http://developer.cisco.com/web/tra/wikidocs/-/wiki/Main/Sample+Code

We do not provide any Front End code. This is a way to access the Reporting APIs programmatically. It is upto individual developers to create Front Ends using the data that is fetched from Reporting APIs

Thanks,
- Arpit</summary>
    <dc:creator>Arpit Desai</dc:creator>
    <dc:date>2011-08-04T21:16:02Z</dc:date>
  </entry>
  <entry>
    <title>Mailbox Account Required for CTS Man Reporting API user</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=3333519" />
    <author>
      <name>Arpit Desai</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=3333519</id>
    <updated>2011-03-28T21:57:56Z</updated>
    <published>2011-03-28T21:57:56Z</published>
    <summary type="html">Due to the security / authentication module being used by CTS Manager, the system requires the Reporting API user to be provisioned with a valid Mailbox on the Calendar Server (Exchange/ Domino).
 
CTS Man will never send any emails to this mailbox</summary>
    <dc:creator>Arpit Desai</dc:creator>
    <dc:date>2011-03-28T21:57:56Z</dc:date>
  </entry>
  <entry>
    <title>Reporting API .Net client environment info</title>
    <link rel="alternate" href="http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=3333492" />
    <author>
      <name>Arpit Desai</name>
    </author>
    <id>http://developer.cisco.com/c/message_boards/find_message?p_l_id=&amp;messageId=3333492</id>
    <updated>2011-03-28T21:51:48Z</updated>
    <published>2011-03-28T21:51:48Z</published>
    <summary type="html">One of our customers have tried to consume CTS Man reporting APIs through .NET platform and faced some security challenges. 
 
It was identified in our testing and integration efforts that Reporting APIs can be accessed through a .NET based client by leveraging WCF standards. 
 
Due to the limitations of WCF security standards it is recommended to use .NET framework 4.0 and above to consume Reporting Web services from CTS Manager. 
 
Also, when client uses https instead of http, CTS Manager self signs its own certificates and sends to the client over ssl. In order for the client to proceed furthere it must accept this certificate blindly. 
 
Hope this information helps other customers who wish to leverage .NET platform for their client applications.</summary>
    <dc:creator>Arpit Desai</dc:creator>
    <dc:date>2011-03-28T21:51:48Z</dc:date>
  </entry>
</feed>

