Upgrade Z-Push v2 (with Zimbra Backend) - Revision history

Sstrutt: /* Go Live */ Added "Ver 2.0 To Ver 2.1"

2013-10-13T22:39:15Z

Go Live: Added "Ver 2.0 To Ver 2.1"

@@ Line 37: / Line 37: @@
 # Restart webserver
 #* <code> apache2ctl -k graceful </code>
 == Test ==

Sstrutt: Revised following upgrade to Z-Push v2.0.7

2013-04-01T21:08:49Z

Revised following upgrade to Z-Push v2.0.7

← Older revision		Revision as of 21:08, 1 April 2013
Line 1:		Line 1:
	It easiest to perform an upgrade by preparing the files for the website first. Then once you're confident all is well, ~~switching~~ over ~~is quick~~ and ~~relatively seamless~~.		It easiest to perform an upgrade by preparing the files for the website in a new folder first. Then, once you're confident all is well, switch over the old and new folders by renaming. If something doesn't work as expected its easy to fall back to the previous running version.

			Whilst it shouldn't be necessary for Active-Sync clients to perform any actions prior to or after an upgrade, its worth making sure that they are syncing properly and don't have any current problems. Un-synced changes (that exist on phones etc) could get lost, and any existing problems may be exacerbated.

	To check your current running versions (assuming you're logging to <code>/var/log/z-push/z-push.log</code>)...		To check your current running versions (assuming you're logging to <code>/var/log/z-push/z-push.log</code>)...
Line 5:		Line 7:
	** <code>grep "] Version=" /var/log/z-push/z-push.log</code>		** <code>grep "] Version=" /var/log/z-push/z-push.log</code>
	* Zimbra backend		* Zimbra backend
	** <code>grep "Zimbra Backend version" /var/log/z-push/z-push.log</code>		** See the version indicated in <code> <z-push dir>/backend/zimbra/Release Notes.txt</code>
			** If you're running the backend in debug mode (eg <code>define('ZIMBRA_DEBUG',true);</code>) then
			*** <code>grep "Zimbra Backend version" /var/log/z-push/z-push.log</code>

	Make sure you read the release notes for the new versions of software that you are installing. You may need to make additional changes as part of the upgrade that are not covered here.		Make sure you read the release notes for the new versions of software that you are installing. You may need to make additional changes as part of the upgrade that are not covered here.
Line 20:		Line 24:
	#* EG <code> svn checkout svn://svn.code.sf.net/p/zimbrabackend/code/zimbra-backend/branches/z-push-2 /var/www/z-push-v2.0.6/backend/zimbra</code>		#* EG <code> svn checkout svn://svn.code.sf.net/p/zimbrabackend/code/zimbra-backend/branches/z-push-2 /var/www/z-push-v2.0.6/backend/zimbra</code>
	# Copy across the config from your old install		# Copy across the config from your old install
	#* I tend to do a diff of my existing and the new config files first in order to detect ~~that~~ there are new config settings that I might be wiping out		#* I tend to do a diff of my existing and the new config files first, in order to detect if there are new config settings that I might be wiping out by copying across
	#** EG <code> diff /var/www/z-push/config.php /var/www/z-push-v2.0.6/config.php </code>		#** EG <code> diff /var/www/z-push/config.php /var/www/z-push-v2.0.6/config.php </code>
	#* Also note that ~~ptior~~ to Z-Push v2.0.6, all config was in only file (see [[Z-Push_v2_with_Zimbra#Z-Push Config\|Z-Push Config]] for more info)		#* Also note that prior to Z-Push v2.0.6, all config was in only one file (see [[Z-Push_v2_with_Zimbra#Z-Push Config\|Z-Push Config]] for more info), since v2.0.6 the backend config has been separated out
	#* EG <code> cp /var/www/z-push/config.php /var/www/z-push-v2.0.6/config.php </code>		#* EG <code> cp /var/www/z-push/config.php /var/www/z-push-v2.0.6/config.php </code>
			#* EG <code> cp /var/www/z-push/backend/zimbra/config.php /var/www/z-push-v2.0.6/backend/zimbra/config.php </code>

	== Go Live ==		== Go Live ==

Sstrutt: /* Preparation */ Corrected SVN path

2013-01-24T16:26:37Z

Preparation: Corrected SVN path

← Older revision		Revision as of 16:26, 24 January 2013
Line 18:		Line 18:
	#* EG <code> mv z-push-2.0.6-1616/* /var/www/z-push/z-push-v2.0.6/</code>		#* EG <code> mv z-push-2.0.6-1616/* /var/www/z-push/z-push-v2.0.6/</code>
	# Download the Zimbra Z-Push backend into a <code>/zimbra</code> folder under the <code>backend</code> folder		# Download the Zimbra Z-Push backend into a <code>/zimbra</code> folder under the <code>backend</code> folder
	#* EG <code> svn checkout ~~https~~://~~zimbrabackend~~.~~svn~~.~~sourceforge~~.net/~~svnroot~~/zimbrabackend/zimbra-backend/branches/z-push /var/www/z-push-v2.0.6/backend/zimbra</code>		#* EG <code> svn checkout svn://svn.code.sf.net/p/zimbrabackend/code/zimbra-backend/branches/z-push-2 /var/www/z-push-v2.0.6/backend/zimbra</code>
	# Copy across the config from your old install		# Copy across the config from your old install
	#* I tend to do a diff of my existing and the new config files first in order to detect that there are new config settings that I might be wiping out		#* I tend to do a diff of my existing and the new config files first in order to detect that there are new config settings that I might be wiping out

Sstrutt: Initial creation

2013-01-23T23:30:39Z

Initial creation

New page

It easiest to perform an upgrade by preparing the files for the website first. Then once you're confident all is well, switching over is quick and relatively seamless.

To check your current running versions (assuming you're logging to <code>/var/log/z-push/z-push.log</code>)...
* Z-Push
** <code>grep "] Version=" /var/log/z-push/z-push.log</code>
* Zimbra backend
** <code>grep "Zimbra Backend version" /var/log/z-push/z-push.log</code>

Make sure you read the release notes for the new versions of software that you are installing. You may need to make additional changes as part of the upgrade that are not covered here.

== Preparation ==
# Create a folder for Z-Push on your webserver
#* EG <code> mkdir /var/www/z-push-v2.0.6 </code>
# Download the latest Z-Push version (see http://zarafa-deutschland.de/z-push-download/final/) to a temp folder and unpack
#* EG <code> wget http://zarafa-deutschland.de/z-push-download/final/2.0/z-push-2.0.6-1616.tar.gz </code>
#* EG <code> tar -zxvf z-push-2.0.6-1616.tar.gz </code>
# Move the contents to your webserver folder
#* EG <code> mv z-push-2.0.6-1616/* /var/www/z-push/z-push-v2.0.6/</code>
# Download the Zimbra Z-Push backend into a <code>/zimbra</code> folder under the <code>backend</code> folder
#* EG <code> svn checkout https://zimbrabackend.svn.sourceforge.net/svnroot/zimbrabackend/zimbra-backend/branches/z-push /var/www/z-push-v2.0.6/backend/zimbra</code>
# Copy across the config from your old install
#* I tend to do a diff of my existing and the new config files first in order to detect that there are new config settings that I might be wiping out
#** EG <code> diff /var/www/z-push/config.php /var/www/z-push-v2.0.6/config.php </code>
#* Also note that ptior to Z-Push v2.0.6, all config was in only file (see [[Z-Push_v2_with_Zimbra#Z-Push Config|Z-Push Config]] for more info)
#* EG <code> cp /var/www/z-push/config.php /var/www/z-push-v2.0.6/config.php </code>

== Go Live ==
# Move old install out of the way
#* EG <code> mv /var/www/z-push /var/www/z-push-v2.0.5 </code>
# Move new install into place
#* EG <code> mv /var/www/z-push-v2.0.6 /var/www/z-push </code>
# Restart webserver
#* <code> apache2ctl -k graceful </code>

== Test ==
# Browse to your server, eg http://as.domain.com/Microsoft-Server-ActiveSync
#* You should be prompted for a username and password (for an account on your Zimbra server)
#* If Apache has failed to deliver the prompt to you, check the webserver log. Either your website isn't configured correctly or Z-Push experienced a PHP error.
# Enter a valid Zimbra user/pass
#* You should get a page showing "Z-Push - Open Source ActiveSync" which doesn't contain errors - this confirms that connectivity exists between all the required components (Apache, Z-Push, Zimbra), and that they are basically OK.
# Using a mobile device test expected functionality
#* Email sending (send to yourself so you test receiving as well)
#* Create a test contact on device and check sync to server
#* Create a test contact on server and chack sync to device
#* As above for a calendar item
#* As above for a task

[[Category:Zimbra]]
[[Category:Z-Push]]
[[Category:Applications]]