PA Provider Deployment Guide - Revision history

Choeger at 06:25, 1 September 2016

2016-09-01T06:25:42Z

← Older revision		Revision as of 06:25, 1 September 2016
Line 191:		Line 191:
	INFO:		INFO:

	If ~~POA XML-RPC Service~~ runs on a different port than „3100“.		If the Spamassassin proxy service runs on a different port than „3100“.

	Please edit file:		Please edit file:

Choeger: /* Global application settings */

2015-09-17T07:10:29Z

Global application settings

← Older revision		Revision as of 07:10, 17 September 2015
Line 317:		Line 317:
	; URL to source Horde: Provide URL to Horde Webmail. Will be used only if data migration is enabled in previous setting.		; URL to source Horde: Provide URL to Horde Webmail. Will be used only if data migration is enabled in previous setting.
	; Service with Connector for Business Mobility: Choose "Webmail Account" if you plan to have mobility per default in a webmail account.		; Service with Connector for Business Mobility: Choose "Webmail Account" if you plan to have mobility per default in a webmail account.
	; Reseller mode: This should be Off in most cases when in use with POA. Makes sense in Plesk deployment, see [[Plesk_Integration]]		; Reseller mode: This should be Off in most cases when in use with POA. Makes sense in Plesk deployment, see [[Plesk_Integration]] '''Note: This setting must not be changed after contexts have been already created.'''
	; Debug mode: Should be Off per default.		; Debug mode: Should be Off per default.

Choeger: /* Support for features like OX Text and OX Guard */

2015-06-24T06:46:06Z

Support for features like OX Text and OX Guard

← Older revision		Revision as of 06:46, 24 June 2015
Line 459:		Line 459:
	to tie different capabilities to them.		to tie different capabilities to them.

	'''Note: Using the syncml feature only works with Open-Xchange APS package 7.2-22 or later since that flag was still used for the Mobile Devices Support in version before. Mobile Devices Support, however, is nowadays reflected only through the activesync feature.'''		'''Note: Using the syncml feature only works with Open-Xchange APS package 7.2-24 or later since that flag was still used for the Mobile Devices Support in version before. Mobile Devices Support, however, is nowadays reflected only through the activesync feature.'''

	Let's say you want to sell a package containing [[AppSuite:OX_Guard\|OX Guard]] and a package [[AppSuite:Text_Installation_Guide\|OX Text]] to your customers using PA.		Let's say you want to sell a package containing [[AppSuite:OX_Guard\|OX Guard]] and a package [[AppSuite:Text_Installation_Guide\|OX Text]] to your customers using PA.

Khgras: /* Open-Xchange Parallels Automation Deployment Guide */

2015-05-19T10:45:53Z

Open-Xchange Parallels Automation Deployment Guide

← Older revision		Revision as of 10:45, 19 May 2015
Line 1:		Line 1:
	= Open-Xchange Parallels Automation Deployment Guide =		= Open-Xchange Odin Service Business Automation (former Parallels Automation) Deployment Guide =

	This guide describes the integration of ~~Parallels~~ Automation with Open-Xchange.		This guide describes the integration of Odin Business Automation with Open-Xchange. Please note that the Parallels service provider division has changed its name to Odin. This means that many of the products referred to on this page have also changed their name.

	== Terms and Abbreviations ==		== Terms and Abbreviations ==

	;APS: Application Packaging Standard		;APS: Application Packaging Standard
	;~~PBA~~: Parallels Business Automation.		;OBA: Odin Business Automation (former Parallels Business Automation PBA).
	;~~POA~~: Parallels Operations Automation.		;OSA: Odin Service Automation (former Parallels Operations Automation POA).
	;RST: Resource Type		;RST: Resource Type
	;RS: Resource		;RS: Resource
Line 43:		Line 43:
	** Entry point (Auto login) link to Open-Xchange Admin Account		** Entry point (Auto login) link to Open-Xchange Admin Account
	** Entry points to link to Open-Xchange Webmail accounts		** Entry points to link to Open-Xchange Webmail accounts
	* Parallels Open-Xchange customer subscription management		* Odin (former Parallels) Open-Xchange customer subscription management
	** Through PBA storefront or subscription’s account details, user can purchase additional features or file storage		** Through PBA storefront or subscription’s account details, user can purchase additional features or file storage
	** No other service upgrades or downgrades offered		** No other service upgrades or downgrades offered
Line 97:		Line 97:
	=== Object Mapping ===		=== Object Mapping ===

	Parallels Automation subscription corresponds to Context in Open-Xchange and ~~Parallels~~ Automation end users correspond to users in Open-Xchange.		Odin Service Automation (former Parallels Automation) subscription corresponds to Context in Open-Xchange and Odin Service Automation end users correspond to users in Open-Xchange.

	== Requirements ==		== Requirements ==

	The APS Package requires POA 5.0 or higher, Plesk 11.5 or higher and Open-Xchange 6.22.3 or higher / OX App Suite 7.2.1 or higher. Hence updating from e.g. 6.20.7 to 6.22.0 needs a further update to a required version as 6.22.0 doesn't work with APS package at all because 6.22.0 doesn't provide a proper authentication service which works with ~~Parallels~~.		The APS Package requires POA 5.0 or higher, Plesk 11.5 or higher and Open-Xchange 6.22.3 or higher / OX App Suite 7.2.1 or higher. Hence updating from e.g. 6.20.7 to 6.22.0 needs a further update to a required version as 6.22.0 doesn't work with APS package at all because 6.22.0 doesn't provide a proper authentication service which works with Odin.

	== Known issues ==		== Known issues ==

Choeger: /* Support for features like OX Text and OX Guard */

2015-05-05T11:14:47Z

Support for features like OX Text and OX Guard

@@ Line 489: / Line 489: @@
 were we tie the capabilities to enable each of the features to the corresponding tag.
-'''Please, make sure to create the indentation as shown above by using spaces and not tabs as yml files are very particular about the formatting.'''
+Please, make sure to create the indentation as shown above by using spaces and not tabs as yml files are very particular about the formatting.
 Just for the completeness, find below the name of existing tags that correspond to the names

Choeger: /* Support for features like OX Text and OX Guard */

2015-05-05T11:11:30Z

Support for features like OX Text and OX Guard

← Older revision		Revision as of 11:11, 5 May 2015
Line 488:		Line 488:

	were we tie the capabilities to enable each of the features to the corresponding tag.		were we tie the capabilities to enable each of the features to the corresponding tag.

			'''Please, make sure to create the indentation as shown above by using spaces and not tabs as yml files are very particular about the formatting.'''

	Just for the completeness, find below the name of existing tags that correspond to the names		Just for the completeness, find below the name of existing tags that correspond to the names
	in the file <tt>/opt/open-xchange/etc/ModuleAccessDefinitions.properties</tt>		in the file <tt>/opt/open-xchange/etc/ModuleAccessDefinitions.properties</tt>
	~~Please, make sure to create the indentation as shown above by using spaces and not tabs as yml files are very particular about the formatting.~~

	* ucWebMail		* ucWebMail

Choeger: /* Support for features like OX Text and OX Guard */

2015-05-05T11:10:29Z

Support for features like OX Text and OX Guard

← Older revision		Revision as of 11:10, 5 May 2015
Line 490:		Line 490:
	Just for the completeness, find below the name of existing tags that correspond to the names		Just for the completeness, find below the name of existing tags that correspond to the names
	in the file <tt>/opt/open-xchange/etc/ModuleAccessDefinitions.properties</tt>		in the file <tt>/opt/open-xchange/etc/ModuleAccessDefinitions.properties</tt>
			Please, make sure to create the indentation as shown above by using spaces and not tabs as yml files are very particular about the formatting.

	* ucWebMail		* ucWebMail

Choeger: /* Support for features like OX Text and OX Guard */

2015-05-05T11:09:45Z

Support for features like OX Text and OX Guard

← Older revision		Revision as of 11:09, 5 May 2015
Line 467:		Line 467:
	for each of it:		for each of it:

	oxguard=webmail,calendar,contacts,infostore,tasks,webdav,ical,vcard~~,syncml~~,usm,olox20,activesync,readcreatesharedfolders,delegatetask,editpublicfolders,editgroup,editresource,editpassword,publicfoldereditable,collectemailaddresses,multiplemailaccounts,subscription,publication		oxguard=<font color=red>syncml</font>,webmail,calendar,contacts,infostore,tasks,webdav,ical,vcard,usm,olox20,activesync,readcreatesharedfolders,delegatetask,editpublicfolders,editgroup,editresource,editpassword,publicfoldereditable,collectemailaddresses,multiplemailaccounts,subscription,publication

	oxoffice=webmail,calendar,contacts,infostore,tasks,webdav~~,webdavxml~~,ical,vcard,usm,olox20,activesync,readcreatesharedfolders,delegatetask,editpublicfolders,editgroup,editresource,editpassword,publicfoldereditable,collectemailaddresses,multiplemailaccounts,subscription,publication		oxoffice=<font color=red>webdavxml</font>,webmail,calendar,contacts,infostore,tasks,webdav,ical,vcard,usm,olox20,activesync,readcreatesharedfolders,delegatetask,editpublicfolders,editgroup,editresource,editpassword,publicfoldereditable,collectemailaddresses,multiplemailaccounts,subscription,publication

	these are based on the ''all'' combination, but of course you can modify it if you want. Essential is, that we add ''syncml'' to the		these are based on the ''all'' combination, but of course you can modify it if you want. Essential is, that we add ''syncml'' to the

Choeger: /* Support for features like OX Text and OX Guard */

2015-05-05T11:07:45Z

Support for features like OX Text and OX Guard

← Older revision		Revision as of 11:07, 5 May 2015
Line 454:		Line 454:

	The Open-Xchange APS1.2 package does not directly support the new way to control latest features in Open-Xchange		The Open-Xchange APS1.2 package does not directly support the new way to control latest features in Open-Xchange
	which are controlled using the ConfigCascade and Capabilities. There is, however, a way to use them using contextSets.		which are controlled using the [[ConfigCascade\|ConfigCascade]] and [[AppSuite:Capabilities\|Capabilities]]. There is, however, a way to use them using contextSets.

	Some of the old style features of Open-Xchange like ''webdavxml'' or ''syncml'' are no longer needed and thus they can be used		Some of the old style features of Open-Xchange like ''webdavxml'' or ''syncml'' are no longer needed and thus they can be used
Line 461:		Line 461:
	'''Note: Using the syncml feature only works with Open-Xchange APS package 7.2-22 or later since that flag was still used for the Mobile Devices Support in version before. Mobile Devices Support, however, is nowadays reflected only through the activesync feature.'''		'''Note: Using the syncml feature only works with Open-Xchange APS package 7.2-22 or later since that flag was still used for the Mobile Devices Support in version before. Mobile Devices Support, however, is nowadays reflected only through the activesync feature.'''

	Let's say you want to sell a package containing OX Guard and a package OX Text to your customers using PA.		Let's say you want to sell a package containing [[AppSuite:OX_Guard\|OX Guard]] and a package [[AppSuite:Text_Installation_Guide\|OX Text]] to your customers using PA.
	The following example will use the syncml feature to tie OX Guard to it and the webdavxml feature for OX Text.		The following example will use the syncml feature to tie OX Guard to it and the webdavxml feature for OX Text.

Choeger: /* Support for features like OX Text and OX Guard */

2015-05-05T11:02:58Z

Support for features like OX Text and OX Guard

← Older revision		Revision as of 11:02, 5 May 2015
Line 456:		Line 456:
	which are controlled using the ConfigCascade and Capabilities. There is, however, a way to use them using contextSets.		which are controlled using the ConfigCascade and Capabilities. There is, however, a way to use them using contextSets.

	Some of the old style features of Open-Xchange like webdavxml or syncml are no longer needed and thus they can be used		Some of the old style features of Open-Xchange like ''webdavxml'' or ''syncml'' are no longer needed and thus they can be used
	to tie different capabilities to them.		to tie different capabilities to them.

Line 464:		Line 464:
	The following example will use the syncml feature to tie OX Guard to it and the webdavxml feature for OX Text.		The following example will use the syncml feature to tie OX Guard to it and the webdavxml feature for OX Text.

	First thing to do is to create two module access combination names within /opt/open-xchange/etc/ModuleAccessDefinitions.properties		First thing to do is to create two module access combination names within <tt>/opt/open-xchange/etc/ModuleAccessDefinitions.properties</tt>
	for each of it:		for each of it:

Line 471:		Line 471:
	oxoffice=webmail,calendar,contacts,infostore,tasks,webdav,webdavxml,ical,vcard,usm,olox20,activesync,readcreatesharedfolders,delegatetask,editpublicfolders,editgroup,editresource,editpassword,publicfoldereditable,collectemailaddresses,multiplemailaccounts,subscription,publication		oxoffice=webmail,calendar,contacts,infostore,tasks,webdav,webdavxml,ical,vcard,usm,olox20,activesync,readcreatesharedfolders,delegatetask,editpublicfolders,editgroup,editresource,editpassword,publicfoldereditable,collectemailaddresses,multiplemailaccounts,subscription,publication

	these are based on the "all" combination, but of course you can modify it if you want. Essential is, that we add syncml to the		these are based on the ''all'' combination, but of course you can modify it if you want. Essential is, that we add ''syncml'' to the
	oxguard and webdavxml to the ~~oxoffic~~ only.		oxguard and ''webdavxml'' to the oxoffice only.

	Next we create a file /opt/open-xchange/etc/contextSets/packages.yml		Next we create a file <tt>/opt/open-xchange/etc/contextSets/packages.yml</tt>

	oxguard:		oxguard:
Line 489:		Line 489:
	were we tie the capabilities to enable each of the features to the corresponding tag.		were we tie the capabilities to enable each of the features to the corresponding tag.
	Just for the completeness, find below the name of existing tags that correspond to the names		Just for the completeness, find below the name of existing tags that correspond to the names
	in the file /opt/open-xchange/etc/ModuleAccessDefinitions.properties		in the file <tt>/opt/open-xchange/etc/ModuleAccessDefinitions.properties</tt>

	* ucWebMail		* ucWebMail