Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

how to deploy custom component author to publisher in adaptive form

Avatar

Avatar
Validate 1
Level 1
ramandeep
Level 1

Likes

0 likes

Total Posts

23 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Applaud 5
View profile

Avatar
Validate 1
Level 1
ramandeep
Level 1

Likes

0 likes

Total Posts

23 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Applaud 5
View profile
ramandeep
Level 1

22-05-2020

I have created a custom component in CRXDE repository by coping and pasting existing component in AEM author. I am able to see that component in Tools -> General -> Components section in author instance. Is there any way to replicate the same on publisher as the component is missing in publish instance.

 

 

component.png

 

Thanks in advance

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
MVP
Theo_Pendle
MVP

Likes

236 likes

Total Posts

251 posts

Correct Reply

105 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 10
Ignite 1
View profile

Avatar
Validate 1
MVP
Theo_Pendle
MVP

Likes

236 likes

Total Posts

251 posts

Correct Reply

105 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 10
Ignite 1
View profile
Theo_Pendle
MVP

23-05-2020

Hi @ramandeep,

CRXDE is a great tool for manipulating the JCR but it's only one small part of the development ecosystem you'll need to effectively deliver change on the AEM platform. If you want to create components, you should do so in an IDE and save your changes to a codebase project under version control, with a build pipeline to make sure that you are delivery reliable, quality change!

I strongly recommend that you follow the WKND Tutorial, which will teach you to set up your development tools, create a new project and create your first custom component.

If you are working for a company that has put AEM in place and wants you to do development, make it clear that they will need to provide the time and resources to:

  • Train the development team or hire AEM developers
  • Set up development tooling
  • Put in place at least three environnements: DEV, UAT, PROD
  • Determine a clear governance for the asset with distinct operational and delivery roles
  • Define a testing strategy
  • Create a CI/CD pipeline
  • Etc.

There is an analogy I often use with non-technical people who don't understand the scope of what it means to host and deliver change to a platform like AEM. AEM and the Adobe Experience and Marketing platforms are consistently rated at the top of their respective categories. AEM is to CMS what a Formula 1 car is to land vehicles. You can't buy a Formula 1 car and expect to win races if you don't also hire a pilot, engineers, mechanics, buy their equipment and put rent a garage. It's the same if you want to successfully run an enterprise piece of software 🙂

However, if you want to copy your work from one instance to another you can do so by building a package that includes your changes and replicating the package to Publisher. To be clear though, this is a one-shot hack and in no way replaces a everything I mentioned above!

  1. Go to http://localhost:4502/crx/packmgr/index.jsp
  2. Create a new package
  3. Add a filter to include your modifications
  4. Click on Build
  5. Then click on More > Replicate to install the package on Publisher
    Selection_021.jpg

Answers (1)

Answers (1)

Avatar

Avatar
Shape 1
Level 2
toimrank
Level 2

Likes

9 likes

Total Posts

22 posts

Correct Reply

1 solution
Top badges earned
Shape 1
Validate 1
Give Back
Boost 5
Boost 3
View profile

Avatar
Shape 1
Level 2
toimrank
Level 2

Likes

9 likes

Total Posts

22 posts

Correct Reply

1 solution
Top badges earned
Shape 1
Validate 1
Give Back
Boost 5
Boost 3
View profile
toimrank
Level 2

23-05-2020

Hi Ramandeep,

 

This is not the correct approach. This must come through code in both author and publish instance after succesful deployment.

For the current scenario you can follow below steps:

1. Replicate all the node from crx/de.

2. As mentioned above, create a package of your component and replicate the same.