How to Verify OSGi Bundle Status on All Publish Instances in AEM
This article explains how to verify that all OSGi bundles are active and functioning as expected on all AEM publish instances in a target environment.
Description description
Environment
Adobe Experience Manager (AEM) 6.5, LTS
Issue/Symptoms
-
You need to verify that all OSGi bundles are in the Active state and operating correctly on all publish instances within the green environment.
-
This request usually comes during or after environment switches, such as from green to blue, to verify system health and readiness.
-
No specific error messages are reported.
-
Publishers are accessible through URLs such as:
https://<publisher-1-host>/libs/granite/core/content/login.htmlhttps://<publisher-2-host>/libs/granite/core/content/login.html
-
The customer requests screenshots or status confirmation for each publish instance.
-
No reproducible error condition is present. This check is a proactive health check.
Cause
This verification is a routine health check to confirm that all OSGi bundles are running as expected after environment changes or deployments.
Resolution resolution
To verify bundle status, follow these steps:
-
Log in to each publish instance in the specified environment by using the provided URLs or hostnames.
-
Navigate to the OSGi Web Console.
- Go to
https://<publisher-host>:<port>/system/console/bundles. - Authenticate with the appropriate credentials.
- Go to
-
Review the Statuscolumn for all bundles.
- Ensure that every bundle is in the Active state.
- If any bundle is not active, such as a bundle in the Installed or Resolved state, note the bundle name and investigate further.
-
Repeat these steps for each publish instance in the environment.
Notes:
- If you need documentation or customer confirmation, capture a screenshot of the bundle status page.
- If requested, share the screenshots or the status summary with the customer through the approved communication channel.