Updating queue names

SAP-samples · Aug 16, 2024 · d0c3129 · d0c3129
1 parent c72b440
commit d0c3129
Show file tree

Hide file tree

Showing 5 changed files with 11 additions and 11 deletions.
diff --git a/exercises/06-publish-and-subscribe-events/README.md b/exercises/06-publish-and-subscribe-events/README.md
@@ -153,7 +153,7 @@ As explained previously, we can subscribe to a topic directly and so far we've c
 > [!IMPORTANT]
 > 🚨 Before we create a queue, make sure you open the `Queues` link in a new tab, so that you don't have to re-enter the credentials in the `Try Me!` page and connect again to the event broker.
 
-👉 Select the `Queues` link on the right-hand side to see the queues in the event broker service. Click the `+ Queue` button and enter a name, e.g. `codejam/edi/ce/[your-sap-community-username]/tickets`. Leave the default settings and add as a subscription the following: `codejam/edi/ce/[your-sap-community-username]/tickets/*`.
+👉 Select the `Queues` link on the right-hand side to see the queues in the event broker service. Click the `+ Queue` button and enter a name, e.g. `codejam_edi_ce_[your-sap-community-username]_tickets`. Leave the default settings and add as a subscription the following: `codejam/edi/ce/[your-sap-community-username]/tickets/*`.
 
 > [!NOTE]
 > You'll notice that we are "adding levels" in the queue name. This is not really necessary and similar to topic names, it is a string and it can be anything. We are just following a pattern to make it easier to understand what the queue is for.
@@ -167,7 +167,7 @@ As explained previously, we can subscribe to a topic directly and so far we've c
 
 Now that we have created a queue, let's subscribe to it in the `Try Me!` page.
 
-👉 Click the `Connect` button in the Subscriber section. It should grab the ***Solace Web Messaging*** credentials from the publisher section, if not provide them again. Expand the *Bind to an endpoint to receive guaranteed messages* collapsible section, enter the queue name in the text box, e.g. `codejam/edi/ce/[your-sap-community-username]/tickets`, and click the `Start Consume` button.
+👉 Click the `Connect` button in the Subscriber section. It should grab the ***Solace Web Messaging*** credentials from the publisher section, if not provide them again. Expand the *Bind to an endpoint to receive guaranteed messages* collapsible section, enter the queue name in the text box, e.g. `codejam_edi_ce_[your-sap-community-username]_tickets`, and click the `Start Consume` button.
 
 <p align = "center">
   <img alt="Consume Queue" src="assets/consume-queue.gif" width="100%"/><br/>

diff --git a/exercises/09-rest-delivery-points/README.md b/exercises/09-rest-delivery-points/README.md
@@ -40,18 +40,18 @@ For simplicity purposes, our REST consumer will be a simple HTTP endpoint that w
 
 ### Clone queue
 
-For this exercise, we will use the `AMER-USEast-Broker` event broker service. If you check out the queues available in this event broker service, you'll notice that there is a queue named `S4HC/BP/Created`. This queue is subscribed to the `sap/S4HANAOD/S4D/ce/sap/s4/beh/businesspartner/v1/BusinessPartner/Created/v1 ` topic, where the events for the BusinessPartner object created in SAP S/4HANA Cloud are being published. We will start by cloning this queue so that we have a copy of the message received and we will forward messages from this queue to a REST consumer.
+For this exercise, we will use the `AMER-USEast-Broker` event broker service. If you check out the queues available in this event broker service, you'll notice that there is a queue named `S4HC_BP_Created`. This queue is subscribed to the `sap/S4HANAOD/S4D/ce/sap/s4/beh/businesspartner/v1/BusinessPartner/Created/v1 ` topic, where the events for the BusinessPartner object created in SAP S/4HANA Cloud are being published. We will start by cloning this queue so that we have a copy of the message received and we will forward messages from this queue to a REST consumer.
 
-👉 Navigate to the `AMER-USEast-Broker` event broker service and click on the `Queues` link. You should see the `S4HC/BP/Created` queue. Select the check box, click on the **Action** button and select `Clone`.
+👉 Navigate to the `AMER-USEast-Broker` event broker service and click on the `Queues` link. You should see the `S4HC_BP_Created` queue. Select the check box, click on the **Action** button and select `Clone`.
 
 <p align = "center">
-    <img alt="Clone S4HC/BP/Created queue in AMER-USEast-Broker" src="assets/cloning_queue.gif" width="100%"/><br/>
-    <i>Clone S4HC/BP/Created queue in AMER-USEast-Broker</i>
+    <img alt="Clone S4HC_BP_Created queue in AMER-USEast-Broker" src="assets/cloning_queue.gif" width="100%"/><br/>
+    <i>Clone S4HC_BP_Created queue in AMER-USEast-Broker</i>
 </p>
 
 You will be prompted to enter a name and if you want to clone its topic subscriptions.
 
-👉 Enter a name for the cloned queue, e.g. `S4HC/BP/Created_[your_sap_community_id]` and select the `Children to Clone - Subscriptions` check box. Finalise by clicking the **Apply** button.
+👉 Enter a name for the cloned queue, e.g. `S4HC_BP_Created_[your_sap_community_id]` and select the `Children to Clone - Subscriptions` check box. Finalise by clicking the **Apply** button.
 
 > [!NOTE]
 > There is a separate service which is simulating the creation of BusinessPartner objects in SAP S/4HANA Cloud. It will also be publishing the events to the `sap/S4HANAOD/S4D/ce/sap/s4/beh/businesspartner/v1/BusinessPartner/Created/v1` topic. Meaning that once you've created the cloned queue, you should start seeing messages in the cloned queue. That said, it is very simple to configure a connection between SAP S/4HANA Cloud and SAP Integration Suite, advanced event mesh, you can find the step by step guide at help.sap.com - [Integration with Advanced Mesh Service Plan for Service Cloud](https://help.sap.com/docs/SAP_S4HANA_CLOUD/0f69f8fb28ac4bf48d2b57b9637e81fa/9b34c841dfba4f82af0825a2f3196ecf.html?locale=en-US). This was recently introduced in the [SAP S/4HANA Cloud 2402 release](https://help.sap.com/docs/SAP_S4HANA_CLOUD/ee9ee0ca4c3942068ea584d2f929b5b1/5fd69458026d47f7bcc11837b42c5371.html?locale=en-US&version=2402.500).
@@ -99,7 +99,7 @@ The newly created REST consumer will be listed in the REST Consumers tab. Now we
 
 ## Configure Queue binding
 
-👉 Navigate to the `Queue Bindings` tab and click on the **+ Queue Binding** button. Select the queue previously created, e.g. `S4HC/BP/Created_[your-sap-community-username]`, and click the **Create** button.
+👉 Navigate to the `Queue Bindings` tab and click on the **+ Queue Binding** button. Select the queue previously created, e.g. `S4HC_BP_Created_[your-sap-community-username]`, and click the **Create** button.
 
 <p align = "center">
     <img alt="Queue binding set up" src="assets/queue-binding.gif" width="100%"/><br/>

diff --git a/exercises/10-consume-message-from-CAP/README.md b/exercises/10-consume-message-from-CAP/README.md
@@ -66,7 +66,7 @@ To keep things simple for this exercise, we will be using the [AMQP 1.0](https:/
 ## Create a queue in the EU-North-Broker
 
 
-👉 Access the `EU-North-Broker` and create a new queue with the following name: `codejam/edi/[your-sap-community-username]/Tickets/Purchased`. Once created, subscribe to the `itelo/TMSPRD/ce/tms/ticket/v1/Ticket/Purchased/v1` topic.
+👉 Access the `EU-North-Broker` and create a new queue with the following name: `codejam_edi_[your-sap-community-username]_Tickets_Purchased`. Once created, subscribe to the `itelo/TMSPRD/ce/tms/ticket/v1/Ticket/Purchased/v1` topic.
 
 We've created the queue that we will be connecting from the CAP project to consume the events.
 

diff --git a/exercises/10-consume-message-from-CAP/code/edi-codejam-cap-processor/.env.sample b/exercises/10-consume-message-from-CAP/code/edi-codejam-cap-processor/.env.sample
@@ -3,7 +3,7 @@ SOLACE_AMQP_HOST="mr-connection-lvu25c1nx4m.messaging.solace.cloud"
 SOLACE_AMQP_PORT="5671"
 SOLACE_AMQP_USERNAME="solace-cloud-client"
 SOLACE_AMQP_PASSWORD="aosoy2veb5g44mmagk7pronet6"
-SOLACE_AMPQ_QUEUE_NAME="codejam/edi/[your-sap-community-username]/Tickets/Purchased"
+SOLACE_AMPQ_QUEUE_NAME="codejam_edi_[your-sap-community-username]_Tickets_Purchased"
 
 SOLACE_REST_PROTOCOL="https"
 SOLACE_REST_HOST="mr-connection-lvu25c1nx4m.messaging.solace.cloud"

diff --git a/exercises/11-aem-cloud-integration-adapter/README.md b/exercises/11-aem-cloud-integration-adapter/README.md
@@ -22,7 +22,7 @@ Before we get started, make a note of the connection details for the Solace Mess
 
 ## Queue for Cloud Integration
 
-👉 Access the `EU-North-Broker` and clone the queue created in the previous exercise and name it: `codejam/edi/[your-sap-community-username]/Tickets/Purchased_CloudIntegration`. Make sure to also clone the subscriptions. 
+👉 Access the `EU-North-Broker` and clone the queue created in the previous exercise and name it: `codejam_edi_[your-sap-community-username]_Tickets_Purchased_CloudIntegration`. Make sure to also clone the subscriptions. 
 
 <p align = "center">
     <img alt="Queue for Cloud Integration" src="assets/clone-queue-cloud-integration.png" width="100%"/><br/>