A bundle is a package consisting of a Magnolia webapp and a selection of modules. Each bundle has a particular purpose such as demonstration or production use. In this tutorial you create your own bundle. Select only the modules the project needs, not more. A small purpose-built bundle is easy to understand and fast to build and deploy. Maven handles the dependencies between modules.
Bundles provided by Magnolia
Magnolia provides a number of ready-made bundles. For more information please read bundles and webapps.
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 , Form , Google sitemap, 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, Google Analytics, Marketing Tags, Personalization, 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.
In this tutorial we use:
- Maven: You should be familiar with the Maven dependency mechanism. The same concept applies to other dependency management and build tools such as Ant+Ivy or Gradle. See Maven setup if you are new to Maven or want to install it in order get access to Magnolia resources from Magnolia Nexus.
- IDE: The examples and screenshots are from IntelliJ IDEA but any Java IDE such as Eclipse or Netbeans works. If you work with a different tool and would like to contribute steps, leave a comment.
- Terminal or command line: Some commands in this tutorial are Mac OS X specific. Replace them with equivalent commands on your operating system.
Create an empty project
Maven archetypes are like templates for projects. An archetype makes it easy to generate a project quickly. By using an archetype you can be sure that your project has the correct structure. An archetype readily defines typical dependencies such as a dependency to a Magnolia webapp. The Magnolia archetype catalog provides examples for various types of modules.
Open a terminal and go to a directory where you keep your Magnolia projects.
- Generate a new project from a Maven archetype:
- Choose the magnolia-project-archetype from the options Maven presents.
- Provide the project information. Press ENTER to accept the default.
- Version: Choose the latest version provided.
- Group ID:
example.comor a group ID that reflects your company.
- Artifact ID:
example-projector an artifact ID that reflects your project.
example.com. Maven proposes a package name based on the group ID. You can change it later in configuration.
- magnolia-bundle-version: Find the latest Magnolia bundle version in Releases, for example
- Project name:
example-com. Maven proposes a package name based on the group ID. You can change it later in configuration.
Verify your input and accept with Y:
Maven creates an empty project structure in the current directory.
example-project: Parent project.
example-project-webapp: Your custom bundle as a child Maven project. Here you find a typical Magnolia project folder structure.
pom.xml: Webapp project POM.
src: Java source code and project configuration
pom.xml: Parent POM.
Build the project
Go to the project folder that Maven created:
Build the project:
Run the project
Open the project in your IDE. These instructions are for IntelliJ IDEA. Adapt for other IDEs.
- In IDEA, go to File > Import project > Browse to the parent project
- Go to Run > Edit Configurations > + > Tomcat Server > Local.
- Go to the Deployment tab and add an artifact
- Set Application Context to root (/). You can deploy the application to a different context if you like.
- Start the project.
The Tomcat application server starts and deploys the Magnolia project. If your IDE does not open a Web browser automatically, go to
Install Magnolia and log in
Start Magnolia installation.
Note: The screenshot above is outdated showing installation tasks when using Magnolia 5.3.6. We recommend always using the latest stable Magnolia version when creating a new custom bundle.
You are now running a basic Magnolia project with an empty webapp.
magnolia-empty-webapp runs without errors, the project is ready to add modules according to your requirements. In this example we add the REST modules.
Look at the parent project pom.xml file in
example-project/pom.xml. It uses Maven's dependency management mechanism to import dependencies from the ce-bundle. (Search for the commented note "Importing dependencyManagement of CE bundle".)
When you add modules to your
example-project-webapp you don't have to specify their versions. Version numbers are inherited from the
dependency-management section of the ce-bundle. You only need to specify the version in
example-project/example-project-webapp/pom.xml - if you want to override the versions defined in the dependency management of the ce-bundle.
As an example, add the REST modules to your project. Add the following code in the
dependencies section of the webapp pom in
IntelliJ IDEA displays a notification when you modify a POM file. It prompts you to “Import Changes” or “Enable Auto-Import”. Enabling auto-import works quite well but can be resource intensive if you modify POM files heavily. In this example you can enable auto-import. If you choose not to, remember to click “Import Changes” at least once before starting up the server.
Restart your server for the new modules to be picked up. Magnolia asks you to install the REST modules. After installation you can find a new app in the Dev group and you can start the REST Tools app.
In this tutorial you learned how to create a Magnolia project from a Maven archetype, built the project with Maven, and added custom modules. The project does not do much yet but you reached important goals already:
- You built your own project with Magnolia. You did not need to manually “drop a jar” in the Web application or modify a configuration file in the deployed webapp.
- The build is reproducible. You can check your files into a source control system. Based on the files your team mates or a continuous integration server can reproduce the build any time. They can also release your project.
- Gregory Joseph: Don't Build Magnolia, Build Your Projects