<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Varun Mitra on Medium]]></title>
        <description><![CDATA[Stories by Varun Mitra on Medium]]></description>
        <link>https://medium.com/@varun-mitra?source=rss-f71c541cd015------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0MhtyYQrjANelXnOuHL2wQ.jpeg</url>
            <title>Stories by Varun Mitra on Medium</title>
            <link>https://medium.com/@varun-mitra?source=rss-f71c541cd015------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:45:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@varun-mitra/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[AEM as Cloud Service: Working with Multiple Source GIT Repositories]]></title>
            <link>https://varun-mitra.medium.com/aem-as-cloud-service-working-with-multiple-source-git-repositories-c0647e500552?source=rss-f71c541cd015------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0647e500552</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[aemasacloudservice]]></category>
            <category><![CDATA[cloud-manager]]></category>
            <category><![CDATA[aem]]></category>
            <dc:creator><![CDATA[Varun Mitra]]></dc:creator>
            <pubDate>Mon, 15 Mar 2021 18:42:44 GMT</pubDate>
            <atom:updated>2021-03-15T18:42:44.820Z</atom:updated>
            <content:encoded><![CDATA[<p>AEM as a Cloud Services, requires customers to host their code in a GIT repository. Instead of directly working with Cloud Manager’s Git repository, customers can work with their own Git repository or multiple own Git repositories.</p><p>In this blog post, we will cover the process of merging multiple Git repositories and projects into a single Git repository. For simplicity, we will use <a href="https://github.com/adobe/aem-guides-wknd">aem-guides-wknd</a> and <a href="https://github.com/adobe/aem-guides-wknd-spa">aem-guides-wknd-spa</a> projects.</p><p>This blog post is comprised of three parts:</p><pre>| <strong>Serial</strong> |                <strong>Scenario</strong>               |  <strong>Complexity</strong> |<br>|--------|---------------------------------------|-------------|<br>|      1 |  Clone and Format WKND Project        |  Medium     |<br>|      2 |  Clone and Format WKND-Events Project |  Low        |<br>|      3 |  Merge WKND and WKND-Events Project   |  High       |</pre><h4>Pre-requisites</h4><ol><li>github.com account</li><li><a href="https://git-scm.com/downloads">git</a> command line or <a href="https://desktop.github.com/">GitHub Desktop</a></li><li>Cloud Ready Adobe Experience Manager</li><li>Apache Maven (3.3.9 or newer)</li><li>Adobe Public Maven Repository in maven settings.xml</li></ol><p><strong>Scenario 1a: Clone the WKND Project</strong></p><ol><li>Clone<a href="https://github.com/adobe/aem-guides-wknd"> WKND Sites Project</a></li></ol><pre>git clone --branch master https://github.com/adobe/aem-guides-wknd.git</pre><p>2. Set up an empty Git Repository</p><p>This GIT repository will be referred to as Origin</p><p>3. Open the Command Prompt or the Terminal Window.</p><p>4. Navigate using the command line to the local directory that contains cloned WKND Project</p><p>5. Execute the following commands, to delete the .git folder</p><ul><li>Windows: rmdir .git /S</li><li>Mac: rm -R .git</li></ul><p>6. Initialize the local repository and point it to the remote Origin GitHub</p><pre>git init</pre><pre>git add .</pre><pre>git commit -m 1_commit</pre><pre>git remote add origin &lt;http URL for the origin git&gt;</pre><pre><strong>e.g.</strong> git remote add origin <a href="https://github.com/varunmitra/aem-guides-wknd.git">https://github.com/varunmitra/aem-guides-wknd.git</a> </pre><pre>git push -f origin master</pre><p><strong>Scenario 1b: Format the WKND project</strong></p><ol><li>Navigate using command line to the local directory that contains cloned WKND Project.</li><li>Create a new directory.</li></ol><p>mkdir wknd</p><p>3. Move projects and files inside the newly created directory</p><p>git mv pom.xml all core it.tests ui.apps.structure ui.apps ui.config ui.content.sample ui.content ui.frontend ui.tests wknd</p><p>4. Resulting folder structure will look like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/656/1*hrzJwDbVtzpKCU8FUGqoSw.png" /></figure><p>5. Create a new pom.xml file.</p><p>6. Update the pom.xml file with the following <a href="https://github.com/varunmitra/aem-guides-wknd/blob/main/pom.xml">code</a>.</p><p>7. Add pom.xml to the current project by running: git add pom.xml</p><p>8. Update the pom.xml file for the dispatcher module with the following <a href="https://github.com/varunmitra/aem-guides-wknd/blob/main/dispatcher/pom.xml">code</a>.</p><p>9. Update pom.xml for the wknd module by removing &lt;module&gt;dispatcher&lt;/module&gt;</p><p>10. Test project sanity by running mvn verify</p><p>11. Commit the GIT Changes: git commit -m “moving wknd”</p><p>12. Push the latest changes to Remote Origin GitHub: git push -f origin main</p><p>13. Resulting GitHub will look something like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*KYc89oEc_bHS8t_oFUvgRA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jZPUSrb1lrP0YYzrTy_Zvw.png" /></figure><p><strong>Scenario 2a: Clone aem-guides-wknd-spa</strong></p><ol><li>Clone <a href="https://github.com/adobe/aem-guides-wknd-spa">aem-guides-wknd-spa</a>.</li></ol><p>git clone --branch React/latest <a href="https://github.com/adobe/aem-guides-wknd-spa.git">https://github.com/adobe/aem-guides-wknd-spa.git</a></p><p>2. Set up an empty Git Repository. This GIT repository will be referred to as Origin.</p><p>3. Open Command Prompt or Terminal Window.</p><p>4. Navigate using command line to the local directory that contains cloned WKND-SPA Project.</p><p>5. Execute the following commands, to delete the .git folder:</p><ul><li>Windows: <em>rmdir .git /S</em></li><li>Mac: <em>rm -R .git</em></li></ul><p>6. Initialize the local repository and point it to remote Origin GitHub</p><pre>git init</pre><pre>git add .</pre><pre>git commit</pre><pre>git branch -M main</pre><pre>git remote add origin &lt;http URL for the origin git&gt;</pre><pre><strong>e.g.</strong> git remote add origin <a href="https://github.com/varunmitra/aem-guides-wknd-spa.git">https://github.com/varunmitra/aem-guides-wknd-spa.git</a></pre><pre>git push -u origin main</pre><p><strong>Scenario 2b: Format WKND-SPA project</strong></p><ol><li>Navigate using command line to the local directory that contains cloned WKND Project</li><li>Create a new directory: mkdir wknd-spa</li><li>Move projects and files inside the newly created directory: git mv pom.xml all core it.tests ui.apps ui.apps.structure ui.content ui.frontend wknd-spa</li><li>Move the dispatcher folder to a new location for safe keeping. Since, you can only have one dispatcher configuration per project as such we will have to manually merge these with the dispatcher configuration under <strong>wknd</strong> project.</li><li>Create a new pom.xml file.</li><li>Update pom.xml with the following <a href="https://github.com/varunmitra/aem-guides-wknd-spa/blob/main/pom.xml">code</a>.</li><li>Add pom.xml to the current project: git add pom.xml</li><li>Test project sanity by running mvn verify</li><li>Commit the git changes: git commit -m “moving wknd-spa”</li><li>Resulting GitHub will look something like:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/1*kqN0iZxpwNkgtHSE45cWRA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*krHrCFEO9jbiMvD3GfWOPA.png" /></figure><p><strong>Scenario 3: Merge the WKND and WKND SPA project</strong></p><blockquote><em>Description</em></blockquote><p>In this section we will merge the WKND and WKND-SPA Project. In order to achieve this we will follow the given steps:</p><ol><li>Add WKND-SPA GitHub as a remote repository for WKND. This will allow us to fetch the content of WKND-SPA Project and add it as a branch of WKND.</li><li>Fetch WKND-SPA Project.</li><li>Switch the branch pointer to WKND-SPA/Main branch.</li><li>Verify the project contents.</li><li>Switch the branch pointer back to the WKND Main branch.</li><li>Perform a branch merge using — allow-unrelated-histories flag.</li><li>Fix the Merge errors. Most importantly, modify the pom.xml to point to both wknd and wknd-spa projects.</li><li>Merge and consolidate dispatcher configurations. Ensure to run <a href="https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/content-delivery/disp-overview.html?lang=en#test-your-configuration-with-a-local-deployment-(requires-docker-installation)">dispatcher validator</a> before committing any changes</li><li>Commit the changes.</li><li>Verify the project using mvn verify or mvn clean install</li><li>Push the consolidated project to Cloud Manager GitHub.</li></ol><blockquote><em>Exact Steps and Git Commands are as below:</em></blockquote><ol><li>Navigate using command line to the WKND project</li><li>Run the following commands:</li></ol><pre>git checkout main</pre><pre>git remote add wknd-spa &lt;path to cloned WKND-Events Git repository&gt;<br><strong>e.g.</strong> git remote add wknd-spa <a href="https://github.com/varunmitra/aem-guides-wknd-spa.git">https://github.com/varunmitra/aem-guides-wknd-spa.git</a></pre><pre>git fetch wknd-spa</pre><pre>git checkout -b wknd-spa wknd-spa/main</pre><pre>git checkout main</pre><pre>git merge wknd-spa --allow-unrelated-histories</pre><p>3. Fix the Merge errors. pom.xml should look something like:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f8a5190e58656131fb6dcbb996a6077f/href">https://medium.com/media/f8a5190e58656131fb6dcbb996a6077f/href</a></iframe><p>4. Verify the directory structure, it should look something like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*QBilWZp2qbuidyxI45SZyQ.png" /></figure><p>5. Run mvn verify</p><p>6. Commit final changes to the git: git commit -am “updating parent pom”</p><p>7. Add cloud manager GitHub: git remote add cm_repo &lt;path to cloud manager git repository&gt;</p><p>8. Push to Cloud Manager GitHub: git push -u cm_repo main:merge</p><p>Resources:</p><p>Accessing Cloud GIT Repository: <a href="https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/using/managing-code/setup-cloud-manager-git-integration.html?lang=en#git-integration-overview">https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/using/managing-code/setup-cloud-manager-git-integration.html?lang=en#git-integration-overview</a></p><p>Managing Source Code: <a href="https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/using/requirements/source-code-repository.html?lang=en#requirements">https://experienceleague.adobe.com/docs/experience-manager-cloud-manager/using/requirements/source-code-repository.html?lang=en#requirements</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0647e500552" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adobe Experience Manager Integration with Adobe Analytics]]></title>
            <link>https://medium.com/adobetech/adobe-experience-manager-integration-with-adobe-analytics-fefdc6d1a6f5?source=rss-f71c541cd015------2</link>
            <guid isPermaLink="false">https://medium.com/p/fefdc6d1a6f5</guid>
            <category><![CDATA[adobe-products]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[adobe-launch]]></category>
            <dc:creator><![CDATA[Varun Mitra]]></dc:creator>
            <pubDate>Fri, 17 May 2019 14:31:00 GMT</pubDate>
            <atom:updated>2019-06-05T16:32:53.367Z</atom:updated>
            <content:encoded><![CDATA[<p>In this blog post, we’re going to explore the Adobe Analytics integration with Adobe Experience Manager. For this integration, we’re going to leverage the Adobe Launch core service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jAiVWAEjt-e2Go6LC1Jw6w.jpeg" /><figcaption>Adobe Experience Cloud Architecture</figcaption></figure><h4>Introduction to Analytics variables</h4><ul><li><strong>TRAFFIC VARIABLES (PROPS / S.PROPS): </strong>Traffic variables count the number of times each value is sent to Analytics. Example: When a visitor opens are page , a prop can be used to increment the existing count.</li><li><strong>EVENTS: </strong>Events are completed visitor actions on your website. Examples of custom events might be login, registration, and signup.</li><li><strong>CONVERSION VARIABLES ( EVARS) </strong>are used to identify how well specific attributes or actions contribute to success events on your site. Example: When a visitor clicks on the internal promotion, an eVar can be used to store a unique identifier for that promotion.</li></ul><p><strong>Prerequisite:</strong></p><p><a href="https://medium.com/adobetech/integrate-adobe-launch-with-adobe-experience-manager-ffc3670e6f4e">AEM Integration with Adobe Launch</a></p><h3>Integrate Adobe Analytics with Adobe Launch</h3><p>===================================</p><p><strong>Add Adobe Analytics Extension to Adobe Launch</strong></p><ol><li>Log in to Adobe Experience Cloud</li><li>Navigate to Adobe Launch</li><li>Select the Adobe Launch property</li><li>Navigate to Extensions tab and select Catalog</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n28Co0Y6nD8y4ceGAf4MNQ.png" /></figure><p>5. Search for Adobe Analytics</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6TXbZzLVqavJwIq6dEXvKA.png" /></figure><p>6. Click Install</p><p>7. Configure</p><ul><li>Development Report Suite</li><li>Staging Report Suite</li><li>Production Report Suite</li><li>Character Set as UTF-8</li></ul><p>8. Save</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pH4Wqg5NVU_wcLlYd9qCgw.gif" /></figure><p>========================================</p><h4>Create data elements</h4><ol><li>Click on Data Elements</li><li>Click Add Data Element</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZvM84suX1CjfGYwFNByUxQ.png" /></figure><p>3. Define a Data Element to capture Page Name and Page URL:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/802a8c8f1e8196074f5248f535d2eb68/href">https://medium.com/media/802a8c8f1e8196074f5248f535d2eb68/href</a></iframe><p>========================================</p><h4>Create rules</h4><ol><li>Goto Rule</li><li>Click Add Rule</li><li>Specify Name</li><li>Goto If and add an Event</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KPjDcHRpkX1P9oeJmFAsIQ.png" /></figure><p>5. Set the Extension to Core</p><p>6. Set Event Type to Page Bottom</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4jf2DiEAlAz33Z4KKUIu2w.png" /></figure><p>7. Click Keep Changes.</p><p>8. Goto Actions and Click Add</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SG4Cs1mUUrkbH8BufzG41w.png" /></figure><p>9. Set Extension to Adobe Analytics</p><p>10. Set Action Type to Set Variables</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k3a-hTVxcpGZ2cavHyOi4A.png" /></figure><p>11. Map Analytics Variables to Data Elements</p><p>12. Set prop1 as page_name</p><p>13. Set prop2 as page_url</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*iRK1FHMqRU498LOoZvsk7g.gif" /></figure><p>14. Click Keep Changes.</p><p>15. Add another action to send Analytics Beacon</p><p>16. Set Extension to Adobe Analytics.</p><p>17. Set Action Type to Send Beacon</p><p>18. Set Tracking to s.t(): Send Data to Adobe Analytics and treat it as a page view</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*VNDhs6z0raHf7skpgXsGTQ.gif" /></figure><p>19. Click Keep Changes</p><p>20. Click Save to save the Load Analytics Rule</p><p>========================================</p><h4><strong>Publish Adobe Analytics extension, page name and page URL data elements, and load analytics rule</strong></h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FpFVSCP1kqAURX8avIC%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FpFVSCP1kqAURX8avIC%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FpFVSCP1kqAURX8avIC%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/de5d4077054b64374bd5e3897ef6522b/href">https://medium.com/media/de5d4077054b64374bd5e3897ef6522b/href</a></iframe><p>========================================</p><h4>Verification</h4><ol><li>Navigate to an AEM Sites WebPage</li><li>Select the View as Published option</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z9Rim13gf_w3D1awTmvf2g.png" /></figure><p>3. Open the Chrome Developer Tools and navigate to the Network Tab</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jnhHoiF_TrVsIj6hZBMWSw.png" /></figure><p>4. Refresh the Page</p><p>5. Use b/ss to filter requests in the network tab</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DXFSkwo9qn_ZTTZJdV45EQ.png" /></figure><p>6. Verify the Analytics Server Call</p><p>7. Use <a href="https://chrome.google.com/webstore/detail/adobe-experience-cloud-de/ocdmogmohccmeicdhlhhgepeaijenapj">Adobe Experience Cloud Debugger</a> to verify the Page Data been send to Adobe Analytics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B3GMssvLW8K1C3jCbkcQAQ.png" /></figure><p>8. Check the status of prop1 and prop2</p><p>9. Navigate to Adobe Analytics</p><p>10. Goto Reports &gt; Custom Traffic &gt; Custom Traffic 1–10 &gt; Custom Insight 1</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fdmw_NOMgq8GZma4piq4kg.png" /></figure><p>11. Custom Insight 1Report displays the data captured by prop1 and Custom Insight 2 Report isplays the data captured by prop2</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BcGPbcqyFiKP_3JqWbCUkQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mlXaHM78n17NJU3UQEz_Tw.png" /></figure><h4>Way beyond vanity metrics</h4><p>Adobe Analytics has evolved beyond simple metrics to use machine learning, artificial intelligence, and other modern data analysis to become the industry’s leading web analytics technology — delivering more accurate customer insights, faster.</p><p>With Adobe Analytics, huge amounts of data get organized, cleaned, and prepared at lightning speed with the help of Adobe Sensei. You get powerful segmentation and easy-to-read visuals of your website data. And you have ability to easily curate all of this so anyone in the company can find their own insights, freeing you up to do the deep data science you were hired to.</p><p><em>Follow the </em><a href="http://medium.com/adobetech"><em>Adobe Tech Blog</em></a><em> for more developer stories and resources, and check out </em><a href="http://twitter.com/adobedevs"><em>Adobe Developers on Twitter</em></a><em> for the latest news and developer products.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fefdc6d1a6f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adobetech/adobe-experience-manager-integration-with-adobe-analytics-fefdc6d1a6f5">Adobe Experience Manager Integration with Adobe Analytics</a> was originally published in <a href="https://medium.com/adobetech">Adobe Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integrate Adobe Experience Manager with Adobe Target]]></title>
            <link>https://medium.com/adobetech/integrate-adobe-experience-manager-with-adobe-target-40fb935bb983?source=rss-f71c541cd015------2</link>
            <guid isPermaLink="false">https://medium.com/p/40fb935bb983</guid>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[adobe-target]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[adobe-launch]]></category>
            <category><![CDATA[adobe-products]]></category>
            <dc:creator><![CDATA[Varun Mitra]]></dc:creator>
            <pubDate>Mon, 21 Jan 2019 15:16:00 GMT</pubDate>
            <atom:updated>2019-01-22T15:20:52.499Z</atom:updated>
            <content:encoded><![CDATA[<p>Adobe Target is a personalization solution that makes it easy to identify and deliver your best content. Adobe Target helps you create a targeted experience specific to each customer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LQ7zKTViAXTVfgn921dgZQ.png" /><figcaption>Capabilities of Adobe Target</figcaption></figure><p>Adobe Target is built on the solid foundation of Adobe Experience Cloud and integrates directly with Adobe core services including Adobe Launch, Adobe Experience Cloud Assets and the Adobe Experience Cloud People core services. These different core services provide for information interchange between Adobe Experience Cloud solutions.</p><p>In this blog post, we’re going to explore the Adobe Target integration with Adobe Experience Manager. For this integration, we’re going to leverage the Adobe Launch core service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a8lLnSVF1Qpmv4rDgMD1MQ.png" /></figure><p><strong>Prerequisite</strong></p><p><a href="https://medium.com/adobetech/integrate-adobe-launch-with-adobe-experience-manager-ffc3670e6f4e">AEM Integration with Adobe Launch</a></p><h3><strong>Integrate Adobe Target with Adobe Launch</strong></h3><ol><li>Log in to Adobe Experience Cloud</li><li>Navigate to Adobe Launch</li><li>Select the Adobe Launch property</li><li>Navigate to Extensions tab</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6QKjvykHutscTx1NsRGHJg.jpeg" /></figure><p>5. Select Adobe Target extension and click “Install”</p><p>6. Verify the environment details and click “Save”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0QVU5PM9DBNSQYf1QWpJ3Q.jpeg" /></figure><p>7. Click on the “Rules” tab</p><p>8. Click on the “Create New Rule” button</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SrMWAZrLranaL1pOtg4C7w.jpeg" /></figure><p>9. Specify the rule name</p><p>10. Set “Event Configuration” as:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3e7ccc88cd579e54ede9f29e61b84e94/href">https://medium.com/media/3e7ccc88cd579e54ede9f29e61b84e94/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BO87pEppJoT-dXWH68UL5g.jpeg" /><figcaption>Adobe Target Library is loaded at Page Top</figcaption></figure><p>11. Set the Actions, in the following order, as:</p><p><strong>Action 1:</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5f8a063e1175f9fe0dece04950ea4c1e/href">https://medium.com/media/5f8a063e1175f9fe0dece04950ea4c1e/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IgNzLHJzkso723Wf6MQV5w.jpeg" /></figure><p><strong>Action 2:</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a07f554c842e521f8f4b0048da3687cd/href">https://medium.com/media/a07f554c842e521f8f4b0048da3687cd/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H81D_eLLarE2uplr0pL-TA.jpeg" /><figcaption>Add Data Elements, if any.</figcaption></figure><p><strong>Action 3:</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ad1a598fdd8b410d709dd9b5f33b043e/href">https://medium.com/media/ad1a598fdd8b410d709dd9b5f33b043e/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lyZeHjCDBKrc4VUOCFHr1g.jpeg" /></figure><p>12. The rule definition should look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*phmZCQi-W2xKM178g-M_uw.jpeg" /><figcaption>Actions should be called in the above order.</figcaption></figure><p>13. Click on the “Publishing” tab and publish the newly created rule and the Target extension</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FpFVSCP1kqAURX8avIC%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FpFVSCP1kqAURX8avIC%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FpFVSCP1kqAURX8avIC%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/de5d4077054b64374bd5e3897ef6522b/href">https://medium.com/media/de5d4077054b64374bd5e3897ef6522b/href</a></iframe><h3><strong>Integrate AEM with Adobe Target</strong></h3><ol><li>Go to We.Retail site and open one of the pages</li><li>Select “View as Published”</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/1*M5UgH_FI2bP9A5DyeLfMQA.png" /></figure><p>4. Open the Browser Developer Tools</p><p>5. In the “Network” tab look for mbox</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FUwX1avFlenuE-KI9clSpg.jpeg" /></figure><p>6. AEM integration with Adobe Target is now in place.</p><h3><strong>Create Adobe Target activity</strong></h3><ol><li>Navigate to Adobe Target using the solution switcher</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*raCZoIMIlcZa95AXl5bJYQ.gif" /></figure><p>2. Click on “Create Activity” button and select “Experience Targeting”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aLmpbUDhLgRyNW2fPPuGYw.jpeg" /></figure><p>3. In the Activity URL provide the URL pointing to the We.Retail page (make sure to remove the editor.html or cf# from the page URL)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e204jf_L-sPDmbUtLneErQ.jpeg" /></figure><p>4. Click on “Next”</p><p>5. Click on “Load Unsafe Script” button</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mrj7tDzSrBRoOlvCASJmRA.gif" /></figure><p>6. You can now edit the We.Retail site content in Adobe Target</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KU_rxy-NTXuehKjXE4j7NA.gif" /></figure><p>7. Make sure to activate the activity</p><p>8. Go back to the AEM We.Retail site page</p><p>9. Verify if the changes done in Adobe Target viewport are now applied</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rM4qdWfYN1mqQj-o-d2OGg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40fb935bb983" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adobetech/integrate-adobe-experience-manager-with-adobe-target-40fb935bb983">Integrate Adobe Experience Manager with Adobe Target</a> was originally published in <a href="https://medium.com/adobetech">Adobe Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integrating Adobe Launch with Adobe Experience Manager]]></title>
            <link>https://medium.com/adobetech/integrate-adobe-launch-with-adobe-experience-manager-ffc3670e6f4e?source=rss-f71c541cd015------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffc3670e6f4e</guid>
            <category><![CDATA[adobe-launch]]></category>
            <category><![CDATA[adobe-products]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Varun Mitra]]></dc:creator>
            <pubDate>Tue, 27 Nov 2018 18:27:04 GMT</pubDate>
            <atom:updated>2019-04-15T14:50:18.532Z</atom:updated>
            <content:encoded><![CDATA[<h3>Integrate Adobe Launch with Adobe Experience Manager</h3><p>Adobe Launch is an Adobe Experience Cloud core service and allows marketers to manage Adobe and third-party tags for tracking or other analytics purposes.</p><p>Adobe Launch provides a standard way to retrieve and use data, some of which comes from the back end. Adobe Launch has the ability to customize and respond to triggers that allow us to create action based on what visitors do. Because of the aforementioned capabilities, Adobe Launch is the perfect solution for managing first-party and third-party tags and extensions in one place.</p><p>Integrating Adobe Experience Manager with Adobe Launch allows you to manage all of your integration in one place. Adobe Launch acts as the centerpiece of your Adobe Experience Cloud implementation, providing access to Adobe Target, Adobe Analytics, Audience Manager, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LT10gX3y45lk4L1Yfeh-Tg.jpeg" /><figcaption>AEM and Adobe Launch Integration</figcaption></figure><p>In this blog, we are going to explore the Adobe Launch integration with Adobe Experience Manager.</p><p><strong>Configure Adobe Launch</strong></p><ol><li>Login to the Adobe Experience Cloud and navigate to Adobe Launch.</li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fnwy0jyzT1zl9Otvdmg%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fnwy0jyzT1zl9Otvdmg%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fnwy0jyzT1zl9Otvdmg%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/a4fcb4c5e35122e54a2966d4e6be61d0/href">https://medium.com/media/a4fcb4c5e35122e54a2966d4e6be61d0/href</a></iframe><p>2. Create a new property. A <strong>Property</strong> is a collection of rules, data elements, configured extensions, environments, and libraries. In Launch, you can create multiple web properties per company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/577/1*NPdINVThAfVFjaRiXAXK0Q.png" /></figure><p>3. Save.</p><p>4. Click on the newly created property.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lPuySyIfSUWLZPe-kpR5JQ.png" /></figure><p>5. Click on the “Adapters” tab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*09Q5oXWMJwMPlUvUOBFF9w.png" /><figcaption>Default configuration is <strong>Managed by Adobe</strong>. This configuration make use of Akamai to host and deliver the Launch libraries.</figcaption></figure><p>6. Click on the “Environments” tab.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FXKGogEPVTdZxA5fPbu%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FXKGogEPVTdZxA5fPbu%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FXKGogEPVTdZxA5fPbu%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/5921b8041966e80d00218bc8f9b64524/href">https://medium.com/media/5921b8041966e80d00218bc8f9b64524/href</a></iframe><p>6. Click on the “Install” button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*xZvEWqeu0PDXcxEL9OGIBA.png" /><figcaption>&lt;script/&gt; tag can be embedded in the &lt;head&gt; tag to integrate directly with Adobe Launch</figcaption></figure><p>7. Click on the “Data Elements” tab.</p><p>8. Create a new Data Element with the following definition:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a65a17412ea469534ca5a8861c48bb1a/href">https://medium.com/media/a65a17412ea469534ca5a8861c48bb1a/href</a></iframe><p>9. Click on the “Extensions” tab and verify the Core Extension.</p><p>10. Click on the “Publishing” tab and publish the newly created Property and the Core Extension.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FpFVSCP1kqAURX8avIC%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FpFVSCP1kqAURX8avIC%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FpFVSCP1kqAURX8avIC%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/de5d4077054b64374bd5e3897ef6522b/href">https://medium.com/media/de5d4077054b64374bd5e3897ef6522b/href</a></iframe><p><strong>Set up Adobe IMS Service with Adobe Experience Manager</strong></p><ol><li>Navigate to <a href="https://console.adobe.io/integrations">https://console.adobe.io/integrations</a></li><li>Click on “New Integration”</li><li>Select “Access an API”</li><li>Select “Experience Platform Launch API” and click “Continue”</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hRbwNorEkhRZplpMEllTXw.png" /></figure><p>5. Select “New Integration” and click “Continue”</p><p>6. Provide a Name and Description for your integration</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LTuFR_bGW5qmbtI52-HCrA.png" /></figure><p>7. Navigate to your AEM Author Server</p><p>8. Go to Tools &gt; Security &gt; Adobe IMS Configuration</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vlHXGPv0uLUzpHGDmhkUkQ.png" /></figure><p>9. Click on “Create.”</p><p>10. Select Adobe Launch</p><p>11. Check the “Create New Certificate” checkbox</p><p>12. Specify an alias and click on “Create Certificate”</p><p>13. Download the Public Key</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FfHu3bCqB1kzn87aHMX%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FfHu3bCqB1kzn87aHMX%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FfHu3bCqB1kzn87aHMX%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/94939a4126bf1c22fa7b90d8dc017888/href">https://medium.com/media/94939a4126bf1c22fa7b90d8dc017888/href</a></iframe><p>14. Go back to Adobe IO Console and upload the Public Key Certificate.</p><p>15. Select an appropriate role and click on “Create Integration”</p><p>16. Click on “Continue to Integration Details”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3zJSMqk5NvV6PDOmm31_wQ.png" /></figure><p>17. Navigate back to AEM Author and click the “Next” button</p><p>18. Specify a Title</p><p>19. Copy the API Key and Client Secret from Adobe I/O console and paste it in the IMS Configuration</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FfdRRj5xkOBb5KrBwws%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FfdRRj5xkOBb5KrBwws%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FfdRRj5xkOBb5KrBwws%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/657fdc38715d3636705c2daf5010ce55/href">https://medium.com/media/657fdc38715d3636705c2daf5010ce55/href</a></iframe><p>20. Go to the JWT Tab in Adobe I/O console and copy the entire JWT Payload and paste it in the Payload text area field of IMS configuration</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F456Y6z6Y9h93gLlPaS%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F456Y6z6Y9h93gLlPaS%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F456Y6z6Y9h93gLlPaS%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/9a75e54ff4af205813b49d7e7d6c8a57/href">https://medium.com/media/9a75e54ff4af205813b49d7e7d6c8a57/href</a></iframe><p>21. Authorization server can be retrieved from the JWT payload. It looks something like <a href="https://ims-na1.adobelogin.com/">https://ims-na1.adobelogin.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0cDgy3JL8MkqqGC_dndxew.png" /></figure><p>22. Click on “Create.”</p><p>23. To test, select the newly created configuration and click on “Check Health”</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F5t05KLNaCM3OpjQZ7K%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F5t05KLNaCM3OpjQZ7K%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F5t05KLNaCM3OpjQZ7K%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/ce4d522fcb49fb94233ef9fc991da1cd/href">https://medium.com/media/ce4d522fcb49fb94233ef9fc991da1cd/href</a></iframe><p><strong>Integrate AEM with Adobe Launch</strong></p><ol><li>On AEM Author, go to Tools &gt; Cloud Services and Select Adobe Launch Configurations</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dz9LlP8Rw8rC7ZG0liqCKg.png" /></figure><p>2. Select We.Retail and click on “Create”</p><p>3. Specify a Title</p><p>4. Select the IMS Configuration from the drop down</p><p>5. Select the Experience Cloud Organization</p><p>6. Select your Adobe Launch Property</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*dK3pD_8_GS7oNKUjHwo24w.png" /></figure><p>7. Click on “Next”</p><p>8. Verify the Staging URI, it should match the Library URI specified in Adobe Launch</p><p>9. Click on “Next”</p><p>10. Click on “Create”</p><p>11. Adobe Launch Integration is now in place.</p><p><strong>Verifying the integration</strong></p><ol><li>Go to any We Retail page</li><li>Select “View as Published”</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/775/1*9pPv1pjHkgPrbeqfGeyCJA.png" /></figure><p>3. Open the Browser Developer Tools</p><p>4. In the “Network” tab look for Launch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OsqhksNWVwdM-0MbyOF-5Q.png" /><figcaption>launch library</figcaption></figure><p>5. Go to the “Console” tab and run</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/33d49b7fcdbb2f7e3fea6f926d9954c9/href">https://medium.com/media/33d49b7fcdbb2f7e3fea6f926d9954c9/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1011/1*ObPLKyB5FKSaQ9RLkJ19AQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffc3670e6f4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adobetech/integrate-adobe-launch-with-adobe-experience-manager-ffc3670e6f4e">Integrating Adobe Launch with Adobe Experience Manager</a> was originally published in <a href="https://medium.com/adobetech">Adobe Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using the OSGi Declarative Service in AEM 6.4]]></title>
            <link>https://medium.com/adobetech/using-the-osgi-declarative-service-in-aem-6-4-21102f649d54?source=rss-f71c541cd015------2</link>
            <guid isPermaLink="false">https://medium.com/p/21102f649d54</guid>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[adobe-products]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[osgi]]></category>
            <dc:creator><![CDATA[Varun Mitra]]></dc:creator>
            <pubDate>Fri, 23 Nov 2018 13:26:01 GMT</pubDate>
            <atom:updated>2018-11-23T13:26:01.530Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Understand a few project changes you might have to make in order to use these new annotations.</em></p><p>With the release of Adobe Experience Manager (AEM) 6.2, greater support for official OSGi Declarative Services was introduced. It’s worthwhile to consider OSGi Declarative Services implementation for your project, not just because AEM as a product is headed in that direction, but also because migration from SCR annotations is easy, and older SCR annotations are supported alongside the new ones. OSGi Declarative Services implementation will provide access to future updates and enhancements as well.</p><p>Here are the key project changes that you might have to incorporate in order to use these new annotations:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8j6wY9EiLk9SJv4Mfz2TkQ.png" /></figure><h3><strong>Service annotation</strong></h3><p>One of the major differences between SCR annotations and OSGI Declarative Services is in the way service references are defined.</p><p>Using SCR annotations, you can easily define a service by using the <em>@service </em>annotation.</p><p>OSGI Declarative Services require you to define a service reference as an attribute of the component annotation. As such, the equivalent code looks like this:</p><p><em>@Component(service = Servlet.class)</em></p><p>This also brings about a major change in the way Sling Servlets are defined using Declarative Services.</p><p>The older way of defining Sling Servlet that used to look something like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0db8006a392ded108b69071901cc3f04/href">https://medium.com/media/0db8006a392ded108b69071901cc3f04/href</a></iframe><p>will now look more like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/064efe56d3693eeee565bb14ea7ed4c1/href">https://medium.com/media/064efe56d3693eeee565bb14ea7ed4c1/href</a></iframe><h3><strong>Service references property</strong></h3><p>Another important change is in the way service reference properties are now defined. In SCR Annotations, to define a service reference property, you might have used code that looked like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/af1e28da03cbe7b7856d93fed673a685/href">https://medium.com/media/af1e28da03cbe7b7856d93fed673a685/href</a></iframe><p>Here <a href="http://twitter.com/Component"><em>@Component</em></a><em>(immediate = true, metatype = true, label = “Training Cleanup Service”) </em>is used to define a<em> </em>Webconsole Configuration called as “Training Cleanup Service.”</p><p>This configuration contain two properties: <em>scheduler.expression </em>and<em> cleanupPath, </em>both of which are defined using the <em>@properties </em>annotation.</p><p>Using the OSGI Declarative Service, the equivalent code would look something like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd609c9d285c9f833deba7c663839b79/href">https://medium.com/media/dd609c9d285c9f833deba7c663839b79/href</a></iframe><p>Here the properties are defined with the help of an inner interface called as <em>Config, </em>which contains all the properties that need to defined within the web console configuration.</p><p>Properties are defined with the help of different JAVA variables, and the underscore(_) in the variable names are automatically converted into dots(.) (e.g., scheduler_expression would be mapped to scheduler.expression).</p><p>Similarly, variable names are preceded by @AttributeDefinition, which allows you to define the label and description for your properties.</p><p>@ObjectClassDefinition specifies that the upcoming inner interface contains the OSGI property definition,<em> </em>and<em> </em>@Designate is used to map the inner interface to the object class definition.</p><p><strong>References</strong></p><p>Code base: <a href="https://github.com/varunmitra/aem-enablement/tree/master/AEM6.4%20Declarative%20Services/trainingproject">https://github.com/varunmitra/aem-enablement/tree/master/AEM6.4%20Declarative%20Services/trainingproject</a></p><p>Further reading and honorable mention: <a href="http://www.nateyolles.com/blog/2017/05/osgi-declarative-services-annotations-in-aem">http://www.nateyolles.com/blog/2017/05/osgi-declarative-services-annotations-in-aem</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21102f649d54" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adobetech/using-the-osgi-declarative-service-in-aem-6-4-21102f649d54">Using the OSGi Declarative Service in AEM 6.4</a> was originally published in <a href="https://medium.com/adobetech">Adobe Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using AEM Experience Fragments with Adobe Target]]></title>
            <link>https://medium.com/adobetech/experience-fragments-and-adobe-target-d8d74381b9b2?source=rss-f71c541cd015------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8d74381b9b2</guid>
            <category><![CDATA[adobe-products]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[adobe-target]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <dc:creator><![CDATA[Varun Mitra]]></dc:creator>
            <pubDate>Sat, 17 Nov 2018 00:02:14 GMT</pubDate>
            <atom:updated>2018-11-17T00:03:06.616Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Use the new Experience Fragments feature to reuse a complete set of content for targeted experiences across channels.</em></p><p><a href="https://helpx.adobe.com/experience-manager/kt/sites/using/experience-fragments-feature-video-use.html">Experience Fragments</a>, introduced with Adobe Experience Manager (AEM) 6.3, provide an excellent feature set to author content in a channel-neutral way. An experience fragment is a set of content that, when grouped, forms an experience that should make sense on its own.</p><p>Experience Fragments can be utilized across several channels and tools including your website, Facebook, Pinterest, Adobe Campaign, and Adobe Target. Experience Fragment integration with Adobe Target is particularly interesting as it allows you to leverage AEM Content and use it for creating offers in Adobe Target. These offers can then be used to insert or replace content within different activities. In this blog post we will go over the steps to export AEM Experience Fragments to Adobe Target.</p><p><strong>Prerequisites</strong></p><ol><li>AEM 6.4 Author</li><li>AEM 6.4 Publish</li><li><a href="https://ngrok.com/download">ngrok</a>: allows you to externalize your local instance and makes it available globally with the help of an external URL. ngrok is free to download from <a href="http://ngrok.com/">ngrok.com</a>.</li><li>Target Classic or Target API User Credentials (Contact: <a href="/service/mailto:customercare@adobe.com">customercare@adobe.com</a>)</li><li>Experience Fragment flag enabled on the Adobe Experience Cloud</li></ol><p><strong>Steps</strong></p><ol><li><strong>Start up the Author and Publish instance. </strong>For this exercise, we are assuming that the Author server is running on port 4502 and Publish server is running on port 4503.</li><li><strong>Start up ngrok for the Publish server.</strong> (You would need to navigate to the ngrok folder before running the command.) The command to start up ngrok is:</li></ol><p><strong>For Mac:</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f688e40e20b0ab7b417b997169e1db61/href">https://medium.com/media/f688e40e20b0ab7b417b997169e1db61/href</a></iframe><p><strong>For Windows:</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e96484d807f4f963165706f21cf91ef6/href">https://medium.com/media/e96484d807f4f963165706f21cf91ef6/href</a></iframe><p>3. <strong>Copy the forwarding URL and use it to update the Publish tag </strong>in the AEM Link Externalizer Configuration:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9yHr66q3OH_YMc1CJrtZXg.png" /></figure><p>4. Head over to <a href="http://localhost:4502/libs/cq/core/content/tools/cloudservices.html">cloud services</a> and <strong>create a new Target configuration</strong>, then specify the client code, email, and password to connect to Adobe Target.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vLEWx9CfxStoANaXLFPMcg.png" /></figure><p>5. <strong>Go to the Experience Fragments Console</strong>, create a new Experience Fragment, and add it to the Target configuration.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F1UPR99JmiXgrTzB5wf%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2F1UPR99JmiXgrTzB5wf&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F1UPR99JmiXgrTzB5wf%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/e13af032be049c62a0f567065ee10e88/href">https://medium.com/media/e13af032be049c62a0f567065ee10e88/href</a></iframe><p>6.<strong> Edit the Experience Fragment.</strong> Make sure to add text and images.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8hA9OyyA_10slNwyinl8ZA.png" /></figure><p>7. <strong>Publish the Experience Fragment</strong> to the Publish Server.</p><p>8. <strong>Export the Experience Fragment </strong>to Adobe Target.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F1BcfToNSpjSpQwMrgG%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2F1BcfToNSpjSpQwMrgG&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F1BcfToNSpjSpQwMrgG%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/3f2c9ef222c316d0ca8bd88db26f879c/href">https://medium.com/media/3f2c9ef222c316d0ca8bd88db26f879c/href</a></iframe><p>9. <strong>Log onto Adobe Experience Cloud</strong> and navigate to Adobe Target.</p><p>10. <strong>Click on the Offers tab</strong> and look for the Experience Fragment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bShNIZtgyHNViU6sFf1NXA.png" /><figcaption>Training Experience Fragment</figcaption></figure><p>11. Navigate back to Activities tab.</p><p>12. <strong>Create a new Activity.</strong> You should be able to insert the Experience Fragment here.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3Z1a1KCPXFMnugVFFV%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2F3Z1a1KCPXFMnugVFFV&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3Z1a1KCPXFMnugVFFV%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/e4f2b4c01042119be059345c1d786b9e/href">https://medium.com/media/e4f2b4c01042119be059345c1d786b9e/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8d74381b9b2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adobetech/experience-fragments-and-adobe-target-d8d74381b9b2">Using AEM Experience Fragments with Adobe Target</a> was originally published in <a href="https://medium.com/adobetech">Adobe Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>