Replace username with display name

Author: ajmaradiaga

assets/codejam-exercises.drawio

@@ -7,7 +7,7 @@ So far, we've learned about events in the SAP ecosystem, CloudEvents and the dif
 Let's log in to the SAP Integration Suite, advanced event mesh instance that we've made available for the event.
 > 🔐 Your instructor will provide you with the details to access the SAP Integration Suite, advanced event mesh instance.
 
-👉 Navigate to the instance URL provided, e.g. `https://[region].console.pubsub.em.services.cloud.sap/login?tenant-id=[our-tenant-id]`, and enter the user credentials provided to you, e.g. `EDI-[country]-[your-sap-community-username]@sap.com`.
+👉 Navigate to the instance URL provided, e.g. `https://[region].console.pubsub.em.services.cloud.sap/login?tenant-id=[our-tenant-id]`, and enter the user credentials provided to you, e.g. `EDI-[country]-[your-sap-community-display-name]@sap.com`.
 
 <p align = "center">
     <img alt="AEM start page" src="assets/aem-start-page.png" width="90%"/><br/>

exercises/05-explore-aem/README.md

@@ -21,7 +21,7 @@ Example: `sap/S4HANAOD/E4L/ce/sap/s4/beh/businesspartner/v1/BusinessPartner/Crea
 - */v1*: Version of the message. If a new version of the message is made available, e.g. adding new fields to the payload, then this will change.
 
 > [!NOTE]
-> In our case, we've defined levels on our topic string based on the week, SAP Community username and action, e.g. `codejam/edi/ce/ajmaradiaga/notification`.
+> In our case, we've defined levels on our topic string based on the week, SAP Community display name and action, e.g. `codejam/edi/ce/ajmaradiaga/notification`.
 
 Now, by knowing the topic on which a message type will be published, we can create a consumer program/service that subscribes to the topic directly and processes the messages sent to it. Generally, you can subscribe to a topic by specifying the entire topic string when establishing the connection, e.g. *sap/S4HANAOD/E4L/ce/sap/s4/beh/businesspartner/v1/BusinessPartner/Created/v1*. But what if we want to subscribe to all actions (Created, Updated, Deleted) that occur on a BusinessPartner object? Luckily, in the case of SAP Integration Suite, advanced event mesh we can subscribe to the topic by using wildcards (\*). For example, by subscribing to the topic sap/S4HANAOD/E4L/ce/sap/s4/beh/businesspartner/v1/BusinessPartner/*/v1 I will be able to get all messages for different actions (Created, Updated, Deleted) whose version is v1. In AEM, the > character can be used at the last level of a subscription to indicate a "one or more" wildcard match for any topics, e.g. by subscribing to the topic *sap/S4HANAOD/E4L/ce/sap/s4/beh/>* will bring all objects that are published under that prefix, independent of type, action, and version.
 
@@ -65,8 +65,8 @@ In AEM there is a concept of a Topic Endpoint. A Topic Endpoint is a durable sto
 We published a simple event in the previous exercise by using the `Try Me!` page in the `EU-North-Broker` event broker service. Let's now explore another mechanism to exchange messages with our event broker. By the end of this exercise we will achieve a communication scenario like the one below. Enter the `Try Me!`.
 
 <p align = "center">
-  <img alt="Publish and subscribe to the codejam/edi/ce/[your-sap-community-username]/tickets/Created topic" src="assets/codejam-exercises-Exercise6 - AdvancedTryMe.png" width="70%"/><br/>
-  <i>Publish/subscribe to the codejam/edi/ce/[your-sap-community-username]/tickets/Created topic</i>
+  <img alt="Publish and subscribe to the codejam/edi/ce/[your-sap-community-display-name]/tickets/Created topic" src="assets/codejam-exercises-Exercise6 - AdvancedTryMe.png" width="70%"/><br/>
+  <i>Publish/subscribe to the codejam/edi/ce/[your-sap-community-display-name]/tickets/Created topic</i>
 </p>
 
 👉 Navigate to the `EU-North-Broker` event broker service and click the `Open Broker manager` link. On the right-hand side, click the `Try Me!` link. Here you can not just publish and subscribe to topics but we can also interact with queues in the event broker.
@@ -93,7 +93,7 @@ Now, we've got the connection details that we need to configure in the `Try Me!`
   <i>Try Me! - Connect</i>
 </p>
 
-We have connected the Publisher section to the event broker service. Now, let's publish an event on a topic. We will use the `codejam/edi/ce/[your-sap-community-username]/tickets/Created` topic and the payload below.
+We have connected the Publisher section to the event broker service. Now, let's publish an event on a topic. We will use the `codejam/edi/ce/[your-sap-community-display-name]/tickets/Created` topic and the payload below.
 
 ```json
 {
@@ -124,7 +124,7 @@ We have connected the Publisher section to the event broker service. Now, let's
 }
 ```
 
-👉 Replace the `[your-sap-community-username]` value in the topic example above, with your SAP Community username, and set it as the topic, e.g. `codejam/edi/ce/ajmaradiaga/tickets/Created`. Copy the JSON payload above and publish the message by clicking the `Publish` button.
+👉 Replace the `[your-sap-community-display-name]` value in the topic example above, with your SAP Community display name, and set it as the topic, e.g. `codejam/edi/ce/ajmaradiaga/tickets/Created`. Copy the JSON payload above and publish the message by clicking the `Publish` button.
 
 <p align = "center">
   <img alt="Try Me! - Publish" src="assets/advanced-try-me-publish.png" width="100%"/><br/>
@@ -137,7 +137,7 @@ Ok, we've published the message but it doesn't seem like much has happened. Apar
 
 We've successfully connected the publisher section to the event broker by providing the ***Solace Web Messaging*** credentials. Let's now connect the subscriber section. In this case, we can reuse the same details used for the publisher.
 
-👉 Click the `Connect` button in the Subscriber section and subscribe to the `codejam/edi/ce/[your-sap-community-username]/tickets/Created` topic. Once subscribed publish the message again.
+👉 Click the `Connect` button in the Subscriber section and subscribe to the `codejam/edi/ce/[your-sap-community-display-name]/tickets/Created` topic. Once subscribed publish the message again.
 
 <p align = "center">
   <img alt="Try Me! - Subscribe" src="assets/advanced-try-me-subscribe.gif" width="90%"/><br/>
@@ -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-display-name]_tickets`. Leave the default settings and add as a subscription the following: `codejam/edi/ce/[your-sap-community-display-name]/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-display-name]_tickets`, and click the `Start Consume` button.
 
 <p align = "center">
   <img alt="Consume Queue" src="assets/consume-queue.gif" width="100%"/><br/>
@@ -196,7 +196,7 @@ In the examples above we've not changed the Delivery Mode. Two delivery modes ar
 
 Before moving to the next exercise, let's clean up the queue we've created in this exercise.
 
-👉 Navigate to the broker manager of the EU-North-Broker event broker service and go to the `Queues` page. Select the queue you've created, e.g. `codejam_edi_ce_[your-sap-community-username]_tickets`, and perform the `Delete` action from the **Action** options.
+👉 Navigate to the broker manager of the EU-North-Broker event broker service and go to the `Queues` page. Select the queue you've created, e.g. `codejam_edi_ce_[your-sap-community-display-name]_tickets`, and perform the `Delete` action from the **Action** options.
 
 <p align = "center">
   <img alt="Delete queue" src="assets/delete-queue.gif" width="100%"/><br/>
@@ -221,7 +221,7 @@ We've covered a lot in this exercise. We've learned about topics, topic subscrip
 If you finish earlier than your fellow participants, you might like to ponder these questions. There isn't always a single correct answer and there are no prizes - they're just to give you something else to think about.
 
 1. What happens if a consumer that's been subscribed to a topic goes down/becomes unavailable and a message is published to a topic that we are interested?
-2. Which wildcard will you be able to specify to receive all messages published `codejam/edi/ce/[your-sap-community-username]/tickets/Created`? What if you want to receive all messages, independent of levels for a particular SAP Community username?
+2. Which wildcard will you be able to specify to receive all messages published `codejam/edi/ce/[your-sap-community-display-name]/tickets/Created`? What if you want to receive all messages, independent of levels for a particular SAP Community display name?
 3. Some queues can be configured to have multiple consumers. Can you think of a scenario where this would be useful?
 4. On the Queues page of our event broker service, there were some queues whose names started with a #. What do you think this means?
 

exercises/06-publish-and-subscribe-events/README.md

@@ -3,8 +3,8 @@
 In the SAP Integration Suite, advanced event mesh instance that we are using for this event has more than one event broker service but so far we've only published and consumed messages within a single event broker service. In this exercise, we will learn about Dynamic Message Routing and we will see messages being exchanged between brokers. By the end of this exercise, we will achieve a communication scenario like the one below.
 
 <p align = "center">
-  <img alt="Publish and subscribe to the codejam/edi/ce/[your-sap-community-username]/dmr topic via DMR" src="assets/codejam-exercises-Exercise7 - DMR.png" width="80%"/><br/>
-  <i>Publish/subscribe to the codejam/edi/ce/[your-sap-community-username]/dmr topic via DMR</i>
+  <img alt="Publish and subscribe to the codejam/edi/ce/[your-sap-community-display-name]/dmr topic via DMR" src="assets/codejam-exercises-Exercise7 - DMR.png" width="80%"/><br/>
+  <i>Publish/subscribe to the codejam/edi/ce/[your-sap-community-display-name]/dmr topic via DMR</i>
 </p>
 
 ## Dynamic Message Routing (DMR)
@@ -41,11 +41,11 @@ We've seen how we can exchange messages within a single event broker service. No
     <i>Message exchange between event broker services</i>
 </p>
 
-👉 Navigate to Mission Control > Cluster Manager and open the broker manager for `APJ-IN-Broker`. Go to the `Try Me!` page and establish a connection in the subscriber section. Subscribe to the `codejam/edi/ce/[your-sap-community-username]/dmr` topic.
+👉 Navigate to Mission Control > Cluster Manager and open the broker manager for `APJ-IN-Broker`. Go to the `Try Me!` page and establish a connection in the subscriber section. Subscribe to the `codejam/edi/ce/[your-sap-community-display-name]/dmr` topic.
 
 We've subscribed to the topic in the `APJ-IN-Broker` event broker service. Now, let's publish a message on the same topic but from the `EU-North-Broker` event broker service.
 
-👉 Navigate to Mission Control > Cluster Manager and select the `EU-North-Broker`. Go to the `Try Me!` tab, navigate to the Broker Manager Try Me! page, establish a connection in the Publisher section and publish the message below to the `codejam/edi/ce/[your-sap-community-username]/dmr` topic.
+👉 Navigate to Mission Control > Cluster Manager and select the `EU-North-Broker`. Go to the `Try Me!` tab, navigate to the Broker Manager Try Me! page, establish a connection in the Publisher section and publish the message below to the `codejam/edi/ce/[your-sap-community-display-name]/dmr` topic.
 
 ```json
 {
@@ -78,7 +78,7 @@ There is an optional exercise part of this CodeJam that covers configuring a Mes
 
 If you finish earlier than your fellow participants, you might like to ponder these questions. There isn't always a single correct answer and there are no prizes - they're just to give you something else to think about.
 
-1. What do you think will happen if we have set up two consumers, one in the `APJ-IN-Broker` and another in the `AMER-USEast-Broker` event broker services, both subscribed to the same topic `codejam/edi/ce/[your-sap-community-username]/dmr` and publish a message from `EU-North-Broker`?
+1. What do you think will happen if we have set up two consumers, one in the `APJ-IN-Broker` and another in the `AMER-USEast-Broker` event broker services, both subscribed to the same topic `codejam/edi/ce/[your-sap-community-display-name]/dmr` and publish a message from `EU-North-Broker`?
 2. Can you think of scenarios when you would use a Message VPN Bridge instead of DMR? What type of message would you rather exchange between event broker services using a Message VPN Bridge?
 
 ## Next

exercises/07-dynamic-message-routing/README.md

@@ -98,7 +98,7 @@ In this folder, we have a few files that we need to get familiar with:
 👉 Make a copy of the `.env.sample` file and name it `.env`. Place it in the same folder as where the `.env.sample` file resides. 
 
 - Replace the placeholder values with the credentials available in the Cluster Manager > `EU-North-Broker` > `Connect` tab > `REST` collapsible section (ensure that you select `Protocol` in the `View by` dropdown).
-- Replace the [your-sap-community-username] placeholder with your SAP Community username in the topic.
+- Replace the [your-sap-community-display-name] placeholder with your SAP Community display name in the topic.
 
 <p align = "center">
   <img alt="EU-North-Broker REST API details" src="assets/broker-details.png" width="90%"/><br/>
@@ -121,7 +121,7 @@ const ticketId = "VPHAH0OC";
 const type = "itelo.tms.ticket.v1.Ticket.Purchased.v1";
 const source = "https://tms-prod.itelo-entertainment.com/tickets";
 const datacontenttype = "application/json";
-const sapcommunityid = "[your-sap-community-username]";
+const sapcommunityid = "[your-sap-community-display-name]";
 
 var data = {
   "ID": ticketId,
@@ -145,7 +145,7 @@ var data = {
 };
 ```
 
-Here we are defining the attributes and data that will be part of the CloudEvent message. We are using the same example as before, the ticket website that generates an event after a customer purchases a ticket. Note: Remember to update the `sapcommunityid` with your SAP Community username.
+Here we are defining the attributes and data that will be part of the CloudEvent message. We are using the same example as before, the ticket website that generates an event after a customer purchases a ticket. Note: Remember to update the `sapcommunityid` with your SAP Community display name.
 
 👉 Add the following code in the `Create a CloudEvent` section:
 
@@ -185,7 +185,7 @@ If everything went well, you should see the CloudEvent message printed in the co
 > Note: If you see an error message, make sure that you have set the environment variables correctly in the `.env` file. Also, a solution for this exercise is available in the `.sap/code/08-cloudevents-sdk` folder.
 
 > [!TIP]
-> 💡 You can subscribe to the `codejam/edi/ce/[your-sap-community-username]/nodejs` topic, via the `Try Me!` page, to see the CloudEvent message being published.
+> 💡 You can subscribe to the `codejam/edi/ce/[your-sap-community-display-name]/nodejs` topic, via the `Try Me!` page, to see the CloudEvent message being published.
 
 ## Summary
 

exercises/08-cloudevents-sdk/README.md

@@ -3,4 +3,4 @@ SOLACE_REST_HOST="mr-connection-[host-id].messaging.solace.cloud"
 SOLACE_REST_PORT="9443"
 SOLACE_REST_USERNAME="solace-cloud-client"
 SOLACE_REST_PASSWORD="super-secret-password"
-TOPIC="codejam/edi/ce/[your-sap-community-username]/nodejs"
+TOPIC="codejam/edi/ce/[your-sap-community-display-name]/nodejs"

exercises/08-cloudevents-sdk/code/.env.sample

@@ -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-display-name]`, and click the **Create** button.
 
 <p align = "center">
     <img alt="Queue binding set up" src="assets/queue-binding.gif" width="100%"/><br/>
@@ -133,7 +133,7 @@ First, let's see all the objects that we've configured.
 
 Now we are ready to enable our RDP.
 
-👉 Navigate to the `Summary` tab, click on the name of the REST consumer, e.g. `POST-BPCreated-[your-sap-community-username]`, click the **Edit** button on the top right-hand side and enable the RDP by toggling the Enabled setting. Click the **Apply** button.
+👉 Navigate to the `Summary` tab, click on the name of the REST consumer, e.g. `POST-BPCreated-[your-sap-community-display-name]`, click the **Edit** button on the top right-hand side and enable the RDP by toggling the Enabled setting. Click the **Apply** button.
 
 Once we enable the RDP, if we navigate to the `Summary` tab, we should see that all the objects are in an operational state.