In this Topic Hide
Upgrading your RPM Installation to Merge Configuration Files During Upgrade
Upgrading to a Newer Version of Zend Server
Upgrading from Zend Server CE to Zend Server
The information in this section refers to the different upgrade options available to users, according to the product currently installed and available installation type. If you are using Zend Server Cluster Manager see Upgrading a Zend Server Cluster.
|
To
control what yum will do with configuration changes when installing
or updating packages, use yum-merge-conf. |
The following instructions pertain to the process of installing a newer version of the same product, i.e., a newer version of Zend Server or a newer version of Zend Server CE (Community Edition). For example, upgrading from version 5.03 to 5.04 or from version 5.0 to 5.1.
Installation Type |
Zend Server |
Configuration Information |
Comments |
RPM |
+ |
|
|
DEB |
+ |
Handles all configuration upgrades. |
|
Tarball |
- |
|
See Tarball Installation. |
Mac OS X |
- |
|
See Upgrading a Mac OS X Installation. |
Windows |
+ |
Upgrades include existing configurations. |
The installer automatically identifies if it is a new installation or an upgrade. See Upgrading a Windows Installation. |
SLES and OpenSUSE |
+ |
Upgrades all Zend related packages. |
Installation Type |
Community Edition |
Configuration Information |
Comments |
RPM |
+ |
|
|
DEB |
+ |
Handles all configuration upgrades |
See Upgrading a DEB Installation.
|
Tarball |
+ |
A separate backup of the ZendServer/etc/ directory is created. |
Manually restore the old configuration file if you want to keep configurations. The configuration file is placed in the same location as the .conf file and is renamed with a timestamp. To use the backup rename to .conf. |
Mac OS X |
+ |
When upgrading, the following information will be preserved. |
apache2/htdocs apache2/conf apache2/conf.d Except for apache2/conf.d/zendserver_gui.conf etc/php.ini etc/conf.d/*.ini All directories under share/pear/ (but not .php files) gui/application/data/zend-server-user.ini gui/application/data/logfiles.xml MySQL data directory MySQL my.cnf file |
Windows |
+ |
Upgrades include existing configurations. |
The installer automatically identifies if it is a new installation or an upgrade. |
SLES and OpenSUSE |
+ |
Upgrades all Zend related packages. |
This procedure can be performed using the Zend Repository Installer script (available in Zend Server's Download Page | Linux Tab | "Zend Server (DEB/RPM Installer Script)") by running the command ./install.sh <php version> in the script's directory after download.
Installation Type |
Availability
|
Configuration Information |
Comments |
RPM |
+ |
|
You must first add the new repository to your sources.list. Use yum-merge-conf to manage configurations (see above). |
DEB |
+ |
Handles all configuration upgrades |
You must first add the new repository to your sources.list. |
Tarball |
- |
|
|
Mac OS X |
- |
|
|
Windows |
+ |
Configuration information is imported from: ZendServer\etc\ ZendServer\GUI\application\data\ Apache2\conf/ |
|
SLES and OpenSUSE |
+ |
Upgrades all Zend related packages. |
RPM Upgrade Note:
After upgrading from the Community Edition to Zend Server, you will need to manually start your server by running the command: <install_path>/bin/zendctl.sh start.
Once you have upgraded your Community Edition to Zend Server, you will need a license to run the fully functional product. If you do not enter a license, Zend Server will run with the same functionality as the Community Edition: There is no need to do anything. The full version of Zend Server will continue to provide the basic Community Edition features and functionality. This also means that when you do decide to purchase Zend Server, all you need to do is add a license to activate the complete functionality.
Alternatively, you can remove Zend Server and reinstall the Community
Edition. To preserve your configurations, back up your configuration files
before you remove Zend Server and return them after you reinstall the
Community Edition.
The recommended directories to backup are:
This procedure describes how to manually update your Zend Server PHP 5.2 to PHP 5.3.
Note:
This procedure can also be performed using the Zend Repository Installer script (available in Zend Server's Download Page | Linux Tab | "Zend Server (DEB/RPM Installer Script)") by running the command ./upgrade_zs_php.sh <php version> in the script's directory after download.
|
|
|
To update your PHP on RPM:
|
|
|
|
|
|
To update your PHP on SLES:
|
|
|
|
|
|
To update your PHP on DEB:
|
|
|
|
|
|
To update your PHP on Windows or Mac OS X, simply download the PHP 5.3 version of Zend Server from the product's Downloads Page on top of your existing one. There is no need to remove the prior version in order to update. |
|
|
Currently there is no automated process for upgrading from Zend Platform/Zend Core to Zend Server. However, it is possible to install Zend Server on a separate machine and manually transfer part of the Zend Platform/Zend Core configurations to the machine running Zend Server. This may help save some time configuring your Zend Server environment.
The following configuration files can be manually copied and used to replace Zend Server configuration files:
After transferring any configuration from Zend Platform/Zend Core to Zend Server it is highly recommended to thoroughly test your applications before permanently applying these changes.
Rollback is the process of reverting to an older version of Zend Server.
Currently there is no automated process for this. Therefore, users who want to rollback should first uninstall their current version and only then install an older version of Zend Server.
Note:
This does not refer to Updates. You can rollback to remove recently added updates. For more information on updating go to Update Notifications.
|
|
|
Related Links: Choosing Which Distribution to InstallPackage Setup and Control Scripts Upgrading a Zend Server Cluster |
|
|
