Magnolia is also available as a Web Application Archive. WAR is the recommended way to deploy Magnolia in production. The WAR file includes the CMS application but no application server or add-ons. You need to deploy it on an existing application server.

Application server

Enterprise Edition

Community Edition

Tomcat

WAR

WAR

JBoss

WAR

WAR

IBM WebSphere

WAR

no WAR available

Oracle WebLogic 10

WAR

no WAR available

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 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.

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels