Template:Main Developer: Difference between revisions
From Open-Xchange
(No development setup for backend supported any more) |
(Move to https://documentation.open-xchange.com/) |
||
| Line 1: | Line 1: | ||
=== Interfaces === | === Interfaces === | ||
* The [ | * The [https://documentation.open-xchange.com/ HTTP API] is used by the new AJAX GUI. It consists mainly of messages in JavaScript Object Notation ([http://json.org JSON]) sent over HTTP. | ||
* Provisioning API to access the Open-Xchange Admin Daemon | * Provisioning API to access the Open-Xchange Admin Daemon | ||
** The [http://java.sun.com/javase/technologies/core/basic/rmi/index.jsp RMI] API is used for data provisioning of Contexts, Users, Groups and Resources as well as for configuring Databases, Filestores and OX Servers. It is currently split into two parts, | ** The [http://java.sun.com/javase/technologies/core/basic/rmi/index.jsp RMI] API is used for data provisioning of Contexts, Users, Groups and Resources as well as for configuring Databases, Filestores and OX Servers. It is currently split into two parts, | ||
Latest revision as of 13:53, 29 June 2016
Interfaces
- The HTTP API is used by the new AJAX GUI. It consists mainly of messages in JavaScript Object Notation (JSON) sent over HTTP.
- Provisioning API to access the Open-Xchange Admin Daemon
- The RMI API is used for data provisioning of Contexts, Users, Groups and Resources as well as for configuring Databases, Filestores and OX Servers. It is currently split into two parts,
- The Open-Xchange Hyperion CLT are shell scripts that simplify groupware and service administration
- Provisioning using SOAP
- The Oxmapi is a windows library for programmers needed to communicate with the OX server
- Open-Xchange Mail Abstraction Layer
- The Plugin API for extending the GUI is described in two documents: an overview and the reference
- UDPPush Open-Xchange PUSH Interface for Groupware Objects