Search results

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

...n successful, the groupware nodes will establish TCP connections for cache communication.

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

...ervices as dependency. The Apache module ''proxy_ajp'' will handle all the communication with the Open-Xchange Servers. Its configuration also contains the setup of

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

The whole cluster communication will now be done through Hazelcast. Please note that even in case of an upd

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

...t the TCP port 9090 may be changed. It is used for the directors’ internal communication. *director-admin unix socket used for director admin communication. director-admin unix listener service needs to be configured in dovecot.con

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

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

== Communication with the server ==

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

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