Template:Main Page Advanced: Difference between revisions

From Open-Xchange
Line 65: Line 65:
* [[UCS_AD_Connector_en|Synchronize Active Directory with OX ASE/SE for UCS]]
* [[UCS_AD_Connector_en|Synchronize Active Directory with OX ASE/SE for UCS]]
* [[Tune_apache2_for_more_concurrent_connections|Apache2 tuning]]
* [[Tune_apache2_for_more_concurrent_connections|Apache2 tuning]]
* [[Running a cluster]]


= Testing and QA =
= Testing and QA =

Revision as of 14:23, 18 January 2013

Overview

Branding

UI Customization and Examples

Groupware Server customization

Programming Interfaces

  • The HTTP API is used by the Open-Xchange GUI and various 3rd party applications. It consists mainly of messages in JavaScript Object Notation (JSON) sent over HTTP.
  • The WebDAV API is used by external clients to modify object on the OX Server. It based mainly on the webdav standard with some enhancements to handle OX objects.
  • 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 CLT are shell scripts that simplify groupware and service administration
    • Create contexts/users with with Csv_import
    • 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

Importing and exporting data

Configuration and Tweaks

Testing and QA

Translations

Installation based on source code