Open-Xchange - User contributions [en]

Template:Main Page Quickinstall

2012-03-01T13:23:35Z

217.7.151.106:

__NOTOC__
{{#switch: {{{1}}}
| HESE=

{{=}} Quick Installation Guide (supported packages) {{=}}

To download and install the software, please use the following Installation Guides:

* [[Open-Xchange_Installation_Guide_for_Debian_5.0|Download and Installation Guide for Debian GNU/Linux 5.0 (Lenny)]]
* [[Open-Xchange_Installation_Guide_for_Debian_6.0|Download and Installation Guide for Debian GNU/Linux 6.0 (Squeeze)]]
* [[Open-Xchange_Installation_Guide_for_SLES11|Download and Installation Guide for SUSE Linux Enterprise Server 11]]
* [[Open-Xchange_Installation_Guide_for_RHEL5|Download and Installation Guide for RedHat Enterprise Linux 5]]
* [[Open-Xchange_Installation_Guide_for_RHEL6|Download and Installation Guide for RedHat Enterprise Linux 6]]
* [[Open-Xchange Installation Guide for CentOS 5‎‎|Download and Installation Guide for CentOS 5]]
* [[OXSE4UCS_Installation_en|Download and Installation Guide for Univention Corporate Server (SE for UCS)]]
* [[Installing_OX_Language_Packages|Installing Open-Xchange Language Packages]]
* [http://software.open-xchange.com/OX6/stable/ Software repository]

{{=}} Hosting Edition deployment tutorials {{=}}

A complete guide of necessary tasks with a hardware and setup recommendation for different Open-Xchange Hosting environments:

* [[OX_HE_Tutorial_10K|Hosting Edition deployment tutorial for up to 10.000 Users]]
* [[OX_HE_Tutorial_100K|Hosting Edition deployment tutorial for up to 100.000 Users]]
* [[OX_HE_Tutorial_1M|Hosting Edition deployment tutorial for up to 1.000.000 Users]]

{{=}} Installing the latest Updates {{=}}

To get in favor of the latest minor features and bugfixes, you need to have a valid license. The article [[UpdatingOXPackages|Updating Open-Xchange Server packages]] packages explains how that can be done.

{{=}}Upsell functionality{{=}}

The Open-xchange Upsell packages provide the ability to show advertisements to an Open-Xchange user who is using a free of charge package like "Webmail" or "PIM". It gives hosting companies the possibility to take advantage of selling premium OX services (Mobility OXtender etc.) via "in app" technology.

[[Upsell|Upsell Layer installation and configuration]] 
[[OX_Permission_Level | OX Permission Level Matrix]]

{{=}}Reporting Tool (Mandatory for Maintenance){{=}}

To receive maintenance in the future, the installation of the Open-Xchange Reporting Tool is mandatory. It documents the current state of your system installation. Furthermore, the tool runs a validity check for your current maintenance. Based on the reported detail information Open-Xchange will be able to improve its own support and maintenance offerings for you. This article explains how that can be done:

* Configuring [[OXReportClient|open-xchange-report-client]]

{{=}}OXtender 2 for Microsoft Outlook{{=}}

The Open-Xchange OXtender 2 for Microsoft Outlook® lets users keep their familiar Outlook client when their organization moves to Open-Xchange Server. Users feel right at home working with their Outlook interface while in the background the OXtender synchronizes E-Mails, Calendar, Contacts and Tasks, along with Public, Shared and System Folders. Real-time synchronization enables fast response times, so teams can work as efficiently as possible.

* [[OXtender_2_for_Microsoft_Outlook|Installation & Configuration of the Open-Xchange OXtender 2 for Microsoft Outlook]]

{{=}}Microsoft Outlook® Uploader{{=}}

Open-Xchange provides Open-Xchange Microsoft Outlook® Uploader (short: OXUploader), a migration tool to export data from Microsoft Outlook® or from a Microsoft Exchange Server® to the Open-Xchange Server.

* [[OX_Outlook_Uploader|Download & Installation of the Open-Xchange Microsoft Outlook® Uploader]]

{{=}}OXtender for Business Mobility (ActiveSync) {{=}}

OXtender for Business Mobility enables to securely manage emails, contacts, calendar and tasks always synchronized with Open-Xchange – Based on Microsoft Exchange Active Sync (EAS) standard.
* [[OXtender_for_Business_Mobility|Installation and information of the OXtender for Business Mobility]]

{{=}}Client Updater (OXtender for MS Outlook){{=}}

The Open-Xchange Updater is a software tool by Open-Xchange that installs the latest version of Open-Xchange client software on computers running Windows. The Updater automatically informs users of new updates of e.g. the Open-Xchange OXtender for Microsoft Outlook.

* [[Open-Xchange_Updater|Installation of the Open-Xchange Client Updater]]

{{=}}Mac OS X synchronization based on CalDAV and CardDAV protocols{{=}}

Integration with Mac OS X makes Open-Xchange e-mails, appointments and contacts available to end users through their native Mac applications -- Mail, iCal and Address Book. Even without a connection to the Internet, users can continue to work without interruption. The new synchronization protocols are available for Open-Xchange Server Edition and Open-Xchange Hosting Edition.

* [[SetUpMacCalCardDAVClients| Configuration CalDAV and CardDAV with Open-Xchange]]
* [[Caldav_carddav_Bundles| Installation CalDAV and CardDAV with Open-Xchange]]

{{=}}Open-Xchange Mobile Web App{{=}}

Open-Xchange Mobile Web App, which lets you access data from Open-Xchange Server 6 with your smartphone running a webkit based browser like the iPhone or Android devices. Open-Xchange Mobile Web App offers online and offline access to appointments, contacts and mails on the road using your smartphone.

* [[OX_Mobile_Web_App|Installation of the Open-Xchange Mobile Web App]]

{{=}}OXtender for SyncML{{=}}

The Open-Xchange OXtender for SyncML extends the power of Smart Collaboration™ to users of hundreds of types of mobile devices offered by major device manufacturers. SyncML enabled devices can update user personal contact information wirelessly. The OXtender for SyncML is a server-side plugin based on the Open-Xchange USM synchronization framework. Synchronizing contacts from the personal contact folder is supported.

* [[OXtender_for_SyncML|Installation/Server- and Client Configuration of the OXtender for SyncML]]

{{=}}OXtender for cPanel{{=}}

Integration of Open-Xchange with cPanel makes deployment and billing of Open-Xchange simple for service providers. Web hosters can offer Open-Xchange to their shared-hosting customers as well as to users of Virtual Private Servers - just by installing a software package together with cPanel.

* [[Open-Xchange_cPanel_Installation|Install Open-Xchange OXtender for cPanel on WHM/cPanel]]

{{=}} Installation Requirements {{=}}

* [[SupportedIMAPServers|Supported IMAP servers]]
* [[SupportedJavaRuntimes|Supported Java runtimes]]
* [[SupportedWebBrowsers|Supported Web browsers]]
* [[Importing_OX_Buildkey|Importing the Open-Xchange public buildkey]]

| CE=

Open-Xchange Community Edition differs from other Open-Xchange
editions in not being supported by Open-Xchange. It has the very same
functionality like all other editions and shares the same code base.

When you choose to install packages for one of the maintained
platforms as listed below, you can later buy maintenance and a support
contract without migrating any data.

Products like OXtender for MS Outlook and OXtender for Mac OS can only
be purchased and supported in combination with a maintenance contract
and thus only with products like HE, SE, SE for UCS or ASE.

= Maintained packages (Support contract available) =

To download and install the software, please use the following Installation Guides:

* [[Open-Xchange_Installation_Guide_for_Debian_5.0|Download and Installation Guide for Debian GNU/Linux 5.0 (Lenny)]]
* [[Open-Xchange_Installation_Guide_for_Debian_6.0|Download and Installation Guide for Debian GNU/Linux 6.0 (Squeeze)]]
* [[Open-Xchange_Installation_Guide_for_SLES11|Download and Installation Guide for SUSE Linux Enterprise Server 11]]
* [[Open-Xchange_Installation_Guide_for_RHEL5|Download and Installation Guide for RedHat Enterprise Linux 5]]
* [[Open-Xchange_Installation_Guide_for_RHEL6|Download and Installation Guide for RedHat Enterprise Linux 6]]
* [[Open-Xchange Installation Guide for CentOS 5‎‎|Download and Installation Guide for CentOS 5]]
* [[OXSE4UCS_Installation_en|Download and Installation Guide for Univention Corporate Server (SE for UCS)]]
* [[Installing_OX_Language_Packages|Installing Open-Xchange Language Packages]]
* [http://software.open-xchange.com/OX6/stable/ Software repository]

= Unsupported packages =
* [[CommunitySoftwareRepositories|About Community Packages]]

* [[Open-Xchange_Installation_Guide_for_Ubuntu_10.04|Installation Guide for Ubuntu 10.04]]
* [[Open-Xchange_Installation_Guide_for_Ubuntu_10.10|Installation Guide for Ubuntu 10.10]]
* [[Open-Xchange_Installation_Guide_for_Fedora_9|Installation Guide
for Fedora 9]]
* [[Open-Xchange_Installation_Guide_for_openSUSE_11.0|Installation Guide for openSUSE 11.0]]
* [http://download.opensuse.org/repositories/server:/OX:/ox6/ Software repository].

= Update from old packages =

* [[UpdatingOXPackages|Updating Open-Xchange Server packages]]

= Installation Requirements =
* [[SupportedIMAPServers|Supported IMAP servers]]
* [[SupportedJavaRuntimes|Supported Java runtimes]]
* [[SupportedWebBrowsers|Supported Web browsers]]
* [[Importing_OX_Buildkey|Importing the Open-Xchange public buildkey]]

| AE=

{{=}}Advanced Server Edition (ASE) {{=}}

Open-Xchange Advanced Server Edition is a multi-tier, small footprint solution that integrates seamlessly into customers architectures enabling smooth start of operation based on flexible services with Enterprise Linux distribution, identity management and Infrastructure management.

* [[OXASE_Installation_en|Download and Install Open-Xchange Advanced Server Edition (English)]]

{{=}}Setup for synchronisation of Active Directory objects to OXASE {{=}}
* [[UCS_AD_Connector_en|Setup]]

=OXtender 2 for Microsoft Outlook=

The Open-Xchange OXtender 2 for Microsoft Outlook® lets users keep their familiar Outlook client when their organization moves to Open-Xchange Server. Users feel right at home working with their Outlook interface while in the background the OXtender synchronizes E-Mails, Calendar, Contacts and Tasks, along with Public, Shared and System Folders. Real-time synchronization enables fast response times, so teams can work as efficiently as possible.

* [[OXtender_2_for_Microsoft_Outlook|Installation & Configuration of the Open-Xchange OXtender 2 for Microsoft Outlook]]

=Microsoft Outlook® Uploader=

Open-Xchange provides Open-Xchange Microsoft Outlook® Uploader (short: OXUploader), a migration tool to export data from Microsoft Outlook® or from a Microsoft Exchange Server® to the Open-Xchange Server.

* [[OX_Outlook_Uploader|Download & Installation of the Open-Xchange Microsoft Outlook® Uploader]]

= OXtender for Business Mobility (ActiveSync) =

OXtender for Business Mobility enables to securely manage emails, contacts, calendar and tasks always synchronized with Open-Xchange – Based on Microsoft Exchange Active Sync (EAS) standard.

* [[OXtender_for_Business_Mobility|Installation and information of the OXtender for Business Mobility]]

= Client Updater (OXtender for MS Outlook) =

The Open-Xchange Updater is a software tool by Open-Xchange that installs the latest version of Open-Xchange client software on computers running Windows. The Updater automatically informs users of new updates of e.g. the Open-Xchange OXtender for Microsoft Outlook.

* [[Open-Xchange_Updater|Installation of the Open-Xchange Client Updater]]
| default=
}}

ProfServProjects

2012-01-25T08:23:32Z

217.7.151.106: /* Initialization Phase / Pre-Sales */

This article gives a detailed overview of the process to run an Open-Xchange implementation project together with the OX Professional Services team.

The phases and decisions are documented here, as well as the documents and tools used to accompany this process.

The following diagram gives a birds-eye view of the whole process: 
<div style="min-width 840px;">[[File:birdseye7.png]]</div> 

=Initialization Phase / Pre-Sales=

The first phase of the project, the "Initialization Phase" is typically the pre-sales cycle to evaluate the product and to evaluate the feasibility of the project as well as to identify potentially necessary customization to integrate into every environment.

At the end of this phase, the results of the evaluation are used to provide a detailed offer and to make the final "Go" / "No-Go" decision.

Typical activities and topics in this phase are as follows:

*User Interface Demo and Evaluation (webcast or on-site)
* Architecture Overview
** Integration into existing customer systems
** Sizing, Scalability
** Available APIs, standards and programming languages
** Branding / Whitelabeling
* Proof Of Concept Installation (POC) in target environment
* Technology Transfer / Workshop
** Using the agenda given below
** Evaluate existing environment (mailsystem, loadbalancer, storage, provisioning, ..)
** Results in Customer Implementation Concept
* Request For Information (RFI) / Request For Quotation (RFQ)

==Tools and Results in Initalization Phase==
* [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/21816/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Workshop Agenda]

This document containing the "Workshop Agenda" is used to prepare for the initial technical workshop. The goal of the workshop is to get a common understanding of all existing infrastructure systems and the capabilities of the OX product. The preparation document lists all persons/roles, who should attend the workshop as well as the topics, which will be covered within a typical evaluation workshop.

*[https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/22276/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Project Charter]

The "Project Charter" is the one central document, outlining the whole project. It is used to document the common understanding of the whole project to ensure, having the same understanding in all projects parties.

It starts with the motivation to run the project and contains all goals and the scope of the whole project. Stakeholders on both sides are defined as well as detailed responsibilities and milestones to measure progress. Also further organization of the project is specified including details about documentation, reporting and communication. It will be maintained throughout the project-timeline.

All efforts, which are already known at this stage of the project are listed in this document.

*[https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/21758/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Customer Implementation Concept]

This "Customer Implementation Concept" outlines all results from the technical evaluation until this point in time, mainly resulting from the workshop. It contains all results from the initialization phase, as well as all already known topics, to be discussed and analyzed in the future.

This is a "living document" as well in that it is updated during the project to reflect the current state of affairs.

* [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/22277/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Basic Statement Of Work]

The "Basic Statement Of Work (SOW)" describes and offers all OX PS implementation efforts already known and agreed upon at this point in time.

=Concept Phase=

The "Concept Phase" is the first one, after the joint project has started formally. During this phase, the basic implementation like installation of hardware starts, but most important, all necessary detailed concepts are created and finalized.

During this phase it is decided what exactly will be done by whom and when.

The Customer Implementation Concept from the Initialization phase will be finalized. All tasks to be done by OX PS are documented and offered in (seperate) SOWs.

Typical activities and topics in this phase are as follows:

* Detail-Workshops for all complex integration topics, to finalize the Concept paper
* Time Planing and Milestones will be agreed on
* Resources are planned to define the responsibilities for each task
* Budget and associated costs are fixed
* Quality Management and Risk Management starts in this phase

==Tools in Concept Phase==

* The "Implementation Concept" from the first phase will be enhanced and is used as a living document to contain all known and discussed technical details. This document will be used throughout the whole project. So it is a very important source of information not only for implementation, also post-implementation as part of the system documentation.

* A [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/52878/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Requirements Checklist] will be introduced in this phase, which is used to track all open topics and issues. All closed topics will be moved to an "archive" to obtain a complete documentation of all project topics, as well as to be used for approval testing.

* WorkBreakdownStructure [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/50871/current?secret=30e01261e422f9ec9b0af51b0d3319e2 mindmeister.com-format] [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/50873/current?secret=30e01261e422f9ec9b0af51b0d3319e2 pdf] [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/50872/current?secret=30e01261e422f9ec9b0af51b0d3319e2 rtf]

The "Work Breakdown Structure" is a tree-like view on all known topics "work items" known at the recent point in time. A template, based on OX project experience, is used during the workshops as starting point. Then the WBS will be enhanced in all workshops and discussions to build a tree, which is as complete, as possible.

* SOWs will be created for all topics, when implementation or customization is requested from the OX team. Each topic will be tracked in on separate SOW, to keep the process as transparent as possible.

=Implementation Phase=

Within the "Implementation Phase" everything that was planned before will be realized, like the name says. However, in reality there always is an overlap in Concept Phase and Implementation Phase.

Typical activities and topics in this phase are as follows:

* Installation / Configuration of the live-system
* Integration into infrastructure
* Customization, Branding, Theming
* Documentation
* Quality Management
* Change Management
* Training (Admin, Support, Sales)

==Tools in the Implementation Phase==

Typically all tools from the former phase will be used to track the implementation process.

=Approval Phase=

During this last phase in the project, everything that was realized will be verified and approved against the documented requirements. After approval the launch process start, recommended in several steps, beginning with a soft-launch.

Typical activities and topics in this phase are as follows:

* Testing, manually and automated
* System- and Configuration Review
* Soft-Launch
* Migration
* Training (Admin, Support, Sales)* Handover to Support
* Documentation including architecture, setup, test-accounts, etc.
* Project retrospective
* Handover to Open-Xchange support

==Tools==

* [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/52878/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Requirements Checklist] ... This list produced during the concept phase contains agreed upon and done items. These will be used in this phase to verify the correct implementation of all topics.

ProfServProjects

2012-01-25T08:23:11Z

217.7.151.106: /* Tools and Results in Initalization Phase */

This article gives a detailed overview of the process to run an Open-Xchange implementation project together with the OX Professional Services team.

The phases and decisions are documented here, as well as the documents and tools used to accompany this process.

The following diagram gives a birds-eye view of the whole process: 
<div style="min-width 840px;">[[File:birdseye7.png]]</div> 

=Initialization Phase / Pre-Sales=

The first phase of the project, the "Initialization Phase" is typically the pre-sales cycle to evaluate the product and to evaluate the feasibility of the project as well as to identify potentially necessary customization to integrate into every environment.

At the end of this this phase, the results of the evaluation are used to provide a detailed offer and to make the final "Go" / "No-Go" decision.

Typical activities and topics in this phase are as follows:

*User Interface Demo and Evaluation (webcast or on-site)
* Architecture Overview
** Integration into existing customer systems
** Sizing, Scalability
** Available APIs, standards and programming languages
** Branding / Whitelabeling
* Proof Of Concept Installation (POC) in target environment
* Technology Transfer / Workshop
** Using the agenda given below
** Evaluate existing environment (mailsystem, loadbalancer, storage, provisioning, ..)
** Results in Customer Implementation Concept
* Request For Information (RFI) / Request For Quotation (RFQ)

==Tools and Results in Initalization Phase==
* [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/21816/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Workshop Agenda]

This document containing the "Workshop Agenda" is used to prepare for the initial technical workshop. The goal of the workshop is to get a common understanding of all existing infrastructure systems and the capabilities of the OX product. The preparation document lists all persons/roles, who should attend the workshop as well as the topics, which will be covered within a typical evaluation workshop.

*[https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/22276/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Project Charter]

The "Project Charter" is the one central document, outlining the whole project. It is used to document the common understanding of the whole project to ensure, having the same understanding in all projects parties.

It starts with the motivation to run the project and contains all goals and the scope of the whole project. Stakeholders on both sides are defined as well as detailed responsibilities and milestones to measure progress. Also further organization of the project is specified including details about documentation, reporting and communication. It will be maintained throughout the project-timeline.

All efforts, which are already known at this stage of the project are listed in this document.

*[https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/21758/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Customer Implementation Concept]

This "Customer Implementation Concept" outlines all results from the technical evaluation until this point in time, mainly resulting from the workshop. It contains all results from the initialization phase, as well as all already known topics, to be discussed and analyzed in the future.

This is a "living document" as well in that it is updated during the project to reflect the current state of affairs.

* [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/22277/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Basic Statement Of Work]

The "Basic Statement Of Work (SOW)" describes and offers all OX PS implementation efforts already known and agreed upon at this point in time.

=Concept Phase=

The "Concept Phase" is the first one, after the joint project has started formally. During this phase, the basic implementation like installation of hardware starts, but most important, all necessary detailed concepts are created and finalized.

During this phase it is decided what exactly will be done by whom and when.

The Customer Implementation Concept from the Initialization phase will be finalized. All tasks to be done by OX PS are documented and offered in (seperate) SOWs.

Typical activities and topics in this phase are as follows:

* Detail-Workshops for all complex integration topics, to finalize the Concept paper
* Time Planing and Milestones will be agreed on
* Resources are planned to define the responsibilities for each task
* Budget and associated costs are fixed
* Quality Management and Risk Management starts in this phase

==Tools in Concept Phase==

* The "Implementation Concept" from the first phase will be enhanced and is used as a living document to contain all known and discussed technical details. This document will be used throughout the whole project. So it is a very important source of information not only for implementation, also post-implementation as part of the system documentation.

* A [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/52878/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Requirements Checklist] will be introduced in this phase, which is used to track all open topics and issues. All closed topics will be moved to an "archive" to obtain a complete documentation of all project topics, as well as to be used for approval testing.

* WorkBreakdownStructure [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/50871/current?secret=30e01261e422f9ec9b0af51b0d3319e2 mindmeister.com-format] [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/50873/current?secret=30e01261e422f9ec9b0af51b0d3319e2 pdf] [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/50872/current?secret=30e01261e422f9ec9b0af51b0d3319e2 rtf]

The "Work Breakdown Structure" is a tree-like view on all known topics "work items" known at the recent point in time. A template, based on OX project experience, is used during the workshops as starting point. Then the WBS will be enhanced in all workshops and discussions to build a tree, which is as complete, as possible.

* SOWs will be created for all topics, when implementation or customization is requested from the OX team. Each topic will be tracked in on separate SOW, to keep the process as transparent as possible.

=Implementation Phase=

Within the "Implementation Phase" everything that was planned before will be realized, like the name says. However, in reality there always is an overlap in Concept Phase and Implementation Phase.

Typical activities and topics in this phase are as follows:

* Installation / Configuration of the live-system
* Integration into infrastructure
* Customization, Branding, Theming
* Documentation
* Quality Management
* Change Management
* Training (Admin, Support, Sales)

==Tools in the Implementation Phase==

Typically all tools from the former phase will be used to track the implementation process.

=Approval Phase=

During this last phase in the project, everything that was realized will be verified and approved against the documented requirements. After approval the launch process start, recommended in several steps, beginning with a soft-launch.

Typical activities and topics in this phase are as follows:

* Testing, manually and automated
* System- and Configuration Review
* Soft-Launch
* Migration
* Training (Admin, Support, Sales)* Handover to Support
* Documentation including architecture, setup, test-accounts, etc.
* Project retrospective
* Handover to Open-Xchange support

==Tools==

* [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/52878/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Requirements Checklist] ... This list produced during the concept phase contains agreed upon and done items. These will be used in this phase to verify the correct implementation of all topics.

OX HE Tutorial 1M

2012-01-24T15:15:05Z

217.7.151.106: /* Mandatory Installation Steps - Instructions & Recommendations */

= Tutorial: High Available OX HE Setup for up to 1 Milion users =

'''This article describes what you need for a typical OX HE Setup for up to 1.000.000 Users, which is fully clustered, high available and scaling very flexible.'''

It contains everything you need to:
* Understand the design of the OX HE setup including additional services
* Install the whole system based on the relevant articles
* Find pointers to the next steps of integration

= System Design =

[[Image:SaaS-1M.jpg]]

The system is designed to provide maximum functionality and availability with a minimum of necessary hardware. If the services on one OX server fail, this is transparently handled by the load balancer. If one MySQL server fails, it is sufficient to take over the IP address on the other MySQL server in the cluster to stay fully in operation.

== Core Components for OX HE ==

* Minimum two (recommended three) OX HE servers (HW recommendation: 32GB RAM / 8 cores each)
* Minimum one MySQL cluster with two servers in Master-Master configuration (HW recommendation: 32GB RAM / 8 cores each)
* NFS Server to store documents and files
* Recommended for more than 500.000 mailboxes: one OX HE server dedicated for user provisioning (HW recommendation: 16GB RAM / 4 cores each)

== Infrastructure Components not delivered by OX ==

* An email system providing IMAP and SMTP
* A control panel for creation and administration of users
* A Load Balancer in front of the OX servers (optional, recommended)

= Overview Installation Steps =

'''To deploy the described OX setup, the following steps need to be done. '''

== Mandatory Steps ==
# Initialize and configure MySQL database servers
# Install and configure OX on all servers

== Steps depending on your environment ==
# Implement Load Balancer
# Connect Control Panel
# Connect Email System

== Recommended Optional Next Steps ==
# Automated Frontend Tests
# Upsell Plugin
# Mobile Autoconfiguration
# Automatic FailOver
# Branding

= Mandatory Installation Steps - Instructions & Recommendations =

'''The following steps need to be done in every case to get OX up and running:'''

== Initialize and configure MySQL database on both servers ==

MySQL will be configured as Master-Master configuration to ensure data consistency on both servers.
If one machine fails, the other machine will take over all functionality.

[[OXLoadBalancingClustering_Database|Database setup for clustered environments]]

== Install and configure OX on both servers ==

OX will be installed on minimum two servers. It will be configured to '''write''' to the '''first''' MySQL database and to '''read''' from the '''second''' MySQL database in one cluster. This will distribute the load during normal operation as smooth as possible. During FailOver the IP address of the failed MySQL server will be taken over to the working server, the system stays operable.

[[OXLoadBalancingClustering_OXConfiguration|Open-Xchange setup and configuration for clustered environments]]

The NFS server will be mounted on all machines and registered as filestore.

[[OXLoadBalancingClustering_Filestore|Filestore setup for clustered environments]]

When multiple Open-Xchange Servers are configured within a cluster Session and Loadbalancing needs to be set up.

[[OXLoadBalancingClustering_SessionLoadbalancing|Session and Loadbalancing for clustered environments]]

[[OXLoadBalancingClustering_NetworkConfiguration|Network configuration for clustered environments]]

You also should install and configure the OXtender for Business Mobility:

[[OXtender_for_Business_Mobility| exchange active sync configuration for Open-Xchange]]

Let your users connect to their data from other services like Facebook, Twitter or LinkedIn by configuring the "SocialOX"

[[SocialOX|SocialOX-Configuration]]

= Installation Steps depending on your environment - Instructions & Recommendations =

'''The following components need to be implemented in your environment.'''

== Implement Load Balancer ==

A load balancer in front of the OX servers is necessary for this deployment size. It needs to handle the requests if one OX server fails.

If you already have a hardware load balancing solution in place, this can be used. OX is known to work with the standard load balancing solutions from BigIP, Barracuda, Foundry, ...

If you do not have a load balancing solution already in place, we recommend to use [http://www.keepalived.org/ Keepalived] as reliable and cost effective solution.

Read more about configuring [[Keepalived | Keepalived for Open-Xchange]]

{{OX_HE_Tutorial_CP}}

{{OX_HE_Tutorial_HGP}}

{{OX_HE_Tutorial_POA}}

{{OX_HE_Tutorial_Auth}}

== Connect Email System ==

Every email system providing IMAP and SMTP can be used as backend to OX. Best experiences are made with the widespread Linux based IMAP servers [http://dovecot.org/ Dovecot], [http://www.cyrusimap.org/ Cyrus] or [http://www.courier-mta.org/imap/ Courier].

Other IMAP servers need to be tested thoroughly before going into production.

There are several possibilities to implement the Email system:

# You already have an email system available: Nothing needs to be done, it just needs to be configured
# You use Parallels Automation (POA): Nothing special needs to be done, everything you need is contained in the APS package
# You want to setup a new Email system: It is recommended to use Dovecot, as this is very stable, fast, feature rich and easy to scale

{{OX_HE_Tutorial_Dovecot}}

{{OX_HE_Tutorial_Next}}

OX HE Tutorial 10K

2012-01-24T15:14:42Z

217.7.151.106: /* Mandatory Installation Steps - Instructions & Recommendations */

= Tutorial: OX HE Setup for up to 10.000 users =

'''This article describes what you need for a typical OX HE Setup for up to 10.000 Users with minimal efforts.'''

It contains everything you need to:
* Understand the design of the OX HE setup including additional services
* Install the whole system based on the relevant articles
* Find pointers to the next steps of integration

= System Design =

[[Image:SaaS-10k.jpg]]

The system is designed to provide maximum functionality with a minimum of necessary hardware. All OX services are running on one single machine.

== Core Components for OX HE ==

* One OX HE server (HW recommendation: 16GB RAM / 4 cores)
* MySQL installed directly on this server
* Optional: NFS Server to store documents and files

== Infrastructure Components not delivered by OX ==

* An email system providing IMAP and SMTP
* A control panel for creation and administration of users

= Overview Installation Steps =

'''To deploy the described OX setup, the following steps need to be done. '''

== Mandatory Steps ==
# Initialize and configure MySQL database
# Install and configure OX service

== Steps depending on your environment ==
# Connect Control Panel
# Connect Email System

== Recommended Optional Next Steps ==
# Automated Frontend Tests
# Upsell Plugin
# Mobile Autoconfiguration
# Branding

= Mandatory Installation Steps - Instructions & Recommendations =

'''The following steps need to be done in every case to get OX up and running:'''

== Install and configure OX ==

OX will be installed on the server.

* [[Open-Xchange_Installation_Guide_for_Debian_5.0|Download and Installation Guide for Debian GNU/Linux 5.0 (Lenny)]]
* [[Open-Xchange_Installation_Guide_for_SLES10|Download and Installation Guide for SUSE Linux Enterprise Server 10]]
* [[Open-Xchange_Installation_Guide_for_SLES11|Download and Installation Guide for SUSE Linux Enterprise Server 11]]
* [[Open-Xchange_Installation_Guide_for_RHEL5|Download and Installation Guide for RedHat Enterprise Linux 5]]

You also should install and configure the OXtender for Business Mobility

[[OXtender_for_Business_Mobility_Installation_Guide|Installation of the OXtender for Business Mobility]]

Let your users connect to their data from other services like Facebook, Twitter or LinkedIn by configuring the "SocialOX"

[[SocialOX|SocialOX-Configuration]]

= Installation Steps depending on your environment - Instructions & Recommendations =

'''The following components need to be implemented in your environment.'''

{{OX_HE_Tutorial_CP}}

{{OX_HE_Tutorial_HGP}}

{{OX_HE_Tutorial_Plesk}}

{{OX_HE_Tutorial_Auth}}

== Connect Email System ==

Every email system providing IMAP and SMTP can be used as backend to OX. Best experiences are made with the widespread Linux based IMAP servers [http://dovecot.org/ Dovecot], [http://www.cyrusimap.org/ Cyrus] or [http://www.courier-mta.org/imap/ Courier].

Other IMAP servers need to be tested thoroughly before going into production.

There are several possibilities to implement the Email system:

# You already have an email system available: Nothing needs to be done, it just needs to be configured
# You use Plesk Panel: Nothing special needs to be done, everything you need is contained in the OXtender for Plesk
# You want to setup a new Email system: It is recommended to use Dovecot, as this is very stable, fast, feature rich and easy to scale

{{OX_HE_Tutorial_Dovecot}}

{{OX_HE_Tutorial_Next}}

OX HE Tutorial 100K

2012-01-24T15:13:51Z

217.7.151.106: /* Install and configure OX on both servers */

= Tutorial: High Available OX HE Setup for up to 100.000 users =

'''This article describes what you need for a typical OX HE Setup for up to 100.000 Users, which is fully clustered and high available.'''

It contains everything you need to:
* Understand the design of the OX HE setup including additional services
* Install the whole system based on the relevant articles
* Find pointers to the next steps of integration

= System Design =

[[Image:SaaS-100k-1.jpg]]

The system is designed to provide maximum functionality and availability with a minimum of necessary hardware. If the services on one server fail, it is enough to take over the IP address to the other machine and service will stay up and running.

== Core Components for OX HE ==

* Two OX HE servers (HW recommendation: 16GB RAM / 4 cores each)
* MySQL installed directly on these server
* NFS Server to store documents and files

== Infrastructure Components not delivered by OX ==

* An email system providing IMAP and SMTP
* A control panel for creation and administration of users
* A Load Balancer in front of the OX servers (optional, recommended)

= Overview Installation Steps =

'''To deploy the described OX setup, the following steps need to be done. '''

== Mandatory Steps ==
# Initialize and configure MySQL database on both servers
# Install and configure OX on both servers

== Steps depending on your environment ==
# Implement Load Balancer
# Connect Control Panel
# Connect Email System

== Recommended Optional Next Steps ==
# Automated Frontend Tests
# Upsell Plugin
# Mobile Autoconfiguration
# Automatic FailOver
# Branding

= Mandatory Installation Steps - Instructions & Recommendations =

'''The following steps need to be done in every case to get OX up and running:'''

== Initialize and configure MySQL database on both servers ==

MySQL will run on both servers. MySQL will be configured as Master-Master configuration to ensure data consistency on both servers.
If one machine fails, the other machine will take over all functionality.

[[OXLoadBalancingClustering_Database|Database setup for clustered environments]]

== Install and configure OX on both servers ==

OX will be installed on both servers. It will be configured to '''write''' to the '''first''' MySQL database and to '''read''' from the '''second''' MySQL database. This will distribute the load during normal operation as smooth as possible. During FailOver the IP address of the failed server will be taken over to the working server, the system stays operable.

[[OXLoadBalancingClustering_OXConfiguration|Open-Xchange setup and configuration for clustered environments]]

The NFS server will be mounted on both machines and registered as filestore.

[[OXLoadBalancingClustering_Filestore|Filestore setup for clustered environments]]

When multiple Open-Xchange Servers are configured within a cluster Session and Loadbalancing needs to be set up.

[[OXLoadBalancingClustering_SessionLoadbalancing|Session and Loadbalancing for clustered environments]]

[[OXLoadBalancingClustering_NetworkConfiguration|Network configuration for clustered environments]]

You also should install and configure the OXtender for Business Mobility

[[OXtender_for_Business_Mobility_Installation_Guide|Installation of the OXtender for Business Mobility]]

Let your users connect to their data from other services like Facebook, Twitter or LinkedIn by configuring the "SocialOX"

[[SocialOX|SocialOX-Configuration]]

= Installation Steps depending on your environment - Instructions & Recommendations =

'''The following components need to be implemented in your environment.'''

== Implement Load Balancer ==

A load balancer in front of the OX servers is recommended, but optional in this deployment size. (In small environments, DNS Round Robin may be sufficient).

If you already have a hardware load balancing solution in place, this can be used. OX is known to work with the standard load balancing solutions from BigIP, Barracuda, Foundry, ...

If you do not have a load balancing solution already in place, we recommend to use [http://www.keepalived.org/ Keepalived] as reliable and cost effective solution.

Read more about configuring [[Keepalived | Keepalived for Open-Xchange]]

{{OX_HE_Tutorial_CP}}

{{OX_HE_Tutorial_HGP}}

{{OX_HE_Tutorial_POA}}

{{OX_HE_Tutorial_Auth}}

== Connect Email System ==

Every email system providing IMAP and SMTP can be used as backend to OX. Best experiences are made with the widespread Linux based IMAP servers [http://dovecot.org/ Dovecot], [http://www.cyrusimap.org/ Cyrus] or [http://www.courier-mta.org/imap/ Courier].

Other IMAP servers need to be tested thoroughly before going into production.

There are several possibilities to implement the Email system:

# You already have an email system available: Nothing needs to be done, it just needs to be configured
# You use Parallels Automation (POA): Nothing special needs to be done, everything you need is contained in the APS package
# You want to setup a new Email system: It is recommended to use Dovecot, as this is very stable, fast, feature rich and easy to scale

{{OX_HE_Tutorial_Dovecot}}

{{OX_HE_Tutorial_Next}}

{{OX_HE_Tutorial_FailOver}}

ProfServProjects

2012-01-24T12:13:43Z

217.7.151.106: /* Tools */

This article gives a detailed overview of the process to run an Open-Xchange implementation project together with the OX Professional Services team.

The phases and decisions are documented here, as well as the documents and tools used to accompany this process.

The following diagram gives a birds-eye view of the whole process: 
<div style="min-width 840px;">[[File:birdseye7.png]]</div> 

=Initialization Phase / Pre-Sales=

The first phase of the project, the "Initialization Phase" is typically the pre-sales cycle to evaluate the product and to evaluate the feasibility of the project as well as to identify potentially necessary customization to integrate into every environment.

At the end of this this phase, the results of the evaluation are used to provide a detailed offer and to make the final "Go" / "No-Go" decision.

Typical activities and topics in this phase are as follows:

*User Interface Demo and Evaluation (webcast or on-site)
* Architecture Overview
** Integration into existing customer systems
** Sizing, Scalability
** Available APIs, standards and programming languages
** Branding / Whitelabeling
* Proof Of Concept Installation (POC) in target environment
* Technology Transfer / Workshop
** Using the agenda given below
** Evaluate existing environment (mailsystem, loadbalancer, storage, provisioning, ..)
** Results in Customer Implementation Concept
* Request For Information (RFI) / Request For Quotation (RFQ)

==Tools and Results in Initalization Phase==
*[https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/22276/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Project Charter]

The "Project Charter" is the one central document, outlining the whole project. It is used to document the common understanding of the whole project to ensure, having the same understanding in all projects parties.

It starts with the motivation to run the project and contains all goals and the scope of the whole project. Stakeholders on both sides are defined as well as detailed responsibilities and milestones to measure progress. Also further organization of the project is specified including details about documentation, reporting and communication. It will be maintained throughout the project-timeline.

All efforts, which are already known at this stage of the project are listed in this document.

* [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/21816/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Workshop Agenda]

This document containing the "Workshop Agenda" is used to prepare for the initial technical workshop. The goal of the workshop is to get a common understanding of all existing infrastructure systems and the capabilities of the OX product. The preparation document lists all persons/roles, who should attend the workshop as well as the topics, which will be covered within a typical evaluation workshop.

*[https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/21758/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Customer Implementation Concept]

This "Customer Implementation Concept" outlines all results from the technical evaluation until this point in time, mainly resulting from the workshop. It contains all results from the initialization phase, as well as all already known topics, to be discussed and analyzed in the future.

This is a "living document" as well in that it is updated during the project to reflect the current state of affairs.

* [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/22277/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Basic Statement Of Work]

The "Basic Statement Of Work (SOW)" describes and offers all OX PS implementation efforts already known and agreed upon at this point in time.

=Concept Phase=

The "Concept Phase" is the first one, after the joint project has started formally. During this phase, the basic implementation like installation of hardware starts, but most important, all necessary detailed concepts are created and finalized.

During this phase it is decided what exactly will be done by whom and when.

The Customer Implementation Concept from the Initialization phase will be finalized. All tasks to be done by OX PS are documented and offered in (seperate) SOWs.

Typical activities and topics in this phase are as follows:

* Detail-Workshops for all complex integration topics, to finalize the Concept paper
* Time Planing and Milestones will be agreed on
* Resources are planned to define the responsibilities for each task
* Budget and associated costs are fixed
* Quality Management and Risk Management starts in this phase

==Tools in Concept Phase==

* The "Implementation Concept" from the first phase will be enhanced and is used as a living document to contain all known and discussed technical details. This document will be used throughout the whole project. So it is a very important source of information not only for implementation, also post-implementation as part of the system documentation.

* A [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/52878/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Requirements Checklist] will be introduced in this phase, which is used to track all open topics and issues. All closed topics will be moved to an "archive" to obtain a complete documentation of all project topics, as well as to be used for approval testing.

* WorkBreakdownStructure [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/50871/current?secret=30e01261e422f9ec9b0af51b0d3319e2 mindmeister.com-format] [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/50873/current?secret=30e01261e422f9ec9b0af51b0d3319e2 pdf] [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/50872/current?secret=30e01261e422f9ec9b0af51b0d3319e2 rtf]

The "Work Breakdown Structure" is a tree-like view on all known topics "work items" known at the recent point in time. A template, based on OX project experience, is used during the workshops as starting point. Then the WBS will be enhanced in all workshops and discussions to build a tree, which is as complete, as possible.

* SOWs will be created for all topics, when implementation or customization is requested from the OX team. Each topic will be tracked in on separate SOW, to keep the process as transparent as possible.

=Implementation Phase=

Within the "Implementation Phase" everything that was planned before will be realized, like the name says. However, in reality there always is an overlap in Concept Phase and Implementation Phase.

Typical activities and topics in this phase are as follows:

* Installation / Configuration of the live-system
* Integration into infrastructure
* Customization, Branding, Theming
* Documentation
* Quality Management
* Change Management
* Training (Admin, Support, Sales)

==Tools in the Implementation Phase==

Typically all tools from the former phase will be used to track the implementation process.

=Approval Phase=

During this last phase in the project, everything that was realized will be verified and approved against the documented requirements. After approval the launch process start, recommended in several steps, beginning with a soft-launch.

Typical activities and topics in this phase are as follows:

* Testing, manually and automated
* System- and Configuration Review
* Soft-Launch
* Migration
* Training (Admin, Support, Sales)* Handover to Support
* Documentation including architecture, setup, test-accounts, etc.
* Project retrospective
* Handover to Open-Xchange support

==Tools==

* [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/52878/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Requirements Checklist] ... This list produced during the concept phase contains agreed upon and done items. These will be used in this phase to verify the correct implementation of all topics.

ProfServProjects

2012-01-24T10:55:41Z

217.7.151.106: /* Tools and Results in Initalization Phase */

This article gives a detailed overview of the process to run an Open-Xchange implementation project together with the OX Professional Services team.

The phases and decisions are documented here, as well as the documents and tools used to accompany this process.

The following diagram gives a birds-eye view of the whole process: 
<div style="min-width 840px;">[[File:birdseye7.png]]</div> 

=Initialization Phase / Pre-Sales=

The first phase of the project, the "Initialization Phase" is typically the pre-sales cycle to evaluate the product and to evaluate the feasibility of the project as well as to identify potentially necessary customization to integrate into every environment.

At the end of this this phase, the results of the evaluation are used to provide a detailed offer and to make the final "Go" / "No-Go" decision.

Typical activities and topics in this phase are as follows:

*User Interface Demo and Evaluation (webcast or on-site)
* Architecture Overview
** Integration into existing customer systems
** Sizing, Scalability
** Available APIs, standards and programming languages
** Branding / Whitelabeling
* Proof Of Concept Installation (POC) in target environment
* Technology Transfer / Workshop
** Using the agenda given below
** Evaluate existing environment (mailsystem, loadbalancer, storage, provisioning, ..)
** Results in Customer Implementation Concept
* Request For Information (RFI) / Request For Quotation (RFQ)

==Tools and Results in Initalization Phase==
*[https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/22276/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Project Charter]

The "Project Charter" is the one central document, outlining the whole project. It is used to document the common understanding of the whole project to ensure, having the same understanding in all projects parties.

It starts with the motivation to run the project and contains all goals and the scope of the whole project. Stakeholders on both sides are defined as well as detailed responsibilities and milestones to measure progress. Also further organization of the project is specified including details about documentation, reporting and communication. It will be maintained throughout the project-timeline.

All efforts, which are already known at this stage of the project are listed in this document.

* [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/21816/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Workshop Agenda]

This document containing the "Workshop Agenda" is used to prepare for the initial technical workshop. The goal of the workshop is to get a common understanding of all existing infrastructure systems and the capabilities of the OX product. The preparation document lists all persons/roles, who should attend the workshop as well as the topics, which will be covered within a typical evaluation workshop.

*[https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/21758/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Customer Implementation Concept]

This "Customer Implementation Concept" outlines all results from the technical evaluation until this point in time, mainly resulting from the workshop. It contains all results from the initialization phase, as well as all already known topics, to be discussed and analyzed in the future.

This is a "living document" as well in that it is updated during the project to reflect the current state of affairs.

* [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/22277/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Basic Statement Of Work]

The "Basic Statement Of Work (SOW)" describes and offers all OX PS implementation efforts already known and agreed upon at this point in time.

=Concept Phase=

The "Concept Phase" is the first one, after the joint project has started formally. During this phase, the basic implementation like installation of hardware starts, but most important, all necessary detailed concepts are created and finalized.

During this phase it is decided what exactly will be done by whom and when.

The Customer Implementation Concept from the Initialization phase will be finalized. All tasks to be done by OX PS are documented and offered in (seperate) SOWs.

Typical activities and topics in this phase are as follows:

* Detail-Workshops for all complex integration topics, to finalize the Concept paper
* Time Planing and Milestones will be agreed on
* Resources are planned to define the responsibilities for each task
* Budget and associated costs are fixed
* Quality Management and Risk Management starts in this phase

==Tools in Concept Phase==

* The "Implementation Concept" from the first phase will be enhanced and is used as a living document to contain all known and discussed technical details. This document will be used throughout the whole project. So it is a very important source of information not only for implementation, also post-implementation as part of the system documentation.

* A [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/52878/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Requirements Checklist] will be introduced in this phase, which is used to track all open topics and issues. All closed topics will be moved to an "archive" to obtain a complete documentation of all project topics, as well as to be used for approval testing.

* WorkBreakdownStructure [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/50871/current?secret=30e01261e422f9ec9b0af51b0d3319e2 mindmeister.com-format] [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/50873/current?secret=30e01261e422f9ec9b0af51b0d3319e2 pdf] [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/50872/current?secret=30e01261e422f9ec9b0af51b0d3319e2 rtf]

The "Work Breakdown Structure" is a tree-like view on all known topics "work items" known at the recent point in time. A template, based on OX project experience, is used during the workshops as starting point. Then the WBS will be enhanced in all workshops and discussions to build a tree, which is as complete, as possible.

* SOWs will be created for all topics, when implementation or customization is requested from the OX team. Each topic will be tracked in on separate SOW, to keep the process as transparent as possible.

=Implementation Phase=

Within the "Implementation Phase" everything that was planned before will be realized, like the name says. However, in reality there always is an overlap in Concept Phase and Implementation Phase.

Typical activities and topics in this phase are as follows:

* Installation / Configuration of the live-system
* Integration into infrastructure
* Customization, Branding, Theming
* Documentation
* Quality Management
* Change Management
* Training (Admin, Support, Sales)

==Tools in the Implementation Phase==

Typically all tools from the former phase will be used to track the implementation process.

=Approval Phase=

During this last phase in the project, everything that was realized will be verified and approved against the documented requirements. After approval the launch process start, recommended in several steps, beginning with a soft-launch.

Typical activities and topics in this phase are as follows:

* Testing, manually and automated
* System- and Configuration Review
* Soft-Launch
* Migration
* Training (Admin, Support, Sales)* Handover to Support
* Documentation including architecture, setup, test-accounts, etc.
* Project retrospective
* Handover to Open-Xchange support

==Tools==
* [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/18613/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Meeting Minutes]

These minutes cover attendees to a meeting, topics discussed, decisions made and action items.

* [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/52878/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Requirements Checklist] ... This list produced during the concept phase contains agreed upon and done items. These will be used in this phase to verify the correct implementation of all topics.

EvaluationBestPractice

2011-12-29T13:01:28Z

217.7.151.106:

This article outlines the best practice process to evaluate the OX product efficiently. We recommend to follow these steps to achieve the best possible evaluation experience in a reasonable timeframe.

<div style="min-width 840px;">[[File:presales-process.png]]</div> 
The diagram shows the different steps to be taken, the color coding shows the responsibility for each step: blue steps will be driven by OX, green ones by the partner/customer.

= Preparation / Questionnaire =
To support the initial assessment of the environment and the requirements, it is recommended to use the following questionnaire as a guideline.

This questionnaire helps Open-Xchange to initially understand the requirements and the environment in which the product will be used from a business standpoint as well as from a technical view.

This understanding is necessary to prepare the initial webcasts efficiently and to provide the necessary specialized know-how, as well as to find the recommended solution and architecture.

Please download the [https://ox6-dev.open-xchange.com/publications/files/1/projectTemplates/4497/current?secret=30e01261e422f9ec9b0af51b0d3319e2 Questionnaire] here.

= Initial Webcast =
An initial webcast will be held with a combination of product focusing people as well as technical people.

Goal of the webcast is to deliver a basic understanding of the products capabilities and the basic technical understanding. It is important, that all stakeholders in the process have a common knowledge of the product before each group of specialists dives deeper into the

The basic agenda of the webcast is as follows and will be adapted following the results from the questionnaire:

* Product Positioning and Demo
* Architecture Overview
* Documentation and Self-Service Overview
* Proof Of Concept (POC) installation planning

= POC Installation =
The goal of a POC installation is, to provide a single-server OX system in the existing target-environment for evaluation purpose.
It will be connected to mail-accounts already existing in the target environment and will be administered manually.

(insert Link to article describing POC Requirements / Deliverables)

There are two possibilities to achieve the goal: the POC can be installed remotely by OX personnel or by the partner/customer himself.

1. Installation by partner/customer
* The POC will be installed following the mandatory steps in the article [[OX_HE_Tutorial_10K]], with the exception, that the storage will be on the local machine.
* After the installation, a review webcast will be held with OX technical people to verify the installation and give some additional hints how to use it

2. Installation by OX
* The requirements for the installation will be fulfilled by partner/customer
* OX personell will do the installation remotely on the prepared machine
* After the installation, a handover webcast will be held to explain the installation and give some additional hints how to use it

= Evaluation Period =

....

= Feedback Webcast =
(approx. 4 weeks later)

File:Presales-process.png

2011-12-29T12:28:22Z

217.7.151.106: uploaded a new version of "File:Presales-process.png"

File:Presales-process.png

2011-12-29T12:27:13Z

217.7.151.106: uploaded a new version of "File:Presales-process.png"

EvaluationBestPractice

2011-12-29T12:26:26Z

217.7.151.106:

This article outlines the best practice process to evaluate the OX product efficiently. We recommend to follow these steps to achieve the best possible evaluation experience in a reasonable timeframe.

<div style="min-width 840px;">[[File:presales-process.png]]</div> 
The diagram shows the different steps to be taken, the color coding shows the responsibility for each step: blue steps will be driven by OX, green ones by the partner/customer.

= Preparation / Questionnaire =
To support the initial assessment of the environment and the requirements, it is recommended to use the following questionnaire as a guideline.

This questionnaire helps Open-Xchange to initially understand the requirements and the environment in which the product will be used from a business standpoint as well as from a technical view.

This understanding is necessary to prepare the initial webcasts efficiently and to provide the necessary specialized know-how, as well as to find the recommended solution and architecture.

(insert link to questionnaire here)

= Initial Webcast =
An initial webcast will be held with a combination of product focusing people as well as technical people.

Goal of the webcast is to deliver a basic understanding of the products capabilities and the basic technical understanding. It is important, that all stakeholders in the process have a common knowledge of the product before each group of specialists dives deeper into the

The basic agenda of the webcast is as follows and will be adapted following the results from the questionnaire:

* Product Positioning and Demo
* Architecture Overview
* Documentation and Self-Service Overview
* Proof Of Concept (POC) installation planning

= POC Installation =
The goal of a POC installation is, to provide a single-server OX system in the existing target-environment for evaluation purpose.
It will be connected to mail-accounts already existing in the target environment and will be administered manually.

(insert Link to article describing POC Requirements / Deliverables)

There are two possibilities to achieve the goal: the POC can be installed remotely by OX personnel or by the partner/customer himself.

1. Installation by partner/customer
* The POC will be installed following the mandatory steps in the article [[OX_HE_Tutorial_10K]], with the exception, that the storage will be on the local machine.
* After the installation, a review webcast will be held with OX technical people to verify the installation and give some additional hints how to use it

2. Installation by OX
* The requirements for the installation will be fulfilled by partner/customer
* OX personell will do the installation remotely on the prepared machine
* After the installation, a handover webcast will be held to explain the installation and give some additional hints how to use it

= Evaluation Period =

....

= Feedback Webcast =
(approx. 4 weeks later)

EvaluationBestPractice

2011-12-29T12:17:18Z

217.7.151.106:

This article outlines the best practice process to evaluate the OX product efficiently. We recommend to follow these steps to achieve the best possible evaluation experience in a reasonable timeframe.

<div style="min-width 840px;">[[File:presales-process.png]]</div> 
The diagram shows the different steps to be taken, the color coding shows the responsibility for each step.

= Preparation / Questionnaire =
To support the initial assessment of the environment and the requirements, it is recommended to use the following questionnaire as a guideline.

This questionnaire helps Open-Xchange to initially understand the requirements and the environment in which the product will be used from a business standpoint as well as from a technical view.

This understanding is necessary to prepare the initial webcasts efficiently and to provide the necessary specialized know-how, as well as to find the recommended solution and architecture.

(insert link to questionnaire here)

= Initial Webcast =
An initial webcast will be held with a combination of product focusing people as well as technical people.

Goal of the webcast is to deliver a basic understanding of the products capabilities and the basic technical understanding. It is important, that all stakeholders in the process have a common knowledge of the product before each group of specialists dives deeper into the

The basic agenda of the webcast is as follows and will be adapted following the results from the questionnaire:

* Product Positioning and Demo
* Architecture Overview
* Documentation and Self-Service Overview
* Proof Of Concept (POC) installation planning

= POC Installation =
The goal of a POC installation is, to provide a single-server OX system in the existing target-environment for evaluation purpose.
It will be connected to mail-accounts already existing in the target environment and will be administered manually.

(insert Link to article describing POC Requirements / Deliverables)

There are two possibilities to achieve the goal: the POC can be installed remotely by OX personnel or by the partner/customer himself.

1. Installation by partner/customer
* The POC will be installed following the mandatory steps in the article [[OX_HE_Tutorial_10K]], with the exception, that the storage will be on the local machine.
* After the installation, a review webcast will be held with OX technical people to verify the installation and give some additional hints how to use it

2. Installation by OX
* The requirements for the installation will be fulfilled by partner/customer
* OX personell will do the installation remotely on the prepared machine
* After the installation, a handover webcast will be held to explain the installation and give some additional hints how to use it

= Evaluation Period =

....

= Feedback Webcast =
(approx. 4 weeks later)

User:Malasa

2011-11-22T08:59:02Z

217.7.151.106:

Hello world

Open-Xchange Architecture Overview

This page gives an overview of used and supported interfaces of the open-xchange server.

[[File:ox_architecture.png]]

User 
*1 All communication from and to the user can be encryptet with HTTPS
*2 Im/Export of userdata:
** General [[HTTP API]] overview
** [[Using the import servlet]], [[Building an importer]]
** [[Using the export servlet]], [[Building an exporter]], [[ Export icl/vard]],
*3 OX Web UI & Mobile UI
** [http://www.open-xchange.com/en/products/ox-hosting-edition/requirements.html Requirements Web UI]
** [[OX Mobile Web App]]
*4 [[OXtender for Business Mobility Installation Guide]]
*5 [[OXtender 2 for Microsoft Outlook]]
*6 [[Caldav carddav Bundles]], [[SetUpMacCalCardDAVClients|Setup Mac Cal/CardDAV Clients]]
*7 webdav

Administrator

*11 Data migration via [[HTTP API]],
*12 [http://software.open-xchange.com/OX6/doc/OX6-Provisioning/ Comandline tools]
*13 RMI [http://software.open-xchange.com/OX6/doc/RMI/admin-core/ Core] API, RMI [http://software.open-xchange.com/OX6/doc/RMI/admin-hosting/ hosting] API
*14 [[Open-Xchange-SOAP]], [http://software.open-xchange.com/OX6/doc/SOAP/admin/OX-Admin-SOAP.html SOAP API], [[POAIntegrationGuide| POA integration guide]], [[Open-Xchange_cPanel_Installation| cPanel installation]]
*15 Plugins for Authentification
**[[Authentication IMAP Plugin description]]
**[[OX and Samba Login through LDAP]]
** Database
** custom
*16 [[OX monitoring interface]], [[OX munin scripts]]

Backend

*21 Database (mySQL)
*22 mySQL contacts storage
*23 Plugins for contacts storage
** mySQL
** LDAP
** custom
*24 Plugins for Mail Abstraction Layer
** IMAP
** SMTP
** custom
*25 Plugins for Storage
** NFS
** Local filesystem
** custom

Social/Public Data
*31 External calendar (google)
*32 External messaging services (Facebook, Twitter, SMS/MMS)
*33 Contacts integration (Xing, LinkedIn, MSN/Windows Live, Yahoo, Facebook, google, gmx.de, web.de)
*34 External email accounts can be integrated (POP3, IMAP)
** preconfigured for mail-account plugin: google, Yahoo, msn/WindowsLive, gmx.com , gmx.de , web.de , freenet.de
** [[Install and configure the mail-account plugin]]

Plugins
* [[Open-Xchange Plugin Overview]]

User:Malasa

2011-11-22T08:54:09Z

217.7.151.106:

Hello world

Open-Xchange Architecture Overview

This page gives an overview of used and supported interfaces of the open-xchange server.

[[File:ox_architecture.png]]

User 
*1 All communication from and to the user can be encryptet with HTTPS
*2 Im/Export of userdata:
** General [[HTTP API]] overview
** [[Using the import servlet]], [[Building an importer]]
** [[Using the export servlet]], [[Building an exporter]], [[ Export icl/vard]],
*3 OX Web UI & Mobile UI
** [http://www.open-xchange.com/en/products/ox-hosting-edition/requirements.html Requirements Web UI]
** [[OX Mobile Web App]]
*4 [[OXtender for Business Mobility Installation Guide]]
*5 [[OXtender 2 for Microsoft Outlook]]
*6 [[Caldav carddav Bundles]], [[SetUpMacCalCardDAVClients|Setup Mac Cal/CardDAV Clients]]
*7 webdav

Administrator

*11 Data migration via [[HTTP API]],
*12 [http://software.open-xchange.com/OX6/doc/OX6-Provisioning/ Comandline tools]
*13 RMI [http://software.open-xchange.com/OX6/doc/RMI/admin-core/ Core] API, RMI [http://software.open-xchange.com/OX6/doc/RMI/admin-hosting/ hosting] API
*14 [[Open-Xchange-SOAP]], [http://software.open-xchange.com/OX6/doc/SOAP/admin/OX-Admin-SOAP.html SOAP API], [[POAIntegrationGuide| POA integration guide]], [[Open-Xchange_cPanel_Installation| cPanel installation]]
*15 Plugins for Authentification
**[[Authentication IMAP Plugin description]]
**[[OX and Samba Login through LDAP]]
** Database
** custom
*16 [[OX monitoring interface]], [[OX munin scripts]]

Backend

*21 Database (mySQL)
*22 mySQL contacts storage
*23 Plugins for contacts storage
** mySQL
** LDAP
** custom
*24 Plugins for Mail Abstraction Layer
** IMAP
** SMTP
** custom
*25 Plugins for Storage
** NFS
** Local filesystem
** custom

Social/Public Data
*31 External calendar (google)
*32 External messaging services (Facebook, Twitter, SMS/MMS)
*33 Contacts integration (Xing, LinkedIn, MSN/Windows Live, Yahoo, Facebook, google, gmx.de, web.de)
*34 External email accounts can be integrated as long the provide POP3 or IMAP
** preconfigured for mail-account plugin: google, yahoo, msn/WindowsLive, gmx.com , gmx.de , web.de , freenet.de
** [[Install and configure the mail-account plugin]]

Plugins
* [[Open-Xchange Plugin Overview]]

User:Malasa

2011-11-22T08:51:34Z

217.7.151.106:

Hello world

Open-Xchange Architecture Overview

This page gives an overview of used and supported interfaces of the open-xchange server.

[[File:ox_architecture.png]]

User 
*1 All communication from and to the user can be encryptet with HTTPS
*2 Im/Export of userdata:
** General [[HTTP API]] overview
** [[Using the import servlet]], [[Building an importer]]
** [[Using the export servlet]], [[Building an exporter]], [[ Export icl/vard]],
*3 OX Web UI & Mobile UI
** [http://www.open-xchange.com/en/products/ox-hosting-edition/requirements.html Requirements Web UI]
** [[OX Mobile Web App]]
*4 [[OXtender for Business Mobility Installation Guide]]
*5 [[OXtender 2 for Microsoft Outlook]]
*6 [[Caldav carddav Bundles]], [[SetUpMacCalCardDAVClients|Setup Mac Cal/CardDAV Clients]]
*7 webdav

Administrator

*11 Data migration via [[HTTP API]],
*12 [http://software.open-xchange.com/OX6/doc/OX6-Provisioning/ Comandline tools]
*13 RMI [http://software.open-xchange.com/OX6/doc/RMI/admin-core/ Core] API, RMI [http://software.open-xchange.com/OX6/doc/RMI/admin-hosting/ hosting] API
*14 [[Open-Xchange-SOAP]], [http://software.open-xchange.com/OX6/doc/SOAP/admin/OX-Admin-SOAP.html SOAP API], [[POAIntegrationGuide| POA integration guide]], [[Open-Xchange_cPanel_Installation| cPanel installation]]
*15 Plugins for Authentification
**[[Authentication IMAP Plugin description]]
**[[OX and Samba Login through LDAP]]
** Database
** custom
*16 [[OX monitoring interface]], [[OX munin scripts]]

Backend

*21 Database (mySQL)
*22 mySQL contacts storage
*23 Plugins for contacts storage
** mySQL
** LDAP
** custom
*24 Plugins for Mail Abstraction Layer
** IMAP
** SMTP
** custom
*25 Plugins for Storage
** NFS
** Local filesystem
** custom

Social/Public Data
*31 External calendar (google)
*32 External messaging services (Facebook, Twitter, SMS/MMS)
*33 Contacts integration (Xing, LinkedIn, MSN/Hotmail, Yahoo, Facebook, google, gmx.de, web.de)
*34 External email accounts can be integrated as long the provide POP3 or IMAP
** preconfigured for mail-account plugin: google, yahoo, msn/windowsLive, gmx.com , gmx.de , web.de , freenet.de
** [[Install and configure the mail-account plugin]]

Plugins
* [[Open-Xchange Plugin Overview]]

OX Outlook Uploader

2011-10-17T06:44:50Z

217.7.151.106: /* Windows System */

=Open-Xchange Microsoft Outlook® Uploader=

Open-Xchange provides Open-Xchange Microsoft Outlook® Uploader (short: ''OXUploader''), a migration tool to export data from Microsoft Outlook® or from a Microsoft Exchange Server® to the Open-Xchange Server.

=Features=
* Migration of E-Mails, appointments, contacts, distribution lists, tasks and sticky notes
* Folder structure is preserved, subfolders are created as necessary
* Attachments of E-Mails and other objects are migrated
* Support for recurring appointments and participants
* Migration of .pst-files
* Migration of data files from installed mail profiles
* Migration of Microsoft Exchange mailboxes
* Easy to use 3-step interactive wizard to configure the migration
* Unattended mode to perform migrations without user interaction
* Commandline interface to automate batch migrations

=Prerequisites=
The OXUploader migration tool is installed on a windows system having access to the data that should be migrated. The data is then migrated from there to the Open-Xchange server. Please ensure that the following requirements are met before installing the tool:

==Windows System==
* Latest Versions of Windows XP, Windows Server 2003
* Latest Versions of Microsoft Office Outlook® (2002/XP, 2003, 2007 SP1 or 2010 SP1, 32-bit) or Microsoft® Exchange Server or standalone versions of Extended MAPI (Exchange 5.5 through 2010)
* Microsoft® .NET Framework 2.0

==Open-Xchange Server==
* Latest Version of the Open-Xchange Serve
* The user account(s) for which the data should be migrated should already have been created

=Download and installation=

To download the Open-Xchange Microsoft Outlook® Uploader installation packages and Release Notes, follow this [http://software.open-xchange.com/OX6/migration/Outlookuploader/ link]

After the download of the package, you can start the installation by double-clicking on the package. Please follow the installation steps in the wizard. The installation does not require administrative rights.

=Usage (interactive mode)=

{|
| [[image:OXUploader_Wizard_1.png|thumb]] ||
==1. Choose the migration source==
* First, either choose to migrate a personal storage file (.pst file), a data store from the local mail profiles, or an Exchange server mailbox.
* Depending on your choice, you can specify the migration source in the next step.
|-
| [[image:OXUploader_Wizard_2a.png|thumb]] ||
==2a. Select a personal storage file to migrate==
* When clicking on Browse the standard folder for saving .pst files opens.
* As some .pst files are password protected the password can be entered in the second field.
* When having chosen a file, click on Next.
|-
| [[image:OXUploader_Wizard_2b.png|thumb]] ||
==2b. Select a data file from a profile to migrate==
* Select one of the existing profiles from the drop-down menu.
* Select a store from the profile.
* Finally, enter a password if needed.
* To proceed, click Next.
|-
| [[image:OXUploader_Wizard_2c.png|thumb]] ||
==2c. Select an Exchange Server mailbox to migrate==
* Enter the URL of the Microsoft Exchange server.
* Select the username of the the account on the Exchange server.
* Click on "Logon..." to connect to the Exchange server and fetch the available mailboxes.
* When being asked, enter your password to logon to the Exchange server
* Select one of the existing mailboxes from the drop-down menu.
* To proceed, click Next.
|-
| [[image:OXUploader_Wizard_3.png|thumb]] ||
==3. Please enter information about the server==
* In the Server URL field, enter the Open-Xchange Server address.
* Enter your username in the second field.
* Enter your password in the third field.
* In order to make further settings, activate the "Configure advanced settings" checkbox.
* To proceed, click on Next.
|-
| [[image:OXUploader_Wizard_4.png|thumb]] ||
==4. Configure advanced options==
* If the folders should be migrated into a subfolder, enter it's name in the first field.
* In case not all mail folders are to be exported, the folders can be selected by clicking on the "Select..." button.
* Select the type of items to be migrated by marking the apporpiate checkboxes, and optionally define a minimum date for the items.
* In order to ignore the "Trash", "Junk" or "Sync Issues" folders for the migration, activate the respective checkbox.
* If empty folders should be skipped, activate the respective checkbox.
* If the target folders should be emptied before items are migrated into them, activate the respective checkbox.
|-
| [[image:OXUploader_Wizard_5.png|thumb]] ||
==5. Migration in process==
* This window displays the status and a log protocol of the migration.
* When the process is finished, click on Next.
|-
| [[image:OXUploader_Wizard_6.png|thumb]] ||
==6. Migration completed==
* This window displays an overview of the migration and you can view the log file by clickin on the respective button.
* To close the wizard, click on Finish.
|}

=Usage (unattended mode)=

The migration tool can be started in a special "batch mode", where no user interaction is necessary. The options for the migration can be set in the configuration files, or passed via the commandline when starting the tool, see (3). When the parameter "batchmode" is "true", the migration starts automatically. In this case, at least the following settings have to be available, either supplied via the commandline or defined in the configuration file:
* Username
* ServerURL
* PSTFile ''or'' ProfileName and StoreName ''or'' ExchangeServerURL
* Password ''or'' AdminUser and AdminPassword

For example, to migrate the .pst-file "c:\test.pst", a command could look
like:
<pre>OXUploaderC.exe -batchmode true -pstfile "c:\test.pst" -serverurl "http://ox.example.invalid" -username test -password secret</pre>

Multiple instances of the tool can be run simultaneously from one or multiple client machines, more information can be found in (6).

=Configuration=

==Configuration files==

The application's configuration settings can be adjusted in config files, both for the OXUploader.exe main application for interactive mode and for the commandline version of the tool OXUploaderC.exe (see below). The files are named as the corresponding executable, with the file extension ".config": OXUploader.exe.config and OXUploaderC.exe.config respectively. A description of each parameter can be found in [[#Configuration parameters|Configuration parameters]]

==Commandline parameters==

Furthermore, the application can be started with commandline parameters. All supplied options overwrite the default settings from the configuration file, which are assumed if an option is missing. The following parameters are recognized:
<pre>-adminuser <Admin username on the OX server (for admin migration)>
-adminpassword <Admin password on the OX server (for admin migration)>
-appointmentsmindate <Minimum date of appointments to be migrated>
-batchmode <true/false>
-clearfolders <true/false>
-emailssmindate <Minimum date of e-mails to be migrated>
-exchangemailboxname <Name of the Exchange mailbox to migrate>
-exchangeserverurl <URL of the Exchange server>
-exchangeserverusername <Username on the Exchange server>
-exportappointmentparticipants <true/false>
-exportappointmentuids <true/false>
-ignorejunkfolder <true/false>
-ignoresyncissuesfolder <true/false>
-ignoretrashfolder <true/false>
-importfoldername <Name of the migration target subfolder>
-logautoflush <true/false>
-logconsole <true/false>
-loglevel <off/error/warning/info/verbose>
-logonexchangemailbox <true/false>
-logpostdata <true/false>
-logtextfile <Path to logfile>
-migrateappointments <true/false>
-migratecontacts <true/false>
-migrateemails <true/false>
-migratenotes <true/false>
-migratetasks <true/false>
-password <Password on the OX server>
-profilename <Name of the profile>
-pstfile <Path to PST file>
-pstpassword <Password for the PST file>
-serverurl <URL of the OX server>
-skipemptyfolders <true/false>
-storename <Name of the store inside the profile>
-tasksmindate <Minimum date of tasks to be migrated>
-uploadchunksize <Number of uploaded mails per request>
-uploadthresholdbytes <Threshold of bytes for sending forced>
-username <Username on the OX server>
-recoverableexceptionmaxretries <max. retries after recoverable error>
</pre>

=Misc=

The following chapters contain some advanced information and configration options for the OXUploader migration tool.

==Performance considerations==

The time needed to perform a migration correspondends with the size of the .pst file, of course. So, for large mailboxes, this could be a quite time intensive task, and may be improved in knowledge of the following observations, especially when performing multiple simultaneous batch migrations.
The I/O-ratio is about the following: Per each byte read from disk, about 0.65 bytes are written to disk, and 0.12 bytes are sent to the server. This is caused by the fact that the messages read out from the .pst-file are exported to RFC822 .eml files first, then those files are loaded again before finally sending them to the server. Therefore, the throughput of the local file system should be as fast as possible. Since the temporary created RFC822 e-mail files are created in the user's temp folder, it would be best to move the location to a separate location as the .pst-file - another hdd, maybe even a ramdisk for the temp directory would make sense for heavy batch migrations. It's also recommended to temporarily disable virus protection and indexing services during the migration, and Outlook 2007 should be preferred against Outlook 2003.

==Limitations when running multiple instances==

When executing multiple migrations simulataneously from one machine, each instance of the tool must have exclusive access to the .pst-file it is migrating. Furthermore, each instance must use a different logfile. The tool relies on Outlook, and so it also can't work around Outlooks own limitations, especially as Outlook is designed as client application. More details can be found at the knowledge base article here: http://support.microsoft.com/kb/257757/en-us .

==Admin migration==

When the server is configured appropiate, the migration tool can also be used to import .pst-files into the OX account of the specified user, without the need to supply the user's password. Therefore, the username and password of a special admin user is needed for authentication against the OX server.
For example, to migrate the .pst-file "c:\test.pst" into the account "test", a command could look like:
<pre>OXUploaderC.exe -batchmode true -pstfile "c:\test.pst" -serverurl "http://ox.example.invalid" -username test -adminuser admin -adminpassword secret</pre>

==Personal storage files==

Sometimes .pst-files are broken our corrupted, and the migration tool may not be able to open them correctly, or opening them takes a very long time when the internal repair operations take place.
To reduce the impact of broken .pst-files, it's recommended to check the integrity of the files using Microsofts SCANPST.exe tool, see http://support.microsoft.com/kb/287497 . Sadly this utility is designed to run interactively, but there are some utilities out there that automate the SCANPST.exe tool to be run from the commandline, pointing to the .pst-file to scan, for example cmdscan.exe from http://www.olfolders.de/Lang/English/OLfix/download.htm . Doing so, one would be able to incorporate a SCANPST.exe launch prior a batch call to the migration tool, e.g. the following command could be invoked to scan and repair the .pst file "c:\test.pst", passing the path to the SCANPST.exe location:
<pre>cmdscan.exe -rename "c:\Program Files (x86)\Microsoft Office\Office12\SCANPST.EXE" "c:\test.pst"</pre>

==Duplicated items==

Migrating the same items into the same target folder multiple times usually results in the items getting duplicated on the server.
An exception to this rule are appointments with unique identifiers (UIDs), see http://www.ietf.org/rfc/rfc2445.txt, chapter 4.8.4.7, for details. To avoid importing an appointment with the same identifier multiple times, the server rejects an appointment when the UID already exists on the server. To force the migration of appointments regardless of their UIDs, the tool optionally removes the UIDs from the appointment. The relevant setting is named "ExportAppointmentUIDs", when set to "False", existing UIDs are removed before sending them to the server.
Furthermore, the migration tool has an option to clear the folder contents before triggering the export. When "ClearFolders" is set to "True", the target folder is emptied prior to the items being exported. Note that any existing data in these folders will be permanently lost.

==Exchange mailboxes==

Instead of using a local mail profile or a .pst file for migration, it's also possible to logon to and migrate an Exchange mailbox directly. It's recommeded that the migration tool is executed inside the exchange domain by the owner of the mailbox.
To perform an administrative migration for other user's mailboxes, the following preconditions must be met:
* Ensure the target account already has been created on the OX server
* Grant the administrating user "Receive As" permissions to the mailbox store of all accounts that should be migrated, details can be found at http://support.microsoft.com/default.aspx?scid=kb;EN-US;821897 and http://msexchangeteam.com/archive/2006/01/25/418099.aspx
* The migration tool is ececuted by the administrative user, who already should be logged on to the exchange domain
The administrative migration can only be executed from the commandline in "batch mode", see (5) for details. The mailbox or the name of the user that is going to be migrated needs to be specified inside the commandline parameter "exchangemailboxname". For example, to migrate the mailbox of exchange user "test" to the Open-Xchange account with username "test", combined with admin migration at the OX server (see (6c) for details), one could execute the migration tool in the following way:
<pre>OXUploaderC.exe -batchmode true -exchangeserverurl 192.168.0.4 -exchangemailboxname test -serverurl "http://ox.example.invalid" -username test -adminuser admin -adminpassword secret</pre>
Or, if the password of the OX user is available:
<pre>OXUploaderC.exe -batchmode true -exchangeserverurl 192.168.0.4 -exchangemailboxname test -serverurl "http://ox.example.invalid" -username test -password secret</pre>

==Administrative installation==

The OXUploader migration tool itself can be installed without the need for elevated access rights by the end user, as the installer only accesses the local non-roaming application data directory and the HKCU hive in the registry. It can't be installed 'per machine', which means that it is not allowed to set the value of the ALLUSERS msi property to "1".
The tool can be pre-configured for the end-users by setting public properties at the commandline for the installation process. These are processed by the installer and then written into the tool's config-file. The following parameters can be adjusted (the values in square brackets that are listed below indicate the default values of the properties when not overridden by the msi commandline - so that would be the default pre-configuration):
<pre>ADMINUSER []
ADMINPASSWORD []
BATCHMODE [False]
CLEARFOLDERS [False]
EXPORTAPPOINTMENTPARTICIPANTS [True]
EXPORTAPPOINTMENTUIDS [True]
IGNOREJUNKFOLDER [True]
IGNORETRASHFOLDER [True]
IMPORTFOLDERNAME []
LOGAUTOFLUSH [True]
LOGCONSOLE [False]
LOGLEVEL [Info]
LOGTEXTFILE [.\pst2ox.log]
MIGRATEAPPOINTMENTS [True]
MIGRATECONTACTS [True]
MIGRATEEMAILS [True]
MIGRATENOTES [True]
MIGRATETASK [True]
PASSWORD []
PROFILENAME []
PSTFILE []
PSTPASSWORD []
SERVERURL [http://]
SKIPEMPTYFOLDERS [True]
STORENAME []
UPLOADCHUNKSIZE [25]
UPLOADTHRESHOLDBYTES [2097152]
OXUSERNAME []
RECOVERABLEEXCEPTIONMAXRETRIES [3]
</pre>

For example, to predefine a Server URL that should be used for the
migration afterwards, one would execute e.g.:
<pre> "Open-Xchange Outlook Uploader.msi" SERVERURL="http://ox.example.invalid"</pre>

==Address Resolution==

While the Open-Xchange server uses SMTP as the only recipient address type, data from Microsoft Exchange might contain several additional address types. To migrate such Exchange data to the Open-Xchange server, each e-mail recipient or particpiant of an appointment or task needs a valid SMTP address. While the migration tool tries to retrieve the SMTP address of message recipients in different ways, sometimes there might be recipients that can't be resolved without a connection to the Microsoft Exchange server / Active Directory and it's global address lists. Especially, this may happen with .pst-files that were created using Microsofts EXMERGE tool.
In order to resolve that issue, the OXUploader migration tool can establish a connection to the exchange server and to it's global address list prior migrating a .pst-file to the Open-Xchange server, so that the recipient's SMTP addresses can be resolved. To do so, there are two parameters that can be set to logon to the exchange server prior migrating the .pst-file: [[#ExchangeServerURL|ExchangeServerURL]] and [[#ExchangeServerUsername|ExchangeServerUsername]]. The username parameter is optional (if not defined, the identity of the current windows user is used) and normally should not need to be set in batch-mode to prevent a windows logon prompt.
For example, to logon to the exchange server at "192.168.0.4" and perform an admin migration for the username "test" in unattended mode, a command could look like:
<pre>OXUploaderC.exe -batchmode true -exchangeserverurl 192.168.0.4 -serverurl "http://ox.example.invalid" -username test -adminuser admin -adminpassword secret -pstfile ".\test.pst" -logtextfile ".\test.log"</pre>

=Configuration parameters=
This chapter describes all possible configuration parameters that can be found in the OXUploader.exe.config / OXUploaderC.exe.config configuration files or can be passed to the migration tool from the commandline.

; AdminPassword: The password associated with the administrator user ([[#AdminUser|AdminUser]]) on the Open-Xchange server. Only used when performing [[#Admin_migration|admin migration]].
; AdminUser: The username of the administrator user on the Open-Xchange server. Only used when performing [[#Admin_migration|admin migration]].
; AppointmentsMinDate: If defined, only appointments that end after this date are migrated. Recurring appointments are migrated, if the end date of the series has not been set, or if the end date of the series is not after this defined value. Date format should be ''yyy-MM-dd''.
; BatchMode: Specifies whether the tool should be run in a special batchmode without user interaction or not, see [[#Usage_(unattended_mode)|unattended mode]] for details.
; ClearFolders: When set to 'True', the migration tool clears the target folder contents before exporting items to that folders. Existing subfolders are not affected by this setting, only the folder's contents. Also, the folder clear-command is only executed for folders that are actually migrated, not for ignored or skipped folders.
; EMailsMinDate: If defined, only e-mails that were sent or received after this date are migrated. Date format should be ''yyyy-MM-dd''.
; ExchangeMailboxName: Specifies the mailbox name on the Microsoft Exchange server that should be used for migration. Used in combination with the [[#ExchangeServerURL|ExchangeServerURL]] and [[#ExchangeServerUsername|ExchangeServerUsername]] parameters. If not defined, the default mailbox for the Exchange user is used. This parameter is also used to define a shared Exchange mailbox, see [[#Exchange mailboxes|Exchange mailboxes]] for details.
; ExchangeServerURL: The URL of the Microsoft Exchange server that hosts the mailbox to be migrated. Only used, when [[#PSTFile|PSTFile]] and [[#ProfileName|ProfileName]] are not defined.
; ExchangeServerUsername: The username of the Exchange account to migrate. Used in combination with the [[#ExchangeServerURL|ExchangeServerURL]] and [[#ExchangeMailboxName|ExchangeMailboxName]] parameters. If not defined, the current windows identity is used.
; ExportAppointmentParticipants: Specifies whether the participants (recipients) of appointments should be migrated or not. If set to 'False', only the Open-Xchange user ([[#Username|Username]]) will participate the exported appointments, otherwise all original participants will be added to the migrated appointment, too.
; ExportAppointmentUIDs: Specifies whether the unique identifiers (UIDs) of appointments should be migrated or not. Details can be found in the chapter [[#Duplicated items|Duplicated items]].
; HistoryFile: The path to the file where the migration tool stores the migration results internally to keep track of which folders already have been migrated successfully.
; IgnoreJunkFolder: Whether to ignore the ''Junk'' folder during the migration or not.
; IgnoreSyncIssuesFolder: Whether to ignore the ''Sync Issues'' folder during the migration or not.
; IgnoreTrashFolder: Whether to ignore the ''Trash'' folder during the migration or not.
; ImportFolderName: Specifies the name of an additional subfolder below the OX default folders that is used as target for the migrated folders. If left blank, the OX default folders are used as target directly.
; LogAutoFlush: Specifies whether the log should be flushed to disk automatically after each entry.
; LogConsole: Whether to output the log to the console or not.
; LogLevel: Specifies the verbosity of the generated log, possible values are ''Error'', ''Warning'', ''Info'' and ''Verbose''.
; LogonExchangeMailbox: It's possible to establish a connection to the an MS Exchange server and to it's global address list prior migrating .pst-files, so that the recipient's SMTP addresses can be resolved. When set to ''True'', the URL of the Exchange server has to be defined in [[#ExchangeServerURL|ExchangeServerURL]].
; LogPOSTData: For debugging reasons, this option enables or disables logging of the complete POST data that is sent to the Open-Xchange server during migration.
; LogTextFile: Specifies the path to the logfile.
; MigrateAppointments: Whether to migrate appointments or not.
; MigrateContacts: Whether to migrate contacts and distribution lists or not.
; MigrateEMails: Whether to migrate e-mail or not.
; MigrateNotes: Whether to migrate sticky notes or not.
; MigrateTasks: Whether to migrate tasks or not.
; Password: The password for the target account ([[#UserName|UserName]]) on the Open-Xchange server.
; ProfileName: The name of the local mail profile to be migrated. Used in combination with the [[#StoreName|StoreName]] parameter.
; PSTFile: The path to the .pst-file to be migrated.
; PSTPassword: The password to access the .pst-file, only needed if the .pst has been protected with a password.
; RecoverableExceptionMaxRetries: Specifies how often a request is repeated in case of possibly recoverable errors.
; ServerURL: The URL of the Open-Xchange server.
; SkipEmptyFolders: Whether to include folders that don't contain any items or not. Subfolders in empty folders are not affected by this setting.
; StoreName: The name of the message store inside the local mail profile. Used in combination with the [[#ProfileName|ProfileName]] parameter.
; TasksMinDate: If defined, only tasks with a due date after this date are migrated. Date format should be ''yyyy-MM-dd''.
; UploadChunkSize: Specifies the number of e-mail items that are sent to the Open-Xchange server during the migration per each request.
; UploadThresholdBytes: Specifies a value in bytes after which an e-mail message chunk is sent to the server, even if when the [[#UploadChunkSize|UploadChunkSize]] is not yet exceeded.
; Username: The user name of the target account on the Open-Xchange server.

=Functional limitations=
* Due to differences in handling recurring tasks between the Open-Xchange server and Microsoft Exchange, recurring tasks are not supported.
* Folder permissions are not transferred to the Open-Xchange server; each new subfolder that is created during the migration gets a set of default permissions (target user has admin permissions).

=Reporting of Bugs=
Please report bugs and missing features via [https://bugzilla.open-xchange.com/enter_bug.cgi?product=Open-Xchange%20MS%20Outlook%20Uploader Open-Xchange Bugzilla]. Many thanks in advance for your support.

Product: Open-Xchange MS Outlook Uploader

=Open-Xchange Microsoft Outlook® Uploader (Open Source via SVN)=

Portions of the Software may use, include third party software, other copyrighted material or Open Source Software. Acknowledgements, licensing terms and disclaimers for such material are contained in separate agreements. Licensee’s use of such material is governed by the terms of the applicable agreements and can be found on the OX web site, are listed under: [http://www.open-xchange.com/de/licenses/open-xchange-microsoft-outlookr-uploader.html http://www.open-xchange.com/de/licenses/open-xchange-microsoft-outlookr-uploader.html]

==Compile from sources==

=== Download and install Outlook Redemption ===

The Open-Xchange Microsoft Outlook Uploader requires the Outlook Redemption library® by Dmitry Streblechenko. As the distributable version of Redemption cannot be used in open source projects, it is not included in the repository. However, for development purposes only, you can download a copy of the library at [http://www.dimastr.com/redemption/ http://www.dimastr.com/redemption/] and install it on your development PC.

=== Checkout the sources from Subversion ===

The source code for the Open-Xchange Microsoft Outlook® Uploader is available in a public Subversion repository. To checkout the latest sources, use the following command:

svn --username anonymous checkout https://svn.open-xchange.com/migration/OXUploader

=== Build using Visual Studio® ===

The Open-Xchange Microsoft Outlook® Uploader can be compiled easily using Visual Studio 2008®. For both the interactive and the commandline version of the migration tool, there are C# project files (.csproj) in the PST2OX and the PST2OXc subdirectories (PST2OX is the 'codename' of the migration tool). Just open the project file in Visual Studio and build the project.

OX Outlook Uploader

2011-10-17T06:44:33Z

217.7.151.106: /* Windows System */

=Open-Xchange Microsoft Outlook® Uploader=

Open-Xchange provides Open-Xchange Microsoft Outlook® Uploader (short: ''OXUploader''), a migration tool to export data from Microsoft Outlook® or from a Microsoft Exchange Server® to the Open-Xchange Server.

=Features=
* Migration of E-Mails, appointments, contacts, distribution lists, tasks and sticky notes
* Folder structure is preserved, subfolders are created as necessary
* Attachments of E-Mails and other objects are migrated
* Support for recurring appointments and participants
* Migration of .pst-files
* Migration of data files from installed mail profiles
* Migration of Microsoft Exchange mailboxes
* Easy to use 3-step interactive wizard to configure the migration
* Unattended mode to perform migrations without user interaction
* Commandline interface to automate batch migrations

=Prerequisites=
The OXUploader migration tool is installed on a windows system having access to the data that should be migrated. The data is then migrated from there to the Open-Xchange server. Please ensure that the following requirements are met before installing the tool:

==Windows System==
* Latest Versions of Windows XP, Windows Server 2003
* Latest Versions of Microsoft Office Outlook® (2002/XP, 2003, 2007 SP1
or 2010 SP1, 32-bit) or Microsoft® Exchange Server or standalone
versions of Extended MAPI (Exchange 5.5 through 2010)
* Microsoft® .NET Framework 2.0

==Open-Xchange Server==
* Latest Version of the Open-Xchange Serve
* The user account(s) for which the data should be migrated should already have been created

=Download and installation=

To download the Open-Xchange Microsoft Outlook® Uploader installation packages and Release Notes, follow this [http://software.open-xchange.com/OX6/migration/Outlookuploader/ link]

After the download of the package, you can start the installation by double-clicking on the package. Please follow the installation steps in the wizard. The installation does not require administrative rights.

=Usage (interactive mode)=

{|
| [[image:OXUploader_Wizard_1.png|thumb]] ||
==1. Choose the migration source==
* First, either choose to migrate a personal storage file (.pst file), a data store from the local mail profiles, or an Exchange server mailbox.
* Depending on your choice, you can specify the migration source in the next step.
|-
| [[image:OXUploader_Wizard_2a.png|thumb]] ||
==2a. Select a personal storage file to migrate==
* When clicking on Browse the standard folder for saving .pst files opens.
* As some .pst files are password protected the password can be entered in the second field.
* When having chosen a file, click on Next.
|-
| [[image:OXUploader_Wizard_2b.png|thumb]] ||
==2b. Select a data file from a profile to migrate==
* Select one of the existing profiles from the drop-down menu.
* Select a store from the profile.
* Finally, enter a password if needed.
* To proceed, click Next.
|-
| [[image:OXUploader_Wizard_2c.png|thumb]] ||
==2c. Select an Exchange Server mailbox to migrate==
* Enter the URL of the Microsoft Exchange server.
* Select the username of the the account on the Exchange server.
* Click on "Logon..." to connect to the Exchange server and fetch the available mailboxes.
* When being asked, enter your password to logon to the Exchange server
* Select one of the existing mailboxes from the drop-down menu.
* To proceed, click Next.
|-
| [[image:OXUploader_Wizard_3.png|thumb]] ||
==3. Please enter information about the server==
* In the Server URL field, enter the Open-Xchange Server address.
* Enter your username in the second field.
* Enter your password in the third field.
* In order to make further settings, activate the "Configure advanced settings" checkbox.
* To proceed, click on Next.
|-
| [[image:OXUploader_Wizard_4.png|thumb]] ||
==4. Configure advanced options==
* If the folders should be migrated into a subfolder, enter it's name in the first field.
* In case not all mail folders are to be exported, the folders can be selected by clicking on the "Select..." button.
* Select the type of items to be migrated by marking the apporpiate checkboxes, and optionally define a minimum date for the items.
* In order to ignore the "Trash", "Junk" or "Sync Issues" folders for the migration, activate the respective checkbox.
* If empty folders should be skipped, activate the respective checkbox.
* If the target folders should be emptied before items are migrated into them, activate the respective checkbox.
|-
| [[image:OXUploader_Wizard_5.png|thumb]] ||
==5. Migration in process==
* This window displays the status and a log protocol of the migration.
* When the process is finished, click on Next.
|-
| [[image:OXUploader_Wizard_6.png|thumb]] ||
==6. Migration completed==
* This window displays an overview of the migration and you can view the log file by clickin on the respective button.
* To close the wizard, click on Finish.
|}

=Usage (unattended mode)=

The migration tool can be started in a special "batch mode", where no user interaction is necessary. The options for the migration can be set in the configuration files, or passed via the commandline when starting the tool, see (3). When the parameter "batchmode" is "true", the migration starts automatically. In this case, at least the following settings have to be available, either supplied via the commandline or defined in the configuration file:
* Username
* ServerURL
* PSTFile ''or'' ProfileName and StoreName ''or'' ExchangeServerURL
* Password ''or'' AdminUser and AdminPassword

For example, to migrate the .pst-file "c:\test.pst", a command could look
like:
<pre>OXUploaderC.exe -batchmode true -pstfile "c:\test.pst" -serverurl "http://ox.example.invalid" -username test -password secret</pre>

Multiple instances of the tool can be run simultaneously from one or multiple client machines, more information can be found in (6).

=Configuration=

==Configuration files==

The application's configuration settings can be adjusted in config files, both for the OXUploader.exe main application for interactive mode and for the commandline version of the tool OXUploaderC.exe (see below). The files are named as the corresponding executable, with the file extension ".config": OXUploader.exe.config and OXUploaderC.exe.config respectively. A description of each parameter can be found in [[#Configuration parameters|Configuration parameters]]

==Commandline parameters==

Furthermore, the application can be started with commandline parameters. All supplied options overwrite the default settings from the configuration file, which are assumed if an option is missing. The following parameters are recognized:
<pre>-adminuser <Admin username on the OX server (for admin migration)>
-adminpassword <Admin password on the OX server (for admin migration)>
-appointmentsmindate <Minimum date of appointments to be migrated>
-batchmode <true/false>
-clearfolders <true/false>
-emailssmindate <Minimum date of e-mails to be migrated>
-exchangemailboxname <Name of the Exchange mailbox to migrate>
-exchangeserverurl <URL of the Exchange server>
-exchangeserverusername <Username on the Exchange server>
-exportappointmentparticipants <true/false>
-exportappointmentuids <true/false>
-ignorejunkfolder <true/false>
-ignoresyncissuesfolder <true/false>
-ignoretrashfolder <true/false>
-importfoldername <Name of the migration target subfolder>
-logautoflush <true/false>
-logconsole <true/false>
-loglevel <off/error/warning/info/verbose>
-logonexchangemailbox <true/false>
-logpostdata <true/false>
-logtextfile <Path to logfile>
-migrateappointments <true/false>
-migratecontacts <true/false>
-migrateemails <true/false>
-migratenotes <true/false>
-migratetasks <true/false>
-password <Password on the OX server>
-profilename <Name of the profile>
-pstfile <Path to PST file>
-pstpassword <Password for the PST file>
-serverurl <URL of the OX server>
-skipemptyfolders <true/false>
-storename <Name of the store inside the profile>
-tasksmindate <Minimum date of tasks to be migrated>
-uploadchunksize <Number of uploaded mails per request>
-uploadthresholdbytes <Threshold of bytes for sending forced>
-username <Username on the OX server>
-recoverableexceptionmaxretries <max. retries after recoverable error>
</pre>

=Misc=

The following chapters contain some advanced information and configration options for the OXUploader migration tool.

==Performance considerations==

The time needed to perform a migration correspondends with the size of the .pst file, of course. So, for large mailboxes, this could be a quite time intensive task, and may be improved in knowledge of the following observations, especially when performing multiple simultaneous batch migrations.
The I/O-ratio is about the following: Per each byte read from disk, about 0.65 bytes are written to disk, and 0.12 bytes are sent to the server. This is caused by the fact that the messages read out from the .pst-file are exported to RFC822 .eml files first, then those files are loaded again before finally sending them to the server. Therefore, the throughput of the local file system should be as fast as possible. Since the temporary created RFC822 e-mail files are created in the user's temp folder, it would be best to move the location to a separate location as the .pst-file - another hdd, maybe even a ramdisk for the temp directory would make sense for heavy batch migrations. It's also recommended to temporarily disable virus protection and indexing services during the migration, and Outlook 2007 should be preferred against Outlook 2003.

==Limitations when running multiple instances==

When executing multiple migrations simulataneously from one machine, each instance of the tool must have exclusive access to the .pst-file it is migrating. Furthermore, each instance must use a different logfile. The tool relies on Outlook, and so it also can't work around Outlooks own limitations, especially as Outlook is designed as client application. More details can be found at the knowledge base article here: http://support.microsoft.com/kb/257757/en-us .

==Admin migration==

When the server is configured appropiate, the migration tool can also be used to import .pst-files into the OX account of the specified user, without the need to supply the user's password. Therefore, the username and password of a special admin user is needed for authentication against the OX server.
For example, to migrate the .pst-file "c:\test.pst" into the account "test", a command could look like:
<pre>OXUploaderC.exe -batchmode true -pstfile "c:\test.pst" -serverurl "http://ox.example.invalid" -username test -adminuser admin -adminpassword secret</pre>

==Personal storage files==

Sometimes .pst-files are broken our corrupted, and the migration tool may not be able to open them correctly, or opening them takes a very long time when the internal repair operations take place.
To reduce the impact of broken .pst-files, it's recommended to check the integrity of the files using Microsofts SCANPST.exe tool, see http://support.microsoft.com/kb/287497 . Sadly this utility is designed to run interactively, but there are some utilities out there that automate the SCANPST.exe tool to be run from the commandline, pointing to the .pst-file to scan, for example cmdscan.exe from http://www.olfolders.de/Lang/English/OLfix/download.htm . Doing so, one would be able to incorporate a SCANPST.exe launch prior a batch call to the migration tool, e.g. the following command could be invoked to scan and repair the .pst file "c:\test.pst", passing the path to the SCANPST.exe location:
<pre>cmdscan.exe -rename "c:\Program Files (x86)\Microsoft Office\Office12\SCANPST.EXE" "c:\test.pst"</pre>

==Duplicated items==

Migrating the same items into the same target folder multiple times usually results in the items getting duplicated on the server.
An exception to this rule are appointments with unique identifiers (UIDs), see http://www.ietf.org/rfc/rfc2445.txt, chapter 4.8.4.7, for details. To avoid importing an appointment with the same identifier multiple times, the server rejects an appointment when the UID already exists on the server. To force the migration of appointments regardless of their UIDs, the tool optionally removes the UIDs from the appointment. The relevant setting is named "ExportAppointmentUIDs", when set to "False", existing UIDs are removed before sending them to the server.
Furthermore, the migration tool has an option to clear the folder contents before triggering the export. When "ClearFolders" is set to "True", the target folder is emptied prior to the items being exported. Note that any existing data in these folders will be permanently lost.

==Exchange mailboxes==

Instead of using a local mail profile or a .pst file for migration, it's also possible to logon to and migrate an Exchange mailbox directly. It's recommeded that the migration tool is executed inside the exchange domain by the owner of the mailbox.
To perform an administrative migration for other user's mailboxes, the following preconditions must be met:
* Ensure the target account already has been created on the OX server
* Grant the administrating user "Receive As" permissions to the mailbox store of all accounts that should be migrated, details can be found at http://support.microsoft.com/default.aspx?scid=kb;EN-US;821897 and http://msexchangeteam.com/archive/2006/01/25/418099.aspx
* The migration tool is ececuted by the administrative user, who already should be logged on to the exchange domain
The administrative migration can only be executed from the commandline in "batch mode", see (5) for details. The mailbox or the name of the user that is going to be migrated needs to be specified inside the commandline parameter "exchangemailboxname". For example, to migrate the mailbox of exchange user "test" to the Open-Xchange account with username "test", combined with admin migration at the OX server (see (6c) for details), one could execute the migration tool in the following way:
<pre>OXUploaderC.exe -batchmode true -exchangeserverurl 192.168.0.4 -exchangemailboxname test -serverurl "http://ox.example.invalid" -username test -adminuser admin -adminpassword secret</pre>
Or, if the password of the OX user is available:
<pre>OXUploaderC.exe -batchmode true -exchangeserverurl 192.168.0.4 -exchangemailboxname test -serverurl "http://ox.example.invalid" -username test -password secret</pre>

==Administrative installation==

The OXUploader migration tool itself can be installed without the need for elevated access rights by the end user, as the installer only accesses the local non-roaming application data directory and the HKCU hive in the registry. It can't be installed 'per machine', which means that it is not allowed to set the value of the ALLUSERS msi property to "1".
The tool can be pre-configured for the end-users by setting public properties at the commandline for the installation process. These are processed by the installer and then written into the tool's config-file. The following parameters can be adjusted (the values in square brackets that are listed below indicate the default values of the properties when not overridden by the msi commandline - so that would be the default pre-configuration):
<pre>ADMINUSER []
ADMINPASSWORD []
BATCHMODE [False]
CLEARFOLDERS [False]
EXPORTAPPOINTMENTPARTICIPANTS [True]
EXPORTAPPOINTMENTUIDS [True]
IGNOREJUNKFOLDER [True]
IGNORETRASHFOLDER [True]
IMPORTFOLDERNAME []
LOGAUTOFLUSH [True]
LOGCONSOLE [False]
LOGLEVEL [Info]
LOGTEXTFILE [.\pst2ox.log]
MIGRATEAPPOINTMENTS [True]
MIGRATECONTACTS [True]
MIGRATEEMAILS [True]
MIGRATENOTES [True]
MIGRATETASK [True]
PASSWORD []
PROFILENAME []
PSTFILE []
PSTPASSWORD []
SERVERURL [http://]
SKIPEMPTYFOLDERS [True]
STORENAME []
UPLOADCHUNKSIZE [25]
UPLOADTHRESHOLDBYTES [2097152]
OXUSERNAME []
RECOVERABLEEXCEPTIONMAXRETRIES [3]
</pre>

For example, to predefine a Server URL that should be used for the
migration afterwards, one would execute e.g.:
<pre> "Open-Xchange Outlook Uploader.msi" SERVERURL="http://ox.example.invalid"</pre>

==Address Resolution==

While the Open-Xchange server uses SMTP as the only recipient address type, data from Microsoft Exchange might contain several additional address types. To migrate such Exchange data to the Open-Xchange server, each e-mail recipient or particpiant of an appointment or task needs a valid SMTP address. While the migration tool tries to retrieve the SMTP address of message recipients in different ways, sometimes there might be recipients that can't be resolved without a connection to the Microsoft Exchange server / Active Directory and it's global address lists. Especially, this may happen with .pst-files that were created using Microsofts EXMERGE tool.
In order to resolve that issue, the OXUploader migration tool can establish a connection to the exchange server and to it's global address list prior migrating a .pst-file to the Open-Xchange server, so that the recipient's SMTP addresses can be resolved. To do so, there are two parameters that can be set to logon to the exchange server prior migrating the .pst-file: [[#ExchangeServerURL|ExchangeServerURL]] and [[#ExchangeServerUsername|ExchangeServerUsername]]. The username parameter is optional (if not defined, the identity of the current windows user is used) and normally should not need to be set in batch-mode to prevent a windows logon prompt.
For example, to logon to the exchange server at "192.168.0.4" and perform an admin migration for the username "test" in unattended mode, a command could look like:
<pre>OXUploaderC.exe -batchmode true -exchangeserverurl 192.168.0.4 -serverurl "http://ox.example.invalid" -username test -adminuser admin -adminpassword secret -pstfile ".\test.pst" -logtextfile ".\test.log"</pre>

=Configuration parameters=
This chapter describes all possible configuration parameters that can be found in the OXUploader.exe.config / OXUploaderC.exe.config configuration files or can be passed to the migration tool from the commandline.

; AdminPassword: The password associated with the administrator user ([[#AdminUser|AdminUser]]) on the Open-Xchange server. Only used when performing [[#Admin_migration|admin migration]].
; AdminUser: The username of the administrator user on the Open-Xchange server. Only used when performing [[#Admin_migration|admin migration]].
; AppointmentsMinDate: If defined, only appointments that end after this date are migrated. Recurring appointments are migrated, if the end date of the series has not been set, or if the end date of the series is not after this defined value. Date format should be ''yyy-MM-dd''.
; BatchMode: Specifies whether the tool should be run in a special batchmode without user interaction or not, see [[#Usage_(unattended_mode)|unattended mode]] for details.
; ClearFolders: When set to 'True', the migration tool clears the target folder contents before exporting items to that folders. Existing subfolders are not affected by this setting, only the folder's contents. Also, the folder clear-command is only executed for folders that are actually migrated, not for ignored or skipped folders.
; EMailsMinDate: If defined, only e-mails that were sent or received after this date are migrated. Date format should be ''yyyy-MM-dd''.
; ExchangeMailboxName: Specifies the mailbox name on the Microsoft Exchange server that should be used for migration. Used in combination with the [[#ExchangeServerURL|ExchangeServerURL]] and [[#ExchangeServerUsername|ExchangeServerUsername]] parameters. If not defined, the default mailbox for the Exchange user is used. This parameter is also used to define a shared Exchange mailbox, see [[#Exchange mailboxes|Exchange mailboxes]] for details.
; ExchangeServerURL: The URL of the Microsoft Exchange server that hosts the mailbox to be migrated. Only used, when [[#PSTFile|PSTFile]] and [[#ProfileName|ProfileName]] are not defined.
; ExchangeServerUsername: The username of the Exchange account to migrate. Used in combination with the [[#ExchangeServerURL|ExchangeServerURL]] and [[#ExchangeMailboxName|ExchangeMailboxName]] parameters. If not defined, the current windows identity is used.
; ExportAppointmentParticipants: Specifies whether the participants (recipients) of appointments should be migrated or not. If set to 'False', only the Open-Xchange user ([[#Username|Username]]) will participate the exported appointments, otherwise all original participants will be added to the migrated appointment, too.
; ExportAppointmentUIDs: Specifies whether the unique identifiers (UIDs) of appointments should be migrated or not. Details can be found in the chapter [[#Duplicated items|Duplicated items]].
; HistoryFile: The path to the file where the migration tool stores the migration results internally to keep track of which folders already have been migrated successfully.
; IgnoreJunkFolder: Whether to ignore the ''Junk'' folder during the migration or not.
; IgnoreSyncIssuesFolder: Whether to ignore the ''Sync Issues'' folder during the migration or not.
; IgnoreTrashFolder: Whether to ignore the ''Trash'' folder during the migration or not.
; ImportFolderName: Specifies the name of an additional subfolder below the OX default folders that is used as target for the migrated folders. If left blank, the OX default folders are used as target directly.
; LogAutoFlush: Specifies whether the log should be flushed to disk automatically after each entry.
; LogConsole: Whether to output the log to the console or not.
; LogLevel: Specifies the verbosity of the generated log, possible values are ''Error'', ''Warning'', ''Info'' and ''Verbose''.
; LogonExchangeMailbox: It's possible to establish a connection to the an MS Exchange server and to it's global address list prior migrating .pst-files, so that the recipient's SMTP addresses can be resolved. When set to ''True'', the URL of the Exchange server has to be defined in [[#ExchangeServerURL|ExchangeServerURL]].
; LogPOSTData: For debugging reasons, this option enables or disables logging of the complete POST data that is sent to the Open-Xchange server during migration.
; LogTextFile: Specifies the path to the logfile.
; MigrateAppointments: Whether to migrate appointments or not.
; MigrateContacts: Whether to migrate contacts and distribution lists or not.
; MigrateEMails: Whether to migrate e-mail or not.
; MigrateNotes: Whether to migrate sticky notes or not.
; MigrateTasks: Whether to migrate tasks or not.
; Password: The password for the target account ([[#UserName|UserName]]) on the Open-Xchange server.
; ProfileName: The name of the local mail profile to be migrated. Used in combination with the [[#StoreName|StoreName]] parameter.
; PSTFile: The path to the .pst-file to be migrated.
; PSTPassword: The password to access the .pst-file, only needed if the .pst has been protected with a password.
; RecoverableExceptionMaxRetries: Specifies how often a request is repeated in case of possibly recoverable errors.
; ServerURL: The URL of the Open-Xchange server.
; SkipEmptyFolders: Whether to include folders that don't contain any items or not. Subfolders in empty folders are not affected by this setting.
; StoreName: The name of the message store inside the local mail profile. Used in combination with the [[#ProfileName|ProfileName]] parameter.
; TasksMinDate: If defined, only tasks with a due date after this date are migrated. Date format should be ''yyyy-MM-dd''.
; UploadChunkSize: Specifies the number of e-mail items that are sent to the Open-Xchange server during the migration per each request.
; UploadThresholdBytes: Specifies a value in bytes after which an e-mail message chunk is sent to the server, even if when the [[#UploadChunkSize|UploadChunkSize]] is not yet exceeded.
; Username: The user name of the target account on the Open-Xchange server.

=Functional limitations=
* Due to differences in handling recurring tasks between the Open-Xchange server and Microsoft Exchange, recurring tasks are not supported.
* Folder permissions are not transferred to the Open-Xchange server; each new subfolder that is created during the migration gets a set of default permissions (target user has admin permissions).

=Reporting of Bugs=
Please report bugs and missing features via [https://bugzilla.open-xchange.com/enter_bug.cgi?product=Open-Xchange%20MS%20Outlook%20Uploader Open-Xchange Bugzilla]. Many thanks in advance for your support.

Product: Open-Xchange MS Outlook Uploader

=Open-Xchange Microsoft Outlook® Uploader (Open Source via SVN)=

Portions of the Software may use, include third party software, other copyrighted material or Open Source Software. Acknowledgements, licensing terms and disclaimers for such material are contained in separate agreements. Licensee’s use of such material is governed by the terms of the applicable agreements and can be found on the OX web site, are listed under: [http://www.open-xchange.com/de/licenses/open-xchange-microsoft-outlookr-uploader.html http://www.open-xchange.com/de/licenses/open-xchange-microsoft-outlookr-uploader.html]

==Compile from sources==

=== Download and install Outlook Redemption ===

The Open-Xchange Microsoft Outlook Uploader requires the Outlook Redemption library® by Dmitry Streblechenko. As the distributable version of Redemption cannot be used in open source projects, it is not included in the repository. However, for development purposes only, you can download a copy of the library at [http://www.dimastr.com/redemption/ http://www.dimastr.com/redemption/] and install it on your development PC.

=== Checkout the sources from Subversion ===

The source code for the Open-Xchange Microsoft Outlook® Uploader is available in a public Subversion repository. To checkout the latest sources, use the following command:

svn --username anonymous checkout https://svn.open-xchange.com/migration/OXUploader

=== Build using Visual Studio® ===

The Open-Xchange Microsoft Outlook® Uploader can be compiled easily using Visual Studio 2008®. For both the interactive and the commandline version of the migration tool, there are C# project files (.csproj) in the PST2OX and the PST2OXc subdirectories (PST2OX is the 'codename' of the migration tool). Just open the project file in Visual Studio and build the project.

Template:Oxinstaller

2011-10-12T08:51:48Z

217.7.151.106:

'''Important:''' You should have your Open-Xchange license code at hand. If you do not plan to license Open-Xchange, you can use the option ''--no-license'' instead. Please also check [[OXReportClient]] documentation for more information about configuring a supported and maintained Open-Xchange server.

$ /opt/open-xchange/sbin/oxinstaller --add-license=YOUR-OX-LICENSE-CODE \
--servername=oxserver --configdb-pass=db_password \
--master-pass=admin_master_password --ajp-bind-port=localhost --servermemory 512

'''Note:''' In a clustered setup, <tt>--ajp-bind-port</tt> must be set to <tt>*</tt>

Template:OX HE Tutorial Next

2011-10-11T15:45:54Z

217.7.151.106: /* Branding */

= Recommended Optional Next Steps =

You will find plenty of additional documentation for customization of OX in our knowledge base [http://oxpedia.org]

When the main setup is completed, we recommend to start with the following articles to enhance your system and to become more attractive for your users.

== Automated Frontend Tests ==

It is a good idea, to verify the functionality of your freshly set up and integrated system. Our QA department does that with tests, running automatically on the web frontend. We release this tests with every release and recommend you to use them to verify your environment with every update.

Read more about [[Automated_GUI_Tests]]

== Monitoring / Statistics ==

It is recommended to implement at least a minimal monitoring/Statistics solution to get an overview of the systems health. If you have a support contract with Open-Xchange, it is very helpful, if the support can access the monitoring graphs. There are example scripts for a basic monitoring with [[http://munin-monitoring.org/ Munin]] available.

Read more about installing and configuring [[OX_munin_scripts|Munin scripts for Open-Xchange]]

== Upsell Plugin / Webmail Replacement ==

If you want to use your OX based Webmail system to upsell premium functions like full groupware functionality or like push to mobile phones, it is strongly recommended to use the in-app sales process.

Read more about [[Upsell]]



== Branding ==

If you want OX to look more like your own Corporate Identity, including your logo, product name and maybe your colors, this can be easily achieved by changing the logos and stylesheets.

Read more about: [[Gui_Theming_Description]]

Read more about: [[Gui_Plugin_Development|Gui Branding Plugins]]

Read more about: [[CCBranding|Branding via the ConfigCascade]]

== Backup ==

It is recommended to run regular backups for your OX installation. This can be done with every backup solution for Linux.

Read more about [[Open-Xchange_backup|Backup your Open-Xchange installation]]

== OXMobileApp (pre Beta) ==

This GUI is designed to run in the mobile browsers and brings basic Open-Xchange functionality to all available HTML 5 capable devices.

Read more about [[OXMobileApp]]

OX munin scripts

2011-09-15T12:51:45Z

217.7.151.106: /* munin and munin-node */

= How to install Munin scripts for Open-Xchange=

== Prerequisites ==

Munin-Node must be installed prior installing the Munin scripts package for Open-Xchange.
Note that SUSE LINUX Enterprise Server does not include Munin.

To get the munin graphs generated for the webserver, munin needs to be installed and configured, too. For more information, please visit http://munin-monitoring.org/.

If you are running RHEL6 you need to enable to optional RHN channel to get munin. Also you need to add the EPEL repo. An instruction for this can be found on https://fedoraproject.org/wiki/EPEL6-FAQ.

{{InstallPlugin|pluginname=open-xchange-munin-scripts|sopath=unsupported/repo|reponame=oxmunin}}

== munin and munin-node ==
munin collects the prepared data (by munin-node) from the nodes. Munin can run on the same system as the node, but if you want to monitor more nodes it makes sense to have it on another server running without Open-Xchange.

munin-node has to be installed on every Open-Xchange server you want to monitor

== Configuring munin-node scripts for Open-Xchange ==

The configuration of the scripts is done automatically. The database pool monitoring scripts will get configured only if the Open-Xchange server is running when installing the open-xchange-munin-scripts packages.

The default configuration allows connections from the localhost, means that munin has to run on the same host. If you have already a munin host running or decided to use not the same as the Open-Xchange server, you have to change the file <code>/etc/munin/munin-node.conf</code> on each node you want to monitor:

# A list of addresses that are allowed to connect. This must be a
# regular expression, since Net::Server does not understand CIDR-style
# network notation unless the perl module Net::CIDR is installed. You
# may repeat the allow line as many times as you'd like

allow ^127\.0\.0\.1$

Replace the <code>allow</code> line with the IP of the munin host server IP.

== Configure Munin host ==
Make sure you have the munin and apache packages installed. If you just monitor the localhost, you have to do nothing. Adding other nodes via the <code>/etc/munin/munin.conf</code> file:

# a simple host tree
[localhost.localdomain]
address 127.0.0.1
use_node_name yes

add the needed nodes like this example.

By default you can reach the munin page only from localhost, so you usually have to allow other hosts or networks to connect. In <code>/etc/apache2/conf.d/munin</code> you can add them:

Allow from localhost 127.0.0.0/8 ::1 # the default setting
Allow from 10.99.0.0/8 # added network

The munin webpage is located at <code>http://yourhost_where_munin_is_running.org/munin</code>.

[[Category: OX6]]

OX munin scripts

2011-09-15T12:48:31Z

217.7.151.106: /* Configuring Munin scripts for Open-Xchange */

= How to install Munin scripts for Open-Xchange=

== Prerequisites ==

Munin-Node must be installed prior installing the Munin scripts package for Open-Xchange.
Note that SUSE LINUX Enterprise Server does not include Munin.

To get the munin graphs generated for the webserver, munin needs to be installed and configured, too. For more information, please visit http://munin-monitoring.org/.

If you are running RHEL6 you need to enable to optional RHN channel to get munin. Also you need to add the EPEL repo. An instruction for this can be found on https://fedoraproject.org/wiki/EPEL6-FAQ.

{{InstallPlugin|pluginname=open-xchange-munin-scripts|sopath=unsupported/repo|reponame=oxmunin}}

== munin and munin-node ==
munin collects the prepared data from the nodes by munin-node. Munin can run on the same system as the node, but if you want to monitor more nodes it makes sense to have it on another server running without Open-Xchange.

munin-node has to be installed on every Open-Xchange server you want to monitor

== Configuring munin-node scripts for Open-Xchange ==

The configuration of the scripts is done automatically. The database pool monitoring scripts will get configured only if the Open-Xchange server is running when installing the open-xchange-munin-scripts packages.

The default configuration allows connections from the localhost, means that munin has to run on the same host. If you have already a munin host running or decided to use not the same as the Open-Xchange server, you have to change the file <code>/etc/munin/munin-node.conf</code> on each node you want to monitor:

# A list of addresses that are allowed to connect. This must be a
# regular expression, since Net::Server does not understand CIDR-style
# network notation unless the perl module Net::CIDR is installed. You
# may repeat the allow line as many times as you'd like

allow ^127\.0\.0\.1$

Replace the <code>allow</code> line with the IP of the munin host server IP.

== Configure Munin host ==
Make sure you have the munin and apache packages installed. If you just monitor the localhost, you have to do nothing. Adding other nodes via the <code>/etc/munin/munin.conf</code> file:

# a simple host tree
[localhost.localdomain]
address 127.0.0.1
use_node_name yes

add the needed nodes like this example.

By default you can reach the munin page only from localhost, so you usually have to allow other hosts or networks to connect. In <code>/etc/apache2/conf.d/munin</code> you can add them:

Allow from localhost 127.0.0.0/8 ::1 # the default setting
Allow from 10.99.0.0/8 # added network

The munin webpage is located at <code>http://yourhost_where_munin_is_running.org/munin</code>.

[[Category: OX6]]

ASE Backup de

2011-07-25T11:44:21Z

217.7.151.106: /* Wiederherstellung Open-Xchange Filestore, Database */

= OX ASE - Backup & Wiederherstellung des Systems =

Open-Xchange-Anwender wünschen sich volle Flexibilität, um ihr individuelles Backup-Konzept mit professionellen Backup-Tools zu realisieren. Entsprechend haben wir diese umfangreiche Dokumentation verfasst, welche verschiedene Backup-Strategien vorstellt und die Vor- und Nachteile der unterschiedlichen Methoden vorstellt. Die vollständige Sicherung des E-Mail- und Groupware-Servers inklusive Betriebssystem und Filesystem ist nach unserer Überzeugung ein absolutes MUSS für jede Organisation, die einen eigenen E-Mail- und Groupware-Server betreibt.

== Backup eines OX ASE-Systems ==

UCS, das von OX ASE als Basis verwendet wird, folgt dem Filesystem Hierarchy Standard, einer Richtli- nie, die die Aufteilung der Daten in der Unix-Dateisystemhierarchie beschreibt. Dies erlaubt eine effiziente Trennung zwischen lokal erzeugten Dateien und Daten, die im Rahmen der Installation erstellt werden.

=== Sicherung der LDAP-Daten ===

Auf einem OXASE-System in der Single Server-Variante ist die Sicherung des LDAP-Datenbestands erforderlich. In der Multi Server-Variante muss die Sicherung des LDAP-Datenbestands nur auf dem Domänencontroller Master erfolgen.

Mit dem folgenden Befehl werden die LDAP-Daten in eine Text-Datei gesichert:
slapcat > LDAP-Daten.ldif

=== Sicherung der lokalen Konfigurationsdateien ===

Die lokalen Konfigurationsdateien werden auf OX ASE-Systemen unterhalb des Verzeichnisses "/etc" gespeichert. In einer Standardinstallation ohne weitere Anpassungen des Administrators werden alle Konfigurationsdateien durch Univention Configuration Registry-Templates abgebildet. Wenn keine lokalen Anpassungen an Konfigurationsdateien oder Templates vorgenommen wurden, reicht es aus, für eine minimale Sicherung die Dateien
/etc/univention/base.conf, /etc/univention/base-forced.conf; /etc/univention/base-schedule.conf
zu sichern.

Wenn Anpassungen an Konfigurationsdateien oder Templates vorgenommen wurden, muss das komplette "/etc"-Verzeichnis gesichert werden. Das Verzeichnis /etc umfasst in aller Regel weniger als 50 MB Daten und sollte daher nach Möglichkeit immer komplett gesichert werden.

=== Sicherung der Benutzerdaten===

Das Heimatverzeichnis des root-Benutzers wird lokal auf jedem System im Verzeichnis /root vorgehalten. Es sollte in das Backup aufgenommen werden. Wenn die Heimatverzeichnisse der weiteren Benutzer nicht auf einer Freigabe sondern lokal gespeichert werden, muss auch das "/home"-Verzeichnis in die Sicherung aufgenommen werden.

=== Sicherung der installierten Pakete===

Die auf dem System installierten Pakete können mit dem Befehl
dpkg --get-selections > paketliste.txt
gesichert werden.

=== Sicherung der Laufzeitdaten ===

Die Laufzeitdaten von System-Programmen (z.B. der Mailspool des Cyrus-IMAPD) und die Logdateien werden unterhalb von /var gespeichert. Auch wenn hier einzelne Daten nicht notwendigerweise gesichert werden müssten ("/var/cache" und "/var/run" enthalten beispielsweise Daten, die nur für die Laufzeit eines Systems bis zum Reboot relevant sind), ist es trotzdem empfehlenswert, das komplette /var-Verzeichnis zu sichern. Außerdem sollte das "/srv"-Verzeichnis gesichert werden.
Es ist zu beachten, dass einige Applikationen eventuell eine gesonderte Sicherung benötigen.

=== Sicherung von Software, die nicht im UCS-Standard-Umfang enthalten ist ===

Wenn Software installiert wurde, die nicht im UCS-Standardpaketumfang enthalten ist, müssen zwei Fälle unterschieden werden:

1. Bei Software, die auch im DEB-Format vorliegt, reicht es diese Pakete in die Sicherung aufzu- nehmen. 
2. Externe Software, die nicht im DEB-Format vorliegt, wird in der Regel nach "/opt" oder "/usr/local" installiert. Diese Verzeichnisse müssen dann ebenfalls gesichert werden.

=== Sicherung der Laufzeitdaten von Open-Xchange===

Die Konfiguration von Open-Xchange wird in dem Verzeichnis "/opt/open-xchange" vorgehalten. Es sollte vollständig in das Backup mitaufgenommen werden. Benutzerdaten werden von OX ASE sowohl in einer MySQL-Datenbank als auch in den registrierten Filestores (als normale Dateien im Dateisystem) vorgehalten.

Es ist wichtig, dass Filestore und Datenbank zum gleichen Zeitpunkt gesichert werden, da Metada- ten über die im Filestore gespeicherten Dateien in der Datenbank vorgehalten werden.

OX ASE speichert den Filestore in der Standardeinstellung im Verzeichnis "/var/oxfilestore". Sofern bereits das gesamte /var-Verzeichnis gesichert wurde, sind die benötigen Dateien dadurch schon abgedeckt. Falls weitere Filestores außerhalb von /var eingerichtet wur- den, sind diese ebenfalls zu sichern. Eine Liste aller Filestores kann über den Befehl
/opt/open-xchange/sbin/listfilestore -A oxadminmaster -P $(</etc/ox-secrets/master.secret)
ermittelt werden.

Die von Open-Xchange verwendete MySQL-Datenbank kann über die MySQL-Standardtools gesichert werden. Zum Erstellen eines Datenbank-Dumps wird der folgende Befehl empfohlen:
mysqldump --all-databases --single-transaction > datenbank-sicherung.mysql

=== Backup von Open-Xchange Filestore, Database===

Ein Backup der Konfiguration Files wird nach jeder Installation oder Update empfohlen. Die Konfiguration ist verfügbar in
/opt/open-xchange/

Die User-Daten sind verfügbar in der Mysql Datenbank sowie als normel Files im Filesystem. Es ist wichtig das der Filestore und die Datenbank zur gleichen Zeit gesichert werden. Der einfachste Weg ist, Snapshots oder ähnliche Mechanismen zu nutzen.

Es können Standarttools für die Ausführung des Filestore-Backup genutzt werden. Das folgende Kommando gibt eine Übersicht über alle verfügbaren Filestore Directories:

/opt/open-xchange/sbin/listfilestore -A oxadminmaster -P $(</etc/ox-secrets/master.secret)

Für das Datenbank-Backup, die Standard Mysql Tools können verwendet werden. Wenn Mysqldump verwendet wird, die folgenden Parameter sind notwendig:
mysqldump -–all-databases -–single-transaction

== Wiederherstellung eines OX ASE-Systems ==
Die folgende Anleitung führt das generelle Vorgehen bei der Wiederherstellung eines OX ASE-Systems auf. Die Wiederherstellung erfordert Erfahrung im Umgang mit UCS und OX ASE und sollte nach Möglichkeit in einer Testumgebung vor Eintreten des “Ernstfalls” simuliert werden.

Die folgenden Schritte sollten in der angegebenen Reihenfolge durchgeführt werden. Nach Abschluss aller Schritte sollte das System neu gestartet werden, um alle Dienste sauber zu initialisieren.

=== Neuinstallation des Systems und Abgleich des Softwarebestandes ===
Das wiederherzustellende System sollte neu installiert werden. Das System, auf dem die LDAP- Daten zurückgespielt werden, muss mit den gleichen Basis-Einstellungen (Rechner- und Domänen- name, Name der LDAP-Basis) installiert werden wie das alte System.

Die Installationsparameter können anhand der Datei "/etc/univention/installation_profile" gesetzt werden. Es ist aber zu beachten, dass diese Datei bei der initialen Installation erzeugt wurde und sich einige Parameter oder Paketnamen geändert haben können.

=== Wiederherstellung der lokalen Konfigurationsdateien ===
Die "/etc/univention/base.conf*"- Dateien sowie "/etc/ldap.secret" und "/etc/machine.secret" sollten zurückgespielt werden. Wurde das komplette "/etc"-Verzeichnis gesichert, sollte das komplette "/etc"-Verzeichnis auf das neue System zurückkopiert werden.

Anschließend sollte als Benutzer root der Befehl
ucr commit
aufgerufen werden. Es löst einen kompletten Rebuild aller über Univention Configuration Registry-Templates generierten Dateien aus.

=== Stoppen der Serverdienste===

Alle Server-Dienste auf dem System sollten durch den Aufruf von
/etc/init.d/DIENST stop
angehalten werden. Um automatische Starts während der folgenden Schritte zu verhindern, ist es sinnvoll über die autostart-Einstellungen der Dienste einen Start zu verhindern, z.B.
ucr set cups/autostart=no

=== Wiederherstellung des Software-Paketbestands===

Die vorher installierten UCS-Pakete sollten anhand der gesicherten Paketliste wieder installiert werden. Dazu muss im ersten Schritt die gesicherte Paketliste wieder eingespielt werden:
dpkg --set-selections < liste.txt
Anschließend kann mit "apt-get" der Paketbestand wieder hergestellt werden (dazu müssen die Repository-Einstellungen wie auf dem alten System gesetzt sein):
apt-get -u dselect-upgrade
Abschließend sollte die Liste der danach installierten Pakete (ermittelbar mit dem Befehl "dpkg --list") abgeglichen werden und ggf. fehlende Pakete mit dem Befehl
univention-install nachinstalliert werden.

Wenn Nicht-UCS-Software installiert war, muss diese sowie ggf. deren Datenbestand ebenfalls zurückgespielt werden.

=== Wiederherstellung der Laufzeitdaten===

Das "/var"-Verzeichnis muss zurückkopiert werden. Das Verzeichnis "/var/run" sollte dabei übersprungen werden.

=== Wiederherstellen der LDAP-Daten/Listener-Notifier-Replikation===

Für das Zurückspielen der LDAP-Daten sind mehrere Schritte notwendig.

Die bei der Installation des System erzeugten initialen LDAP-Daten müssen zunächst entfernt werden. Dazu müssen im Verzeichnis "/var/lib/univention-ldap/ldap/" alle Dateien mit Ausnahme der Datei "DB_CONFIG" entfernt oder verschoben werden. Anschließend können die Daten aus dem LDIF wieder eingespielt werden:
mv /var/lib/univention-ldap/ldap /var/lib/univention-ldap/ldap.old
mkdir /var/lib/univention-ldap/ldap
ucr commit /var/lib/univention-ldap/ldap/DB_CONFIG
slapadd -l LDAP-Daten.ldif
Außerdem sollte der Univention Directory Listener zurückgesetzt werden:
rm -rf /var/lib/univention-directory-listener
mkdir -p /var/lib/univention-directory-listener/
chown listener /var/lib/univention-directory-listener/
Anschließend sollten die betroffenen Dienste neu gestartet werden:
/etc/init.d/slapd start
/etc/init.d/univention-directory-notifier start
/etc/init.d/univention-directory-listener start
Die Neuinitialisierung des Univention Directory Listener kann je nach Menge der im LDAP-Verzeichnis gespeicherten Daten einige Zeit in Anspruch nehmen. In dieser Zeit sollte das System nicht neu gestartet werden.

=== Zurückspielen der Laufzeitdaten von Open-Xchange===

Es wird empfohlen, dass alle Daten unterhalb des Filestore-Basisverzeichnisses (i.d.R. "/var/oxfilestore") gelöscht werden, bevor das Backup des Filestores zurückgespielt wird.

Um Inkonsistenzen zu vermeiden, wird dringend empfohlen, nur Backups von MySQL-Datenbank und Filestore zurückzuspielen, die zum selben Zeitpunkt erstellt wurden. Nach dem Zurückspielen kann über den folgenden Befehl ein Konsistenzcheck durchgeführt werden:
/opt/open-xchange/sbin/checkconsistency

=== Zurücksetzen der Autostart-Einstellungen===

Die UCR-Autostart-Einstellungen, welche in den vorigen Schritten vorgenommen wurden, sollten zurückgesetzt werden.

=== Wiederherstellung Open-Xchange Filestore, Database===

Es wird empfohlen, alle vorhandenen Daten unter dem Filestore Einstiegspunkt zu löschen, zB ""/ var / opt / filestore / *", um Unstimmigkeiten vor dem Wiederherstellen der Sicherungskopie im Filestore.

Der Datenbankdump wird durch folgendes Kommando importiert. Existierende Tabellen sollten nach Möglichkeit im Datenbankserver zuvor gedroppt werden:
mysql -uroot -p$(cat /etc/mysql.secret) < datenbank-sicherung.mysql

Bei der Wiederherstellung der Datenbank und des Filestores, es ist wichtig dies zur gleichen Zeit durchzuführen um Inkonsistenten zu vermeiden. Nach der Wiederherstellung, das Consistency Tool muss gestartet werden:
/opt/open-xchange/sbin/checkconsistency

Es ist möglich einen Single-Kontext Wiederherstellung der MySQL-Datenbank durchzuführen. Dies ist im Installations- und Administrationshandbuch beschrieben: http://software.open-xchange.com/OX6/doc/OX6-Installation-and-Administration.pdf

Versioning and Numbering

2011-07-04T05:33:50Z

217.7.151.106: /* Releases */

=Versioning and Numbering of Open-Xchange Products=

== General Declaration ==
The Open-Xchange GmbH currently release two different generations of the Open-Xchange Collaboration Suite.

Open-Xchange Server 5 has been released as a community edition that uses the version namespace 0.8.x which is published in regular cycles as a source-only release. It is the groundwork for the commercial ''Open-Xchange Server 5'' product line. Commercial products use build numbers starting at "5000". Outlook connectors for this version use build numbers starting at 4.0.

Open-Xchange Server 6 has been initial published in February 2007 and its sourcecode is distributed via a daily synchronized CVS repository and precompiled packages to the Open-Source community. It is the groundwork for the commercial products ''Open-Xchange Advanced Server Edition (powered by Univention)'', ''Open-Xchange Hosting Edition'' and ''Open-Xchange Server Edition''. Version numbers for all releases of the server and client/connector software are all starting with a "6".

Open-Xchange Server 6 is the successor of Open-Xchange Server 5.

Those two software generations differ extremely from each other, they use different backends, different APIs, different code and different user interfaces. They have in common that they are maintained by Open-Xchange GmbH and are at steady improvement by Open-Xchange and the Open-Source community. Those two generations as well as the connectors are not compatible to each other as of different backend technology and data formats. Open-Xchange offers a wide array of client and synchronization software for popular PIM client software like Outlook. There is also a connector for synchronization between Open-Xchange Server 6 and MacOS X native applications, a web interface optimized for mobile devices and several solutions for mobile device synchronization. Partners and the community are working on synchronization solutions for popular platforms like Evolution or Mozilla Thunderbird/Lightning.

=== Abbreviations ===

The Open-Xchange versioning 2009 (After SP5 Update 1) will be structured in the following way: 
'''<generation>.<major release>.<minor release> Rev<build number>''' 

{| border="1" cellpadding="3" cellspacing="0"
!align="left" |Abbreviation
!align="left" |Meaning
!align="left" |Comparison
|-
|<generation>
|The first number is the product generation number. A new generation may contain new architecture, different technology and many more.
|OX 6
|-
|<major release>
|The second version number (major release) indicates significant program changes in terms of added functionality. Major changes to design and enhancements of APIs are possible. All APIs shall be backward compatible, which means, that mainly new functions can be added. If Open-Xchange releases a new major release this will be an even number, unstable interim releases have odd numbers.
|6.10 
|-
|<minor release>
|The third version number (minor releases) indicates an update with consolidated bug fixes and non-intrusive feature enhancements. APIs and database will not be changed if this can be avoided. All changes must be backward compatible.
|6.10.1
|-
|<build number>
|The Rev-number (Revision) shows the progress of the development in single steps
|6.10.1-Rev3
|}
 

=== Release Levels of Open-Xchange ===

These are the new Open-Xchange Release Levels 2009: 

{| border="1" cellpadding="3" cellspacing="0"
!align="left" |OX Release Level (new)
!align="left" |New Generation
!align="left" |Major Release
!align="left" |Minor Release
!align="left" |Program Temporary Fix (PTF)
!align="left" |Public Program Temporary Fix (PTF), Security Fix
|-
| '''OX Release Level (old)'''
| New Generation
| Service Pack
| Maintenance Release
| Program Temporary Fix (PTF)
| Security Fix
|-
|'''Target Audience'''
|All
|Public/All
|Maintenance customers & Partners
|L3 Support Customers, Value Package Partners
|Public/All
|-
|'''Purpose'''
|Provide new technologies
|Provide functional enhancements including Bug Fixes, accumulate earlier PTF’s/ major releases
|Provide common bug fixes for all customers, accumulate previous PTF’s
|Provide fixes for severity level 1/2 tickets, for Support Customer, temporary until next Maintenance Release accumulative
|Fix security holes
|-
|'''Frequency'''
|Open-Xchange Roadmap
|Every 6 to 12 weeks
|Decided by Open-Xchange
|According to SLA
|As soon as required
|-
|'''Support Committment'''
|5 years after First Customer Shippment (FCS)
|6 months after FCS of the Major Release
|Next Major Release
|Next Major Release
|Next Major Release
|-
|'''Requested by'''
|Product Management
|Product Management, Professional Services
|Support, QA, Product Management, Professional Services
|Entitled Customer (Support, Professional Services)
|Entitled Customer (Support, Professional Services)
|-
|'''Compatibility requirements/backward compatibility'''
|
|Database updates, Changes of configuration files
|Backward compatibility to last major release. In urgent cases there could be database updates or configuration file changes
|Backward compatibility to last major release
|Backward compatibility to last major release
|-
|'''Test Efforts OX (QA)'''
|Smoke Tests, Always Tests, Bug Fix Tests, Feature Tests, Dependencies Tests, Heuristic Tests, Performance Tests
|Smoke Tests, Always Tests, Bug Fix Tests, Feature Tests, Dependencies Tests, Heuristic Tests, Performance Tests
|Smoke Test, Always Tests, Bug Fix Tests, Dependencies Tests, Heuristic Tests, Performance Tests
|Smoke Tests, Always Tests, Bug Fix Tests - Support: Fix Approval
|Smoke Tests, Always Tests, Bug Fix Tests - Support: Fix Approval
|-
|'''Test Efforts Customer/Partner'''
|Smoke Tests, Bug Fix Tests, New Feature Tests, Integration Tests
|Smoke Tests, Bug Fix Tests, New Feature Tests, Integration Tests
|Smoke Tests, Bug Fix Tests, Integration Tests
|Smoke Tests, Bug Fix Approval
|Smoke Tests
|-
|}
 

== Open-Xchange Server 6 ==

=== Editions ===
{| border="1" cellpadding="3" cellspacing="0"
!align="left" width="50"|Abbreviation
!align="left" width="200"|Description
!align="left" |Target usage
|-
|OX:HE
|Open-Xchange Hosting Edition
|Designed for organizations that want to provide a scalable, multi-tenant e-mail and collaboration solution to their customers. Focus: Software-as-a-Service offerings
|-
|OX:SE
|Open-Xchange Server Edition
|Designed for medium and large size organizations, educational institutions and public administrations seeking a customizable communication solution. Focus: System Integrators
|-
|OX:SEforUCS
|Open-Xchange Server Edition for Univention Corporate Server
|Integration to in-house customer environments
|-
|OX:ASE
|Open-Xchange Advanced Server Edition
|Designed for small to medium size organizations, educational institutions and public administrations seeking for a customizable and in-house communication solution. Available for single-server (former OX Appliance Edition) and multi-server-setups. Focus: SIs and VARs
|}

=== Releases ===

{| border="1" cellpadding="3" cellspacing="0"
!align="left" |GA
!align="left" |Release Name
|-
| 2007-02-27
| Open-Xchange Hosting Edition
|-
| 2007-03-12
| Open-Xchange Community Release (CVS)
|-
| 2007-06-04
| Open-Xchange Hosting Edition SP1
|-
| 2007-07-19
| Open-Xchange Hosting Edition SP2
|-
| 2007-09-20
| Open-Xchange Hosting Edition SP3
|-
| 2007-11-13
| Open-Xchange Hosting Edition SP3 Update 1
|-
| 2008-09-30
| Open-Xchange Hosting/Server Edition SP4
|-
| 2008-11-05
| Open-Xchange Appliance Edition
|-
| 2008-12-05
| Open-Xchange Hosting/Server Edition SP4 Update 1
|-
| 2008-12-15
| Open-Xchange Appliance Edition Update 1
|-
| 2009-01-22
| Open-Xchange Hosting/Server Edition SP5
|-
| 2009-03-17
| Open-Xchange Hosting/Server Edition SP5 Update 1
|-
| 2009-05-06
| Open-Xchange Appliance Edition Update 2
|-
| 2009-05-29
| Open-Xchange Appliance Edition Update 3
|-
| 2009-07-21
| Open-Xchange Hosting/Server Edition 6.10
|-
| 2009-08-13
| Open-Xchange Appliance Edition Update 4 (6.10
|-
| 2009-09-11
| Open-Xchange Hosting/Server Edition 6.12
|-
| 2009-10-07
| Open-Xchange Appliance Edition Update 5 (6.12)
|-
| 2009-12-01
| Open-Xchange Hosting/Server Edition 6.14
|-
| 2010-01-15
| Open-Xchange Appliance Edition 6.14
|-
| 2010-03-15
| Open-Xchange Hosting/Server Edition 6.16
|-
| 2010-04-19
| Open-Xchange Appliance Edition / Open-Xchange Advanced Server Edition / Open-Xchange Server Edition for UCS 6.16
|-
| 2010-08-30
| Open-Xchange Hosting/Server Edition 6.18
|-
| 2010-10-18
| Open-Xchange Hosting/Server Edition 6.18.1
|-
| 2010-12-15
| Open-Xchange Advanced Server Edition / Open-Xchange Server Edition for UCS 6.18.1 (with UCS 2.4)
|-
| 2010-12-22
| Open-Xchange Hosting/Server Edition 6.18.2
|-
| 2011-02-23
| Open-Xchange Appliance Edition consolidation to Open-Xchange Advanced Server Edition/Server Edition for UCS 6.18.2 (with UCS 2.4)
|-
| 2011-03-22
| Open-Xchange Hosting/Server 6.20
|-
| 2011-05-05
| Open-Xchange Advanced Server Edition/SE for UCS 6.20
|-

|}

=== What version do I have installed ===

Check [[UpdatingOXPackages#What_Service_Pack_do_I_have_installed.3F|this article]] to find out.

[[Category: General]]

OX6:Available Translations

2011-06-21T09:05:53Z

217.7.151.106: /* Available Language Translations */

= Open-Xchange Server Translations =

=== Available Language Translations ===

{| border="1" cellpadding="3" cellspacing="0"
!align="left" |Language
!align="left" |Status
!align="left" |Documentation
!align="left" |Contributor
!align="left" |Contact
|-
| [[Image:Flag_us.png]] US English
| Supported and included in standard packages
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-English.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_gb.png]] British English
| Supported and included in standard packages
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-English.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_fr.png]] French
| Supported and included in standard packages
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-French.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_de.png]] German
| Supported and included in standard packages
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-German.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_es.png]] Spanish
| [http://software.open-xchange.com/OX6/stable/ Supported]
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Spanish.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_nl.png]] Dutch
| [http://software.open-xchange.com/OX6/stable/ Supported]
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Dutch.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_pl.png]] Polish
| [http://software.open-xchange.com/OX6/stable/ Supported]
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Polish.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:japanese.jpeg]] Japanese
| [http://software.open-xchange.com/OX6/stable/ Supported]
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-User-Guide-Japanese.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_it.png]] Italian
| [http://software.open-xchange.com/OX6/stable/ Supported]
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Italian.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:china.jpg]] Simplified Chinese
| [http://software.open-xchange.com/OX6/stable/ Supported]
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-simplified_Chinese.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_se.png]] Swedish
| [http://software.open-xchange.com/OX6/stable/ Unsupported]
| Online Help (for SP5)
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_no.png]] Norsk
| [http://www.open-xchange.com/forum/showthread.php?t=3400 Forum]
| --
| Erol Haagenrud
|
|-
| [[Image:Flag_dk.png]] Dansk
| [http://software.open-xchange.com/OX6/stable/ Unsupported]
| --
| Milan / Netsite.dk
|
|-
| [[Image:Flag_tr.png]] Turkish
| [http://software.open-xchange.com/OX6/stable/ Unsupported]
| --
| Ismet Sonmez
|
|-
| [[Image:Flag_co.png]] Spanish (Colombia)
| [http://www.open-xchange.com/forum/showthread.php?p=3251 Forum]
| --
| xiao
|
|-
| [[Image:Flag_kr.png]] Korean
| [http://software.open-xchange.com/OX6/stable/ Unsupported]
| --
| Andrew Park
|
|}

How to include and build a new language please take a look at the section [[GUI Translation]].

[[Category: OX6]]

OX6:Available Translations

2011-06-21T09:03:38Z

217.7.151.106: /* Available Language Translations */

= Open-Xchange Server Translations =

=== Available Language Translations ===

{| border="1" cellpadding="3" cellspacing="0"
!align="left" |Language
!align="left" |Status
!align="left" |Documentation
!align="left" |Contributor
!align="left" |Contact
|-
| [[Image:Flag_us.png]] US English
| Supported and included in standard packages
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-English.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_gb.png]] British English
| Supported and included in standard packages
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-English.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_fr.png]] French
| Supported and included in standard packages
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-French.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_de.png]] German
| Supported and included in standard packages
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-German.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_es.png]] Spanish
| [http://software.open-xchange.com/OX6/stable/ Supported]
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Spanish.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_nl.png]] Dutch
| [http://software.open-xchange.com/OX6/stable/ Supported]
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Dutch.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_pl.png]] Polish
| [http://software.open-xchange.com/OX6/stable/ Supported]
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Polish.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:japanese.jpeg]] Japanese
| [http://software.open-xchange.com/OX6/stable/ Supported]
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Japanes.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_it.png]] Italian
| [http://software.open-xchange.com/OX6/stable/ Supported]
| Online Help/[http://software.open-xchange.com/OX6/doc/OX6-QuickGuide-Italian.pdf Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:china.jpg]] Simplified Chinese
| [http://software.open-xchange.com/OX6/stable/ Supported]
| Online Help/[http://software.open-xchange.com/OX6/doc/ Manual]
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_se.png]] Swedish
| [http://software.open-xchange.com/OX6/stable/ Unsupported]
| Online Help (for SP5)
| Open-Xchange
| documentation@open-xchange.com
|-
| [[Image:Flag_no.png]] Norsk
| [http://www.open-xchange.com/forum/showthread.php?t=3400 Forum]
| --
| Erol Haagenrud
|
|-
| [[Image:Flag_dk.png]] Dansk
| [http://software.open-xchange.com/OX6/stable/ Unsupported]
| --
| Milan / Netsite.dk
|
|-
| [[Image:Flag_tr.png]] Turkish
| [http://software.open-xchange.com/OX6/stable/ Unsupported]
| --
| Ismet Sonmez
|
|-
| [[Image:Flag_co.png]] Spanish (Colombia)
| [http://www.open-xchange.com/forum/showthread.php?p=3251 Forum]
| --
| xiao
|
|-
| [[Image:Flag_kr.png]] Korean
| [http://software.open-xchange.com/OX6/stable/ Unsupported]
| --
| Andrew Park
|
|}

How to include and build a new language please take a look at the section [[GUI Translation]].

[[Category: OX6]]