You are here
Home > AEM > AEM – Best approaches for Maintenance Releases and Validating Packages

AEM – Best approaches for Maintenance Releases and Validating Packages

AEM-Best-Approaches-For-Maintenance-Releases-And-Validating-Packages

AEM Maintenance:

In this article we are going to cover AEM Maintenance releases standard and validating packages before deploying to AEM instances.

1.Maintenance release:

Earlier we use to get Hotfix from Day care if we face any platform related issues . Now instead we get Cumulative Fix pack .

1. Hot fix is replaced by Cumulative Fix pack.

2.Service Pack .

2.Installation Overview:

AEM-Installation-overview

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3.Installation methods :

 

i).Package Manager Console:

This is the default console where AEM resource logins and install/build/download the selected packages.

Console URL : <hostname:port>/crx/packmgr/index.jsp

Pros : UI console provides easy access to users . Activity log provides the exact status of your action performed in package manager console.

AEM – Best approaches for Maintenance Releases and Validating Packages

Each letter in starts represent the status for each node.

A : Added new content/code to specified path.

D: Deleted content/code.

U: Updated

-: No action taken (left as it is )

E: Error on path.

ii).Curl Commands via API

Usually admin prefer this method if package is more in size.

Curl commands executes faster .

All the steps which performed in package manager can be accomplished by CURL. Many websites provides detailed walk through on each commands.

Best URL to prefer : http://www.aemcq5tutorials.com/tutorials/adobe-cq5-aem-curl-commands/

4.Deployment challenges:

Below are most common challenges during deployment.

a.OSGi Export changes : List unsatisfied package imports.

b.Overlay conflicts : List any Overlay and rebase issues . Inform conflict on JSP, CSS , JS overlays.

To overcome this challenges , validate the packages before deploying into servers.

AEM – Best approaches for Maintenance Releases and Validating Packages

Select the checkbox the types to be validated. Once selected click on Validate.

AEM – Best approaches for Maintenance Releases and Validating Packages

Activity log shows the validated logs. In my case it shows issue on OSGi imports.

AEM – Best approaches for Maintenance Releases and Validating Packages

From this log, AEM release engineers can be notified with errors/incompatibility before installing the packages .

5.Installation Validation :

Step 1.Bundle starts to confirm if it is in Active state.

Step 2.Tail error.log and looks any ERROR Keyword .

Step 3.Check the below status on JMX – OSGi console

AEM – Best approaches for Maintenance Releases and Validating Packages

Active > False

Active resource count > 0

Both the condition needs to be satisfied if installed properly.

Step 4: In case to check the product version , use below URLs

4a.<hostname:port>/libs/cq/core/content/welcome.html

#At the bottom of the screen we can see the product version , Service pack , version and all other details.

4b. .<hostname:port>/system/console/productinfo

 

6.Best practice during Releases:

1.Test in Lower environment.

2.Backup – PROD instances (referrably Offline backup )

3.Deploy

4.Restart  AEM . ( Most probably it is good to clear cache )

5.Test and Validate the version and few other checkpoints.

6.Release the environment.

If you need any support , please contact me @ www.devopscracks.com

You may like: Restore AEM Using Journal Log

Follow us in Facebook

6 thoughts on “AEM – Best approaches for Maintenance Releases and Validating Packages

  1. Hey very cool website!! Man .. Excellent .. Amazing .. I’ll bookmark your web site and take the feeds also…I’m happy to find a lot of useful information here in the post, we need work out more strategies in this regard, thanks for sharing. . . . . .

  2. I must say, as a lot as I enjoyed reading what you had to say, I couldnt help but lose interest after a while.

Leave a Reply

Top