CMS, Java

AEM Application Server (JBOSS) Install

Introduction:

Adobe Experience Manager can run either as a standalone server (the quickstart JAR file) or as web application within a third party application server (the WAR file). JAR and WAR are the file types AEM is released in.

JAR is used to standalone installation of AEM. Any web application to run needs a server for e.g. Tomcat, JBoss etc., Jetty is the server that comes prepackaged in AEM Jar, so when you run AEM using the JAR file, then the entire AEM is using Jetty to run and execute.

Jetty is not the only server compatible, but you can run AEM inside any application container, if you opt to do so, then you will need AEM WAR file and deploy AEM as standard web-app in those servers. Application server install may be more appropriate, if your existing development or deployment methods predominantly deal in WAR/EARs.

Now we could see how to install AEM in JBOSS Application server.

Prerequisites:

  • jboss-eap-7.0.0-installer.jar
  • AEM 6.3/6.4 WAR file

 

Download and Install JBoss:

Use jboss-eap-7.0.0-installer jar file to install JBoss. Once the installation of JBoss is done, we can install AEM server in to JBoss application server. To download and install JBoss Application Server in to your machine, refer  How to install JBoss EAP.

Download AEM WAR:

Customers with a valid Maintenance & Support contract with ADOBE can download the Adobe Experience Manager (jar and as well as WAR) from the Adobe Licensing Website (LWS).

Integrate AEM into JBoss:

  • Go to bin folder of JBoss HOME_DIRECTORY (e.g., c\jboss\bin) and click on standalone.bat file to start the JBoss server.
  • By default JBoss is installed on 8080 port, hit http://<hostname>:<port> to check if Jboss server has started successfully.
  • Give “admin” as username and password.
  • On the JBoss start page, click on the “Administration Console” link to go to the Admin console.

  • In the Administration Console on JBoss server, click on the “Deployments”  option to deploy our AEM instance.

  • Click on “Add” button. To set the context root of the AEM, rename the war file. For e.g., if you want to access AEM as http://localhost:8080/aem63, then rename the war file to aem63.war.

 

 

  • Then a pop up will be opened to browse the aem war file. Select AEM WAR path, save it and enable it.

 

  • Now, AEM is installed in JBoss application server.

  • After couple of minutes access http://<hostname>:<port>/<contextroot> (e.g., http://localhost:8080/aem63), you will be prompted to enter license information.
  • Once you enter the license information, you will be navigated to a login page where you can login using admin/admin credentials.

  • Observe that, you will be normally redirected to start page of AEM.

Metrics:

Average load time for a page with content, load time of DOM content  are less when we use application server when compared to standalone AEM. We can see these metrics as below:

Application server (JBoss) Installation:

Standalone Installation:

From the above illustrations, it is clearly proved that application server runs faster than standalone AEM.

I would like to thank Ravi Kumar Sangubotla for his guidance. I hope you enjoyed this blog post!

About The Author

Leave a Reply

*