Product Communities

Android App - AEM Headless Example by Adobe Abstract Video: https://images-tv.adobe.com/mpcv3/6285/c09f070e-eafd-400b-a4b6-8c5eac6a47b2_1634842665.854x480at800_h264.mp4 Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). An Android application is provided that demonstrates how to query content using the GraphQL APIs of AEM. The AEM Headless Client for Java is used to execute the GraphQL queries and map data to Java objects to power the app. How to use Clone the aem-guides-wknd-graphql repository: git clone git@github.com:adobe/aem-guides-wknd-graphql.git Launch Android Studio and open the folder android-app Modify the file config.properties at app/src/main/assets/config.properties and update contentApi.endpoint to match your target AEM environment: contentApi.endpoint=http://10.0.2.2:4502 contentApi.user=admin contentApi.password=admin Download an Android Virtual Device (min API 28) Build and deploy the app using the Andro

React App - AEM Headless Example by Adobe Abstract React App Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). A React application is provided that demonstrates how to query content using the GraphQL APIs of AEM. The AEM Headless Client for JavaScript is used to execute the GraphQL queries that power the app. How to use Clone the aem-guides-wknd-graphql repository: git clone git@github.com:adobe/aem-guides-wknd-graphql.git Edit the aem-guides-wknd/react-app/.env.development file and ensure that REACT_APP_HOST_URI points to your target AEM instance. Update the authentication method (if connecting to an author instance). # Server namespace REACT_APP_HOST_URI=http://localhost:4503 REACT_APP_GRAPHQL_ENDPOINT=/content/graphql/global/endpoint.json #AUTH (Choose one method) # Authentication methods: 'service-token', 'dev-token', 'basic' or leave blank to use no authentication ... Open a terminal and run the commands: $ cd aem-gui

Getting started with SPA Editor and Remote SPA - Overview by Adobe Abstract Video: https://images-tv.adobe.com/mpcv3/5258/2391dff6-584d-4b22-9ae2-faeb78a10505_1620845706.854x480at800_h264.mp4 Welcome to the multi-part tutorial for developers looking to augment an existing React-based (or Next.js) Remote SPAs with editable AEM content using AEM SPA Editor. This tutorial builds upon the WKND GraphQL App, a React app that consumes AEM Content Fragment content over AEM’s GraphQL APIs, however does not provide any in-context authoring of SPA content. About the tutorial The tutorial intended to illustrate how a Remote SPA, or a SPA running outside the context of AEM, can be updated to consume and deliver content authored in AEM. Most activities in the tutorial focus on JavaScript development, however critical aspects are covered that revolve around AEM. These aspects include defining where the content is authored and stored in AEM and mapping SPA routes to AEM Pages. The tutorial is d

Create your first React SPA in AEM by Adobe Abstract Welcome to a multi-part tutorial designed for developers new to the SPA Editor feature in Adobe Experience Manager (AEM). This tutorial walks through the implementation of a React application for a fictitious lifestyle brand, the WKND. The React app will be developed and designed to be deployed with AEM’s SPA Editor, which maps React components to AEM components. The completed SPA, deployed to AEM, can be dynamically authored with traditional in-line editing tools of AEM. Local Development Environment A local development environment is necessary to complete this tutorial. Screenshots and video are captured using the AEM as a Cloud Service SDK running on a Mac OS environment with Visual Studio Code as the IDE. Commands and code should be independent of the local operating system, unless otherwise noted. NOTE New to AEM as a Cloud Service? Check out the following guide to setting up a local development environment using the AEM as a

Create your first Angular SPA in AEM by Adobe Abstract Welcome to a multi-part tutorial designed for developers new to the SPA Editor feature in Adobe Experience Manager (AEM). This tutorial walks through the implementation of a Angular application for a fictitious lifestyle brand, the WKND. The Angular app will be developed and designed to be deployed with AEM’s SPA Editor, which maps Angular components to AEM components. The completed SPA, deployed to AEM, can be dynamically authored with traditional in-line editing tools of AEM. The goal for this multi-part tutorial is to teach a developer how to implement an Angular application to work with the SPA Editor feature of AEM. In a real-world scenario the development activities are broken down by persona, often involving a Front End developer and a Back End developer. We believe it is beneficial for any developer who will be involved in an AEM SPA Editor project to complete this tutorial. Local Development Environment A local developm

Getting Started with AEM Headless - Content Services by Adobe Abstract Video: https://images-tv.adobe.com/mpcv3/d1a4ed05-9dae-492f-8505-66c2cfdccbe3_1564765898.1920x1080at3000_h264.mp4 AEM’s Content Services leverages traditional AEM Pages to compose headless REST API endpoints, and AEM Components define, or reference, the content to expose on these endpoints. AEM Content Services allows for the same content abstractions used for authoring web pages in AEM Sites, to define the content and schemas of these HTTP APIs. The use of AEM Pages and AEM Components empowers marketers to quickly compose and update flexible JSON APIs that can power any application. Content Services Tutorial An end-to-end tutorial illustrating how to build-out and expose content using AEM and consumed by a native mobile app, in a headless CMS scenario. This tutorial explores how AEM Content Services can be used to power the experience of an Mobile App that displays Event information (music, performance, art, e

Token-based authentication to AEM as a Cloud Service by Adobe Abstract AEM exposes a variety of HTTP endpoints that can be interacted with in a headless manner, from GraphQL, AEM Content Services to Assets HTTP API. Often, these headless consumers may need to authenticate to AEM in order to access protected content or actions. To facilitate this, AEM supports token-based authentication of HTTP requests from external applications, services or systems. In this tutorial well explore how an external application can programmatically authenticate and interact with to AEM as a Cloud Service over HTTP using access tokens. External Application overview This tutorial uses a simple Node.js application run from the command line to update asset metadata on AEM as a Cloud Service using Assets HTTP API. Local Development Access Token Local Development Access Tokens are generated for a specific AEM as a Cloud Service environment and providing access to Author and Publish services. These access tok

Accessing and Delivering Content Fragments Headless Quick Start Guide by Adobe Abstract Learn how to use AEM’s Assets REST API to manage Content Fragments and the GraphQL API for headless delivery of Content Fragment content. What are GraphQL and Assets REST APIs? Now that you have created some content fragments, you can use AEM’s APIs to deliver them headlessly. 1. The GraphQL API allows you to create requests to access and deliver Content Fragments. ->To use this, endpoints need to be defined and enabled in AEM, and if required, the GraphiQL interface installed. 2. The Assets REST API allows you to create and modify Content Fragments (and other assets). The remainder of this guide will focus on GraphQL access and Content Fragment delivery. How to Deliver a Content Fragment Using GraphQL Information architects will need to design queries for their channel endpoints in order to deliver content. These queries will generally only need to be considered once per endpoint per model.

Hi there, i wonder how you guys are thinking about the Tags feature in AEM Assets (as a cloud service). If we use Adobe Bridge to set keywords on assets before upload the keywords will be mapped to the field dc:subject and not cq:tags, I assume this is by design but how can we set tags on assets outside of AEM that map to the tag taxonomy we have in AEM Assets? Any input appreciated on this topic

Hi AllI need to write a UnitTest for a doGet method in a Servlet that extends SlingSafeMethodsServlet.  This is the doGet method I need to write the UnitTest for and I am not sure how to mock the resource for it:@Overrideprotected void doGet(@Nonnull SlingHttpServletRequest request, @Nonnull SlingHttpServletResponse response) throws IOException { final JsonResponse jsonResponse = new JsonResponse(response); final String title = request.getParameter("title"); final List<APIResult> locations = LocationFinderUtil.getLocationResultStream(request, searchService) .filter(result -> StringUtils.isNotBlank(title) && (StringUtils.containsIgnoreCase(result.getTitle(), title) || StringUtils.containsIgnoreCase(result.getAdditionalAddress(), title))) .map(APIResult::new) .collect(Collectors.toList()); jsonResponse.write(locations);} 

Join us for our next Adobe Campaign Community Q&A Coffee Break, on Thursday, December 2nd, 2021 @ 8am PT   Register here for this Adobe Campaign Community Q&A Coffee Break.   We'll be joined by Zariely Garcia aka @zariely8, Senior Technical Consultant for Adobe Campaign, who will be signed in here to the Adobe Campaign Community to chat directly with you on this thread to take your Adobe Campaign questions pertaining to her areas of expertise:  Data Import via other applications - Best practices to import data via SFTP/APIs using technical workflows   REQUIREMENTS TO PARTICIPATE  Must be signed in to the Community during the 1-hour period  Must post a Question about Adobe Campaign Coffee Break topic on this thread Think of this as the Adobe Campaign Community equivalent of an AMA, (“Ask Me Anything”), and bring your best speed-typing game   INSTRUCTIONS Click the blue “Reply” but

Step by Step approach to build AEM Screens Demo Application Checkout the detailed article in the below link, https://hemalathachockalingam002.medium.com/build-phygital-customer-experiences-using-aem-screens-part-2-hands-on-demo-891df51df8f1 

I'm trying to figure out how to migrate some custom products from 6.3 to 6.5.x and support different editing for different product types. The original products were stored under /etc/assets/project_name/product_type format. I realize that in the OOTB AEM 6.5 that this has moved to /var/commerce/products by default. There were some scaffolding dialogs created to edit each type of product.What I'm looking for is a detailed document on how to implement products in 6.5. My web searches keep coming up with whitepapers that say it can be done but I'm not finding the detail. Thanks in advance for any assistance.

Please help me with best approaches to write HTML string to PDF fileThanks in advance

Hi all, I upgrade AEM 6.2 to 6.5.0. I already updated the uber jar 6.5.0. But, OracleDriver (OracleDriver) show "Installed" status, not "Active." Saw this error below: javax.activity -- Cannot be resolvedjavax.rmi -- Cannot be resolved javax.rmi.CORBA -- Cannot be resolved May I know how to tackle this? Thanks in advance.

The purpose of this thread is to continue the conversation from the Virtual User Group on the topic of System Admin Enablement on November 16, 2021. Many thanks to everyone who joined, and special thanks to our System Admin panelists: @Monique Evans‚, @Chuck Holden‚, @Teale McCleaf‚ and @Randy Roberts‚. There aren’t any slides from the session since it was a live discussion vs. a presentation, but here is a link to the recording. Do you have any additional questions for our expert panel? There isn't much this group hasn't tackled, so leave a comment below and we’ll keep the conversation going! Thanks again. If you have any feedback (good or bad), please don’t hesitate to reach out. You can find the schedule for all upcoming User Groups on the Events page on Workfront One (one.workfront.com/events

We have recently implemented login functionality with the help of OKTA and we have utilized SAML OOTB configuration for it.  Issue: Whenever we login, it is showing "Anonymous" user instead of showing logged in user id. I can see users created on publishers but still it is not treating them actual users. Below are logs: 30.11.2021 14:17:35.153 *DEBUG* [qtp629093193-3004] org.apache.sling.auth.core.impl.SlingAuthenticator getAuthenticationInfo: no handler could extract credentials; assuming anonymous30.11.2021 14:17:35.153 *DEBUG* [qtp629093193-3004] org.apache.sling.auth.core.impl.SlingAuthenticator doHandleSecurity: No credentials in the request, anonymous30.11.2021 14:17:35.155 *DEBUG* [qtp629093193-3004] org.apache.sling.auth.core.impl.SlingAuthenticator setAttributes: ResourceResolver stored as request attribute: user=anonymous30.11.2021 14:17:45.154 *DEBUG* [qtp629093193-2991] org.apache.sling.auth.core.impl.HttpBasicAuthenticationHandler forceAuthentication: N

Join us for the next monthly Adobe Target Community Q&A Coffee Break,  taking place Wednesday, October 13th, 2021 @ 8am PT   🗓️☕Be sure to MARK YOUR CALENDARS with a link to this thread☕🗓️   We'll be joined by Gentry Lin (aka @adobe-gentry), Senior Solutions Consultant for Adobe Target, who will be signed in here to the Adobe Target Community to chat directly with you on this thread about your Adobe Target questions pertaining to her areas of expertise She : Implementation Personalization Core web authoring workflows Adobe Experience Cloud integrations   REQUIREMENTS TO PARTICIPATE  Must be signed in to the Community during the 1-hour period  Must post a Question about Adobe Target THAT'S IT!  *(think of this as the Adobe Target Community equivalent of an AMA, (“Ask Me Anything”), and bring your best speed-typing game)    INSTRUCTIONS  C

We're trying to set up SDI on pages that use authored templates on 6.3 but aren't having any luck.  We have a user widget in the header that uses dynamic data but we aren't seeing anything happen in page rendering when we flag the header component as being an SDI resource type.  We are seeing includes being properly written when we indicate a component in the authored section of a page using that template, so we know SDI is set up properly.  Is there anything that needs to be done to get the two features working together?

We are accessing and submitting an Adaptive Form from an SSL URL (https).  When it redirects to the Thank you page, it is using a non-SSL url (http). Is this a configuration issue? Thank you,Charles

Hi Guys, When I am triyng to update the content in push delivery it is not updating, actually  "save" button in not coming. I have tried in different browsers and incognito mode as will and also I have tried in different machine as well but none is working.  Any suggestion?

Author: Ankur Ahlawat Adobe Experience Manager is the recognized leader for digital experience management, and now, it's strengthening this position even further. Adobe is moving Adobe Experience Manager (AEM) to the cloud. AEM Cloud Service introduces the next generation of the AEM product line, moving away from versioned releases like AEM 6.4, AEM 6.5, etc. to version-less, fully continual releases of "AEM as a Cloud Service." Below, we'll cover: The advantages of making AEM a Cloud Service offering What changes/challenges this move to AEM as a Cloud Service brings Features Not Supported in AEM Cloud Service. The advantages of AEM as a Cloud Service AEM Cloud Service adopts all the benefits of modern cloud-based services: High availability: One of the key benefits of moving to AEM Cloud Service is the ability for all services to be always on, so that our customers never experience downtime. In the past, especially on the author side, there was a need to periodically stop the serv

Author: Erin Davis What information can I gain from reading this article? Apple changed how cookies are persisted in Safari Browsers so that some cookies expire after 7 days. Despite the change to Safari, data sets from Adobe Experience Cloud cookies are still being collected. Lookback windows and return visitor counts may be reduced for Safari traffic until an Adobe update is made available, targeting end of April to May 2019. Along with everyone in the industry, Adobe is developing both short and long-term mitigations. The details in this post can change at any time. What does not change is our commitment to our customers and consumer privacy and choice. What is ITP 2.1? On Feb. 21, 2019, Apple announced its latest update to ITP (Intelligent Tracking Prevention). Unlike previous versions focused on third party cookies, this version details new tracking prevention measures for first party cookies. In upcoming releases of iOS 12.2 and Safari 12.1 browsers, first party persistent coo

Author: Nils Meder The first time most people hear about chaos engineering their instinctive response is "Be careful," "Be safe," "Keep buffers up." But when they say that, they're missing the point. With chaos engineering, we are making our environments stronger and more useful by purposefully trying to destroy them. To ensure a working platform even under the most inconceivable circumstances, you have to move beyond planning for the "known" scenarios. We began our chaos engineering journey a few years back, starting with small experiments and tools such as Chaos Monkey, used by Netflix, Amazon, and others. With these first smaller experiments, we mostly confined our chaos to a very limited non-production environment. One where you probably already know beforehand what the consequences are. Often we'd even disconnect the system from other services, to mitigate damage. Each of those experiments produced results that were improving the system, and we grew from there. But the recent add

Author: Chetan Prasad We're pleased to announce the general availability of the Adobe Experience Platform Mobile SDK, initially released in the fall of 2018. This new major version has been re-architected from the ground up and replaces the existing 4x Mobile SDK. This new Adobe Experience Platform SDK is easily configured and managed via Adobe Experience Platform Launch, and provides a wide variety of new features in addition to the existing functionality from the 4x Mobile SDK. Watch a short clip to see how we’ve brought Adobe Experience Cloud Mobile Activation to Launch The Adobe Experience Platform SDK is available today for Android and iOS and also includes support for React Native. In addition to server-side and programmatic configuration options, the SDK also supports third-party vendor extensions, and a robust client-side rules and actions engine. The Adobe Experience Platform SDK also introduces support for new Adobe solution functionality such as mobile pus