Skip to content

Commit c89fa4c

Browse files
committed
Update links
1 parent ff81728 commit c89fa4c

2 files changed

Lines changed: 10 additions & 10 deletions

File tree

content/en/docs/marketplace/platform-supported-content/services/business-events/_index.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -32,12 +32,12 @@ To use Mendix Business Events, you will need the following:
3232

3333
* The [Mendix Business Events](https://marketplace.mendix.com/link/component/202649) service from the Mendix Marketplace
3434
* Studio Pro [9.24](/releasenotes/studio-pro/9.24/) and above
35-
* An event broker; this can be a licensed [Mendix Event Broker](#mendix-event-broker) for apps running in Mendix Cloud or the [local testing](#local-testing) broker (see [Deployment](#deployment))
35+
* An event broker; this can be a licensed [Mendix Event Broker](/appstore/services/event-broker/) for apps running in Mendix Cloud or the [local testing](/appstore/services/business-events-deployment/#local-testing) broker (see [Deployment](/appstore/services/business-events-deployment/#deployment))
3636
* [Docker](https://www.docker.com/) for local deployment
3737

3838
## Licensing {#licensing}
3939

40-
The Mendix Business Events service itself does not require a license, but it depends on an event broker to deploy to production environments. You can purchase a [Mendix Event Broker License](/appstore/services/event-broker/#event-broker-license) for a broker to be set up for you. See the [Mendix Event Broker](https://marketplace.mendix.com/link/component/202907) platform service page for more details. You can also run business events on [your own Kafka cluster](#byok).
40+
The Mendix Business Events service itself does not require a license, but it depends on an event broker to deploy to production environments. You can purchase a [Mendix Event Broker License](/appstore/services/event-broker/#event-broker-license) for a broker to be set up for you. See the [Mendix Event Broker](https://marketplace.mendix.com/link/component/202907) platform service page for more details. You can also run business events on [your own Kafka cluster](/appstore/services/business-events-deployment/#byok).
4141

4242
## Frequently Asked Questions
4343

@@ -47,7 +47,7 @@ The Mendix Business Events service itself does not require a license, but it dep
4747

4848
2. Can I publish my own events from other software directly to a Kafka topic?
4949

50-
No, that is currently not supported when using Mendix Cloud Event Broker. This can be achieved on [your own Kafka cluster](#byok).
50+
No, that is currently not supported when using Mendix Cloud Event Broker. This can be achieved on [your own Kafka cluster](/appstore/services/business-events-deployment/#byok).
5151

5252
3. Can I send related or associated objects as a single business event?
5353

@@ -59,7 +59,7 @@ The Mendix Business Events service itself does not require a license, but it dep
5959

6060
5. Are business events guaranteed to be delivered only once?
6161

62-
The [Outbox](#be-entities) will publish each business event only once. This does not prevent business logic from sending duplicate messages to the Outbox.
62+
The [Outbox](/appstore/services/business-events-deployment/#be-entities) will publish each business event only once. This does not prevent business logic from sending duplicate messages to the Outbox.
6363

6464
6. Are business events guaranteed to be delivered in the original sequence?
6565

@@ -71,21 +71,21 @@ The Mendix Business Events service itself does not require a license, but it dep
7171

7272
8. How do I configure which Kafka cluster to use?
7373

74-
During modeling, you can use the **Constants** described in the [Configuring Local Deployments](#config-local-deployment) section to configure to a local or other Kafka. This does not transfer through to runtime.
74+
During modeling, you can use the **Constants** described in the [Configuring Local Deployments](/appstore/services/business-events-configuration/#config-local-deployment) section to configure to a local or other Kafka. This does not transfer through to runtime.
7575

7676
9. How do I delete or clean up events and tasks?
7777

7878
This will be implemented in a forthcoming release. In the meantime, you could use scheduled event to clean up the events yourself (make sure the consumer doesn’t need them anymore). For the task queue, the **Task Queue Helpers**, a service linked in [Task Queue](/refguide/task-queue/), can be used.
7979

8080
10. How do I know the event was successfully published?
8181

82-
Messages are first queued within the **Outbox** for successful delivery as a business event, after which they are deleted. You can match the unique `Event Id` to your business event. Monitoring the **Outbox** entity will allow the developer to determine if there are unpublished business event entities. See the [Business Event Entities](#be-entities) for more information on the **Outbox**.
82+
Messages are first queued within the **Outbox** for successful delivery as a business event, after which they are deleted. You can match the unique `Event Id` to your business event. Monitoring the **Outbox** entity will allow the developer to determine if there are unpublished business event entities. See the [Business Event Entities](/appstore/services/business-events-deployment/#be-entities) for more information on the **Outbox**.
8383

8484
11. How do I know events are consumed successfully?
8585

86-
The flow of events are controlled by the persistence of the event to the **Consumed Business Event** entity (see [Business Event Entities](#be-entities)). The flow will not continue in the case of such a failure. They only cause for such failure would be database-related and is unlikely to occur.
86+
The flow of events are controlled by the persistence of the event to the **Consumed Business Event** entity (see [Business Event Entities](/appstore/services/business-events-deployment/#be-entities)). The flow will not continue in the case of such a failure. They only cause for such failure would be database-related and is unlikely to occur.
8787

88-
On the microflow, a log message action can be added after the start action in order to track the movement. Refer to the [Dead Letter Queue for Failed Messages](#dead-letter-queue) section for more information.
88+
On the microflow, a log message action can be added after the start action in order to track the movement. Refer to the [Dead Letter Queue for Failed Messages](/appstore/services/business-events-deployment/#dead-letter-queue) section for more information.
8989

9090
## Read More
9191

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ There is a single Kafka broker for Free Apps that your company Free Apps can con
1818

1919
Purchase a license to the Mendix Event Broker to deploy unlimited apps on production environments in Mendix Cloud. Ask your Customer Success Manager or Account Manager to reach out to purchase a license. See the [Mendix Event Broker](https://marketplace.mendix.com/link/component/202907) platform service page for more details.
2020

21-
A license for the Mendix Event Broker is available for any Mendix region, but once selected, you can only run on a single region (no multi-region support). This license is available for all customers. You can also run business events on [your own Kafka cluster](/appstore/services/business-events/#byok).
21+
A license for the Mendix Event Broker is available for any Mendix region, but once selected, you can only run on a single region (no multi-region support). This license is available for all customers. You can also run business events on [your own Kafka cluster](/appstore/services/business-events-deployment/#byok).
2222

2323
### Enabling the Mendix Event Broker Service {#enable-mx-event-broker}
2424

@@ -88,7 +88,7 @@ From the main overview page, an administrator can assign the default application
8888

8989
From here, you can manage the default access settings:
9090

91-
* **An app can access events defined in it** – enabling this setting allows newly-deployed applications to always have access to any events defined within that application (see [Creating a New Business Event Service](/appstore/services/business-events/#two-way-be-create) for more information)
91+
* **An app can access events defined in it** – enabling this setting allows newly-deployed applications to always have access to any events defined within that application (see [Creating a New Business Event Service](/appstore/services/business-events-configuration/#two-way-be-create) for more information)
9292
* **For other events, in all environments, the app can:**
9393

9494
* **Publish events it implements**

0 commit comments

Comments
 (0)