Custom applications

Connect Enterprise Web Services provides an XML API, so your application must be able to communicate with Enterprise Server or Enterprise Hosted using XML over HTTP or XML over HTTPS. Your application calls the API by building a request URL and passing it one or more parameters, either as name/value pairs or as an XML document. Web Services returns an XML response, from which you can extract values.

Custom applications retrieve metadata from the Connect Enterprise database. Metadata includes meeting or course names and times, meeting room URLs, content URLs, and report information.

The data flow for a custom application retrieving metadata from the database is from a client web browser, to the client web application server, to the XML API, the Connect Enterprise web application server, and the SQL database--and then back again.

The data flow between a custom application and Connect Enterprise works like this:

A user accesses your custom application from a web browser.
The application calls the XML API over HTTP:80 or HTTPS:443.
The Connect Enterprise web application server authorizes the application and its users, retrieves metadata from the SQL database, and returns the metadata.
On the client side, your web or application server, XML parser, and software libraries handle the response and return it to your application.
The user continues to work in your custom application, and clicks a meeting or content URL. At this point, the user accesses a Connect Enterprise application, such as Acrobat Connect Professional to enter a meeting room, and the typical data flow between a Connect Enterprise application and the server begins.

Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/breeze/6/xml_api/01_usin3.htm