Search results

  • This chapter describes how the backend components of OX Mail are installed and configured on the server. Mobile API Facade is available with the following backend packages:
    13 KB (1,829 words) - 14:30, 9 June 2022
  • ...=open-xchange-authentication-imap|toplevel=products|sopath=appsuite/stable/backend|version=App Suite}}
    3 KB (478 words) - 07:12, 26 January 2017
  • {{InstallPlugin|pluginname=open-xchange-eas-provisioning|sopath=6.22/updates/backend|version=v6.22.x}}
    4 KB (664 words) - 11:41, 12 June 2014
  • ...plugins, you should check out the [[AppSuite:Backend build system#Source | backend]]. ...e App Suite product consists of a server and a UI, you also need a working backend (App Suite application server) to communicate with.
    5 KB (835 words) - 10:01, 22 May 2017
  • deb https://software.open-xchange.com/products/appsuite/7.8.2/backend/DebianWheezy/ / ...://[CUSTOMERID:PASSWORD]@software.open-xchange.com/products/appsuite/7.8.2/backend/updates/DebianWheezy/ /
    10 KB (1,406 words) - 12:31, 8 December 2016
  • Every email system providing IMAP and SMTP can be used as backend to OX. Best experiences are made with the widespread Linux based IMAP serve
    5 KB (754 words) - 08:16, 8 February 2018
  • Every email system providing IMAP and SMTP can be used as backend to OX. Best experiences are made with the widespread Linux based IMAP serve
    4 KB (517 words) - 08:17, 8 February 2018
  • Every email system providing IMAP and SMTP can be used as backend to OX. Best experiences are made with the widespread Linux based IMAP serve
    5 KB (809 words) - 08:17, 8 February 2018
  • ...nname=open-xchange-admin-reseller|toplevel=products|sopath=appsuite/stable/backend}}
    6 KB (791 words) - 16:52, 3 December 2019
  • The whole documentconverter product consists of 3 different parts: the OX backend documentconverter bundles, written in Java as OSGi plugins, the native read The '''readerengine''' is - as the name implies - the low level backend engine for the converter implementation, that acts as a general purpose doc
    28 KB (3,931 words) - 14:07, 14 February 2023
  • ...redirect the browser there. This will usually be a relative URL, since the backend and frontend are usually accessible using the same host (they have to be to So, in essence, what we need is a form for POSTing to the backend with the above parameters. This is pretty basic HTML stuff:
    8 KB (1,301 words) - 09:03, 18 July 2014
  • ...to be installed in an OX App Suite configuration with a [[AppSuite:Grizzly|backend based on Grizzly]] (including hazelcast as installed and activated by defau ...tt> and <tt>open-xchange-documents-ui</tt>. The <tt>open-xchange-documents-backend</tt> package also requires and installs these packages:
    36 KB (5,058 words) - 06:08, 29 November 2023
  • ...d". If this path exists, you can control which services are enabled by the backend. In order to do so, you can add the following to <code>/opt/open-xchange/et
    4 KB (514 words) - 15:28, 9 September 2011
  • |Open-Xchange App Suite Middleware (Backend) v7.10.6-rev57 ...n-Xchange App Suite Frontend v8.20.3<br>Open-Xchange App Suite Middleware (Backend) v8.20.0
    26 KB (3,911 words) - 08:51, 22 March 2024
  • <!-- as long as the backend for OX6 and AppSuite is the same, we only have one article. Less redundancy
    153 bytes (27 words) - 12:51, 16 July 2013
  • = Backend Improvements = ...he page [http://oxpedia.org/wiki/index.php?title=Backend_Improvements_6_22 Backend Improvements v6.22] for an overview of improvements to the Open-Xchange arc
    2 KB (230 words) - 19:11, 27 September 2012
  • = Backend Improvements = ...he page [http://oxpedia.org/wiki/index.php?title=Backend_Improvements_6_22 Backend Improvements v6.22] for an overview of improvements to the Open-Xchange arc
    2 KB (234 words) - 12:52, 22 November 2012
  • '''Foreword''': This article describes the changes between backend version 6.20.7 and 6.22.0. It is sometimes considered to be ''the differenc ...r servlets will continue to function it is strongly recommended to migrate backend extensions that are accessed by HTTP API clients to the new framework to be
    12 KB (1,851 words) - 10:38, 14 March 2013
  • This is an overview of all configuration parameters for the AppSuite backend. By default, this list is sorted by the .properties files they appear in. | <nowiki>Every client tells the backend through the client parameter on the login request his identity. This is not
    231 KB (31,767 words) - 10:27, 19 April 2013
  • = Grizzly based backend = ...HTTP based connector for the communication between the HTTP server and the backend. This new connector is based on Oracle's '''[http://grizzly.java.net Projec
    21 KB (3,032 words) - 06:05, 18 September 2019

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)