Application Server Install application-server-install

the run mode is author

the instance (Repository, Felix OSGI environment, bundles, and so on) is installed in ${user.dir}/crx-quickstartwhere ${user.dir} is the current working directory, this path to crx-quickstart is called sling.home

the context root is the war file name for example, aem-6

run mode : configure the sling.run.modes parameter in the WEB-INF/web.xml file of the AEM war file before deployment

sling.home: configure the sling.home parameter in the WEB-INF/web.xmlfile of the AEM war file before deployment

context root: rename the AEM war file

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 = /, change the context root of the existing Default 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 (if you want to set the sling run modes you need to select the detailed steps of the deploy wizard, then specify it in step 6 of the wizard)

Start AEM web application

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

Enable the AEM web application.

In ${myDomain}/config/config.xmladd to the security-configuration section:

• <enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials> see on https://xmlns.oracle.com/weblogic/domain/1.0/domain.xsd for the correct position (per default to position it at the end of the section is ok)

Increase VM Memory settings:

• open ${myDomain}/bin/setDomainEnv.cmd (resp .sh) search for WLS_MEM_ARGS, set, for example, set WLS_MEM_ARGS_64BIT=-Xms256m -Xmx2048m
• restart WebLogic Server

Create in ${myDomain} a packages folder and inside a cq folder and in it a Plan folder

Download AEM war file

Put the AEM war file into the ${myDomain}/packages/cq folder

Make your configurations In WEB-INF/web.xml if needed (see above in the General Description)

• Unpack WEB-INF/web.xmlfile
• change sling.run.modes parameter to publish
• uncomment sling.home initial parameter and set this path as you need (see General Description)
• Repack web.xml file

Deploy AEM war file as an Application (for the other settings, use the default settings)

The installation can take time…

Check that the installation has finished as mentioned above in the General Description (for example, tailing the error.log)

You can change the context root in the Configuration tab of the web application in the WebLogic /console

Prepare Tomcat Server

• Increase VM memory settings:

  • In bin/catalina.bat (resp catalina.sh on UNIX®) add the following setting:
  • set "JAVA_OPTS= -Xmx2048m

• Tomcat enables not admin or manager access at installation. Therefore, you have to manually edit tomcat-users.xml to allow access for these accounts:

  • Edit tomcat-users.xml to include access for admin and manager. The configuration should look similar to the following example:

    code language-xml

    <?xml version='1.0' encoding='utf-8'?> <tomcat-users> role rolename="manager"/> role rolename="tomcat"/> <role rolename="admin"/> <role rolename="role1"/> <role rolename="manager-gui"/> <user username="both" password="tomcat" roles="tomcat,role1"/> <user username="tomcat" password="tomcat" roles="tomcat"/> <user username="admin" password="admin" roles="admin,manager-gui"/> <user username="role1" password="tomcat" roles="role1"/> </tomcat-users>

• If you like to deploy AEM with context root “/”, then you have to change context root of the existing ROOT webapp:

  • Stop and undeploy ROOT webapp
  • Rename ROOT.war folder in tomcat’s webapps folder
  • Start webapp again

• If you install the AEM web application using the manager-gui then you need to increase the maximal size of an uploaded file, as the default only allows 50MB upload size. For that open the web.xml of the manager web application,

  webapps/manager/WEB-INF/web.xml

  and increase the max-file-size and max-request-size to at least 500MB, see the following multipart-config example of such a web.xml file.

  code language-xml
  <multipart-config> <!-- 500MB max --> <max-file-size>524288000</max-file-size> <max-request-size>524288000</max-request-size> <file-size-threshold>0</file-size-threshold> </multipart-config>

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.

• Rename AEM war file to ROOT.war if you want to deploy it as root webapp. Rename it to aemauthor.war if you want to have aemauthor as context root.

• Copy it into tomcat’s webapps folder.

• Wait until AEM is installed.