Start Adobe Experience Manager AEM in command line

1. Get license jar (e.g. cq-quickstart-6.3.0.jar) and license.properties file from Adobe.
Please make sure you have a valid licensed product.

2. Move the above two files in the same folder

3. Rename jar file to desired run modes and port  (e.g. aem-author-4502.jar)

4. Start jar using Java 8.
Example of run command:
java -XX:MaxMetaspaceSize=1024m -Xmx1024M -jar aem-author-4502.jar

5, It takes few minutes to start - once started you can get login screen with admin/admin user.

Use crontab on AWS RedHat

1. Get your script defined and get it into a proper location on the machine:

touch script.sh
chmod +x script.sh

vi script.sh

Example of script copying files to a user home folders:

#!/bin/bash
cd /folder/test-pckg/
chown dest_user:dest_user filename*
mv filename* /home/dest_user/prod-pckg/

2. Add your script to crontab

crontab -e 
30 21 * * * /folder/test-pckg/script.sh

The above runs each day at 21:30 local machine time.

3. Verify if it runs under cron tab logs:
cat /var/log/cron

You should grep for a line like the below:
Jun 20 21:30:01 instance-name CROND[12092]: (root) CMD (/folder/script.sh)

Get cURL to not show progress bar

It's very simple, just add -s parameter:

curl -s http://domain.com

AEM curl command to get JMX status of replication queue - pending items

Syntax is the following:

curl -u admin:admin -X GET http://IP:PORT/system/console/jmx/com.adobe.granite.replication%3Aid%3D%22publishagentname%22%2Ctype%3Dagent

It gets all fields, to parse it, you can use the bellow

curl -u admin:admin -X GET http://IP:PORT/system/console/jmx/com.adobe.granite.replication%3Aid%3D%22publishagentname%22%2Ctype%3Dagent | grep "QueueNumEntries" | cut -d ">" -f5 | cut -d "<" -f1'

Linux - check every few seconds if file size grows using Watch command

Complete syntax:

watch -n 5 ls -lh filename

Output (error.log is the filename):

Office 365 - Check O365 quota via outlook.office.com

From under Settings->Options->General->My Account as described in below picture:

Splunk forwarder not working

1. Logs are not splunk despite splunk showing as running:

2. Looking at the PID 13223, there is nothing specific to splunk running at this PID.

3. For some reasons, splunk PID remained hanged, so manually remove pid file from under "/opt/splunkforwarder/var/run/splunk" and start splunk.

4. This time everything fine and log files are splunked.