Search results

...ard-core.properties</code>. The first configuration file is part of the OX backend and contains properties, among others, that enable the OX Guard functionali The username to access the OX Backend and Guard database. This user needs to have select, create, lock, insert, u

grunt install:dist --prefix backend --htdoc www After that, check if the directories <tt>backend</tt> and <tt>www</tt> contain files that look a little familiar. If everyth

...open-xchange-file-storage-dropbox|toplevel=products|sopath=appsuite/stable/backend|version=App Suite}} ...-xchange-file-storage-googledrive|toplevel=products|sopath=appsuite/stable/backend|version=App Suite}}

...be able to determine the users ID and context. This is done through the OX backend by default, which in turn looks up the email address using the default logi ...e <nowiki>/opt/open-xchange/etc/guard-core.properties</nowiki> file (Guard backend) by adding the setting com.openexchange.guard.mailResolverUrl

...y the installation which can be removed and protected tiles are set by the backend. In order to configure widgets on the backend we have to turn the above into a valid YAML structure:

Tell your Apache to process .htaccess files and how to connect to backend: ...the proper document root depending on your OS or custom configuration! If backend does not run on localhost (127.0.0.1), you have to adjust the ProxyPass dir

...Java virtual machine, and about the Open-Xchange Middleware (aka groupware backend) including Imageconverter.

...xchange Active Sync" protocol supports Push via HTTPS, therefore the email backend needs to send push events to the OX server. Details, see: [[OXtender for Bu =<span style="background:#E5E5E5">Backend related components and communication flow</span>=

...UIs (OX6 and OX App Suite) is supported beginning with OX6 version 6.22.2 (backend version 7.0.2) and OX App Suite version 7.0.1. ...adding a frontend, there is nothing to change in the configuration of the backend servers, the database, mail, or such. It is only required to adjust the apa

...pen-xchange-filestore-sproxyd | toplevel=products | sopath=appsuite/stable/backend | version=App Suite}} * Open a terminal on a running backend server of your OX cluster

...nge-oauth open-xchange-messaging|toplevel=products |sopath=appsuite/stable/backend |version=App Suite}}

...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:

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

...UIs (OX6 and OX App Suite) is supported beginning with OX6 version 6.22.2 (backend version 7.0.2) and OX App Suite version 7.0.1. ...adding a frontend, there is nothing to change in the configuration of the backend servers, the database, mail, or such. It is only required to adjust the apa

This chapter describes how the backend components of OX Drive are installed and configured on the server. Open-Xchange Drive is available with the following backend packages:

= 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

...UIs (OX6 and OX App Suite) is supported beginning with OX6 version 6.22.2 (backend version 7.0.2) and OX App Suite version 7.0.2. ...adding a frontend, there is nothing to change in the configuration of the backend servers, the database, mail, or such. It is only required to adjust the apa

You need a clone of the [[SourceCodeAccess|backend git repo]]. Therein you find the com.openexchange.admin.rmi package which c javac -d build -cp ~/git/backend.git/com.openexchange.admin.rmi/src:. *.java

backend = static backend = static_append

...It uses an existing portal widget, which you just need to configure on the backend. It makes use of the [[AppSuite:Configuring portal plugins|config options]] [[Category: Backend]]