Updated references to Try Me page

exercises/03-cloudevents-at-sap/README.md

@@ -104,7 +104,7 @@ SAP Event Broker is the latest service released by SAP that focuses on event-dri
 
 ![CloudEvents-SeamlessIntegration.drawio.png](assets/CloudEvents-SeamlessIntegration.drawio.png "Integration between SAP S/4HANA Cloud and SAP Subscription Billing")
 
-CloudEvents are first-class citizens in SAP Event Broker, as events that are distributed between SAP cloud applications using SAP Event Broker all conform to the [CloudEvent Specification](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md "https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md")\[6\]. Evidence of this is how we can [filter SAP event subscriptions](https://help.sap.com/docs/event-broker/event-broker-service-guide/filtering-sap-event-subscriptions?locale=en-US "https://help.sap.com/docs/event-broker/event-broker-service-guide/filtering-sap-event-subscriptions?locale=en-US") by defining filters based on the CloudEvent context attributes, e.g. by filter by [type, subject, or extension context attribute](https://help.sap.com/docs/event-broker/event-broker-service-guide/event-filter-examples?locale=en-US "https://help.sap.com/docs/event-broker/event-broker-service-guide/event-filter-examples?locale=en-US"). _Note: This is an example of content-based filtering taking place in the message-oriented middleware._
+CloudEvents are first-class citizens in SAP Event Broker, as events that are distributed between SAP cloud applications using SAP Event Broker all conform to the [CloudEvent Specification](https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md "https://github.com/cloudevents/spec/blob/v1.0.2/cloudevents/spec.md")\[6\]. Evidence of this is how we can [filter SAP event subscriptions](https://help.sap.com/docs/event-broker/event-broker-service-guide/filtering-sap-event-subscriptions?locale=en-US "https://help.sap.com/docs/event-broker/event-broker-service-guide/filtering-sap-event-subscriptions?locale=en-US") by defining filters based on the CloudEvent context attributes, e.g. filter by [type, subject, or extension context attribute](https://help.sap.com/docs/event-broker/event-broker-service-guide/event-filter-examples?locale=en-US "https://help.sap.com/docs/event-broker/event-broker-service-guide/event-filter-examples?locale=en-US"). _Note: This is an example of content-based filtering taking place in the message-oriented middleware._
 
 If all your event needs are within the SAP cloud world, e.g. exchange events between SAP cloud applications and SAP BTP, this service can fulfill your needs.
 

exercises/05-explore-aem/README.md

@@ -119,14 +119,14 @@ In the ***Configuration*** tab, we can see the service type (service class), the
 
 👉 In the `EU-North-Broker` event broker service, go to the ***Try Me!*** tab of the event broker service.
 
-And last but certainly not least.... the ***Try Me*** tab. From here, you can see some event broker service metrics, e.g. the number of active connections, Guaranteed Messaging endpoints, and network usage. Most importantly, we will be able to easily interact with the event broker service via the CodePen projects embedded in the web page. Through them, we can connect to the event broker, publish messages to it and also consume messages sent to topics. This is a great way to quickly test the event broker service and exchange simple messages.
+And last but certainly not least.... the ***Try Me*** tab. From here, we will be able to access the Try Me! functionality that's available from within the event broker service. Through it, we can connect to the event broker, publish messages to it and also consume messages sent to topics. This is a great way to quickly test the event broker service and exchange simple messages.
 
 <p align = "center">
     <img alt="Event Broker - Try Me!" src="assets/event-broker-try-me.png" width="90%"/><br/>
     <i>Event Broker - Try Me!</i>
 </p>
 
-Just as a quick test, let's use the CodePen projects section to quickly establish a connection and exchange a message. We will achieve the communication scenario below.
+Just as a quick test, let's use the Try Me! functionality to quickly establish a connection and exchange a message. We will achieve the communication scenario below.
 
 <p align = "center">
     <img alt="Exchange a simple message by publishing and subscribing to the try-me topic" src="assets/codejam-exercises-Exercise5 - CodePen TryMe.png" width="70%"/><br/>
@@ -135,11 +135,12 @@ Just as a quick test, let's use the CodePen projects section to quickly establis
 
 👉 In the ***Try Me!*** tab, follow the instructions below:
 
+- Copy the credentials (`Client Username` and `Client Password`) available in the UI. These are also available in the ***Connect*** tab.
+- Click on the `Open Broker Manager` button that's within the `Try Me!` tab.
 - On the `Publisher` side, connect to the event broker service by clicking the `Connect` button.
 - On the `Subscriber` side, connect to the event broker service by clicking the `Connect` button.
   - After establishing the connection, subscribe to the topic `try-me` by clicking the `Subscribe` button.
 - Back on the `Publisher` side, publish a message to the topic `try-me` by clicking the `Publish` button.
-  - By default, the message is in binary mode, you can change it to text mode by selecting the `text` radio button. Publish the message again.
 - Check the message being consumed on the `Subscriber` side.
 
 <p align = "center">
@@ -217,7 +218,6 @@ If you finish earlier than your fellow participants, you might like to ponder th
 
 1. Which protocols can we use to connect to an event broker service in SAP Integration Suite, advanced event mesh?
 2. Can you list some of the programming languages that there are SDKs available for, which can be used for Solace Messaging?
-3. There are two `Try Me!` pages in an event broker service, there's one on the main services page (*CodePen Try Me!*) and another one within the broker manager of the service. Can you spot any differences between them?
 
 ## Next
 

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

@@ -7,9 +7,6 @@ In a previous exercise, we learned more about Event-Driven Architecture and we a
   <i>Try Me! with Queue functionality</i>
 </p>
 
-> [!IMPORTANT]
-> 🚨 You might have noticed that the `Try Me!` page in the screenshot above has more functionality than the one we used in the previous exercise. To differentiate between both of them I will refer to the one in the screenshot as "**`Advanced Try Me!`**" and to the one used in the previous exercise as "`CodePen Try Me!`". 🚨
-
 ## Topics
 
 In a previous exercise, we mentioned that a topic is a means by which a publisher classifies a message. The topic tells us what type of message we will receive if we subscribe to a specific topic. In essence, it is a string that is composed of one or more levels. Each level is separated by a forward slash (/) and the levels can be anything. This is commonly known as topic-level granularity. The granularity allows for more targeted and efficient information exchange. Instead of having a single topic for all updates on a business object in a complex system (/BusinessPartner), the system can have distinct topics for different types of updates on a business object (/BusinessPartner/Created, /BusinessPartner/Updated, /BusinessPartner/Deleted). There is no specific schema/specification on how you need to structure your topic string but you do find that patterns are established within a system. Let's get familiar with the structure of a topic by "dissecting" a real-world topic. Below we can see a topic on which an SAP S/4HANA Cloud system will publish a Business Partner message.
@@ -49,7 +46,7 @@ In the case of AEM, Queues can be durable or non-durable:
 
 ## Topic subscription
 
-As mentioned before, we can subscribe to a topic directly. A topic subscription is created after establishing a connection to AEM. We achieved this previously when we subscribed to the `try-me` topic in the `Subscriber` section of the `CodePen Try Me!`. This is not a polling mechanism, but a running connection is needed, through which AEM will send a message to the subscriber. In this case, the web page. If there is no subscriber available, the message will be missed.
+As mentioned before, we can subscribe to a topic directly. A topic subscription is created after establishing a connection to AEM. We achieved this previously when we subscribed to the `try-me` topic in the `Subscriber` section of the `Try Me!` page. This is not a polling mechanism, but a running connection is needed, through which AEM will send a message to the subscriber. In this case, the web page. If there is no subscriber available, the message will be missed.
 
 In the case of a queue, which is subscribed to topics, a message sent to a topic, will be stored in the queue until a consumer is available to process it. This is a more reliable way to ensure that messages are not lost.
 
@@ -65,35 +62,35 @@ In AEM there is a concept of a Topic Endpoint. A Topic Endpoint is a durable sto
 
 ## Publish an event
 
-We published a simple event in the previous exercise by using the `CodePen Try Me!` 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 `Advanced Try Me!`.
+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>
 </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. This will take you to a page that looks similar to the `CodePen Try Me!` page we used before but that's a bit more advanced. Here you can not just publish and subscribe to topics but we can also interact with queues in the event broker.
+👉 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.
 
 <p align = "center">
-  <img alt="Event Broker - Advanced Try Me!" src="assets/event-broker-advanced-try-me.gif" width="90%"/><br/>
-  <i>Event Broker - Advanced Try Me!</i>
+  <img alt="Event Broker - Try Me!" src="assets/event-broker-advanced-try-me.gif" width="90%"/><br/>
+  <i>Event Broker - Try Me!</i>
 </p>
 
 Now, let's use some of the concepts that we've learned so far in this exercise and publish an event on a topic that has some levels in it but first, we will need to connect to the event broker.
 
 👉 Click the `Connect` button in the Publisher section.
 
-This will fail, it is not as simple as the `CodePen Try Me!`, as we need to provide the connection details. To get the credentials needed, we will need to copy some values available to us in the event broker service `Connect` tab. Let's do that now.
+This will fail, as we need to provide the connection details. To get the credentials needed, we will need to copy some values available to us in the event broker service `Connect` tab. Let's do that now.
 
 👉 Navigate to the `EU-North-Broker` and go to the `Connect` tab. Expand the ***Solace Web Messaging*** collapsible section and copy the username, password, message VPN and secured web messaging host details.
 
-Now, we've got the connection details that we need to configure in the `Advanced Try Me!` page.
+Now, we've got the connection details that we need to configure in the `Try Me!` page.
 
-👉 Go to the `Advanced Try Me!` page, provide the connection details in the Publisher section and click the `Connect` button.
+👉 Go to the `Try Me!` page, provide the connection details in the Publisher section and click the `Connect` button.
 
 <p align = "center">
-  <img alt="Advanced Try Me! - Connect" src="assets/advanced-try-me-connect.gif" width="80%"/><br/>
-  <i>Advanced Try Me! - Connect</i>
+  <img alt="Try Me! - Connect" src="assets/advanced-try-me-connect.gif" width="80%"/><br/>
+  <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.
@@ -130,8 +127,8 @@ 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.
 
 <p align = "center">
-  <img alt="Advanced Try Me! - Publish" src="assets/advanced-try-me-publish.png" width="100%"/><br/>
-  <i>Advanced Try Me! - Publish</i>
+  <img alt="Try Me! - Publish" src="assets/advanced-try-me-publish.png" width="100%"/><br/>
+  <i>Try Me! - Publish</i>
 </p>
 
 Ok, we've published the message but it doesn't seem like much has happened. Apart from the stats being updated after sending the message, we don't have any feedback. Let's now subscribe to the topic and see if we can receive the message.
@@ -143,18 +140,18 @@ We've successfully connected the publisher section to the event broker by provid
 👉 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.
 
 <p align = "center">
-  <img alt="Advanced Try Me! - Subscribe" src="assets/advanced-try-me-subscribe.gif" width="90%"/><br/>
-  <i>Advanced Try Me! - Subscribe</i>
+  <img alt="Try Me! - Subscribe" src="assets/advanced-try-me-subscribe.gif" width="90%"/><br/>
+  <i>Try Me! - Subscribe</i>
 </p>
 
-Excellent! We were able to receive the message published. We've achieved the same scenario we completed in the previous exercise but this time we used the `Advanced Try Me!` page in the event broker service and we are now sending a CloudEvent message.
+Excellent! We were able to receive the message published. We've achieved the same scenario we completed in the previous exercise but this time we are getting used to interact with the `Try Me!` page in the event broker service and we are now sending a CloudEvent message.
 
 As explained previously, we can subscribe to a topic directly and so far we've created a topic subscription. For us to receive messages, our subscriber needs to be online and connected to AEM. But what if we want to ensure that we receive all messages published, even if our subscriber is offline? This is where Queues come into play. Let's explore how we can create a queue to receive/accumulate messages in it and finally, we will subscribe to it.
 
 ## Create a Queue
 
 > [!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 `Advanced Try Me!` page and connect again to the event broker.
+> 🚨 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/*`.
 
@@ -168,7 +165,7 @@ As explained previously, we can subscribe to a topic directly and so far we've c
 
 ## Subscribe to a Queue
 
-Now that we have created a queue, let's subscribe to it in the `Advanced Try Me!`.
+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.
 
@@ -192,7 +189,7 @@ In the examples above we've not changed the Delivery Mode. Two delivery modes ar
 > - Manage your queue:
 >   - Add new topic subscriptions to your queue.
 >   - Look at the stats of your queue.
->   - When consuming messages from the Advanced Try Me! page, check the Consumers listed in the Queue.
+>   - When consuming messages from Try Me! page, check the Consumers listed in the Queue.
 > - Stop consuming messages from the queue and see how the messages are accumulated in the queue. Check the queue stats in `Queues`.
 
 ## Clean-up
@@ -208,7 +205,7 @@ Before moving to the next exercise, let's clean up the queue we've created in th
 
 ## Summary
 
-We've covered a lot in this exercise. We've learned about topics, topic subscriptions, queues, and how to publish and subscribe to events in the event broker service using the `Advanced Try Me!` page. We've also learned about the different types of queues, durable and non-durable, and how they can be used to ensure that messages are not lost if the consumer is offline. We created a queue, subscribed to a topic and consumed messages. These are activities that we will do more in future exercises.
+We've covered a lot in this exercise. We've learned about topics, topic subscriptions, queues, and how to publish and subscribe to events in the event broker service using the `Try Me!` page. We've also learned about the different types of queues, durable and non-durable, and how they can be used to ensure that messages are not lost if the consumer is offline. We created a queue, subscribed to a topic and consumed messages. These are activities that we will do more in future exercises.
 
 ## Further Study
 

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

@@ -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 `Advanced 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-username]/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 `CodePen Try Me!` tab, 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-username]/dmr` topic.
 
 ```json
 {