https://wiki.open-xchange.com/wiki/api.php?action=feedcontributions&feedformat=atom&user=HolgiOpen-Xchange - User contributions [en]2026-06-30T19:12:33ZUser contributionsMediaWiki 1.39.7https://wiki.open-xchange.com/wiki/index.php?title=Change-Request&diff=21373Change-Request2016-02-04T12:13:37Z<p>Holgi: </p>
<hr />
<div>= How to request a change for OXaaS =<br />
<br />
= Concern: =<br />
You are customer of OXaaS and have your Support Keys at hand. Furthermore you want to request a change for the service.<br />
<br />
= Todo: =<br />
Send an E-Mail to <oxaas-change AT open-xchange.com> and provide the following information within the E-Mail body. Please take care to put your Support Key always to the top. If you provide more than one key the first recognised key wins.<br />
<br />
Subject: The subject should give a high level description of the Change Request and is used as Title<br />
<br />
Support Key: OX-SUPPORT-OR-LICENSE-KEY-XXX <br />
Reason: give the reason why the change is needed<br />
Description: provide a meaningful description of the desired change<br />
Server url: provide the URL of the service (tenant url)<br />
<br />
further information you might think is important comes here...<br />
<br />
example E-Mail:<br />
<br />
To: oxaas-change AT open-xchange.com<br />
Subject: renewal of ssl certificates<br />
<br />
Support Key: OX-SUPPORT-OR-LICENSE-KEY-123123123123 <br />
Reason: our ssl certificates expire in 40 days<br />
Description: please change certificates on the systems<br />
Server URL: www.oxaas.com<br />
<br />
attached my new encrypted certificates, please proceed.<br />
thank you.<br />
<br />
If all of the above information has been provided, a confirmation mail is sent from Open-Xchange's ticket system which includes the ticket number for that incident.</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Change-Request&diff=21372Change-Request2016-02-04T12:09:37Z<p>Holgi: </p>
<hr />
<div>= How to request a change for OXaaS =<br />
<br />
= Concern: =<br />
You are customer of the OXaaS and have a Support Keys. Furthermore you want a request a change for the service.<br />
<br />
= Todo: =<br />
Send an E-Mail to <oxaas-change AT open-xchange.com> and provide the following information within the E-Mail body. Please take care to put your Support Key always to the top. If you provide more than one key the first recognised key wins.<br />
<br />
Subject: The subject should give a high level description of the Change Request and is used as Title<br />
<br />
Support Key: OX-SUPPORT-OR-LICENSE-KEY-XXX <br />
Reason: give the reason why the change is needed<br />
Description: provide a meaningful description of the desired change<br />
Server url: provide the URL of the service (tenant url)<br />
<br />
further information you might think is important comes here...<br />
<br />
example E-Mail:<br />
<br />
To: oxaas-change AT open-xchange.com<br />
Subject: renewal of ssl certificates<br />
<br />
Support Key: OX-SUPPORT-OR-LICENSE-KEY-123123123123 <br />
Reason: our ssl certificates expire in 40 days<br />
Description: please change certificates on the systems<br />
Server URL: www.oxaas.com<br />
<br />
attached my new encrypted certificates, please proceed.<br />
thank you.<br />
<br />
If all of the above information has been provided, a confirmation mail is sent from Open-Xchange's ticket system which includes the ticket number for that incident.</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Change-Request&diff=21370Change-Request2016-02-02T15:37:38Z<p>Holgi: Created page with "= How to request a change for OXaaS = = Concern: = You are entitled for Advanced Support and have obtained one of Open-Xchange's Support offerings, have registered all your S..."</p>
<hr />
<div>= How to request a change for OXaaS =<br />
<br />
= Concern: =<br />
You are entitled for Advanced Support and have obtained one of Open-Xchange's Support offerings, have registered all your Support Keys, which you have got after purchasing your Support offering according the information provided in the [http://knowledgebase.open-xchange.com/index.php?id=163 My Registrations] section. Please also have a look at sdb.open-xchange.com/create-ldb-account-en<br />
<br />
Furthermore you have an issue with your Open-Xchange Software and need help by the Open-Xchange Support.<br />
<br />
= Todo: =<br />
Send an E-Mail to <support AT open-xchange.com> and provide the following information within the E-Mail body. Please take care to put your Support Key always to the top. If you provide more than one key the first recognised key wins.<br />
<br />
Support Key: OX-SUPPORT-OR-LICENSE-KEY-XXX<br />
Server: url of the machine<br />
Server Version: server version or package list<br />
Platform: Please choose one from [https://oxpedia.org/wiki/index.php?title=Contact-Support:PossibleValues#Platform: possible values].<br />
GUI Version: GUI version or package list<br />
Category: Please choose one from [https://oxpedia.org/wiki/index.php?title=Contact-Support:PossibleValues#Module: possible values].<br />
Severity: 1, 2, 3, 4<br />
Track-ID: the customer's internal tracking number, e.g. from its Bugzilla<br />
Product: Please choose one from [https://oxpedia.org/wiki/index.php?title=Contact-Support:PossibleValues#Product: possible values].<br />
<br />
Steps to reproduce:<br />
...<br />
<br />
Current behaviour:<br />
...<br />
<br />
Expected behaviour:<br />
...<br />
<br />
The Severity of an Incident determines the impact it has on the customer's business and therefore the urgency of solving an Incident of certain impact.<br />
<br />
'''Important:''' Please note that Open-Xchange's response time depends on both the Severity and the Service Level Agreement between the customer and Open-Xchange.<br />
<br />
If all of the above information has been provided a confirmation mail is sent from Open-Xchange's ticket system which includes the ticket number for that incident.<br />
<br />
= Open-Xchange Severity: =<br />
<br />
== Severity 1==<br />
<br />
Shall mean Incidents that are defined as a complete outage and do not allow the Licensee to further conduct his business. Licensee's system or application is completely not available and no Workaround exists. The Incident affects all users deployed on the Joint Solution Environment.<br />
Also means a security or general threat causing potential risk to the customers’ data integrity or privacy.<br />
A situation in which one or several servers do not operate correctly is not a Severity 1 issue, unless the issue causes one of the above to happen.<br />
<br />
==Severity 2==<br />
<br />
The Licensee’s operation is severely disrupted. A business critical component of the Joint Solution Environment cannot be used by a majority of the users.<br />
<br />
==Severity 3==<br />
<br />
Shall mean Incidents which involve partial loss of non-critical functionality, one which impairs many operations, but allows the Licensee to continue to operate.<br />
<br />
==Severity 4==<br />
<br />
Shall mean general usage questions, recommendations for product enhancements or modifications, and calls that are passed to the Parties for informational purposes. This includes but is not limited to documentation and translation errors.<br />
<br />
= Personal Data Policy =<br />
According to German law, companies are forced to handle any (log) files from customers which contain data related to a third person or has any personal protection in a special way. Personal data shall mean any information concerning the personal or material circumstances of an identified or identifiable natural person. Even so they have to be deleted once they aren't used any more. To fulfil this 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 personal data. This can be every thing from names, email addresses, screen-shots, logs files and even credentials to system accounts. This personal data only has to be handed over in form of attachments which was common practice before. Transfer channels for personal data are attachments via the ticket system, attachment in encrypted emails or provided by protected download links. How to send encrypted emails via PGP is described [http://sdb.open-xchange.com/node/59 here].<br />
<br />
The integrity of an 'Incident Request' with all available data needs to be saved up to 90 days after a ticket was closed to ensure a holistic assessment in case of Contractual complaints. This time frame is mandatory and gives also the customer time for detailed tests. In case of reopening an incident within these three months all information is still available and needs not to be recollected by customers and end users.<br />
<br />
Open-Xchange introduced a weekly deletion process, the deletion work on ticket attachments and on raw email files which are affected by attachments. The automatic deletion of all ticket attachments takes place weekly at Sunday and affects all tickets which are in a 'closed' state since 90 days.<br />
<br />
= Creating an OX Support Tarball =<br />
<br />
[http://oxpedia.org/wiki/index.php?title=AppSuite:Oxsysreport Creating an OX Support Tarball]</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXaaS_FAQ&diff=21369OXaaS FAQ2016-02-02T15:35:34Z<p>Holgi: </p>
<hr />
<div>= OX as a Service - Technical FAQ =<br />
<br />
== How can I request a change for my service? ==<br />
<br />
We have a change process, please use following [[Change-Request]]<br />
<br />
== Can I create my users in the default domain and change later to my own domain? ==<br />
<br />
Yes, you can create the users and add aliases for another domain later.<br />
<br />
== What is an MX record? ==<br />
<br />
An MX record tells senders where to send email for your domain.<br />
<br />
When you have a domain registered, there are several DNS records assigned to it. These enable it to be located on the Internet. These include MX records, which direct the domain’s mail flow. <br />
Each and every MX record points to an email server that should be configured to process all emails for that domain. <br />
There’s typically one record that points to a Primary Server, then additional records that point to one or more backup servers. <br />
For users to send and receive email, their domain's MX records must point to a server that can process their mail.<br />
<br />
== Where are my MX records? ==<br />
<br />
Your authoritative MX records are on your DNS Service Provider Server. When you change the MX record on your DNS Service Provider, other servers will make copies of these updated MX records over time.<br />
<br />
== How long do MX record updates take? ==<br />
<br />
MX record updates are not immediate. After you've updated your MX records, it will take a while for every sender to use the new MX records. <br />
<br />
== Will I lose mail after changing MX records? ==<br />
<br />
No. As long as you enter the MX records correctly, you won't lose any MX email. While your MX records are changing over, some mail will be delivered using your old MX information, and some mail will be delivered using your new MX information, but all of it will be delivered.<br />
<br />
== What happens if I type the wrong information into the MX record? ==<br />
<br />
If you type the incorrect delivery information in the MX record, some mail will bounce. The sender will receive a notice that the mail wasn't delivered. If this happens, correct the MX records as soon as possible. Some mail may still bounce for a period of time, but the sooner you update the MX records to the correct setting, the fewer messages will bounce.<br />
<br />
== What happens when I update my MX records? ==<br />
<br />
Once you update your MX records, mail will start flowing to the OX as a Service (After your old previous TTL (Time To Live in seconds) has expired).<br />
<br />
== Are there limits set a user might run into? ==<br />
<br />
The size of emails is limited to 20MB per mail including all attachments. There is also a general 100MB limit for data uploaded via the web ui.<br />
The Service has limits for request rates and of course for the amount of objects one can create in total. Those are set as high so normal users do not run into.</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXaaS_FAQ&diff=18916OXaaS FAQ2014-11-24T08:42:05Z<p>Holgi: /* Are there limits set a user might run into? */</p>
<hr />
<div>= OX as a Service - Technical FAQ =<br />
<br />
== Can I create my users in the default domain and change later to my own domain? ==<br />
<br />
Yes, you can create the users and add aliases for another domain later.<br />
<br />
== What is an MX record? ==<br />
<br />
An MX record tells senders where to send email for your domain.<br />
<br />
When you have a domain registered, there are several DNS records assigned to it. These enable it to be located on the Internet. These include MX records, which direct the domain’s mail flow. <br />
Each and every MX record points to an email server that should be configured to process all emails for that domain. <br />
There’s typically one record that points to a Primary Server, then additional records that point to one or more backup servers. <br />
For users to send and receive email, their domain's MX records must point to a server that can process their mail.<br />
<br />
== Where are my MX records? ==<br />
<br />
Your authoritative MX records are on your DNS Service Provider Server. When you change the MX record on your DNS Service Provider, other servers will make copies of these updated MX records over time.<br />
<br />
== How long do MX record updates take? ==<br />
<br />
MX record updates are not immediate. After you've updated your MX records, it will take a while for every sender to use the new MX records. <br />
<br />
== Will I lose mail after changing MX records? ==<br />
<br />
No. As long as you enter the MX records correctly, you won't lose any MX email. While your MX records are changing over, some mail will be delivered using your old MX information, and some mail will be delivered using your new MX information, but all of it will be delivered.<br />
<br />
== What happens if I type the wrong information into the MX record? ==<br />
<br />
If you type the incorrect delivery information in the MX record, some mail will bounce. The sender will receive a notice that the mail wasn't delivered. If this happens, correct the MX records as soon as possible. Some mail may still bounce for a period of time, but the sooner you update the MX records to the correct setting, the fewer messages will bounce.<br />
<br />
== What happens when I update my MX records? ==<br />
<br />
Once you update your MX records, mail will start flowing to the OX as a Service (After your old previous TTL (Time To Live in seconds) has expired).<br />
<br />
== Are there limits set a user might run into? ==<br />
<br />
The size of emails is limited to 20MB per mail including all attachments. There is also a general 100MB limit for data uploaded via the web ui.<br />
The Service has limits for request rates and of course for the amount of objects one can create in total. Those are set as high so normal users do not run into.</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXCloud_DE-FAQ&diff=18813OXCloud DE-FAQ2014-10-23T10:50:40Z<p>Holgi: </p>
<hr />
<div>= OX as a Service - Technische FAQ =<br />
<br />
== Ist es möglich, Benutzer zuerst für die allgemein verfügbare Domain anzulegen und später auf eine eigene umzuändern? ==<br />
<br />
Ja, Sie können für jeden Benutzer später einen Alias mit der neuen Domain hinzufügen.<br />
<br />
== Was ist ein MX Record? ==<br />
<br />
MX Records bestimmen, wohin Emails für eine Domain geleitet werden.<br />
<br />
Beim Registrieren einer Domain werden für diese verschiedene DNS Records festgelegt. Darunter sind auch MX Records. Diese bestimmen, wohin Emails an diese Domain verschickt werden. Jeder MX Record zeigt <br />
zu einem Server. Dieser muss so konfiguriert sein, dass er Emails für die Domain annimmt und verarbeitet.<br />
Normalerweise gibt es einen MX-Eintrag für einen primären Server und zusätzliche für Redundanz.<br />
Damit Benutzer Emails an eine Domain schicken und für diese empfangen können, müssen MX Records vorhanden sein, die auf einen Mailserver zeigen, der deren Emails verarbeitet.<br />
<br />
== Wo finde ich meine MX Records? ==<br />
<br />
Ihre "authoritative" MX Records finden Sie auf dem DNS Service Provider-Server. Nach einiger Zeit erzeugen sich andere Server Kopien der Änderungen.<br />
<br />
== Wie lange dauert es, bis eine MX Record-Änderung Wirkung zeigt? ==<br />
<br />
Eine MX Record-Änderung zeigt nicht sofort Wirkung. Es dauert eine gewisse Zeit bis alle Sender diese benutzen.<br />
<br />
== Kann ich Emails verlieren, wenn ich MX Records verändere? ==<br />
<br />
Nein. Solange ein korrekter MX Record vorhanden ist, geht keine Email verloren. Während die MX Records-Änderung durchgeführt wird, kann es sein, dass Emails mit der alten und manche mit der neuen MX-Information verschickt werden.<br />
<br />
== Was passiert, wenn ich einen falschen MX Record eingetragen habe? ==<br />
<br />
Wenn ein falscher MX Record eingetragen wurde, bekommen Sender eine Fehlermeldung und Emails werden zurückgeschickt bzw. nicht angenommen. Der Sender bekommt eine Nachricht, dass die Email nicht ausgeliefert werden konnte.<br />
Falsche MX Records müssen sobald als möglich berichtigt werden. Nach einiger Zeit werden dann Emails wieder richtig zugestellt.<br />
<br />
== Was passiert, wenn ich einen MX Record ändere? ==<br />
<br />
Nach einer MX Record-Änderung wird diese nach einiger Zeit bei allen Sendern bekannt (spätestens nachdem die TTL abgelaufen ist. TTL=Zeit in Sekunden, für die ein Eintrag zwischengespeichert werden darf).</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXaaS_FAQ&diff=18733OXaaS FAQ2014-10-15T11:08:00Z<p>Holgi: </p>
<hr />
<div>= OX as a Service - Technical FAQ =<br />
<br />
== Can I create my users in the default domain and change later to my own domain? ==<br />
<br />
Yes, you can create the users and add aliases for another domain later.<br />
<br />
== What is an MX record? ==<br />
<br />
An MX record tells senders where to send email for your domain.<br />
<br />
When you have a domain registered, there are several DNS records assigned to it. These enable it to be located on the Internet. These include MX records, which direct the domain’s mail flow. <br />
Each and every MX record points to an email server that should be configured to process all emails for that domain. <br />
There’s typically one record that points to a Primary Server, then additional records that point to one or more backup servers. <br />
For users to send and receive email, their domain's MX records must point to a server that can process their mail.<br />
<br />
== Where are my MX records? ==<br />
<br />
Your authoritative MX records are on your DNS Service Provider Server. When you change the MX record on your DNS Service Provider, other servers will make copies of these updated MX records over time.<br />
<br />
== How long do MX record updates take? ==<br />
<br />
MX record updates are not immediate. After you've updated your MX records, it will take a while for every sender to use the new MX records. <br />
<br />
== Will I lose mail after changing MX records? ==<br />
<br />
No. As long as you enter the MX records correctly, you won't lose any MX email. While your MX records are changing over, some mail will be delivered using your old MX information, and some mail will be delivered using your new MX information, but all of it will be delivered.<br />
<br />
== What happens if I type the wrong information into the MX record? ==<br />
<br />
If you type the incorrect delivery information in the MX record, some mail will bounce. The sender will receive a notice that the mail wasn't delivered. If this happens, correct the MX records as soon as possible. Some mail may still bounce for a period of time, but the sooner you update the MX records to the correct setting, the fewer messages will bounce.<br />
<br />
== What happens when I update my MX records? ==<br />
<br />
Once you update your MX records, mail will start flowing to the OX as a Service (After your old previous TTL (Time To Live in seconds) has expired).<br />
<br />
== Are there limits set a user might run into? ==<br />
<br />
In addition, the size of emails is limited to 20MB per mail including all attachments. There is also a general 100MB limit for data uploaded via the web ui.<br />
The Service has limits for request rates and of course for the amount of objects one can create in total. Those are set as high so normal users do not run into.</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXaaS_FAQ&diff=17286OXaaS FAQ2014-03-17T08:16:21Z<p>Holgi: /* How to connect Email clients like Apple Mail, Outlook and Mozilla to the OX as a Service? */</p>
<hr />
<div>= OX as a Service - Technical FAQ =<br />
<br />
== Can I create my users in the default domain and change later to my own domain? ==<br />
<br />
Yes, you can create the users and add aliases for another domain later.<br />
<br />
== What is an MX record? ==<br />
<br />
An MX record tells senders where to send email for your domain.<br />
<br />
When you have a domain registered, there are several DNS records assigned to it. These enable it to be located on the Internet. These include MX records, which direct the domain’s mail flow. <br />
Each and every MX record points to an email server that should be configured to process all emails for that domain. <br />
There’s typically one record that points to a Primary Server, then additional records that point to one or more backup servers. <br />
For users to send and receive email, their domain's MX records must point to a server that can process their mail.<br />
<br />
== Where are my MX records? ==<br />
<br />
Your authoritative MX records are on your DNS Service Provider Server. When you change the MX record on your DNS Service Provider, other servers will make copies of these updated MX records over time.<br />
<br />
== How long do MX record updates take? ==<br />
<br />
MX record updates are not immediate. After you've updated your MX records, it will take a while for every sender to use the new MX records. <br />
<br />
== Will I lose mail after changing MX records? ==<br />
<br />
No. As long as you enter the MX records correctly, you won't lose any MX email. While your MX records are changing over, some mail will be delivered using your old MX information, and some mail will be delivered using your new MX information, but all of it will be delivered.<br />
<br />
== What happens if I type the wrong information into the MX record? ==<br />
<br />
If you type the incorrect delivery information in the MX record, some mail will bounce. The sender will receive a notice that the mail wasn't delivered. If this happens, correct the MX records as soon as possible. Some mail may still bounce for a period of time, but the sooner you update the MX records to the correct setting, the fewer messages will bounce.<br />
<br />
== What happens when I update my MX records? ==<br />
<br />
Once you update your MX records, mail will start flowing to the OX as a Service (After your old previous TTL (Time To Live in seconds) has expired).</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXaaS_FAQ&diff=15069OXaaS FAQ2013-07-18T12:23:06Z<p>Holgi: </p>
<hr />
<div>= OX Cloud Service - Technical FAQ =<br />
<br />
== Can I create my users in the default domain and change later to my own domain? ==<br />
<br />
Yes, you can create the users and add aliases for another domain later.<br />
<br />
== What is an MX record? ==<br />
<br />
An MX record tells senders where to send email for your domain.<br />
<br />
When you have a domain registered, there are several DNS records assigned to it. These enable it to be located on the Internet. These include MX records, which direct the domain’s mail flow. <br />
Each and every MX record points to an email server that should be configured to process all emails for that domain. <br />
There’s typically one record that points to a Primary Server, then additional records that point to one or more backup servers. <br />
For users to send and receive email, their domain's MX records must point to a server that can process their mail.<br />
<br />
== Where are my MX records? ==<br />
<br />
Your authoritative MX records are on your DNS Service Provider Server. When you change the MX record on your DNS Service Provider, other servers will make copies of these updated MX records over time.<br />
<br />
== How long do MX record updates take? ==<br />
<br />
MX record updates are not immediate. After you've updated your MX records, it will take a while for every sender to use the new MX records. <br />
<br />
== Will I lose mail after changing MX records? ==<br />
<br />
No. As long as you enter the MX records correctly, you won't lose any MX email. While your MX records are changing over, some mail will be delivered using your old MX information, and some mail will be delivered using your new MX information, but all of it will be delivered.<br />
<br />
== What happens if I type the wrong information into the MX record? ==<br />
<br />
If you type the incorrect delivery information in the MX record, some mail will bounce. The sender will receive a notice that the mail wasn't delivered. If this happens, correct the MX records as soon as possible. Some mail may still bounce for a period of time, but the sooner you update the MX records to the correct setting, the fewer messages will bounce.<br />
<br />
== What happens when I update my MX records? ==<br />
<br />
Once you update your MX records, mail will start flowing to the cloud service (After your old previous TTL (Time To Live in seconds) has expired).<br />
<br />
== How to connect Email clients like Apple Mail, Outlook and Mozilla to the OX Cloud Service? ==<br />
<br />
Email client can be connected to the OX Cloud service using the standard IMAP protocol.</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXaaS_FAQ&diff=15068OXaaS FAQ2013-07-18T12:21:17Z<p>Holgi: </p>
<hr />
<div>= OX Cloud Service - Technical FAQ =<br />
<br />
== Can I create my users in the default domain and change later to my own domain? ==<br />
<br />
Yes, you can create the users and add aliases for another domain later.<br />
<br />
== What is an MX record? ==<br />
<br />
An MX record tells senders where to send email for your domain.<br />
<br />
When you have a domain registered, there are several DNS records assigned to it. These enable it to be located on the Internet. These include MX records, which direct the domain’s mail flow. <br />
Each and every MX record points to an email server that should be configured to process all emails for that domain. <br />
There’s typically one record that points to a Primary Server, then additional records that point to one or more backup servers. <br />
For users to send and receive email, their domain's MX records must point to a server that can process their mail.<br />
<br />
== Where are my MX records? ==<br />
<br />
Your authoritative MX records are on your DNS Service Provider Server. When you change the MX record on your DNS Service Provider, other servers will make copies of these updated MX records over time.<br />
<br />
== How long do MX record updates take? ==<br />
<br />
MX record updates are not immediate. After you've updated your MX records, it will take a while for every sender to use the new MX records. <br />
<br />
== Will I lose mail after changing MX records? ==<br />
<br />
No. As long as you enter the MX records correctly, you won't lose any MX email. While your MX records are changing over, some mail will be delivered using your old MX information, and some mail will be delivered using your new MX information, but all of it will be delivered.<br />
<br />
== What happens if I type the wrong information into the MX record? ==<br />
<br />
If you type the incorrect delivery information in the MX record, some mail will bounce. The sender will receive a notice that the mail wasn't delivered. If this happens, correct the MX records as soon as possible. Some mail may still bounce for a period of time, but the sooner you update the MX records to the correct setting, the fewer messages will bounce.<br />
<br />
== What happens when I update my MX records? ==<br />
<br />
Once you update your MX records, mail will start flowing to the cloud service (After your old previous TTL (Time To Live in seconds) has expired).<br />
<br />
== How to connect Email clients like Apple Mail, Outlook and Mozilla to the OX Cloud Service?<br />
<br />
Email client can be connected to the OX Cloud service using the standard IMAP protocol.</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXCloud_DE-FAQ&diff=14603OXCloud DE-FAQ2013-05-21T08:23:08Z<p>Holgi: </p>
<hr />
<div>= OX Cloud Service - Technische FAQ =<br />
<br />
== Ist es möglich Benutzer zuerst für die allgemein verfügbare Domain anzulegen und später auf eine Eigene umzuändern? ==<br />
<br />
Ja, Sie können für jeden User später einen Alias mit der neuen Domain hinzufügen.<br />
<br />
== Was ist ein MX Record? ==<br />
<br />
MX Records bestimmen wohin Emails für eine Domain geleitet werden.<br />
<br />
Beim Registrieren einer Domain, werden verschiedene DNS Records dafür festgelegt. Darunter sind auch MX Records, welche bestimmen wohin Emails an die Domain verschickt werden. Jeder MX Record zeigt <br />
zu einem Server welcher so konfiguriert sein muss, das dieser emails für die Domain annimmt und verarbeitet.<br />
Normalerweise gibt es einen MX Eintrag für einen primären Server und zusätzliche für Redundanz.<br />
Damit Benutzer emails an eine Domain schicken und für diese empfangen können, müssen MX Records vorhanden sein, die auf einen Mailserver zeigen der deren Emails verarbeitet.<br />
<br />
== Wo finde ich meine MX Records? ==<br />
<br />
Ihre "authoritative" MX Records finden Sie auf dem DNS Service Provider Server. Nach einiger Zeit erzeugen sich andere Server Kopien der Änderungen.<br />
<br />
== Wie lange dauert es bis eine MX Record Änderung Wirkung zeigt? ==<br />
<br />
Eine MX Record Änderung zeigt nicht sofort Wirkung. Es dauert eine gewisse Zeit bis alle Sender diese benutzen.<br />
<br />
== Kann ich Emails verlieren wenn ich MX Records verändere? ==<br />
<br />
Nein. Solange ein korrekter MX Record vorhanden ist, geht keine Email verloren. Während die MX Records Änderung durchgeführt wird, kann es sein, das emails mit der alten und manche mit der der neuen MX Information verschickt werden.<br />
<br />
== Was passiert wenn ich einen falschen MX Record eingetragen habe? ==<br />
<br />
Wenn ein falscher MX Record eingetragen wurde, bekommen Sender einen Fehler und Emails werden zurück geschickt bzw. nicht angenommen. Der Sender bekommt eine Nachricht das die Email nicht ausgeliefert werden konnte.<br />
Falsche MX Records müssen sobald als möglich berichtigt werden. Nach einiger Zeit werden dann Emails wieder richtig zugestellt.<br />
<br />
== Was passiert wenn ich einen MX Record Ändere? ==<br />
<br />
Nach einer MX Record Änderung wird diese nach einiger Zeit bei allen Sendern bekannt (spätestens nach dem TTL - Zeit in Sekunden für die ein Eintrag zwischengespeichert werden darf - abgelaufen ist).</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXCloud_DE-FAQ&diff=14602OXCloud DE-FAQ2013-05-21T08:10:45Z<p>Holgi: Created page with "= OX Cloud Service - Technische FAQ = == Ist es möglich Benutzer zuerst für die allgemein verfügbare Domain anzulegen und später auf eine Eigene umzuändern? == Ja, Sie ..."</p>
<hr />
<div>= OX Cloud Service - Technische FAQ =<br />
<br />
== Ist es möglich Benutzer zuerst für die allgemein verfügbare Domain anzulegen und später auf eine Eigene umzuändern? ==<br />
<br />
Ja, Sie können für jeden User später einen Alias mit der neuen Domain hinzufügen.<br />
<br />
== Was ist ein MX Record? ==<br />
<br />
Ein MX Record bestimmt wohin Emails für eine Domain geleitet werden.<br />
<br />
Beim Registrieren einer Domain, werden verschiedene DNS Records dafür festgelegt. Darunter sind auch MX Records, welche bestimmen wohin Emails an die Domain verschickt werden. Jeder MX Record zeigt <br />
zu einem Server welcher so konfiguriert sein muss, das er emails für die Domain annimmt und verarbeitet.<br />
Normalerweise gibt es einen MX Eintrag für einen primären Server und zusätzliche für Redundanz.<br />
Damit Benutzer emails an eine Domain schicken und für diese empfangen können, müssen MX Records vorhanden sein, die auf einen Mailserver zeigen der deren Emails verarbeitet.<br />
<br />
== Wo finde ich meine MX Records? ==<br />
<br />
Ihre "authoritative" MX Records finden Sie auf dem DNS Service Provider Server. Nach einiger Zeit erzeugen sich andere Server Kopien der Änderungen.<br />
<br />
== Wie lange dauert bis eine MX Record Änderung Wirkung zeigt? ==<br />
<br />
Eine MX Record Änderung zeigt nicht sofort Wirkung. Es dauert eine gewisse Zeit bis alle Sender diese benutzen.<br />
<br />
== Kann ich Emails verlieren wenn ich MX Records verändere? ==<br />
<br />
Nein. Solange ein korrekter MX Record vorhanden ist, geht keine Email verloren. Solange die MX Records Änderung durchgeführt wird, kann es sein, das emails mit der alten und manche mit der der neuen MX Information verschickt.<br />
<br />
== Was passiert wenn ich einen falschen MX Record eingetragen habe? ==<br />
<br />
<br />
If you type the incorrect delivery information in the MX record, some mail will bounce. The sender will receive a notice that the mail wasn't delivered. If this happens, correct the MX records as soon as possible. Some mail may still bounce for a period of time, but the sooner you update the MX records to the correct setting, the fewer messages will bounce.<br />
<br />
== What happens when I update my MX records? ==<br />
<br />
Once you update your MX records, mail will start flowing to the cloud service (After your old previous TTL (Time To Live in seconds) has expired).</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXaaS_FAQ&diff=14601OXaaS FAQ2013-05-21T07:51:40Z<p>Holgi: /* Will I lose mail after changing MX records? */</p>
<hr />
<div>= OX Cloud Service - Technical FAQ =<br />
<br />
== Can I create my users in the default domain and change later to my own domain? ==<br />
<br />
Yes, you can create the users and add aliases for another domain later.<br />
<br />
== What is an MX record? ==<br />
<br />
An MX record tells senders where to send email for your domain.<br />
<br />
When you have a domain registered, there are several DNS records assigned to it. These enable it to be located on the Internet. These include MX records, which direct the domain’s mail flow. <br />
Each and every MX record points to an email server that should be configured to process all emails for that domain. <br />
There’s typically one record that points to a Primary Server, then additional records that point to one or more backup servers. <br />
For users to send and receive email, their domain's MX records must point to a server that can process their mail.<br />
<br />
== Where are my MX records? ==<br />
<br />
Your authoritative MX records are on your DNS Service Provider Server. When you change the MX record on your DNS Service Provider, other servers will make copies of these updated MX records over time.<br />
<br />
== How long do MX record updates take? ==<br />
<br />
MX record updates are not immediate. After you've updated your MX records, it will take a while for every sender to use the new MX records. <br />
<br />
== Will I lose mail after changing MX records? ==<br />
<br />
No. As long as you enter the MX records correctly, you won't lose any MX email. While your MX records are changing over, some mail will be delivered using your old MX information, and some mail will be delivered using your new MX information, but all of it will be delivered.<br />
<br />
== What happens if I type the wrong information into the MX record? ==<br />
<br />
If you type the incorrect delivery information in the MX record, some mail will bounce. The sender will receive a notice that the mail wasn't delivered. If this happens, correct the MX records as soon as possible. Some mail may still bounce for a period of time, but the sooner you update the MX records to the correct setting, the fewer messages will bounce.<br />
<br />
== What happens when I update my MX records? ==<br />
<br />
Once you update your MX records, mail will start flowing to the cloud service (After your old previous TTL (Time To Live in seconds) has expired).</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXaaS_FAQ&diff=14600OXaaS FAQ2013-05-21T07:50:50Z<p>Holgi: /* What happens when I update my MX records? */</p>
<hr />
<div>= OX Cloud Service - Technical FAQ =<br />
<br />
== Can I create my users in the default domain and change later to my own domain? ==<br />
<br />
Yes, you can create the users and add aliases for another domain later.<br />
<br />
== What is an MX record? ==<br />
<br />
An MX record tells senders where to send email for your domain.<br />
<br />
When you have a domain registered, there are several DNS records assigned to it. These enable it to be located on the Internet. These include MX records, which direct the domain’s mail flow. <br />
Each and every MX record points to an email server that should be configured to process all emails for that domain. <br />
There’s typically one record that points to a Primary Server, then additional records that point to one or more backup servers. <br />
For users to send and receive email, their domain's MX records must point to a server that can process their mail.<br />
<br />
== Where are my MX records? ==<br />
<br />
Your authoritative MX records are on your DNS Service Provider Server. When you change the MX record on your DNS Service Provider, other servers will make copies of these updated MX records over time.<br />
<br />
== How long do MX record updates take? ==<br />
<br />
MX record updates are not immediate. After you've updated your MX records, it will take a while for every sender to use the new MX records. <br />
<br />
== Will I lose mail after changing MX records? ==<br />
<br />
No. As long as you enter the MX records correctly, you won't lose any MX records. While your MX records are changing over, some mail will be delivered using your old MX information, and some mail will be delivered using your new MX information, but all of it will be delivered.<br />
<br />
== What happens if I type the wrong information into the MX record? ==<br />
<br />
If you type the incorrect delivery information in the MX record, some mail will bounce. The sender will receive a notice that the mail wasn't delivered. If this happens, correct the MX records as soon as possible. Some mail may still bounce for a period of time, but the sooner you update the MX records to the correct setting, the fewer messages will bounce.<br />
<br />
== What happens when I update my MX records? ==<br />
<br />
Once you update your MX records, mail will start flowing to the cloud service (After your old previous TTL (Time To Live in seconds) has expired).</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXaaS_FAQ&diff=14592OXaaS FAQ2013-05-20T11:29:30Z<p>Holgi: </p>
<hr />
<div>= OX Cloud Service - Technical FAQ =<br />
<br />
== Can I create my users in the default domain and change later to my own domain? ==<br />
<br />
Yes, you can create the users and add aliases for another domain later.<br />
<br />
== What is an MX record? ==<br />
<br />
An MX record tells senders where to send email for your domain.<br />
<br />
When you have a domain registered, there are several DNS records assigned to it. These enable it to be located on the Internet. These include MX records, which direct the domain’s mail flow. <br />
Each and every MX record points to an email server that should be configured to process all emails for that domain. <br />
There’s typically one record that points to a Primary Server, then additional records that point to one or more backup servers. <br />
For users to send and receive email, their domain's MX records must point to a server that can process their mail.<br />
<br />
== Where are my MX records? ==<br />
<br />
Your authoritative MX records are on your DNS Service Provider Server. When you change the MX record on your DNS Service Provider, other servers will make copies of these updated MX records over time.<br />
<br />
== How long do MX record updates take? ==<br />
<br />
MX record updates are not immediate. After you've updated your MX records, it will take a while for every sender to use the new MX records. <br />
<br />
== Will I lose mail after changing MX records? ==<br />
<br />
No. As long as you enter the MX records correctly, you won't lose any MX records. While your MX records are changing over, some mail will be delivered using your old MX information, and some mail will be delivered using your new MX information, but all of it will be delivered.<br />
<br />
== What happens if I type the wrong information into the MX record? ==<br />
<br />
If you type the incorrect delivery information in the MX record, some mail will bounce. The sender will receive a notice that the mail wasn't delivered. If this happens, correct the MX records as soon as possible. Some mail may still bounce for a period of time, but the sooner you update the MX records to the correct setting, the fewer messages will bounce.<br />
<br />
== What happens when I update my MX records? ==<br />
<br />
Once you update your MX records, mail will start flowing through the message security service. After your old previous TTL (Time To Live in seconds) has expired, all your mail flows through the message security service. <br />
security service.</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXaaS_FAQ&diff=14569OXaaS FAQ2013-05-16T11:59:35Z<p>Holgi: /* How can I add MX records to my domain? */</p>
<hr />
<div>= OX Cloud Service - Technical FAQ =<br />
<br />
== Can I create my users in the default domain and change later to my own domain? ==<br />
<br />
Yes, you can create the users and add aliases for another domain later.<br />
<br />
== What are MX records for? ==<br />
<br />
MX records are needed for email senders to identify where the mails should go to.<br />
<br />
== Do I need to update MX records? ==<br />
<br />
If you want to receive mails for your own domain in the ox cloud service, the domain MX records must point to the service<br />
<br />
== How can I add MX records to my domain? ==<br />
<br />
You need to ask the DNS administrator who is in control of the domain configuration to perform the change.<br />
<br />
== Which MX records do i need to add? ==<br />
<br />
Please follow instructions within Parallels. The needed MX records are listed when creating a App Suite resource.</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXaaS_FAQ&diff=14568OXaaS FAQ2013-05-16T11:59:09Z<p>Holgi: /* Which MX records do i need to add? */</p>
<hr />
<div>= OX Cloud Service - Technical FAQ =<br />
<br />
== Can I create my users in the default domain and change later to my own domain? ==<br />
<br />
Yes, you can create the users and add aliases for another domain later.<br />
<br />
== What are MX records for? ==<br />
<br />
MX records are needed for email senders to identify where the mails should go to.<br />
<br />
== Do I need to update MX records? ==<br />
<br />
If you want to receive mails for your own domain in the ox cloud service, the domain MX records must point to the service<br />
<br />
== How can I add MX records to my domain? ==<br />
<br />
You need to ask the DNS administrator which hosts the domain configuration to perform the change.<br />
<br />
== Which MX records do i need to add? ==<br />
<br />
Please follow instructions within Parallels. The needed MX records are listed when creating a App Suite resource.</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OXaaS_FAQ&diff=14563OXaaS FAQ2013-05-16T11:47:15Z<p>Holgi: </p>
<hr />
<div>= OX Cloud Service - Technical FAQ =<br />
<br />
== Can i create my users in the default domain and change later to my own domain? ==<br />
<br />
Yes, you can create the users and add aliases for another domain later.<br />
<br />
== What are MX records for? ==<br />
<br />
MX records are needed for email senders to identify where the mails should go to.<br />
<br />
== Do i need to update MX records? ==<br />
<br />
If you want to receive mails for your own domain in the ox cloud service, the domain MX records must point to the service<br />
<br />
== How can i add MX records to my domain? ==<br />
<br />
You need to ask the DNS administrator which hosts the domain configuration to perform the change.<br />
<br />
== Which MX records do i need to add? ==<br />
<br />
Please follow instructions within the POA frontend. The needed MX records are listed when creating a App Suite resource</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Oxcs_bundles_install&diff=13283Oxcs bundles install2013-04-08T16:01:23Z<p>Holgi: </p>
<hr />
<div>= Open-Xchange oxcs package =<br />
<br />
The oxcs package provides a bundle for authentiation, provisioning and proxy auth. This package is for special usage. If you do not know what oxcs is, you can stop reading here.<br />
<br />
== Setup ==<br />
<br />
{{InstallPlugin|pluginname=open-xchange-oxcs|sopath=private/4aea518e3cc15a687d6ce682dfef9a5b}}<br />
<br />
== Configuration == <br />
<br />
=== Authentication plugin ===<br />
<br />
oxcs-authentication.properties<br />
<br />
# URL of the LDAP server to connect to for authenticating users.<br />
# ldaps is supported.<br />
com.openexchange.authentication.oxcs.url= ldap://somehost:389<br />
<br />
# Timeouts are useful to get quick responses for login requests. This timeout is <br />
# used if a new connection is established.<br />
com.openexchange.authentication.oxcs.connect.timeout=10000<br />
<br />
# This timeout only works since Java 6 SE to time out waiting for a response.<br />
com.openexchange.authentication.oxcs.read.timeout=10000<br />
<br />
# HTTP Header from which the brand name is fetched<br />
com.openexchange.authentication.oxcs.header=host<br />
<br />
# Regex to validate host HTTP Header value<br />
com.openexchange.authentication.oxcs.host.regex= [0-9a-zA-Z.]*<br />
<br />
#Regex to validate user name<br />
com.openexchange.authentication.oxcs.user.regex= [0-9a-zA-Z.@]*<br />
<br />
=== Proxy Servlet ===<br />
<br />
oxcs-proxy-servlet.properties<br />
<br />
# URL of the LDAP server to connect to for authenticating users.<br />
# ldaps is supported.<br />
com.openexchange.oxcs.proxy.servlet.url=ldap://somehost:389<br />
<br />
# Timeouts are useful to get quick responses for login requests. This timeout is<br />
# used if a new connection is established.<br />
com.openexchange.oxcs.proxy.servlet.connect.timeout=10000<br />
<br />
# This timeout only works since Java 6 SE to time out waiting for a response.<br />
com.openexchange.oxcs.proxy.servlet.read.timeout=10000<br />
<br />
# Regex to validate brandName value<br />
com.openexchange.oxcs.proxy.servlet.brandName.regex= [0-9a-zA-Z.]*<br />
<br />
#Regex to validate user name<br />
com.openexchange.oxcs.proxy.servlet.uid.regex= [0-9a-zA-Z.@]*<br />
<br />
=== Provisioning bundle===<br />
<br />
oxcs-provisioning.properties<br />
<br />
# ldap server url<br />
com.openexchange.oxcs.provisioning.ldapurl=ldap://somehost:389<br />
<br />
# admin dn<br />
com.openexchange.oxcs.provisioning.admindn=cn=oxadmin,o=oxcs<br />
<br />
# admin dn password<br />
com.openexchange.oxcs.provisioning.adminsecret= yourpassword<br />
<br />
# tree for brands<br />
com.openexchange.oxcs.provisioning.branddn=ou=brands,o=oxcs<br />
<br />
# tree for other stuff like mailstores<br />
com.openexchange.oxcs.provisioning.configdn=ou=config,o=oxcs<br />
<br />
# tree for contexts<br />
com.openexchange.oxcs.provisioning.contextdn=ou=contexts,o=oxcs</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Oxcs_bundles_install&diff=13281Oxcs bundles install2013-04-08T15:43:07Z<p>Holgi: </p>
<hr />
<div>= Open-Xchange oxcs package =<br />
<br />
The oxcs package provides a bundle for authentiation, provisioning and proxy auth.<br />
<br />
== Setup ==<br />
<br />
{{InstallPlugin|pluginname=open-xchange-oxcs|sopath=private/somenotyetavailablenumber}}<br />
<br />
== Configuration == <br />
<br />
=== Authentication plugin ===<br />
<br />
oxcs-authentication.properties<br />
<br />
# URL of the LDAP server to connect to for authenticating users.<br />
# ldaps is supported.<br />
com.openexchange.authentication.oxcs.url= ldap://somehost:389<br />
<br />
# Timeouts are useful to get quick responses for login requests. This timeout is <br />
# used if a new connection is established.<br />
com.openexchange.authentication.oxcs.connect.timeout=10000<br />
<br />
# This timeout only works since Java 6 SE to time out waiting for a response.<br />
com.openexchange.authentication.oxcs.read.timeout=10000<br />
<br />
# HTTP Header from which the brand name is fetched<br />
com.openexchange.authentication.oxcs.header=host<br />
<br />
# Regex to validate host HTTP Header value<br />
com.openexchange.authentication.oxcs.host.regex= [0-9a-zA-Z.]*<br />
<br />
#Regex to validate user name<br />
com.openexchange.authentication.oxcs.user.regex= [0-9a-zA-Z.@]*<br />
<br />
=== Proxy Servlet ===<br />
<br />
oxcs-proxy-servlet.properties<br />
<br />
# URL of the LDAP server to connect to for authenticating users.<br />
# ldaps is supported.<br />
com.openexchange.oxcs.proxy.servlet.url=ldap://somehost:389<br />
<br />
# Timeouts are useful to get quick responses for login requests. This timeout is<br />
# used if a new connection is established.<br />
com.openexchange.oxcs.proxy.servlet.connect.timeout=10000<br />
<br />
# This timeout only works since Java 6 SE to time out waiting for a response.<br />
com.openexchange.oxcs.proxy.servlet.read.timeout=10000<br />
<br />
# Regex to validate brandName value<br />
com.openexchange.oxcs.proxy.servlet.brandName.regex= [0-9a-zA-Z.]*<br />
<br />
#Regex to validate user name<br />
com.openexchange.oxcs.proxy.servlet.uid.regex= [0-9a-zA-Z.@]*<br />
<br />
=== Provisioning bundle===<br />
<br />
oxcs-provisioning.properties<br />
<br />
# ldap server url<br />
com.openexchange.oxcs.provisioning.ldapurl=ldap://somehost:389<br />
<br />
# admin dn<br />
com.openexchange.oxcs.provisioning.admindn=cn=oxadmin,o=oxcs<br />
<br />
# admin dn password<br />
com.openexchange.oxcs.provisioning.adminsecret= yourpassword<br />
<br />
# tree for brands<br />
com.openexchange.oxcs.provisioning.branddn=ou=brands,o=oxcs<br />
<br />
# tree for other stuff like mailstores<br />
com.openexchange.oxcs.provisioning.configdn=ou=config,o=oxcs<br />
<br />
# tree for contexts<br />
com.openexchange.oxcs.provisioning.contextdn=ou=contexts,o=oxcs</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Oxcs_bundles_install&diff=13280Oxcs bundles install2013-04-08T15:39:54Z<p>Holgi: Created page with "= Open-Xchange oxcs package = The oxcs package provides a bundle for authentiation, provisioning and proxy auth. == Setup == {{InstallPlugin|pluginname=open-xchange-oxcs|so..."</p>
<hr />
<div>= Open-Xchange oxcs package =<br />
<br />
The oxcs package provides a bundle for authentiation, provisioning and proxy auth.<br />
<br />
== Setup ==<br />
<br />
{{InstallPlugin|pluginname=open-xchange-oxcs|sopath=private/somenotyetavailablenumber}}<br />
<br />
== Configuration == <br />
<br />
Authentication plugin oxcs-authentication.properties<br />
<br />
# URL of the LDAP server to connect to for authenticating users.<br />
# ldaps is supported.<br />
com.openexchange.authentication.oxcs.url= ldap://somehost:389<br />
<br />
# Timeouts are useful to get quick responses for login requests. This timeout is <br />
# used if a new connection is established.<br />
com.openexchange.authentication.oxcs.connect.timeout=10000<br />
<br />
# This timeout only works since Java 6 SE to time out waiting for a response.<br />
com.openexchange.authentication.oxcs.read.timeout=10000<br />
<br />
# HTTP Header from which the brand name is fetched<br />
com.openexchange.authentication.oxcs.header=host<br />
<br />
# Regex to validate host HTTP Header value<br />
com.openexchange.authentication.oxcs.host.regex= [0-9a-zA-Z.]*<br />
<br />
#Regex to validate user name<br />
com.openexchange.authentication.oxcs.user.regex= [0-9a-zA-Z.@]*<br />
<br />
Proxy Servlet oxcs-proxy-servlet.properties<br />
<br />
# URL of the LDAP server to connect to for authenticating users.<br />
# ldaps is supported.<br />
com.openexchange.oxcs.proxy.servlet.url=ldap://somehost:389<br />
<br />
# Timeouts are useful to get quick responses for login requests. This timeout is<br />
# used if a new connection is established.<br />
com.openexchange.oxcs.proxy.servlet.connect.timeout=10000<br />
<br />
# This timeout only works since Java 6 SE to time out waiting for a response.<br />
com.openexchange.oxcs.proxy.servlet.read.timeout=10000<br />
<br />
# Regex to validate brandName value<br />
com.openexchange.oxcs.proxy.servlet.brandName.regex= [0-9a-zA-Z.]*<br />
<br />
#Regex to validate user name<br />
com.openexchange.oxcs.proxy.servlet.uid.regex= [0-9a-zA-Z.@]*<br />
<br />
provisioning oxcs-provisioning.properties<br />
<br />
<br />
# ldap server url<br />
com.openexchange.oxcs.provisioning.ldapurl=ldap://somehost:389<br />
<br />
# admin dn<br />
com.openexchange.oxcs.provisioning.admindn=cn=oxadmin,o=oxcs<br />
<br />
# admin dn password<br />
com.openexchange.oxcs.provisioning.adminsecret= yourpassword<br />
<br />
# tree for brands<br />
com.openexchange.oxcs.provisioning.branddn=ou=brands,o=oxcs<br />
<br />
# tree for other stuff like mailstores<br />
com.openexchange.oxcs.provisioning.configdn=ou=config,o=oxcs<br />
<br />
# tree for contexts<br />
com.openexchange.oxcs.provisioning.contextdn=ou=contexts,o=oxcs</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OX6:Gui_path&diff=11952OX6:Gui path2012-11-12T08:01:05Z<p>Holgi: /* GUI settings */</p>
<hr />
<div>==== GUI settings ====<br />
This table shows the possible gui settings stored in /gui. The settings are stored in a javascript object notation (JSON) which is directly computed by the GUI. Information about JSON can be found in the [[HTTP_API]]. Per default, this object is not existent upon user creation and is stored by the GUI after the first logout. This object then can be manipulated through the RMI interface (as well as on the command line). It is not necessary to define all settings (inner objects), missing ones will be added by the GUI automatically. When settings should be changed after a user has logged in, remember that there might be user defined settings which should not be touched and kept. This also means if the GUI settings of a user should be reset, this can be done by deleting the whole object.<br />
<br />
Please note: Any stored gui settings object will get overwritten with that operation!<br />
<br />
{| id="gui_path" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''Gui settings'''<br />
|-<br />
! name !! type !! value !! comment<br />
|-<br />
| infostore || Object || [[#infostore object|infostore object]] || infostore settings<br />
|-<br />
| mail || Object || [[#mail object|mail object]] || mail settings<br />
|-<br />
| portal || Object || [[#portal object|portal object]] || portal layout and content<br />
|- <br />
| global || Object || [[#global object|global object]] || timestamp settings and global settings<br />
|-<br />
| menu || Object || [[#menue object|menue object]] || menu iteration<br />
|-<br />
| theme || Object || [[#theme object|theme object]] || default theme and path<br />
|- <br />
| effects || Object || [[#effects object|effects object]] || hover and global effects<br />
|- <br />
| tasks || Object || [[#tasks objects|tasks objects]] || tasks settings <br />
|- <br />
| FolderTreeState || Object || [[#foldertree object|foldertree object]] || holds the folder tree state<br />
|-<br />
| contacts || Object || [[#contacts object|contacts object]] || contacts settings <br />
|-<br />
| calendar || Object || [[#calendar object|calendar object]] || calendar settings <br />
|-<br />
|}<br />
<br />
====Settings for the infostore module====<br />
This table contains the settings for the GUI's infostore<br />
{| id="infostore object" style="width:100%" cellspacing="0" border="1" align="bottom" <br />
|+'''infostore object'''<br />
|-<br />
! name !! type !! values !! comment<br />
|-<br />
| view || value || infostore/(list,split) || infostore view<br />
|}<br />
<br />
====Settings for the E-Mail module====<br />
This tables contains the settings for the E-Mail module.<br />
{| id="mail object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''mail object'''<br />
|-<br />
! name !! type !! values !! comment<br />
|-<br />
| auto_save_drafts || Number || 0,1,3,5,10,15,30|| time in minutes, 0 for disabled<br />
|-<br />
| htmlmessage || Boolean|| true,false || show email as html or plain text<br />
|-<br />
| signatures || Array || [[#signature objects|signature objects]] || array of signature objects<br />
|-<br />
| view || String || mail/(list,hsplit,vsplit)/unthreaded || mail view<br />
|-<br />
| view spam || String || mail/(list,hsplit,vsplit)/unthreaded || mail view for spam folder<br />
|-<br />
| autocomplete || Boolean || true,false || autocomplete functions<br />
|-<br />
| fullmailheader || Boolean || true,false || show complete mail header<br />
|-<br />
| notifyacknoledge ||Boolean || true,false || notify on read acknowledgment<br />
|-<br />
| newmail_options || Object || [[#newmail_options objects|newmail_options objects]] || object for the new email window settings<br />
|-<br />
| formatmessage || String || ALTERNATIVE,TEXT/HTML,TEXT/PLAIN || email format<br />
|}<br />
<br />
<br />
{| id="newmail_options objects" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''newmail_options objects'''<br />
! name !! type !! values !! comment<br />
|-<br />
| cc || Boolean || true,false || show cc input field<br />
|-<br />
| bcc || Boolean || true,false || show bcc input field<br />
|-<br />
| from || Boolean || true,false || show from input field<br />
|-<br />
| options || Boolean || true,false || show options field<br />
|- <br />
|}<br />
<br />
<br />
{| id="signature objects" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''signature objects'''<br />
! name !! type !! values !! comment<br />
|-<br />
| signature_name || String || name || signature name<br />
|-<br />
| position || String || below,above || where to show the signature in the mail text<br />
|-<br />
| signature_text || String || text || signature text<br />
|-<br />
| signature_default || Boolean || true,false || true only for the default signature<br />
|-<br />
|}<br />
<br />
====Start page settings====<br />
This table contains the possible settings for the start page.<br />
{| id="portal object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''portal object'''<br />
! name !! type !! values !! comment<br />
|-<br />
| externalcontents || Array || [[#externalcontents objects|externalcontents objects]] || array of external content objects (UWA widgeds)<br />
|-<br />
| minicalendar ||Boolean || true,false|| show minicalendar<br />
|-<br />
| internalcontents || Array || [[#internalcontens objects|internalcontents objects]] || array of internal content objects (groupware modules)<br />
|-<br />
| infobox || Boolean || true,false|| show infobox<br />
|-<br />
| tooltip ||Boolean ||true,false || show tooltip<br />
|-<br />
|}<br />
<br />
<br />
{| id="externalcontents objects" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''externalcontents objects'''<br />
! name !! type !! values !! comment<br />
|-<br />
| autorefresh || Boolean || true,false || enable autorefresh for the widget<br />
|-<br />
| title || String || name || widget title<br />
|-<br />
| standalone || Boolean || true,false || widget is standalone<br />
|-<br />
| visible || Boolean || true,false || widget is visible on the portal page<br />
|-<br />
| adj || Object || [[#adj object|adj object]] || position setting of the widget<br />
|-<br />
| url || String || url || widget url<br />
|-<br />
| parameter || Object || parameter object || widget parameters in an object<br />
|-<br />
| id || String || unique id || unique id for the widget<br />
|- <br />
|}<br />
<br />
<br />
{| id="internalcontens objects" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''internalcontens objects'''<br />
! name !! type !! values !! comment<br />
|-<br />
| params || Object || [[#params object|params object]] || widget parameter<br />
|-<br />
| header || Sting || E-Mail,Calendar,InfoStore,Tasks || header name<br />
|-<br />
| visible || Boolean || true,false || show module on the portal<br />
|-<br />
| adj || Object || [[#adj object|adj object]] || position setting of the widget<br />
|- <br />
| external || Boolean || false || only false is implemented<br />
|-<br />
| module || String || mail,calendar,infostore,tasks || internal module name<br />
|-<br />
|}<br />
<br />
<br />
{| id="adj object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''adj object'''<br />
! name !! type !! values !! comment<br />
|-<br />
| hw || Number || 0... || widget height relative to others, 0 for auto<br />
|-<br />
| ww || Number || 0... || widget width relative to others, 0 for auto<br />
|-columns<br />
| y || Number || 0... || vertical position on the start page in rows, 0 for auto<br />
|-<br />
| x || Number || 0... || horizontal position on the start page in columns, 0 for auto<br />
|-<br />
|}<br />
<br />
<br />
{| id="params object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''params object'''<br />
! name !! type !! values !! comment<br />
|-<br />
| limit || Number || 5,10,15,20 || number of shown items in the module<br />
|-<br />
|}<br />
<br />
====global settings====<br />
This table contains the global settings options<br />
{| id="global object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''global object'''<br />
|-<br />
! name !! type !! values !! comment<br />
|-<br />
| confirmtimestamp ||Number || Timestamp || timestamp for the last confirmed/declined appointment<br />
|-<br />
| confirmpopup || Boolean || true,false|| confirmation pop-up for new appointments<br />
|-<br />
| save || Number || 0,1,2 || save layout on logout: 0 no, 1 yes, 2 ask<br />
|-<br />
| autorefresh || Number || 0,5,10,15,30 || time in minutes for GUI autorefresh, 0 for never<br />
|-<br />
| region || Object || [[#region object|region object]] || region settings for time and date formats<br />
|-<br />
| private_categories || String || tag,tag,.. || comma separated list of user defined tags <br />
|}<br />
<br />
<br />
{| id="region object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''region object'''<br />
|-<br />
! name !! type !! values !! Comment<br />
|-<br />
| time || Object || [[#time object|time object]] || object for time defaults<br />
|-<br />
| date || Object || [[#date object|date object]] || object for date defaults<br />
|-<br />
|}<br />
<br />
<br />
{| id="time object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''time object'''<br />
|-<br />
! name !! type !! values !! Comment<br />
|-<br />
| predefined || Number || 0,1 || 0 user defined, 1 language depending<br />
|-<br />
| format || String || HH:mm,"hh:mm a" || a stands for suffix which needs to be true then, too. m is 0-59, mm is 00-59, H is 1-24, HH is 01-24, h is 1-12, hh is 01-12, a is AM/PM.<br />
|-<br />
| format_hour || String || "hh a",HH || a stands for suffix which needs to be true then, too. H is 1-24, HH is 01-24, h is 1-12, hh is 01-12, a is AM/PM.<br />
|-<br />
| format_suffix || Boolean || true,false || add suffix<br />
|-<br />
|}<br />
<br />
<br />
{| id="date object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''date object'''<br />
|-<br />
! name !! type !! values !! Comment<br />
|-<br />
| format_selected_index || Number || id from [[#index|index]] || preselection for the user time format drop down<br />
|-<br />
| separator || String || /,.,- || date separator<br />
|-<br />
| predifined || Number || 0,1 || 0 user defined, 1 language depending<br />
|-<br />
| format || String || value from [[#index|index]] || date format <br />
|-<br />
|}<br />
<br />
<br />
{| id="index" style="width:50%" cellspacing="0" border="1" align="bottom"<br />
|+'''date index'''<br />
|-<br />
! id !! value<br />
|-<br />
| 0 || M/d/yyyy<br />
|-<br />
| 1 || M/d/yy<br />
|-<br />
| 2 || MM/dd/yy<br />
|-<br />
| 3 || MM/dd/yyyy<br />
|-<br />
| 4 || yy/MM/dd<br />
|-<br />
| 5 || dd/MM/yyyy<br />
|-<br />
| 6 || dd/MM/yy<br />
|-<br />
| 7 || dd.MM.yyyy<br />
|-<br />
| 8 || dd.MM.yy<br />
|-<br />
| 9 || d.MM.yy<br />
|-<br />
| 10 || d.M.yy<br />
|-<br />
| 11 || d.M.yyyy<br />
|-<br />
| 12 || yyyy-MM-dd<br />
|-<br />
| 13 || dd-MMM-yy<br />
|-<br />
|}<br />
<br />
===menuiteration===<br />
This object holds the setting of the pannel <br />
{| id="menue object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''menue object'''<br />
|-<br />
! name !! type !! values !! Comment<br />
|-<br />
| menuiteration || Number || 1,2,3,4,5,6 || highs of the GUI pannel in rows <br />
|-<br />
|}<br />
<br />
===theme settings===<br />
This table shows the setting for the default theme<br />
{| id="theme object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''theme object'''<br />
|-<br />
! name !! type !! values !! Comment<br />
|-<br />
| name || String || <theme name> || name of the default theme <br />
|-<br />
| path ||String || <theme path> || path to the default theme<br />
|-<br />
|}<br />
<br />
===effects object===<br />
the effects object holds the settings for GUI effects like hovers and fading.<br />
{| id="effects object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''effects object'''<br />
|-<br />
! name !! type !! values !! Comment<br />
|-<br />
| global || Boolean || true,false || enable effects<br />
|-<br />
| hover || Object || [[#hover object|hover object]] || includes hover settings for the modules<br />
|-<br />
| fading|| Boolean || true,false || fading<br />
|-<br />
|}<br />
<br />
<br />
{| id="hover object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''hover object'''<br />
|-<br />
! name !! type !! values !! Comment<br />
|-<br />
| speed || Number || 1,2,3 || hover delay, 1 short, 2 normal, 3 long<br />
|-<br />
| calendar || Boolean || true,false || hover for calendar<br />
|-<br />
| contacts || Boolean || true,false || hover for contacts<br />
|-<br />
| portal || Boolean || true,false || hovers on the portal page<br />
|- <br />
| infostore || Boolean || true,false || hover for infostore<br />
|-<br />
| mail || Boolean || true,false || hover for mail <br />
|-<br />
| tasks || Boolean || true,false || hover for tasks<br />
|-<br />
|}<br />
<br />
===setting for tasks===<br />
This objects holds the settings for tasks<br />
{| id="tasks objects" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''tasks objects'''<br />
! name !! type !! values !! Comment<br />
|-<br />
| interval || Number || 5,10,15,20,30,60 || interval for reminder<br />
|-<br />
| gridsort || String || asc || how tasks get sorted<br />
|-<br />
| view || String || tasks/(split,list) || task view<br />
|-<br />
|}<br />
<br />
===foldertree object===<br />
this is an internal gui object to store the folder tree on logout. This<br />
object should not be modified.<br />
{| id="foldertree object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''foldertree object'''<br />
! name !! type !! values !! Comment<br />
|-<br />
| FolderTreeState || Object || foldertree object || folder tree state on GUI logout, you should not touch <br />
|-<br />
|}<br />
<br />
<br />
===Settings for contacts===<br />
the contacts object holds the settings for the contacts.<br />
{| id="contacts object" style="width:100%" cellspacing="0" border="1" align="bottom"<br />
|+'''contacts object'''<br />
! name !! type !! values !! Comment<br />
|-<br />
| gridsort ||String || asc || Sorting of contacts<br />
|-<br />
| cardsToViewPerColumn || String || auto,4,5,6,7|| displayed cards per column <br />
|-<br />
| view || String || contacts/(cards,phonelist) || card view<br />
|-<br />
|}<br />
<br />
===settings for the calendar===<br />
The calendar object stores the settings for the calendar.<br />
{| id="calendar object" style="width:100%" cellspacing="0" border="1" align="bottom" <br />
|+'''calendar object'''<br />
! name !! type !! values !! Comment<br />
|-<br />
| workweek ||Object || [[#workweek object|workweek object]] || settings for the workweek <br />
|-<br />
| endtime || Number || 0..23 || calendar display end time in hours<br />
|-<br />
| teams || Array || [[#teams object|teams object]] || Array of teams<br />
|-<br />
| allfolders ||Boolean || true,false || activate "Show all my appointments from all calendars"<br />
|-<br />
| starttime || Number || 0..23 || calendar display end time in hours<br />
|-<br />
| interval || Number || 5,10,15,20,30,60 || calendar resolution<br />
|-<br />
| day || Object || [[#day object|day object]] || settings for day view <br />
|-<br />
| view || String || calendar/(calendar,team,list)/(day,workweek,month,week,custom,) || Calendar view, for team, groupware functionality must be available. '''Deprecated''', see views.<br />
|-<br />
| views || Object || [[#views object|views object]] || default calendar views<br />
|-<br />
| custom || Object || [[#custom object|custom object]] || setting for the custom view<br />
|-<br />
|}<br />
<br />
<br />
{| id="workweek object" style="width:100%" cellspacing="0" border="1" align="bottom" <br />
|+'''workweek object'''<br />
! name !! type !! values !! Comment<br />
|-<br />
| countdays || Number || 1,2,3,4,5,6,7 || Number of days in work week<br />
|-<br />
| numberofappointments || Number || 1,2,3,4,5,6,7,8 || Number of concurrent appointments shown in workweek view<br />
|-<br />
| startday || Number || 0,1,2,3,4,5,6 || 0 Sunday,...,6 Saturday <br />
|-<br />
|}<br />
<br />
<br />
{| id="day object" style="width:100%" cellspacing="0" border="1" align="bottom" <br />
|+'''day object'''<br />
! name !! type !! values !! Comment<br />
|-<br />
| numberofappointments || Number || 1,2,3,4,5,6,7,8 || Number of concurrent appointments shown in day view<br />
|-<br />
|}<br />
<br />
<br />
{| id="views object" style="width: 100%" cellspacing="0" border="1" align="bottom"<br />
|+'''views object'''<br />
! name !! type !! values !! Comment<br />
|-<br />
| shared || Boolean || true, false || Whether all views share the same default time range or not.<br />
|-<br />
| view || String || "calendar", "team", "list" || Default view.<br />
|-<br />
| calendar || String || "day", "workweek", "month", "week", "custom" || Default time range for the calendar view.<br />
|-<br />
| team || String || "day", "workweek", "month", "week", "custom" || Default time range for the team view.<br />
|-<br />
| list || String || "day", "workweek", "month", "week", "custom" || Default time range for the list view.<br />
|-<br />
|}<br />
<br />
<br />
{| id="custom object" style="width:100%" cellspacing="0" border="1" align="bottom" <br />
|+'''custom object'''<br />
! name !! type !! values !! Comment<br />
|-<br />
| numberofappointments || Number || 1,2,3,4,5,6,7,8 || Number of concurrent appointments shown in day view<br />
|-<br />
| countdays || Number || 1,2,3,4,5,6,7 || Number of days in work week<br />
|-<br />
|}<br />
<br />
<br />
{| id="teams object" style="width:100%" cellspacing="0" border="1" align="bottom" <br />
|+'''teams object'''<br />
! name !! type !! values !! Comment<br />
|-<br />
| team_default || Boolean || true,false || true for the default team<br />
|-<br />
| name || string || name || name for the team<br />
|-<br />
| children || Array || [[#children objects|children objects]] || Array of children objects, childrens are users that belong to the team<br />
|- <br />
|}<br />
<br />
<br />
{| id="children objects" style="width:100%" cellspacing="0" border="1" align="bottom" <br />
|+'''children object'''<br />
! name !! type !! values !! Comment<br />
|-<br />
| id || Number || userid || user id of the team member<br />
|-<br />
| display _name || String || display name || display name of the team member<br />
|-<br />
| type || Number || 1 || only 1 implemented<br />
|-<br />
|}<br />
<br />
===example /path, saved from a fresh user directly after the first login/logout===<br />
/path={"calendar":{"view":"calendar/calendar/day","day":{"numberofappointments":4},"workweek":{"countdays":5,"startday":1,"numberofappointments":2},"starttime":8,"allfolders":true,"custom":{"countdays":3,"numberofappointments":3},"endtime":18,"interval":30},"FolderTreeState":{"folder_tree$1":{"folder_tree$default":{"folder_tree$default.INBOX":{}},"folder_tree$25":{}},"folder_tree$9":{"folder_tree$10":{"folder_tree$28":{}}}},"contacts":{"view":"contacts/cards","cardsToViewPerColumn":"auto","gridsort":"asc"},"theme":{"path":"default","name":"Default"},"portal":{"infobox":true,"internalcontents":[{"params":{"limit":5},"header":"E-Mail","visible":true,"adj":{"hw":1,"ww":1,"y":0,"x":1},"external":false,"module":"mail"},{"params":{"limit":5},"header":"Calendar","visible":true,"adj":{"hw":1,"ww":1,"y":0,"x":0},"external":false,"module":"calendar"},{"params":{"limit":5},"header":"InfoStore","visible":true,"adj":{"hw":1,"ww":1,"y":1,"x":0},"external":false,"module":"infostore"},{"params":{"limit":5},"header":"Tasks","visible":true,"adj":{"hw":1,"ww":1,"y":1,"x":1},"external":false,"module":"tasks"}],"tooltip":false,"externalcontents":[],"minicalendar":true},"infostore":{"view":"infostore/split"},"effects":{"hover":{"calendar":true,"speed":2,"contacts":true,"portal":true,"infostore":true,"mail":true,"tasks":true},"global":false,"fading":false},"mail":{"newmail_options":{"cc":true,"bcc":false,"from":true,"options":false},"view":"mail/hsplit/unthreaded","formatmessage":"ALTERNATIVE","notifyacknoledge":true,"autocomplete":true,"auto_save_drafts":3,"signatures":[],"fullmailheader":true,"htmlmessage":true},"tasks":{"view":"tasks/split","gridsort":"asc","interval":30},"menu":{"menuiteration":4},"private_categories":"","global":{"autorefresh":10,"save":1,"confirmtimestamp":1216928454103,"confirmpopup":true}}<br />
<br />
for example, here is how it would work on the command line:<br />
/opt/open-xchangen/sbin/changeuser -c 71 -i 5 --addguipreferences \<br />
'/gui={"calendar":{"view":"calendar/calendar/day","day":{"numberofappointments":4},\<br />
"workweek":{"countdays":5,"startday":1,"numberofappointments":2},"starttime":8,"allfolders":true,\ <br />
"custom":{"countdays":3,"numberofappointments":3},"endtime":18,"interval":30},\ <br />
"FolderTreeState":{"folder_tree$1":{"folder_tree$default":{"folder_tree$default.INBOX":{}},\ <br />
"folder_tree$25":{}},"folder_tree$9":{"folder_tree$10":{"folder_tree$28":{}}}},\ <br />
"contacts":{"view":"contacts/cards","cardsToViewPerColumn":"auto","gridsort":"asc"},\ <br />
"theme":{"path":"default","name":"Default"},\ "portal":{"infobox":true,\ <br />
"internalcontents":[{"params":{"limit":5},"header":"E-Mail","visible":true,\ <br />
"adj":{"hw":1,"ww":1,"y":0,"x":1},"external":false,"module":"mail"},\ <br />
{"params":{"limit":5},"header":"Calendar","visible":true,\ <br />
"adj":{"hw":1,"ww":1,"y":0,"x":0},\ "external":false,"module":"calendar"},\ <br />
{"params":{"limit":5},"header":"InfoStore","visible":true,\ <br />
"adj":{"hw":1,"ww":1,"y":1,"x":0},"external":false,"module":"infostore"},\ <br />
{"params":{"limit":5},"header":"Tasks","visible":true,\ <br />
"adj":{"hw":1,"ww":1,"y":1,"x":1},"external":false,"module":"tasks"}],\ <br />
"tooltip":false,"externalcontents":[],"minicalendar":true},\ <br />
"infostore":{"view":"infostore/split"},\ <br />
"effects":{"hover":{"calendar":true,"speed":2,"contacts":true,\ <br />
"portal":true,"infostore":true,"mail":true,"tasks":true},\ <br />
"global":false,"fading":false},\ <br />
"mail":{"newmail_options":{"cc":true,"bcc":false,"from":true,"options":false},\ <br />
"view":"mail/hsplit/unthreaded","formatmessage":"ALTERNATIVE",\ <br />
"notifyacknoledge":true,"autocomplete":true,"auto_save_drafts":3,\ <br />
"signatures":[],"fullmailheader":true,"htmlmessage":true},\ <br />
"tasks":{"view":"tasks/split","gridsort":"asc","interval":30},\ <br />
"menu":{"menuiteration":4},"private_categories":"",\ <br />
"global":{"autorefresh":10,"save":1,"confirmtimestamp":1216928454103,\ <br />
"confirmpopup":true}}'<br />
<br />
[[Category: OX6]]</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OX6:Update_to_6_22&diff=11705OX6:Update to 6 222012-10-10T12:56:50Z<p>Holgi: /* Configuration Changes */</p>
<hr />
<div>= Open-Xchange Server v6.22 - Update and Installation =<br />
<br />
The new Open-Xchange Server v6.22 is the first step on the way to the next generation Open-Xchange App Suite. The update provides a new and improved Open-Xchange Server backend with enhancements for both generations. <br />
<br />
Especially on the backend, Open-Xchange implemented various changes and improvements like a new and clear structure for the configuration files and packages, an improved exception framework, unified OSGi, etc.<br />
<br />
On this page you can find an overview of the differences between the Open-Xchange 6.20.x and the Open-Xchange v.6.22 backend. There are new requirements, update guides, and multiple other changes.<br />
<br />
'''Please read the different articles and manuals regarding the update. We encourage administrators of Open-Xchange 6 v6.20.x to install this update. The further feature development will be based on v6.22'''<br />
<br />
'''Custom Packages: Unfortunately custom packages will not be ready with 6.22 release. If you have custom packages provided by Open-Xchange, please discuss with your Open-Xchange contact when these packages will be available for 6.22.'''<br />
<br />
'''Custom Plugins: If you have custom plugins written by yourself which depend on Open-Xchange Server OSGI bundles please check the information about necessary code and packaging changes below.'''<br />
<br />
'''Furthermore, Open-Xchange provides the complete v6.22 materials as a document which is available here: [http://software.open-xchange.com/OX6/6.22/doc Software Repository].'''<br />
<br />
= Supported Update Path =<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!align="left" |Old version<br />
!align="left" |New version<br />
!align="left" |Update supported<br />
|-<br />
|v6.20.7<br />
|v6.22.0<br />
|[[File:check.gif]]<br />
|-<br />
|v6.20.x<br />
|v6.22.x<br />
|[[File:cross.gif]](1)<br />
|-<br />
|v6.18.x<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|Older Versions<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|}<br />
<br />
(1) If you don't [http://oxpedia.org/wiki/index.php?title=UpdatingOXPackages update to 6.20.7] before you start the 6.22 update, it is possible that some important scripts have not run on your system(s) and configuration options might be missing. If you have already updated to 6.22 from an v6.20 version earlier than 6.20.7 and you are experiencing problems, please contact Open-Xchange Support.<br />
<br />
<br />
= Rollback =<br />
<br />
Please note that after updating to 6.22 there is no way to get back to an earlier version of Open-Xchange. Please make sure that you have a full backup of your Open-Xchange installation(s).<br />
<br />
<br />
= Cluster setups =<br />
<br />
If you have several Open-Xchange systems in a cluster setup, you need to shut down all of them before attempting the upgrade. Parallel operation of v6.20 and v6.22 nodes in one cluster may lead to unforeseen errors and is not supported even for a short time.<br />
<br />
<br />
= Supported Server / Client Combinations =<br />
<br />
== Client Support ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!align="left" |Open-Xchange GUI / Clients<br />
!align="left" |Open-Xchange Server<br />
!align="left" |Supported<br />
|-<br />
|v6.22.x<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|v6.20.x<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|v6.18.x<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|Older versions of Open-Xchange GUI<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|OXtender 2 for Microsoft Outlook<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|OXtender for Business Mobility<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|Open-Xchange Web Interface v1.2<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|OXtender for cPanel<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|OXtender 1 for Microsoft Outlook<br />
|<br />
|[[File:cross.gif]]<br />
|-<br />
|OXtender for SyncML<br />
|<br />
|[[File:cross.gif]]<br />
|-<br />
|Parallels Operations Automation<br />
|<br />
|[[File:cross.gif]] (Supported with upcoming 6.22.1, Q4 2012)<br />
|-<br />
|}<br />
<br />
== Open-Xchange Database Support (Parallel Setup) ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!align="left" |Database<br />
!align="left" |New Version<br />
!align="left" |Supported<br />
|- style="vertical-align:top"<br />
|rowspan="5" | Open-Xchange Database<br />
|v6.22.x<br />
|[[File:check.gif]] (after running v6.22 update tasks)<br />
|-<br />
|v6.20.7<br />
|[[File:check.gif]] (after running v6.22 update tasks)<br />
|-<br />
|v6.20.x<br />
|[[File:check.gif]] (after running v6.22 update tasks)<br />
|-<br />
|v6.18.x<br />
|[[File:cross.gif]]<br />
|-<br />
|Older Versions<br />
|[[File:cross.gif]]<br />
|-<br />
|}<br />
<br />
<br />
= Improvements Overview of 6.20.x to 6.22 Backend =<br />
<br />
Open-Xchange provides an overview page regarding the main improvements of the new v6.22. Please have a look at [http://oxpedia.org/wiki/index.php?title=Backend_Improvements_6_22 Backend Improvements 6.22]<br />
<br />
<br />
= Configuration Changes =<br />
<br />
== Configuration file location ==<br />
In v6.22 we simplified the directory tree containing all configuration files to not longer include the subdirectories <code>admindaemon</code>, <code>common</code> and <code>groupware</code>.<br />
<br />
For more details see the packaging changes [http://oxpedia.org/wiki/index.php?title=6.22_Packaging_Changes overview page].<br />
<br />
'''If you have any configuration management or templating system for automatic deployment of OX instances in place, theses changes mean that you will have to adapt that system to the new configuration file tree.'''<br />
<br />
== Other configuration changes ==<br />
<br />
* push.properties has been renamed to push-udp.properties<br />
* the configuration of theme packages has changed. This is also described on the packaging changes [http://oxpedia.org/wiki/index.php?title=6.22_Packaging_Changes overview page].<br />
* since there is no administration deamon running any more, all, provisioning and general logs are written to one singel logfile<br />
<br />
= Packages changes =<br />
<br />
With v6.22 we have significantly reduced the number of packages necessary to install Open-Xchange Server. We encourage administrators of Open-Xchange v6.20.x to read the article [[6.22_Package_Changes|Package changes with 6.22]] before updating to Open-Xchange v6.22. This article describes in detail which new packages correspond to which old ones.<br />
<br />
The changes in the package structure should be completely transparent to the system administrator and are handled by standard package management tools during the upgrade.<br />
<br />
'''If you have any custom system for automatic installation and deployment of OX instances in place, it is very likely that you need to adapt your system to the new package structure.'''<br />
<br />
<br />
= Dropped packages =<br />
<br />
The package open-xchange-upsell-generic has been dropped for this release. An update will replace the package with open-xchange-upsell-multiple which offers the same features. The configuration needs to be converted though:<br />
<br />
In upsell.properties:<br />
com.openexchange.upsell.multiple.method=direct<br />
com.openexchange.upsell.multiple.method.static.shop_redir_url=URL_TO_STATIC_HTML_DOCUMENT<br />
<br />
The URL must point to an HTML document which holds the content previously defined in upsell.properties' modules/com.openexchange.upsell.generic/html.<br />
<br />
<br />
= Default languages =<br />
<br />
Starting with v6.22 the localization files for German, French and British English are no longer part of the core packages. This change was necessary to allow customers to uninstall these languages when they are not needed. If you want to offer German, French and/or British English to your customers as language option, you need to install the corresponding packages after the update. Please see the [http://oxpedia.org/wiki/index.php?title=Update_to_6_22#Update_Guide_.28supported_packages.29 update guide] for your distribution for details.<br />
<br />
<br />
= No separate admin daemon =<br />
<br />
Admin functionality will now be a part of the Groupware Process as optional bundle. This means the former, as root running, Admin daemon will no longer exist.<br />
<br />
Admin functionality is only available when the corresponding packages are installed.<br />
<br />
As a result of this change, there is now only one startup script which starts the Open-Xchange Server. The new unified process is called <code>open-xchange</code>.<br />
<br />
Following are potential pitfalls :<br />
* ox-admin-scriptconf.sh is merged to /opt/open-xchange/etc/ox-scriptconf.sh, check NRFILES and Memory setting to fit the environment.<br />
* If /etc/security/limits.conf does set limits for the open-xchange user, those need to be adopted.<br />
* administrative tasks are now executed as user open-xchange (for example the filestore mount is no longer accessed as root).<br />
* The new, unified process is not able to open tcp sockets below 1024.<br />
* Separate monitoring for the admin process is no longer needed.<br />
* admindaemon used to limit its network usage to IPv4 which is not the case anymore. This means that proper network setup is needed to avoid DNS and routing issues caused by dual stack usage.<br />
<br />
<br />
= Changes to programming APIs which might break custom plugins to the OX Server =<br />
<br />
* Please see [http://oxpedia.org/wiki/index.php?title=Backend_Improvements_6_22 Backend Improvements 6.22] for changes to the v6.22 core.<br />
* If you have custom plugins written by yourself which depend on Open-Xchange Server OSGI bundles, check the pages [[6.22_Packaging_Changes|v6.22 Packaging Changes]] and [[6.22_Necessary_Code_Changes|v6.22 Necessary Code Changes]] for changes you might need to do.<br />
<br />
<br />
= Update Guide for Open-Xchange v6.22 =<br />
<br />
== Update Guide (supported packages) ==<br />
<br />
To update the software to Open-Xchange v6.22, please use the following Update Guides. '''There you can also find information on how to start the groupware with / without admin part, on known issues and manual steps required.'''<br />
<br />
* [[Open-Xchange_620_622_Update_Guide_for_Debian_6.0|Update Guide from 6.20 to 6.22 for Debian GNU/Linux 6.0 (Squeeze)]]<br />
* [[Open-Xchange_620_622_Update_Guide_for_SLES11|Update Guide from 6.20 to 6.22 for SUSE Linux Enterprise Server 11]]<br />
* [[Open-Xchange_620_622_Update_Guide_for_RHEL5|Update Guide from 6.20 to 6.22 for RedHat Enterprise Linux 5]]<br />
* [[Open-Xchange_620_622_Update_Guide_for_RHEL6|Update Guide from 6.20 to 6.22 for RedHat Enterprise Linux 6]]<br />
* [[Open-Xchange_620_622_UpdateGuide_for_CentOS5|Update Guide from 6.20 to 6.22 for CentOS 5]]<br />
* [[Open-Xchange_620_622_Update_Guide_for_CentOS6|Update Guide from 6.20 to 6.22 for CentOS 6]]<br />
<br />
<br />
= Installation Guide for Open-Xchange v6.22 =<br />
<br />
== Quick Installation Guide (supported packages) ==<br />
<br />
To download and install the software, please use the following Installation Guides.<br />
<br />
* [[Open-Xchange_Installation_Guide_for_Debian_6.0_622|Download and Installation Guide for Debian GNU/Linux 6.0 (Squeeze)]]<br />
* [[Open-Xchange_Installation_Guide_for_SLES11_622|Download and Installation Guide for SUSE Linux Enterprise Server 11]]<br />
* [[Open-Xchange_Installation_Guide_for_RHEL5_622|Download and Installation Guide for RedHat Enterprise Linux 5]]<br />
* [[Open-Xchange_Installation_Guide_for_RHEL6_622|Download and Installation Guide for RedHat Enterprise Linux 6]]<br />
* [[Open-Xchange Installation Guide for CentOS 5_622|Download and Installation Guide for CentOS 5]]<br />
* [[Open-Xchange Installation Guide for CentOS 6_622|Download and Installation Guide for CentOS 6]]<br />
<br />
<br />
= Migration from OLOX1 to OLOX2 =<br />
<br />
== Migration Path ==<br />
<br />
Open-Xchange will discontinue the support for OXtender 1 for Microsoft Outlook with the new release v6.22. Additional, at the new backend, the Open-Xchange WebDAV XML API will no longer be officially supported. Open-Xchange will provide an upgrade path to the OXtender 2 for Microsoft Outlook.<br />
<br />
If the user installs the upcoming OLOX1 6.18.19 we will provide the following information to the user when trying to sync against the OX server >= 6.22. Open-Xchange provides via a pop-up window at the product the following migration possibilities:<br />
<br />
* User can use the OXUpdater to install the new version<br />
* User can directly start installing by clicking on a provided link<br />
<br />
If the user closes the pop-up window, the OLOX 1 will be deactivated for the current session and profil. After installing OLOX2 and starting Outlook the user has to select the new OLOX2 profile and the migration is done.<br />
<br />
'''A complete migration path is documented at http://oxpedia.org/wiki/index.php?title=OLOX_Migration'''<br />
<br />
== Known Issues ==<br />
<br />
* After the start of the new OLOX 2 profile, contacts, appointments and tasks will be synchronized<br />
* Per default server configuration, mails older as one year won't be synchronized<br />
* Notice and Journal information won't be synchronized. It is possible to export and import the information via the Outlook functionalities</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OX6:Update_to_6_22&diff=11125OX6:Update to 6 222012-09-14T08:59:09Z<p>Holgi: /* Configuration Changes */</p>
<hr />
<div>= Update and Installation Open-Xchange Server v6.22 =<br />
<br />
The new Open-Xchange Server v6.22 is the first step on the way to the next generation Open-Xchange Server 7. The update provides a new and improved Open-Xchange Server backend with enhancements for both generations. <br />
<br />
Especially on the backend, Open-Xchange implemented various changes and improvements like a new and clear structure for the configuration files and packages, an improved exception framework, unified OSGi, etc.<br />
<br />
On this page you can find an overview of the differences between the Open-Xchange 6.20.x and the Open-Xchange v.6.22 backend. There are new requirements, update guides, and multiple other changes.<br />
<br />
'''Please read the different articles and manuals regarding the update. We encourage administrators of Open-Xchange 6 v6.20.x to install this update. The further feature development will be based on v6.22'''<br />
<br />
'''Furthermore, Open-Xchange provides the complete v6.22 materials as a document which is available here: [http://software.open-xchange.com/OX6/6.22/doc Software Repository].'''<br />
<br />
= Supported Update Path =<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!align="left" |Old version<br />
!align="left" |New version<br />
!align="left" |Update supported<br />
|-<br />
|v6.20.7<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|v6.20.x<br />
|v6.22.x<br />
|[[File:cross.gif]](1)<br />
|-<br />
|v6.18.x<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|Older Versions<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|}<br />
<br />
(1) If you don't [http://oxpedia.org/wiki/index.php?title=UpdatingOXPackages update to 6.20.7] before you start the 6.22 update, it is possible that some important scripts have not run on your system(s) and configuration options might be missing. See HERE for a list of changes that were done during the updates between 6.20.x versions<br />
<br />
= Rollback =<br />
<br />
Please note that after updating to 6.22 there is no way to get back to an earlier version of Open-Xchange. Please make sure that you have a backup. (TODO)<br />
<br />
= Supported Server / Client Combinations =<br />
<br />
== Client Support ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!align="left" |Open-Xchange GUI / Clients<br />
!align="left" |Open-Xchange Server<br />
!align="left" |Supported<br />
|-<br />
|v6.22.x<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|v6.20.x<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|v6.18.x<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|Older versions of Open-Xchange GUI<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|OXtender 2 for Microsoft Outlook<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|OXtender for Business Mobility<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|Open-Xchange Web Interface v1.2<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|OXtender 1 for Microsoft Outlook<br />
|<br />
|[[File:cross.gif]]<br />
|-<br />
|OXtender for SyncML<br />
|<br />
|[[File:cross.gif]]<br />
|-<br />
|}<br />
<br />
== Open-Xchange Database Support (Parallel Setup) ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!align="left" |Database<br />
!align="left" |New Version<br />
!align="left" |Supported<br />
|- style="vertical-align:top"<br />
|rowspan="5" | Open-Xchange Database<br />
|v6.22.x<br />
|[[File:check.gif]] (after running v6.22 update tasks)<br />
|-<br />
|v6.20.7<br />
|[[File:check.gif]] (after running v6.22 update tasks)<br />
|-<br />
|v6.20.x<br />
|[[File:check.gif]] (after running v6.22 update tasks)<br />
|-<br />
|v6.18.x<br />
|[[File:cross.gif]]<br />
|-<br />
|Older Versions<br />
|[[File:cross.gif]]<br />
|-<br />
|}<br />
<br />
<br />
= Improvements Overview of 6.20.x to 6.22 Backend =<br />
<br />
Open-Xchange provides an overview page regarding the main improvements of the new v6.22. Please have a look at [http://oxpedia.org/wiki/index.php?title=Backend_Improvements_6_22 Backend Improvements 6.22]<br />
<br />
<br />
= Configuration Changes =<br />
<br />
The overview page provides a list of<br />
<br />
* unchanged config files with old and new location<br />
** push.properties renamed to push-udp.properties<br />
* completely new config files<br />
* config files that do not longer exist<br />
* merged / split config files<br />
* config options which need to be changed and their containing files<br />
<br />
<br />
'''If you have any configuration management or templating system for automatic deployment of OX instances in place, theses changes mean that you will have to adapt that system to the new configuration file tree.'''<br />
<br />
= Packages changes =<br />
<br />
The overview page provides a list of<br />
<br />
* new packages and metapackages with short description<br />
* removed metapackages<br />
* remaining metapackages and what they do<br />
<br />
We encourage administrators of Open-Xchange v6.20.x to read the [http://oxpedia.org/wiki/index.php?title=6.22_Packaging_Changes '''list'''] before updating to Open-Xchange v6.22.<br />
<br />
'''If you have any custom system for automatic installation and deployment of OX instances in place, it is very likely that you need to adapt your system to the new package structure.'''<br />
<br />
= No separate admin daemon =<br />
<br />
Admin functionality will now be a part of the Groupware Process as optional bundle. This means the former, as root running, Admin daemon will no longer exist.<br />
<br />
following are potential pitfalls :<br />
* ox-admin-scriptconf.sh is merged to /opt/open-xchange/etc/ox-scriptconf.sh, check NRFILES and Memory setting to fit the environment.<br />
* If /etc/security/limits.conf does set limits for the open-xchange user, those need to be adopted.<br />
* administrative tasks are now executed as user open-xchange (for example the filestore mount is no longer accessed as root).<br />
* The mutual process is not able to open tcp sockets below 1024.<br />
* Monitoring for the admin process is no longer needed.<br />
<br />
= Startup Scripts =<br />
<br />
The overview page provides a list of<br />
<br />
* startup scripts<br />
<br />
We encourage administrators of Open-Xchange v6.20.x to read the ['''list'''] before updating to Open-Xchange v6.22.<br />
<br />
= Changes to programming APIs which might break custom plugins to the OX Server =<br />
<br />
The overview page provides a list of<br />
<br />
* changes to exception handling & other code changes that break customer's custom developments<br />
<br />
We encourage administrators of Open-Xchange v6.20.x to read the ['''list'''] before updating to Open-Xchange v6.22.<br />
<br />
= Installation and Update Guide for Open-Xchange v6.22 =<br />
<br />
== Quick Installation Guide (supported packages) ==<br />
<br />
To download and install the software, please use the following Installation Guides.<br />
<br />
* [[Open-Xchange_Installation_Guide_for_Debian_6.0_622|Download and Installation Guide for Debian GNU/Linux 6.0 (Squeeze)]]<br />
* [[Open-Xchange_Installation_Guide_for_SLES11_622|Download and Installation Guide for SUSE Linux Enterprise Server 11]]<br />
* [[Open-Xchange_Installation_Guide_for_RHEL5_622|Download and Installation Guide for RedHat Enterprise Linux 5]]<br />
* [[Open-Xchange_Installation_Guide_for_RHEL6_622|Download and Installation Guide for RedHat Enterprise Linux 6]]<br />
* [[Open-Xchange Installation Guide for CentOS 5_622|Download and Installation Guide for CentOS 5]]<br />
* [[Open-Xchange Installation Guide for CentOS 6_622|Download and Installation Guide for CentOS 6]]<br />
<br />
== Update Guide (supported packages) ==<br />
<br />
To update the software to Open-Xchange v6.22, please use the following Update Guides. '''There you can also find information on how to start the groupware with / without admin part, on known issues and manual steps required.'''<br />
<br />
* [[Open-Xchange_620_622_Update_Guide_for_Debian_6.0|Update Guide from 6.20 to 6.22 for Debian GNU/Linux 6.0 (Squeeze)]]<br />
* [[Open-Xchange_620_622_Update_Guide_for_SLES11|Update Guide from 6.20 to 6.22 for SUSE Linux Enterprise Server 11]]<br />
* [[Open-Xchange_620_622_Update_Guide_for_RHEL5|Update Guide from 6.20 to 6.22 for RedHat Enterprise Linux 5]]<br />
* [[Open-Xchange_620_622_Update_Guide_for_RHEL6|Update Guide from 6.20 to 6.22 for RedHat Enterprise Linux 6]]<br />
* [[Open-Xchange_620_622_UpdateGuide_for_CentOS5|Update Guide from 6.20 to 6.22 for CentOS 5]]<br />
* [[Open-Xchange_620_622_Update_Guide_for_CentOS6|Update Guide from 6.20 to 6.22 for CentOS 6]]<br />
<br />
= Migration from OLOX1 to OLOX2 =<br />
<br />
== Migration Path ==<br />
<br />
Open-Xchange will discontinue the support for OXtender 1 for Microsoft Outlook with the new release v6.22. Additional, at the new backend, the Open-Xchange WebDAV XML API will no longer be officially supported. Open-Xchange will provide an upgrade path to the OXtender 2 for Microsoft Outlook.<br />
<br />
If the user installs the upcoming OLOX1 6.18.19 we will provide the following information to the user when trying to sync against the OX server >= 6.22. Open-Xchange provides via a pop-up window at the product the following migration possibilities:<br />
<br />
* User can use the OXUpdater to install the new version<br />
* User can directly start installing by clicking on a provided link<br />
<br />
<br />
If the user closes the pop-up window, the OLOX 1 will be deactivated for the current session and profil. After installing OLOX2 and starting Outlook the user has to select the new OLOX2 profile and the migration is done.<br />
<br />
== Known Issues ==<br />
<br />
* After the start of the new OLOX 2 profile, contacts, appointments and tasks will be synchronized<br />
* Per default server configuration, mails older as one year will be synchronized<br />
* Notice and Journal information won't be synchronized. It is possible to export and import the information via the Outlook functionalities</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OX6:Update_to_6_22&diff=10954OX6:Update to 6 222012-07-31T12:33:21Z<p>Holgi: /* Process Descriptions */</p>
<hr />
<div>= Update and Installation Portal Open-Xchange Server v6.22 =<br />
<br />
The new Open-Xchange Server v6.22 is the first step on the way to the next generation Open-Xchange Server 7. The update provides a new and improved Open-Xchange Server backend with enhancements for both generations. <br />
<br />
Especially on the backend, Open-Xchange implemented various changes and improvements like a new and clear structure for the configuration files and packages, an improved exception framework, unified OSGi, etc.<br />
<br />
On this portal you can find an overview of the differences between the Open-Xchange 6.20.x and the Open-Xchange v.6.22 backend. There are new requirements, update guides, and multiple other changes.<br />
<br />
'''Please read the different articles and manuals regarding the update. We encourage administrators of Open-Xchange 6 v6.20.x to install this update. The further feature development will be based on v6.22'''<br />
<br />
'''Furthermore, Open-Xchange provides the complete v6.22 materials as a document which is available here: [http://software.open-xchange.com/OX6/6.22/doc Software Repository].'''<br />
<br />
= Supported Update Path =<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!align="left" |Old version<br />
!align="left" |New version<br />
!align="left" |Update supported<br />
|-<br />
|v6.20.7<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|v6.20.x<br />
|v6.22.x<br />
|[[File:cross.gif]](1)<br />
|-<br />
|v6.18.x<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|Older Versions<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|}<br />
<br />
(1) If you don't [http://oxpedia.org/wiki/index.php?title=UpdatingOXPackages update to 6.20.7] before you start the 6.22 update, it is possible that some important scripts have not run on your system(s) and configuration options might be missing. See HERE for a list of changes that were done during the updates between 6.20.x versions<br />
<br />
= Rollback =<br />
<br />
Please note that after updating to 6.22 there is no way to get back to an earlier version of Open-Xchange. Please make sure that you have a backup. (TODO)<br />
<br />
= Supported Server / Client Combinations =<br />
<br />
== Client Support ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!align="left" |Open-Xchange GUI / Clients<br />
!align="left" |Open-Xchange Server<br />
!align="left" |Supported<br />
|-<br />
|v6.22.x<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|v6.20.x<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|v6.18.x<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|Older versions of Open-Xchange GUI<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|OXtender 2 for Microsoft Outlook<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|OXtender for Business Mobility<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|Open-Xchange Web Interface v1.2<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|}<br />
<br />
== Open-Xchange Database Support (Parallel Setup) ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!align="left" |Database<br />
!align="left" |New Version<br />
!align="left" |Supported<br />
|- style="vertical-align:top"<br />
|rowspan="5" | Open-Xchange Database<br />
|v6.22.x<br />
|[[File:check.gif]] (after running v6.22 update tasks)<br />
|-<br />
|v6.20.7<br />
|[[File:check.gif]] (after running v6.22 update tasks)<br />
|-<br />
|v6.20.x<br />
|[[File:check.gif]] (after running v6.22 update tasks)<br />
|-<br />
|v6.18.x<br />
|[[File:cross.gif]]<br />
|-<br />
|Older Versions<br />
|[[File:cross.gif]]<br />
|-<br />
|}<br />
<br />
<br />
= Improvements Overview of 6.20.x to 6.22 Backend =<br />
<br />
Open-Xchange provides an overview page regarding the main improvements of the new v6.22. Please have a look at [http://oxpedia.org/wiki/index.php?title=Backend_Improvements_6_22 Backend Improvements 6.22]<br />
<br />
<br />
= Configuration Changes =<br />
<br />
The overview page provides a list of<br />
<br />
* unchanged config files with old and new location<br />
* completely new config files<br />
* config files that do not longer exist<br />
* merged / split config files<br />
* config options which need to be changed and their containing files<br />
All pre-update config files are copied to DIRECTORY during the update so they are still accessible after the update. They can be safely removed at any time.<br />
<br />
We encourage administrators of Open-Xchange v6.20.x to read the [http://oxpedia.org/wiki/index.php?title=6.22_Packaging_Changes '''list'''] before updating to Open-Xchange v6.22.<br />
<br />
'''If you have any configuration management or templating system for automatic deployment of OX instances in place, theses changes mean that you will have to adapt that system to the new configuration file tree.'''<br />
<br />
= Packages changes =<br />
<br />
The overview page provides a list of<br />
<br />
* new packages and metapackages with short description<br />
* removed metapackages<br />
* remaining metapackages and what they do<br />
<br />
We encourage administrators of Open-Xchange v6.20.x to read the ['''list'''] before updating to Open-Xchange v6.22.<br />
<br />
'''If you have any custom system for automatic installation and deployment of OX instances in place, it is very likely that you need to adapt your system to the new package structure.'''<br />
<br />
= Process Descriptions =<br />
<br />
Admin functionality will now be a part of the Groupware Process as optional bundle. This means the former, as root running, Admin daemon will no longer exist.<br />
<br />
following are potential pitfalls :<br />
* ox-admin-scriptconf.sh is merged to /opt/open-xchange/etc/ox-scriptconf.sh, check NRFILES and Memory setting to fit the environment.<br />
* If /etc/security/limits.conf does set limits for the open-xchange user, those need to be adopted.<br />
* administrative tasks are now executed as user open-xchange (for example the filestore mount is no longer accessed as root).<br />
* The mutual process is not able to open tcp sockets below 1024.<br />
* Monitoring for the admin process is no longer needed.<br />
<br />
= Startup Scripts =<br />
<br />
The overview page provides a list of<br />
<br />
* startup scripts<br />
<br />
We encourage administrators of Open-Xchange v6.20.x to read the ['''list'''] before updating to Open-Xchange v6.22.<br />
<br />
= Changes to programming APIs which might break custom plugins to the OX Server =<br />
<br />
The overview page provides a list of<br />
<br />
* changes to exception handling & other code changes that break customer's custom developments<br />
<br />
We encourage administrators of Open-Xchange v6.20.x to read the ['''list'''] before updating to Open-Xchange v6.22.<br />
<br />
= Installation and Update Guide for Open-Xchange v6.22 =<br />
<br />
== Quick Installation Guide (supported packages) ==<br />
<br />
To download and install the software, please use the following Installation Guides.<br />
<br />
* [[Open-Xchange_Installation_Guide_for_Debian_6.0_622|Download and Installation Guide for Debian GNU/Linux 6.0 (Squeeze)]]<br />
* [[Open-Xchange_Installation_Guide_for_SLES11_622|Download and Installation Guide for SUSE Linux Enterprise Server 11]]<br />
* [[Open-Xchange_Installation_Guide_for_RHEL5_622|Download and Installation Guide for RedHat Enterprise Linux 5]]<br />
* [[Open-Xchange_Installation_Guide_for_RHEL6_622|Download and Installation Guide for RedHat Enterprise Linux 6]]<br />
* [[Open-Xchange Installation Guide for CentOS 5_622|Download and Installation Guide for CentOS 5]]<br />
* [[Open-Xchange Installation Guide for CentOS 6_622|Download and Installation Guide for CentOS 6]]<br />
<br />
== Update Guide (supported packages) ==<br />
<br />
To update the software to Open-Xchange v6.22, please use the following Update Guides. '''There you can also find information on how to start the groupware with / without admin part, on known issues and manual steps required.'''<br />
<br />
* [[Open-Xchange_Installation_Guide_for_Debian_6.0|Download and Installation Guide for Debian GNU/Linux 6.0 (Squeeze)]]<br />
* [[Open-Xchange_Installation_Guide_for_SLES11|Download and Installation Guide for SUSE Linux Enterprise Server 11]]<br />
* [[Open-Xchange_Installation_Guide_for_RHEL5|Download and Installation Guide for RedHat Enterprise Linux 5]]<br />
* [[Open-Xchange_Installation_Guide_for_RHEL6|Download and Installation Guide for RedHat Enterprise Linux 6]]<br />
* [[Open-Xchange Installation Guide for CentOS 5|Download and Installation Guide for CentOS 5]]<br />
* [[Open-Xchange Installation Guide for CentOS 6|Download and Installation Guide for CentOS 6]]</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OX6:Update_to_6_22&diff=10953OX6:Update to 6 222012-07-31T12:30:16Z<p>Holgi: /* Process Descriptions */</p>
<hr />
<div>= Update and Installation Portal Open-Xchange Server v6.22 =<br />
<br />
The new Open-Xchange Server v6.22 is the first step on the way to the next generation Open-Xchange Server 7. The update provides a new and improved Open-Xchange Server backend with enhancements for both generations. <br />
<br />
Especially on the backend, Open-Xchange implemented various changes and improvements like a new and clear structure for the configuration files and packages, an improved exception framework, unified OSGi, etc.<br />
<br />
On this portal you can find an overview of the differences between the Open-Xchange 6.20.x and the Open-Xchange v.6.22 backend. There are new requirements, update guides, and multiple other changes.<br />
<br />
'''Please read the different articles and manuals regarding the update. We encourage administrators of Open-Xchange 6 v6.20.x to install this update. The further feature development will be based on v6.22'''<br />
<br />
'''Furthermore, Open-Xchange provides the complete v6.22 materials as a document which is available here: [http://software.open-xchange.com/OX6/6.22/doc Software Repository].'''<br />
<br />
= Supported Update Path =<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!align="left" |Old version<br />
!align="left" |New version<br />
!align="left" |Update supported<br />
|-<br />
|v6.20.7<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|v6.20.x<br />
|v6.22.x<br />
|[[File:cross.gif]](1)<br />
|-<br />
|v6.18.x<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|Older Versions<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|}<br />
<br />
(1) If you don't [http://oxpedia.org/wiki/index.php?title=UpdatingOXPackages update to 6.20.7] before you start the 6.22 update, it is possible that some important scripts have not run on your system(s) and configuration options might be missing. See HERE for a list of changes that were done during the updates between 6.20.x versions<br />
<br />
= Rollback =<br />
<br />
Please note that after updating to 6.22 there is no way to get back to an earlier version of Open-Xchange. Please make sure that you have a backup. (TODO)<br />
<br />
= Supported Server / Client Combinations =<br />
<br />
== Client Support ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!align="left" |Open-Xchange GUI / Clients<br />
!align="left" |Open-Xchange Server<br />
!align="left" |Supported<br />
|-<br />
|v6.22.x<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|v6.20.x<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|v6.18.x<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|Older versions of Open-Xchange GUI<br />
|v6.22.x<br />
|[[File:cross.gif]]<br />
|-<br />
|OXtender 2 for Microsoft Outlook<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|OXtender for Business Mobility<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|Open-Xchange Web Interface v1.2<br />
|v6.22.x<br />
|[[File:check.gif]]<br />
|-<br />
|}<br />
<br />
== Open-Xchange Database Support (Parallel Setup) ==<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!align="left" |Database<br />
!align="left" |New Version<br />
!align="left" |Supported<br />
|- style="vertical-align:top"<br />
|rowspan="5" | Open-Xchange Database<br />
|v6.22.x<br />
|[[File:check.gif]] (after running v6.22 update tasks)<br />
|-<br />
|v6.20.7<br />
|[[File:check.gif]] (after running v6.22 update tasks)<br />
|-<br />
|v6.20.x<br />
|[[File:check.gif]] (after running v6.22 update tasks)<br />
|-<br />
|v6.18.x<br />
|[[File:cross.gif]]<br />
|-<br />
|Older Versions<br />
|[[File:cross.gif]]<br />
|-<br />
|}<br />
<br />
<br />
= Improvements Overview of 6.20.x to 6.22 Backend =<br />
<br />
Open-Xchange provides an overview page regarding the main improvements of the new v6.22. Please have a look at [http://oxpedia.org/wiki/index.php?title=Backend_Improvements_6_22 Backend Improvements 6.22]<br />
<br />
<br />
= Configuration Changes =<br />
<br />
The overview page provides a list of<br />
<br />
* unchanged config files with old and new location<br />
* completely new config files<br />
* config files that do not longer exist<br />
* merged / split config files<br />
* config options which need to be changed and their containing files<br />
All pre-update config files are copied to DIRECTORY during the update so they are still accessible after the update. They can be safely removed at any time.<br />
<br />
We encourage administrators of Open-Xchange v6.20.x to read the [http://oxpedia.org/wiki/index.php?title=6.22_Packaging_Changes '''list'''] before updating to Open-Xchange v6.22.<br />
<br />
'''If you have any configuration management or templating system for automatic deployment of OX instances in place, theses changes mean that you will have to adapt that system to the new configuration file tree.'''<br />
<br />
= Packages changes =<br />
<br />
The overview page provides a list of<br />
<br />
* new packages and metapackages with short description<br />
* removed metapackages<br />
* remaining metapackages and what they do<br />
<br />
We encourage administrators of Open-Xchange v6.20.x to read the ['''list'''] before updating to Open-Xchange v6.22.<br />
<br />
'''If you have any custom system for automatic installation and deployment of OX instances in place, it is very likely that you need to adapt your system to the new package structure.'''<br />
<br />
= Process Descriptions =<br />
<br />
Admin functionality will now, as optional bundle, be a part of the Groupware Process. This means the former, as root running, Admin daemon will no longer exist.<br />
<br />
following are potential pitfalls :<br />
* ox-admin-scriptconf.sh is merged to /opt/open-xchange/etc/ox-scriptconf.sh, check NRFILES and Memory setting to fit the environment<br />
* if /etc/security/limits.conf does set limits for the open-xchange user, those need to be adopted<br />
* administrative tasks are now executed as user open-xchange (for example the filestore mount is no longer accessed as root)<br />
<br />
= Startup Scripts =<br />
<br />
The overview page provides a list of<br />
<br />
* startup scripts<br />
<br />
We encourage administrators of Open-Xchange v6.20.x to read the ['''list'''] before updating to Open-Xchange v6.22.<br />
<br />
= Changes to programming APIs which might break custom plugins to the OX Server =<br />
<br />
The overview page provides a list of<br />
<br />
* changes to exception handling & other code changes that break customer's custom developments<br />
<br />
We encourage administrators of Open-Xchange v6.20.x to read the ['''list'''] before updating to Open-Xchange v6.22.<br />
<br />
= Installation and Update Guide for Open-Xchange v6.22 =<br />
<br />
== Quick Installation Guide (supported packages) ==<br />
<br />
To download and install the software, please use the following Installation Guides.<br />
<br />
* [[Open-Xchange_Installation_Guide_for_Debian_6.0_622|Download and Installation Guide for Debian GNU/Linux 6.0 (Squeeze)]]<br />
* [[Open-Xchange_Installation_Guide_for_SLES11_622|Download and Installation Guide for SUSE Linux Enterprise Server 11]]<br />
* [[Open-Xchange_Installation_Guide_for_RHEL5_622|Download and Installation Guide for RedHat Enterprise Linux 5]]<br />
* [[Open-Xchange_Installation_Guide_for_RHEL6_622|Download and Installation Guide for RedHat Enterprise Linux 6]]<br />
* [[Open-Xchange Installation Guide for CentOS 5_622|Download and Installation Guide for CentOS 5]]<br />
* [[Open-Xchange Installation Guide for CentOS 6_622|Download and Installation Guide for CentOS 6]]<br />
<br />
== Update Guide (supported packages) ==<br />
<br />
To update the software to Open-Xchange v6.22, please use the following Update Guides. '''There you can also find information on how to start the groupware with / without admin part, on known issues and manual steps required.'''<br />
<br />
* [[Open-Xchange_Installation_Guide_for_Debian_6.0|Download and Installation Guide for Debian GNU/Linux 6.0 (Squeeze)]]<br />
* [[Open-Xchange_Installation_Guide_for_SLES11|Download and Installation Guide for SUSE Linux Enterprise Server 11]]<br />
* [[Open-Xchange_Installation_Guide_for_RHEL5|Download and Installation Guide for RedHat Enterprise Linux 5]]<br />
* [[Open-Xchange_Installation_Guide_for_RHEL6|Download and Installation Guide for RedHat Enterprise Linux 6]]<br />
* [[Open-Xchange Installation Guide for CentOS 5|Download and Installation Guide for CentOS 5]]<br />
* [[Open-Xchange Installation Guide for CentOS 6|Download and Installation Guide for CentOS 6]]</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Template:Oxinstaller&diff=10594Template:Oxinstaller2012-06-26T08:11:13Z<p>Holgi: </p>
<hr />
<div>'''Important:''' You should have your Open-Xchange license code at hand. If you do not plan to license Open-Xchange, you can use the option ''--no-license'' instead. Please also check [[OXReportClient]] documentation for more information about configuring a supported and maintained Open-Xchange server.<br />
<br />
'''Important:''' For MAX_MEMORY_FOR_JAVAVM a rule of thumb for simple installations is half available system memory. For production environments please consult our {{DocLink|docpath=whitepaper/OX6-Sizing-Whitepaper.pdf|name=Sizing Whitepaper}}.<br />
<br />
$ /opt/open-xchange/sbin/oxinstaller --add-license=YOUR-OX-LICENSE-CODE \<br />
--servername=oxserver --configdb-pass=db_password \<br />
--master-pass=admin_master_password --ajp-bind-port=localhost --servermemory MAX_MEMORY_FOR_JAVAVM<br />
<br />
'''Note:''' In a clustered setup, <tt>--ajp-bind-port</tt> must be set to <tt>*</tt></div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Template:Oxinstaller&diff=10560Template:Oxinstaller2012-06-20T05:15:36Z<p>Holgi: </p>
<hr />
<div>'''Important:''' You should have your Open-Xchange license code at hand. If you do not plan to license Open-Xchange, you can use the option ''--no-license'' instead. Please also check [[OXReportClient]] documentation for more information about configuring a supported and maintained Open-Xchange server.<br />
<br />
'''Important:''' the option "--servermemory 512" configures 512 MB Ram for the groupware process. This works for small environments. Please refere to the {{DocLink|docpath=whitepaper/OX6-Sizing-Whitepaper.pdf|name=Sizing Whitepaper}} to learn how to set this value for your needs.<br />
<br />
$ /opt/open-xchange/sbin/oxinstaller --add-license=YOUR-OX-LICENSE-CODE \<br />
--servername=oxserver --configdb-pass=db_password \<br />
--master-pass=admin_master_password --ajp-bind-port=localhost --servermemory 512<br />
<br />
'''Note:''' In a clustered setup, <tt>--ajp-bind-port</tt> must be set to <tt>*</tt></div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Template:Main_Page_Advanced&diff=9764Template:Main Page Advanced2011-12-14T08:00:04Z<p>Holgi: /* Programming Interfaces */</p>
<hr />
<div>__NOTOC__<br />
= Overview =<br />
*[[Architecture_Overview|Architecture Overview]]<br />
<br />
= Branding =<br />
* [[Whitelabel|White-labeling the Open-Xchange GUI for big hosting/reseller environments]]<br />
* [[Gui_Theming_Description|GUI Theming Description]]<br />
* [[User_and_context_based_themes|User and context based themes]]<br />
* [[Gui_Plugin_Development|GUI Branding Plugins]]<br />
<br />
= UI Customization and Examples =<br />
* [[Gui_Plugin_Development|Embedding external web applications which require authentication]]<br />
* [[Gui_path|Setting User/GUI Preferences via RMI]]<br />
* [[Open-Xchange_UWA|Open-Xchange Netvibes UWA mashup]]<br />
* [[Gui_Plugin_Development|GUI Plugin Development]]<br />
* [[Plugin_API|GUI Plugin API Documentation]]<br />
* [[Enable_TinyMCE_spellcheck_module|Enable the TinyMCE spell-checker module]]<br />
* [[HTTP_API_Examples|HTTP API Examples]]<br />
* [[Install_and_configure_the_mail-account_plugin|Install and configure the mail-account plugin]]<br />
<br />
= Groupware Server customization =<br />
* [[Plugin_Extension_Quickstart_Guide|How to make custom changes to existing plugins (Authentication plugin)]]<br />
* [[Automatic_Delete_OXObjects_Per_User|Automatically delete users OX-Objects and OX-Folders]]<br />
* Auto login, session handling, single sign on<br />
** [http://www.open-xchange.com/fileadmin/user_upload/open-xchange/document/presentation/OX-HE-Authentication-Sessionhandling.pdf Authentication and Sessionhandling white paper (EasyLogin)]<br />
** [http://www.open-xchange.com/fileadmin/user_upload/open-xchange/document/presentation/OX-HE-Authentication-Sessionhandling-en-6.18.pdf Authentication and Sessionhandling white paper (EasyLogin) (v.6.18.0)]<br />
** Custom login masks<br />
*** [[Open-Xchange servlet for external login masks]]<br />
<br />
= Programming Interfaces =<br />
* The [[HTTP_API|HTTP API]] is used by the Open-Xchange GUI and various 3rd party applications. It consists mainly of messages in JavaScript Object Notation ([http://json.org JSON]) sent over HTTP.<br />
* The [[Oxwebdavapi|WebDAV API]] is used by external clients to modify object on the OX Server. It based mainly on the webdav standard with some enhancements to handle OX objects.<br />
* Provisioning API to access the Open-Xchange Admin Daemon<br />
** The [http://java.sun.com/javase/technologies/core/basic/rmi/index.jsp RMI] API is used for data provisioning of Contexts, Users, Groups and Resources as well as for configuring Databases, Filestores and OX Servers. It is currently split into two parts,<br />
*** a {{DocLink|docpath=RMI/admin-core/|name=core}} and<br />
*** a {{DocLink|docpath=RMI/admin-hosting/|name=hosting}} component.<br />
** The {{DocLink|docpath=OX6-Provisioning/|name=Open-Xchange CLT}} are shell scripts that simplify groupware and service administration<br />
** Create contexts/users with with [[Csv_import]]<br />
** [[Open-Xchange-SOAP|Provisioning using SOAP]]<br />
* The [[Oxmapi|Oxmapi]] is a windows library for programmers needed to communicate with the OX server<br />
* {{DocLink|docpath=mal/|name=Open-Xchange Mail Abstraction Layer}}<br />
* The Plugin API for extending the GUI is described in two documents: [[Plugin API|an overview]] and {{DocLink|docpath=gui-plugin-api|name=the reference}}<br />
* [[UDPPush]] Open-Xchange PUSH Interface for Groupware Objects<br />
<br />
{{=}} Importing and exporting data {{=}}<br />
* Migrate a batch of users and contexts at once. Check the CSV Batch Import documentation [[Csv_import|page]].<br />
* Documentation for the [[data import format|data import format]]<br />
* [[VCard and ICal support]]<br />
* [[Using the export servlet]]<br />
* [[Using the import servlet]]<br />
* [[export ical/vcard|Example in bash to extract private contacts,tasks,appointments in ical/vcard format]]<br />
* [[Import_holidays|Importing holidays into the OX Calendar]]<br />
* [[CrawlerArchitecture|Architecture of the crawler bundle]]<br />
<br />
{{=}} Configuration and Tweaks {{=}}<br />
* [[OX6_Troubleshooting|Basic troubleshooting]]<br />
* {{DocLink|docpath=Html-Whitelist|name=HTML Whitelist configuration}}<br />
* [[Open_Xchange_Configuration|Open-Xchange Configuration]]<br />
* [[Open-Xchange_Lighttpd|Open-Xchange and Lighttpd]]<br />
* [[Open-Xchange_RSS_Client|Open-Xchange as RSS client]]<br />
* [[On_The_Fly_Configuration_Update|On The Fly Configuration Update (experimental)]]<br />
* [[Session_Migration|Session migration]]<br />
* [[Syslog_Configuration|syslog Configuration]]<br />
* [[OXAE_MailingLists_with_contacts-ldap|Integrate OXAE Mailinglists into Open-Xchange]]<br />
* [[MailNotify_Bundle|Mail Notification (Push) with Open-Xchange]]<br />
* [[UCS_AD_Connector_en|Synchronize Active Directory with OX ASE/SE for UCS]]<br />
* [[Tune_apache2_for_more_concurrent_connections|Apache2 tuning]]<br />
<br />
= Testing and QA =<br />
* [[Automated GUI Tests]]<br />
* [[Jmeter profile for performance tests|JMeter profile for performance tests]]<br />
<br />
= Translations =<br />
* [[Available_Translation| Available Language Translations]]<br />
* [[GUI Translation|Translate Open-Xchange to your community language]]<br />
* [[Translate Open-Xchange to supported language]]<br />
<br />
= Installation based on source code =<br />
* [[SourceCodeAccess|Download the sourcecode]]<br />
* [[EclipseQuickInstallGuide|Eclipse Quick Install Guide]]</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Tune_apache2_for_more_concurrent_connections&diff=9762Tune apache2 for more concurrent connections2011-12-14T07:51:25Z<p>Holgi: moved Development:Tune apache2 for more concurrent connections to Tune apache2 for more concurrent connections</p>
<hr />
<div>=The problem=<br />
By default apache2 is configured to support 150 concurrent connections.<br />
This forces all parallel requests beyond that limit to wait. <br />
Especially if, for example, active sync clients maintain a permanent connection for push events to arrive.<br />
<br />
=The solution=<br />
This is an example configuration to provide 800 concurrent connections.<br />
Please ensure that your apache is using the mpm_worker module. This allows us to serve lots of concurrent connections by using less RAM than with mpm_prefork as we are going to start much less processes.<br />
<br />
<pre><nowiki><br />
<IfModule mpm_worker_module><br />
ServerLimit 25<br />
StartServers 10<br />
MinSpareThreads 75<br />
MaxSpareThreads 250 <br />
ThreadLimit 64<br />
ThreadsPerChild 32<br />
MaxClients 800<br />
MaxRequestsPerChild 0<br />
</IfModule><br />
</nowiki></pre><br />
<br />
<br />
<br />
==Short explanation of the parameters:==<br />
<br />
<table border="1" cellpadding="5" cellspacing="0"><br />
<tr><br />
<td><b>ServerLimit</b></td><td>Declares the maximum number of running apache processes. If you change this value you have to restart the daemon.</td><br />
</tr><br />
<tr><br />
<td><b>StartServers</b></td><td>The number of processes to start initially when starting the apache daemon.</td><br />
</tr><br />
<tr><br />
<td><b>MinSpareThreads/MaxSpareThreads</b></td><td>This regulates how many threads may stay idle without being killed. Apache regulates this on its own very well with default values.</td><br />
</tr><br />
<tr><br />
<td><b>ThreadsPerChild</b></td><td>How many threads can be created per process. Can be changed during a reload.</td><br />
</tr><br />
<tr><br />
<td><b>ThreadLimit</b></td><td><b>ThreadsPerChild</b> can be configured as high as this value during runtime. If you change this value you have to restart the daemon.</td><br />
</tr><br />
<tr><br />
<td><b>MaxClients</b></td><td>This declares how many concurrent connections we provide. Devided by '''ThreadsPerChild''' you get the suitable ServerLimit value. May be less than '''ServerLimit * ThreadsPerChild''' to reserve some resources that can be engaged during runtime with increasing '''MaxClients''' and reloading the configuration.</td><br />
</tr><br />
<tr><br />
<td><b>MaxRequestsPerChild</b></td><td>Defines the number of Connections that a process can handle during its lifetime (keep-alives are counted once). After that it will be killed.</td><br />
</tr><br />
</table><br />
<br />
<br />
For further information on these parameters see http://httpd.apache.org/docs/2.2/mod/worker.html and http://httpd.apache.org/docs/2.2/mod/mpm_common.html.<br />
<br />
--[[User:Steffen.templin|Steffen.templin]] 12:10, 23 May 2011 (UTC)</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Tune_apache2_for_more_concurrent_connections&diff=9761Tune apache2 for more concurrent connections2011-12-14T07:50:46Z<p>Holgi: /* The problem */</p>
<hr />
<div>=The problem=<br />
By default apache2 is configured to support 150 concurrent connections.<br />
This forces all parallel requests beyond that limit to wait. <br />
Especially if, for example, active sync clients maintain a permanent connection for push events to arrive.<br />
<br />
=The solution=<br />
This is an example configuration to provide 800 concurrent connections.<br />
Please ensure that your apache is using the mpm_worker module. This allows us to serve lots of concurrent connections by using less RAM than with mpm_prefork as we are going to start much less processes.<br />
<br />
<pre><nowiki><br />
<IfModule mpm_worker_module><br />
ServerLimit 25<br />
StartServers 10<br />
MinSpareThreads 75<br />
MaxSpareThreads 250 <br />
ThreadLimit 64<br />
ThreadsPerChild 32<br />
MaxClients 800<br />
MaxRequestsPerChild 0<br />
</IfModule><br />
</nowiki></pre><br />
<br />
<br />
<br />
==Short explanation of the parameters:==<br />
<br />
<table border="1" cellpadding="5" cellspacing="0"><br />
<tr><br />
<td><b>ServerLimit</b></td><td>Declares the maximum number of running apache processes. If you change this value you have to restart the daemon.</td><br />
</tr><br />
<tr><br />
<td><b>StartServers</b></td><td>The number of processes to start initially when starting the apache daemon.</td><br />
</tr><br />
<tr><br />
<td><b>MinSpareThreads/MaxSpareThreads</b></td><td>This regulates how many threads may stay idle without being killed. Apache regulates this on its own very well with default values.</td><br />
</tr><br />
<tr><br />
<td><b>ThreadsPerChild</b></td><td>How many threads can be created per process. Can be changed during a reload.</td><br />
</tr><br />
<tr><br />
<td><b>ThreadLimit</b></td><td><b>ThreadsPerChild</b> can be configured as high as this value during runtime. If you change this value you have to restart the daemon.</td><br />
</tr><br />
<tr><br />
<td><b>MaxClients</b></td><td>This declares how many concurrent connections we provide. Devided by '''ThreadsPerChild''' you get the suitable ServerLimit value. May be less than '''ServerLimit * ThreadsPerChild''' to reserve some resources that can be engaged during runtime with increasing '''MaxClients''' and reloading the configuration.</td><br />
</tr><br />
<tr><br />
<td><b>MaxRequestsPerChild</b></td><td>Defines the number of Connections that a process can handle during its lifetime (keep-alives are counted once). After that it will be killed.</td><br />
</tr><br />
</table><br />
<br />
<br />
For further information on these parameters see http://httpd.apache.org/docs/2.2/mod/worker.html and http://httpd.apache.org/docs/2.2/mod/mpm_common.html.<br />
<br />
--[[User:Steffen.templin|Steffen.templin]] 12:10, 23 May 2011 (UTC)</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=My.cnf&diff=9156My.cnf2011-10-13T08:31:27Z<p>Holgi: </p>
<hr />
<div>This page lists some parameters (MySQL 5.1) which might be worth to adjust on a MySQL instance running the Open-Xchange databases.<br />
This is NOT a reference configuration but shows some possible settings. Please check the MySQL documentation for your version to understand the settings and test local changes carefully.<br />
<br />
You should adjust the <code>innodb_buffer_pool_size</code> parameter for better memory usage.<br />
<br />
On bigger installations you should use <code>innodb_file_per_table = 1</code>, which is creating single files instead of one big blob. If you change this parameter after the database initialization you have to recreate (like dump/drop and re-import) the tables. <br />
<br />
#<br />
[client]<br />
port = 3306<br />
socket = /var/run/mysqld/mysqld.sock<br />
<br />
[mysqld]<br />
socket = /var/run/mysqld/mysqld.sock<br />
port = 3306<br />
user = mysql<br />
# applies only when running as root<br />
#memlock = 1<br />
<br />
table_open_cache = 3072<br />
table_definition_cache = 4096<br />
max_heap_table_size = 64M<br />
tmp_table_size = 64M<br />
max_connections = 505<br />
max_user_connections = 500<br />
max_allowed_packet = 16M<br />
thread_cache_size = 32<br />
query_cache_size = 64M<br />
<br />
# InnoDB<br />
default_table_type = InnoDB<br />
<br />
# 80% of ram that is dedicated for the database (this needs to be adjusted to your system)<br />
innodb_buffer_pool_size = 14G<br />
<br />
innodb_data_file_path = ibdata1:128M:autoextend<br />
innodb_file_per_table = 1<br />
innodb_log_file_size = 512M<br />
innodb_log_files_in_group = 2<br />
<br />
# MyISAM<br />
myisam_recover = backup,force<br />
<br />
# Logging<br />
log_warnings = 2<br />
log_error = /var/log/mysql/error.log<br />
<br />
slow_query_log = 1<br />
slow_query_log_file = /var/log/mysql/mysql-slow.log<br />
long_query_time = 1<br />
log_queries_not_using_indexes = 1<br />
min_examined_row_limit = 20<br />
<br />
# Binary Log / Replication<br />
server_id = 1<br />
log-bin = mysql-bin<br />
binlog_cache_size = 1M <br />
sync_binlog = 8<br />
binlog_format = row<br />
expire_logs_days = 7<br />
max_binlog_size = 128M <br />
relay-log = /var/log/mysql/slave-relay.log<br />
relay-log-index = /var/log/mysql/slave-relay-log.index <br />
<br />
[mysqldump]<br />
quick<br />
single-transaction<br />
max_allowed_packet = 16M<br />
<br />
[mysql]<br />
no_auto_rehash<br />
<br />
[myisamchk]<br />
key_buffer = 512M<br />
sort_buffer_size = 512M<br />
read_buffer = 8M<br />
write_buffer = 8M<br />
<br />
[mysqld_safe]<br />
open-files-limit = 8192<br />
log-error = /var/log/mysql/error.log</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=AppSuite:Open-Xchange_Plugin_Overview&diff=8134AppSuite:Open-Xchange Plugin Overview2011-07-01T12:23:48Z<p>Holgi: /* Core Plugins */</p>
<hr />
<div>= Overview of available Open-Xchange Plugins =<br />
<br />
<br />
<br />
== Core Plugins ==<br />
<br />
These plugins are part of the Open-Xchange Server Core platform.<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!style="width:230px" align="left" |Name<br />
!style="width:230px" align="left" |Description<br />
!align="left" |Documentation<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-authentication-ldap]<br />
|Authentication against LDAP server<br />
|<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-authentication-imap]<br />
|Authentication against IMAP server<br />
|[[Authentication_IMAP_Plugin_description|Authentication imap plugin description]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-contextrestore]<br />
|Plugin to restore one or more contexts from a complete database dump<br />
|http://software.open-xchange.com/OX6/doc/OX6-Installation-and-Administration.pdf<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-dataretention / open-xchange-dataretention-csv]<br />
|Module to be used for data retention (german: Vorratsdatenspeicherung)<br />
|open-xchange-dataretention-csv is an example implementation of the data retention service<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-commons-logging-log4j / open-xchange-log4j]<br />
|These packages must be installed when Open-Xchange should use syslog<br />
|[[Syslog_Configuration|Syslog configuration]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-contacts-ldap]<br />
|Integrate LDAP address book into Open-Xchange public folder tree<br />
|http://software.open-xchange.com/OX6/doc/OX6-Installation-and-Administration.pdf<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-subscribe-crawler]<br />
|The open-xchange Social OX PlugIn bundle to subscribe/import data<br />
|[[CrawlerArchitecture|Architecture of the Social OX PlugIn bundle]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-upsell-generic]<br />
|Basic examples to implement an up sell layer in Open-Xchange<br />
|[[Upsell_Layer_Package|Upsell package description]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-easylogin]<br />
|Example package to implement the EasyLogin mechanism<br />
|[[Open-Xchange_servlet_for_external_login_masks|EasyLogin description]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-report-client]<br />
|Tool to display and report the amount of users and contexts in the Open-Xchange environment<br />
|[[OXReportClient|Report Client description]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/OXtender-stable/OXUpdater/ open-xchange-outlook-updater]<br />
|Updater server bundle to download OXtender directly from Open-Xchange GUI<br />
|<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-passwordchange-script]<br />
|Use an external command to change a password<br />
|[[ChangePasswordExternal|Example Script]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-publish-microformats]<br />
|Publishing of Open-Xchange internal data structures like contacts, documents.<br />
|[[Open-Xchange_Publishing|Publishing Data with Open-Xchange]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-calendar-printing]<br />
|Generating printviews of calendar items<br />
|[[Open-Xchange_Publishing|Publishing Data with Open-Xchange]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-audit]<br />
|User action tracking bundle<br />
|[[OXAudit|Audit bundle description]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-push-mailnotify]<br />
|Accepting external new mail notifications<br />
|[[MailNotify_Bundle|Mail Notification (Push) with Open-Xchange]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-push-imapidle]<br />
|Mail push using IMAP IDLE<br />
|[[MailPushIMAPIDLE_Bundle|Mail Notification (Push) with Open-Xchange]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-messaging-facebook open-xchange-subscribe-facebook]<br />
|Facebook messaging and subscription<br />
|[[FacebookMessaging_Bundle|Using Facebook with Open-Xchange]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-subscribe-msn]<br />
|MSN subscription<br />
|[[MSN_Bundles|Windows Live / MSN]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-messaging-twitter]<br />
|Twitter messaging<br />
|[[Twitter_Bundles|Twitter]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-subscribe-linkedin]<br />
|LinkedIn subscription<br />
|[[LinkedIn_Bundles|LinkedIn]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-voipnow-gui open-xchange-voipnow-json]<br />
|Integration of 4PSA VoipNow<br />
|[[Installing_VoipNow|Install the Open-Xchange VoipNow integration packages]]<br />
|-<br />
|[http://software.open-xchange.com/OX6/stable/ open-xchange-admin-plugin-reseller]<br />
|Reseller provisioning plugin<br />
|[[Reseller_Bundle|Install the Open-Xchange Reseller package]]<br />
|}<br />
<br />
<br />
----<br />
<br />
== Additional Plugins ==<br />
<br />
The plugins listed here are not - yet - part of the Core platform and may or may not ever be part of the Open-Xchange Core platform.<br />
<br />
These plugins are not supported by Open-Xchange with the exception of concrete projects. Please [http://www.open-xchange.com/en/contactus contact us] for more details.<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!style="width:230px" align="left" |Name<br />
!style="width:230px" align="left" |Description<br />
!align="left" |Documentation<br />
|-<br />
|}<br />
<br />
<br />
----<br />
<br />
== Custom Plugins ==<br />
<br />
<br />
The following list consists of plugins, that Open-Xchange developed for specific customers. It is an overview of what is possible to do with the Open-Xchange integration platform.<br />
<br />
If you want Open-Xchange to develop a specific plugin for you, please [http://www.open-xchange.com/en/contactus contact us] for more details.<br />
<br />
<br />
{| border="1" cellpadding="3" cellspacing="0"<br />
!style="width:150px" align="left" |Name<br />
!align="left" |Description<br />
|-<br />
|MAL<br />
|Plugin which replaces the standard imap/smtp plugin to access the mail store with a customer specific plugin, e.g. directly access a [http://en.wikipedia.org/wiki/Maildir maildir] mailstore.<br />
|-<br />
|Upsell<br />
|If the example upsell plugin does not fit your needs or has some missing functionality, do not hesitate to contact us.<br />
|-<br />
|Spam<br />
|It's possible to integrate the built in mark as SPAM/HAM functionality into almost any solution.<br />
|-<br />
|Authentication<br />
|Authentication can be done against every system that allows to specify a username/password combination.<br />
|-<br />
|Migration from OX5 to OX6<br />
|Migration plugin that updates the user passwords in OX6 Database after a successful login to the OX5 LDAP service. That way, passwords can be migrated automatically from any LDAP to OX6 database.<br />
|-<br />
|Corporate Integration: EasyLogin<br />
|The EasyLogin mechanism allows to login into Open-Xchange from other applications without specifying username and password again.<br />
|-<br />
|Corporate Integration: ConfigJump<br />
|Integrate your own configuration application in the Open-Xchange settings tree.<br />
|-<br />
|UI Customization<br />
|A lot of customization can be done in the Open-Xchange UI. Starting from themes to the integration of custom modules and functions.<br />
|}<br />
<br />
[[Category: OX6]]</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=My.cnf&diff=7737My.cnf2011-05-03T12:18:35Z<p>Holgi: Created page with " # # /etc/mysql/my.cnf # [client] port = 3306 socket = /var/run/mysqld/mysqld.sock [mysqld] socket = /var/run/mysqld/mysqld.sock port ..."</p>
<hr />
<div> #<br />
# /etc/mysql/my.cnf<br />
#<br />
[client]<br />
port = 3306<br />
socket = /var/run/mysqld/mysqld.sock<br />
<br />
[mysqld]<br />
socket = /var/run/mysqld/mysqld.sock<br />
port = 3306<br />
user = mysql<br />
memlock = 1<br />
<br />
table_open_cache = 3072<br />
table_definition_cache = 4096<br />
max_heap_table_size = 64M<br />
tmp_table_size = 64M<br />
max_connections = 505<br />
max_user_connections = 500<br />
max_allowed_packet = 16M<br />
thread_cache_size = 32<br />
query_cache_size = 64M<br />
<br />
# InnoDB<br />
default_table_type = InnoDB<br />
<br />
# 80% of ram that is dedicated for the database<br />
innodb_buffer_pool_size = 14G<br />
<br />
innodb_data_file_path = ibdata1:512M:autoextend<br />
innodb_file_per_table = 1<br />
innodb_log_file_size = 512M<br />
innodb_log_files_in_group = 2<br />
<br />
# MyISAM<br />
myisam_recover = backup,force<br />
<br />
# Logging<br />
log_warnings = 2<br />
log_error = /var/log/mysql/error.log<br />
<br />
slow_query_log = 1<br />
slow_query_log_file = slow.log<br />
long_query_time = 1<br />
log_queries_not_using_indexes = 1<br />
min_examined_row_limit = 20<br />
<br />
# Binary Log / Replication<br />
server_id = 1<br />
log-bin = mysql-bin<br />
binlog_cache_size = 1M <br />
sync_binlog = 8<br />
binlog_format = row<br />
expire_logs_days = 7<br />
max_binlog_size = 128M <br />
<br />
[mysqldump]<br />
quick<br />
single-transaction<br />
max_allowed_packet = 16M<br />
<br />
[mysql]<br />
no_auto_rehash<br />
<br />
[myisamchk]<br />
key_buffer = 512M<br />
sort_buffer_size = 512M<br />
read_buffer = 8M<br />
write_buffer = 8M<br />
<br />
[mysqld_safe]<br />
open-files-limit = 8192<br />
log-error = /var/log/mysql/error.log</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Template:ApacheOXConf&diff=7639Template:ApacheOXConf2011-04-12T09:38:09Z<p>Holgi: </p>
<hr />
<div>Configure the ''mod_proxy_ajp'' module by creating a new Apache configuration file.<br />
<br />
$ vim {{{ajpconf}}}<br />
<br />
<Location /axis2><br />
# restrict access to the soap provisioning API<br />
Order Deny,Allow<br />
Deny from all<br />
Allow from 127.0.0.1<br />
# you might add more ip addresses / networks here<br />
# Allow from 192.168 10 172.16<br />
</Location><br />
<br />
{{{loadmodule}}}<br />
<br />
<IfModule mod_proxy_ajp.c><br />
ProxyRequests Off<br />
<Proxy balancer://oxcluster><br />
Order deny,allow<br />
Allow from all<br />
# multiple server setups need to have the hostname inserted instead localhost<br />
BalancerMember ajp://localhost:8009 timeout=100 smax=0 ttl=60 retry=60 loadfactor=50 route=OX1<br />
# Enable and maybe add additional hosts running OX here<br />
# BalancerMember ajp://oxhost2:8009 timeout=100 smax=0 ttl=60 retry=60 loadfactor=50 route=OX2<br />
ProxySet stickysession=JSESSIONID<br />
</Proxy><br />
<Proxy /ajax><br />
ProxyPass balancer://oxcluster/ajax<br />
</Proxy><br />
<Proxy /axis2><br />
ProxyPass balancer://oxcluster/axis2<br />
</Proxy><br />
<Proxy /servlet><br />
ProxyPass balancer://oxcluster/servlet<br />
</Proxy><br />
<Proxy /infostore><br />
ProxyPass balancer://oxcluster/infostore<br />
</Proxy><br />
<Proxy /publications><br />
ProxyPass balancer://oxcluster/publications<br />
</Proxy><br />
<Proxy /Microsoft-Server-ActiveSync><br />
ProxyPass balancer://oxcluster/Microsoft-Server-ActiveSync<br />
</Proxy><br />
<Proxy /usm-json><br />
ProxyPass balancer://oxcluster/usm-json<br />
</Proxy><br />
</IfModule><br />
<br />
<br />
Modify the default website settings to display the Open-Xchange GUI<br />
<br />
$ vim {{{apacheconf}}}<br />
<br />
<VirtualHost *:80><br />
ServerAdmin webmaster@localhost<br />
<br />
DocumentRoot {{{docroot}}}<br />
<br />
<Directory {{{docroot}}}><br />
AllowOverride None<br />
Order allow,deny<br />
allow from all<br />
RedirectMatch ^/$ /ox6/<br />
Options +FollowSymLinks +SymLinksIfOwnerMatch<br />
</Directory><br />
# deflate<br />
AddOutputFilterByType DEFLATE text/html text/plain text/javascript application/javascript text/css text/xml application/xml text/x-js application/x-javascript<br />
<br />
# pre-compressed files<br />
AddType text/javascript .jsz<br />
AddType text/css .cssz<br />
AddType text/xml .xmlz<br />
AddType text/plain .po<br />
<br />
AddEncoding gzip .jsz .cssz .xmlz<br />
SetEnvIf Request_URI "\.(jsz|cssz|xmlz)$" no-gzip<br />
<br />
ExpiresActive On<br />
<br />
<Location /ox6><br />
# Expires (via ExpiresByType to override global settings)<br />
ExpiresByType image/gif "access plus 6 months"<br />
ExpiresByType image/png "access plus 6 months"<br />
ExpiresByType image/jpg "access plus 6 months"<br />
ExpiresByType image/jpeg "access plus 6 months"<br />
ExpiresByType text/css "access plus 6 months"<br />
ExpiresByType text/html "access plus 6 months"<br />
ExpiresByType text/xml "access plus 6 months"<br />
ExpiresByType text/javascript "access plus 6 months"<br />
ExpiresByType text/x-js "access plus 6 months"<br />
ExpiresByType application/x-javascript "access plus 6 months"<br />
ExpiresDefault "access plus 6 months"<br />
Header append Cache-Control "private"<br />
Header unset Last-Modified<br />
Header unset Vary<br />
# Strip version<br />
RewriteEngine On<br />
RewriteRule v=\w+/(.+) $1 [L]<br />
# Turn off ETag<br />
Header unset ETag<br />
FileETag None<br />
</Location><br />
<br />
<Location /ox6/ox.html><br />
ExpiresByType text/html "now"<br />
ExpiresDefault "now"<br />
Header unset Last-Modified<br />
Header set Cache-Control "no-store, no-cache, must-revalidate, post-check=0, pre-check=0"<br />
# Turn off ETag<br />
Header unset ETag<br />
FileETag None<br />
</Location><br />
<br />
<Location /ox6/index.html><br />
ExpiresByType text/html "now"<br />
ExpiresDefault "now"<br />
Header unset Last-Modified<br />
Header set Cache-Control "no-store, no-cache, must-revalidate, post-check=0, pre-check=0"<br />
# Turn off ETag<br />
Header unset ETag<br />
FileETag None<br />
</Location><br />
</VirtualHost></div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=OX6:OX_Mobile_Web_Interface&diff=7592OX6:OX Mobile Web Interface2011-03-28T07:31:08Z<p>Holgi: /* Configuration */</p>
<hr />
<div>= Information and Installation of Open-Xchange Mobile Web App (Preview)=<br />
<br />
== Description ==<br />
<br />
Later this year, Open-Xchange will release Open-Xchange Mobile Web App, which lets you access data from Open-Xchange Server 6 with your smartphone running a webkit based browser like the iPhone or Android devices.<br />
Open-Xchange Mobile Web App offers online and offline access to appointments, contacts and mails on the road using your smartphone. Optimized for low bandwiths Open-Xchange Mobile Web App offers instant and fast over the air access to your data, which are at the same time safely stored on Open-Xchange Server. The following modules are supported:<br />
<br />
*E-Mail<br />
*Calendar<br />
*Contacts<br />
<br />
Moreover the app offers seamless integration to use your phones basic functions like phone calls. You can easily start calls from your Open-Xchange contacts on your smartphone or directly send E-Mails.<br />
<br />
== Features and Functions ==<br />
<br />
=== Mail Module ===<br />
*Access to all Open-Xchange standard folder: Inbox, Sent, Trash, Spam and Drafts<br />
*Creation of new e-mails<br />
*Answer, forward and delete e-mails<br />
*Mail attachments (Attachment handling/support is defined by mobile device)<br />
<br />
=== Contact Module ===<br />
*Access to all Open-Xchange contact folder and contacts with details<br />
*Creation of e-mail directly from contact module<br />
*Start call directly from contact module<br />
<br />
=== Calendar Module ===<br />
* Access to all Open-Xchange calendar folder and appointments with details<br />
* Accept/Decline of appointments<br />
* Participants and resources list from all appointments<br />
* Planned: Additional notes for Accept/Decline function, creation of new appointments<br />
<br />
=== Persistence of the Mobile Web App ===<br />
*Offline capability<br />
*All contacts are available offline<br />
*All appointments are available offline<br />
*All mail header are available offline<br />
*All mails which are opened once are available offline<br />
<br />
===Configuration===<br />
*Number of e-mails retrieved (25,50,75,100)<br />
*Number of days which will be checked for appointments (5,10,20,30)<br />
*Animation for iOS devices (on/off)<br />
*Subscription of contact folders<br />
*Autologin<br />
<br />
===Themeability, branding and i18n ===<br />
<br />
* i18n for DE and EN, other languages can be added.<br />
* Branding options: App name and app icon<br />
* Themeability by CSS<br />
<br />
== Supported devices ==<br />
<br />
The OX Mobile Web App should work on devices running a Webkit based browser. These are mainly the devices running iOS, Android and newest generation of BlackBerrys. For devices running Symbian we recommend to use Opera Mobile Browser.<br />
<br />
{|border="2" rules="all" align="left"><br />
|-<br />
|'''Device Support'''<br />
|&nbsp;<br />
|&nbsp;<br />
|-<br />
|Apple iPhone<br />
|yes (iPhone running iOS 2.0, 2.1, 3.0, 4.0, 4.2.1, 4.3)<br />
|Official Supported by OX: 2G, 3G, 3GS, 4 and iPod-Touch 3.1.3<br />
|-<br />
|Android<br />
|yes<br />
|Official Supported by OX: Google Nexus One (Android 2.3.3), HTC Desire (Sense Android 2.1)<br />
|-<br />
|Nokia/Symbian S60 5th Edition<br />
|via Opera Mini<br />
|i.e Nokia N97 (Although there is a built-in Webkit browser running on this device a Symbian bug in the cookie-handling which prevents login to the OX-Server)<br />
|-<br />
|Windows Mobile running Internet Explorer<br />
|no<br />
|<br />
|-<br />
|Windows Phone 7<br />
|not yet<br />
|<br />
|-<br />
|}<br />
<br />
== Technical overview ==<br />
* Based on HTML5, CSS, Javascript (Frameworks jQuery and jQTouch)<br />
* Optimized for Webkit browsers like Mobile Safari and Chrome. Will also work with restrictions on Firefox and Opera Mobile<br />
* Complete offline capability<br />
<br />
===Offline Mode details===<br />
<br />
The OX Mobile Web App uses HTML5 to provide an offline mode for the user. To do this, there are two different kinds of storage mechanisms.<br />
<br />
* The whole application will be cached using the "HTML5 application cache". This will be done on the first visit/start of the app. After this initial download, all graphics, language files, js-files and everything else which is needed to run the app is stored locally on your phone in a storage managed by the browser.<br />
<br />
* The data from the OX server will be stored using the HTML5 storage mechanism which will be supportet by the users device. These can be a HTML5 local storage, session storage or an SQLite database. For the user there's no difference between these different storage modes.<br />
<br />
Note: In case your device has no storage support (like the Nokia N97), a log message will inform you about this. The log can be found under the settings page, hitting the button in the upper right corner showing the exclamation mark symbol.<br />
<br />
== Requirements ==<br />
<br />
* Open-Xchange Server >= v.6.20<br />
* 1GB RAM<br />
<br />
== Download & Documentation==<br />
<br />
Please note that everything from this page and beyond is in Preview: This means nothing is final, changes will be made before final release, stability is not guaranteed and nothing from this site should be used in production.<br />
<br />
Follow this [http://software.open-xchange.com/OX6/OXtender-unstable/MobileApp/ link] to download the installation package, Release Notes and documentation.<br />
<br />
{{InstallPlugin|pluginname=open-xchange-gui-mobile-v2-gui open-xchange-gui-mobile-v2|sopath=OXtender-unstable/MobileApp|reponame=mobilewebapp}}<br />
<br />
== Configuration ==<br />
<br />
Installation on the Apache or another webserver:<br />
* After installation locate the installed files in your webroot directory, i.e. <code>/var/www/ox6-mobile-v2/</code> on Debian<br />
* Edit the file <code>"ox-access.conf"</code> in directory ox6-mobile-v2<br />
* If your open-xchange server is running on a different host, change localhost to your OX server address, i.e. "<code>https://example.com/ajax</code>". '''Note''': We strongly recommend the usage of https, otherwise data will be transmitted unencrypted via client and server<br />
* run the command (adopt webserver path on SLES/RHEL).<br />
$ /opt/open-xchange/sbin/update-cache.manifest /var/www/ox6-mobile-v2/cache.manifest.in /var/www/ox6-mobile-v2/cache.manifest /var/www/ox6-mobile-v2/ox-access.conf<br />
* You also need to add a new mimetype to your webserver configuration to make sure the caching (offline mode) works. <br />
** On Apache servers you can add the mimetype either global or via "<code>.htaccess</code>" file.<br />
** For global configuration edit the file <code>mime.conf</code> under <code>/etc/apache2/mods-enabled/</code><br />
** Add the line "<code>AddType text/cache-manifest .manifest</code>" to the file, save and restart apache<br />
** For configuration via <code>.htaccess</code> file just add a .htaccess file to the install directory. This should include the line "<code>AddType text/cache-manifest .manifest'</code>". '''Note''': Either the global configuration or the .htaccess file should be used. (.htaccess files will only work if your Apache settings contain <code>AllowOverride</code>. For further information on mime types, please refer to your webservers user manual)<br />
<br />
* For more details and README see the systems documentation directory (/usr/share/doc).<br />
<br />
==Running the OX Mobile Web App on your smartphone==<br />
<br />
After installation of the App on your webserver, a client can easily access the app via his phone's browser. We recommend to add a new subdomain to your web address to make access for clients easy. A short subdomain like <code>https://m.example.com</code> which points to your installation will save users from entering a long URL on their devices.<br />
<br />
Like mentioned before, the OX Mobile Web App is a pure web application. Due to this fact there is no installation or download needed to use this app on a smartphone. Just add a bookmark in your browser to access the app again later. <br />
<br />
Especially on iOS devices there's a seamless integration within the native apps installed via the AppStore®. Just add a new bookmark to the OX Mobile Web App and choose "Add to homescreen". After this, the OX Mobile Web App will place a new app icon on the homescreen.<br />
<br />
===Using the offline mode===<br />
<br />
During the first run, the app is stored localy on your smartphone. These caching mechanism makes a later access to the app very fast and gives you the possibility to run the app even if there's no internet connection available. <br />
<br />
The OX Mobile Web App detects on startup whether there's an internet connection available or not. If not, the App will start in offline mode. In this case a plane icon is shown in the upper left corner of the main menu. In offline mode you can access all your subscribed contacts and all of your appointments. Also all your mail headlines are available. Furthermore each email which was opened earlier is available in offline mode. <br />
<br />
'''Note:''' At the moment the OX Mobile Web App will not detect if internet connection reappears during a run in offline mode. To re-enter online mode just restart the app.<br />
<br />
===Known Problems===<br />
<br />
* The OX Mobile Web App uses a custom, built-in navigation and history. To navigate back you will have to use the "back" buttons located on the top-left of the page. Do not use browser's back button. This causes the app to jump to the login screen and you will have to reload the app.<br />
<br />
* If you want to use the App in airplane mode or no network connection is availabe, the android browser will show up a message like "page could not be loaded due to missing network connection". Just ignore this alert and press "OK". The app will work in offline mode even android shows up this message. <br />
<br />
* If you clean the browser cache on your device or reset it to defaults, all local stored data will be flushed.<br />
<br />
== Deployment as native app ==<br />
<br />
The OX Mobile Web App can also be deployed as a native smartphone app. This option is available for Android Systems and later for iOS, too. As Android allows installation of apps from every location you can place an *.apk file on a webserver or in your own Android App-Store. The OX Mobile Web App will act like any other app on the device and offers the same functionality as the web hosted variant.<br />
<br />
Deploying a native iOS App can only be done via the Apple AppStore®. To do so you need to submit your special branded version of the app to Apple. Only Apple decides if the app will be listed in the AppStore or not. These option will not be available for the Preview version of the app.<br />
<br />
For more information on native app deployment please contact us directly.<br />
<br />
== Branding options ==<br />
=== Application name===<br />
The OX Mobile Web App comes with the standard name set "OX Mobile Web App". This title is saved in a png file under "/lib/jqtouch/themes/cupertino/external/brand.png". To brand the app with you custom title just replace this file in the standard theme or you own theme. To configure the page title (in html title tag) please use the i18n module:<br />
<br />
# Locate your installstion directory (i.e. /var/www/ox6-mobile-v2)<br />
# Change to "lang" folder<br />
# The folder contains all available language files (*.po)<br />
# Open one of the files and locate the line containing msgid "OX Mobile" <br />
# Change the corresponding msgstr to your title of the app, i.e. "My App". <br />
# Do this for all language files<br />
* Note: Do not change the '''msgid''', this must be "OX Mobile". Only change the '''msgstr''' value.<br />
<br />
This title will also be the "App title" for the iPhone when the function "Add to homescreen" is used.<br />
<br />
== Theming ==<br />
<br />
The OX Mobile Web App is themed via CSS and HTML. To create your own theme you will have to create new graphics and edit the css files in the theme path. To do so follow the steps below:<br />
<br />
# Locate the theme path under "path to your webroot/ox6-mobile-v2/lib/jqtouch/themes"<br />
# The default theme is named "cupertino". To create your own theme make a copy of this folder and backup the original one<br />
# The folder contains two css files and two folders with images. The file jqt_theme.css contains all styles which belong to the "overall" look of the app. These are styles for lists, buttons, background, toolbars and so on. The file ox_theme.css contains more high level theming styles such as module icons, progress bars, infobox and the way the details in lists are shown (like the appointment lists or mail list). To change the whole look of the app (like colors) you will mainly edit the file jqt_theme.css<br />
# The folders "img" and "external" hold all graphics which are used in the app. To change them, just edit and save them under the same name. Don't change filenames or the theme will be broken. Also keep all file dimensions and file types (*.png, *.jpg). Changing files dimensions will corrupt the theme and layout will be broken.<br />
# Always remember: Your are designing for mobile. This means: Keep fonts clear and easy to read. Keep file sizes small due to small bandwiths. Keep buttons big enought the user can touch them easily.<br />
<br />
==Reporting==<br />
<br />
Open-Xchange is interested in learning about bugs, specifically in your runtime environment. If you experience any misbehaviors, please report bugs via our public bugzilla:<br />
[https://bugzilla.open-xchange.com/enter_bug.cgi?product=OX%20Mobile%20App Open-Xchange Bugzilla]<br><br />
Product: OX Mobile App<br />
<br />
The OX Mobile Web App logs all errors to a logfile which can be found under settings -> log.<br />
<br />
== Please note ==<br />
<br />
There may be some issues with checkboxes on Android devices. Sometimes checkboxes and listboxes do not respond to tap actions. If so, please rotate your phone to landscape mode and back. Then, the checkboxes should response again <br />
<br />
Please read the SDB article to inform you about the reasons and solution.<br />
<br />
[[Category: OX6]]</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Template:ApacheOXConf&diff=7553Template:ApacheOXConf2011-03-21T11:02:31Z<p>Holgi: </p>
<hr />
<div>Configure the ''mod_proxy_ajp'' module by creating a new Apache configuration file.<br />
<br />
$ vim {{{ajpconf}}}<br />
<br />
<Location /axis2><br />
# restrict access to the soap provisioning API<br />
Order Deny,Allow<br />
Deny from all<br />
Allow from 127.0.0.1<br />
# you might add more ip addresses / networks here<br />
# Allow from 192.168 10 172.16<br />
</Location><br />
<br />
{{{loadmodule}}}<br />
<br />
<IfModule mod_proxy_ajp.c><br />
ProxyRequests Off<br />
<Proxy balancer://oxcluster><br />
Order deny,allow<br />
Allow from all<br />
# multiple server setups need to have the hostname inserted instead localhost<br />
BalancerMember ajp://localhost:8009 smax=0 ttl=60 retry=60 loadfactor=50 route=OX1<br />
# Enable and maybe add additional hosts running OX here<br />
# BalancerMember ajp://oxhost2:8009 smax=0 ttl=60 retry=60 loadfactor=50 route=OX2<br />
ProxySet stickysession=JSESSIONID timeout=70 <br />
</Proxy><br />
<Proxy /ajax><br />
ProxyPass balancer://oxcluster/ajax<br />
</Proxy><br />
<Proxy /axis2><br />
ProxyPass balancer://oxcluster/axis2<br />
</Proxy><br />
<Proxy /servlet><br />
ProxyPass balancer://oxcluster/servlet<br />
</Proxy><br />
<Proxy /infostore><br />
ProxyPass balancer://oxcluster/infostore<br />
</Proxy><br />
<Proxy /publications><br />
ProxyPass balancer://oxcluster/publications<br />
</Proxy><br />
<Proxy /Microsoft-Server-ActiveSync><br />
ProxyPass balancer://oxcluster/Microsoft-Server-ActiveSync<br />
</Proxy><br />
<Proxy /usm-json><br />
ProxyPass balancer://oxcluster/usm-json<br />
</Proxy><br />
</IfModule><br />
<br />
<br />
Modify the default website settings to display the Open-Xchange GUI<br />
<br />
$ vim {{{apacheconf}}}<br />
<br />
<VirtualHost *:80><br />
ServerAdmin webmaster@localhost<br />
<br />
DocumentRoot {{{docroot}}}<br />
<br />
<Directory {{{docroot}}}><br />
AllowOverride None<br />
Order allow,deny<br />
allow from all<br />
RedirectMatch ^/$ /ox6/<br />
Options +FollowSymLinks +SymLinksIfOwnerMatch<br />
</Directory><br />
# deflate<br />
AddOutputFilterByType DEFLATE text/html text/plain text/javascript application/javascript text/css text/xml application/xml text/x-js application/x-javascript<br />
<br />
# pre-compressed files<br />
AddType text/javascript .jsz<br />
AddType text/css .cssz<br />
AddType text/xml .xmlz<br />
AddType text/plain .po<br />
<br />
AddEncoding gzip .jsz .cssz .xmlz<br />
SetEnvIf Request_URI "\.(jsz|cssz|xmlz)$" no-gzip<br />
<br />
ExpiresActive On<br />
<br />
<Location /ox6><br />
# Expires (via ExpiresByType to override global settings)<br />
ExpiresByType image/gif "access plus 6 months"<br />
ExpiresByType image/png "access plus 6 months"<br />
ExpiresByType image/jpg "access plus 6 months"<br />
ExpiresByType image/jpeg "access plus 6 months"<br />
ExpiresByType text/css "access plus 6 months"<br />
ExpiresByType text/html "access plus 6 months"<br />
ExpiresByType text/xml "access plus 6 months"<br />
ExpiresByType text/javascript "access plus 6 months"<br />
ExpiresByType text/x-js "access plus 6 months"<br />
ExpiresByType application/x-javascript "access plus 6 months"<br />
ExpiresDefault "access plus 6 months"<br />
Header append Cache-Control "private"<br />
Header unset Last-Modified<br />
Header unset Vary<br />
# Strip version<br />
RewriteEngine On<br />
RewriteRule v=\w+/(.+) $1 [L]<br />
# Turn off ETag<br />
Header unset ETag<br />
FileETag None<br />
</Location><br />
<br />
<Location /ox6/ox.html><br />
ExpiresByType text/html "now"<br />
ExpiresDefault "now"<br />
Header unset Last-Modified<br />
Header set Cache-Control "no-store, no-cache, must-revalidate, post-check=0, pre-check=0"<br />
# Turn off ETag<br />
Header unset ETag<br />
FileETag None<br />
</Location><br />
<br />
<Location /ox6/index.html><br />
ExpiresByType text/html "now"<br />
ExpiresDefault "now"<br />
Header unset Last-Modified<br />
Header set Cache-Control "no-store, no-cache, must-revalidate, post-check=0, pre-check=0"<br />
# Turn off ETag<br />
Header unset ETag<br />
FileETag None<br />
</Location><br />
</VirtualHost></div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Lawful_Interception&diff=7518Lawful Interception2011-03-11T10:22:38Z<p>Holgi: /* Lawful Interception (Telekommunikationsüberwachung) */</p>
<hr />
<div>= Lawful Interception (Telekommunikationsüberwachung) =<br />
<br />
This article describes the configuration options which are needet to activate the client IP transmission for email service usage.<br />
<br />
== Configuration ==<br />
==Mail Store Access (IMAP)==<br />
For IMAP access, it is possible to let the groupware server issue a noop command directly after login. This noop command gets the "real" client IP as argument. Activation is done via <br />
vim /opt/open-xchange/etc/groupware/imap.properties<br />
<br />
option to change is:<br />
<br />
# Whether client's IP address should be propagated by a NOOP command; e.g. <br />
"A01 NOOP <CLIENT_IP>"<br />
com.openexchange.imap.propagateClientIPAddress=false<br />
<br />
in case users are allowed to configure external email accounts, a list of imap servers can be specified, which, when added as external accounts, will also receive a noop command with IP as argument direct after login:<br />
<br />
# Configure a comma-separated list of external IMAP server's host names <br />
# which should receive client's IP address by a NOOP command, too<br />
com.openexchange.imap.propagateHostNames=<br />
<br />
==MTA access (SMTP)==<br />
<br />
For all emails send by the groupware process, it is possible to set the custom header "X-Originating-IP" with the "real" client IP as argument. This can be achieved by editing mail.properties:<br />
vim /opt/open-xchange/etc/groupware/mail.properties <br />
option to change is:<br />
# Set whether client's IP address should be added to mail headers on delivery<br />
# as custom header "X-Originating-IP"<br />
com.openexchange.mail.addClientIPAddress=true</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Lawful_Interception&diff=7513Lawful Interception2011-03-10T21:40:05Z<p>Holgi: /* Mail Store Access (IMAP) */</p>
<hr />
<div>= Lawful Interception (Telekommunikationsüberwachung) =<br />
<br />
This article describes the configuration to activate the needed client IP transmission for email service usage.<br />
<br />
== Configuration ==<br />
==Mail Store Access (IMAP)==<br />
For IMAP access, it is possible to let the groupware server issue a noop command directly after login. This noop command gets the "real" client IP as argument. Activation is done via <br />
vim /opt/open-xchange/etc/groupware/imap.properties<br />
<br />
option to change is:<br />
<br />
# Whether client's IP address should be propagated by a NOOP command; e.g. <br />
"A01 NOOP <CLIENT_IP>"<br />
com.openexchange.imap.propagateClientIPAddress=false<br />
<br />
in case users are allowed to configure external email accounts, a list of imap servers can be specified, which, when added as external accounts, will also receive a noop command with IP as argument direct after login:<br />
<br />
# Configure a comma-separated list of external IMAP server's host names <br />
# which should receive client's IP address by a NOOP command, too<br />
com.openexchange.imap.propagateHostNames=<br />
<br />
==MTA access (SMTP)==<br />
<br />
For all emails send by the groupware process, it is possible to set the custom header "X-Originating-IP" with the "real" client IP as argument. This can be achieved by editing mail.properties:<br />
vim /opt/open-xchange/etc/groupware/mail.properties <br />
option to change is:<br />
# Set whether client's IP address should be added to mail headers on delivery<br />
# as custom header "X-Originating-IP"<br />
com.openexchange.mail.addClientIPAddress=true</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Lawful_Interception&diff=7512Lawful Interception2011-03-10T19:32:15Z<p>Holgi: /* Lawful_Interception (Telekommunikationsüberwachung) */</p>
<hr />
<div>= Lawful Interception (Telekommunikationsüberwachung) =<br />
<br />
This article describes the configuration to activate the needed client IP transmission for email service usage.<br />
<br />
== Configuration ==<br />
==Mail Store Access (IMAP)==<br />
For IMAP access, it is possible to let the groupware server issue a noop command directly after login. This noop command gets the "real" client IP as argument. Activation is done via <br />
vim /opt/open-xchange/etc/groupware/imap.properties<br />
<br />
option to change is:<br />
<br />
# Whether client's IP address should be propagated by a NOOP command; e.g. <br />
"A01 NOOP <CLIENT_IP>"<br />
com.openexchange.imap.propagateClientIPAddress=false<br />
<br />
in case the users are allowed to configure external email accounts, a list of imap servers can be specified which, when added as external accounts, will also receive a noop command with IP as argument direct after login:<br />
<br />
# Configure a comma-separated list of external IMAP server's host names <br />
# which should receive client's IP address by a NOOP command, too<br />
com.openexchange.imap.propagateHostNames=<br />
<br />
This option is useful in case users configure own managed IMAP server as external servers.<br />
<br />
==MTA access (SMTP)==<br />
<br />
For all emails send by the groupware process, it is possible to set the custom header "X-Originating-IP" with the "real" client IP as argument. This can be achieved by editing mail.properties:<br />
vim /opt/open-xchange/etc/groupware/mail.properties <br />
option to change is:<br />
# Set whether client's IP address should be added to mail headers on delivery<br />
# as custom header "X-Originating-IP"<br />
com.openexchange.mail.addClientIPAddress=true</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Lawful_Interception&diff=7511Lawful Interception2011-03-10T19:27:04Z<p>Holgi: /* MTA access (SMTP) */</p>
<hr />
<div>= Lawful_Interception (Telekommunikationsüberwachung) =<br />
<br />
This article describes the configuration to activate the needed client IP transmission for email usage.<br />
<br />
== Configuration ==<br />
==Mail Store Access (IMAP)==<br />
For the IMAP access, it is possible to let the groupware server issue a noop command directly after login. This noop command gets the "real" client IP as argument. Activation is done via <br />
vim /opt/open-xchange/etc/groupware/imap.properties<br />
<br />
option to change is:<br />
<br />
# Whether client's IP address should be propagated by a NOOP command; e.g. <br />
"A01 NOOP <CLIENT_IP>"<br />
com.openexchange.imap.propagateClientIPAddress=false<br />
<br />
in case the users are allowed to configure external email accounts, a list of imap servers can be specified which, when added as external accounts, will also receive a noop command with IP as argument direct after login:<br />
<br />
# Configure a comma-separated list of external IMAP server's host names <br />
# which should receive client's IP address by a NOOP command, too<br />
com.openexchange.imap.propagateHostNames=<br />
<br />
==MTA access (SMTP)==<br />
<br />
For all emails send by the groupware process, it is possible to let the set the custom header "X-Originating-IP" with the "real" client IP as argument. This can be achieved by editing mail.properties:<br />
vim /opt/open-xchange/etc/groupware/mail.properties <br />
option to change is:<br />
# Set whether client's IP address should be added to mail headers on delivery<br />
# as custom header "X-Originating-IP"<br />
com.openexchange.mail.addClientIPAddress=true</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Lawful_Interception&diff=7510Lawful Interception2011-03-10T19:23:03Z<p>Holgi: /* Mail Store Access (IMAP) */</p>
<hr />
<div>= Lawful_Interception (Telekommunikationsüberwachung) =<br />
<br />
This article describes the configuration to activate the needed client IP transmission for email usage.<br />
<br />
== Configuration ==<br />
==Mail Store Access (IMAP)==<br />
For the IMAP access, it is possible to let the groupware server issue a noop command directly after login. This noop command gets the "real" client IP as argument. Activation is done via <br />
vim /opt/open-xchange/etc/groupware/imap.properties<br />
<br />
option to change is:<br />
<br />
# Whether client's IP address should be propagated by a NOOP command; e.g. <br />
"A01 NOOP <CLIENT_IP>"<br />
com.openexchange.imap.propagateClientIPAddress=false<br />
<br />
in case the users are allowed to configure external email accounts, a list of imap servers can be specified which, when added as external accounts, will also receive a noop command with IP as argument direct after login:<br />
<br />
# Configure a comma-separated list of external IMAP server's host names <br />
# which should receive client's IP address by a NOOP command, too<br />
com.openexchange.imap.propagateHostNames=<br />
<br />
==MTA access (SMTP)==</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Lawful_Interception&diff=7509Lawful Interception2011-03-10T18:06:45Z<p>Holgi: Created page with "= Lawful_Interception (Telekommunikationsüberwachung) = This article describes the configuration to activate the needed client IP transmission for email usage. == Configurati..."</p>
<hr />
<div>= Lawful_Interception (Telekommunikationsüberwachung) =<br />
<br />
This article describes the configuration to activate the needed client IP transmission for email usage.<br />
<br />
== Configuration ==<br />
==Mail Store Access (IMAP)==<br />
<br />
==MTA access (SMTP)==</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Template:Main_Page_Documentation&diff=7508Template:Main Page Documentation2011-03-10T18:01:33Z<p>Holgi: </p>
<hr />
<div>__NOTOC__<br />
{{#ifeq: {{{1}}} | HESE | <!-- only HESE: headline --> {{=}}Manuals{{=}}<br />
==Hosting Edition / Server Edition (HE/SE)==<br />
}}{{#ifeq: {{{1}}} | CE | <!-- only CE: headline --> {{=}}Manuals{{=}}<br />
==Community Edition (CE)==<br />
}}{{#ifeq: {{{1}}} | AE | | <!-- NOT on AE, i.e. HESE and CE: manuals for both: --><br />
* Installation and Administration Manual ([http://software.open-xchange.com/OX6/doc/OX6-Installation-and-Administration.pdf English])<br />
* Provisioning of users and groups ([http://software.open-xchange.com/OX6/doc/OX6-Provisioning.pdf English])<br />
* User Manual ([http://software.open-xchange.com/OX6/doc/OX6-User-Guide-German.pdf German], [http://software.open-xchange.com/OX6/doc/OX6-User-Guide-English.pdf English], [http://software.open-xchange.com/OX6/doc/OX6-User-Guide-French.pdf French], [http://software.open-xchange.com/OX6/doc/OX6-User-Guide-Dutch.pdf Dutch], [http://software.open-xchange.com/OX6/doc/OX6-User-Guide-Spanish.pdf Spanish], [http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Polish.pdf Polish], [http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Japanese.pdf Japanese])<br />
}}{{#ifeq: {{{1}}} | AE | <!-- only AE --> <br />
== Advanced Server Edition (ASE) ==<br />
* Installation and Administration Manual ([http://software.open-xchange.com/OX6/OXASE/doc/oxase_handbuch_6_18_2_de.pdf German], [http://software.open-xchange.com/OX6/OXASE/doc/oxase_handbuch_6_18_2_en.pdf English])<br />
* User Manual ([http://software.open-xchange.com/OX6/doc/OX6-User-Guide-German.pdf German], [http://software.open-xchange.com/OX6/doc/OX6-User-Guide-English.pdf English], [http://software.open-xchange.com/OX6/doc/OX6-User-Guide-French.pdf French], [http://software.open-xchange.com/OX6/doc/OX6-User-Guide-Dutch.pdf Dutch], [http://software.open-xchange.com/OX6/doc/OX6-User-Guide-Spanish.pdf Spanish], [http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Polish.pdf Polish], [http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Japanese.pdf Japanese])<br />
<br />
==Setup for synchronisation of Active Directory objects to OX ASE==<br />
* [[UCS_AD_Connector_en|Setup]]<br />
<br />
}}<br />
{{#ifeq: {{{1}}} | HESE | <!-- only on HESE: UCS --><br />
== Server Edition for Univention Corporate Server (SE for UCS)==<br />
* Installation and Administration Manual ([http://software.open-xchange.com/OX6/OXSEforUCS/doc/OXSE4UCS-German-v6.18.1.pdf German], [http://software.open-xchange.com/OX6/OXSEforUCS/doc/OXSE4UCS-English-v6.18.1.pdf English])<br />
* User Manual ([http://software.open-xchange.com/OX6/doc/OX6-User-Guide-German.pdf German], [http://software.open-xchange.com/OX6/doc/OX6-User-Guide-English.pdf English], [http://software.open-xchange.com/OX6/doc/OX6-User-Guide-French.pdf French], [http://software.open-xchange.com/OX6/doc/OX6-User-Guide-Dutch.pdf Dutch], [http://software.open-xchange.com/OX6/doc/OX6-User-Guide-Spanish.pdf Spanish], [http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Polish.pdf Polish], [http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Japanese.pdf Japanese])<br />
<br />
==Setup for synchronisation of Active Directory objects to OXSE for UCS==<br />
* [[UCS_AD_Connector_en|Setup]]<br />
<br />
| }}<br />
{{#ifeq: {{{1}}} | CE | | <!-- not on CE: OXtenders --> <br />
==OXtender for Business Mobility==<br />
<br />
* User Manual OXtender for Business Mobility ([http://software.open-xchange.com/OX6/doc/BusinessMobilityOXtender/OX6-OXtender-for-Business-Mobility-German.pdf German], [http://software.open-xchange.com/OX6/doc/BusinessMobilityOXtender/OX6-OXtender-for-Business-Mobility-English.pdf English], [http://software.open-xchange.com/OX6/doc/BusinessMobilityOXtender/OX6-OXtender-for-Business-Mobility-French.pdf French], [http://software.open-xchange.com/OX6/doc/BusinessMobilityOXtender/OX6-OXtender-for-Business-Mobility-Dutch.pdf Dutch], [http://software.open-xchange.com/OX6/doc/BusinessMobilityOXtender/OX6-OXtender-for-Business-Mobility-Spanish.pdf Spanish])<br />
<br />
==OXtender 2 for MS Outlook==<br />
<br />
* User Manual OXtender for MS Outlook ([http://software.open-xchange.com/OX6/doc/Outlook-OXtender/OX6-OXtender2-for-Microsoft-Outlook-German.pdf German], [http://software.open-xchange.com/OX6/doc/Outlook-OXtender/OX6-OXtender2-for-Microsoft-Outlook-English.pdf English], [http://software.open-xchange.com/OX6/doc/Outlook-OXtender/OX6-OXtender2-for-Microsoft-Outlook-French.pdf French] [http://software.open-xchange.com/OX6/doc/Outlook-OXtender/OX6-OXtender2-for-Microsoft-Outlook-Dutch.pdf Dutch], [http://software.open-xchange.com/OX6/doc/Outlook-OXtender/OX6-OXtender2-for-Microsoft-Outlook-Spanish.pdf Spanish], [http://software.open-xchange.com/OX6/doc/Outlook-OXtender/OX6-OXtender2-for-Microsoft-Outlook-Polish.pdf Polish])<br />
<br />
==OXtender for Mac OS X==<br />
<br />
* User Manual OXtender for Mac OS X ([http://software.open-xchange.com/OX6/doc/Mac-OXtender/OXtender-for-MacOS-X-Manual-German-v1.0.pdf German], [http://software.open-xchange.com/OX6/doc/Mac-OXtender/OXtender-for-MacOS-X-Manual-English.pdf English], [http://software.open-xchange.com/OX6/doc/Mac-OXtender/OXtender-for-MacOS-X-Manual-French.pdf French], [http://software.open-xchange.com/OX6/doc/Mac-OXtender/OXtender-for-MacOS-X-Manual-Dutch.pdf Dutch], [http://software.open-xchange.com/OX6/doc/Mac-OXtender/OXtender-for-MacOS-X-Manual-Spanish.pdf Spanish])<br />
<br />
==Client Updater ==<br />
<br />
* User Manual Open-Xchange Client Updater ([http://software.open-xchange.com/OX6/6.10/doc/Outlook-OXtender/Updater-Overview-German.pdf German], [http://software.open-xchange.com/OX6/6.10/doc/Outlook-OXtender/Updater-Overview-English.pdf English], [http://software.open-xchange.com/OX6/6.10/doc/Outlook-OXtender/Updater-Overview-French.pdf French], [http://software.open-xchange.com/OX6/6.10/doc/Outlook-OXtender/Updater-Overview-Dutch.pdf Dutch], [http://software.open-xchange.com/OX6/6.10/doc/Outlook-OXtender/Updater-Overview-Spanish.pdf Spanish])<br />
* Administrator Manual Open-Xchange Client Updater Update.XML ([http://software.open-xchange.com/OX6/6.10/doc/Outlook-OXtender/Updater-XML-English.pdf English])<br />
}}<br />
{{#ifeq: {{{1}}} | HESE | <!-- only on HESE --><br />
{{=}} Parallels Integration (POA + Virtuozzo) {{=}}<br />
* [[POAIntegrationGuide|OX HE Integration for Parallels Operations Automation]]<br />
* [[Ox_virtuozzo_templates|OX HE Virtuozzo Application Templates(Updated to 6.12)]]<br />
<br />
{{=}} Parallels Integration (4PSA OXtender for Plesk) {{=}}<br />
* [http://oxpedia.org/wiki/index.php?title=Plesk_Oxtender 4PSA OXtender for Parallels Plesk Installation]<br />
<br />
{{=}} Data MigrationTools {{=}}<br />
* [[Open-Xchange_Datamigration_OX5toOX6_Installation|Download and Install OX5 to OXSE]]<br />
* [http://www.open-xchange.com/en/ox5_vs_ox6 Differences between Open-Xchange Server 5 and Open-Xchange Server 6]<br />
* [[Datamigration_Fieldcomparison|Open-Xchange Data Migration Tools - Field Comparison OX5 vs. OX6]]<br />
}}{{#ifeq: {{{1}}} | AE | <!-- only on AE: data migration tools --><br />
{{=}} Data MigrationTools {{=}}<br />
* [[Open-Xchange_Datamigration_OXEEtoOXAE_Installation|Download and Install OXEE to OXAE]]<br />
* [[Open-Xchange_Datamigration_OX5toOXAE_Installation|Download and Install OX5 to OXAE]]<br />
* [http://www.open-xchange.com/en/ox5_vs_ox6 Differences between Open-Xchange Server 5 and Open-Xchange Server 6]<br />
* [[Datamigration_Fieldcomparison|Open-Xchange Data Migration Tools - Field Comparison OX5 vs. OX6]]<br />
}}<br />
{{=}} Troubleshooting {{=}}<br />
* [http://www.open-xchange.com/forum/ Open-Xchange Forum]<br />
* Check the [http://sdb.open-xchange.com/ Open-Xchange Support Database]<br />
* FAQs can be found in the [http://sdb.open-xchange.com/faq SDB FAQ section].<br />
* [[Passwords in Open-Xchange]]<br />
{{#ifeq: {{{1}}} | CE | | * [[Outlook_OXtender_Best_Practice| Outlook OXtender best practice]]}} <!-- ONLY on HESE --> <br />
{{=}} Documentation and Examples {{=}}<br />
<br />
<br />
* [[DefaultTreeView|Changing the default tree view]]<br />
* [[SupportedCrawler | Open-Xchange Supported Crawler Matrix (Status OX6 v.6.16)]]<br />
* [[Architecture_Diagram | Software architecture diagram]]<br />
* [[Open-Xchange-Integration-SLES11 | Integrate Open-Xchange into SuSE Linux Enterprise Server 11]]<br />
* [[Load_balancing_and_clustering | Load balancing and OX clustering]]<br />
* [[Open-Xchange-RHEL-AD-Integration|Integration of Open-Xchange into MS Active Directory and Exchange ]]<br />
* [[Open-Xchange_Publishing|Publishing Data with Open-Xchange]]<br />
* [[FacebookMessaging_Bundle|Using the Facebook messaging with Open-Xchange]]<br />
* [[ContextRestore_Bundle|Restoring contexts using the context restore bundle]]<br />
* [[Lawful_Interception|Lawful Interception (Telekommunikationsüberwachung)]]<br />
<br />
{{#ifeq: {{{1}}} | AE | | * [[Open-Xchange_backup|Backup of an Open-Xchange installation]] }}<br />
<br />
{{#ifeq: {{{1}}} | HESE | <!-- ONLY on HESE --> <br />
{{=}} OXtender for Microsoft Outlook {{=}}<br />
* [[MSI| How to configure the OXtender .msi file for automatic creation of an Outlook profile and an IMAP account]]<br />
* [[MSIsilent| How to do the same as a silent installation]]<br />
* [[additional_language| How to add an additional Language]]<br />
* [[Outlook_OXtender_Best_Practice| Best practice]] <br />
<br />
}}<br />
{{=}} Whitepapers {{=}}<br />
* {{DocLink|docpath=whitepaper/OX6-Sizing-whitepaper.pdf|name=OX6 Sizing Whitepaper}}<br />
* {{DocLink|docpath=whitepaper/OX-Hosted-Architecture.pdf|name=OX6 Hosted Architecture}} <br />
* {{DocLink|docpath=whitepaper/OX-Directory-Integration-Whitepaper-English.pdf|name=Directory Integration Whitepaper}}<br />
* {{DocLink|docpath=whitepaper/oxae_whitepaper_oxforucs_de.pdf|name=OXAE/OX4UCS Whitepaper (German)}} <br />
* {{DocLink|docpath=whitepaper/oxae_whitepaper_oxforucs_en.pdf|name=OXAE/OX4UCS Whitepaper (English)}}<br />
* {{DocLink|docpath=whitepaper/ucs-xen_en.pdf|name=Install OX4UCS in Xen (English)}}<br />
* {{DocLink|docpath=whitepaper/GUI_and_Mobility.pdf|name=GUI and Mobility Training}}</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Template:ApacheOXConf&diff=7426Template:ApacheOXConf2011-03-04T06:44:46Z<p>Holgi: </p>
<hr />
<div>Configure the ''mod_proxy_ajp'' module by creating a new Apache configuration file.<br />
<br />
$ vim {{{ajpconf}}}<br />
<br />
{{{loadmodule}}}<br />
<br />
<IfModule mod_proxy_ajp.c><br />
ProxyRequests Off<br />
<Proxy balancer://oxcluster><br />
Order deny,allow<br />
allow from all<br />
# none single server setups need to have the hostname inserted in stead localhost<br />
BalancerMember ajp://localhost:8009 smax=0 ttl=60 retry=60 loadfactor=50 route=OX1<br />
# Enable and maybe add additional hosts running OX here<br />
# BalancerMember ajp://oxhost2:8009 smax=0 ttl=60 retry=60 loadfactor=50 route=OX2<br />
ProxySet stickysession=JSESSIONID timeout=70 <br />
</Proxy><br />
<Proxy /ajax><br />
ProxyPass balancer://oxcluster/ajax<br />
</Proxy><br />
<Proxy /axis2><br />
ProxyPass balancer://oxcluster/axis2<br />
</Proxy><br />
<Proxy /servlet><br />
ProxyPass balancer://oxcluster/servlet<br />
</Proxy><br />
<Proxy /infostore><br />
ProxyPass balancer://oxcluster/infostore<br />
</Proxy><br />
<Proxy /publications><br />
ProxyPass balancer://oxcluster/publications<br />
</Proxy><br />
<Proxy /Microsoft-Server-ActiveSync><br />
ProxyPass balancer://oxcluster/Microsoft-Server-ActiveSync<br />
</Proxy><br />
<Proxy /usm-json><br />
ProxyPass balancer://oxcluster/usm-json<br />
</Proxy><br />
</IfModule><br />
<br />
<br />
Modify the default website settings to display the Open-Xchange GUI<br />
<br />
For versions of Open-Xchange '''starting with''' 6.18:<br />
<br />
$ vim {{{apacheconf}}}<br />
<br />
<VirtualHost *:80><br />
ServerAdmin webmaster@localhost<br />
<br />
DocumentRoot {{{docroot}}}<br />
<br />
<Directory {{{docroot}}}><br />
AllowOverride None<br />
Order allow,deny<br />
allow from all<br />
RedirectMatch ^/$ /ox6/<br />
Options +FollowSymLinks +SymLinksIfOwnerMatch<br />
</Directory><br />
# deflate<br />
AddOutputFilterByType DEFLATE text/html text/plain text/javascript application/javascript text/css text/xml application/xml text/x-js application/x-javascript<br />
<br />
# pre-compressed files<br />
AddType text/javascript .jsz<br />
AddType text/css .cssz<br />
AddType text/xml .xmlz<br />
<br />
AddEncoding gzip .jsz .cssz .xmlz<br />
SetEnvIf Request_URI "\.(jsz|cssz|xmlz)$" no-gzip<br />
<br />
ExpiresActive On<br />
<br />
<Location /ox6><br />
# Expires (via ExpiresByType to override global settings)<br />
ExpiresByType image/gif "access plus 6 months"<br />
ExpiresByType image/png "access plus 6 months"<br />
ExpiresByType image/jpg "access plus 6 months"<br />
ExpiresByType image/jpeg "access plus 6 months"<br />
ExpiresByType text/css "access plus 6 months"<br />
ExpiresByType text/html "access plus 6 months"<br />
ExpiresByType text/xml "access plus 6 months"<br />
ExpiresByType text/javascript "access plus 6 months"<br />
ExpiresByType text/x-js "access plus 6 months"<br />
ExpiresByType application/x-javascript "access plus 6 months"<br />
ExpiresDefault "access plus 6 months"<br />
Header append Cache-Control "private"<br />
Header unset Last-Modified<br />
Header unset Vary<br />
# Strip version<br />
RewriteEngine On<br />
RewriteRule v=\w+/(.+) $1 [L]<br />
# Turn off ETag<br />
Header unset ETag<br />
FileETag None<br />
</Location><br />
<br />
<Location /ox6/ox.html><br />
ExpiresByType text/html "now"<br />
ExpiresDefault "now"<br />
Header unset Last-Modified<br />
Header set Cache-Control "no-store, no-cache, must-revalidate, post-check=0, pre-check=0"<br />
# Turn off ETag<br />
Header unset ETag<br />
FileETag None<br />
</Location><br />
<br />
<Location /ox6/index.html><br />
ExpiresByType text/html "now"<br />
ExpiresDefault "now"<br />
Header unset Last-Modified<br />
Header set Cache-Control "no-store, no-cache, must-revalidate, post-check=0, pre-check=0"<br />
# Turn off ETag<br />
Header unset ETag<br />
FileETag None<br />
</Location><br />
</VirtualHost><br />
<br />
For versions of Open-Xchange '''prior''' to 6.18:<br />
<br />
$ vim {{{apacheconf}}}<br />
<br />
<VirtualHost *:80><br />
ServerAdmin webmaster@localhost<br />
<br />
DocumentRoot {{{docroot}}}<br />
<br />
<Directory {{{docroot}}}><br />
AllowOverride None<br />
Order allow,deny<br />
allow from all<br />
RedirectMatch ^/$ /ox6/<br />
</Directory><br />
<br />
ExpiresActive On<br />
ExpiresByType image/gif "access plus 23 hours"<br />
ExpiresByType image/png "access plus 23 hours"<br />
ExpiresByType image/jpg "access plus 23 hours"<br />
ExpiresByType image/jpeg "access plus 23 hours"<br />
ExpiresByType text/javascript "access plus 23 hours"<br />
ExpiresByType text/css "access plus 23 hours"<br />
ExpiresByType text/html "access plus 23 hours"<br />
ExpiresByType application/x-javascript "access plus 23 hours"<br />
<Files ~ "\.(js|css|gif|jpe?g|png)$"><br />
Header append Cache-Control "public"<br />
</Files><br />
<br />
DeflateFilterNote ratio<br />
AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/x-js application/x-javascript application/javascript<br />
BrowserMatch ^Mozilla/4 gzip-only-text/html<br />
BrowserMatch ^Mozilla/4\.0[678] no-gzip<br />
BrowserMatch \bMSI[E] !no-gzip !gzip-only-text/html<br />
Header append Vary User-Agent env=!dont-vary<br />
</VirtualHost></div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Template:OX_HE_Tutorial_Next&diff=7407Template:OX HE Tutorial Next2011-03-03T09:59:01Z<p>Holgi: /* Mobile GUI (pre Beta) */</p>
<hr />
<div>= Recommended Optional Next Steps =<br />
<br />
You will find plenty of additional documentation for customization of OX in our knowledge base [http://oxpedia.org]<br />
<br />
When the main setup is completed, we recommend to start with the following articles to enhance your system and to become more attractive for your users.<br />
<br />
<br />
== Automated Frontend Tests ==<br />
<br />
It is a good idea, to verify the functionality of your freshly set up and integrated system. Our QA department does that with tests, running automatically on the web frontend. We release this tests with every release and recommend you to use them to verify your environment with every update.<br />
<br />
Read more about [[Automated_GUI_Tests]]<br />
<br />
<br />
== Monitoring / Statistics ==<br />
<br />
It is recommended to implement at least a minimal monitoring/Statistics solution to get an overview of the systems health. If you have a support contract with Open-Xchange, it is very helpful, if the support can access the monitoring graphs. There are example scripts for a basic monitoring with [[http://munin-monitoring.org/ Munin]] available.<br />
<br />
Read more about installing and configuring [[OX_munin_scripts|Munin scripts for Open-Xchange]]<br />
<br />
<br />
== Upsell Plugin / Webmail Replacement ==<br />
<br />
If you want to use your OX based Webmail system to upsell premium functions like full groupware functionality or like push to mobile phones, it is strongly recommended to use the in-app sales process.<br />
<br />
Read more about [[Upsell]]<br />
<br />
<br />
<!-- <br />
== Mobile Autoconfiguration ==<br />
<br />
If you have the OXtender for Business Mobility installed, it is recommended also to install the autoconfiguration plugin, to allow your users to configure their iPhones and Windows Mobile devices directly from within the OX webfrontend. All you need is to adapt the SMS interface to send autoprovisioning SMS. <br />
<br />
Read more about WO_IST_DAS_DOKUMENTIERT<br />
--><br />
<br />
== Branding ==<br />
<br />
If you want OX to look more like your own Corporate Identity, including your logo, product name and maybe your colors, this can be easily achieved by changing the logos and stylesheets.<br />
<br />
Read more about: [[Gui_Theming_Description]]<br />
<br />
Read more about: [[Gui_Plugin_Development|Gui Branding Plugins]]<br />
<br />
<br />
== Backup ==<br />
<br />
It is recommended to run regular backups for your OX installation. This can be done with every backup solution for Linux.<br />
<br />
Read more about [[Open-Xchange_backup|Backup your Open-Xchange installation]]<br />
<br />
<br />
== OXMobileApp (pre Beta) ==<br />
<br />
This GUI is designed to run in the mobile browsers and brings basic Open-Xchange functionality to all available HTML 5 capable devices.<br />
<br />
Read more about [[OXMobileApp]]</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Template:OX_HE_Tutorial_Next&diff=7406Template:OX HE Tutorial Next2011-03-03T09:58:24Z<p>Holgi: /* Recommended Optional Next Steps */</p>
<hr />
<div>= Recommended Optional Next Steps =<br />
<br />
You will find plenty of additional documentation for customization of OX in our knowledge base [http://oxpedia.org]<br />
<br />
When the main setup is completed, we recommend to start with the following articles to enhance your system and to become more attractive for your users.<br />
<br />
<br />
== Automated Frontend Tests ==<br />
<br />
It is a good idea, to verify the functionality of your freshly set up and integrated system. Our QA department does that with tests, running automatically on the web frontend. We release this tests with every release and recommend you to use them to verify your environment with every update.<br />
<br />
Read more about [[Automated_GUI_Tests]]<br />
<br />
<br />
== Monitoring / Statistics ==<br />
<br />
It is recommended to implement at least a minimal monitoring/Statistics solution to get an overview of the systems health. If you have a support contract with Open-Xchange, it is very helpful, if the support can access the monitoring graphs. There are example scripts for a basic monitoring with [[http://munin-monitoring.org/ Munin]] available.<br />
<br />
Read more about installing and configuring [[OX_munin_scripts|Munin scripts for Open-Xchange]]<br />
<br />
<br />
== Upsell Plugin / Webmail Replacement ==<br />
<br />
If you want to use your OX based Webmail system to upsell premium functions like full groupware functionality or like push to mobile phones, it is strongly recommended to use the in-app sales process.<br />
<br />
Read more about [[Upsell]]<br />
<br />
<br />
<!-- <br />
== Mobile Autoconfiguration ==<br />
<br />
If you have the OXtender for Business Mobility installed, it is recommended also to install the autoconfiguration plugin, to allow your users to configure their iPhones and Windows Mobile devices directly from within the OX webfrontend. All you need is to adapt the SMS interface to send autoprovisioning SMS. <br />
<br />
Read more about WO_IST_DAS_DOKUMENTIERT<br />
--><br />
<br />
== Branding ==<br />
<br />
If you want OX to look more like your own Corporate Identity, including your logo, product name and maybe your colors, this can be easily achieved by changing the logos and stylesheets.<br />
<br />
Read more about: [[Gui_Theming_Description]]<br />
<br />
Read more about: [[Gui_Plugin_Development|Gui Branding Plugins]]<br />
<br />
<br />
== Backup ==<br />
<br />
It is recommended to run regular backups for your OX installation. This can be done with every backup solution for Linux.<br />
<br />
Read more about [[Open-Xchange_backup|Backup your Open-Xchange installation]]<br />
<br />
<br />
== Mobile GUI (pre Beta) ==<br />
<br />
This GUI is designed to run in the mobile browsers and brings basic Open-Xchange functionality to all available HTML 5 capable devices.<br />
<br />
Read more about [[OXMobileApp]]</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Template:OX_HE_Tutorial_Next&diff=7405Template:OX HE Tutorial Next2011-03-03T09:57:49Z<p>Holgi: /* Recommended Optional Next Steps */</p>
<hr />
<div>= Recommended Optional Next Steps =<br />
<br />
You will find plenty of additional documentation for customization of OX in our knowledge base [http://oxpedia.org]<br />
<br />
When the main setup is completed, we recommend to start with the following articles to enhance your system and to become more attractive for your users.<br />
<br />
<br />
== Automated Frontend Tests ==<br />
<br />
It is a good idea, to verify the functionality of your freshly set up and integrated system. Our QA department does that with tests, running automatically on the web frontend. We release this tests with every release and recommend you to use them to verify your environment with every update.<br />
<br />
Read more about [[Automated_GUI_Tests]]<br />
<br />
<br />
== Monitoring / Statistics ==<br />
<br />
It is recommended to implement at least a minimal monitoring/Statistics solution to get an overview of the systems health. If you have a support contract with Open-Xchange, it is very helpful, if the support can access the monitoring graphs. There are example scripts for a basic monitoring with [[http://munin-monitoring.org/ Munin]] available.<br />
<br />
Read more about installing and configuring [[OX_munin_scripts|Munin scripts for Open-Xchange]]<br />
<br />
<br />
== Upsell Plugin / Webmail Replacement ==<br />
<br />
If you want to use your OX based Webmail system to upsell premium functions like full groupware functionality or like push to mobile phones, it is strongly recommended to use the in-app sales process.<br />
<br />
Read more about [[Upsell]]<br />
<br />
<br />
<!-- <br />
== Mobile Autoconfiguration ==<br />
<br />
If you have the OXtender for Business Mobility installed, it is recommended also to install the autoconfiguration plugin, to allow your users to configure their iPhones and Windows Mobile devices directly from within the OX webfrontend. All you need is to adapt the SMS interface to send autoprovisioning SMS. <br />
<br />
Read more about WO_IST_DAS_DOKUMENTIERT<br />
--><br />
<br />
== Branding ==<br />
<br />
If you want OX to look more like your own Corporate Identity, including your logo, product name and maybe your colors, this can be easily achieved by changing the logos and stylesheets.<br />
<br />
Read more about: [[Gui_Theming_Description]]<br />
<br />
Read more about: [[Gui_Plugin_Development|Gui Branding Plugins]]<br />
<br />
<br />
== Backup ==<br />
<br />
It is recommended to run regular backups for your OX installation. This can be done with every backup solution for Linux.<br />
<br />
Read more about [[Open-Xchange_backup|Backup your Open-Xchange installation]]<br />
<br />
== Mobile GUI (pre Beta) ==<br />
<br />
This GUI is designed to run in the mobile browsers and brings basic Open-Xchange functionality to all available HTML 5 capable devices.<br />
<br />
Read more about [[OXMobileApp]]</div>Holgihttps://wiki.open-xchange.com/wiki/index.php?title=Template:OX_HE_Tutorial_Next&diff=7404Template:OX HE Tutorial Next2011-03-03T09:37:55Z<p>Holgi: /* Mobile Autoconfiguration */</p>
<hr />
<div>= Recommended Optional Next Steps =<br />
<br />
You will find plenty of additional documentation for customization of OX in our knowledge base [http://oxpedia.org]<br />
<br />
When the main setup is completed, we recommend to start with the following articles to enhance your system and to become more attractive for your users.<br />
<br />
<br />
== Automated Frontend Tests ==<br />
<br />
It is a good idea, to verify the functionality of your freshly set up and integrated system. Our QA department does that with tests, running automatically on the web frontend. We release this tests with every release and recommend you to use them to verify your environment with every update.<br />
<br />
Read more about [[Automated_GUI_Tests]]<br />
<br />
<br />
== Monitoring / Statistics ==<br />
<br />
It is recommended to implement at least a minimal monitoring/Statistics solution to get an overview of the systems health. If you have a support contract with Open-Xchange, it is very helpful, if the support can access the monitoring graphs. There are example scripts for a basic monitoring with [[http://munin-monitoring.org/ Munin]] available.<br />
<br />
Read more about installing and configuring [[OX_munin_scripts|Munin scripts for Open-Xchange]]<br />
<br />
<br />
== Upsell Plugin / Webmail Replacement ==<br />
<br />
If you want to use your OX based Webmail system to upsell premium functions like full groupware functionality or like push to mobile phones, it is strongly recommended to use the in-app sales process.<br />
<br />
Read more about [[Upsell]]<br />
<br />
<br />
<!-- <br />
== Mobile Autoconfiguration ==<br />
<br />
If you have the OXtender for Business Mobility installed, it is recommended also to install the autoconfiguration plugin, to allow your users to configure their iPhones and Windows Mobile devices directly from within the OX webfrontend. All you need is to adapt the SMS interface to send autoprovisioning SMS. <br />
<br />
Read more about WO_IST_DAS_DOKUMENTIERT<br />
--><br />
<br />
== Branding ==<br />
<br />
If you want OX to look more like your own Corporate Identity, including your logo, product name and maybe your colors, this can be easily achieved by changing the logos and stylesheets.<br />
<br />
Read more about: [[Gui_Theming_Description]]<br />
<br />
Read more about: [[Gui_Plugin_Development|Gui Branding Plugins]]<br />
<br />
<br />
== Backup ==<br />
<br />
It is recommended to run regular backups for your OX installation. This can be done with every backup solution for Linux.<br />
<br />
Read more about [[Open-Xchange_backup|Backup your Open-Xchange installation]]</div>Holgi