Those two versions support a list of environment variables that could be used to start and tune the AEM instance.
Environment variable Description
CQ_PORT TCP Port used for stop and status scripts
CQ_HOST Hostname
CQ_INTERFACE Interface that this server should listen to
CQ_RUNMODE Run mode(s) separated by a comma
CQ_JARFILE Name of the jar file
CQ_USE_JAAS Use of JAAS (if true)
CQ_JAAS_CONFIG Path of the JAAS configuration
CQ_JVM_OPTS Default JVM options
Caution:
Note that some run modes, among them author and publish, need to be set before first starting AEM and can not be changed afterward. Before setting up an AEM instance that is supposed to be used in production,
Windows platform start.bat script example
SET CQ_PORT=1234 & ./start.bat
Unix platform start script example
CQ_PORT=1234 ./start
Note:
The start script launches the AEM Quickstart installed under the /app folder
Stopping Adobe Experience Manager
To stop AEM, do one of the following:
Depending on the platform you are using:
If you started AEM from either a script or the command line, press Ctrl+C to shut down the server.
If you have used the start script on UNIX, you must use the stop script to stop AEM.
If you started AEM by double-clicking the jar file, click the On button on the startup window (the button then changes to Off) to shut down the server.
Stopping Adobe Experience Manager from the Command Line
The stop script is available under the /bin directory. Both Unix and Windows versions are provided. The script stops the running instance installed in directory.
Unix platform stop script example
./stop
Windows platform stop.bat script example
./stop.bat
If you just want to preconfigure the repository (without relocating it) you only have to:
- extract repository.xml to the required location
- update repository.xml as required
- create bootstrap.properties and define repository.config
No comments:
Post a Comment
If you have any doubts or questions, please let us know.