Magnolia 5.4 reached end of life on November 15, 2018. This branch is no longer supported, see End-of-life policy.
Deploying Magnolia as a WAR file on JBoss Application Server.
To deploy a WAR file on JBoss AS:
magnoliaAuthor.war
.JBOSS_HOME/standalone/deployments
.JBOSS_HOME/server/default/deploy
.The application server will automatically pick up the file and deploy it.
JBoss AS unpacks .war files to a tmp
directory and deletes the directory as part of the shutdown process. This means that every time JBoss AS restarts, the Magnolia webapp forgets everything – modules, repository, license key. To get around this issue, you can deploy the Magnolia webapp as an extracted (unpacked) directory or configure Magnolia to store the repository outside the tmp
directory. Alternatively, specify the following paths in your magnolia.properties
configuration. If you point the paths outside of JBoss AS tmp
directory, Magnolia will not reinstall on every startup and they will not be deleted on every shutdown.
magnolia.home=/somewhere/outside/of/jboss/tmp/folder magnolia.cache.startdir=${magnolia.home}/cache magnolia.upload.tmpdir=${magnolia.home}/tmp magnolia.exchange.history=${magnolia.home}/history magnolia.repositories.home=${magnolia.home}/repositories magnolia.logs.dir=${magnolia.home}/logs
Deploying an extracted directory
To deploy an extract directory:
/magnoliaAuthor.war
directory.JBOSS_HOME/standalone/deployments
.JBOSS_HOME/server/default/deploy
.magnoliaAuthor.war.dodeploy
.The application server will pick up extracted directory on startup and will deploy it.
http://localhost:8080/<WAR file name>
JBoss AS7+. It may happen that the Magnolia application is not deployed because of deployment timeout. You can avoid this by setting the deployment-timeout
parameter to higher value in JBOSS_HOME/standalone/configuration/standalone.xml
. The default is 60 seconds.
<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1"> <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" deployment-timeout="120"/> </subsystem>
Without this file placed under WEB-INF
folder, the context path will be the web application's folder name by default.
jboss-web.xml
file in WEB-INF
folder of your Magnolia instance.Add the following section in the file. Replace YourContextPath
with your actual context path which can be /
for a public instance, for example.
<jboss-web> <context-root>/YourContextPath</context-root> </jboss-web>
Restart JBoss AS. Your webapp should be available at http://localhost:8080/<YourContextPath>
context-root
value and rename the WAR file magnoliaPublic.war
.superuser/superuser
on http://localhost:8080/magnoliaPublic
and follow the instructions in Changing author to public instance.JBoss AS JNDI Datasource Setup