You are here
Home > AEM > In-Built JARs in AEM 6.4

In-Built JARs in AEM 6.4



In this article ( AEM6.4 inbuilt jars ) we are going to analyses about /opt folder. In /opt folder we can see some JARs and we are going to explore them.

PATH : /opt/aem/crxquickstart/opt

Tree command :

AEM6.4 inbuilt jars












1.Composite-init.jar: ( Still WIP state)
This Jar present inside of extensions folder.

Composite-init is basically a run mode that will be is used for Composite node store AEM setup.

Future Plan :
1.Create crx-quickstart with customer application to merged.
2. Enable composite capabilities using composite-init runmode
3.Start instance with New Runmode. ( Composite Node store mode )
4.Upgrade the existing instance with this new composite enabled mode.

Yet to hear from Adobe once implemented.

2.Crx2oak.jar :

Crx2oak is used to upgrade old CQ version Jackrabbit 2 to oak repository.
It is also used to copy data between oak repo.

Adobe provides clear steps on how to use this JAR file while performing upgrades.

Troubleshoot steps:
While performing , please ensure to add the below log level to know the status of your upgrade.
–log-level DEBUG (or) –log-level Trace
Logs are redirected to upgrade.log .


Jtail.jar is present inside helpers folder.

Usage :
Jtail.jar seems to be useful if you run AEM instance on windows OS.

This is used to view error log and get details about running instance.

Command :
Java -jar jtail.jar

In-Built JARs in AEM 6.4


In-Built JARs in AEM 6.4

4.Proxy-2.1.jar :

Proxy jar is to use to proxying the incoming and outgoing request.

Usages :

This Jar can be useful to identify some connection lost before and after firewall.

New Syntax :

Java -jar proxy-2.1.jar <localport> :<host> :<remoteport>  <options>

Whereas in my case

Java -jar proxy-2.1.jar 8090:localhost:5502 <options as needed>

This Jar as backward compatibility , we can use old syntax as well

Old Syntax:

Java -jar proxy-2.1.jar <host>  <remoteport>  <localport> <options>

Once we started the proxy.jar , we can access the instance via localhost:<remoteport>

In-Built JARs in AEM 6.4

C > Represent Cookies and its IDs

S > Sessions.

Note : Ensure AEM started already to access it via Proxyport.


Rlog.jar can be known as requestlog.jar. This jar will act on top of request.log

Usages :

This Jar is very useful to debug slow requests. Mainly we consider this on our performance optimization.


Java -jar rlog.jar -n <numbers> </path/to/request.log>

Sample :

Java -jar rlog.jar -n 10 ../../log/request.log

In-Built JARs in AEM 6.4

-n 10 > Shows top 10 slow request details


This jar is of no use with current AEM release and will be dropped anytime.

Earlier it tested performance of lock  acquiring for a file ( using -f option) and displays the time .


This is actually SerDE ( Serialization / Deserialization ) concept on JAVA. Notsoserial.jar is used to mitigate this issue and this jar includes adobe’s modification as well.

Call this jar on AEM startup JVM

In-Built JARs in AEM 6.4
AEM config :

Search for Deserialization firewall configuration in OSGi configMgr.

This config is dynamic and can be changed whenever required

Whitelist values : Added classes or package will be allowed for Deserialization.

Blacklist Values : This contains classes and that never allow Deserialization.

Logs : Full-stack or classes

In-Built JARs in AEM 6.4

Access the below URL to verify.

In-Built JARs in AEM 6.4

Author Note :

Thanks for your kind response. If you have any queries please do comments . Also if you need any new articles related to AEM admin , please share.

You may like: Restore AEM Using Journal Log
Follow us in Facebook

6 thoughts on “In-Built JARs in AEM 6.4

  1. I was looking at some of your articles on this site and I believe this internet site is really instructive! Keep on posting .

  2. Appreciate it for this howling post, I am glad I observed this internet site on yahoo.

  3. Pingback: bear onesie

Leave a Reply