Magnolia 4.5 reached end of life on June 30, 2016. This branch is no longer supported, see End-of-life policy.

Page tree
Skip to end of metadata
Go to start of metadata

Magnolia has a modular architecture. A module is a independent component that performs a particular task or packages content and functionality. The system itself is built of modules: AdminCentral, the built-in Document Management System and the Workflow functionality are all modules.


Pluggable modules
Modules are independent and pluggable in the sense that you can add and remove them at will. A module consists of a set of components packaged in a JAR file. Deploying a module is a matter of copying the JAR file into the WEB-INF/lib folder and restarting the instance. Magnolia update wizard recognizes the JAR and installs its contents.

Module development lifecycle
Illustrates how custom modules and resources can be packaged into a JAR file and deployed to production in a controlled manner. The level of environmental control and the amount of testing required depends on your client. A financial or insurance client may have compliance requirements that require complete segregation between development, test and production environments.

  • No labels