OpenWGA 7.0 - Updating to OpenWGA 7.0

OpenWGA 7.0 again comes with the ability to upgrade OpenWGA Content Stores to a new patch level. Patch level 4 allows content stores to utilize the following new functionalities:

• A new storage mode for file attachments, called distinct file contents, allows to reduce storage space - in some situations drastically - and speed up some authoring operations
• A new feature called file derivates allows OpenWGA to automatically create derivate versions of file attachments, like scaled down versions of images, that can be used in publishing for various purposes.

The upgrading process however is not started automatically this time, unlike on earlier occasions. Instead the administrator should manually start the upgrade process applicable for upgrading. The reason for this is that patch level 4 is optional and there are certain situations where you should take prerequisites for patching or should not upgrade at all:

• If you are running an OpenWGA cluster: In order to ensure continuous service of the apps on your cluster you should do things in a special order.
• If your content stores are still accessed by earlier OpenWGA versions: Upgrading content stores to patch level 4 will make their file attachments unreadable for earlier OpenWGA versions. If certain content stores should still be accessed by other OpenWGA servers of versions 6.2 or lower then you should not upgrade them.
• If you are (very) low on database storage space: While the new "distinct file contents" storage may spare a lot of storage data the "file derivates" feature on the contrary may take up additional space. It heavily depends on the amount and type of file attachment data of your content stores if storage space is actually reduced (like in most situations) or increased. So If you are short on database storage space you might want to disable file derivates for selected databases before starting the upgrade, like described in the following chapter.
• If your database server user has no rights to change tables and indexes: Letting OpenWGA upgrade content stores may not work if the database server user by which OpenWGA connects to the database server does not have the necessary rights for the patch operations. The patch tries to add new tables to the content store database, add new columns to existing tables and create new indexes, which may not be allowed operations for this user. Instead of letting OpenWGA do the upgrade you can retrieve the patch code and execute it yourself via any SQL terminal, like described under "Individual content store upgrade".

Please follow the guide The cautious path below, if one or more of the conditions described above applies to you. Otherwise you may do a simple upgrade using the The easy path.