51黑料不打烊

The run mode is author

The instance (Repository, Felix OSGI environment, bundles, and so on) is installed in is ${user.dir}/crx-quickstart, where ${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-65-lts.

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.xml file 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 authenticate a user is to disable the global administrative security of the WebSphere庐 server. In order to do that, 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 the AEM war file

Make your configurations in the web.xml file if needed. For more info, see General Description above.

• Unpack the WEB-INF/web.xml file
• Change the sling.run.modes parameter to publish
• Uncomment initial sling.home parameter and set this path as you need
• Repack the web.xml file.

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

Startthe AEM web application

Prepare Tomcat Server

• Increase VM memory settings:

  • In bin/catalina.bat (resp catalina.sh on UNIX庐) add the following setting:

    code language-none
    set "JAVA_OPTS= -Xmx2048m`

• Tomcat does not enable 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 the ROOT webapp
  • Rename the ROOT.war folder in Tomcat鈥檚 webapps folder
  • Start the 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. In order to achieven 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 see the following multipart-config in an example web.xml file below:

  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 the AEM web application

• Download the AEM war file.

• Make your configurations in the web.xml file if needed.

  • Unpack the WEB-INF/web.xml file
  • Change the sling.run.modes parameter to publish
  • Uncomment the initial sling.home parameter and set this path as you need
  • Repack the web.xml file.

• Rename the 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鈥檚 webapps folder

• Wait until AEM is installed.