Sap aem int day 3 - updated adapter import (#335)

* Initial version of SAP AEM Integration - day 3

* Populating content for 3rd day

Populating content for 3rd day, prereqs mostly done, AEM configuration done, importing iflows done, configuring and deploying iflows in progress

* Populating codelab for day 3 - configuration steps

Added more steps for setting up Integration Suite with security credentials etc.

* Adjusted time estimates

Adjusted time estimates

* Added Overall Duration estimate

Added Overall Duration estimate

* Finished AEMBusinessPartnerAddressCheck

Finished description and configuration and deployment steps for AEMBusinessPartnerAddressCheck iflow.

* fixed typos and formatting

fixed typos and formatting

* Added configuration and deployment for 2 more flows

Added configuration and deployment for 2 more flows

* Added more details on the LegacyOutputAdapter

Added more details on the LegacyOutputAdapter

* Finished basic description of event flows

Finished basic description of event flows

* Finished describing AEM related settings and processing steps

Finished describing AEM related settings and processing steps

* Added takeaways

Added takeaways

* Fixed formatting

Fixed formatting

* Updated day-3 codelab

* Formatting updates

Formatting updates

* updated codelabs

* Formatting

Formatting

* Updated markdown and codelab to fix formatting

* More formatting

More formatting

* Updated codelab

* Formatting and new AEM adapter version

Formatting and new AEM adapter version

* Updated with latest codelab changes

* Fixed queue subs and more formatting

Fixed queue subs and more formatting

* Updated codelabs

* Repush updated queue subs for Legacy adapter

Repush updated queue subs for Legacy adapter

* Formatting

Formatting

* updated files

* Updated section 3

Updated section 3

* Removed  Unneeded artifacts

Removed unneeded artifacts

* More detailed steps

More detailed steps, more screenshots.

* More improvements and details

Added more details on security configuration, reordered iflow steps to prioritise the AEMLegacyOutputAdatper iflow demonstrating the DMQ handling, followed by the AddressChecker, then Email notification iflow last.

* Hide Todos

Hidden Todos and wip areas.

* Updated links

Updated links for downloadable content.

* Removed downloadables

Removed downloadables from codelab (moved to separete repository)

* Updated codelabs for SAP AEM INT - Day 3

* Marked BP address checker optional

Marked BP address checker optional as it requires set up of SAP BTP's DQM service.

* Updated codelabs for SAP AEM INT - Day 3

* Updated codelabs for SAP AEM INT - Day 3

* Updated codelabs SAP AEM INT-Day-3 to remove old redundant artifacts

* Restructured code lab

Restructured code lab to complete configuration and deployment of one iflow at a time.

* Restructured codelab

Restructured to separate into 3 separate iflow deployment scenarios, that can be completed one after the other end to end.

* Formatting

formatting

* further formatting

formatting

* formatting titles

* formatting

* Added section for CI/CD

* Note for CI/CD users

Added note to skip over queue configuration for those that used the CI/CD tool in  a previous step.

* test

test

* Updates to intro sections and scenario 1

Updates to intro sections and scenario 1

* Prepared scenario 2 for changes

Prepared scenario 2 to slot in changes developed by Scott.

* Updates to scenario 2

Updates to scenario 2

* Added troubleshooting guide

Added troubleshooting guide

* fixed link to CI tool

fixed link to CI tool

* Updating time estimates

Updating time estimates

* Added security module

Added security module

* formatting

formatting

* formatting

formatting

* more formatting

more formatting

* format, format

format, format

* more formatting testing

more formatting testing

* Updating wording/rephrasing

Updating wording/rephrasing

* Rephrased prereqs

Rephrased prereqs

* Added clarifications

Added clarifications after RPP in Feb 2024

* Additional instructions for importing the AEM adapter

Additional instructions for importing the AEM adapter from SAP.

* Created prereq codelab

* building skeleton for prereq codelab

building skeleton for prereq codelab

* Revert "building skeleton for prereq codelab"

This reverts commit f746ec9.

* Revert "Revert "building skeleton for prereq codelab""

This reverts commit 0c75036.

* Revert "Revert "Revert "building skeleton for prereq codelab"""

This reverts commit 5d7abba.

* Removed prereqs lab in day 3 branch

* Updated AEM adapter import

Updated lab with latest instructions for adapter import.

* Fixed typo and added duration

---------

Co-authored-by: HariRangarajan-Solace <[email protected]>
Co-authored-by: Hari-Rangarajan-Solace <[email protected]>
Co-authored-by: Tamimi Ahmad <[email protected]>

markdown/sap-aem-int-day-3/sap-aem-int-day-3.md

@@ -47,43 +47,20 @@ Download [AEM-Rapid-Pilot-day3.zip](https://github.com/SolaceLabs/aem-sap-integr
 ### B) Importing the official SAP AdvancedEventMesh Adapter into your CI tenant
 >aside negative A new Advanced Event Mesh specific adapter was made available in January 2024. If you haven't used this adatper in your CI tenant before, you may need to import it once. Follow these steps to get the official adapter from SAP. <br>
 
-- Navigate to your newly imported package: AEM-Rapid-Pilot-day3.
-- Take a copy of the AEMLegacyOutputAdapter flow.
-![CI Copy flow](img/CICopyFlow.png)
-- Choose a new name. (Accepting the default of `AEMLegacyOutputAdapter_copy` will do.)
-- Then open and edit your copy named  `AEMLegacyOutputAdapter_copy` or similar.
-![CI Edit flow](img/CICopyflowEdit.png)
-- Select the line named AdvancedEventMesh and delete it by clicking on the rubbish bin icon that appears.
-![CI delete adapter](img/CICopyflowDeleteAdapter.png)
-- After deletion, select the connector tool from the top and reconnect the Sender box to the Start icon.
-![CI connector tool](img/CICopyFlowConnectorTool.png)
-- You should see a pop up appear in which you can select the AdvancedEventMesh adapter. Selecting this should pull the SAP version of this adapter into your CI tenant.
-
-That's it, we should now be good to proceed.
-(You can cancel the changes in your copy `AEMLegacyOutputAdapter_copy` or similar and delete the copy of the flow now.)
-
->aside negative Skip over C) if you have successfully completed this step.
-
-### C) Download and import the AEM adapter for Integration Suite
-
->aside negative A new Advanced Event Mesh specific adapter was made available in January 2024. <br>
-**Only follow this step if you can't see the AdvancedEventMesh adapter in your Integration Suite tenant or if you want to use the preview version (provided) instead.** <br>
-	In that case, follow the steps in this section to get a preview of the AEM adapter:<br>
-	- Download the Integration Suite AEM Adapter<br>
-	- Import the AEM adapter into your Integration Suite tenant and deploy this adapter.
-
-Import the adapter into your package.
-![CI Adapter import](img/CIAdapterImport.png)
-
-Extract the downloaded zip and select the .esa file in the upload dialog. Runtime Profile should be Cloud Integration. (You should not be seeing the warning message `Integration adapter with the ID 'AdvancedEventMesh' already exists`. If you do, then you can skip this step as the adapter has already been made available to you.)
-![CI Adapter import](img/CIAdapterImportWizard.png)
-
-Deploy the adapter after import.
-![CI Adapter deploy](img/CIAdapterDeploy.png)
-
-
-See  [SAP documentation](https://help.sap.com/docs/integration-suite/sap-integration-suite/importing-custom-integration-adapter-in-cloud-foundry-environment#procedure) for more detailed instructions
-
+- Navigate to "Discover" -> "Integrations" in the left hand menu:<br>
+![CI Discover Integrations](img/CIDiscoverIntegrations.png)
+- Search for “advanced” to find the “Advanced Event Mesh Adapter for SAP Integration Suite”:<br>
+![CI Discover Adapter](img/CIDiscoverAdapter.png)
+- Select the adapter package by clicking on it, then click on “Copy” on the top right.<br>
+![CI Copy Adapter](img/CICopyAdapter.png)
+- Go to “Design” -> “Integrations and APIs” in the left hand menu and click on the newly created “Advanced Event Mesh Adapter for SAP Integration Suite” package.<br>
+![CI AEM package](img/CIAEMPackage.png)
+- Navigate to “Artifacts” to see the Integration Adapter and click on and select “Deploy” from the “Actions” menu.<br>
+![CI Deploy Adapter](img/CIDeployAdapter.png)
+- Select the “Cloud Integration” Runtime Profile.<br>
+![CI Deploy CI Runtime](img/CIDeployRuntime.png)
+- You should now be able to see the AdvancedEventMesh Integration Adapter if you navigate to “Monitor” -> “Integrations and APIs” and click on the tile “All” under “Manage Integration Content” with a status of “Started” if everything went well:<br>
+![CI Adapter Monitor](img/CIAdapterMonitor.png)
 
 ## Scenario 1 - SalesOrder: AEMLegacyOutputAdapter (mandatory)
 Duration: 0:30:00
@@ -546,7 +523,7 @@ Lastly, the AEM Receiver adapter is configured to persistently (to avoid message
 
 
 #### 2. Configuring and deploying the AEMBusinessPartnerAddressCheck iflow:
-![DQM service configuration](img/CIDQMServiceConfiguration.png)You
+![DQM service configuration](img/CIDQMServiceConfiguration.png)
 - Populate the connection details for the DQM service call out with the ones for your own DQM service instance. (You don't need to change the address, if you are using our DQM service. If you are using your own DQM service, you'll need to take the API URL from your token and append `/dq/addressCleanse/batch` to the end of it. It should look something like `https://api.dqmmicro.cfapps.eu10.hana.ondemand.com/dq/addressCleanse/batch`).
 - Hit configure at the top right and fill in the details to connect to your AEM broker service:
 
@@ -656,6 +633,7 @@ As you can see, broker ACLs are a quite powerful tool to tightly control access
 In addition to topic ACLs, remember that queue access is controlled by the queue ownership model and the "other permission".
 
 ## Troubleshooting
+Duration: 0:05:00
 
 #### Checking that your flow was deployed successfully.
 - Go to Monitor Artifacts -> Manage Integration Content -> All. <br>