APIs allow aggregation of content from various data sources. CMS & Marketing Products which supports OSGI & API plugins like Java Content Repository framework/standard allow dynamic and uniform approaches to access content through APIs.
Today, customers shop using the web, mobile, video, and media as they research and make purchases. Companies needs to offer consistent experiences across all of these channels and show consumers that they know exactly who they are and what they want — and that their brand is the best way to get it. It is vital to create, deliver, measure, and optimize customer experiences, from the checkout counter to the website to the mobile device, and beyond.
It is important to
– Get the right content to customers at the right time regardless of device
– Easily manage digital assets, focusing on quality and relevance.
– Dynamically deliver channel-optimized content.
– Rapidly deploy promotional content as a reaction to real-time market dynamics.
This requires the ability to leverage your existing information assets for content generation from your CMS or Marketing platform. Framework & standards like OSGI and Apache Sling and JCR content repository allows you to leverage the content using Rest interfaces.
The OSGI (Open Services Gateway Initiative) framework is a module system and service platform for the Java programming language that implements a complete and dynamic component model. Applications or components can be remotely installed, started, stopped, updated, and uninstalled without requiring a reboot.
Apache Sling is a web framework that uses a Java Content Repository, such as Apache Jackrabbit, to store and manage content. Sling applications use either scripts or Java servlets, selected based on simple name conventions, to process HTTP requests in a RESTful way.
Content Repository API for Java (JCR) is a specification for a Java platform application programming interface (API) to access content repositories in a uniform manner.
Adobe AEM is one such product which supports OSGI framework and allows you to pull content using Java content repository standard through APIs. APIs allow you to standardize your content and back-end business logic.
Adobe AEM & Integration with APIs for content and business logic
Adobe Experience Manager enables marketers and developers to design, manage, and deliver customer facing digital experiences across all interaction channels including web, mobile, social, video, and in-store. With Adobe Marketing Cloud, marketers can Combine data across solutions and third-party data sources, such as CRM, POS, email, and survey, to create a single view of the customer.
OSGi is a fundamental element in the technology stack of Adobe Experience Manager (AEM). It is used to control the composite bundles of AEM and their configuration.
You can create an Adobe CQ application that lets users to enter data into a web page and post the data to a custom Java Sling Servlet. The posted data is processed by the Sling Servlet through APIs. The Sling Servlet that is created encodes the submitted form data into JSON formatted data and returns the data to the web client where it is displayed.
Below diagram explain how AEM can leverage API Rest interfaces
This integration of OSGI and API plugins approach allows API developers to develop and test application components that have no dependencies on the content management system. The OSGi-based deployment approach further decouple development cycles of the web developer and the API developer.