Manual updates and order

The installer installs components in a fixed order. If you have to update a single component by hand, keep the same order.

The installer's internal order:

1. Server protection is put into maintenance mode.
2. Server extensions (.jar) are copied to /opt/zimbra/lib/ext/<module>/.
3. Zimlets are deployed with zmzimletctl deploy.
4. User zimlets are granted to the default COS.
5. Helper components are installed.
6. Caches are flushed and mailboxd restarts once.
7. Verification runs.

Updating a single extension

zimbra-guard maintenance on
cp -a com_profelis_<module>/. /opt/zimbra/lib/ext/com_profelis_<module>/
chown -R zimbra:zimbra /opt/zimbra/lib/ext/com_profelis_<module>
su - zimbra -c 'zmmailboxdctl restart'
zimbra-guard baseline && zimbra-guard maintenance off

Check /opt/zimbra/log/mailbox.log for the line showing that the Profelis extension started.

Updating a single zimlet

su - zimbra -c 'zmzimletctl deploy com_profelis_<module>.zip'
su - zimbra -c 'zmprov flushCache zimlet'

Then hard-reload the browser. If only the zimlet changed, mailboxd does not need a restart.

Do not overwrite a jar on a running server

Overwriting a jar while mailboxd runs can cause errors. Restart right after copying the file.

You can also deploy a zimlet from the admin console instead of the command line: Deploying a zimlet from the admin console.