Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
Sync External Git Repository to Cloud Manager Repository by Stories by Albin Issac on Medium Abstract In the earlier tutorial, we have discussed the basic details on Cloud Manager and how to use CM API/Events to trigger the notification to Social Channel(Teams). As discussed earlier, the Cloud Manager enables own Git repository to manage the deployment to different environments, for simple projects the Cloud Manager enabled git repository should be enough to manage the day to day development activities of the project. But for complex projects, the feature-based easy to manage repository(CM don’t provide any UI to manage the branches) should be required to manage the day to day development activities. In that case, the customer-specific repository can be used to manage the day-to-day development activities and the code can be merged to Cloud Manager Git repository branches once ready for deployment. As a manual process, the branches between the local repository and Cloud Manager repo
Hi Experts, I have created a Image profile containing smart crop config and applied it on a folder. Below are the configs for smart crop:Environment - AEM Assets CloudName *Width *Height *Desktop-XL561748Desktop-L376501Table-M1208208Mobile-S272272 After reprocessing the asset/uploading new asset on folder, the smart crop renditions are not working properly.Rendition Table-M1(208X208) looks bigger than Desktop-XL(561X748). But it should not happen in ideal case. Need you advice here what is causing this issue.
Here I am using Embed Component along with some core components(Text, Title, etc.,). But when I am trying to confugure my embed component in the page, no dialog is opening. Other all components are working fine except for Embed. Is there any way to fix this issue. ( I am using AEM Cloud) Page with Embed Component (Diaog is not opening when trying to configure Embed)-
As AEP dynamically evolves, getting used to all the terms at once can be tough. Here are few links I find useful, have you come across any other docs with the same usage? https://experienceleague.adobe.com/docs/experience-platform/landing/glossary.htmlhttps://jimalytics.com/adobe-experience-platform/adobe-experience-platform-aep-dictionary/
Author: Klaasjan Tukker In the past couple of months, I spent a significant amount of time with our technical sales and consulting organization at Adobe, to bring them up to speed on the power and capabilities of Adobe Experience Platform. Experience Platform operates two "brains" that are connected with each other. First, an analytical brain, to store and process a huge amount of analytical data, run machine-learning with Data Science Workspace, query the data with Query Service. The second brain is the Real-Time Customer Profile, which is optimized to power real-time experiences at scale. This real-time Customer Profile is at the heart of Adobe Experience Platform and has several very unique features. How do you simply explain this complex system? During the workshops, I developed a simple analogy, where I used sticky notes to explain the concept of the real-time Customer Profile. Attendees were given sticky notes and asked to write down the answers to a number of questions. Let me
Author: Brandon Poyfair Location is the most personal context for designing and delivering personalized experiences. Understanding where your users are fundamentally changes how you understand and engage with them. Experience Platform Location Service enables your mobile apps with location intelligence while maintaining privacy sensitivity for your users. You can use the Location Service to Send a real time notification when someone is near your store to drive foot traffic. Segment an audience of health conscious users based on frequency of visits to gyms and health food stores. Personalize an in-store experience. Analyze where users are most likely to use certain features. Increase engagement by limiting touch points to contextually relevant settings. Dynamic point of interest database management The point of interest (POI) database allows you to easily create and manage geofences unique to your organization. This can be done in our product interfa
Authors: Anand Phatak, Nipun Nair, Anshuman Nangia, and Dave Weinstein A summary of how we deployed a single enterprise-level message bus ("Pipeline") using Kafka for Adobe Experience Platform, from our presentation at Kafka Summit 2018 in San Francisco. Over the last decade, the expectations for data processing at scale have changed dramatically. Data collection and processing have moved from being a largely batch-oriented affair to requiring fully streaming methodologies. This change has been driven by the needs of companies to work on high-velocity data and respond to changes in customer behavior and demand in seconds, not days and hours. The aggregation, enrichment, and near-real-time analysis of high-frequency data present a whole new set of challenges. Particularly when the goal is to take data collected at any experience point, derive insights, and then deliver the next best experience at the speed customers demand, tying multiple messaging systems together is a non-starter. To
Authors: Joel Huff, James Rennie, Nishith Kota, Kevin Davis, Gowtham Ranganath, Jayant Bhushan, and Jody Arthur This blog is how Adobe Experience Platform was implemented at Adobe IT and Support organizations to help sales and support teams deliver better customer experiences as part of our "Customer Zero" program. When it comes to using enterprise data to deliver extraordinary customer experiences, 1/10th of the data often represents 10x of the complexity. This complexity is the result of customer data fragmentation caused by many different types of data from numerous data silos. Enterprises across all industries are struggling with data fragmentation as a roadblock to their ROI for deep investments in digital transformation intended to increase loyalty and retention by providing exceptional customer experiences. The data fragmentation roadblock presents two fundamental challenges that must be overcome in order to deliver indelible personalized customer experiences in real-time. The
Authors: Mandeep Gandhi, Som Satpathy, and Harry S. Adobe recently announced two new Streaming Sources and Destinations as part of its real-time customer data platform offering: Azure Event Hub and AWS Kinesis. This blog will detail the use cases, how we started, what technical decisions we took, and the challenges we faced while executing this release. Adobe Experience Platform has a large Kafka infrastructure with multiple environments and data centers. We had already built Pipeline Smarts for stream processing. It made perfect sense for us to explore Kafka Connect for our Ingress/Egress story. We got this opportunity in our Adobe Experience Platform Hack-week last December. During our Hack-Week in December 2019, we built a powerful proof of concept that included filters on attributes of data, SMTs, and how to ingress/egress. Development Common DSL We set on the quest of what would it take to get Kafka Connect production-ready. The idea was not just to build a couple of connectors a
java.lang.IllegalStateException: String is too long: 2318847350793139939 at org.apache.jackrabbit.oak.plugins.segment.Segment.loadString(Segment.java:397) at org.apache.jackrabbit.oak.plugins.segment.Segment.readString(Segment.java:364) at org.apache.jackrabbit.oak.plugins.segment.Segment.readString(Segment.java:358) at org.apache.jackrabbit.oak.plugins.segment.SegmentPropertyState.getValue(SegmentPropertyState.java:174) at org.apache.jackrabbit.oak.plugins.segment.SegmentPropertyState.getValue(SegmentPropertyState.java:165) at org.apache.jackrabbit.oak.plugins.value.ValueImpl.getValue(ValueImpl.java:381) at org.apache.jackrabbit.oak.plugins.value.ValueImpl.getOakString(ValueImpl.java:144) at org.apache.jackrabbit.oak.plugins.value.ValueImpl.getString(ValueImpl.java:287) at org.apache.jackrabbit.oak.jcr.session.PropertyImpl.getString(PropertyImpl.java:273)I believe this to be a similar question to http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-ex
Session Details Learn how to manage environment variables with AEM as a Cloud Service and use them in the context of a build process or OSGI configuration variables. Session Recording Session Schedule 9-Feb, 11:45 AM - 12:15 PM PST Speaker(s) Shankari Panchapakesan & Raul Hudea Full Schedule Check Here Q&A Please use this thread to ask the question related to this Session. Session FAQs Q. Can you use the json format and environment variables for osgi configs also in on-premise or AMS AEM's A. the variable interpolation works with any configuration serialization -- properties, json, sling:OsgiConfig nodes | there is a way to use this with the AEM as a Cloud Service SDK Q. Can I set multiple variables at once? A. yes multiple variables can be set using the CLI tool all at one time Q. Are the secrets / configs added to the store version? Or overwritten? A.
How to WhiteList IP through AEM Dispatcher ? by Anuj Gangwar Abstract The dispatcher is used as a load balancing/caching tool by AEM. It can also be used to block anyone from accessing your AEM author instance. This is to ensure that no one outside the client’s network can access it. AEM Author and publisher should never be exposed directly. In most cases, clients may also require a block to be put on AEM pub dispatchers before going live. This is to ensure that no one can see the site except for the client so performance, penetration, and UAT testing can be performed before going live. In this article, we will see, 5 easy steps to enable IP whitelisting in Apache so only the allowed list of IPs have access to AEM through the dispatcher. 1) In Apache to enable whitelisting, the Require directive is used which is provided by the mod_authz_host module. Make sure that you have the module enabled first in /dispatcher/src/conf.modules.do/00-base.conf LoadModule authz_host_module modul
Editable Template Strategy — AEM(Adobe Experience Manager) by Albinsblog Abstract Some of my last posts explained the Website Structure in AEM — Multi-Site Manager(MSM), Reusing the same template across multiple websites; in this post, let us discuss the Editable Template Strategy to support the multi-sites on the AEM platform. The below questions asked when the AEM projects adopt the Editable templates. How many editable templates are to be created? How to organize the editable template? Who manages the editable template? Can we reuse the editable templates across multiple You can have quite flexible, very rigid templates, or somewhere in between. Adobe does not recommend having more than 1000 templates due to potential performance impacts. Here are a few keynotes to consider when developing this crucial building block: The unique structure and initial content requirement Page properties — Page priorities on different page types, e.g., root page, product page, etc Policy Variation
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. Pre-requisites Ensure the following are in place before following along with this tutorial: Access to am AEM as a Cloud Service environment (preferably a Development environment or a Sandbox program) Membership in the AEM as a Cloud Service environment’s Author services AEM Administrator Product Profile Membership in, or access, to your Adobe IMS Org Administrator (they
Develop an Asset Compute metadata worker by Adobe Abstract Custom Asset Compute workers can produce XMP (XML) data that is sent back to AEM and stored as metadata on an asset. Common use cases include: Integrations with 3rd party systems, such as a PIM (Product Information Management system), where additional metadata must be retrieved and stored on the asset Integrations with Adobe services, such as Content and Commerce AI to augment asset metadata with additional machine learning attributes Deriving metadata about the asset from its binary and storing it as asset metadata in AEM as a Cloud Service In this tutorial we’ll create an Asset Compute metadata worker that derives the most commonly used colors in an image asset, and writes the names of the colors back to the asset’s metadata in AEM. While the worker itself is basic, this tutorial uses it to explore how Asset Compute workers can be used to write back metadata to assets in AEM as a Cloud Service. Logical flow of a Asset Co
Asset Compute microservices extensibility by Adobe Abstract AEM as Cloud Service’s Asset Compute microservices support the development and deployment of custom workers that are used to read, and manipulate binary data of assets stored in AEM, most commonly, to create custom asset renditions. Whereas in AEM 6.x custom AEM Workflow processes were used to read, transform, and write back asset renditions, in AEM as a Cloud Service Asset Compute workers satisfy this need. This tutorial walks through the creation of a simple Asset Compute worker that creates an asset rendition by cropping the original asset to a circle, and applies configurable contrast and brightness. While the worker itself is basic, this tutorial uses it to explore creating, developing, and deploying a custom Asset Compute worker for use with AEM as a Cloud Service. Objectives Provision and set up the necessary accounts and services to build and deploy an Asset Compute worker Create and configure an Asset Compute proj
Configuring access to AEM as a Cloud Service by Adobe Abstract AEM as a Cloud Service is the cloud-native way of leveraging the AEM applications, and as such, leverages Adobe IMS (Identity Management System) to facilitate the log in of its users, both administrators and regular users, to AEM Author service. Learn how Adobe IMS users, groups and product profiles are used in concert with AEM groups and permissions to provide fine-grained access to AEM Author service. Adobe IMS users Users requiring access to AEM Author service are managed as Adobe IMS users in Adobe’s AdminConsole. Learn about what Adobe IMS users are, and how they are accessed and managed in Admin Console. Learn about Adobe IMS users Adobe IMS user groups Users accessing AEM Author service should be organized into logical groups using Adobe IMS user groups in Adobe’s AdminConsole. Adobe IMS user groups do not provide direct permissions or access to AEM (this is the job of Adobe IMS product profiles), however, they
Debugging AEM SDK by Adobe Abstract AEM SDK’s local quickstart is the primary development environment used by developers, and supports a myriad of ways to debug AEM and deployed applications. This user guide takes, you through some of the more common debug tools and consoles for debugging your application on the AEM SDK’s local quickstart. Logs Logs act as the frontline for debugging AEM applications, but are dependent on adequate logging in the deployed AEM application. Debugging AEM SDK using logs Remote debugging Remote debugging of Java code running in AEM SDK’s local quickstart allows for the step-through of live code execution in AEM from your IDE. Remote debugging the AEM SDK OSGi web consoles The AEM SDK’s local quickstart has an OSGi web console that provides a variety of information and introspections into the local AEM runtime that are useful to understand how your application is recognized by, and functions within AEM. Debugging the AEM SDK using the OSGi web console
Adobe updates its Experience Cloud with a focus on personalization by Frederic Lardinois Abstract Experience Cloud is Adobe’s umbrella brand for its digital experience solutions. These include, among other things, its data and analytics services, content management tools, a commerce platform and, with the 2020 acquisition of Workfront, a full marketing workflow management service, too. The Experience Cloud brand made its debut at the company’s 2017 Digital Marketing Summit. This event is now the Adobe Summit — you can think of it as the Experience Cloud counterpart to the Creative Cloud-centric Adobe MAX conference — and it’s no surprise that the company is announcing a slew of new products and updates to its digital experience platform today at this year’s (virtual) conference. The focus of today’s announcements is on providing new tools to help brands — and the developers that work for them — build more personalized experiences and provide deeper integrations between the different
AEM – A Peak Into Its History by Satish k choudhary Abstract Adobe Experience Manager (AEM), is a comprehensive content management solution for building websites, mobile apps and forms. And it makes it easy to manage your marketing content and assets. A powerhouse combo for your content and digital asset management needs. Get personalized, content-led experiences into market faster with Adobe Experience Manager, which combines digital asset management with the power of a content management system. AEM – History (Day Communiqué) CQ5 was originally started by a Swiss company Day Software in early 2000 with the name “Communique”. CQ is the short form of “Communique”. Day Software was acquired by Adobe Systems on 28 July 2010 for US$240 million after Day CQ 5.3 release. AEM – Many Names – Day Communiqué WCM – Communiqué – Day Software’s CQ – Adobe CQ – Adobe WEM – Adobe WCM – Adobe Experience Manager or AEM Read Full Blog AEM – A Peak Into Its History Q&A Please use this thread
Storing JSON in a Marketo Textarea field (or String, if it’s short enough) is a cool way to add new dimensions to a Marketo person record. JSON fields are easy-to-write alternatives to Marketo Custom Objects — “poor man’s custom objects,” as I’ve called them before. They can be parsed into one-to-many lists of objects using Velocity (in emails) or JavaScript (on landing pages). But you know what? While I fully endorse JSON fields, and was the first user to popularize ’em, they’re not always the right fit. If you need a set of key-value pairs (just one new dimension, you could say, not multiple nested dimensions) consider a URL-encoded string, a.k.a. query string without the leading ? instead of JSON. Why? Well, primarily because Velocity has a built-in decoder for query strings. It doesn’t have a built-in decoder for JSON. While you can easily get VTL to parse JSON — just make sure there aren’t any nulls and use full Unic
I am trying to code a profile script that looks for some query parameters. At some point after I have split the query parameters into an array, how should i iterate over the array to find the query parameter I need. I have tried using for, forEach, while loops...all show some syntax error although the function works perfectly fine when ran on the browser console.
Is it possible to embed interactive presentations (such as Captivate or Articulate files) within a microsite created with the AEM? I have been able to easily embed links to index files in iFrames with other products. I do not see this as an option for the microsites in AEM. Right now, our sites are limited to mp4 and document files. It would be great if it easily supported a broader variety of files. Thanks in advance!
What is the best way to search and sort JCR nodes[having references to another set of nodes] based on a properties on the referenceable nodes they are referencing ?Please look at the below sample node structure Parent-node-aChild-node-a1: name - String - Test1: propertyX- Reference - uuid1Child-node-a2: name - String - Test2: propertyX- Reference - uuid2 ….. Parent-node-bChild-node-b1: title- String - TestTitle1: id - String- 123: jcr:uuid - uuid1 Child-node-b2: title- String - TestTitle2: id - String- 453: jcr:uuid - uuid2 Now I would like to search and sort child nodes under parent-node-a based on the tile property on the nodes they are reference from parent-node-b. Appreciate any guidance here.
As you already know (right?) Marketo-hosted Landing Pages can be accessed with or without a trailing .html in the path part of the URL.[1]So these URLs are aliases for the same content:https://pages.example.com/myoffer?utm_medium=emailhttps://pages.example.com/myoffer.html?utm_medium=email From a Marketo perspective, then, it’s merely a cosmetic choice. (Personalized URLs are an exception, which I’ll explain in the notes.[2])However, when you add 3rd-party trackers like the ubiquitous Google Analytics, those packages can’t know out-of-the-box that the URLs are equivalent. As far as GA knows, your webserver may well treat them differently: they are, after all, different URLs.(/myoffer.html, /myoffer.rss, /myoffer.json etc. could deliver very different content. Some web apps use resources differentiated only by their “extension” to switch content types.[3] The extension-less /myoffer would probably be an alias for one of the types, but GA couldn’t know which one.)With Market
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.