Implementing an AEM Connector | AEM Community Blog Seeding

[kautuk_sahni]

Implementing an AEM Connector by Adobe

Abstract

Provided below are useful references for building AEM Connectors and should be read in conjunction with guidance on submitting and maintaining connectors.

Note that a Developer license for AEM can be obtained through the Adobe Exchange Program.

Common Integration Patterns
AEM is a cutting-edge web experience management solution and offers many potential areas of integrations. Common integration patterns include:

Pulling data from an external system into AEM. For example, exporting contact information from a CRM to make it available to a wider audience visiting an AEM-powered website. Implementations should use Sling’s Scheduled Jobs, which guarantees that the job is executed even if containers go down. Code should be designed to assume that the job can potentially be triggered more than once.
Exporting data from AEM into an external system. For example, newsletter subscription settings submitted on an AEM-powered website to a CRM.
Retrieving assets from AEM. For example, an external Content Management System (CMS) referencing an asset stored in AEM Assets. Or as another example, a PIM system linking to an image in AEM Assets.
Storing assets in the AEM infrastructure. For example, a Marketing Resource Management (MRM) system storing an approved asset in AEM Assets.
Configuring and rendering a custom UI component. For example, allow an author to drag and drop a video component and configure a specific video to play on the live site.

Acting on an asset with a partner service. For example, sending an asset to a video platform when a page is published.
Analyzing a site, page, or asset in the AEM admin console. For example, making SEO recommendations for an existing or unpublished page.
Page-level access to user data maintained by an external service. For example, leverage demographic information to personalize the site experience. Read about ContextHub, a framework for storing, manipulating, and presenting context data.
Translating site copy or asset metadata. See the AEM Translation Framework Bootstrap Connector for sample code using the AEM Translation Framework, which is the preferred implementation of translation connectors.
Useful Documentation
Experience Manager as a Cloud Service documentation provides valuable insights into developing in AEM. Below are some specific technical topics and references that you may find useful while implementing an AEM connector:

Adobe Consulting Services (ACS) AEM Samples for well-commented code to help educate AEM developers
The various documentation links in the Common Integration Patterns section of this article

Read Full Blog

Implementing an AEM Connector

Q&A

Please use this thread to ask the related questions.