Starting-stopping AEM from the Command Line


The start script is available under the /bin directory. Both Unix and Windows versions are provided. The script starts the instance installed in  directory.
Those two versions support a list of environement variables that could be used to start and tune the AEM instance.
Environment variableDescription
CQ_PORTTCP port used for stop and status scripts
CQ_HOSTHost name
CQ_INTERFACEInterface that this server should listen to
CQ_RUNMODERunmode(s) separated by comma
CQ_JARFILEName of the jarfile
CQ_USE_JAASUse of JAAS (if true)
CQ_JAAS_CONFIGPath of the JAAS configuration
CQ_JVM_OPTSDefault 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 afterwards. 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.
    chlimage_1
  • 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

1
./stop

Windows platform stop.bat script example

1
./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
Again, before starting the actual installation.

No comments:

Post a Comment