AEM6 with CRX2 | Community
Skip to main content
B
Bxxs93
Level 2
October 16, 2015
Solved

AEM6 with CRX2

  • October 16, 2015
  • 3 replies
  • 1227 views

I have some Questions about AEM6 with CRX2 :

- Is there an installation of AEM6 which comes with CRX2 or do i have to upgrade a CQ5 Version to AEM6 to run AEM6 with CRX2?

- Which CRX2 Version should i use to run with AEM6?

- How can i transfer content with the commandline (in Linux) like the Package Manager is doing ? Is there a option to do it the same way with the commandline (no restriction about the filesize, in the Package manager there are some restrictions about it)

 

thx a lot

julian

Best answer by Mshaji

If you plan on running AEM 6 with a CRX 2 backend, you can simply run the jar at this point. However, note that for all upgrades from versions up to and including AEM 5.5 this needs to be explicitly stated via the "crx2" runmode option when the AEM 6.0 jar is first started. To do this, run the quickstart with the following command:

java -jar aem-quickstart.jar -r crx2

If the runmode is not specified, the AEM 6.0 instance will start with a new CRX 3 repository instead of the existing CRX 2 one.

For package manager commands please follow this link

http://balawcm.wordpress.com/2013/02/13/curl-it-out-adobe-cq5-curl-commands-and-usage/

You need to have CURL installed on your system

3 replies

Lokesh_Shivalingaiah
Lokesh_Shivalingaiah
Level 10
October 16, 2015

You can do an 'In-place upgrade' which will use your existing CRX2 with AEM 6.0. Refer here [1]

[1] http://docs.adobe.com/docs/en/aem/6-0/deploy/upgrade.html#In-Place Upgrade

    M
    Community Advisor
    MshajiCommunity AdvisorAccepted solution
    Community Advisor
    October 16, 2015

    If you plan on running AEM 6 with a CRX 2 backend, you can simply run the jar at this point. However, note that for all upgrades from versions up to and including AEM 5.5 this needs to be explicitly stated via the "crx2" runmode option when the AEM 6.0 jar is first started. To do this, run the quickstart with the following command:

    java -jar aem-quickstart.jar -r crx2

    If the runmode is not specified, the AEM 6.0 instance will start with a new CRX 3 repository instead of the existing CRX 2 one.

    For package manager commands please follow this link

    http://balawcm.wordpress.com/2013/02/13/curl-it-out-adobe-cq5-curl-commands-and-usage/

    You need to have CURL installed on your system

      AmitVishwakarma
      Community Advisor
      AmitVishwakarmaCommunity Advisor
      Community Advisor
      January 18, 2025

      1. Is there an installation of AEM6 which comes with CRX2 or do I have to upgrade a CQ5 version to AEM6 to run AEM6 with CRX2?

      • AEM 6 comes with CRX2 by default. However, AEM 6 uses CRX2 as the repository backend, and the upgrade from CQ5 to AEM 6 should not affect this. If you are running CQ5, upgrading it to AEM 6 will still have CRX2 unless you choose to migrate to CRX3 (or CRX 3.0, which is available in newer versions).

      2. Which CRX2 Version should I use to run with AEM6?

      • For AEM 6, you should use CRX2 version 2.6 or a version that's compatible with the AEM 6 version you are using. Typically, CRX2 is bundled with the AEM installation, so you would use the version that comes with the installation. If you are upgrading, ensure that the CRX2 version is compatible with the AEM version you are installing.

      3. How can I transfer content with the command line (in Linux) like the Package Manager is doing? Is there an option to do it the same way with the command line (no restriction about the file size, in the Package Manager there are some restrictions about it)?

      • Yes, you can transfer content via command line using CRX2 tools. The crx2 command-line tools and content-package-maven-plugin provide functionality similar to the Package Manager.
      • To transfer content without the file size limitations:
        • Use the CRX2 package manager commands such as crx2package for creating and deploying content packages. You can create content packages and transfer them using commands such as package:install, which allows large file sizes without restrictions.
        • Alternatively, Sling's JCR-based API or SlingPostServlet could be used to create content via HTTP POST.

      The Package Manager does indeed have file size restrictions, but you can bypass this by using lower-level tools (e.g., curl for HTTP requests, jcr:content export and import methods, or using Sling's JCR API directly).

      These methods allow greater control over content transfers and avoid the limitations of the GUI-based package manager interface.

      Terms & ConditionsAccessibility statement

      Loading footer...