Difference between revisions of "Plesk Integration"
(Created page with "= Integrate Open-Xchange with Plesk = This document describes how to integrate Open-Xchange with Plesk. == Requirements == In order to integrate Open-Xchange with Plesk, th...") |
|||
Line 16: | Line 16: | ||
Download the APS package from the [http://www.apsstandard.org/applications#searchterm=open-xchange APS catalogue] | Download the APS package from the [http://www.apsstandard.org/applications#searchterm=open-xchange APS catalogue] | ||
+ | |||
+ | == Install and configure Open-Xchange == | ||
+ | |||
+ | Before you continue, you have to find out your requirements on how to integrate your Plesk instance(s) with Open-Xchange. | ||
+ | There are two possible scenarios: | ||
+ | |||
+ | ; One Open-Xchange installation for one Plesk Installation: You want to serve one Plesk system with one single Open-Xchange installation or you are the only one managing the Plesk servers. | ||
+ | ; One Open-Xchange installation fo many Plesk systems: You want to resell many Plesk systems but only use one single Open-Xchange installation. | ||
+ | |||
+ | '''Note: Finding the correct scenario is important as it is hard to change later!''' | ||
+ | |||
+ | The main problem is, that usually on Open-Xchange, you have ONE single "root" account to provision contexts/tenants in Open-Xchange. | ||
+ | The name of this account is usually ''oxadminmaster'', but it can be renamed to what ever you like. | ||
+ | Now imagine there's a scenario where not you, but your customers should create contexts. This is usually the case when you are a reseller. | ||
+ | In this case you do not want to hand out that single "root" account to all your customers. | ||
+ | |||
+ | Fortunately, Open-Xchange has a solution for that. It is called the [[Reseller_Bundle]]. | ||
+ | |||
+ | Roughly summarised, if you are a Reseller you most likely need [[Plesk_Integration#One_Open-Xchange_installation_fo_many_Plesk_systems]] | ||
+ | |||
+ | == One Open-Xchange installation for one Plesk Installation == | ||
+ | |||
+ | |||
+ | |||
+ | == One Open-Xchange installation fo many Plesk systems == |
Revision as of 11:34, 26 August 2013
Contents
Integrate Open-Xchange with Plesk
This document describes how to integrate Open-Xchange with Plesk.
Requirements
In order to integrate Open-Xchange with Plesk, the Open-Xchange APS package must be used. This requires the following versions of Plesk and the APS package:
- Open-Xchange APS package version 7.2 and above (Not yet available).
- Parallels Plesk Panel version 11.5 and above
Older versions are not supported.
Download
Download the APS package from the APS catalogue
Install and configure Open-Xchange
Before you continue, you have to find out your requirements on how to integrate your Plesk instance(s) with Open-Xchange. There are two possible scenarios:
- One Open-Xchange installation for one Plesk Installation
- You want to serve one Plesk system with one single Open-Xchange installation or you are the only one managing the Plesk servers.
- One Open-Xchange installation fo many Plesk systems
- You want to resell many Plesk systems but only use one single Open-Xchange installation.
Note: Finding the correct scenario is important as it is hard to change later!
The main problem is, that usually on Open-Xchange, you have ONE single "root" account to provision contexts/tenants in Open-Xchange. The name of this account is usually oxadminmaster, but it can be renamed to what ever you like. Now imagine there's a scenario where not you, but your customers should create contexts. This is usually the case when you are a reseller. In this case you do not want to hand out that single "root" account to all your customers.
Fortunately, Open-Xchange has a solution for that. It is called the Reseller_Bundle.
Roughly summarised, if you are a Reseller you most likely need Plesk_Integration#One_Open-Xchange_installation_fo_many_Plesk_systems