Template:Main Page Advanced: Difference between revisions
From Open-Xchange
No edit summary |
|||
| Line 27: | Line 27: | ||
*** [[Open-Xchange servlet for external login masks]] | *** [[Open-Xchange servlet for external login masks]] | ||
= Interfaces = | = Programming and Network Interfaces = | ||
* The [[HTTP_API|HTTP API]] is used by the Open-Xchange GUI and various 3rd party applications. It consists mainly of messages in JavaScript Object Notation ([http://json.org JSON]) sent over HTTP. | * The [[HTTP_API|HTTP API]] is used by the Open-Xchange GUI and various 3rd party applications. It consists mainly of messages in JavaScript Object Notation ([http://json.org JSON]) sent over HTTP. | ||
* The [[Oxwebdavapi|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. | * The [[Oxwebdavapi|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. | ||
Revision as of 16:20, 24 January 2011
Translations
Branding
- White-labeling the Open-Xchange GUI for big hosting/reseller environments
- GUI Theming Description
- User and context based themes
- GUI Branding Plugins
UI Customization
- Embedding external web applications which require authentication
- Setting User/GUI Preferences via RMI
- Open-Xchange Netvibes UWA mashup
- GUI Plugin Development
- GUI Plugin API Documentation
- Enable the TinyMCE spell-checker module
Programming Examples and Howtos
- How to make custom changes to existing plugins (Authentication plugin)
- Automatically delete users OX-Objects and OX-Folders
- Auto login, session handling, single sign on
Programming and Network 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
- 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
- Documentation for the data import format
- VCard and ICal support
- Using the export servlet
- Using the import servlet
- Example in bash to extract private contacts,tasks,appointments in ical/vcard format
- Importing holidays into the OX Calendar
- Architecture of the crawler bundle
Configuration and Tweaks
- Basic troubleshooting
- HTML Whitelist configuration
- Open-Xchange Configuration
- Open-Xchange and Lighttpd
- Open-Xchange as RSS client
- On The Fly Configuration Update (experimental)
- Session migration
- syslog Configuration
- Integrate OXAE Mailinglists into Open-Xchange
- Mail Notification (Push) with Open-Xchange