AEM with JBoss EAP 6.3.0/6.4.0 installation and integration

Before a deployment read the General Description above.

Prepare JBoss server

Set Memory arguments in your conf file(e.g. standalone.conf)

• JAVA_OPTS="-Xms64m -Xmx2048m"

if you use the deployment-scanner for to install the AEM web application it might be good to increase the deployment-timeout, for that set a deployment-tiimeout attribute in the xml file of your instance (e.g configuration/standalone.xml):

1 2 3

<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">             <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" deployment-timeout="1000"/> </subsystem>

Deploy AEM web application

- Upload the AEM web application in your JBoss Administration Console.

- Enable the AEM web application.

AEM and Websphere application server installation and integrations

WebSphere 8.5

Before a deployment read the General Description above.

Server Preparation

• Let Basic Auth Headers pass through:
  • One way to let AEM to authenticate a user is to disable the global administrative security of the WebSphere server, to do so: 
  • go to Security -> Global Security and uncheck the Enable administrative security checkbox, save and restart the server.
• set "JAVA_OPTS= -Xmx2048m"
• If you want to install AEM using context root = / then you have first to change the context root of the existing Default web application

Deploy AEM web application

• Download AEM war file
• Make your configurations In web.xml if needed (see above in the General Description)
  • Unpack WEB-INF/web.xml file
  • change sling.run.modes parameter to publish
  • uncomment sling.home initial parameter and set this path as you need
  • Repack web.xml file
• Deploy AEM war file
  • Choose a context root 
• Start AEM web application

How to install two Instances of AEM on the same Application Server

For demonstration purposes it can be appropriate to install author and publish instance in one application server. For that do the following:

1. Change sling.home variable and sling.run.modes variables of the publish instance.
2. Unpack WEB-INF/web.xml file from the AEM war file.
2. Change sling.home parameter to a different path, (absolute and relative paths are possible).
3. Change sling.run.modes to publish for the publish instance.
4. Repack the web.xml file.
5. Rename the war files, so they have different  names: e.g. one rename to aemauthor.war and the other to aempublish.war.
6. Use higher memory settings, e.g. for default AEM instances use e.g.: -Xmx3072m
7. Deploy the two web applications.
8. After Deployment stop the two web applications.
9. In both author and publish instances assure that in the  sling.properties files the property felix.service.urlhandlers=false is set to false (default is that it is set to true).
10. Start the two web applications again.