The RPM file used to a fresh ESF install can be used to upgrade an existing installation. The RPM file, indeed, contains all the resources needed to upgrade/install ESF. The upgrade will preserve all the user preferences, scripts and snapshots.
To upgrade ESF using .rpm files, use the following command:
rpm -Uvh esf-*.rpm
The ESF upgrade using RPM files allows switching from a certain version (for example x.y.z) to the next available minor (x.y+1) version.
In the case of different upgrade requirements, please keep in touch with your Eurotech sales representative for the quotation of a specific Professional Service.
The upgrade of an ESF in production mode to ESF 6.1.2 will require the installation, prior to the framework upgrade, of a bundle named com.eurotech.framework.policy.updater that will update the existing policy to make it compatible with the new signing certificates used by ESF and the new security policy suggested by Eurotech for production deployments.
The policy update will be done appending a new policy to the existing one and will not modify any customer change to it.
Once applied, the bundle will remove itself from the framework and restart the gateway.
To have more details on the new suggested production policy, please refer to the Security Policy File page in the Security chapter.
The Policy updater bundle is available in the Eurotech ESF download site
The upgrade from ESF 6.0.0 requires, especially for gateways in "production mode", a pre-update applied to the framework, prior to the rpm upgrade.
The pre-update is a deployment package available here as jar file that the customer needs to download and install into a running ESF instance.
Once installed, the package prepares the framework for the rpm upgrade. When done, the bundle uninstalls itself.
Updated about a month ago