- Open the Runtime Event Manager (1), then go to the Event Management Agent tab (2). Click on the 3 dots next to your Event Managment Agent (the script created one for you). Then click on Edit Connection Details (4).
- On the next screen, click on the three dots next to the PROD-solace event broker, then click on "Edit Connection Details"
- - Update the Message VPN, SEMP username and SEMP URL to point to your local broker.
Message VPN (1) is typically:default
SEMP username (2) is typically:admin
Assuming the port is typically 8080, you can form the SEMP_URL as below :
+ - Update the Message VPN (1), SEMP username (2) and SEMP URL (3) to point to your cloud broker. You will recall you saved them to a text pad in a previous step. You will use the admin password later. Once properly configured, click on Save Changes (4)
-
-
- If using Docker, use
http://host.docker.internal:8080
- - If using Podman, use
http://host.containers.internal:8080
Once properly configured, click on Save Changes (4)
-
Click on the Save & Create connection file button as shown : 
Alternative Instructions for Newman– only for those using Newm --env TESTsolace_SOLACE_SEMP_PASSWORD=${PASSWORD_ENV_VAR_2} \ --name event-management-agent solace/event-management-agent:latest -
where PASSWORD_ENV_VAR_1 is the password for your locally running broker and /absolute/path/to/your/ema/config.yml points to your downloaded EMA configuration.
where PASSWORD_ENV_VAR_1 is the password for your cloud broker and /absolute/path/to/your/ema/config.yml points to your downloaded EMA configuration.
- Confirm the connection by running:
docker logs -f event-management-agent
Alternative Instructions for Newman– only for those using Newm
Delivering innovative event-driven features to the hands of users means moving micro-integrations from development to production. That means getting the right event infrastructure in the right environment at the right time. Event Portal makes that easier, faster and more resilient.
-This code lab establishes connectivity between Event Portal, Pub Sub+ Event Broker (the runtime component) and the Event Management Agent. This in turn enables config push, which we will explore in the next Codelab. 
+Now that you've established that connectivity, you can explore how Event Portal reuses events you already have, automates event access and auto-generates code for Event Driven applications..
+
Thanks for participating in this codelab! Let us know what you thought in the Solace Community Forum! 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.
diff --git a/codelabs/ep-lifecycle/codelab.json b/codelabs/ep-lifecycle/codelab.json
index 6001ad6d..ccafa89e 100644
--- a/codelabs/ep-lifecycle/codelab.json
+++ b/codelabs/ep-lifecycle/codelab.json
@@ -3,7 +3,7 @@
"format": "html",
"prefix": "https://storage.googleapis.com",
"mainga": "UA-49880327-14",
- "updated": "2024-06-05T15:20:27Z",
+ "updated": "2024-07-02T19:47:59Z",
"id": "ep-lifecycle",
"duration": 71,
"title": "Event Portal: event-driven innovation that's faster, easier, more resilient",
@@ -11,7 +11,7 @@
"source": "main/markdown/ep-lifecycle/ep-lifecycle.md",
"theme": "",
"status": [
- "hidden"
+ "published"
],
"category": [
"eventportal"
diff --git a/codelabs/ep-lifecycle/img/7b5c691d210d1902.png b/codelabs/ep-lifecycle/img/7b5c691d210d1902.png
new file mode 100644
index 00000000..06489a0d
Binary files /dev/null and b/codelabs/ep-lifecycle/img/7b5c691d210d1902.png differ
diff --git a/codelabs/ep-lifecycle/index.html b/codelabs/ep-lifecycle/index.html
index 6498487d..c94995fa 100644
--- a/codelabs/ep-lifecycle/index.html
+++ b/codelabs/ep-lifecycle/index.html
@@ -38,11 +38,11 @@
For all sections, you'll need to:
-- Complete the Connecting Event Portal to a runtime Event Broker code lab
+- Complete the Connecting Event Portal to a runtime Event Broker code lab.
For config push and CICD integration sections, you will also need to:
-- Have a running Event Management Agent connected to an Event Broker
+- Have a running Event Management Agent connected to a cloud Event Broker (That's also covered in the Connecting Event Portal to a runtime Event Broker code lab.)
- A GitHub account. If you don't have one, you can get one free.
@@ -143,11 +143,12 @@ Assign your application to an environment/event broker
Back in the main screen, expand the Prod environment (1) again click on the three dots, and then "Add Application" (2)
The resulting popup previews the changes that will occur. Expand out the credentials (1) and queues (2) to see more details. Then click on Add (3)
-
Delivering innovative event-driven features to the hands of users means moving micro-integrations from development to production. That means getting the right event infrastructure in the right environment at the right time. Event Portal makes that easier, faster and more resilient.
-This code lab establishes connectivity between Event Portal, Pub Sub+ Event Broker (the runtime component) and the Event Management Agent. This in turn enables config push, which we will explore in the next Codelab.
Now that you've established that connectivity, you can explore how Event Portal reuses events you already have, automates event access and auto-generates code for Event Driven applications..
+
Thanks for participating in this codelab! Let us know what you thought in the Solace Community Forum! 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.
diff --git a/codelabs/ep-lifecycle/codelab.json b/codelabs/ep-lifecycle/codelab.json index 6001ad6d..ccafa89e 100644 --- a/codelabs/ep-lifecycle/codelab.json +++ b/codelabs/ep-lifecycle/codelab.json @@ -3,7 +3,7 @@ "format": "html", "prefix": "https://storage.googleapis.com", "mainga": "UA-49880327-14", - "updated": "2024-06-05T15:20:27Z", + "updated": "2024-07-02T19:47:59Z", "id": "ep-lifecycle", "duration": 71, "title": "Event Portal: event-driven innovation that's faster, easier, more resilient", @@ -11,7 +11,7 @@ "source": "main/markdown/ep-lifecycle/ep-lifecycle.md", "theme": "", "status": [ - "hidden" + "published" ], "category": [ "eventportal" diff --git a/codelabs/ep-lifecycle/img/7b5c691d210d1902.png b/codelabs/ep-lifecycle/img/7b5c691d210d1902.png new file mode 100644 index 00000000..06489a0d Binary files /dev/null and b/codelabs/ep-lifecycle/img/7b5c691d210d1902.png differ diff --git a/codelabs/ep-lifecycle/index.html b/codelabs/ep-lifecycle/index.html index 6498487d..c94995fa 100644 --- a/codelabs/ep-lifecycle/index.html +++ b/codelabs/ep-lifecycle/index.html @@ -38,11 +38,11 @@For all sections, you'll need to:
-
-
- Complete the Connecting Event Portal to a runtime Event Broker code lab +
- Complete the Connecting Event Portal to a runtime Event Broker code lab.
For config push and CICD integration sections, you will also need to:
-
-
- Have a running Event Management Agent connected to an Event Broker +
- Have a running Event Management Agent connected to a cloud Event Broker (That's also covered in the Connecting Event Portal to a runtime Event Broker code lab.)
- A GitHub account. If you don't have one, you can get one free.
Assign your application to an environment/event broker