Search results

The installation of the <code>open-xchange-guard-backend-plugin</code> package which is required for Guard and the main <code>open-x ...X middleware are: <code>open-xchange-rest</code>, <code>open-xchange-guard-backend-plugin</code> and <code>open-xchange-guard-ui</code>.

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

# detect capacity issues in wforce backend # deny request if primary backend doesn't have capacity

deb https://software.open-xchange.com/products/appsuite/stable/backend/DebianStretch/ / ...//[CUSTOMERID:PASSWORD]@software.open-xchange.com/products/appsuite/stable/backend/updates/DebianStretch/ /

...d is intergraded into the OSGi stack, it will start automatically with the backend, i.e. when the <code>open-xchange</code> system service starts. ...et. There are a few things to do before having a fully functional OX Guard backend.

...=open-xchange-authentication-imap|toplevel=products|sopath=appsuite/stable/backend|version=App Suite}}

...essionID is used to identify every session. It is a UUID, generated by the backend via default Java UUID implementation. It is written into the OX logfiles fo ...ion-Secret is used to verify every session. It is a UUID, generated by the backend via default Java UUID implementation. Only accesses, where the Session-Secr

...pen-xchange-spamhandler-cloudmark|toplevel=products|sopath=appsuite/stable/backend|version=App Suite}}

...the Guard service. They can be all installed on the same server as the OX backend, or on a separate server. ...nts required for the OX backend are: open-xchange-rest, open-xchange-guard-backend-plugin

The corresponding documentconverter server needs to be set on the Ox backend node, where the documentconverter-client package has been installed. The na ...be held within the error cache for the rest of the runtime of the current backend instance.

...and starts processing the list of target images via one started processing backend for each required target image. The number of processing backends that can === Processing backend memory usage ===

...gin|pluginname=open-xchange-log4j|toplevel=products|sopath=appsuite/stable/backend|version=App Suite}}

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

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

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

You can find Perl and PHP example code in the git repository <tt>wd/backend/com.openexchange.admin.soap</tt>.

deb http://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 /

{{InstallPlugin|pluginname=open-xchange-eas-provisioning|sopath=6.22/updates/backend|version=v6.22.x}}

== Get the configuration of the mail filter backend == Note that this call is only used as workaround for parsing errors in the backend, so that the user is able to kick a whole script if it contains errors in t

|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