Skip to content

Commit 1bef4b3

Browse files
committed
Review
1 parent a77e459 commit 1bef4b3

File tree

1 file changed

+26
-35
lines changed
  • content/en/docs/marketplace/platform-supported-content/services

1 file changed

+26
-35
lines changed

content/en/docs/marketplace/platform-supported-content/services/event-broker.md

Lines changed: 26 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ See [CloudEvents](https://github.com/cloudevents/spec/blob/v1.0.1/spec.md#requir
119119

120120
For HTTP Bridges, an additional HTTP header is required for authentication.
121121

122-
* **Authorization**: The value must be set as a Bearer token using the Personal Access Token (PAT) generated during bridge configuration.
122+
* **Authorization** The value must be set as a Bearer token using the Personal Access Token (PAT) generated during bridge configuration.
123123
For example: `Authorization: Bearer <your-personal-access-token>`
124124

125125
This header must be included in all HTTP requests sent to the Mendix Event Broker via the HTTP Bridge. For details on how to obtain your Bearer token, see [Using the HTTP Bridge](#using-the-http-bridge).
@@ -137,7 +137,7 @@ Technical Contacts with a license to the Mendix Event Broker can manage this fea
137137
1. Click **Create a Bridge** to create a new bridge.
138138
2. Select either an **AWS SQS** or an **HTTP** service to configure.
139139

140-
An AWS SQS bridge uses the [Amazon Simple Queue Service](https://aws.amazon.com/sqs/). The HTTP Bridge uses HTTP requests to send events from external systems to the Mendix Event Broker. The HTTP bridge is one-way: **HTTP to Event Broker**.
140+
* An AWS SQS bridge uses the [Amazon Simple Queue Service](https://aws.amazon.com/sqs/). The HTTP Bridge uses HTTP requests to send events from external systems to the Mendix Event Broker. The HTTP bridge is one-way: **HTTP to Event Broker**.
141141

142142
3. Click **Next** to continue with creating your bridge.
143143

@@ -146,15 +146,15 @@ Technical Contacts with a license to the Mendix Event Broker can manage this fea
146146

147147
### Configuring a Bridge with AWS SQS {#bridge-with-aws-sqs}
148148

149-
The creation process for AWS SQS bridges contains two further steps on the Mendix side and policies that need to be implemented on the AWS side.
149+
The creation process for AWS SQS bridges includes two further steps on the Mendix side and policies that need to be implemented on the AWS side.
150150

151151
#### Configuration Details
152152

153-
The next step of configuration is to select a [Space](#spaces), Name, and Region for the bridge to operate in.
153+
1. Select a [Space](#spaces), Name, and Region for the bridge to operate in.
154154

155155
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/event_broker_bridges_create_3_sqs.png" class="no-border" >}}
156156

157-
Click **Next** to continue the configuration.
157+
2. Click **Next** to continue the configuration.
158158

159159
#### Choose the Business Events to Integrate
160160

@@ -163,26 +163,24 @@ The user must select events from the Event Broker landscape of events to send to
163163
1. Select **Add Business Events** and search for the appropriate events.
164164
2. Select the checkbox for the event(s) you want to add, then click **Select**.
165165

166-
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/event_broker_bridges_create_4_sqs.png" class="no-border" >}}
166+
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/event_broker_bridges_create_4_sqs.png" class="no-border" width="400" >}}
167167

168-
3. Configure each event with its own SQS URL for each direction that the event will be integrated.
168+
3. Configure each event with its own SQS URL for each direction the event will be integrated.
169169

170-
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/event_broker_bridges_create_5_sqs.png" class="no-border" >}}
170+
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/event_broker_bridges_create_5_sqs.png" class="no-border" width="400" >}}
171171

172172
4. Click **Next** to continue.
173173

174174
5. Confirm the configuration with the AWS Access Policy.
175175

176-
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/event_broker_bridges_create_6_sqs.png" class="no-border" >}}
176+
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/event_broker_bridges_create_6_sqs.png" class="no-border" width="400" >}}
177177

178178
6. After all events have been configured, click **Start** to start the Mendix Event Broker Bridge. This process will take several minutes to complete. You can also choose to **Start Later**.
179179

180-
You will be taken back to the overview page.
180+
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/event_broker_bridges_overview_sqs.png" class="no-border" width="400" >}}
181181

182182
Once the Mendix Event Broker Bridge has been successfully deployed, its configuration and status can be viewed on the **Overview** page.
183183

184-
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/event_broker_bridges_overview_sqs.png" class="no-border" >}}
185-
186184
#### Configure AWS Access Policy
187185

188186
You need to configure AWS access policies for both sending and receiving messages.
@@ -231,52 +229,45 @@ Add this object to your Access Policy of the AWS SQS queue if it is receiving me
231229

232230
### Configuring a Bridge with HTTP {#bridge-with-http}
233231

234-
The creation process for HTTP bridges contains two further steps:
235-
236232
#### Configure Service
237233

238-
Configure the service by doing the following:
234+
Configure the service by filling out the following:
239235

240-
1. Select the **Event Broker Space** – the space where the bridge will operate.
241-
2. Enter the **Bridge Name** – the name you want to call the bridge.
242-
3. Select the **AWS region** - the AWS region where your bridge operates.
243-
4. Click **Next** to connect events to your bridge.
236+
* **Event Broker Space** – the space where the bridge will operate
237+
* **Bridge Name** – the name you want to call the bridge
238+
* **AWS region** – the AWS region where your bridge operates
244239

245-
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/http/event_broker_bridges_create_3_http.png" class="no-border" >}}
240+
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/http/event_broker_bridges_create_3_http.png" class="no-border" width="400" >}}
241+
242+
Click **Next** to connect events to your bridge.
246243

247244
#### Connect Events
248245

249246
Initially, you will have no business events. Choose the business events to integrate by doing the following:
250247

251-
1. Click **Add Business Events** to open a dialog displaying all events managed by the Event Broker (including Mendix app-defined and uploaded AsyncAPI events).
252-
253-
Only events that can **subscribe** are displayed, as this bridge is one-way.
254-
255-
2. Select the event(s) you want to integrate.
256-
257-
Once events are selected, the URL for the HTTP connection is automatically generated. No further configuration is required.
258-
248+
1. Click **Add Business Events** to open a dialog displaying all events managed by the Event Broker (including Mendix app-defined and uploaded AsyncAPI events). Only events that can **subscribe** are displayed, as this bridge is one-way.
249+
2. Select the event(s) you want to integrate. Once events are selected, the URL for the HTTP connection is automatically generated. No further configuration is required.
259250
3. Click **Next** to integrate the chosen business events.
260251

261-
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/http/event_broker_bridges_create_4_http.png" class="no-border" >}}
252+
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/http/event_broker_bridges_create_4_http.png" class="no-border" width="400" >}}
262253

263254
#### Confirmation
264255

265256
On the confirmation screen you can do the following:
266257

267-
* Click **Start** to the bridge immediately
268-
* Click **Start Later** to continue without starting the bridge.
258+
* Click **Start** to start the bridge immediately
259+
* Click **Start Later** to continue without starting the bridge
269260

270-
Once The HTTP Bridge has been configured, its configuration and status can be viewed on the **Overview** page.
261+
Once The HTTP Bridge has been configured, its configuration and status can be viewed on the **Overview** page.
271262

272-
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/http/event_broker_bridges_create_6_http.png" class="no-border" >}}
263+
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/http/event_broker_bridges_create_6_http.png" class="no-border" >}}
273264

274265
#### Using the HTTP Bridge {#using-the-http-bridge}
275266

276267
To run the HTTP bridge from your client, include a Bearer token in the request header.
277268

278-
1. Open the HTTP bridge details using **Options** ({{% icon name="three-dots-menu-horizontal" %}}) menu on the overview.
279-
2, Add the **Bearer token**
269+
1. Open the HTTP bridge details using **Options** ({{% icon name="three-dots-menu-horizontal" %}}) menu on the Overview page.
270+
2. Add the **Bearer token**.
280271

281272
{{< figure src="/attachments/appstore/platform-supported-content/services/event-broker/bridges/http/event_broker_bridges_create_7_http.png" class="no-border" >}}
282273

0 commit comments

Comments
 (0)