<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.open-xchange.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Markus.wagner</id>
	<title>Open-Xchange - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.open-xchange.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Markus.wagner"/>
	<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=Special:Contributions/Markus.wagner"/>
	<updated>2026-11-19T17:41:06Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.7</generator>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=AppSuite:OX_Guard&amp;diff=20927</id>
		<title>AppSuite:OX Guard</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=AppSuite:OX_Guard&amp;diff=20927"/>
		<updated>2015-11-26T09:46:48Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: /* Debian GNU/Linux 7.0 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= OX Guard =&lt;br /&gt;
&lt;br /&gt;
OX Guard is a fully integrated security add-on to OX App Suite that provides end users with a flexible email and file encryption solution. OX Guard is a highly scalable, multi server, feature rich solution that is so simple-to-use that end users will actually use it. With a single click a user can take control of their security and send secure emails and share encrypted files. This can be done from any device to both OX App Suite and non-OX App Suite users. &lt;br /&gt;
&lt;br /&gt;
OX Guard uses standard PGP encryption for the encryption of email and files. PGP has been around for a long time, yet has not really caught on with the masses. This is generally blamed on the confusion and complications of managing the keys, understanding trust, PGP format types, and lack of trusted central key repositories. Guard simplifies all of this, making PGP encryption as easy as a one click process, with no keys to keep track of, yet the options of advanced PGP management for those that know how.&lt;br /&gt;
&lt;br /&gt;
This article will guide you through the installation of Guard and describes the basic configuration and software requirements. As it is intended as a quick walk-through it assumes an existing installation of the operating system including a single server App Suite setup as well as average system administration skills. This guide will also show you how to setup a basic installation with none of the typically used distributed environment settings. The objective of this guide is:&lt;br /&gt;
&lt;br /&gt;
* To setup a single server installation&lt;br /&gt;
* To setup a single Guard instance on an existing Open-Xchange installation, no cluster&lt;br /&gt;
* To use the database service on the existing Open-Xchange installation for Guard, no replication&lt;br /&gt;
* To provide a basic configuration setup, no mailserver configuration&lt;br /&gt;
&lt;br /&gt;
== Key features ==&lt;br /&gt;
&lt;br /&gt;
* Simple security at the touch of a button&lt;br /&gt;
* Provides user based security - Separate from provider&lt;br /&gt;
* Supplementary security to Provider based security - Layered&lt;br /&gt;
* Powerful features yet simple to use and understand&lt;br /&gt;
* Security - Inside and outside of the OX environment&lt;br /&gt;
* Email and Drive integration&lt;br /&gt;
* Uses proven PGP security&lt;br /&gt;
&lt;br /&gt;
== Availability ==&lt;br /&gt;
&lt;br /&gt;
If an OX App Suite customer would like to evaluate OX Guard integration, the first step is to contact OX Sales. OX Sales will then work on the request and send prices and license/API (for the hosted infrastructure) key details to the customer.&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
Please review following URL for remaining requirements  &lt;br /&gt;
&lt;br /&gt;
Please review [[AppSuite:OX_System_Requirements#OX_Guard|OX Guard Requirements]] for a full list of requirements.&lt;br /&gt;
&lt;br /&gt;
Since OX Guard is a Microservice it can either be added to an existing Open-Xchange installation or it can be deployed on a dedicated environment without having any of the other Open-Xchange App Suite core services installed. OX App Suite v7.6.0 or later is required to operate this extension both in a single or multi server environments.&lt;br /&gt;
&lt;br /&gt;
Prerequisites:&lt;br /&gt;
* Open-Xchange REST API&lt;br /&gt;
* Grizzly HTTP connector (open-xchange-grizzly)&lt;br /&gt;
* A supported Java Virtual Machine (Java 7)&lt;br /&gt;
* An Open-Xchange App Suite installation v7.6.0 or later&lt;br /&gt;
* Please Note: To get access to the latest minor features and bug fixes, you need to have a valid license. The article [[AppSuite:UpdatingOXPackages|Updating OX-Packages]] explains how that can be done.&lt;br /&gt;
&lt;br /&gt;
== Important Notes ==&lt;br /&gt;
&lt;br /&gt;
=== Customization ===&lt;br /&gt;
&lt;br /&gt;
OX Guard version supports branding / theming using the configuration cascade, defining a templateID for a user or context.  Additional details will be provided in customization documentation. Check bottom of this page. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Mail Resolver ===&lt;br /&gt;
&lt;br /&gt;
READ THIS VERY CAREFULLY; BEFORE PROCEEDING WITH GUARD INSTALLATION!&lt;br /&gt;
&lt;br /&gt;
The Guard installation must be able to determine if an email recipient is a local OX user or if it should be a guest account.  The default MailResolver uses the context domain name to do this.  On many installations, domains may extend across multiple context and multiple database shards.  In these cases, the default MailResolver won&#039;t work.  In addition, if a custom authentication package is used, the Mail Resolver will likely not work.&lt;br /&gt;
&lt;br /&gt;
Be sure to test the mail resolver using&lt;br /&gt;
&lt;br /&gt;
 /opt/open-xchange/guard/sbin/guard test email@domain &lt;br /&gt;
&lt;br /&gt;
to see if the mail Resolver works.&lt;br /&gt;
&lt;br /&gt;
If the test does not work, you will likely need a custom Mail Resolver.  Please see [[AppSuite:GuardMailResolver| Mail Resolver page]]&lt;br /&gt;
&lt;br /&gt;
This resolver software &#039;&#039;depends heavily on your local deployment&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
= Download and Installation =&lt;br /&gt;
&lt;br /&gt;
=== General ===&lt;br /&gt;
The installation of the open-xchange-rest package which is required for Guard will eventually execute database update tasks if installed and activated. Please take this into account.&lt;br /&gt;
&lt;br /&gt;
There are several components to the Guard service.  They can be all installed on the same server as the OX backend, or on a separate server.&lt;br /&gt;
&lt;br /&gt;
The components required for the OX backend are: open-xchange-rest, open-xchange-guard-backend-plugin&lt;br /&gt;
&lt;br /&gt;
The components required for the OX frontend are: open-xchange-guard-ui open-xchange-guard-ui-static and optionally open-xchange-guard-help-en-us (or preferred language for help files)&lt;br /&gt;
&lt;br /&gt;
The components required for the Guard server (may be on same as the backend) open-xchange-guard&lt;br /&gt;
&lt;br /&gt;
=== Redhat Enterprise Linux 6 or CentOS 6 ===&lt;br /&gt;
&lt;br /&gt;
If not already done, add the following repositories to your Open-Xchange yum configuration:&lt;br /&gt;
&lt;br /&gt;
 {{for loop||call=YUMRepo|pv=reponame|pc1n=path|pc1v=products|pc2n=rhelname|pc2v=RHEL6|guard/stable/guard}}&lt;br /&gt;
&lt;br /&gt;
and run&lt;br /&gt;
&lt;br /&gt;
 $ yum update&lt;br /&gt;
 $ yum install open-xchange-rest open-xchange-guard open-xchange-guard-ui open-xchange-guard-ui-static open-xchange-guard-backend-plugin&lt;br /&gt;
&lt;br /&gt;
=== Redhat Enterprise Linux 7 or CentOS 7 ===&lt;br /&gt;
&lt;br /&gt;
If not already done, add the following repositories to your Open-Xchange yum configuration:&lt;br /&gt;
&lt;br /&gt;
 {{for loop||call=YUMRepo|pv=reponame|pc1n=path|pc1v=products|pc2n=rhelname|pc2v=RHEL7|guard/stable/guard}}&lt;br /&gt;
&lt;br /&gt;
and run&lt;br /&gt;
&lt;br /&gt;
 $ yum update&lt;br /&gt;
 $ yum install open-xchange-rest open-xchange-guard open-xchange-guard-ui open-xchange-guard-ui-static open-xchange-guard-backend-plugin&lt;br /&gt;
&lt;br /&gt;
=== Debian GNU/Linux 7.0 ===&lt;br /&gt;
&lt;br /&gt;
If not already done, add the following repositories to your Open-Xchange apt configuration:&lt;br /&gt;
&lt;br /&gt;
 {{for loop||call=APTRepo|pv=reponame|pc1n=path|pc1v=products|pc2n=debianname|pc2v=DebianWheezy|guard/stable/guard}}&lt;br /&gt;
&lt;br /&gt;
and run&lt;br /&gt;
&lt;br /&gt;
 $ apt-get update&lt;br /&gt;
 $ apt-get install open-xchange-rest open-xchange-guard open-xchange-guard-ui open-xchange-guard-ui-static open-xchange-guard-backend-plugin&lt;br /&gt;
&lt;br /&gt;
=== Debian GNU/Linux 8.0 ===&lt;br /&gt;
&lt;br /&gt;
If not already done, add the following repositories to your Open-Xchange apt configuration:&lt;br /&gt;
&lt;br /&gt;
 {{for loop||call=APTRepo|pv=reponame|pc1n=path|pc1v=products|pc2n=debianname|pc2v=DebianJessie|guard/stable/guard}}&lt;br /&gt;
&lt;br /&gt;
and run&lt;br /&gt;
&lt;br /&gt;
 $ apt-get update&lt;br /&gt;
 $ apt-get install open-xchange-rest open-xchange-guard open-xchange-guard-ui open-xchange-guard-ui-static open-xchange-guard-backend-plugin&lt;br /&gt;
&lt;br /&gt;
=== SUSE Linux Enterprise Server 11 ===&lt;br /&gt;
&lt;br /&gt;
Add the package repository using zypper if not already present:&lt;br /&gt;
&lt;br /&gt;
 {{for loop||call=SUSERepo|pv=reponame|pc1n=path|pc1v=products|pc2n=susename|pc2v=SLES11|guard/stable/guard}}&lt;br /&gt;
&lt;br /&gt;
and run&lt;br /&gt;
&lt;br /&gt;
 $ zypper ref&lt;br /&gt;
 $ zypper in open-xchange-rest open-xchange-guard open-xchange-guard-ui open-xchange-guard-ui-static open-xchange-guard-backend-plugin&lt;br /&gt;
&lt;br /&gt;
Guard requires Java 1.7, which will be installed through the Guard packages, still SUSE Linux Enterprise Server 11 will not use Java 1.7 by default. Therefor we have to set Java 1.7 as the default instead of Java 1.6:&lt;br /&gt;
&lt;br /&gt;
 $ update-alternatives --config java&lt;br /&gt;
&lt;br /&gt;
Now select the Java 1.7 JRE, example:&lt;br /&gt;
&lt;br /&gt;
 There are 2 alternatives which provide `java&#039;.&lt;br /&gt;
&lt;br /&gt;
   Selection    Alternative&lt;br /&gt;
 -----------------------------------------------&lt;br /&gt;
 *         1    /usr/lib64/jvm/jre-1.6.0-ibm/bin/java&lt;br /&gt;
  +        2    /usr/lib64/jvm/jre-1.7.0-ibm/bin/java&lt;br /&gt;
 &lt;br /&gt;
 Press enter to keep the default[*], or type selection number: 2&lt;br /&gt;
 Using &#039;/usr/lib64/jvm/jre-1.7.0-ibm/bin/java&#039; to provide &#039;java&#039;.&lt;br /&gt;
&lt;br /&gt;
=== SUSE Linux Enterprise Server 12 ===&lt;br /&gt;
&lt;br /&gt;
Add the package repository using zypper if not already present:&lt;br /&gt;
&lt;br /&gt;
 {{for loop||call=SUSERepo|pv=reponame|pc1n=path|pc1v=products|pc2n=susename|pc2v=SLE_12|guard/stable/guard}}&lt;br /&gt;
&lt;br /&gt;
and run&lt;br /&gt;
&lt;br /&gt;
 $ zypper ref&lt;br /&gt;
 $ zypper in open-xchange-rest open-xchange-guard open-xchange-guard-ui open-xchange-guard-ui-static&lt;br /&gt;
&lt;br /&gt;
Guard requires Java 1.7, which will be installed through the Guard packages, still SUSE Linux Enterprise Server 11 will not use Java 1.7 by default. Therefor we have to set Java 1.7 as the default instead of Java 1.6:&lt;br /&gt;
&lt;br /&gt;
 $ update-alternatives --config java&lt;br /&gt;
&lt;br /&gt;
Now select the Java 1.7 JRE, example:&lt;br /&gt;
&lt;br /&gt;
 There are 2 alternatives which provide `java&#039;.&lt;br /&gt;
&lt;br /&gt;
   Selection    Alternative&lt;br /&gt;
 -----------------------------------------------&lt;br /&gt;
 *         1    /usr/lib64/jvm/jre-1.6.0-ibm/bin/java&lt;br /&gt;
  +        2    /usr/lib64/jvm/jre-1.7.0-ibm/bin/java&lt;br /&gt;
 &lt;br /&gt;
 Press enter to keep the default[*], or type selection number: 2&lt;br /&gt;
 Using &#039;/usr/lib64/jvm/jre-1.7.0-ibm/bin/java&#039; to provide &#039;java&#039;.&lt;br /&gt;
&lt;br /&gt;
=== Univention Corporate Server ===&lt;br /&gt;
&lt;br /&gt;
If you have purchased the OX App Suite for UCS, the OX Guard is part of the offering. OX Guard is available in the Univention App Center. Please check the UMC module App Center for the installation of the OX Guard at your already available environment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please note:&#039;&#039;&#039; By default, OX Guard generates the link to the secure content for external recipients on the basis of the local fully qualified domain name (FQDN). If the local FQDN is not reachable from the internet, it has to be specified manually. This can be done by setting a UCR variable, e.g. via the UMC module &amp;quot;Univention Configuration Registry&amp;quot;. The variable has to contain the external FQDN of the OX Guard system:&lt;br /&gt;
&lt;br /&gt;
 oxguard/cfg/guard.properties/com.openexchange.guard.externalEmailURL=HOSTNAME.DOMAINNAME&lt;br /&gt;
&lt;br /&gt;
= Update OX Guard =&lt;br /&gt;
&lt;br /&gt;
Before upgrading Guard to version 2.0.0 you need to install the package &amp;lt;code&amp;gt;open-xchange-guard-backend&amp;lt;/code&amp;gt; on all groupware nodes used by Guard throught the REST api. In other words, every groupware node have &amp;lt;code&amp;gt;open-xchange-rest&amp;lt;/code&amp;gt; installed, now needs to have &amp;lt;code&amp;gt;open-xchange-guard-backend&amp;lt;/code&amp;gt; installed.&lt;br /&gt;
&lt;br /&gt;
=== Redhat Enterprise Linux 6 or CentOS 6 ===&lt;br /&gt;
&lt;br /&gt;
If not already done, add the following repositories to your Open-Xchange yum configuration:&lt;br /&gt;
&lt;br /&gt;
 {{for loop||call=YUMRepo|pv=reponame|pc1n=path|pc1v=products|pc2n=rhelname|pc2v=RHEL6|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|guard/stable/guard/updates}}&lt;br /&gt;
&lt;br /&gt;
and run&lt;br /&gt;
&lt;br /&gt;
 $ yum update&lt;br /&gt;
 $ yum upgrade&lt;br /&gt;
&lt;br /&gt;
After the new packages are installed, the guard process needs a restart:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;pre&amp;gt;$ /etc/init.d/open-xchange-guard restart&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Redhat Enterprise Linux 7 or CentOS 7 ===&lt;br /&gt;
&lt;br /&gt;
If not already done, add the following repositories to your Open-Xchange yum configuration:&lt;br /&gt;
&lt;br /&gt;
 {{for loop||call=YUMRepo|pv=reponame|pc1n=path|pc1v=products|pc2n=rhelname|pc2v=RHEL7|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|guard/stable/guard/updates}}&lt;br /&gt;
&lt;br /&gt;
and run&lt;br /&gt;
&lt;br /&gt;
 $ yum update&lt;br /&gt;
 $ yum upgrade&lt;br /&gt;
&lt;br /&gt;
After the new packages are installed, the guard process needs a restart:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;pre&amp;gt;$ /etc/init.d/open-xchange-guard restart&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Debian GNU/Linux 7.0 ===&lt;br /&gt;
&lt;br /&gt;
If not already done, add the following repositories to your Open-Xchange apt configuration:&lt;br /&gt;
&lt;br /&gt;
 {{for loop||call=APTRepo|pv=reponame|pc1n=path|pc1v=products|pc2n=debianname|pc2v=DebianWheezy|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|guard/stable/guard/updates}}&lt;br /&gt;
&lt;br /&gt;
Then run&lt;br /&gt;
&lt;br /&gt;
 $ apt-get update&lt;br /&gt;
 $ apt-get dist-upgrade&lt;br /&gt;
&lt;br /&gt;
If you want to see, what apt-get is going to do without actually doing it, you can run:&lt;br /&gt;
&lt;br /&gt;
 $ apt-get dist-upgrade -s&lt;br /&gt;
&lt;br /&gt;
After the new packages are installed, the guard process needs a restart:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;pre&amp;gt;$ /etc/init.d/open-xchange-guard restart&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Debian GNU/Linux 8.0 ===&lt;br /&gt;
&lt;br /&gt;
If not already done, add the following repositories to your Open-Xchange apt configuration:&lt;br /&gt;
&lt;br /&gt;
 {{for loop||call=APTRepo|pv=reponame|pc1n=path|pc1v=products|pc2n=debianname|pc2v=DebianJessie|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|guard/stable/guard/updates}}&lt;br /&gt;
&lt;br /&gt;
Then run&lt;br /&gt;
&lt;br /&gt;
 $ apt-get update&lt;br /&gt;
 $ apt-get dist-upgrade&lt;br /&gt;
&lt;br /&gt;
If you want to see, what apt-get is going to do without actually doing it, you can run:&lt;br /&gt;
&lt;br /&gt;
 $ apt-get dist-upgrade -s&lt;br /&gt;
&lt;br /&gt;
After the new packages are installed, the guard process needs a restart:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;pre&amp;gt;$ /etc/init.d/open-xchange-guard restart&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== SUSE Linux Enterprise Server 11 ===&lt;br /&gt;
&lt;br /&gt;
Add the package repository using zypper if not already present:&lt;br /&gt;
&lt;br /&gt;
 {{for loop||call=SUSERepo|pv=reponame|pc1n=path|pc1v=products|pc2n=susename|pc2v=SLES11|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|guard/stable/guard/updates}}&lt;br /&gt;
&lt;br /&gt;
and run&lt;br /&gt;
&lt;br /&gt;
 $ zypper dup -r guard-stable-guard-backend-updates&lt;br /&gt;
 $ zypper dup -r guard-stable-guard-ui-updates&lt;br /&gt;
&lt;br /&gt;
You might need to run&lt;br /&gt;
&lt;br /&gt;
 $ zypper ref&lt;br /&gt;
&lt;br /&gt;
to update the repository metadata before running &#039;&#039;zypper up&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
After the new packages are installed, the guard process needs a restart:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;pre&amp;gt;$ open-xchange-guard restart&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== SUSE Linux Enterprise Server 12 ===&lt;br /&gt;
&lt;br /&gt;
Add the package repository using zypper if not already present:&lt;br /&gt;
&lt;br /&gt;
 {{for loop||call=SUSERepo|pv=reponame|pc1n=path|pc1v=products|pc2n=susename|pc2v=SLE_12|pc3n=ldbaccount|pc3v=LDBUSER:LDBPASSWORD|guard/stable/guard/updates}}&lt;br /&gt;
&lt;br /&gt;
and run&lt;br /&gt;
&lt;br /&gt;
 $ zypper dup -r guard-stable-guard-backend-updates&lt;br /&gt;
 $ zypper dup -r guard-stable-guard-ui-updates&lt;br /&gt;
&lt;br /&gt;
You might need to run&lt;br /&gt;
&lt;br /&gt;
 $ zypper ref&lt;br /&gt;
&lt;br /&gt;
to update the repository metadata before running &#039;&#039;zypper up&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
After the new packages are installed, the guard process needs a restart:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;pre&amp;gt;$ open-xchange-guard restart&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Univention Corporate Server ===&lt;br /&gt;
&lt;br /&gt;
If you have purchased the OX App Suite for UCS, the OX Guard is part of the offering. OX Guard is available in the Univention App Center. Please check the UMC module App Center for the update of the OX Guard.&lt;br /&gt;
&lt;br /&gt;
=== Update OX Guard v1.2 to OX Guard v2.0.0 ===&lt;br /&gt;
&lt;br /&gt;
IMPORTANT: &#039;&#039;&#039;&#039;&#039;If you did not run GUARD 1.2 already, you DO NOT NEED to execute the &amp;quot;upgradePGP&amp;quot; command!&#039;&#039;&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you have an existing Guard v1.2 database, and are upgrading to v2.0, additional PGP key table need to be created and populated.  Once the Guard package has been updated, type&lt;br /&gt;
&lt;br /&gt;
 /opt/open-xchange/guard/sbin/guard upgradePGP&lt;br /&gt;
&lt;br /&gt;
This process will alter the needed database tables and populate the needed lookup tables.  Guard 1.2 can continue to run in the background.  Once complete, Guard 2.0 can be started.&lt;br /&gt;
&lt;br /&gt;
= Configuration =&lt;br /&gt;
&lt;br /&gt;
The following gives an overview of the most important settings to enable Guard for users on the Open-Xchange installation. Some of those settings have to be modified in order to establish the database and REST API access from the Guard service. All settings relating to the Guard backend component are located in the configuration file guard.properties located in /opt/open-xchange/guard/etc. The default configuration should be sufficient for a basic &amp;quot;up-and-running&amp;quot; setup (with the exception of defining the database username and password). Please refer to the inline documentation of the configuration file for more advanced options.  Additional information can be found here [[AppSuite:GuardConfiguration|Guard Configuration]]&lt;br /&gt;
&lt;br /&gt;
 $ vim /opt/open-xchange/guard/etc/guard.properties&lt;br /&gt;
&lt;br /&gt;
Open-Xchange config_db host - Guard will establish a connection to the config_db&lt;br /&gt;
&lt;br /&gt;
 com.openexchange.guard.configdbHostname=localhost&lt;br /&gt;
&lt;br /&gt;
Guard database for storing Guard user information, main lookup tables&lt;br /&gt;
&lt;br /&gt;
 com.openexchange.guard.oxguardDatabaseHostname=localhost&lt;br /&gt;
&lt;br /&gt;
Guard database that stores keys for guest users.  May be the same as above.  New guest shards will be created on this database as needed.  If not supplied, will use the oxguardDatabaseHostname&lt;br /&gt;
&lt;br /&gt;
 com.openexchange.guard.oxguardShardDatabase=localhost&lt;br /&gt;
&lt;br /&gt;
Username and Password for the databases above&lt;br /&gt;
&lt;br /&gt;
 com.openexchange.guard.databaseUsername=openexchange&lt;br /&gt;
 com.openexchange.guard.databasePassword=db_password&lt;br /&gt;
&lt;br /&gt;
Open-Xchange REST API host&lt;br /&gt;
&lt;br /&gt;
 com.openexchange.guard.restApiHostname=localhost&lt;br /&gt;
&lt;br /&gt;
Open-Xchange REST API username and password (need to be defined in the OX backend in the &amp;quot;Configure services&amp;quot; below)&lt;br /&gt;
&lt;br /&gt;
 com.openexchange.guard.restApiUsername=apiusername&lt;br /&gt;
 com.openexchange.guard.restApiPassword=apipassword&lt;br /&gt;
&lt;br /&gt;
External URL for this Open-Xchange installation. This setting will be used to generate the link to the secure content for external recipients&lt;br /&gt;
&lt;br /&gt;
 com.openexchange.guard.externalEmailURL=URL_TO_OX&lt;br /&gt;
&lt;br /&gt;
== Configure services ==&lt;br /&gt;
&lt;br /&gt;
=== Apache ===&lt;br /&gt;
&lt;br /&gt;
Configure the mod_proxy_http module by adding the Guard API.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Redhat Enterprise Linux 6 or CentOS 6&#039;&#039;&#039;&lt;br /&gt;
 $ vim /etc/httpd/conf.d/proxy_http.conf&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Debian GNU/Linux 7.0 and SUSE Linux Enterprise Server 11&#039;&#039;&#039;&lt;br /&gt;
 $ vim /etc/apache2/conf.d/proxy_http.conf&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;Proxy balancer://oxguard&amp;gt;&lt;br /&gt;
        Order deny,allow&lt;br /&gt;
        Allow from all&amp;lt;br&amp;gt;&lt;br /&gt;
        BalancerMember http://localhost:8080/oxguard timeout=1800 smax=0 ttl=60 retry=60 loadfactor=100 route=OX1&lt;br /&gt;
        ProxySet stickysession=JSESSIONID|jsessionid scolonpathdelim=ON&lt;br /&gt;
        SetEnv proxy-initial-not-pooled&lt;br /&gt;
        SetEnv proxy-sendchunked&lt;br /&gt;
 &amp;lt;/Proxy&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ProxyPass /appsuite/api/oxguard balancer://oxguard&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please Note:&#039;&#039;&#039; The Guard API settings must be inserted before the existing “&amp;lt;Proxy /appsuite/api&amp;gt;” parameter.&lt;br /&gt;
&lt;br /&gt;
After the configuration is done, restart the Apache webserver&lt;br /&gt;
&lt;br /&gt;
 $ apachectl restart&lt;br /&gt;
&lt;br /&gt;
=== Open-Xchange ===&lt;br /&gt;
&lt;br /&gt;
Starting in Guard 2.0, there is an administrative component to the Open-Xchange backend that notifies Guard when a user or context is deleted.  Install the package open-xchange-guard-backend-plugin on all OX backend servers.  On a debian install, this command would be:&lt;br /&gt;
&lt;br /&gt;
 apt-get install open-xchange-guard-backend-plugin&lt;br /&gt;
&lt;br /&gt;
There is also a configuration file for the OX backend regarding some general Guard settings.  Please remove comments in front of the following settings to the configuration file guard.properties on the Open-Xchange backend servers:&lt;br /&gt;
&lt;br /&gt;
 $ vim /opt/open-xchange/etc/guard.properties&lt;br /&gt;
&lt;br /&gt;
 # OX GUard general permission, required to activate Guard in the AppSuite UI.&lt;br /&gt;
 com.openexchange.capability.guard=true&lt;br /&gt;
 &lt;br /&gt;
 # Default theme template id for all users that have no custom template id configured.&lt;br /&gt;
 com.openexchange.guard.templateID=0&lt;br /&gt;
&lt;br /&gt;
Configure the API username and password that you assigned to Guard in the server.properties file&lt;br /&gt;
&lt;br /&gt;
 $ vim /opt/open-xchange/etc/server.properties&lt;br /&gt;
&lt;br /&gt;
 # Specify the user name used for HTTP basic auth by internal REST servlet&lt;br /&gt;
 com.openexchange.rest.services.basic-auth.login=apiusername&lt;br /&gt;
 &lt;br /&gt;
 # Specify the password used for HTTP basic auth by internal REST servlet&lt;br /&gt;
 com.openexchange.rest.services.basic-auth.password=apipassword&lt;br /&gt;
&lt;br /&gt;
Finally, the OX backend needs to know where the Guard server is located.  This is used to notify the Guard server of changes in users, and to send emails marked for signature.  The URL for the Guard server should include the url suffix /guardadmin .  In the event of a cluster setup, any Guard server can be referenced here, as it is not session specific, though ideally would have a HTTP load balancer/failover URL&lt;br /&gt;
&lt;br /&gt;
 $ vim /opt/open-xchange/etc/guard.properties&lt;br /&gt;
&lt;br /&gt;
 # Specifies the URI to the OX Guard end-point; e.g. http://guard.host.invalid:8081/guardadmin&lt;br /&gt;
 # Default is empty&lt;br /&gt;
 com.openexchange.guard.endpoint=http://guardserver:8080/guardadmin&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Restart the OX backend&lt;br /&gt;
&lt;br /&gt;
 $ /etc/init.d/open-xchange restart&lt;br /&gt;
&lt;br /&gt;
=== SELinux ===&lt;br /&gt;
&lt;br /&gt;
Running SELinux prohibits your local Open-Xchange backend service to connect to localhost:8080, which is where the Guard backend service listens to. In order to allow localhost connections to 8080 execute the following:&lt;br /&gt;
&lt;br /&gt;
 $ setsebool -P httpd_can_network_connect 1&lt;br /&gt;
&lt;br /&gt;
== Initiating the Guard database and key store ==&lt;br /&gt;
&lt;br /&gt;
Once the Guard configuration (database and backend configuration) and the service configuration has been applied, the Guard administration script needs to be executed in order to create the Guard databases. The administration script also takes care of the creation of the master keys and the master password file in /opt/open-xchange/guard. The initiation only needs to be done once for a multi server setup, for details please see “Optional / Clustering”.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please Note:&#039;&#039;&#039; If you run a cluster of OX / Guard nodes, only execute this command on ONE node. Not on all nodes!  See [[AppSuite:GuardCluster | Ox Guard Clustering]] for details.&lt;br /&gt;
&lt;br /&gt;
 /opt/open-xchange/guard/sbin/guard init&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please Note:&#039;&#039;&#039; It is important to understand that the master password file located at /opt/open-xchange/guard/oxguardpass is required to reset user passwords, without them the administrator will not be able to reset user passwords anymore in the future. The file contains the passwords used to encrypt the master database key, as well as passwords used to encrypt protected data in the users table.  It must be the same on all Guard servers.&lt;br /&gt;
&lt;br /&gt;
== Test Setup ==&lt;br /&gt;
&lt;br /&gt;
Not required, but it is a good idea to test the Guard setup before starting the initialization.  The test function will verify that Guard has a good connection to the OX backend, and that it can resolve email addresses to users.&lt;br /&gt;
&lt;br /&gt;
To test, use an email address that exists on the OX backend (john@example.com for this example)&lt;br /&gt;
&lt;br /&gt;
 /opt/open-xchange/guard/sbin/guard test john@example.com&lt;br /&gt;
&lt;br /&gt;
Guard should return information from the OX backend regarding the user associated with john@example.com.  Problems resolving information for the user should be resolved before using Guard.  Check Rest API passwords and settings if errors returned.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Start Guard ==&lt;br /&gt;
&lt;br /&gt;
The services have been configured and the database has been initiated, it&#039;s time to start Guard&lt;br /&gt;
&lt;br /&gt;
 $ /etc/init.d/open-xchange-guard start&lt;br /&gt;
&lt;br /&gt;
== Enabling Guard for Users ==&lt;br /&gt;
&lt;br /&gt;
Guard provides two capabilities for users in the environment as well as a basic &amp;quot;core&amp;quot; level:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Guard:&#039;&#039;&#039; com.openexchange.capability.guard&lt;br /&gt;
* &#039;&#039;&#039;Guard Mail:&#039;&#039;&#039; com.openexchange.capability.guard-mail&lt;br /&gt;
* &#039;&#039;&#039;Guard Drive:&#039;&#039;&#039; com.openexchange.capability.guard-drive&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;core&amp;quot; Guard enabled a basic read functionality for Guard encrypted emails.  We recommend enabling this for all users, as this allows all recipients to read Guard emails sent to them.  Great opportunity for upsell.  Recipients with only Guard enabled can then do a secure reply to the sender, but they can&#039;t start a new email or add recipients.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Guard Mail&amp;quot; and &amp;quot;Guard Drive&amp;quot; are additional options for users.  &amp;quot;Guard Mail&amp;quot; allows users the full functionality of Guard emails.  &amp;quot;Guard Drive&amp;quot; allows for encryption and decryption of drive files.&lt;br /&gt;
&lt;br /&gt;
Each of those two Guard components is enabled for all users that have the according capability configured. Please note that users need to have the Drive permission set to use Guard Drive. So the users that have Guard Drive enabled must be a subset of those users with OX Drive permission. Since v7.6.0 we enforce this via the default configuration. Those capabilities can be activated for specific user by using the Open-Xchange provisioning scripts:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Guard Mail:&#039;&#039;&#039;&lt;br /&gt;
 $ /opt/open-xchange/sbin/changeuser -c 1 -A oxadmin -P admin_password -u testuser --config/com.openexchange.capability.guard-mail=true&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Guard Drive:&#039;&#039;&#039;&lt;br /&gt;
 $ /opt/open-xchange/sbin/changeuser -c 1 -A oxadmin -P admin_password -u testuser --config/com.openexchange.capability.guard-drive=true&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please Note:&#039;&#039;&#039; Guard Drive requires Guard Mail to be configured for the user as well.  In addition, these capabilities may be configured globally by editing the guard.properties file on the OX bakend&lt;br /&gt;
&lt;br /&gt;
== Optional ==&lt;br /&gt;
&lt;br /&gt;
=== SSL Configuration ===&lt;br /&gt;
&lt;br /&gt;
Per default the connection between the Guard backend and the configured Open-Xchange REST API host is unencrypted. Even though that Guard will never transmit unencrypted emails to or from the REST API you can optionally encrypt the whole communication between those two components by using SSL. To enforce Guard to use SSL in the communication between those two components enable the follwing configuration in Guard configuration file. &lt;br /&gt;
&lt;br /&gt;
  $ vim /opt/open-xchange/guard/etc/guard.properties&lt;br /&gt;
&lt;br /&gt;
  com.openexchange.guard.backend_ssl=true&lt;br /&gt;
&lt;br /&gt;
The Guard backend is most commonly placed behind a load balancer (APACHE or other) and defaults to HTTP for incoming and outgoing traffic, using the load balancer to do SSL with the users.  If you want Guard to use SSL for all communications, you need to set up the SSL key to use.&lt;br /&gt;
&lt;br /&gt;
Please note that you have to provide access to the certificates.&lt;br /&gt;
&lt;br /&gt;
 com.openexchange.guard.useSSL: true&lt;br /&gt;
 com.openexchange.guard.SSLPort: 8443&lt;br /&gt;
 com.openexchange.guard.SSLKeyStore: //keystore location//&lt;br /&gt;
 com.openexchange.guard.SSLKeyName: //alias name here//&lt;br /&gt;
 com.openexchange.guard.SSLKeyPass: //ssl password//&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please Note:&#039;&#039;&#039; Enabling SSL might decrease performance and/or create more system load due to additional encoding of the HTTP streams.&lt;br /&gt;
&lt;br /&gt;
For details on SSL installation and configuration, please see [[AppSuite:GuardSSL|OX Guard SSL Installation]]&lt;br /&gt;
&lt;br /&gt;
== Recipient key detection ==&lt;br /&gt;
&lt;br /&gt;
=== Local ===&lt;br /&gt;
&lt;br /&gt;
Guard needs to determine if an email recipients email address is an internal or external (non-ox) user.  &lt;br /&gt;
&lt;br /&gt;
To detect if the recipient is an account on the same OX Guard system there is a mechanism needed to map a recipient mail address to the correct local OX context. The default implementation delivered in the product achieves that by looking up the mail domain (@example.com) within the list of context mappings. That is at least not possible in case of ISPs where different users/contexts use the same mail domain. In case your OX system does not use mail domains in context mappings it is required to deploy an OX OSGi bundle implementing the com.openexchange.mailmapping.MailResolver class or by interfacing Guard with your mail resolver system.&lt;br /&gt;
Please see [[Appsuite:GuardMailResolver|OX Guard Mail Resolver]] for details&lt;br /&gt;
&lt;br /&gt;
=== External ===&lt;br /&gt;
&lt;br /&gt;
Starting with Guard 2.0, Guard will use public PGP Key servers if configured to find PGP Public keys.  In addition, Guard will also look up SRV records for PGP Key servers for a recipients domain.  This follows the standards [http://tools.ietf.org/html/draft-shaw-openpgp-hkp-00#page-9 OpenPGP Draft].&lt;br /&gt;
&lt;br /&gt;
External PGP servers to use can be configured in the guard.properties file on the Guard servers.&lt;br /&gt;
&lt;br /&gt;
 com.openexchange.guard.publicPGPDirectory = hkp://keys.gnupg.net:11371, hkp://pgp.mit.edu:11371&lt;br /&gt;
&lt;br /&gt;
If you would like this Guard installation discoverable by other Guard servers, then create a SRV record for each domain (&amp;quot;example.com&amp;quot; in this illustration)&lt;br /&gt;
 &lt;br /&gt;
 _hkp._tcp.open-xchange.com. 28800 IN    SRV     10 1 80 appsuite.example.com.&lt;br /&gt;
&lt;br /&gt;
You will also need to make additional entries in the apache proxy_http.conf file.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;Proxy balancer://oxguardpgp&amp;gt;&lt;br /&gt;
        Order deny,allow&lt;br /&gt;
        Allow from all, add&lt;br /&gt;
        BalancerMember http://guardserver:8080/pgp timeout=1800 smax=0 ttl=60 retry=60 loadfactor=50 route=OX3&lt;br /&gt;
        ProxySet stickysession=JSESSIONID|jsessionid scolonpathdelim=ON&lt;br /&gt;
        SetEnv proxy-initial-not-pooled&lt;br /&gt;
        SetEnv proxy-sendchunked&lt;br /&gt;
   &amp;lt;/Proxy&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;Proxy /pks&amp;gt;&lt;br /&gt;
        ProxyPass balancer://oxguardpgp&lt;br /&gt;
 &amp;lt;/Proxy&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please Note&#039;&#039;&#039; PGP Public key servers by default append use the url server/pks when the record is obtained from a SRV record.  The proxy above routes anything with the apache domain/pks to the Oxguard PGP server&lt;br /&gt;
&lt;br /&gt;
== Clustering ==&lt;br /&gt;
&lt;br /&gt;
You can run multiple OX Guard servers in your environment to ensure high availability or enhance scalability. OX Guard integrates seamlessly into the existing Open-Xchange infrastructure by using the existing interface standards and is therefor transparent to the environment. A couple of things have to be prepared in order to loosely couple OX Guard servers with Open-Xchange servers in a cluster.&lt;br /&gt;
&lt;br /&gt;
=== MySQL ===&lt;br /&gt;
&lt;br /&gt;
The MySQL servers need to be configured in order to allow access to the configdb of Open-Xchange. To do so you need to set the following configuration in the MySQL my.cnf:&lt;br /&gt;
&lt;br /&gt;
 bind = 0.0.0.0&lt;br /&gt;
&lt;br /&gt;
This allows the Guard backend to bind to the MySQL host which is configured in the guard.properties file with com.openexchange.guard.configdbHostname. After the bind for the MySQL instance is configured and the OX Guard backend would be able to connect to the configured host, you have to grant access for the OX Guard service on the MySQL instance to manage the databases. Do so by connecting to the MySQL server via the mysql client. Authenticate if necessary and execute the following, please note that you have to modify the hostname / IP address of the client who should be able to connect to this database, it should include all possible OX Guard servers:&lt;br /&gt;
&lt;br /&gt;
 GRANT ALL PRIVILEGES ON *.* TO &#039;openexchange&#039;@&#039;oxguard.example.com&#039; IDENTIFIED BY ‘secret’;&lt;br /&gt;
&lt;br /&gt;
=== Apache ===&lt;br /&gt;
&lt;br /&gt;
OX Guard uses the Open-Xchange REST API to store and fetch data from the Open-Xchange databases. The REST API is a servlet running in the Grizzly container. By default it is not exposed as a servlet through Apache and is only accessibly via port 8009. In order to use Apache&#039;s load balancing via mod_proxy we need to add a servlet called &amp;quot;preliminary&amp;quot; to proxy_http.conf, example based on a clustered mod_proxy configuration:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;Location /preliminary&amp;gt;&lt;br /&gt;
      Order Deny,Allow&lt;br /&gt;
      Deny from all&lt;br /&gt;
      # Only allow access from Guard servers within the network. Do not expose this&lt;br /&gt;
      # location outside of your network. In case you use a load balancing service in front&lt;br /&gt;
      # of your Apache infrastructure you should make sure that access to /preliminary will&lt;br /&gt;
      # be blocked from the internet / outside clients. Examples:&lt;br /&gt;
      # Allow from 192.168.0.1&lt;br /&gt;
      # Allow from 192.168.1.1 192.168.1.2&lt;br /&gt;
      # Allow from 192.168.0.&lt;br /&gt;
      ProxyPass /preliminary balancer://oxcluster/preliminary&lt;br /&gt;
 &amp;lt;/Location&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure that the balancer is properly configured in the mod_proxy configuration. Examples on how to do so can be found in our clustering configuration for Open-Xchange AppSuite. Like explained in the example above, please make sure that this location is only available in your internal network, there is no need to expose /preliminary to the public, it is only used by Guard servers to connect to the OX backend. If you have a load balancer in front of the Apache cluster you should consider blocking access to /preliminary from WAN to restrict access to the servlet to internal network services only.&lt;br /&gt;
&lt;br /&gt;
Now add the OX Guard BalancerMembers to the oxguard balancer configuration (also in proxy_http.conf) to address all your OX Guard nodes in the cluster in this balancer configuration. The configuration has to be applied to all Apache nodes within the cluster.&lt;br /&gt;
&lt;br /&gt;
If the Apache server is a dedicated server / instance you also have to install the OX Guard UI-Static package on all Apache nodes in the cluster in order to provide static files like images or CSS to the OX Guard client. Example for Debian (the OX Guard repository has to be configured in the package management prior):&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install open-xchange-guard-ui-static&lt;br /&gt;
&lt;br /&gt;
=== Open-Xchange ===&lt;br /&gt;
&lt;br /&gt;
Disable the Open-Xchange IPCheck for session verification. This is required because OX Guard will use the users session cookie to connect to the Open-Xchange REST API, but as a different IP address than the OX Guard server has been used during authentication the request would fail if you don&#039;t disable the IPCheck:&lt;br /&gt;
&lt;br /&gt;
 $ vim /opt/open-xchange/etc/server.properties&lt;br /&gt;
&lt;br /&gt;
and set:&lt;br /&gt;
&lt;br /&gt;
 com.openexchange.IPCheck=false&lt;br /&gt;
&lt;br /&gt;
The OX Guard UI package has to be installed on all Open-Xchange backend nodes as well, example for Debian (the OX Guard repository has to be configured in the package management prior):&lt;br /&gt;
&lt;br /&gt;
 $ apt-get install open-xchange-guard-ui&lt;br /&gt;
&lt;br /&gt;
Restart the Open-Xchange service afterwards.&lt;br /&gt;
&lt;br /&gt;
=== OX Guard ===&lt;br /&gt;
&lt;br /&gt;
For details in clustering Guard servers, please see [[AppSuite:GuardCluster | OxGuard Clustering]] .  It is critical that all Guard servers have the same oxguardpass file.  Please see the clustering link for details.  Do not run ./guard init on more than one server.&lt;br /&gt;
&lt;br /&gt;
After all the services like MySQL, Apache and Open-Xchange have been configured you need to update the OX Guard backend configuration to point to the correct API endpoints. Set the REST API endpoint to an Apache server by setting the following value in /opt/open-xchange/guard/etc/guard.properties:&lt;br /&gt;
&lt;br /&gt;
 com.openexchange.guard.restApiHostname=apache.example.com&lt;br /&gt;
&lt;br /&gt;
Per default Guard will try to connect to port 8009 to this host, but as we configured the REST API to be proxies thorugh the serblet /preliminary on every Apache we now also need to change the target port for the REST API. You can do so by adding the following line into /opt/open-xchange/guard/etc/guard.properties:&lt;br /&gt;
&lt;br /&gt;
 com.openexchange.guard.oxBackendPort=80&lt;br /&gt;
&lt;br /&gt;
Please also change all settings in regards to MySQL like com.openexchange.guard.configdbHostname, com.openexchange.guard.oxguardDatabaseHostname, com.openexchange.guard.databaseUsername or com.openexchange.guard.databasePassword. Afterwards restart the OX Guard service and check the logfile if the OX Guard backend is able to connect to the configured REST API.&lt;br /&gt;
&lt;br /&gt;
== Multi Node ==&lt;br /&gt;
&lt;br /&gt;
If you have multiple OX and Guard installations, please see the following documentation [[AppSuite:OX_Guard_Modular|OX Guard Modular Setup]]&lt;br /&gt;
&lt;br /&gt;
= Support API =&lt;br /&gt;
&lt;br /&gt;
The OX Guard Support API enables administrative access to various functions for maintaining OX Guard from a client in a role as a support employee. A client has to do a BASIC AUTH authentication in order to access the API. Username and password can be configured in the guard.properties file using the following settings:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
    # Specify the username and password for accessing the Support API of Guard&lt;br /&gt;
    com.openexchange.guard.supportapiusername=&lt;br /&gt;
    com.openexchange.guard.supportapipassword=&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In contrast to the rest of the OX Guard requests, the OX Guard support API requests are accessible using: /guardsupport. This distinction allows more flexible configuration since the support API should not always be accessible from everywhere. But if you want to expose the Guard Support API using Apache a very basic Apache configuration could look like this:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Warning&#039;&#039;&#039; Exposing the support API to the internet could be huge security risk.  Only add to apache if you know what you are doing&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
   &amp;lt;Location /appsuite/api/guardsupport&amp;gt;                                                               &lt;br /&gt;
        ProxyPass http://localhost:8080/guardsupport                                                    &lt;br /&gt;
        #...&lt;br /&gt;
   &amp;lt;/Location&amp;gt;      &lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
it might also be preferable to add a new balancer directive for guardsupport&lt;br /&gt;
&amp;lt;code&amp;gt;&lt;br /&gt;
 &amp;lt;Location /appsuite/api/guardsupport&amp;gt;                                                               &lt;br /&gt;
        ProxyPass balancer://oxguardsupport                                                           &lt;br /&gt;
 &amp;lt;/Location&amp;gt; &lt;br /&gt;
 &amp;lt;Proxy balancer://oxguardsupport&amp;gt;                                                                &lt;br /&gt;
       #...&lt;br /&gt;
        BalancerMember http://localhost:8080/guardsupport #...&lt;br /&gt;
       #...&lt;br /&gt;
 &amp;lt;/Proxy&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Reset password ===&lt;br /&gt;
POST &amp;lt;code&amp;gt;/guardsupport/?action=reset_password&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Performs a password reset and sends a new random generated password to a specified email address by the user or a default address if the user did not specify an email address. The reset password function is currently not available for guest users.&lt;br /&gt;
&lt;br /&gt;
Since Guard 2.0&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
* &amp;lt;code&amp;gt;email&amp;lt;/code&amp;gt; – The email address of the user to reset the password for&lt;br /&gt;
* &amp;lt;code&amp;gt;default&amp;lt;/code&amp;gt; (optional) – The email address to send the new password to, if the user did not specify a secondary email address&lt;br /&gt;
&lt;br /&gt;
=== Expose key ===&lt;br /&gt;
&lt;br /&gt;
POST &amp;lt;code&amp;gt;/guardsupport/?action=expose_key&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Marks a deleted user key temporary as “exposed” and creates a unique URL for downloading the exposed key.&lt;br /&gt;
Automatic resetting of exposed keys to &amp;quot;not exposed&amp;quot; is scheduled once a day and resets all exposed keys which have been exposed before X hours, where X can be configured using com.openexchange.guard.exposedKeyDurationInHours in the guard.properties files.&lt;br /&gt;
&lt;br /&gt;
Since Guard 2.0&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
* &amp;lt;code&amp;gt;email&amp;lt;/code&amp;gt; – The email address of the user to expose the deleted keys for&lt;br /&gt;
* &amp;lt;code&amp;gt;cid&amp;lt;/code&amp;gt; – The context id&lt;br /&gt;
&lt;br /&gt;
Response:&lt;br /&gt;
An URL pointing to the downloadable exposed keys&lt;br /&gt;
&lt;br /&gt;
=== Delete user ===&lt;br /&gt;
&lt;br /&gt;
POST &amp;lt;code&amp;gt;/guardsupport/?action=delete_user&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Deletes all keys related to a certain user. The keys are backed up and can be exposed using the “expose_key” call.&lt;br /&gt;
&lt;br /&gt;
Since Guard 2.0&lt;br /&gt;
&lt;br /&gt;
Parameters:&lt;br /&gt;
* &amp;lt;code&amp;gt;user_id&amp;lt;/code&amp;gt; – The user&#039;s id&lt;br /&gt;
* &amp;lt;code&amp;gt;cid&amp;lt;/code&amp;gt; - The context id&lt;br /&gt;
&lt;br /&gt;
= Customization =&lt;br /&gt;
&lt;br /&gt;
Guard&#039;s templates are customizable at the user and context level.  Please see [[AppSuite:GuardCustomization| Customization]] for details&lt;br /&gt;
&lt;br /&gt;
= Entropy =&lt;br /&gt;
&lt;br /&gt;
Guard requires entropy (randomness) to generate the private/public keys that are used.  Depending on the server and it&#039;s environment, this may become a problem.  Please see [[AppSuite:GuardEntropy | Entropy]] for a possible solution&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=Template:AdditionalKnownIssues&amp;diff=16697</id>
		<title>Template:AdditionalKnownIssues</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=Template:AdditionalKnownIssues&amp;diff=16697"/>
		<updated>2013-12-11T13:52:33Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- A collection of additional known issues with all our software that might be necessary to warn customers about --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* This feature does not work if this feature is &#039;&#039;disabled&#039;&#039;. The latter means it is &#039;&#039;not enabled&#039;&#039;.&lt;br /&gt;
** It would be okay to be disabled if you continue to enable it before usage.&lt;br /&gt;
*** Never call this process disdisabling, though.&lt;br /&gt;
* If you enable the feature, it may be broken&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=Template:AdditionalKnownIssues&amp;diff=16695</id>
		<title>Template:AdditionalKnownIssues</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=Template:AdditionalKnownIssues&amp;diff=16695"/>
		<updated>2013-12-11T13:26:11Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- A collection of additional known issues with all our software that might be necessary to warn customers about --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* This feature does not work if this feature is &#039;&#039;disabled&#039;&#039;. The latter means it is &#039;&#039;not enabled&#039;&#039;.&lt;br /&gt;
** It would be okay to be disabled if you continue to enable it before usage.&lt;br /&gt;
*** Never call this process disdisabling, though.&lt;br /&gt;
* If you enabled the feature, it may be broken&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=OX6:UpdatingOXPackages&amp;diff=6791</id>
		<title>OX6:UpdatingOXPackages</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=OX6:UpdatingOXPackages&amp;diff=6791"/>
		<updated>2010-12-22T15:12:14Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: /* On Debian based distributions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Updating Open-Xchange Server packages ==&lt;br /&gt;
&lt;br /&gt;
This article describes how to update Open-Xchange Server packages from one service pack to another.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What is written here only applies to Open-Xchange Server Service Pack levels SP4 and newer!&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== How to get updates? ===&lt;br /&gt;
&lt;br /&gt;
Open-Xchange Server 6 updates can be accessed by customers with a valid license for&lt;br /&gt;
&lt;br /&gt;
* OX SE&lt;br /&gt;
* OX HE&lt;br /&gt;
&lt;br /&gt;
Have a look at the article:&lt;br /&gt;
[http://sdb.open-xchange.com/node/65 How to create an OXAccount and unlock Keys within the License Database]&lt;br /&gt;
for more information about how to create an account in the [http://ldb.open-xchange.com LDB].&lt;br /&gt;
&lt;br /&gt;
=== What Service Pack do I have installed? ===&lt;br /&gt;
&lt;br /&gt;
The service pack can be determined in checking the version number of the &amp;lt;tt&amp;gt;open-xchange&amp;lt;/tt&amp;gt; package. The second digit relates to the SP version. As of 6.10, these service pack version are obsolete. The following table shows a list of package versions and the corresponding SP number:&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
! Package version&lt;br /&gt;
! SP Version&lt;br /&gt;
|- &lt;br /&gt;
| 6.4&lt;br /&gt;
| SP3&lt;br /&gt;
|-&lt;br /&gt;
| 6.6&lt;br /&gt;
| SP4&lt;br /&gt;
|-&lt;br /&gt;
| 6.8&lt;br /&gt;
| SP5&lt;br /&gt;
|-&lt;br /&gt;
| 6.10&lt;br /&gt;
| -&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
If the second digit is an odd number (e.g. 6.3, 6.5 or 6.7), you have a beta or snapshot version installed.&lt;br /&gt;
&lt;br /&gt;
See [[Versioning_and_Numbering]] for more information on Open-Xchange versioning.&lt;br /&gt;
&lt;br /&gt;
==== How to determine the version number? ====&lt;br /&gt;
===== On Debian based distributions =====&lt;br /&gt;
&lt;br /&gt;
Run&lt;br /&gt;
&lt;br /&gt;
 $ dpkg -l open-xchange&lt;br /&gt;
&lt;br /&gt;
The following output should appear:&lt;br /&gt;
&lt;br /&gt;
 Desired=Unknown/Install/Remove/Purge/Hold&lt;br /&gt;
 | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed&lt;br /&gt;
 |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)&lt;br /&gt;
 ||/ Name               Version            Description&lt;br /&gt;
 +++-==================-==================-====================================================&lt;br /&gt;
 ii  open-xchange       6.6.0-1            Open-Xchange server scripts and configuration&lt;br /&gt;
&lt;br /&gt;
===== On RPM based distributions =====&lt;br /&gt;
&lt;br /&gt;
Run&lt;br /&gt;
&lt;br /&gt;
 $ rpm -q open-xchange&lt;br /&gt;
&lt;br /&gt;
The following output should appear:&lt;br /&gt;
&lt;br /&gt;
 open-xchange-6.6.0-1.1&lt;br /&gt;
&lt;br /&gt;
=== Installing Updates ===&lt;br /&gt;
&lt;br /&gt;
A new service pack usually introduces new packages and requires configuration changes. To get all required new packages and configuration changes, the following &#039;&#039;&#039;must&#039;&#039;&#039; be done when installing updates.&lt;br /&gt;
&lt;br /&gt;
==== On Debian based distributions ====&lt;br /&gt;
&lt;br /&gt;
To ensure, that all required configuration file changes will be applied to the Open-Xchange packages, you need to leave the original files as they are and the &amp;lt;tt&amp;gt;postinst&amp;lt;/tt&amp;gt; mechanism will automatically apply all new configuration options to the existing configuration files. Existing configuration parameters will not be automatically updated and need to be reviewed manually.&lt;br /&gt;
&lt;br /&gt;
You can do that in answering all the questions like e.g. this&lt;br /&gt;
&lt;br /&gt;
 Configuration file `/opt/open-xchange/etc/groupware/system.properties&#039;&lt;br /&gt;
  ==&amp;gt; Modified (by you or by a script) since installation.&lt;br /&gt;
  ==&amp;gt; Package distributor has shipped an updated version.&lt;br /&gt;
    What would you like to do about it ?  Your options are:&lt;br /&gt;
     Y or I  : install the package maintainer&#039;s version&lt;br /&gt;
     N or O  : keep your currently-installed version&lt;br /&gt;
       D     : show the differences between the versions&lt;br /&gt;
       Z     : background this process to examine the situation&lt;br /&gt;
  The default action is to keep your current version.&lt;br /&gt;
 *** system.properties (Y/I/N/O/D/Z) [default=N] ?&lt;br /&gt;
&lt;br /&gt;
with the default answer &amp;quot;N&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Note: this will not replace the existing configuration files. Depending on the new Open-Xchange version you&#039;re installing it is mandatory that configuration options shipped with the new packages are taken over to the configuration. This can be done by using &amp;lt;tt&amp;gt;diff&amp;lt;/tt&amp;gt; on the currently installed configuration and the updated configuration files which are copied to the configuration directory and have the file extension &amp;lt;tt&amp;gt;.dpkg-dist&amp;lt;/tt&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
If you don&#039;t want to do that every time, you could tell apt-get to answer this question for you, just cut and paste the following command in a shell as root user:&lt;br /&gt;
&lt;br /&gt;
 cat&amp;lt;&amp;lt;EOF &amp;gt; /etc/apt/apt.conf.d/01oxupdater&lt;br /&gt;
 DPkg::options {&amp;quot;--force-confold&amp;quot;;};&lt;br /&gt;
 EOF&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Note: This change will apply to ALL packages you are going to update in the future, not only Open-Xchange packages.&lt;br /&gt;
&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Add the following entry to &amp;lt;tt&amp;gt;/etc/apt/sources.list&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 deb http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/DebianLenny /&lt;br /&gt;
&lt;br /&gt;
Then run&lt;br /&gt;
&lt;br /&gt;
 $ apt-get update&lt;br /&gt;
&lt;br /&gt;
 $ apt-get dist-upgrade&lt;br /&gt;
&lt;br /&gt;
If you want to see, what apt-get is going to do without actually doing it, you can run:&lt;br /&gt;
&lt;br /&gt;
 $ apt-get dist-upgrade -s&lt;br /&gt;
&lt;br /&gt;
==== On RPM based distributions ====&lt;br /&gt;
&lt;br /&gt;
===== RHEL5 =====&lt;br /&gt;
&lt;br /&gt;
Add the following entry to &amp;lt;tt&amp;gt;/etc/yum.repos.d/ox.repo&amp;lt;/tt&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
 [ox-updates]&lt;br /&gt;
 name=Open-Xchange Updates&lt;br /&gt;
 baseurl=http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/RHEL5/&lt;br /&gt;
 enabled=1&lt;br /&gt;
 gpgcheck=0&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
and run&lt;br /&gt;
&lt;br /&gt;
 $ yum update&lt;br /&gt;
&lt;br /&gt;
 $ yum upgrade&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== SLES10 =====&lt;br /&gt;
&lt;br /&gt;
Add the updates repository to the repository list:&lt;br /&gt;
&lt;br /&gt;
 $ zypper sa http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/SLES10/ OXUPDATES&lt;br /&gt;
&lt;br /&gt;
and run&lt;br /&gt;
&lt;br /&gt;
 $ zypper up -y -t package&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note: package is not the name of a package, but an option, so just copy and paste the complete line.&lt;br /&gt;
&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===== SLES11 =====&lt;br /&gt;
&lt;br /&gt;
Add the updates repository to the repository list:&lt;br /&gt;
&lt;br /&gt;
 $ zypper ar http://LDBACCOUNT:LDBPASSWORD@software.open-xchange.com/OX6/updates/SLES11/ OXUPDATES&lt;br /&gt;
&lt;br /&gt;
and run&lt;br /&gt;
&lt;br /&gt;
 $ zypper dup -r OXUPDATES&lt;br /&gt;
&lt;br /&gt;
You might need to run&lt;br /&gt;
&lt;br /&gt;
 $ zypper ref&lt;br /&gt;
&lt;br /&gt;
to update the repository metadata before running &#039;&#039;zypper up&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
[[Category: OX6]]&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=OXSE4UCS_Installation_en&amp;diff=6713</id>
		<title>OXSE4UCS Installation en</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=OXSE4UCS_Installation_en&amp;diff=6713"/>
		<updated>2010-12-15T12:37:26Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: /* OXtender for Business Mobility */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Introduction= &lt;br /&gt;
The Open-Xchange Advanced Server Edition (OXASE)/Open-Xchange Server Edition for Univention Corporate Server (OXSE4UCS) includes the groupware Open-Xchange and the integration packages for Univention Corporate Server (UCS).&lt;br /&gt;
&lt;br /&gt;
Open-Xchange Advanced Server Edition (OXASE)/Open-Xchange Server Edition for Univention Corporate Server (OXSE4UCS) is tailored to professional users looking for a tried-and-tested solution for the management of their entire IT infrastructure including groupware or companies which already employ UCS and wish to expand their infrastructure with innovative groupware functions.&lt;br /&gt;
&lt;br /&gt;
More detailed information on UCS can be found on the Univention GmbH website: [http://www.univention.de/dokumentation.html http://www.univention.de/dokumentation.html].&lt;br /&gt;
&lt;br /&gt;
= Differences between OXASE and OXSE for UCS =&lt;br /&gt;
OXASE can not be used as&lt;br /&gt;
* Domain Controller&lt;br /&gt;
* Print Server&lt;br /&gt;
* Database, web or directory service server (unless not for the exclusive use with Open Xchange)&lt;br /&gt;
* IP management system&lt;br /&gt;
* Software distribution system&lt;br /&gt;
* Network or service monitoring system&lt;br /&gt;
* Management tool for Windows or Linux based systems&lt;br /&gt;
&lt;br /&gt;
Except for&lt;br /&gt;
* the provisioning, use and management of file services  („shares“) with the Samba software&lt;br /&gt;
* the temporary, three-months limited, non-productive use of UCS for evaluation purposes&lt;br /&gt;
&lt;br /&gt;
= First Step: Installation Univention Corporate Server =&lt;br /&gt;
As OXASE/OXSE4UCS is an expansion pack for the Univention Corporate Server, one or more UCS server(s) must be installed firstly.&lt;br /&gt;
There are several possible different installation scenarios. In principle, OXASE/OXSE4UCS can be installed on all UCS domain controller server roles: DC master, DC backup or DC slave. Installation on the server roles member server or base system is not currently possible.&lt;br /&gt;
&lt;br /&gt;
To start, the Univention Corporate Server systems are installed as usual with UCS 2.4. &#039;&#039;&#039;The download link for the installation of the Univention Corporate Server system is provided at your Email purchase information.&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
If these information isn&#039;t available, you have the possibility to download the Univention Corporate Server Free-For-Personal-Use-Version under [http://www.univention.de/en/download/free-for-personal-use-edition/download/ http://www.univention.de/en/download/free-for-personal-use-edition/download/]. After registration of your Univention license key or license file authorizes the use of the respective Univention components of the purchased product for the respective license agreement.&lt;br /&gt;
&lt;br /&gt;
If several systems are in the UCS domain, a check must be performed that the join procedure has been run on all servers. This is usually done at the end of the installation procedure. Further information on the installation of UCS can be found in the UCS manual: [http://www.univention.de/dokumentation.html http://www.univention.de/dokumentation.html]&lt;br /&gt;
&lt;br /&gt;
= Second Step: Installation Open-Xchange Advanced Server Edition / Server Edition =&lt;br /&gt;
&lt;br /&gt;
The password-protected Open-Xchange repository must be integrated on all the systems where OXASE/OXSE4UCS packages are to be installed. The following Univention Configuration Registry variables (UCR variables) can be used to do this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ export LDBUSER=”myusername” LDBPASS=”secret”&lt;br /&gt;
$ ucr set repository/online/component/ox/server=software.open-xchange.com \&lt;br /&gt;
	repository/online/component/ox/prefix=OX6/OXSEforUCS \&lt;br /&gt;
	repository/online/component/ox/username=”$LDBUSER” \&lt;br /&gt;
	repository/online/component/ox/password=”$LDBPASS” \&lt;br /&gt;
	repository/online/component/ox/version=current \&lt;br /&gt;
	repository/online/component/ox=enabled \&lt;br /&gt;
	repository/online/component/oxseforucs/server=software.open-xchange.com \&lt;br /&gt;
	repository/online/component/oxseforucs/prefix=OX6/OXSEforUCS \&lt;br /&gt;
	repository/online/component/oxseforucs/username=”$LDBUSER” \&lt;br /&gt;
	repository/online/component/oxseforucs/password=”$LDBPASS” \&lt;br /&gt;
	repository/online/component/oxseforucs/version=current \&lt;br /&gt;
	repository/online/component/oxseforucs=enabled&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The access data (&#039;&#039;myusername&#039;&#039; and &#039;&#039;secret&#039;&#039;) are created when the Open-Xchange licence is activated and must be adapted here accordingly.&lt;br /&gt;
&lt;br /&gt;
== Installation on a DC master ==&lt;br /&gt;
When installing OXASE/OXSE4UCS on a DC master, only the &#039;&#039;&#039;univention-ox-meta-singleserver&#039;&#039;&#039; package requires installing. This can be performed via the Univention Management Console or on the command line:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
  $ univention-install univention-ox-meta-singleserver&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The univention-ox-meta-singleserver package automatically installs packages for the filtering of spam and viruses at the same time. If this is not required, the univention-ox and univention-mail-cyrus-ox packages can be installed instead of the univention-ox-meta-singleserver package.&lt;br /&gt;
&lt;br /&gt;
==Installation on a dedicated DC slave==&lt;br /&gt;
In this installation scenario, the DC slave system acts as a standalone Open-Xchange groupware server. To start, the univention-ox-directory-integration package must be installed on the DC master in order to initiate integration in the UCS management system.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 $ univention-install univention-ox-directory-integration&lt;br /&gt;
 $ univention-actualise&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
     &lt;br /&gt;
The univention-ox-meta-singleserver package is installed on the DC slave which is to be used as the groupware server. In addition, the join scripts must also be run following the installation:                                                     &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ univention-install univention-ox-meta-singleserver&lt;br /&gt;
$ univention-actualise&lt;br /&gt;
$ univention-run-join-scripts&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The univention-ox-meta-singleserver package automatically installs packages for the filtering of spam and viruses. If this is not required, the univention-ox and univention-mail-cyrus-ox packages can be specified instead of the univention-ox-meta-singleserver package.&lt;br /&gt;
&lt;br /&gt;
== Installation in a distributed environment ==&lt;br /&gt;
When installing a distributed environment, integration in the UCS management system must be performed firstly by installing univention-ox-directory-integration on DC Master.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ univention-install univention-ox-directory-integration&lt;br /&gt;
$ univention-actualise                                  &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following services can then be distributed on the other UCS systems:  &lt;br /&gt;
* IMAP server and optionally spam and virus filtering (univention-mail-cyrus-ox and optionally univention-mail-antispam-ox and univention-antivir-mail)&lt;br /&gt;
* MySQL server (&#039;&#039;mysql-server&#039;&#039;)&lt;br /&gt;
* OX instance (&#039;&#039;univention-ox&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
	&lt;br /&gt;
===MySQL server===&lt;br /&gt;
The MySQL server is installed by installing the mysql-server package.                                                     &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ univention-install mysql-server&lt;br /&gt;
$ univention-actualise                                           &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The configuration of the MySQL server should be set so that the MySQL service can be accessed via the external network interfaces. To do this, for example, the bind-address option can be set to 0.0.0.0 in the MySQL configuration file /etc/mysql/my.cnf.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
bind-address 0.0.0.0                                                             &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After the change, the MySQL service needs to be restarted:                 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ /etc/init.d/mysql restart&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In addition, the OX instances must be authorized to access the database. The following gives an example, which must be adapted to the environment at hand.                                                                  &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ mysql                                                                            &lt;br /&gt;
mysql&amp;gt; GRANT ALL PRIVILEGES ON *.* TO \                                          &lt;br /&gt;
 &#039;openexchange&#039;@&#039;ox-instance1.example.com&#039; \                                       &lt;br /&gt;
 IDENTIFIED BY &#039;secret&#039;;                                                         &lt;br /&gt;
mysql&amp;gt; GRANT ALL PRIVILEGES ON *.* TO \                                          &lt;br /&gt;
 &#039;openexchange&#039;@&#039;ox-instance2.example.com&#039; \                                       &lt;br /&gt;
 IDENTIFIED BY &#039;secret&#039;;                                                         &lt;br /&gt;
mysql&amp;gt; GRANT ...                                                                 &lt;br /&gt;
mysql&amp;gt; FLUSH PRIVILEGES;                                                         &lt;br /&gt;
mysql&amp;gt; exit                           &lt;br /&gt;
$&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
                                           &lt;br /&gt;
=== Active OX instance ===&lt;br /&gt;
The &#039;&#039;&#039;univention-ox&#039;&#039;&#039; package must be installed on the active OX instance.       &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ univention-install univention-ox&lt;br /&gt;
$ univention-actualise                                                    &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then certain environment variables must be set to ensure that the join scripts run later receive the corresponding permissions. The following gives an example, which must be adapted to the environment at hand. The variable OXDB defines the MySQL server to be used by the OX instance. The corresponding password should be saved in the variable OXDBPW. The standard IMAP server must be specified in the variable OXIMAPSERVER. Hostnames need to be specified as fully qualified domain names (FQDN). It is not possible to use IP addresses.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ export HISTIGNORE=&amp;quot;export*&amp;quot;&lt;br /&gt;
$ export OXDB=oxdbserver.ucs.local&lt;br /&gt;
$ export OXDBPW=&amp;quot;secret&amp;quot;&lt;br /&gt;
$ export OXIMAPSERVER=oximapserver.ucs.local                                 &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then the join scripts need to run:                                       &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ univention-run-join-scripts&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally, the environment variable OXDBPW with the password can be unset using the following command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ unset OXDBPW&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
=== IMAP server ===&lt;br /&gt;
The IMAP server is installed by installing the &#039;&#039;&#039;univention-mail-cyrus-ox&#039;&#039;&#039; package.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ univention-install univention-mail-cyrus-ox&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The spam check via spamassassin can be installed and activated by installing the univention-mail-antispam-ox package:             &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ univention-install univention-mail-antispam-ox&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The virus check via &#039;&#039;amavis&#039;&#039; and &#039;&#039;clamav&#039;&#039; can be installed and activated by installing the u&#039;&#039;&#039;nivention-antivir-mail&#039;&#039;&#039; package.                                                            &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ univention-install univention-antivir-mail                                  &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A check should then be performed to see whether all join scripts have been run successfully:                                                            &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ univention-actualise&lt;br /&gt;
$ univention-run-join-scripts&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Additional passive OX instances ===&lt;br /&gt;
Firstly, the &#039;&#039;&#039;univention-ox&#039;&#039;&#039; package must also be installed on the additional passive OX instances. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ univention-install univention-ox&lt;br /&gt;
$ univention-actualise                                                                                                                    &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then the settings can be copied from the active OX instance. This can be done, for example, using the following command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ rsync -essh -a root@ox-instance1.ucs.local:/opt/open-xchange/. /opt/open-xchange/&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The FQDN of the current computer must be entered in the&#039;&#039; /opt/open-xchange/etc/groupware/usm.properties&#039;&#039; file:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
com.openexchange.usm.ox.url=ox-instance2.ucs.local&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The FQDN of the current computer must also be entered in the&#039;&#039; /opt/open-xchange/etc/authplugin.properties&#039;&#039; file:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
LDAP_HOST=ox-instance2.ucs.local&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally, the groupware must be restarted on the passive OX instance:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ /etc/init.d/open-xchange-admin restart&lt;br /&gt;
$ /etc/init.d/open-xchange-groupware restart&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OXtender for Business Mobility ==&lt;br /&gt;
&lt;br /&gt;
The Open-Xchange OXtender for Business Mobility is an optionally available component for OXASE/OXSE4UCS which enables the connection of mobile devices. The repository must be activated for it to be possible to install the corresponding packages:                                                                            &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ export LDBUSER=”ldbuser” LDBPASS=”lsbpass”&lt;br /&gt;
$ ucr set repository/online/component/oxmobility/server=software.open-xchange.com \&lt;br /&gt;
	repository/online/component/oxmobility/prefix=OX6/OXSEforUCS \&lt;br /&gt;
	repository/online/component/oxmobility/username=”$LDBUSER” \&lt;br /&gt;
	repository/online/component/oxmobility/password=”$LDBPASS” \&lt;br /&gt;
	repository/online/component/oxmobility/version=current \&lt;br /&gt;
	repository/online/component/oxmobility=enabled&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Installing the &#039;&#039;&#039;univention-ox-usm-ox&#039;&#039;&#039; package installs the Oxtender for Business Mobility on the OXASE/OXSE4UCS system.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ univention-install univention-ox-usm-ox&lt;br /&gt;
§ reboot&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the target system is neither a DC master nor a DC backup system, the &#039;&#039;&#039;univention-ox-usm-udm&#039;&#039;&#039; package should also be installed on the DC master.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ univention-install univention-ox-usm-udm&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Updating=&lt;br /&gt;
To update a UCS 2.3-2 system with OXASE/OXSE4UCS 6.16 to 6.18.1 with UCS 2.4, the following variables must be set before the update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ ucr set repository/online/component/ox/version=current \&lt;br /&gt;
	repository/online/component/oxseforucs/version=current&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The system can then be updated as usual for UCS using the univention-updater net command or the UMC module Online Update.&lt;br /&gt;
&lt;br /&gt;
=Administration=&lt;br /&gt;
&lt;br /&gt;
== UMC module “Licence management” ==&lt;br /&gt;
Alongside the configuration of the Open-Xchange account, the UMC module “Licence management” can also be used to set a maintenance key and for the simplified import of a licence file.&lt;br /&gt;
&lt;br /&gt;
The configuration of an Open-Xchange account is necessary to be able to import version and software updates for OXSE for UCS via the UMC module “Online updates”, as the online repositories require an authentication. In this case, the user data (user name and password) required are the same as those which were also used for the licence database (http://ldb.open-xchange.com). &lt;br /&gt;
&lt;br /&gt;
Once the account has been added via the Add account button, the OXSE for UCS is configured automatically for a subsequent online update. The account can be altered subsequently via the Change account button.&lt;br /&gt;
&lt;br /&gt;
When adding/changing an account, the user name and password entered are verified automatically. This is done by connecting to the licence database. To reset the password for an account, the Request password reset button can be used to reset the password for the specified account. The user name must be entered in the dialogue which opens; the password must be entered twice. On confirmation, an e-mail is sent to the e-mail address specified for the account containing a confirmation link, which can be opened in the browser to complete the process.&lt;br /&gt;
&lt;br /&gt;
Alongside specification of an Open-Xchange account, it is also possible to select a licence key at this stage, which was saved automatically on the Open-Xchange account on its activation. The licence key is selected using the Change licence key button.&lt;br /&gt;
&lt;br /&gt;
A variety of licence information for a licence key is stored in the licence database (e.g., LDAP basic DN or the number of licensed users). The Update licence button is used to request this licence information online in the form of a licence file initially after the installation or following subsequent licensing and import it automatically into the management system.&lt;br /&gt;
&lt;br /&gt;
You may be requested to accept the current end user license agreement (EULA) at this stage. If the EULA has already been accepted, e.g., via the (http://ldb.open-xchange.com) license database, this step is bypassed automatically. In the case of a EULA update, it may be necessary to confirm the EULA anew at a subsequent point in time.&lt;br /&gt;
Once licensing is completed, the Switch to online update module button can be used to open the module for importing version and security updates.&lt;br /&gt;
	&lt;br /&gt;
== User and group management ==&lt;br /&gt;
New users and groups can be created using the Univention Directory Manager (UDM). The UDM can be accessed on the DC master via a web browser at https://&amp;lt;IP address of DC master&amp;gt;/udm/. It is possible to log in as the Administrator user using the password specified during the installation.&lt;br /&gt;
&lt;br /&gt;
When creating a user, the open-xchange groupware account user template should be selected. This preselects all Open-Xchange specific settings.&lt;br /&gt;
&lt;br /&gt;
== System messages ==&lt;br /&gt;
The mail/alias/root UCS variable must be set so that system messages can be delivered. To do this, either a new account can be created or, alternatively, oxadmin@DOMAIN is provided for this purpose:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ ucr set mail/alias/root=oxadmin@ucs.local&lt;br /&gt;
$ newaliases&lt;br /&gt;
$ /etc/init.d/postfix reload&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is possible to log in as the oxadmin user in the Open-Xchange web interface using the password from the /etc/ox-secrets/context10.secret file.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: OX6]]&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=Template:ApacheOXConf&amp;diff=6384</id>
		<title>Template:ApacheOXConf</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=Template:ApacheOXConf&amp;diff=6384"/>
		<updated>2010-08-04T09:00:23Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Configure the &#039;&#039;mod_proxy_ajp&#039;&#039; module by creating a new Apache configuration file.&lt;br /&gt;
&lt;br /&gt;
 $ vim {{{ajpconf}}}&lt;br /&gt;
&lt;br /&gt;
 {{{loadmodule}}}&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;Proxy *&amp;gt;&lt;br /&gt;
 Order deny,allow&lt;br /&gt;
 allow from all&lt;br /&gt;
 &amp;lt;/Proxy&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ProxyPass /axis2 ajp://127.0.0.1:8009/axis2 smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /ajax ajp://127.0.0.1:8009/ajax smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /servlet ajp://127.0.0.1:8009/servlet smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /infostore ajp://127.0.0.1:8009/infostore smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /publications ajp://127.0.0.1:8009/publications smax=0 ttl=60 retry=5&lt;br /&gt;
 # next line is required for OXtender for Business Mobility only&lt;br /&gt;
 ProxyPass /Microsoft-Server-ActiveSync ajp://127.0.0.1:8009/Microsoft-Server-ActiveSync smax=0 ttl=60 retry=5&lt;br /&gt;
&lt;br /&gt;
Modify the default website settings to display the Open-Xchange GUI&lt;br /&gt;
&lt;br /&gt;
For versions of Open-Xchange &#039;&#039;&#039;prior&#039;&#039;&#039; to 6.18:&lt;br /&gt;
&lt;br /&gt;
 $ vim {{{apacheconf}}}&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:80&amp;gt;&lt;br /&gt;
 	ServerAdmin webmaster@localhost&lt;br /&gt;
 &lt;br /&gt;
 	DocumentRoot {{{docroot}}}&lt;br /&gt;
 &lt;br /&gt;
 	&amp;lt;Directory {{{docroot}}}&amp;gt;&lt;br /&gt;
 		AllowOverride None&lt;br /&gt;
 		Order allow,deny&lt;br /&gt;
 		allow from all&lt;br /&gt;
 		RedirectMatch ^/$ /ox6/&lt;br /&gt;
 	&amp;lt;/Directory&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 	ExpiresActive On&lt;br /&gt;
 	ExpiresByType image/gif &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType image/png &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType image/jpg &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType image/jpeg &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType text/javascript &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType text/css &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType text/html &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType application/x-javascript &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	&amp;lt;Files ~ &amp;quot;\.(js|css|gif|jpe?g|png)$&amp;quot;&amp;gt;&lt;br /&gt;
 		Header append Cache-Control &amp;quot;public&amp;quot;&lt;br /&gt;
 	&amp;lt;/Files&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 	DeflateFilterNote ratio&lt;br /&gt;
 	AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/x-js application/x-javascript application/javascript&lt;br /&gt;
 	BrowserMatch ^Mozilla/4 gzip-only-text/html&lt;br /&gt;
 	BrowserMatch ^Mozilla/4\.0[678] no-gzip&lt;br /&gt;
 	BrowserMatch \bMSI[E] !no-gzip !gzip-only-text/html&lt;br /&gt;
 	Header append Vary User-Agent env=!dont-vary&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For versions of Open-Xchange &#039;&#039;&#039;starting with&#039;&#039;&#039; 6.18:&lt;br /&gt;
&lt;br /&gt;
 $ vim {{{apacheconf}}}&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:80&amp;gt;&lt;br /&gt;
 	ServerAdmin webmaster@localhost&lt;br /&gt;
 &lt;br /&gt;
 	DocumentRoot {{{docroot}}}&lt;br /&gt;
 &lt;br /&gt;
 	&amp;lt;Directory {{{docroot}}}&amp;gt;&lt;br /&gt;
 		AllowOverride None&lt;br /&gt;
 		Order allow,deny&lt;br /&gt;
 		allow from all&lt;br /&gt;
 		RedirectMatch ^/$ /ox6/&lt;br /&gt;
                Options +FollowSymLinks +SymLinksIfOwnerMatch&lt;br /&gt;
 	&amp;lt;/Directory&amp;gt;&lt;br /&gt;
        # deflate&lt;br /&gt;
       AddOutputFilterByType DEFLATE text/html text/plain text/javascript application/javascript text/css text/xml application/xml text/x-js application/x-javascript&lt;br /&gt;
 &lt;br /&gt;
 	# pre-compressed files&lt;br /&gt;
 	AddType text/javascript .jsz&lt;br /&gt;
 	AddType text/css .cssz&lt;br /&gt;
 	AddType text/xml .xmlz&lt;br /&gt;
 	&lt;br /&gt;
 	AddEncoding x-gzip .jsz .cssz .xmlz&lt;br /&gt;
 	SetEnvIf Request_URI &amp;quot;\.(jsz|cssz|xmlz)$&amp;quot; no-gzip&lt;br /&gt;
 	&lt;br /&gt;
 	ExpiresActive On&lt;br /&gt;
 	&lt;br /&gt;
 	&amp;lt;Location /ox6&amp;gt;&lt;br /&gt;
 	        # Expires (via ExpiresByType to override global settings)&lt;br /&gt;
 	        ExpiresByType image/gif &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType image/png &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType image/jpg &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType image/jpeg &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/css &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/html &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/xml &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/javascript &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/x-js &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType application/x-javascript &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresDefault &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        Header append Cache-Control &amp;quot;private&amp;quot;&lt;br /&gt;
 	        Header unset Last-Modified&lt;br /&gt;
 	        Header unset Vary&lt;br /&gt;
 	        # Strip version&lt;br /&gt;
 	        RewriteEngine On&lt;br /&gt;
 	        RewriteRule v=\w+/(.+) $1 [L]&lt;br /&gt;
 	        # Turn off ETag&lt;br /&gt;
 	        Header unset ETag&lt;br /&gt;
 	        FileETag None&lt;br /&gt;
 	&amp;lt;/Location&amp;gt;&lt;br /&gt;
 	&lt;br /&gt;
 	&amp;lt;Location /ox6/ox.html&amp;gt;&lt;br /&gt;
 	        ExpiresByType text/html &amp;quot;now&amp;quot;&lt;br /&gt;
 	        ExpiresDefault &amp;quot;now&amp;quot;&lt;br /&gt;
 	        Header unset Last-Modified&lt;br /&gt;
 	        Header set Cache-Control &amp;quot;no-store, no-cache, must-revalidate, post-check=0, pre-check=0&amp;quot;&lt;br /&gt;
 	        # Turn off ETag&lt;br /&gt;
 	        Header unset ETag&lt;br /&gt;
 	        FileETag None&lt;br /&gt;
 	&amp;lt;/Location&amp;gt;&lt;br /&gt;
 	&lt;br /&gt;
 	&amp;lt;Location /ox6/index.html&amp;gt;&lt;br /&gt;
 	        ExpiresByType text/html &amp;quot;now&amp;quot;&lt;br /&gt;
 	        ExpiresDefault &amp;quot;now&amp;quot;&lt;br /&gt;
 	        Header unset Last-Modified&lt;br /&gt;
 	        Header set Cache-Control &amp;quot;no-store, no-cache, must-revalidate, post-check=0, pre-check=0&amp;quot;&lt;br /&gt;
 	        # Turn off ETag&lt;br /&gt;
 	        Header unset ETag&lt;br /&gt;
 	        FileETag None&lt;br /&gt;
 	&amp;lt;/Location&amp;gt;&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=Template:ApacheOXConf&amp;diff=6383</id>
		<title>Template:ApacheOXConf</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=Template:ApacheOXConf&amp;diff=6383"/>
		<updated>2010-08-04T08:59:10Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Configure the &#039;&#039;mod_proxy_ajp&#039;&#039; module by creating a new Apache configuration file.&lt;br /&gt;
&lt;br /&gt;
 $ vim {{{ajpconf}}}&lt;br /&gt;
&lt;br /&gt;
 {{{loadmodule}}}&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;Proxy *&amp;gt;&lt;br /&gt;
 Order deny,allow&lt;br /&gt;
 allow from all&lt;br /&gt;
 &amp;lt;/Proxy&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ProxyPass /axis2 ajp://127.0.0.1:8009/axis2 smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /ajax ajp://127.0.0.1:8009/ajax smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /servlet ajp://127.0.0.1:8009/servlet smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /infostore ajp://127.0.0.1:8009/infostore smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /publications ajp://127.0.0.1:8009/publications smax=0 ttl=60 retry=5&lt;br /&gt;
 # next line is required for OXtender for Business Mobility only&lt;br /&gt;
 ProxyPass /Microsoft-Server-ActiveSync ajp://127.0.0.1:8009/Microsoft-Server-ActiveSync smax=0 ttl=60 retry=5&lt;br /&gt;
&lt;br /&gt;
Modify the default website settings to display the Open-Xchange GUI&lt;br /&gt;
&lt;br /&gt;
For versions of Open-Xchange &#039;&#039;&#039;prior&#039;&#039;&#039; to 6.18:&lt;br /&gt;
&lt;br /&gt;
 $ vim {{{apacheconf}}}&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:80&amp;gt;&lt;br /&gt;
 	ServerAdmin webmaster@localhost&lt;br /&gt;
 &lt;br /&gt;
 	DocumentRoot {{{docroot}}}&lt;br /&gt;
 &lt;br /&gt;
 	&amp;lt;Directory {{{docroot}}}&amp;gt;&lt;br /&gt;
 		AllowOverride None&lt;br /&gt;
 		Order allow,deny&lt;br /&gt;
 		allow from all&lt;br /&gt;
 		RedirectMatch ^/$ /ox6/&lt;br /&gt;
 	&amp;lt;/Directory&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 	ExpiresActive On&lt;br /&gt;
 	ExpiresByType image/gif &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType image/png &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType image/jpg &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType image/jpeg &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType text/javascript &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType text/css &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType text/html &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType application/x-javascript &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	&amp;lt;Files ~ &amp;quot;\.(js|css|gif|jpe?g|png)$&amp;quot;&amp;gt;&lt;br /&gt;
 		Header append Cache-Control &amp;quot;public&amp;quot;&lt;br /&gt;
 	&amp;lt;/Files&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 	DeflateFilterNote ratio&lt;br /&gt;
 	AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/x-js application/x-javascript application/javascript&lt;br /&gt;
 	BrowserMatch ^Mozilla/4 gzip-only-text/html&lt;br /&gt;
 	BrowserMatch ^Mozilla/4\.0[678] no-gzip&lt;br /&gt;
 	BrowserMatch \bMSI[E] !no-gzip !gzip-only-text/html&lt;br /&gt;
 	Header append Vary User-Agent env=!dont-vary&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For versions of Open-Xchange &#039;&#039;&#039;starting with&#039;&#039;&#039; 6.18:&lt;br /&gt;
&lt;br /&gt;
 $ vim {{{apacheconf}}}&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:80&amp;gt;&lt;br /&gt;
 	ServerAdmin webmaster@localhost&lt;br /&gt;
 &lt;br /&gt;
 	DocumentRoot {{{docroot}}}&lt;br /&gt;
 &lt;br /&gt;
 	&amp;lt;Directory {{{docroot}}}&amp;gt;&lt;br /&gt;
 		AllowOverride None&lt;br /&gt;
 		Order allow,deny&lt;br /&gt;
 		allow from all&lt;br /&gt;
 		RedirectMatch ^/$ /ox6/&lt;br /&gt;
                Options +FollowSymLinks +SymLinksIfOwnerMatch&lt;br /&gt;
 	&amp;lt;/Directory&amp;gt;&lt;br /&gt;
        # deflate&lt;br /&gt;
       AddOutputFilterByType DEFLATE text/html text/plain text/javascript application/javascript text/css text/xml application/xml text/x-js application/x-javascript&lt;br /&gt;
 &lt;br /&gt;
 	# pre-compressed files&lt;br /&gt;
 	AddType text/javascript .jsz&lt;br /&gt;
 	AddType text/css .cssz&lt;br /&gt;
 	AddType text/xml .xmlz&lt;br /&gt;
 	&lt;br /&gt;
 	AddEncoding x-gzip .jsz .cssz .xmlz&lt;br /&gt;
 	SetEnvIf Request_URI &amp;quot;\.(jsz|cssz|xmlz)$&amp;quot; no-gzip&lt;br /&gt;
 	&lt;br /&gt;
 	ExpiresActive On&lt;br /&gt;
 	&lt;br /&gt;
 	&amp;lt;Location /ox6&amp;gt;&lt;br /&gt;
 	        # Expires (via ExpiresByType to override global settings)&lt;br /&gt;
 	        ExpiresByType image/gif &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType image/png &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType image/jpg &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType image/jpeg &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/css &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/html &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/xml &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/javascript &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
                ExpiresByType text/x-js &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType application/x-javascript &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresDefault &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        Header append Cache-Control &amp;quot;private&amp;quot;&lt;br /&gt;
 	        Header unset Last-Modified&lt;br /&gt;
 	        Header unset Vary&lt;br /&gt;
 	        # Strip version&lt;br /&gt;
 	        RewriteEngine On&lt;br /&gt;
 	        RewriteRule v=\w+/(.+) $1 [L]&lt;br /&gt;
 	        # Turn off ETag&lt;br /&gt;
 	        Header unset ETag&lt;br /&gt;
 	        FileETag None&lt;br /&gt;
 	&amp;lt;/Location&amp;gt;&lt;br /&gt;
 	&lt;br /&gt;
 	&amp;lt;Location /ox6/ox.html&amp;gt;&lt;br /&gt;
 	        ExpiresByType text/html &amp;quot;now&amp;quot;&lt;br /&gt;
 	        ExpiresDefault &amp;quot;now&amp;quot;&lt;br /&gt;
 	        Header unset Last-Modified&lt;br /&gt;
 	        Header set Cache-Control &amp;quot;no-store, no-cache, must-revalidate, post-check=0, pre-check=0&amp;quot;&lt;br /&gt;
 	        # Turn off ETag&lt;br /&gt;
 	        Header unset ETag&lt;br /&gt;
 	        FileETag None&lt;br /&gt;
 	&amp;lt;/Location&amp;gt;&lt;br /&gt;
 	&lt;br /&gt;
 	&amp;lt;Location /ox6/index.html&amp;gt;&lt;br /&gt;
 	        ExpiresByType text/html &amp;quot;now&amp;quot;&lt;br /&gt;
 	        ExpiresDefault &amp;quot;now&amp;quot;&lt;br /&gt;
 	        Header unset Last-Modified&lt;br /&gt;
 	        Header set Cache-Control &amp;quot;no-store, no-cache, must-revalidate, post-check=0, pre-check=0&amp;quot;&lt;br /&gt;
 	        # Turn off ETag&lt;br /&gt;
 	        Header unset ETag&lt;br /&gt;
 	        FileETag None&lt;br /&gt;
 	&amp;lt;/Location&amp;gt;&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=Template:ApacheOXConf&amp;diff=6382</id>
		<title>Template:ApacheOXConf</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=Template:ApacheOXConf&amp;diff=6382"/>
		<updated>2010-08-04T08:55:35Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Configure the &#039;&#039;mod_proxy_ajp&#039;&#039; module by creating a new Apache configuration file.&lt;br /&gt;
&lt;br /&gt;
 $ vim {{{ajpconf}}}&lt;br /&gt;
&lt;br /&gt;
 {{{loadmodule}}}&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;Proxy *&amp;gt;&lt;br /&gt;
 Order deny,allow&lt;br /&gt;
 allow from all&lt;br /&gt;
 &amp;lt;/Proxy&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ProxyPass /axis2 ajp://127.0.0.1:8009/axis2 smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /ajax ajp://127.0.0.1:8009/ajax smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /servlet ajp://127.0.0.1:8009/servlet smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /infostore ajp://127.0.0.1:8009/infostore smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /publications ajp://127.0.0.1:8009/publications smax=0 ttl=60 retry=5&lt;br /&gt;
 # next line is required for OXtender for Business Mobility only&lt;br /&gt;
 ProxyPass /Microsoft-Server-ActiveSync ajp://127.0.0.1:8009/Microsoft-Server-ActiveSync smax=0 ttl=60 retry=5&lt;br /&gt;
&lt;br /&gt;
Modify the default website settings to display the Open-Xchange GUI&lt;br /&gt;
&lt;br /&gt;
For versions of Open-Xchange &#039;&#039;&#039;prior&#039;&#039;&#039; to 6.18:&lt;br /&gt;
&lt;br /&gt;
 $ vim {{{apacheconf}}}&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:80&amp;gt;&lt;br /&gt;
 	ServerAdmin webmaster@localhost&lt;br /&gt;
 &lt;br /&gt;
 	DocumentRoot {{{docroot}}}&lt;br /&gt;
 &lt;br /&gt;
 	&amp;lt;Directory {{{docroot}}}&amp;gt;&lt;br /&gt;
 		AllowOverride None&lt;br /&gt;
 		Order allow,deny&lt;br /&gt;
 		allow from all&lt;br /&gt;
 		RedirectMatch ^/$ /ox6/&lt;br /&gt;
 	&amp;lt;/Directory&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 	ExpiresActive On&lt;br /&gt;
 	ExpiresByType image/gif &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType image/png &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType image/jpg &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType image/jpeg &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType text/javascript &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType text/css &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType text/html &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType application/x-javascript &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	&amp;lt;Files ~ &amp;quot;\.(js|css|gif|jpe?g|png)$&amp;quot;&amp;gt;&lt;br /&gt;
 		Header append Cache-Control &amp;quot;public&amp;quot;&lt;br /&gt;
 	&amp;lt;/Files&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 	DeflateFilterNote ratio&lt;br /&gt;
 	AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/x-js application/x-javascript application/javascript&lt;br /&gt;
 	BrowserMatch ^Mozilla/4 gzip-only-text/html&lt;br /&gt;
 	BrowserMatch ^Mozilla/4\.0[678] no-gzip&lt;br /&gt;
 	BrowserMatch \bMSI[E] !no-gzip !gzip-only-text/html&lt;br /&gt;
 	Header append Vary User-Agent env=!dont-vary&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For versions of Open-Xchange &#039;&#039;&#039;starting with&#039;&#039;&#039; 6.18:&lt;br /&gt;
&lt;br /&gt;
 $ vim {{{apacheconf}}}&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:80&amp;gt;&lt;br /&gt;
 	ServerAdmin webmaster@localhost&lt;br /&gt;
 &lt;br /&gt;
 	DocumentRoot {{{docroot}}}&lt;br /&gt;
 &lt;br /&gt;
 	&amp;lt;Directory {{{docroot}}}&amp;gt;&lt;br /&gt;
 		AllowOverride None&lt;br /&gt;
 		Order allow,deny&lt;br /&gt;
 		allow from all&lt;br /&gt;
 		RedirectMatch ^/$ /ox6/&lt;br /&gt;
                Options +FollowSymLinks +SymLinksIfOwnerMatch&lt;br /&gt;
 	&amp;lt;/Directory&amp;gt;&lt;br /&gt;
        # deflate&lt;br /&gt;
       AddOutputFilterByType DEFLATE text/html text/plain text/javascript application/javascript text/css text/xml application/xml text/x-js application/x-javascript&lt;br /&gt;
 &lt;br /&gt;
 	# pre-compressed files&lt;br /&gt;
 	AddType text/javascript .jsz&lt;br /&gt;
 	AddType text/css .cssz&lt;br /&gt;
 	AddType text/xml .xmlz&lt;br /&gt;
 	&lt;br /&gt;
 	AddEncoding x-gzip .jsz .cssz .xmlz&lt;br /&gt;
 	SetEnvIf Request_URI &amp;quot;\.(jsz|cssz|xmlz)$&amp;quot; no-gzip&lt;br /&gt;
 	&lt;br /&gt;
 	ExpiresActive On&lt;br /&gt;
 	&lt;br /&gt;
 	&amp;lt;Location /ox6&amp;gt;&lt;br /&gt;
 	        # Expires (via ExpiresByType to override global settings)&lt;br /&gt;
 	        ExpiresByType image/gif &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType image/png &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType image/jpg &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType image/jpeg &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/css &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/html &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/xml &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/javascript &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType application/x-javascript &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresDefault &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        Header append Cache-Control &amp;quot;private&amp;quot;&lt;br /&gt;
 	        Header unset Last-Modified&lt;br /&gt;
 	        Header unset Vary&lt;br /&gt;
 	        # Strip version&lt;br /&gt;
 	        RewriteEngine On&lt;br /&gt;
 	        RewriteRule v=\w+/(.+) $1 [L]&lt;br /&gt;
 	        # Turn off ETag&lt;br /&gt;
 	        Header unset ETag&lt;br /&gt;
 	        FileETag None&lt;br /&gt;
 	&amp;lt;/Location&amp;gt;&lt;br /&gt;
 	&lt;br /&gt;
 	&amp;lt;Location /ox6/ox.html&amp;gt;&lt;br /&gt;
 	        ExpiresByType text/html &amp;quot;now&amp;quot;&lt;br /&gt;
 	        ExpiresDefault &amp;quot;now&amp;quot;&lt;br /&gt;
 	        Header unset Last-Modified&lt;br /&gt;
 	        Header set Cache-Control &amp;quot;no-store, no-cache, must-revalidate, post-check=0, pre-check=0&amp;quot;&lt;br /&gt;
 	        # Turn off ETag&lt;br /&gt;
 	        Header unset ETag&lt;br /&gt;
 	        FileETag None&lt;br /&gt;
 	&amp;lt;/Location&amp;gt;&lt;br /&gt;
 	&lt;br /&gt;
 	&amp;lt;Location /ox6/index.html&amp;gt;&lt;br /&gt;
 	        ExpiresByType text/html &amp;quot;now&amp;quot;&lt;br /&gt;
 	        ExpiresDefault &amp;quot;now&amp;quot;&lt;br /&gt;
 	        Header unset Last-Modified&lt;br /&gt;
 	        Header set Cache-Control &amp;quot;no-store, no-cache, must-revalidate, post-check=0, pre-check=0&amp;quot;&lt;br /&gt;
 	        # Turn off ETag&lt;br /&gt;
 	        Header unset ETag&lt;br /&gt;
 	        FileETag None&lt;br /&gt;
 	&amp;lt;/Location&amp;gt;&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=Template:ApacheOXConf&amp;diff=6381</id>
		<title>Template:ApacheOXConf</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=Template:ApacheOXConf&amp;diff=6381"/>
		<updated>2010-08-04T08:53:51Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Configure the &#039;&#039;mod_proxy_ajp&#039;&#039; module by creating a new Apache configuration file.&lt;br /&gt;
&lt;br /&gt;
 $ vim {{{ajpconf}}}&lt;br /&gt;
&lt;br /&gt;
 {{{loadmodule}}}&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;Proxy *&amp;gt;&lt;br /&gt;
 Order deny,allow&lt;br /&gt;
 allow from all&lt;br /&gt;
 &amp;lt;/Proxy&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ProxyPass /axis2 ajp://127.0.0.1:8009/axis2 smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /ajax ajp://127.0.0.1:8009/ajax smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /servlet ajp://127.0.0.1:8009/servlet smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /infostore ajp://127.0.0.1:8009/infostore smax=0 ttl=60 retry=5&lt;br /&gt;
 ProxyPass /publications ajp://127.0.0.1:8009/publications smax=0 ttl=60 retry=5&lt;br /&gt;
 # next line is required for OXtender for Business Mobility only&lt;br /&gt;
 ProxyPass /Microsoft-Server-ActiveSync ajp://127.0.0.1:8009/Microsoft-Server-ActiveSync smax=0 ttl=60 retry=5&lt;br /&gt;
&lt;br /&gt;
Modify the default website settings to display the Open-Xchange GUI&lt;br /&gt;
&lt;br /&gt;
For versions of Open-Xchange &#039;&#039;&#039;prior&#039;&#039;&#039; to 6.18:&lt;br /&gt;
&lt;br /&gt;
 $ vim {{{apacheconf}}}&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:80&amp;gt;&lt;br /&gt;
 	ServerAdmin webmaster@localhost&lt;br /&gt;
 &lt;br /&gt;
 	DocumentRoot {{{docroot}}}&lt;br /&gt;
 &lt;br /&gt;
 	&amp;lt;Directory {{{docroot}}}&amp;gt;&lt;br /&gt;
 		AllowOverride None&lt;br /&gt;
 		Order allow,deny&lt;br /&gt;
 		allow from all&lt;br /&gt;
 		RedirectMatch ^/$ /ox6/&lt;br /&gt;
 	&amp;lt;/Directory&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 	ExpiresActive On&lt;br /&gt;
 	ExpiresByType image/gif &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType image/png &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType image/jpg &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType image/jpeg &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType text/javascript &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType text/css &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType text/html &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	ExpiresByType application/x-javascript &amp;quot;access plus 23 hours&amp;quot;&lt;br /&gt;
 	&amp;lt;Files ~ &amp;quot;\.(js|css|gif|jpe?g|png)$&amp;quot;&amp;gt;&lt;br /&gt;
 		Header append Cache-Control &amp;quot;public&amp;quot;&lt;br /&gt;
 	&amp;lt;/Files&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 	DeflateFilterNote ratio&lt;br /&gt;
 	AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/x-js application/x-javascript application/javascript&lt;br /&gt;
 	BrowserMatch ^Mozilla/4 gzip-only-text/html&lt;br /&gt;
 	BrowserMatch ^Mozilla/4\.0[678] no-gzip&lt;br /&gt;
 	BrowserMatch \bMSI[E] !no-gzip !gzip-only-text/html&lt;br /&gt;
 	Header append Vary User-Agent env=!dont-vary&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For versions of Open-Xchange &#039;&#039;&#039;starting with&#039;&#039;&#039; 6.18:&lt;br /&gt;
&lt;br /&gt;
 $ vim {{{apacheconf}}}&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;VirtualHost *:80&amp;gt;&lt;br /&gt;
 	ServerAdmin webmaster@localhost&lt;br /&gt;
 &lt;br /&gt;
 	DocumentRoot {{{docroot}}}&lt;br /&gt;
 &lt;br /&gt;
 	&amp;lt;Directory {{{docroot}}}&amp;gt;&lt;br /&gt;
 		AllowOverride None&lt;br /&gt;
 		Order allow,deny&lt;br /&gt;
 		allow from all&lt;br /&gt;
 		RedirectMatch ^/$ /ox6/&lt;br /&gt;
                Options +FollowSymLinks +SymLinksIfOwnerMatch&lt;br /&gt;
 	&amp;lt;/Directory&amp;gt;&lt;br /&gt;
        # deflate&lt;br /&gt;
       AddOutputFilterByType DEFLATE text/html text/plain text/javascript application/javascript text/css text/xml application/xml text/x-js application/x-javascript&lt;br /&gt;
 &lt;br /&gt;
 	# pre-compressed files&lt;br /&gt;
 	AddType text/javascript .jsz&lt;br /&gt;
 	AddType text/css .cssz&lt;br /&gt;
 	AddType text/xml .xmlz&lt;br /&gt;
 	&lt;br /&gt;
 	AddEncoding x-gzip .jsz .cssz .xmlz&lt;br /&gt;
 	SetEnvIf Request_URI &amp;quot;\.(jsz|cssz|xmlz)$&amp;quot; no-gzip&lt;br /&gt;
 	&lt;br /&gt;
 	ExpiresActive On&lt;br /&gt;
 	&lt;br /&gt;
 	&amp;lt;Location /ox6&amp;gt;&lt;br /&gt;
 	        # Expires (via ExpiresByType to override global settings)&lt;br /&gt;
 	        ExpiresByType image/gif &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType image/png &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType image/jpg &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType image/jpeg &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/css &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/html &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/xml &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType text/javascript &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresByType application/x-javascript &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        ExpiresDefault &amp;quot;access plus 6 months&amp;quot;&lt;br /&gt;
 	        Header append Cache-Control &amp;quot;private&amp;quot;&lt;br /&gt;
 	        Header unset Last-Modified&lt;br /&gt;
 	        Header unset Vary&lt;br /&gt;
 	        # Strip version&lt;br /&gt;
 	        RewriteEngine On&lt;br /&gt;
 	        RewriteRule v=\w+/(.+) $1 [L]&lt;br /&gt;
 	        # Turn off ETag&lt;br /&gt;
 	        Header unset ETag&lt;br /&gt;
 	        FileETag None&lt;br /&gt;
 	&amp;lt;/Location&amp;gt;&lt;br /&gt;
 	&lt;br /&gt;
 	&amp;lt;Location /ox6/ox.html&amp;gt;&lt;br /&gt;
 	        ExpiresByType text/html &amp;quot;now&amp;quot;&lt;br /&gt;
 	        ExpiresDefault &amp;quot;now&amp;quot;&lt;br /&gt;
 	        Header unset Last-Modified&lt;br /&gt;
 	        Header set Cache-Control &amp;quot;no-store, no-cache, must-revalidate, post-check=0, pre-check=0&amp;quot;&lt;br /&gt;
 	        # Turn off ETag&lt;br /&gt;
 	        Header unset ETag&lt;br /&gt;
 	        FileETag None&lt;br /&gt;
 	&amp;lt;/Location&amp;gt;&lt;br /&gt;
 	&lt;br /&gt;
 	&amp;lt;Location /ox6/index.html&amp;gt;&lt;br /&gt;
 	        ExpiresByType text/html &amp;quot;now&amp;quot;&lt;br /&gt;
 	        ExpiresDefault &amp;quot;now&amp;quot;&lt;br /&gt;
 	        Header unset Last-Modified&lt;br /&gt;
 	        Header set Cache-Control &amp;quot;no-store, no-cache, must-revalidate, post-check=0, pre-check=0&amp;quot;&lt;br /&gt;
 	        # Turn off ETag&lt;br /&gt;
 	        Header unset ETag&lt;br /&gt;
 	        FileETag None&lt;br /&gt;
 	&amp;lt;/Location&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;/VirtualHost&amp;gt;&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=OXSE4UCS_Installation_en&amp;diff=6036</id>
		<title>OXSE4UCS Installation en</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=OXSE4UCS_Installation_en&amp;diff=6036"/>
		<updated>2010-04-14T08:29:45Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: /* Updating */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Introduction= &lt;br /&gt;
The Open-Xchange Server Edition for Univention Corporate Server (OXSE4UCS) includes the groupware Open-Xchange and the integration packages for Univention Corporate Server (UCS).&lt;br /&gt;
&lt;br /&gt;
OXSE4UCS is tailored to professional users looking for a tried-and-tested solution for the management of their entire IT infrastructure including groupware or companies which already employ UCS and wish to expand their infrastructure with innovative groupware functions.&lt;br /&gt;
&lt;br /&gt;
More detailed information on UCS can be found on the Univention GmbH website: [http://www.univention.de/dokumentation.html http://www.univention.de/dokumentation.html].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Installation =&lt;br /&gt;
As OXSE4UCS is an expansion pack for the Univention Corporate Server, one or more UCS server(s) must be installed firstly. &lt;br /&gt;
&lt;br /&gt;
There are several possible different installation scenarios. In principle, OXSE4UCS can be installed on all UCS domain controller server roles: DC master, DC backup or DC slave. Installation on the server roles member server or base system is not currently possible.&lt;br /&gt;
&lt;br /&gt;
To start, the UCS systems are installed as usual with UCS 2.3. If several systems are in the UCS domain, a check must be performed that the join procedure has been run on all servers. This is usually done at the end of the installation procedure. Further information on the installation of UCS can be found in the UCS manual: [http://www.univention.de/dokumentation.html http://www.univention.de/dokumentation.html].&lt;br /&gt;
&lt;br /&gt;
The password-protected Open-Xchange repository must be integrated on all the systems where OXSE4UCS packages are to be installed. The following Univention Configuration Registry variables (UCR variables) can be used to do this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
export LDBUSER=myusername LDBPASS=secret&lt;br /&gt;
ucr set repository/online/component/ox/server=software.open-xchange.com \                                                                                                                            &lt;br /&gt;
	repository/online/component/ox/prefix=OX6/OXSEforUCS \                                                                                                                                       &lt;br /&gt;
	repository/online/component/ox/username=$LDBUSER \                                                                                                                                           &lt;br /&gt;
	repository/online/component/ox/password=$LDBPASS \                                                                                                                                           &lt;br /&gt;
	repository/online/component/ox/version=2.2,2.3 \                                                                                                                                            &lt;br /&gt;
	repository/online/component/ox=enabled \                                                                                                                                                     &lt;br /&gt;
	repository/online/component/oxseforucs/server=software.open-xchange.com \                                                                                                                    &lt;br /&gt;
	repository/online/component/oxseforucs/prefix=OX6/OXSEforUCS \                                                                                                                               &lt;br /&gt;
	repository/online/component/oxseforucs/username=$LDBUSER \                                                                                                                                   &lt;br /&gt;
	repository/online/component/oxseforucs/password=$LDBPASS \                                                                                                                                   &lt;br /&gt;
	repository/online/component/oxseforucs/version=2.2,2.3 \                                                                                                                                    &lt;br /&gt;
	repository/online/component/oxseforucs=enabled                                                                                                                                               &lt;br /&gt;
apt-get update&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The access data (&#039;&#039;myusername&#039;&#039; and &#039;&#039;secret&#039;&#039;) are created when the Open-Xchange licence is activated and must be adapted here accordingly.&lt;br /&gt;
&lt;br /&gt;
== Installation on a DC master ==&lt;br /&gt;
When installing OXSE4UCS on a DC master, only the &#039;&#039;&#039;univention-ox-meta-singleserver&#039;&#039;&#039; package requires installing. This can be performed via the Univention Management Console or on the command line:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
DEBIAN_FRONTEND=noninteractive apt-get \                                         &lt;br /&gt;
	-o DPkg::Options::=--force-confold -y --force-yes \                             &lt;br /&gt;
	install univention-ox-meta-singleserver                                                                                              &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;univention-ox-meta-singleserver&#039;&#039;&#039; package automatically installs packages for the filtering of spam and viruses at the same time. If this is not required, the &#039;&#039;&#039;univention-ox and univention-mail-cyrus-ox&#039;&#039;&#039; packages can be installed instead of the &#039;&#039;&#039;univention-ox-meta-singleserver package&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
==Installation on a dedicated DC slave==&lt;br /&gt;
In this installation scenario, the DC slave system acts as a standalone Open-Xchange groupware server. To start, the &#039;&#039;&#039;univention-ox-directory-integration&#039;&#039;&#039; package must be installed on the DC master in order to initiate integration in the UCS management system.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
DEBIAN_FRONTEND=noninteractive apt-get \                                         &lt;br /&gt;
	 -o DPkg::Options::=--force-confold -y --force-yes \                             &lt;br /&gt;
	 install univention-ox-directory-integration                                                                           &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
     &lt;br /&gt;
The &#039;&#039;&#039;univention-ox-meta-singleserver&#039;&#039;&#039; package is installed on the DC slave which is to be used as the groupware server. In addition, the join scripts must also be run following the installation:                                                     &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
DEBIAN_FRONTEND=noninteractive apt-get \                                         &lt;br /&gt;
	 -o DPkg::Options::=--force-confold -y --force-yes \                             &lt;br /&gt;
	 install univention-ox-meta-singleserver                                     &lt;br /&gt;
&lt;br /&gt;
univention-run-join-scripts&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The &#039;&#039;&#039;univention-ox-meta-singleserver&#039;&#039;&#039; package automatically installs packages for the filtering of spam and viruses. If this is not required, the &#039;&#039;&#039;univention-ox&#039;&#039;&#039; and &#039;&#039;&#039;univention-mail-cyrus-ox&#039;&#039;&#039; packages can be specified instead of the &#039;&#039;&#039;univention-ox-meta-singleserver&#039;&#039;&#039; package.&lt;br /&gt;
&lt;br /&gt;
== Installation in a distributed environment ==&lt;br /&gt;
When installing a distributed environment, integration in the UCS management system must be performed firstly by installing &#039;&#039;&#039;univention-ox-directory-integration&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
DEBIAN_FRONTEND=noninteractive apt-get \                                         &lt;br /&gt;
	 -o DPkg::Options::=--force-confold -y --force-yes \                             &lt;br /&gt;
	 install univention-ox-directory-integration                                      &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The following services can then be distributed on the other UCS systems:  &lt;br /&gt;
* IMAP server and optionally spam and virus filtering (&#039;&#039;univention-mail-cyrus-ox and optionally univention-mail-antispam-ox and univention-antivir-mail&#039;&#039;)&lt;br /&gt;
* MySQL server (&#039;&#039;mysql-server&#039;&#039;)&lt;br /&gt;
* OX instance (&#039;&#039;univention-ox&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
	&lt;br /&gt;
===MySQL server===&lt;br /&gt;
The MySQL server is installed by installing the mysql-server package.                                                     &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
apt-get install mysql-server                                                &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The configuration of the MySQL server should be set so that the MySQL service can be accessed via the external network interfaces. To do this, for example, the &#039;&#039;bind-address&#039;&#039; option can be set to &#039;&#039;0.0.0.0&#039;&#039; in the MySQL configuration file &#039;&#039;/etc/mysql/my.cnf&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
bind-address 0.0.0.0                                                             &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After the change, the MySQL service needs to be restarted:                 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/etc/init.d/mysql restart&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In addition, the OX instances must be authorized to access the database. The following gives an example, which must be adapted to the environment at hand.                                                                  &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ mysql                                                                            &lt;br /&gt;
mysql&amp;gt; GRANT ALL PRIVILEGES ON *.* TO \                                          &lt;br /&gt;
 &#039;openexchange&#039;@&#039;ox-instance1.example.com&#039; \                                       &lt;br /&gt;
 IDENTIFIED BY &#039;secret&#039;;                                                         &lt;br /&gt;
mysql&amp;gt; GRANT ALL PRIVILEGES ON *.* TO \                                          &lt;br /&gt;
 &#039;openexchange&#039;@&#039;ox-instance2.example.com&#039; \                                       &lt;br /&gt;
 IDENTIFIED BY &#039;secret&#039;;                                                         &lt;br /&gt;
mysql&amp;gt; GRANT ...                                                                 &lt;br /&gt;
mysql&amp;gt; FLUSH PRIVILEGES;                                                         &lt;br /&gt;
mysql&amp;gt; exit                           &lt;br /&gt;
$&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
                                           &lt;br /&gt;
=== Active OX instance ===&lt;br /&gt;
The &#039;&#039;&#039;univention-ox&#039;&#039;&#039; package must be installed on the active OX instance.       &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
DEBIAN_FRONTEND=noninteractive apt-get \                                         &lt;br /&gt;
	 -o DPkg::Options::=--force-confold -y --force-yes \                             &lt;br /&gt;
	 install univention-ox                                                           &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then certain environment variables must be set to ensure that the join scripts run later receive the corresponding permissions. The following gives an example, which must be adapted to the environment at hand. The variable OXDB defines the MySQL server to be used by the OX instance. The corresponding password should be saved in the variable OXDBPW. The standard IMAP server must be specified in the variable OXIMAPSERVER. Hostnames need to be specified as fully qualified domain names (FQDN). It is not possible to use IP addresses.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
export HISTIGNORE=&amp;quot;export*&amp;quot;                                                      &lt;br /&gt;
export OXDB=oxdbserver.example.com                                                 &lt;br /&gt;
export OXDBPW=&amp;quot;secret&amp;quot;                                                           &lt;br /&gt;
export OXIMAPSERVER=oximapserver.example.com                                        &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then the join scripts need to run:                                       &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
univention-run-join-scripts&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally, the environment variable OXDBPW with the password can be unset using the following command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
unset OXDBPW&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
=== IMAP server ===&lt;br /&gt;
The IMAP server is installed by installing the &#039;&#039;&#039;univention-mail-cyrus-ox&#039;&#039;&#039; package.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
DEBIAN_FRONTEND=noninteractive apt-get \                                         &lt;br /&gt;
	 -o DPkg::Options::=--force-confold -y --force-yes \                             &lt;br /&gt;
	 install univention-mail-cyrus-ox                                                                              &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The spam check via &#039;&#039;spamassassin&#039;&#039; can be installed and activated by installing the &#039;&#039;&#039;univention-mail-antispam-ox&#039;&#039;&#039; package:             &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
apt-get install univention-mail-antispam-ox                                          &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The virus check via &#039;&#039;amavis&#039;&#039; and &#039;&#039;clamav&#039;&#039; can be installed and activated by installing the u&#039;&#039;&#039;nivention-antivir-mail&#039;&#039;&#039; package.                                                            &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
apt-get install univention-antivir-mail                                      &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A check should then be performed to see whether all join scripts have been run successfully:                                                            &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
univention-run-join-scripts&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Additional passive OX instances ===&lt;br /&gt;
Firstly, the &#039;&#039;&#039;univention-ox&#039;&#039;&#039; package must also be installed on the additional passive OX instances. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
DEBIAN_FRONTEND=noninteractive apt-get \                                         &lt;br /&gt;
	 -o DPkg::Options::=--force-confold -y --force-yes \                             &lt;br /&gt;
	 install univention-ox                                                                                                                     &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then the settings can be copied from the active OX instance. This can be done, for example, using the following command:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
rsync -essh -a root@ox-instance1.example.com:/opt/open-xchange/. /opt/open-xchange/&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The FQDN of the current computer must be entered in the&#039;&#039; /opt/open-xchange/etc/groupware/usm.properties&#039;&#039; file:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
com.openexchange.usm.ox.url=ox-instance2.example.com&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The FQDN of the current computer must also be entered in the&#039;&#039; /opt/open-xchange/etc/authplugin.properties&#039;&#039; file:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
LDAP_HOST=ox-instance2.example.com&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally, the groupware must be restarted on the passive OX instance:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/etc/init.d/open-xchange-admin restart&lt;br /&gt;
/etc/init.d/open-xchange-groupware restart&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OXtender for Business Mobility ==&lt;br /&gt;
&lt;br /&gt;
The Open-Xchange OXtender for Business Mobility is an optionally available component for OXSE4UCS which enables the connection of mobile devices. The repository must be activated for it to be possible to install the corresponding packages:                                                                            &lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
export LDBUSER=ldbuser LDBPASS=lsbpass&lt;br /&gt;
ucr set repository/online/component/oxmobility/server=software.open-xchange.com \&lt;br /&gt;
	repository/online/component/oxmobility/prefix=OX6/OXSEforUCS \&lt;br /&gt;
	repository/online/component/oxmobility/username=$LDBUSER \&lt;br /&gt;
	repository/online/component/oxmobility/password=$LDBPASS \&lt;br /&gt;
	repository/online/component/oxmobility/version=2.2,2.3 \&lt;br /&gt;
	repository/online/component/oxmobility=enabled&lt;br /&gt;
&lt;br /&gt;
apt-get update&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Installing the &#039;&#039;&#039;univention-ox-usm-ox&#039;&#039;&#039; package installs the Oxtender for Business Mobility on the OXSE4UCS system.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
apt-get install &#039;&#039;&#039;univention-ox-usm-ox&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If the target system is neither a DC master nor a DC backup system, the &#039;&#039;&#039;univention-ox-usm-udm&#039;&#039;&#039; package should also be installed on the DC master.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
apt-get install &#039;&#039;&#039;univention-ox-usm-udm&#039;&#039;&#039;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Updating=&lt;br /&gt;
To update a UCS 2.2 system with OXSE4UCS 6.12 or 6.14 to UCS 2.3, the following variables must be set before the update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
ucr set repository/online/component/ox/version=2.2,2.3 \&lt;br /&gt;
        repository/online/component/oxseforucs/version=2.2,2.3&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The system can then be updated as usual for UCS using the &#039;&#039;univention-updater net&#039;&#039; command.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Don&#039;t update the system with the &#039;&#039;UMC module Online Update&#039;&#039;, this could cause an unavailability of the UMC!!!&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=Administration=&lt;br /&gt;
	&lt;br /&gt;
== User and group management ==&lt;br /&gt;
New users and groups can be created using the Univention Directory Manager (UDM). The UDM can be accessed on the DC master via a web browser at https://&amp;lt;IP-Adresse des DC Master&amp;gt;/udm/. It is possible to log in as the Administrator user using the password specified during the installation.&lt;br /&gt;
&lt;br /&gt;
When creating a user, the &#039;&#039;&#039;open-xchange groupware account&#039;&#039;&#039; user template should be selected. This preselects all Open-Xchange specific settings.&lt;br /&gt;
&lt;br /&gt;
== System messages ==&lt;br /&gt;
The &#039;&#039;mail/alias/root&#039;&#039; UCS variable must be set so that system messages can be delivered. To do this, either a new account can be created or, alternatively, oxadmin@DOMAIN is provided for this purpose:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
ucr set mail/alias/root=oxadmin@example.com&lt;br /&gt;
newaliases&lt;br /&gt;
/etc/init.d/postfix reload&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is possible to log in as the oxadmin user in the Open-Xchange web interface using the password from the &#039;&#039;/etc/ox-secrets/context10.secret&#039;&#039; file.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: OX6]]&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=OX6:OXtender_for_Business_Mobility_Installation_Guide&amp;diff=4719</id>
		<title>OX6:OXtender for Business Mobility Installation Guide</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=OX6:OXtender_for_Business_Mobility_Installation_Guide&amp;diff=4719"/>
		<updated>2009-09-01T13:22:30Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: /* Open-Xchange configuration */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Installation of the OXtender for Business Mobility =&lt;br /&gt;
&lt;br /&gt;
== Description ==&lt;br /&gt;
&lt;br /&gt;
The OXtender for Business Mobility is an extension to the Open-Xchange Server enabling Exchange ActiveSync capabilities. ActiveSync is a widespread proprietary protocol developed by Microsoft which allows mobile devices to communicate with groupware servers or desktop computers. Client-side implementations of ActiveSync are available for Windows Mobile, Apple iPhone, Symbian, BlackBerry and Android devices. The protocol covers a very large amount of business smartphones and handheld computers. Since Open-Xchange is able to communicate through native ActiveSync, there are no third party clients required on compatible devices. Integration to the native applications of the specific device is more seamless than with any other synchronization technology. ActiveSync supports synchronization of E-Mail, appointments, contacts and tasks by polling, manual sync or push.&lt;br /&gt;
&lt;br /&gt;
== Components ==&lt;br /&gt;
&lt;br /&gt;
With the OXtender for Business Mobility, Open-Xchange also introduces the Universal Synchronization Module (USM). This module provides a framework for synchronization protocols such as Exchange ActiveSync (EAS) or other services building on this foundation. USM acts as a layer between the Open-Xchange HTTP API and the synchronization protocol. It handles synchronization specific tasks like conflict management.&lt;br /&gt;
The synchronization stack (USM) and protocol implementation (EAS) are shipped as OSGi bundles and run as a plug-in of an Open-Xchange instance.&lt;br /&gt;
&lt;br /&gt;
== Component Overview ==&lt;br /&gt;
USM, EAS and OX work together as components. This is a general outline about how these components interact.&lt;br /&gt;
&lt;br /&gt;
When the device initiates a synchronization through ActiveSync, it contacts the webserver using the URL /Microsoft-Server-ActiveSync via HTTP/s. This URL is forwarded to the Open-Xchange application server where the corresponding servlet is offered by the EAS component. The EAS component then uses USM to initiate a connection to the OX HTTP API and exchanges groupware data. In all cases, USM works as an client to the Open-Xchange HTTP API. It also uses some database tables which are accessed through the Open-Xchange SQL interface to store metadata like synchronization status. The same component stack is used to transport groupware data back to the device.&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
&lt;br /&gt;
Since the OXtender for Business Mobility is a server plug-in based on the OSGi Framework it can be added to an existing Open-Xchange installation very easily. Open-Xchange Server 6.10 or later is required to operate this extension. The OXtender for Business Mobility uses the resources and services offered by the Open-Xchange server, no additional software or configuration is required.&lt;br /&gt;
&lt;br /&gt;
* [[Open-Xchange_Installation_Guide_for_Debian_4.0 | Debian 4.0 (Etch)]]&lt;br /&gt;
* [[Open-Xchange_Installation_Guide_for_Debian_5.0 | Debian 5.0 (Lenny)]]&lt;br /&gt;
* [[Open-Xchange_Installation_Guide_for_SLES10 | SLES10]]&lt;br /&gt;
* [[Open-Xchange_Installation_Guide_for_SLES11 | SLES11]]&lt;br /&gt;
* [[Open-Xchange_Installation_Guide_for_RHEL5 | RHEL5]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Please Note:&#039;&#039;&#039; To get in favor of the latest minor features and bugfixes, you need to have a valid license.  The article [[UpdatingOXPackages | Updating OX-Packages]] explains how that can be done.&lt;br /&gt;
&lt;br /&gt;
== Upgrade from a previous version ==&lt;br /&gt;
It is very important to know that updating your installation requires a bit more than just installing the latest packages. Some additional tasks need to be executed by the administrator to successfully upgrade the USM installation. &lt;br /&gt;
&lt;br /&gt;
Please follow these steps to do so:&lt;br /&gt;
&lt;br /&gt;
After downloading the packages, they can be installed using the operating systems package manager. For example:&lt;br /&gt;
&lt;br /&gt;
 dpkg -i open-xchange-usm_6.10.0.0-6_all.deb&lt;br /&gt;
&lt;br /&gt;
This will extract the package and configure the integration to the Open-Xchange server.&lt;br /&gt;
&lt;br /&gt;
Please make sure that if you have chosen to not overwrite the existing configuration file during the package installation process, you need to merge the new settings in the newly created /opt/open-xchange/etc/groupware/usm.properties.dpkg-new file to the existing file, or just overwrite the old one with the new one and redo your configuration settings.&lt;br /&gt;
&lt;br /&gt;
Now the Open-Xchange Groupware daemon needs to be shut down:&lt;br /&gt;
&lt;br /&gt;
 /etc/init.d/open-xchange-groupware stop&lt;br /&gt;
&lt;br /&gt;
The next step is to purge some database tables, as the USM installer is not able to do this step on his own at the moment. To do so please execute the following mysql commands. Afterwards you need to re-run the updatetasks once again. This is done by resetting the database version of the OX database which will trigger all relevant updatetasks. Note that the database name for Open-Xchange Server mentioned in this example can be different, depending on your setup.&lt;br /&gt;
&lt;br /&gt;
 mysql&amp;gt; USE oxdatabase_6;&lt;br /&gt;
 mysql&amp;gt; drop table USMSessionFields;&lt;br /&gt;
 mysql&amp;gt; drop table usmSessionIdSequenceTable;&lt;br /&gt;
 mysql&amp;gt; drop table USMDataStorage;&lt;br /&gt;
 mysql&amp;gt; drop table usmIdMapping;&lt;br /&gt;
 mysql&amp;gt; drop table usmIdSequenceTable;&lt;br /&gt;
 mysql&amp;gt; drop table easUIDMapping;&lt;br /&gt;
 mysql&amp;gt; drop table USMSession;&lt;br /&gt;
 mysql&amp;gt; UPDATE version SET version=33;&lt;br /&gt;
&lt;br /&gt;
Finally the Open-Xchange Groupware daemon needs to started again:&lt;br /&gt;
&lt;br /&gt;
 /etc/init.d/open-xchange-groupware start&lt;br /&gt;
&lt;br /&gt;
== New Installation ==&lt;br /&gt;
&lt;br /&gt;
After downloading the packages, they can be installed using the operating systems package manager. For example:&lt;br /&gt;
&lt;br /&gt;
 dpkg -i open-xchange-usm_6.10.0.0-6_all.deb&lt;br /&gt;
&lt;br /&gt;
This will extract the package and configure the integration to the Open-Xchange server.&lt;br /&gt;
&lt;br /&gt;
Since the USM package provides some additional database tables, it is required to re-run several updatetasks after the installation. This is done by resetting the database version of the OX database which will trigger all relevant updatetasks. Note that the database name for Open-Xchange Server mentioned in this example can be different, depending on your setup.&lt;br /&gt;
&lt;br /&gt;
 mysql&amp;gt; USE oxdatabase_6;&lt;br /&gt;
 mysql&amp;gt; UPDATE version SET version=33;&lt;br /&gt;
&lt;br /&gt;
Please restart the Open-Xchange Server after adding this plug-in and applying the database modification. On the first login of a user after the restart, all required database tables will be created.&lt;br /&gt;
&lt;br /&gt;
== Configuration ==&lt;br /&gt;
=== Open-Xchange configuration ===&lt;br /&gt;
The configuration for USM and the EAS protocol can be found in the two configuration files:&lt;br /&gt;
 /opt/open-xchange/etc/groupware/usm.properties&lt;br /&gt;
 /opt/open-xchange/etc/groupware/eas.properties&lt;br /&gt;
&lt;br /&gt;
Make sure that the following two parameters are properly set:&lt;br /&gt;
&lt;br /&gt;
In usm.properties&lt;br /&gt;
 com.openexchange.usm.access_check_module=syncml&lt;br /&gt;
&lt;br /&gt;
and in eas.properties&lt;br /&gt;
 com.openexchange.usm.eas.access_check=false&lt;br /&gt;
&lt;br /&gt;
Documentation about the configuration parameters can be found inside the configuration file. After the installation is complete, the Open-Xchange groupware needs to be restarted, after that USM and EAS services are available.&lt;br /&gt;
&lt;br /&gt;
=== Apache Configuration ===&lt;br /&gt;
Mobile devices supporting ActiveSync use a special URL to communicate with the ActiveSync enabled server. This URL needs to be forwarded to the Open-Xchange ActiveSync servlet. When using Apache 2 and mod_proxy_ajp, this servlet can simply be added to the webservers proxy_ajp configuration:&lt;br /&gt;
&lt;br /&gt;
 ProxyPass /Microsoft-Server-ActiveSync ajp://127.0.0.1:8009/Microsoft-Server-ActiveSync smax=0 ttl=60 retry=5&lt;br /&gt;
&lt;br /&gt;
The example assumes that the Open-Xchange server is running on the same machine like the webserver. Please refer the Open-Xchange administrator documentation for more information about Apache configuration.&lt;br /&gt;
&lt;br /&gt;
[[Category: OX6]]&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=AppSuite:Open-Xchange_Plugin_Overview&amp;diff=3752</id>
		<title>AppSuite:Open-Xchange Plugin Overview</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=AppSuite:Open-Xchange_Plugin_Overview&amp;diff=3752"/>
		<updated>2009-05-13T13:24:40Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: /* Core Plugins */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Overview of available Open-Xchange Plugins =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Core Plugins ==&lt;br /&gt;
&lt;br /&gt;
These plugins are part of the Open-Xchange Server Core platform.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!style=&amp;quot;width:230px&amp;quot; align=&amp;quot;left&amp;quot; |Name&lt;br /&gt;
!style=&amp;quot;width:230px&amp;quot; align=&amp;quot;left&amp;quot; |Description&lt;br /&gt;
!align=&amp;quot;left&amp;quot; |Documentation&lt;br /&gt;
|-&lt;br /&gt;
|[http://software.open-xchange.com/OX6/stable/ open-xchange-authentication-ldap]&lt;br /&gt;
|Authentication against LDAP server&lt;br /&gt;
|[[Authentication_Plugin_description|Authentication plugin description]]&lt;br /&gt;
|-&lt;br /&gt;
|[http://software.open-xchange.com/OX6/stable/ open-xchange-authentication-imap]&lt;br /&gt;
|Authentication against IMAP server&lt;br /&gt;
|[[Authentication_Plugin_description|Authentication plugin description]]&lt;br /&gt;
|-&lt;br /&gt;
|[http://software.open-xchange.com/OX6/stable/ open-xchange-contextrestore]&lt;br /&gt;
|Plugin to restore one or more contexts from a complete database dump&lt;br /&gt;
|http://software.open-xchange.com/OX6/doc/Context_Restore_Documentation.pdf&lt;br /&gt;
|-&lt;br /&gt;
|[http://software.open-xchange.com/OX6/stable/ open-xchange-configjump-generic]&lt;br /&gt;
|Integrate custom configuration website&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|[http://software.open-xchange.com/OX6/stable/ open-xchange-dataretention / open-xchange-dataretention-csv]&lt;br /&gt;
|Module to be used for data retention (german: Vorratsdatenspeicherung)&lt;br /&gt;
|open-xchange-dataretention-csv is an example implementation of the data retention service&lt;br /&gt;
|-&lt;br /&gt;
|[http://software.open-xchange.com/OX6/stable/ open-xchange-commons-logging-log4j / open-xchange-log4j]&lt;br /&gt;
|These packages must be installed when Open-Xchange should use syslog&lt;br /&gt;
|[[Syslog_Configuration|Syslog configuration]]&lt;br /&gt;
|-&lt;br /&gt;
|open-xchange-contacts-ldap&lt;br /&gt;
|Integrate LDAP address book into Open-Xchange public folder tree&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Additional Plugins ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!style=&amp;quot;width:230px&amp;quot; align=&amp;quot;left&amp;quot; |Name&lt;br /&gt;
!style=&amp;quot;width:230px&amp;quot; align=&amp;quot;left&amp;quot; |Description&lt;br /&gt;
!align=&amp;quot;left&amp;quot; |Documentation&lt;br /&gt;
|-&lt;br /&gt;
|[http://software.open-xchange.com/OX6/unsupported/stable/extensions/ open-xchange-upsell-generic]&lt;br /&gt;
|Basic examples to implement an up sell layer in Open-Xchange&lt;br /&gt;
|[[Upsell_Layer_Package|Upsell package description]]&lt;br /&gt;
|-&lt;br /&gt;
|[http://software.open-xchange.com/OX6/unsupported/stable/extensions/ open-xchange-easylogin]&lt;br /&gt;
|Example package to implement the EasyLogin mechanism&lt;br /&gt;
|[[Open-Xchange_servlet_for_external_login_masks|EasyLogin description]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Custom Plugins ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
!style=&amp;quot;width:150px&amp;quot; align=&amp;quot;left&amp;quot; |Name&lt;br /&gt;
!align=&amp;quot;left&amp;quot; |Description&lt;br /&gt;
|-&lt;br /&gt;
|MAL&lt;br /&gt;
|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.&lt;br /&gt;
|-&lt;br /&gt;
|Upsell&lt;br /&gt;
|If the example upsell plugin does not fit your needs or has some missing functionality, do not hesitate to contact us.&lt;br /&gt;
|-&lt;br /&gt;
|Spam&lt;br /&gt;
|It&#039;s possible to integrate the built in mark as SPAM/HAM functionality into almost any solution.&lt;br /&gt;
|-&lt;br /&gt;
|Authentication&lt;br /&gt;
|Authentication can be done against every system that allows to specify a username/password combination.&lt;br /&gt;
|-&lt;br /&gt;
|Corporate Integration: EasyLogin&lt;br /&gt;
|The EasyLogin mechanism allows to login into Open-Xchange from other applications without specifying username and password again.&lt;br /&gt;
|-&lt;br /&gt;
|Corporate Integration: ConfigJump&lt;br /&gt;
|Integrate your own configuration application in the Open-Xchange settings tree.&lt;br /&gt;
|-&lt;br /&gt;
|UI Customization&lt;br /&gt;
|A lot of customization can be done in the Open-Xchange UI. Starting from themes to the integration of custom modules and functions.&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=File:Mwagner.jpg&amp;diff=1470</id>
		<title>File:Mwagner.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=File:Mwagner.jpg&amp;diff=1470"/>
		<updated>2008-04-01T05:09:10Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: Next try...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Next try...&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=File:MWagner.jpg&amp;diff=1465</id>
		<title>File:MWagner.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=File:MWagner.jpg&amp;diff=1465"/>
		<updated>2008-03-31T06:14:52Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
	<entry>
		<id>https://wiki.open-xchange.com/wiki/index.php?title=File:Markusw.jpg&amp;diff=1464</id>
		<title>File:Markusw.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.open-xchange.com/wiki/index.php?title=File:Markusw.jpg&amp;diff=1464"/>
		<updated>2008-03-31T06:13:38Z</updated>

		<summary type="html">&lt;p&gt;Markus.wagner: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Markus.wagner</name></author>
	</entry>
</feed>