AEM as a Service

Adobe Experience Manager is an enterprise Content Management System and Digital asset management. It is a Software as a Service (SaaS) which is a suite of online cloud-based services provided by Adobe for Digital Asset Management.

In this blog, we will learn about the AEM installation process on Linux server and setting up the AEM service to avoid manual effort on starting AEM process every time the server is rebooted.

Once the AEM package is downloaded on your local server. It basically contains AEM Quickstart Jar (AEM_6.x_Quickstart.jar) and a License file which should be placed in the same installation folder on the instance running in Author or Publisher mode.

Installation process

• Create a installation directory named "aem" under opt directory.

mkdir -p /opt/aem/


• Copy the downloaded AEM package into the aem folder:

cp cq-quickstart-6.5.0.jar /opt/aem/cq-quickstart-6.5.0.jar
cp license.properties /opt/aem/license.properties

• Unpack the JAR file

java -jar /opt/aem/cq-quickstart-6.5.0.jar -unpack

• Unpacking of the jar files creates a folder named ‘crx-quickstart’ which contains the script to start/stop the AEM instance.

• Edit start script, if you want to run the aem instance in publisher mode.

CQ_PORT=4503
CQ_RUNMODE='publish'

• Start the aem process with this script

bash /opt/aem/crx-quickstart/bin/start

Implementation of AEM as a Service

1. Create the following file:

vi /etc/systemd/system/aem.service

[Unit]

Description=AEM Author/Publisher Service

[Service]

Type=simple

ExecStart=/opt/aem/crx-quickstart/bin/start

ExecStop=/opt/aem/crx-quickstart/bin/stop

RemainAfterExit=yes

[Install]

WantedBy=multi-user.target

2. Provide the permissions:

chmod 755 aem.service

3. Reload all systemd service files: 

systemctl daemon-reload

4. Check that it is working by starting the service with following commands

systemctl start aem.service

systemctl status aem.service

5. Enable the service to start on boot:

systemctl enable aem.service

Created symlink from /etc/systemd/system/multi-user.target.wants/aem.service to /etc/systemd/system/aem.service.

6. Reboot the server and check the status of AEM service once it boots up again. It should be up and running.

systemctl status aem.service