Updating Day-4 with Master (#296)

* Sap aem int day 4 (#286) * Initial version of SAP AEM Integration - day 4 * Add files via upload * Update sap-aem-int-day-4.md * updated codelabs folder * Update sap-aem-int-day-4.md * Add files via upload * Update sap-aem-int-day-4.md * updated exported codelabs * updated exported codelabs * Update sap-aem-int-day-4.md * Add files via upload * Update sap-aem-int-day-4.md * Add files via upload * Update sap-aem-int-day-4.md * Add files via upload * Add files via upload * updated files * Update sap-aem-int-day-4.md * Add files via upload * Update sap-aem-int-day-4.md * Update sap-aem-int-day-4.md * Add files via upload * Update sap-aem-int-day-4.md * Updated codelabs based on Scott's changes * Update sap-aem-int-day-4.md * Add files via upload * Update sap-aem-int-day-4.md * Add files via upload * Updated codelabs with latest content * Update sap-aem-int-day-4.md * Add files via upload * Add files via upload * Update sap-aem-int-day-4.md * Update sap-aem-int-day-4.md * Add files via upload * Update sap-aem-int-day-4.md * Updated codelabs based on Scott's changes * Update sap-aem-int-day-4.md * Updated codelabs based on Scott's changes * Updated codelabs for SAP AEM INT-Day-4 to include Neha's changes * Updated codelabs for SAP AEM INT-Day-4 to include Neha's changes * Updated codelabs for SAP AEM INT-Day-4 to include Neha's changes * Add files via upload * Update sap-aem-int-day-4.md * Add files via upload * Add files via upload * Update sap-aem-int-day-4.md * Updated codelabs SAP AEM INT-Day-4 to include Scott's changes --------- Co-authored-by: HariRangarajan-Solace <[email protected]> Co-authored-by: ScottDillonSol <[email protected]> Co-authored-by: Tamimi Ahmad <[email protected]> * minor modification (#287) * update dt codelab (#288) * update github user on main * update dt codelab steps (#289) * test git config users * remove test file * update workflow * update dt codelab (#290) * update PAT * update dt codelab (#291) * Adding dt-otel html files * update wokrflow * minor update (#292) * Adding dt-otel html files * Adding a test file * update workflow file * update workflow file * Minor modifications to the DT codelab (#293) * update secrets in workflow * minor modification (#294) * Adding dt-otel html files * Update netlify Badge Update netlify Badge * fix broken links * Adding boomi-v2-getting-started html files * Remove export scripts. Not needed anymore * Sap aem int day 1 (#295) * Initial version of SAP AEM Integration - day 1 * Update sap-aem-int-day-1.md * Updated day-1 for intro/takeaways * fixed takeaway step formatting * updated takeaways step codelab folder * Finalized Day-1 codelab * Removed steps setting cluster and vpn name Removed steps setting cluster and vpn name as this is causing issues with Mesh Manager. * SAP AEM Integration workshop - Day 3 (#264) * 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 --------- Co-authored-by: HariRangarajan-Solace <[email protected]> Co-authored-by: Christian <[email protected]> * SAP AEM Integration workshop - Day 2 (#263) * 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 --------- Co-authored-by: HariRangarajan-Solace <[email protected]> Co-authored-by: bradcaldwell88 <[email protected]> * Updated codelabs for SAP AEM INT - Day 1 * Updated codelabs for SAP AEM INT - Day 1 * Updated codelabs for SAP AEM INT - Day 1 to fix cluster names * Updated codelabs SAP AEM INT-Day-1 to fix the CF push command. --------- Co-authored-by: HariRangarajan-Solace <[email protected]> Co-authored-by: Christian <[email protected]> Co-authored-by: bradcaldwell88 <[email protected]> * Adding sap-aem-int-day-1 html files --------- Co-authored-by: HariRangarajan-Solace <[email protected]> Co-authored-by: ScottDillonSol <[email protected]> Co-authored-by: Tamimi Ahmad <[email protected]> Co-authored-by: Tamimi <[email protected]> Co-authored-by: solacecommunity-bot <[email protected]> Co-authored-by: Christian <[email protected]> Co-authored-by: bradcaldwell88 <[email protected]>
SolaceDev · Dec 5, 2023 · 21f9ebf · 21f9ebf
1 parent 08efc0f
commit 21f9ebf
Show file tree

Hide file tree

Showing 70 changed files with 64 additions and 637 deletions.
diff --git a/.github/workflows/comment.yml b/.github/workflows/comment.yml
@@ -8,9 +8,9 @@ jobs:
     name: Add guidelines comment
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@master
+      - uses: actions/checkout@v3
       - uses: harupy/comment-on-pr@master
         env:
-          GITHUB_TOKEN: ${{ secrets.SOLACE_BOT }}
+          GITHUB_TOKEN: ${{ secrets.SOLACE_COMMUNITY_BOT_ULTIMATE }}
         with:
           filename: comment-content.md
diff --git a/.github/workflows/export-codelab.yml b/.github/workflows/export-codelab.yml
@@ -17,13 +17,19 @@ jobs:
           go-version: '1.20.5'
 
       - name: Checkout Current Branch
-        uses: actions/checkout@master
+        uses: actions/checkout@v3
         with:
+          persist-credentials: false
+          fetch-depth: 0
+          token: ${{ secrets.SOLACE_COMMUNITY_BOT_ULTIMATE }}
           path: main
 
       - name: Checkout claat repo
-        uses: actions/checkout@v2
+        uses: actions/checkout@v3
         with:
+          ref: ${{ github.head_ref }}
+          fetch-depth: 0
+          token: ${{ secrets.SOLACE_COMMUNITY_BOT_ULTIMATE }}
           repository: SolaceDev/google-tools
           path: google-tools
 
@@ -49,8 +55,10 @@ jobs:
       - name: Push updates to codelabs repo
         run: |
           cd main
-          git config user.name SollyBot
+          git config user.name solacecommunity-bot
           git config user.email [email protected]
           git add codelabs/.
           git commit -m "Adding ${{env.CHANGED_CODELABS}} html files"
-          git push https://${{env.SOLACE_BOT}}@github.com/Solacedev/solace-dev-codelabs
+          git push https://solacecommunity-bot:${{secrets.SOLACE_COMMUNITY_BOT_ULTIMATE}}@github.com/Solacedev/solace-dev-codelabs
+        env:
+          GITHUB_TOKEN: ${{ secrets.SOLACE_COMMUNITY_BOT_ULTIMATE }}
diff --git a/.github/workflows/site-update.yml b/.github/workflows/site-update.yml
@@ -26,6 +26,7 @@ jobs:
 
       - name: Update submodule
         run: |
+          cd site
           git submodule update --remote
           git config user.name github-actions
           git config user.email [email protected]

diff --git a/.gitignore b/.gitignore
@@ -2,3 +2,5 @@
 node_modules
 *lock*
 temp/
+.project
+.vscode
diff --git a/.project b/.project
diff --git a/.vscode/settings.json b/.vscode/settings.json
diff --git a/README.md b/README.md
@@ -1,5 +1,5 @@
 ![Update Codelabs Site Repo](https://github.com/SolaceDev/solace-dev-codelabs/workflows/Update%20Codelabs%20Site%20Repo/badge.svg)
-[![Netlify Status](https://api.netlify.com/api/v1/badges/e66602c6-9a94-4095-a7c4-4e37ff2cdd41/deploy-status)](https://app.netlify.com/sites/focused-beaver-3cc79d/deploys)
+[![Netlify Status](https://api.netlify.com/api/v1/badges/e66602c6-9a94-4095-a7c4-4e37ff2cdd41/deploy-status)](https://app.netlify.com/sites/codelabs-solace/deploys)
 [![Weekly link checker](https://github.com/SolaceDev/solace-dev-codelabs/actions/workflows/fullbrokenlink.yml/badge.svg)](https://github.com/SolaceDev/solace-dev-codelabs/actions/workflows/fullbrokenlink.yml)
 
 
@@ -44,4 +44,4 @@ Follow the steps in this tutorial: https://codelabs.solace.dev/codelabs/codelab-
 Note: original markdown of this codelab is found under [codelabs/codelab-4-codelab](./codelabs/codelab-4-codelab)
 
 ## Learn About CodeLab
-* CodeLabs are being created using Google Codelabs: https://github.com/googlecodelabs/tools
+* CodeLabs are being created using Google Codelabs: https://github.com/googlecodelabs/tools
diff --git a/codelabs/boomi-salesforce-codelab/codelab.json b/codelabs/boomi-salesforce-codelab/codelab.json
@@ -3,16 +3,26 @@
   "format": "html",
   "prefix": "https://storage.googleapis.com",
   "mainga": "UA-49880327-14",
-  "updated": "2020-10-01T13:28:49-04:00",
+  "updated": "2023-11-30T00:33:04Z",
   "id": "boomi-salesforce-codelab",
   "duration": 103,
   "title": "Event enabling Salesforce and AzureDB using Boomi and Solace",
   "summary": "",
-  "source": "boomi-salesforce-codelab.md",
+  "source": "main/markdown/boomi-salesforce-codelab/boomi-salesforce-codelab.md",
   "theme": "",
-  "status": ["draft"],
-  "category": ["boomi", "salesforce", "azure", "taxi"],
-  "tags": ["web", "workshop"],
+  "status": [
+    "draft"
+  ],
+  "category": [
+    "boomi",
+    "salesforce",
+    "azure",
+    "taxi"
+  ],
+  "tags": [
+    "web",
+    "workshop"
+  ],
   "feedback": "https://github.com/jmenning-solace/nycmoderntaxi",
   "url": "boomi-salesforce-codelab"
 }
diff --git a/codelabs/boomi-salesforce-codelab/index.html b/codelabs/boomi-salesforce-codelab/index.html
@@ -20,8 +20,9 @@
   </style>
 </head>
 <body>
-   
+  <google-codelab-analytics gaid="UA-49880327-14" ga4id=""></google-codelab-analytics>
   <google-codelab codelab-gaid=""
+                  codelab-ga4id=""
                   id="boomi-salesforce-codelab"
                   title="Event enabling Salesforce and AzureDB using Boomi and Solace"
                   environment="web"
@@ -360,7 +361,7 @@ <h2 is-upgraded>⚙️ Test it out using Salesforce Workbench</h2>
 
       <google-codelab-step label="Takeaways" duration="1">
         <p>Thanks for participating in this codelab! Let us know what you thought in the <a href="https://solace.community/" target="_blank">Solace Community Forum</a>! If you found any issues along the way we&#39;d appreciate it if you&#39;d raise them by clicking the Report a mistake button at the bottom left of this codelab.</p>
-<p>✅ For more information on the Solace Connector check out the <a href="https://solace.com/connectors/dell-boomi-ipaas/" target="_blank">PubSub+ Connector Hub</a> page</p>
+<p>✅ For more information on the Solace Connector check out the <a href="https://solace.com/integration-hub/boomi-ipaas/" target="_blank">PubSub+ Connector Hub</a> page</p>
 
 
       </google-codelab-step>

diff --git a/codelabs/boomi-v2-getting-started/codelab.json b/codelabs/boomi-v2-getting-started/codelab.json
@@ -3,19 +3,19 @@
   "format": "html",
   "prefix": "https://storage.googleapis.com",
   "mainga": "UA-49880327-14",
-  "updated": "2021-11-30T13:24:45-05:00",
+  "updated": "2023-11-30T00:33:04Z",
   "id": "boomi-v2-getting-started",
   "duration": 86,
   "title": "Getting started with Boomi and Solace",
   "summary": "",
-  "source": "boomi-v2-getting-started.md",
+  "source": "main/markdown/boomi-v2-getting-started/boomi-v2-getting-started.md",
   "theme": "",
   "status": [
     "published"
   ],
   "category": [
     "boomi",
-    "event portal"
+    "eventportal"
   ],
   "tags": [
     "web",

diff --git a/codelabs/boomi-v2-getting-started/index.html b/codelabs/boomi-v2-getting-started/index.html
@@ -20,8 +20,9 @@
   </style>
 </head>
 <body>
-   
+  <google-codelab-analytics gaid="UA-49880327-14" ga4id=""></google-codelab-analytics>
   <google-codelab codelab-gaid=""
+                  codelab-ga4id=""
                   id="boomi-v2-getting-started"
                   title="Getting started with Boomi and Solace"
                   environment="web"
@@ -283,7 +284,7 @@ <h2 is-upgraded>Check out the logs</h2>
       </google-codelab-step>
 
       <google-codelab-step label="Takeaways" duration="7">
-        <p>✅ Sign up for a Solace PubSub+ Cloud account and configure a messaging service broker with a queue<br> ✅ Sign up for a Boomi AtomSphere account and setup a Solace Pubsub+ Connector for a listen configuration and bind to a message queue<br> ✅ Send events to the same topic the queue is subscribed to<br> ✅ Check out more information on the Solace Connector in the <a href="https://solace.com/connectors/dell-boomi-ipaas/" target="_blank">PubSub+ Connector Hub</a> page</p>
+        <p>✅ Sign up for a Solace PubSub+ Cloud account and configure a messaging service broker with a queue<br> ✅ Sign up for a Boomi AtomSphere account and setup a Solace Pubsub+ Connector for a listen configuration and bind to a message queue<br> ✅ Send events to the same topic the queue is subscribed to<br> ✅ Check out more information on the Solace Connector in the <a href="https://solace.com/integration-hub/boomi-ipaas/" target="_blank">PubSub+ Connector Hub</a> page</p>
 <p>Thanks for participating in this codelab! Let us know what you thought in the <a href="https://solace.community/" target="_blank">Solace Community Forum</a>!</p>
 
 

diff --git a/codelabs/dt-otel/codelab.json b/codelabs/dt-otel/codelab.json
@@ -3,12 +3,12 @@
   "format": "html",
   "prefix": "https://storage.googleapis.com",
   "mainga": "UA-49880327-14",
-  "updated": "2023-10-06T12:44:20-04:00",
+  "updated": "2023-11-30T00:24:36Z",
   "id": "dt-otel",
   "duration": 89,
   "title": "Getting Started with Solace Distributed Tracing and Context Propagation",
   "summary": "This Codelab will walk you through how to get started using Solace Distributed Tracing with Context Propagation",
-  "source": "dt-otel.md",
+  "source": "main/markdown/dt-otel/dt-otel.md",
   "theme": "",
   "status": [
     "published"

diff --git a/codelabs/dt-otel/index.html b/codelabs/dt-otel/index.html
@@ -20,21 +20,22 @@
   </style>
 </head>
 <body>
-   
+  <google-codelab-analytics gaid="UA-49880327-14" ga4id=""></google-codelab-analytics>
   <google-codelab codelab-gaid=""
+                  codelab-ga4id=""
                   id="dt-otel"
                   title="Getting Started with Solace Distributed Tracing and Context Propagation"
                   environment="web"
                   feedback-link="https://github.com/SolaceDev/solace-dev-codelabs/blob/master/markdown/dt-otel">
 
       <google-codelab-step label="What you&#39;ll learn: Overview" duration="3">
-        <p>This codelab will take you through the basics of the Soalce PubSub+ Distributed Tracing feature. Following these steps will take you through:</p>
+        <p>This codelab will take you through the basics of the Soalce PubSub+ Distributed Tracing feature. The following steps will take you through:</p>
 <ul>
-<li>Launching and configuring a PubSub+ Event Broker Software</li>
-<li>Launching the OpenTelemetry Collector Contribution</li>
-<li>Launching Jaeger, the open source, end-to-end distributed tracing backend to observe our traces</li>
-<li>Publishing and receiving messages to/from your broker to generate broker trace events</li>
-<li>Context propagation via auto-instrumented JMS applications that will generate end to end linked traces (publisher – broker – receiver traces)</li>
+<li>Launching and configuring a PubSub+ Event Broker locally via Docker</li>
+<li>Launching and configuring the OpenTelemetry Collector Contribution</li>
+<li>Launching Jaeger: the open source, end-to-end distributed tracing backend to observe our traces</li>
+<li>Publishing and receiving messages to and from the broker to generate broker trace events</li>
+<li>Context propagation via auto-instrumented JMS applications that generates end to end linked traces (publisher – broker – receiver traces)</li>
 <li>Context propagation via manual-instrumented JCSMP applications that will generate end to end linked traces (publisher – broker – receiver traces)</li>
 </ul>
 <p>Upon successful completion of this codelab, we encourage you to experiment with distributed tracing and the environment provided to see how it fits with your use case(s). This can include other message sources, OpenTelemetry exporters, and telemetry analysis tools.</p>

diff --git a/codelabs/sap-aem-int-day-1/codelab.json b/codelabs/sap-aem-int-day-1/codelab.json
@@ -3,12 +3,12 @@
   "format": "html",
   "prefix": "https://storage.googleapis.com",
   "mainga": "UA-49880327-14",
-  "updated": "2023-11-23T11:28:57+01:00",
+  "updated": "2023-12-04T09:44:23Z",
   "id": "sap-aem-int-day-1",
   "duration": 12,
   "title": "Event Enable SAP Using SAP Advanced Event Mesh - Day 1",
   "summary": "Day 1/5 : This code lab walks the participant through the experience of using SAP AEM to event enable their SAP ecosystem and workflows",
-  "source": "sap-aem-int-day-1.md",
+  "source": "main/markdown/sap-aem-int-day-1/sap-aem-int-day-1.md",
   "theme": "",
   "status": [
     "hidden"

diff --git a/codelabs/sap-aem-int-day-1/index.html b/codelabs/sap-aem-int-day-1/index.html
@@ -160,7 +160,7 @@ <h2 is-upgraded>3 : Login to CloudFoundry space</h2>
 <h2 is-upgraded>4 : Deploying the SAP Simulator application</h2>
 <ul>
 <li>Navigate to the directory where the above deployable artefact files are saved.</li>
-<li>Run the command <code>cf push</code> which will upload the jar file and use the manifest.yml for properties. <strong>Note : this command will take some time to completely execute as it uploads the jar deployable and also start the application.</strong></li>
+<li>Run the command <code>cf push --random-route</code> which will upload the jar file and use the manifest.yml for properties. <strong>Note : this command will take some time to completely execute as it uploads the jar deployable and also start the application.</strong></li>
 <li>Once the command is completely executed, run the command <code>cf apps</code> to view a listing of the apps in your cloudfoundry space</li>
 <li>Verify that the app <strong>capm-erp-simulation</strong> is deployed and started</li>
 </ul>

diff --git a/markdown/Boomi-request-reply/export.sh b/markdown/Boomi-request-reply/export.sh
diff --git a/markdown/azure2Solace/export.sh b/markdown/azure2Solace/export.sh
diff --git a/markdown/boomi-salesforce-codelab/boomi-salesforce-codelab.md b/markdown/boomi-salesforce-codelab/boomi-salesforce-codelab.md
@@ -487,4 +487,4 @@ Duration: 0:01:00
 
 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.
 
-✅ For more information on the Solace Connector check out the [PubSub+ Connector Hub](https://solace.com/connectors/dell-boomi-ipaas/) page
+✅ For more information on the Solace Connector check out the [PubSub+ Connector Hub](https://solace.com/integration-hub/boomi-ipaas/) page
diff --git a/markdown/boomi-salesforce-codelab/export.sh b/markdown/boomi-salesforce-codelab/export.sh
diff --git a/markdown/boomi-v2-getting-started/boomi-v2-getting-started.md b/markdown/boomi-v2-getting-started/boomi-v2-getting-started.md
@@ -419,6 +419,6 @@ Duration: 0:07:00
 ✅ Sign up for a Solace PubSub+ Cloud account and configure a messaging service broker with a queue  
 ✅ Sign up for a Boomi AtomSphere account and setup a Solace Pubsub+ Connector for a listen configuration and bind to a message queue  
 ✅ Send events to the same topic the queue is subscribed to  
-✅ Check out more information on the Solace Connector in the [PubSub+ Connector Hub](https://solace.com/connectors/dell-boomi-ipaas/) page
+✅ Check out more information on the Solace Connector in the [PubSub+ Connector Hub](https://solace.com/integration-hub/boomi-ipaas/) page
 
 Thanks for participating in this codelab! Let us know what you thought in the [Solace Community Forum](https://solace.community/)!
diff --git a/markdown/boomi-v2-getting-started/export.sh b/markdown/boomi-v2-getting-started/export.sh
diff --git a/markdown/codelab-4-codelab/export.sh b/markdown/codelab-4-codelab/export.sh
diff --git a/markdown/create-api-products-using-scs-and-ep/export.sh b/markdown/create-api-products-using-scs-and-ep/export.sh
diff --git a/markdown/design-document-discover-develop-event-driven-apis/export.sh b/markdown/design-document-discover-develop-event-driven-apis/export.sh
diff --git a/markdown/design-to-code-workshop/export.sh b/markdown/design-to-code-workshop/export.sh
diff --git a/markdown/dt-otel/dt-otel.md b/markdown/dt-otel/dt-otel.md
@@ -13,11 +13,11 @@ feedback link: https://github.com/SolaceDev/solace-dev-codelabs/blob/master/mark
 Duration: 0:03:00
 
 This codelab will take you through the basics of the Soalce PubSub+ Distributed Tracing feature. The following steps will take you through:
-* Launching and configuring a PubSub+ Event Broker Software
-* Launching the OpenTelemetry Collector Contribution
-* Launching Jaeger, the open source, end-to-end distributed tracing backend to observe our traces   
-* Publishing and receiving messages to/from your broker to generate broker trace events
-* Context propagation via auto-instrumented JMS applications that will generate end to end linked traces (publisher – broker – receiver traces)
+* Launching and configuring a PubSub+ Event Broker locally via Docker
+* Launching and configuring the OpenTelemetry Collector Contribution
+* Launching Jaeger: the open source, end-to-end distributed tracing backend to observe our traces   
+* Publishing and receiving messages to and from the broker to generate broker trace events
+* Context propagation via auto-instrumented JMS applications that generates end to end linked traces (publisher – broker – receiver traces)
 * Context propagation via manual-instrumented JCSMP applications that will generate end to end linked traces (publisher – broker – receiver traces)
 
 Upon successful completion of this codelab, we encourage you to experiment with distributed tracing and the environment provided to see how it fits with your use case(s). This can include other message sources, OpenTelemetry exporters, and telemetry analysis tools.
-Original file line number
+Diff line change
@@ Expand Up / @@ -2,3 +2,5 @@ @@
     node_modules
     *lock*
     temp/
+    .project
+    .vscode
Original file line number	Diff line number	Diff line change
Expand Up		@@ -487,4 +487,4 @@ Duration: 0:01:00

		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.

		✅ For more information on the Solace Connector check out the [PubSub+ Connector Hub](https://solace.com/connectors/dell-boomi-ipaas/) page
		✅ For more information on the Solace Connector check out the [PubSub+ Connector Hub](https://solace.com/integration-hub/boomi-ipaas/) page