This tutorial explains how you can create custom Magnolia webapps with Maven. Using Maven allows you to customize your webapps with the POM files, which can be tracked with a version control system like Git. A tailored webapp makes building and deploying faster and has a positive impact on the performance of your instances. With Maven, you can streamline your Magnolia project to meet the specific demands of the project.
If you just want to try out Magnolia, follow instead the tutorial called How to get and adapt a bundle with Magnolia CLI.
What is a webapp?
A Java Web Application (webapp) is a collection of servlets, other Java classes, static resources such as HTML pages, other resources, and meta information that describes the webapp bundled together. You can run a webapp on a servlet container. A Java webapp has a typical structure. It can be packaged as a WAR file. A webapp usually contains already packed portions called libraries or modules as JAR files.
Magnolia provides several preconfigured webapps and bundles. Some of them are ideal candidates as a starting point to build your custom webapp.
Magnolia provides the following stand-alone, pre-configured Apache Tomcat server that does not include a webapp:
|Usage / purpose|
|A preconfigured Tomcat server ready to be used together with any Magnolia webapp.|
Magnolia provides the following webapps and bundles.
|The standard Magnolia cloud offer bundles a selection of enterprise-level modules, including connectors enabling you to integrate third-party systems, tools and data sources.||See Supported modules in the cloud.|
|Enterprise level webapp specifically built for testing Magnolia Cloud development work locally.||See Supported modules in the cloud .|
|Bundles a lighter selection of enterprise-level modules enabling you to create content and use it in headless deployment scenarios.||See Supported modules in the cloud - Headless cloud bundle modules .|
|This is the most basic Magnolia webapp. Use this as a base for custom tailored webapp.||Core modules from main and ui, Cache (core and ehcache), Pages, Resources, Publishing, Security and Scheduler.|
|Complete Magnolia community edition webapp; no demo project.||Same as |
Cache tools, Cache Browser, Categorization, Commenting, Contacts, DAM, Find Bar, Form , Groovy, Mail, Messages, MTE , REST and Site.
|Same as ||Travel demo community edition 2|
|Tomcat-bundle including ||Travel demo community edition 2|
Enterprise Standard edition
|Same as |
|Same as ||Travel demo Enterprise Standard edition 3|
|Enterprise Pro edition|
Backup, Content Dependencies, Content Editor, Content tagging, Content Translation Support, Diff, Image Recognition module, Marketing Tags, Personalization, Privacy module Publishing Transactional, Soft Locking, Workflow and Multisite.
|Travel demo enterprise pro edition 4|
|Tomcat bundle with ||Travel demo Enterprise Pro edition 4|
|Installer for |
|5||Webapp based on ||Travel demo Enterprise Pro edition 4|
|5||Webapp based on ||Travel demo Enterprise Pro edition 4|
(1) The module summary does not list all modules but provides a good summary. To get the complete list of the modules, look at the corresponding pom file of the bundle.
(2) Travel demo Community edition contains the following modules: magnolia-travel-demo, magnolia-travel-tours.
(3) Travel demo Enterprise Standard edition contains the following modules: magnolia-travel-demo, magnolia-travel-tours, magnolia-travel-demo-personalization, magnolia-travel-demo-marketing-tags.
(4) Travel demo Enterprise Pro edition contains the following modules: magnolia-travel-demo, magnolia-travel-tours, magnolia-travel-demo-personalization, magnolia-travel-demo-marketing-tags, magnolia-travel-demo-multisite.
(5) Both magnolia-enterprise-weblogic-webapp and magnolia-enterprise-websphere-webapp contain all Enterprise Standard and Pro modules but not those for workflow.
We assume that you are familiar with Maven and the basics of POM files. Your Maven settings should comply with the Magnolia Maven setup, which provides access to the Magnolia Nexus repositories, and thus ensures that you can build the webapps described in the examples. If you are new to Magnolia, we recommend that you first carefully follow the Maven setup page.
When creating a custom webapp, you have to decide whether your webapp will contain Enterprise modules or only Community edition modules. If you go for the Enterprise Edition, you need credentials to access the Enterprise repositories on Nexus and you also need an Enterprise license to run the Enterprise webapps. If you don't have the Enterprise credentials yet, but want to try out the Magnolia Enterprise Edition, apply for a trial license.
This section describes two approaches to define a custom webapp with Maven. For both of them, keep in mind the following:
A minimal webapp and adding modules
If your aim is a minimalistic webapp, we recommend using the
magnolia-empty-webapp as a base for your webapp project. it is also the base for every Magnolia webapp and provides the essentials such as the Core and UI modules. This approach is applied on the subpage Creating a minimal webapp with Maven. It could be suitable for you, if you aim at creating a custom headless instance.
A feature-rich webapp and excluding modules
Most of the preconfigured Magnolia webapps come with a feature-rich set allowing you to accomplish a number of different tasks and run complex websites. The most prominent preconfigured Magnolia webapps are these:
The second example — Creating an EE Pro webapp with Maven — uses the
magnolia-enterprise-pro-webapp as a starting point. We then exclude some modules which are not necessary for the example use case.
When creating a feature-rich webapp, you cannot only exclude modules, you also need to add additional modules. Usually, it is common to do both, exclude and add modules.
- Create a webapp skeleton from a Magnolia Maven archetype.
- Modify the POM files according to your needs.
- Add additional resources, if necessary.
- Build the webapp.
Creating an archetype-based webapp skeleton
Just as Maven provides archetypes to create a typical skeleton for Maven projects, Magnolia too provides an archetype to create a skeleton for a Magnolia Maven project. The Magnolia archetype comes with options for different tasks. Here, we use the
magnolia-project-archetype. It is an archetype that creates a Magnolia project with its parent POM and a webapp with its own POM.
Before running the maven
archetype command, please read How to use Magnolia Maven archetypes: Check Maven settings.
If you are not familiar with the Maven archetype plugin, please also read How to use Magnolia Maven archetypes: The archetype plugin.
The archetype command
The first step to create your Maven-based custom webapp is running the archetype command. Change into the directory where you want to create the Maven project for the Magnolia webapp. In the directory, use a shell to run the following command:
While the archetype script is running, Maven prompts you to supply values for a list of parameters. Some of them are Maven-specific, others concern only Magnolia. In some cases, Maven suggests a value. To accept it, enter
RETURN or specify your own value and press
Executing the archetype command is the very first step you always have to take irrespective of the webapp edition you wish to create (Community or Enterprise) and the approach you want follow (minimal or feature-rich). The parameters you specify in the prompts have no influence on the edition type or the approach.
These are the parameters Maven prompts you with in the order they appear:
|It typically reflects the name or domain of your company or projects.|
|Maven artifact ||Project version. Typically, when creating a new project, use the value suggested, |
Package name for Java classes reflecting both your company (or domain) and the specific project.
For this archetype, this parameter is not used, but you must provide a value. You can use the value proposed by the archetype script.
The Magnolia version from which your custom project inherits. If you are unsure, use the latest released version (see releases).
This version is used in the
In many cases it is reasonable to use the same value as in
1) See also the Maven Guide to naming conventions on groupId, artifactId, and version.
After entering a
project-name value, the archetype script lists all the values you have provided. Now you can:
Confirm your choice by pressing
RETURN. Maven will generate the skeleton based on your parameters.
- Escape the running archetype script by pressing
C. The script terminates, not creating anything. To start again, execute the archetype command as described above.
If you have confirmed your choice of parameters, the script finishes the build with the
BUILD SUCCESS message:
The webapp skeleton
Maven generates the following webapp skeleton:
- Line 3: The webapp's POM file, defining the modules going into the webapp.
- Line 4: The
srcdirectory, containing more subfolders. In Example 2, you add more resources to this directory.
- Line 5: The parent (actually the root) POM file of the created project. This POM file manages the dependencies.
The POM files are the central pieces of the skeleton. Make sure you understand these files since you must adapt them in the examples to define the custom webapps.
The contents of the parent POM file:Depending on the requirements of your project, the
dependencyManagementsections may need some adjustments.
properties section is where you define values such as versions. You can use the section in both the parent POM and the webapp POM.
On lines 10-13 in the file embedded above, for example, the archetype adds the
dependencyManagement section, you define the artifact dependencies that you also add to the module in the webapp POM. See lines 22-47 in the file embedded above.
In the skeleton,Option A and Option B were created, the latter as a comment.
- Use the Option A to inherit dependency management for a Magnolia Community Edition (CE) webapp.
Have a look at the parent POM of the CE bundle to understand what exactly you inherit with Option A.
- Use the Option B to inherit dependency management for a Magnolia Enterprise Edition (EE) webapp.
Importing the EE dependency management section also indirectly imports the CE dependency management.
Have a look at the parent POM of the EE bundle to understand what exactly you inherit with Option B. To access the parent POM of the EE bundle on Git, you need EE credentials.
Also, use the
dependencyManagement section to define the versions of other modules which you want to add to the webapp.
The contents of the webapp POM file:
Finally, in the
dependencies section of the webapp POM, you assemble the modules which should be part of the webapp. Since you are using a preconfigured Magnolia webapp as the base, the Magnolia archetype creates and adds the following options to the webapp POM (lines 13-83 above):
Each of these options has a dependency to two artifact types –
Besides adding an existing webapp, you typically also add other dependencies to single modules.
For examples of creating custom webapps with Maven, see the following pages: