Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.
Take a backup of your system before you install a module. Uninstalling a module is not as simple as removing the .jar file. Modules add new configuration nodes, modify existing configuration and may change content. We recommend trying out new modules in a test environment first.
A module consist of a JAR file and potentially other dependencies as JAR files. Modules are responsible for updating their own content and configuration across versions. Be sure to keep one single version of each module and its dependencies.
- Stop the application server where you deploy the module.
- Copy the JAR file(s) into
WEB-INF/libdirectory inside your webapp. Location of this directory depends on the application server.- Tomcat:
/webapps/magnoliaAuthor/WEB-INF/lib - JBoss:
/server/default/deploy/magnoliaPublic/WEB-INF/lib
- Tomcat:
- Restart the instance.
- Access the AdminCentral interface.
Magnolia CMS update wizard will start. - Click the link to start the update process.
The update wizard installs the JAR file and reports results. - Click Start up Magnolia.
- Magnolia CMS restarts.
Install the module for each Author and Public instance by repeating the steps above.
Overview
Content Tools