Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
WAR means Web Application Archive. A WAR file is a zipped Java web application containing all the resources such as jar files, Java classes, Java server pages (JSP), static resources and configuration data.
Since a WAR file is one single file, it is the easiest way to deploy a Java Web application to an application server. Many vendors support WAR file deployment in different ways. Please read the manual of your application server.
Remember that every Magnolia instance (author or public) is its own Java Web application. Deploy one WAR file per instance. Magnolia provides preconfigured WAR files for Community Edition or Enterprise Edition. When using custom bundles, use Maven to build the WAR file of your custom bundle webapp.
Preconfigured Magnolia WAR files
Application server | Enterprise Edition | Community Edition |
|---|---|---|
Tomcat | ||
JBoss | ||
IBM WebSphere | - | |
Oracle WebLogic 10 | - |
Deploying a WAR file
Deploying a WAR file on an application server is a procedure which differs from one server to the next. Some servers require specific steps to deploy Magnolia.
- Deploying a WAR on Apache Tomcat
- Deploying a WAR on IBM WebSphere
- Deploying a WAR on WebSphere Liberty
- Deploying a WAR on Oracle WebLogic
- Deploying a WAR on JBoss WildFly or EAP
Deploying a WAR file as a public instance
If you make no changes to the webapp before deployment, it will automatically be deployed as an author instance. If you change the name of the webapp to magnoliaPublic by for example renaming the WAR file to magnoliaPublic.war, it will be automatically deployed as a public instance. The name of the webapp folder determines the configuration that will be used. This is discussed in detail in WAR file with multiple configurations.
If you are not familiar with these procedures, use a standalone installation that ships with an application server.
Overview
Content Tools