Sap aem int day 2 (#276)

* Initial version of SAP AEM Integration - day 2 * Initial version of SAP AEM Integration - day 2 * Update sap-aem-int-day-2.md * updated codelabs folder * Add files via upload * Add files via upload * Updated Day-2 codelab with final changes * Obfuscated credentials Obfuscated credentials * Updated codelabs for SAP AEM INT - Day 2 * Updated codelabs for SAP AEM INT - Day 2 * Added download link for EP design * Updated Day-2 content codelab --------- Co-authored-by: HariRangarajan-Solace <[email protected]> Co-authored-by: bradcaldwell88 <[email protected]>
SolaceDev · Nov 20, 2023 · eb55582 · eb55582 · github-actions · Nov 21, 2023
1 parent cc81308
commit eb55582
Show file tree

Hide file tree

Showing 7 changed files with 11 additions and 11 deletions.
diff --git a/codelabs/sap-aem-int-day-2/codelab.json b/codelabs/sap-aem-int-day-2/codelab.json
@@ -3,7 +3,7 @@
   "format": "html",
   "prefix": "https://storage.googleapis.com",
   "mainga": "UA-49880327-14",
-  "updated": "2023-10-15T21:40:06+02:00",
+  "updated": "2023-11-20T09:24:13+01:00",
   "id": "sap-aem-int-day-2",
   "duration": 19,
   "title": "Event Enable SAP Using SAP Advanced Event Mesh - Day 2",

diff --git a/codelabs/sap-aem-int-day-2/img/c4ca105fac243a9a.png b/codelabs/sap-aem-int-day-2/img/c4ca105fac243a9a.png
diff --git a/codelabs/sap-aem-int-day-2/img/de30158a431426c2.png b/codelabs/sap-aem-int-day-2/img/de30158a431426c2.png
diff --git a/codelabs/sap-aem-int-day-2/img/ede078b8efa29ed9.png b/codelabs/sap-aem-int-day-2/img/ede078b8efa29ed9.png
diff --git a/codelabs/sap-aem-int-day-2/index.html b/codelabs/sap-aem-int-day-2/index.html
@@ -20,7 +20,7 @@
   </style>
 </head>
 <body>
-   
+  <google-codelab-analytics gaid="UA-49880327-14" ga4id=""></google-codelab-analytics>
   <google-codelab codelab-gaid=""
                   codelab-ga4id=""
                   id="sap-aem-int-day-2"
@@ -54,7 +54,7 @@
         <p>In this task, you will be importing the design representing the events for this rapid evaluation.<br> This design is an example, and not a full implementation. The intent is to have enough design for an evaluation while allowing easy understanding of the concepts being demonstrated. The level of detail in the model is &#34;medium size,&#34; meaning that there are enough attributes to enable the demonstration, but it is not the full schema for the SAP objects involved.</p>
 <ol type="1">
 <li>From the SAP AEM Console, open the Designer.<br><img alt="SAP AEM EP Designer" src="img/d58daeb939b0a198.png"></li>
-<li>Import the demo domain from the provided export file.<br><br> Pull down the menu extension in the Application Domains view and select the import function. <img alt="SAP AEM EP Designer Import AppDomain-1" src="img/c5f026f0fa771f6b.png"><br><img alt="SAP AEM EP Designer Import AppDomain-2" src="img/e6a327048559bfbe.png"><br><br> Locate the <strong>btp_aem_demo.json</strong> file in your file system and import it:<br><img alt="SAP AEM EP Designer Import AppDomain-3" src="img/de669e9213753bf1.png"><br> After the import is complete, you will see the evaluation domain in the domains list.<br><img alt="SAP AEM EP Designer Import AppDomain-4" src="img/4d9cc373188ebae0.png"></li>
+<li>Import the demo domain from the provided export file.<br><br> Pull down the menu extension in the Application Domains view and select the import function. <img alt="SAP AEM EP Designer Import AppDomain-1" src="img/c5f026f0fa771f6b.png"><br><img alt="SAP AEM EP Designer Import AppDomain-2" src="img/e6a327048559bfbe.png"><br><br> Download <a href="https://github.com/SolaceLabs/aem-sap-integration/blob/main/EP-design/btp_aem_demo.json" target="_blank">btp_aem_demo.json</a> to your file system and import it:<br><img alt="SAP AEM EP Designer Import AppDomain-3" src="img/de669e9213753bf1.png"><br> After the import is complete, you will see the evaluation domain in the domains list.<br><img alt="SAP AEM EP Designer Import AppDomain-4" src="img/4d9cc373188ebae0.png"></li>
 <li>Take a quick tour of the domain model.<br><br> The initial view of the domain will be of the Applications tab.<br> You will see a number of modeled applications in the list related to the demo.<br><img alt="SAP AEM EP Designer AppDomain-view" src="img/170b4a8b5cdec379.png">Event APIs and Event API Products can be used to expose and manage AsyncAPI interfaces within organizations, or with external partners through your APIM vendor.<aside class="warning"><p> Note that Event APIs and Event API Products are advanced topics that will not be covered by this demonstration design.</p>
 </aside>
 Clicking on the Events tab, you will see a listing of events defined for the domain. <img alt="SAP AEM EP Designer events list" src="img/564daa43eb512d6c.png"><br> Clicking on the Schemas tab, you will see 5 schemas. <img alt="SAP AEM EP Designer schema list" src="img/965027f7518009ad.png"><br> For simplicity, we have defined one schema for use by all events dealing with each object.<br> Clicking on the Enumerations tab, you will see one enum. <img alt="SAP AEM EP Designer enum list" src="img/94ce2e7bbe3cce10.png"><br> Enums are used in the model to show a finite set of possible values.<br> For example, this one is defined to hold a concise set of rejected reason code values for sales orders.Moving back to the Events tab, we can use the search box near the top to filter down to the event(s) we want to find. For example, typing &#34;Sales&#34; here results in a live search that filters the list down to just Sales Order related events. <img alt="SAP AEM EP Designer events filter" src="img/dd05c94ee6c4ba7e.png"><br><br> Clicking on the Sales Order Create event in this view will drill into the definition of that event. <img alt="SAP AEM EP Designer event definition" src="img/cfe5260ce39f4688.png"><br> This provides an overview of the event details including the version, state, description, topic address, schema reference, and reference-by links. <img alt="SAP AEM EP Designer event details" src="img/3353bdcac289af25.png"><strong>Version &amp; State:<br></strong> Designer can be used to manage the version and state of model objects and tracks their relationships for you, enabling full SDLC (software development lifecycle) visibility. It also serves as a collaboration space that allows you to leverage events you create more effectively to derive new value for the business. <br><strong>Broker Type &amp; Topic Address:<br></strong> For AEM services (broker type = Solace), the topic address is a string with <strong>&#34;/&#34;</strong> separators that enables dynamic routing and filtering. Following best practice guidelines for creating topic strings is critical to your EDA success.<br><br> The general format is <strong>ORG/DOMAIN/VERB/VERSION/{ATTRIBUTE1}/{ATTRIBUTE2}/...<br></strong> Topics are a powerful mechanism employed by AEM to perform dynamic routing in an event mesh, moving copies of events only where they are needed. It also enables consuming clients to filter events within topics using subscriptions and wildcard characters <strong>(*, &gt;)</strong>.<br> This capability avoids client applications having to implement brittle, complex filtering logic to reject unwanted events.<br><br> Next, click on the referenced schema to expand your view. <img alt="SAP AEM EP Designer event schema reference" src="img/ea20b88b5d991693.png"><br> The referenced schema can be displayed as content in this view.<br> Now click on the expanded menu in this section and select Open Schema.<br><img alt="SAP AEM EP Designer event schema open" src="img/5f75f16b8f664ede.png"><br> This takes you directly to the Schema tab content. Here, you can see a more detailed description and have control to edit, create a version, and adjust the state of the schema.<br> The description includes links to references used to define the objects in the demonstration.<br> If you click on the expander, you can view just the schema text in a larger view without opening it for editing. <img alt="SAP AEM EP Designer schema designer" src="img/67f91f0845fed286.png"><br> The Designer tool will be a useful way to explore the demonstration data throughout your evaluation.</li>
@@ -85,7 +85,7 @@ <h2 is-upgraded>2: Connect with Your Broker Details</h2>
 <p>To connect with your broker details:</p>
 <ul>
 <li>Open your broker and select the &#34;connect&#34; tab at the top. <img alt="BrokerDetails" src="img/2f6785aaeae066de.png"></li>
-<li>Then, under the &#34;Solace Web Messaging&#34; section, you will find the 4 inputs you need to connect your broker to the dashboard. <img alt="BrokerDetails" src="img/6658a06e3a5a1f85.png"></li>
+<li>Then, under the &#34;Solace Web Messaging&#34; section, you will find the 4 inputs you need to connect your broker to the dashboard. <img alt="BrokerDetails" src="img/ede078b8efa29ed9.png"></li>
 <li>Now, you can copy and paste each input into the fields at the top of the dashboard and then finally click &#34;Connect&#34;. <img alt="Dashboard" src="img/6f7f3b7343384ea7.png"></li>
 <li>If your credentials are entered correctly, you will get a &#34;Success&#34; message that will verify that you are connected properly to the dashboard. If you do not see a &#34;Success&#34; message, then try again and make sure your details are correct for each input. <img alt="Dashboard" src="img/b51830a9e153bf13.png"></li>
 </ul>

diff --git a/markdown/sap-aem-int-day-2/img/Broker_Credentials_Find2.png b/markdown/sap-aem-int-day-2/img/Broker_Credentials_Find2.png
diff --git a/markdown/sap-aem-int-day-2/sap-aem-int-day-2.md b/markdown/sap-aem-int-day-2/sap-aem-int-day-2.md
@@ -47,7 +47,7 @@ but it is not the full schema for the SAP objects involved.
    ![SAP AEM EP Designer Import AppDomain-1](img/ep-designer-import-app-domain-1.png)\
    ![SAP AEM EP Designer Import AppDomain-2](img/ep-designer-import-app-domain-2.png)\
    \
-   Locate the **btp_aem_demo.json** file in your file system and import it: \
+   Download [btp_aem_demo.json](https://github.com/SolaceLabs/aem-sap-integration/blob/main/EP-design/btp_aem_demo.json) to your file system and import it: \
    ![SAP AEM EP Designer Import AppDomain-3](img/ep-designer-import-app-domain-3.png) \
    After the import is complete, you will see the evaluation domain in the domains list. \
    ![SAP AEM EP Designer Import AppDomain-4](img/ep-designer-import-app-domain-4.png)
@@ -130,7 +130,7 @@ but it is not the full schema for the SAP objects involved.
    Finally, click on the filter icon next to the search box to see how results can be filtered further: \
    ![SAP AEM EP Catalog-Screen 4](img/ep-catalog-4.png)
 5. Visualize your imported design with a modeled event mesh.
-   Event Portal includes a powerful tool called the Runtime Manager. One of the functions of this tool is to associate a domain model with a “modeled event mesh” running on your launched AEM event services. 
+   Event Portal includes a powerful tool called the Runtime Manager. One of the functions of this tool is to associate a domain model with a “modeled event mesh” running on your launched AEM event services.
    This allows the Runtime Manager to display a visualization of the interactions between applications and events. \
    While there are many additional powerful features of Runtime Manager, our evaluation will focus just on visualization. \
    From the SAP AEM Console, open the Runtime Manager: \
@@ -150,14 +150,14 @@ but it is not the full schema for the SAP objects involved.
    ![SAP AEM EP Runtime Event Manager - 7](img/ep-runtime-event-manager-7.png)
 
    Next, navigate back to the Designer and open the **BTP AEM Demo** domain. \
-   Under the Applications tab, you will see all the modeled applications. **For each application**, perform the following actions: 
-   - Click on the application’s row where it says “Standard” for application type. 
-   - In the preview pane to the right, select the “Add to Environment” extended menu action for version 1.0.0 of the application object. 
+   Under the Applications tab, you will see all the modeled applications. **For each application**, perform the following actions:
+   - Click on the application’s row where it says “Standard” for application type.
+   - In the preview pane to the right, select the “Add to Environment” extended menu action for version 1.0.0 of the application object.
    - Leaving the Default environment selected, pick your Modeled Event Mesh from the second pull down and both of your event mesh services from the Event Broker menu, then click Add.
    ![SAP AEM EP Runtime Event Manager - 8](img/ep-runtime-event-manager-8.png)\
    This will add the modeled applications to your modeled event mesh.  Since these applications reference the events, and those events reference the schemas, all of your model will now be associated with your modeled event mesh. \
    \
-   Finally, navigate back to the Runtime Manager and your modeled event mesh to see the default visualization: 
+   Finally, navigate back to the Runtime Manager and your modeled event mesh to see the default visualization:
    ![SAP AEM EP Runtime Event Manager - 9](img/ep-runtime-event-manager-9.png)\
    The applications are connected to one another with flow lines through the events which they are exchanging. This provides an overview of the interactions being modeled by the design.\
    You can use the view controls to zoom, center and change visualization settings: \
@@ -248,4 +248,4 @@ Duration: 0:07:00
 
 ![Soly Image Caption](img/soly.gif)
 
-Thanks for participating in this codelab! Let us know what you thought in the [Solace Community Forum](https://solace.community/)! If you found any issues along the way we'd appreciate it if you'd raise them by clicking the Report a mistake button at the bottom left of this codelab.
+Thanks for participating in this codelab! Let us know what you thought in the [Solace Community Forum](https://solace.community/)! If you found any issues along the way we'd appreciate it if you'd raise them by clicking the Report a mistake button at the bottom left of this codelab.