- Deploying User Guide
- Introduction to the AEM Platform
- Deploying AEM
- Deploying and Maintaining
- Recommended Deployments
- Application Server Install
- Custom Standalone Install
- Command Line Start and Stop
- Configuring node stores and data stores in AEM 6
- Revision Cleanup
- How to Run AEM with TarMK Cold Standby
- RDBMS Support in AEM 6.4
- Oak Queries and Indexing
- Indexing via the Oak-run Jar
- Oak-run.jar Indexing Use Cases
- Troubleshooting Oak Indexes
- Opting Into Aggregated Usage Statistics Collection
- Troubleshooting
- Configuring AEM
- Basic Configuration Concepts
- Logging
- Configuring OSGi
- OSGi Configuration Settings
- Run Modes
- Web Console
- Replication
- Replicating Using Mutual SSL
- Troubleshooting Replication
- Expiration of Static Objects
- Version Purging
- Monitoring and Maintaining Your AEM instance
- Offloading Jobs
- Single Sign On
- Resource Mapping
- Enabling HTTP Over SSL
- Consistency and Traversal Checks
- Performance Guidelines
- Performance Optimization
- Assets Performance Guide
- Configuration How-To Articles
- Removing the Geometrixx Sites
- Configuring Web Console
- Upgrading to AEM 6.4
- Upgrading to AEM 6.4
- Planning Your Upgrade
- Assessing the Upgrade Complexity with the Pattern Detector
- Backward Compatibility in AEM 6.4
- Upgrade Procedure
- Using Offline Reindexing To Reduce Downtime During an Upgrade
- Performing an In-Place Upgrade
- Lazy Content Migration
- Using the CRX2Oak Migration Tool
- Pre-Upgrade Maintenance Tasks
- Post Upgrade Checks and Troubleshooting
- Upgrading Custom Search Forms
- Sustainable Upgrades
- Upgrading Code and Customizations
- Upgrade Steps for Application Server Installations
- List of Obsolete Bundles Uninstalled After the Upgrade
- Repository Restructuring
- Repository Restructuring in AEM 6.4
- Common Repository Restructuring in AEM 6.4
- Sites Repository Restructuring in AEM 6.4
- Assets Repository Restructuring in AEM 6.4
- Dynamic Media Repository Restructuring in AEM 6.4
- Forms Repository Restructuring in AEM 6.4
- E-Commerce Repository Restructuring in AEM 6.4
- Repository Restructuring for AEM Communities in 6.4
- eCommerce
- Best Practices
Command Line Start and Stop
AEM 6.4 has reached the end of extended support and this documentation is no longer updated. For further details, see our technical support periods. Find the supported versions here.
Starting Adobe Experience Manager from the Command Line
The start script is available under the <cq-installation>/bin directory. Both Unix and Windows versions are provided. The script starts the instance installed in <cq-installation> directory.
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 | Host name |
| CQ_INTERFACE | Interface that this server should listen to |
| CQ_RUNMODE | Runmode(s) separated by comma |
| CQ_JARFILE | Name of the jarfile |
| CQ_USE_JAAS | Use of JAAS (if true) |
| CQ_JAAS_CONFIG | Path of the JAAS configuration |
| CQ_JVM_OPTS | Default JVM options |
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, please see the run modes documentation for details.
Windows platform start.bat script example
SET CQ_PORT=1234 & ./start.bat
Unix platform start script example
CQ_PORT=1234 ./start
The start script launches the AEM Quickstart installed under the <cq-installation>/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 <cq-installation>/bin directory. Both Unix and Windows versions are provided. The script stops the running instance installed in <cq-installation> 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.xmlto the required location -
update
repository.xmlas required -
create
bootstrap.propertiesand definerepository.config
Again, before starting the actual installation.
Business.Adobe.com resources
Resources
Adobe Account
