Slurp.. technical blogs!: AEM bundles

Thursday, August 3, 2023

New bundles in AEM Cloud

In this blog, we will discuss what New bundles in AEM as a Cloud Service(AEMaaCS) has been introduced.

AEM as a Cloud Service has some new bundles:

com.adobe.bp.bp-cloudservice – Adobe Brand Portal Cloudservice configuration
com.adobe.bp.bp-distribution – Adobe Brand Portal Distribution Implementation
com.adobe.cq.cq-ref-update-processor-util – AEM – Reference Update Processor Utility bundle
com.adobe.cq.dam.cq-dam-ui-models – AEM – DAM Sling Model Bundle
com.adobe.cq.inbox.cq-inbox-api – AEM – Inbox API
com.adobe.cq.remotedam.cq-remotedam-api – Adobe CQ Remote DAM API Bundle
com.adobe.cq.ups-integration – Unified Profile Service IMS integration
com.adobe.cq.ups-profile-lookup – Unified Profile Lookup routines
com.adobe.granite.jobs.async.ui.commons – Adobe Granite Async Jobs
com.adobe.granite.toggle.api – Adobe Granite Toggle API
com.adobe.granite.toggle.impl – Adobe Granite Toggle Implementation
com.adobe.granite.toggle.impl.static – Adobe Granite Toggle Implementation
com.day.cq.dam.cq-dam-asset-sourcing – Day Communique 6 DAM Asset Sourcing Implementation
com.day.cq.remote.content.renderer – Remote Content Renderer
org.apache.felix.configadmin.plugin.interpolation – Apache Felix Configuration Admin Values Interpolation Plugin
org.apache.felix.log – Apache Felix Log Service
org.apache.felix.rootcause – Apache Felix – Root Cause Analysis
org.apache.jackrabbit.oak-authorization-principalbased – Oak Principal-Based Authorization
org.apache.sling.feature.apiregions – Apache Sling Feature API Regions Runtime
rideau – Adobe Rideau (PDF API)

Sunday, April 24, 2022

OSGi is a fundamental element in the technology stack of AEM. It is used to control the composite bundles of AEM and their configuration. OSGi “provides the standardized primitives that allow applications to be constructed from small, reusable and collaborative components.

OSGi

OSGi is a Java framework for developing and deploying modular software programs and libraries. OSGi has two parts.

Bundles or Plug-in
Java Virtual Machine (JVM)-level service registry.

In this article, we will focus on bundle states only.

A Bundle object is the access point to define the lifecycle of an installed bundle. Each bundle installed in the OSGi environment must have an associated Bundle object.

A bundle must have a unique identity, a long, chosen by the Framework. This identity must not change during the lifecycle of a bundle, even when the bundle is updated. Uninstalling and then reinstalling the bundle must create a new unique identity.

A bundle can be in one of six states:

Name	Value	Description
UNINSTALLED	0x00000001	Only visible after a bundle is uninstalled; the bundle is in an unusable state but references to the bundle object may still be available and used for introspection.
INSTALLED	0x00000002	Visible if the bundle’s code dependencies are not resolved. The Framework may attempt to resolve an INSTALLED bundle’s code dependencies and move the bundle to the RESOLVED state.
RESOLVED	0x00000004	The Framework has successfully resolved the bundle’s code dependencies, but the bundle is not active. Dependencies include: the bundle’s classpath; the bundle’s package dependencies; the bundle’s required bundle dependencies;
STARTING	0x00000008	The bundle’s start method is active. A bundle must be in this state when the bundle’s BundleActivator.start(BundleContext) is called. If the BundleActivator.start method completes without exception, then the bundle has successfully started and must move to the ACTIVE state.
STOPPING	0x00000010	The bundle’s stop method is active. A bundle must be in this state when the bundle’s BundleActivator.stop(BundleContext) method is called. When the BundleActivator.stop method completes the bundle is stopped and must move to the RESOLVED state.
ACTIVE	0x00000020	The bundle has been successfully started and activated.