Search results

...=products/appsuite/stable|pc2n=debianname|pc2v=DebianJessie|backend|office-communication|calcengine}} ...bianJessie|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|backend/updates|office-communication/updates|calcengine/updates}}

Ideal for customers looking for a secure email, communication, and collaboration suite for their consumer or SMB market. ...lco’s and ISPs the leading IMAP server combined with an easy-to-use UI for communication and collaboration.

...bmail, desktop clients, or mobile apps, your users will receive your email communication on all devices. [[Category: Communication]]

An easy-to-use email, communication, and collaboration platform, OX App Suite v7 provides access to a wide rang

...nternal components, plugin capabilities, public interfaces (APIs) and data communication streams of the Open-Xchange server. =<span style="background:#dcdcdc">Frontend and client based communication flow </span>=

== Setup the backend communication ==

[[Category: Communication]]

...of concept (POC) for an online service offering a privacy oriented email, communication and collaboration platform with integrated search. The purpose of this POC ...of concept (POC) for an online service offering a privacy oriented email, communication and collaboration platform with integrated search.

...e ticket system (OTRS). The ticket system provides additional features for communication between you and Open-xchange, but it is not meant as a full substitution of ...requirement, customers and support agents have to keep the readable ticket communication, in form of email/article body, subject or attachment names, free from any

...6<br>Open-Xchange Documents frontend v7.8.0-rev6<br>Open-Xchange Documents communication v7.8.0-rev6<br>Open-Xchange Calcengine v7.8.0-rev6<br>Open-Xchange Readeren ...6<br>Open-Xchange Documents frontend v7.8.0-rev6<br>Open-Xchange Documents communication v7.8.0-rev6<br>Open-Xchange Calcengine v7.8.0-rev6<br>Open-Xchange Readeren

This covers how-to articles including server communication, extension points and how to write widgets, applications and plugins:

The port for the OX Backend. Default is 8009 (which is direct communication with the backend). Could be 80, etc, if going through load balancers Communication between Guard and the OX backend is set to HTTP by default. All items to be

[[Category: Communication]]

...ge of our people, the power of their collaboration, and the success of our communication; we look at all potential acquisitions with this in mind.

The port for the OX Backend. Default is 8009 (which is direct communication with the backend). Could be 80, etc, if going through load balancers emails to or from the REST API you can optionally encrypt the whole communication between

The port for the OX Backend. Default is 8009 (which is direct communication with the backend). Could be 80, etc, if going through load balancers emails to or from the REST API you can optionally encrypt the whole communication between

Multiple Open-Xchange servers can form a cluster with inter-OX-communication over a network. OX App Suite offers a second HTTP based connector for the communication between the HTTP server and the backend. This new connector is based on Ora

...ng App Store. Availability will be confirmed by Open-Xchange via the usual communication channels.

...ease 7.0.1 of OX App Suite, we offer a second HTTP based connector for the communication between the HTTP server and the backend. This new connector is based on Ora [[Appsuite:Grizzly#Cluster_setup]] shows that HTTPS communication is terminated by the Apache balancer in front of the OX backends. To let th

...unning.<br/>But the client is not connected to the server directly.<br/>As communication channel between both nodes JMS is used. * 1x JMS Server for communication