From 333c59edda89780e48f950d4501f16f6392fd63d Mon Sep 17 00:00:00 2001 From: Amara Date: Tue, 17 Dec 2024 14:23:05 -0600 Subject: [PATCH] adjust links --- .../configuration/clustering.md | 106 ------------------ .../configuration/history-cleanup.md | 2 +- .../configuration/system-configuration.md | 2 - .../migration-update/camunda-8/3.9-to-3.10.md | 2 +- optimize_sidebars.js | 1 - .../configuration/event-based-processes.md | 2 +- .../configuration/history-cleanup.md | 2 +- .../migration-update/2.7-to-3.0.md | 2 +- .../configuration/event-based-processes.md | 2 +- .../configuration/history-cleanup.md | 2 +- .../migration-update/2.7-to-3.0.md | 2 +- .../configuration/event-based-processes.md | 2 +- .../configuration/history-cleanup.md | 2 +- .../migration-update/2.7-to-3.0.md | 2 +- .../configuration/event-based-processes.md | 2 +- .../configuration/history-cleanup.md | 2 +- .../migration-update/camunda-7/2.7-to-3.0.md | 2 +- .../camunda-7/3.10-to-3.11.md | 2 +- .../migration-update/camunda-7/3.9-to-3.10.md | 2 +- .../migration-update/camunda-8/3.9-to-3.10.md | 2 +- sidebars.js | 4 - 21 files changed, 17 insertions(+), 130 deletions(-) delete mode 100644 optimize/self-managed/optimize-deployment/configuration/clustering.md diff --git a/optimize/self-managed/optimize-deployment/configuration/clustering.md b/optimize/self-managed/optimize-deployment/configuration/clustering.md deleted file mode 100644 index f6796361dd1..00000000000 --- a/optimize/self-managed/optimize-deployment/configuration/clustering.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -id: clustering -title: "Clustering" -description: "Read about how to run Optimize in a cluster." ---- - -This document describes the set up of a Camunda Optimize cluster which is mainly useful in a failover scenario, but also provides means of load-balancing in terms of distributing import and user load. - -## Configuration - -There are two configuration requirements to address in order to operate Camunda Optimize successfully in a cluster scenario. -Both of these aspects are explained in detail in the following subsections. - -### 1. Import - define importing instance - - - -Camunda 7 only - -It is important to configure the cluster in the sense that only one instance at a time is actively importing from a particular Camunda 7 engine. - -:::note Warning -If more than one instance is importing data from one and the same Camunda 7 engine concurrently, inconsistencies can occur. -::: - -The configuration property [`engines.${engineAlias}.importEnabled`](#) allows to disable the import from a particular configured engine. - -Given a simple failover cluster consisting of two instances connected to one engine, the engine configurations in the `environment-config.yaml` would look like the following: - -**Instance 1 (import from engine `default` enabled):** - -``` -... -engines: - 'camunda-bpm': - name: default - rest: 'http://localhost:8080/engine-rest' - importEnabled: true - -historyCleanup: - processDataCleanup: - enabled: true - decisionDataCleanup: - enabled: true -... -``` - -**Instance 2 (import from engine `camunda-bpm` disabled):** - -``` -... -engines: - 'camunda-bpm': - name: default - rest: 'http://localhost:8080/engine-rest' - importEnabled: false -... -``` - -:::note -The importing instance has the [history cleanup enabled](./system-configuration.md#history-cleanup-settings). It is strongly recommended all non-importing Optimize instances in the cluster do not enable history cleanup to prevent any conflicts when the [history cleanup](../history-cleanup/) is performed. -::: - -### 1.1 Import - event-based process import - - - -Camunda 7 only - -In the context of event-based process import and clustering, there are two additional configuration properties to consider carefully. - -One is specific to each configured Camunda engine [`engines.${engineAlias}.eventImportEnabled`](#) and controls whether data from this engine is imported as event source data as well for [event-based processes](#). You need to enable this on the same cluster node for which the [`engines.${engineAlias}.importEnabled`](#) configuration flag is set to `true`. - -[`eventBasedProcess.eventImport.enabled`](#) controls whether the particular cluster node processes events to create event based process instances. This allows you to run a dedicated node that performs this operation, while other nodes might just feed in Camunda activity events. - -### 2. Distributed user sessions - configure shared secret token - -If more than one Camunda Optimize instance are accessible by users for e.g. a failover scenario a shared secret token needs to be configured for all the instances. -This enables distributed sessions among all instances and users do not lose their session when being routed to another instance. - -The relevant configuration property is [`auth.token.secret`](./system-configuration.md#security) which needs to be configured in the `environment-configuration.yaml` of each Camunda Optimize instance that is part of the cluster. - -It is recommended to use a secret token with a length of at least 64 characters generated using a sufficiently good random number generator, for example the one provided by `/dev/urandom` on Linux systems. - -The following example command would generate a 64-character random string: - -``` -< /dev/urandom tr -dc A-Za-z0-9 | head -c64; echo -``` - -The corresponding `environment-config.yaml` entry would look the **same for all instances of the cluster**: - -``` -auth: - token: - secret: '' -``` - -## Example setup - -The tiniest cluster setup consisting of one importing instance from a given `default` engine and another instance where the import is disabled would look like the following: - -![Two Optimize instances](./img/Optimize-Clustering.png) - -The HTTP/S Load-Balancer would route user requests to either of the two instances, while Optimize #1 would also care about importing data from the engine to the shared -Elasticsearch instance/cluster and Optimize #2 only accesses the engine in order to authenticate and authorize users. diff --git a/optimize/self-managed/optimize-deployment/configuration/history-cleanup.md b/optimize/self-managed/optimize-deployment/configuration/history-cleanup.md index d6e95a96d2b..e7dbe7abd28 100644 --- a/optimize/self-managed/optimize-deployment/configuration/history-cleanup.md +++ b/optimize/self-managed/optimize-deployment/configuration/history-cleanup.md @@ -95,7 +95,7 @@ historyCleanup: -The age of ingested event data is determined by the [`time`](../../../apis-tools/optimize-api/event-ingestion.md#request-body) field provided for each event at the time of ingestion. +The age of ingested event data is determined by the [`time`](##request-body) field provided for each event at the time of ingestion. To enable the cleanup of event data, the `historyCleanup.ingestedEventCleanup.enabled` property needs to be set to `true`. diff --git a/optimize/self-managed/optimize-deployment/configuration/system-configuration.md b/optimize/self-managed/optimize-deployment/configuration/system-configuration.md index ee43e065d77..564826cf08b 100644 --- a/optimize/self-managed/optimize-deployment/configuration/system-configuration.md +++ b/optimize/self-managed/optimize-deployment/configuration/system-configuration.md @@ -88,8 +88,6 @@ These values control mechanisms of Optimize related security, e.g. security head | | | security.auth.token.lifeMin | 60 | Optimize uses token-based authentication to keep track of which users are logged in. Define the lifetime of the token in minutes. | | security.auth.token.secret | null | Optional secret used to sign authentication tokens, it's recommended to use at least a 64-character secret. If set to `null` a random secret will be generated with each startup of Optimize. | -| security.auth.superUserIds | [ ] | List of user IDs that are granted full permission to all collections, reports, and dashboards.

Note: For reports, these users are still required to be granted access to the corresponding process/decision definitions in Camunda 7 Admin. See [Authorization Management](#). | -| security.auth.superGroupIds | [ ] | List of group IDs that are granted full permission to all collections, reports, and dashboards. All members of the groups specified will have superuser permissions in Optimize.

Note: For reports, these groups are still required to be granted access to the corresponding process/decision definitions in Camunda 7 Admin. See [Authorization Management](#). | | security.responseHeaders.HSTS.max-age | 63072000 | HTTP Strict Transport Security (HSTS) is a web security policy mechanism which helps to protect websites against protocol downgrade attacks and cookie hijacking. This field defines the time, in seconds, that the browser should remember that this site is only to be accessed using HTTPS. If you set the number to a negative value no HSTS header is sent. | | security.responseHeaders.HSTS.includeSubDomains | true | HTTP Strict Transport Security (HSTS) is a web security policy mechanism which helps to protect websites against protocol downgrade attacks and cookie hijacking. If this optional parameter is specified, this rule applies to all the site’s subdomains as well. | | security.responseHeaders.X-XSS-Protection | 1; mode=block | This header enables the cross-site scripting (XSS) filter in your browser. Can have one of the following options:
  • `0`: Filter disabled.
  • `1`: Filter enabled. If a cross-site scripting attack is detected, in order to stop the attack, the browser will sanitize the page.
  • `1; mode=block`: Filter enabled. Rather than sanitize the page, when a XSS attack is detected, the browser will prevent rendering of the page.
  • `1; report=http://[YOURDOMAIN]/your_report_URI`: Filter enabled. The browser will sanitize the page and report the violation. This is a Chromium function utilizing CSP violation reports to send details to a URI of your choice.
| diff --git a/optimize/self-managed/optimize-deployment/migration-update/camunda-8/3.9-to-3.10.md b/optimize/self-managed/optimize-deployment/migration-update/camunda-8/3.9-to-3.10.md index 862e36c8211..89be4e8541f 100644 --- a/optimize/self-managed/optimize-deployment/migration-update/camunda-8/3.9-to-3.10.md +++ b/optimize/self-managed/optimize-deployment/migration-update/camunda-8/3.9-to-3.10.md @@ -49,7 +49,7 @@ From Optimize 3.10.4, the minimum version of Java that Optimize supports is now ### Plugins -From 3.10.4, Optimize runs with Spring Boot 3. As a result, some plugin interfaces have been updated accordingly. More specifically, the [Engine Rest Filter Plugin](./../../plugins/engine-rest-filter-plugin.md) and the [Single-Sign-On Plugin](./../../plugins/single-sign-on.md) now import jakarta dependencies. If you use these plugins, you will need to adjust your implementation accordingly. +From 3.10.4, Optimize runs with Spring Boot 3. As a result, some plugin interfaces have been updated accordingly. More specifically, the [Engine Rest Filter Plugin](#) and the [Single-Sign-On Plugin](./../../plugins/single-sign-on.md) now import jakarta dependencies. If you use these plugins, you will need to adjust your implementation accordingly. ### Logging diff --git a/optimize_sidebars.js b/optimize_sidebars.js index 9925dd55c28..ce96e9a90c3 100644 --- a/optimize_sidebars.js +++ b/optimize_sidebars.js @@ -2915,7 +2915,6 @@ module.exports = { "self-managed/optimize-deployment/configuration/history-cleanup", "self-managed/optimize-deployment/configuration/localization", "self-managed/optimize-deployment/configuration/object-variables", - "self-managed/optimize-deployment/configuration/clustering", "self-managed/optimize-deployment/configuration/multi-tenancy", "self-managed/optimize-deployment/configuration/common-problems", ], diff --git a/optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/configuration/event-based-processes.md b/optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/configuration/event-based-processes.md index bbccda648b5..30d927a052e 100644 --- a/optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/configuration/event-based-processes.md +++ b/optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/configuration/event-based-processes.md @@ -21,7 +21,7 @@ Configuration of the Optimize event based process feature. Camunda 7 only -Configuration of the Optimize [Event Ingestion REST API](../../../apis-tools/optimize-api/event-ingestion.md) for [event-based processes](#). +Configuration of the Optimize [Event Ingestion REST API](#) for [event-based processes](#). | YAML Path | Default Value | Description | | ----------------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/configuration/history-cleanup.md b/optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/configuration/history-cleanup.md index 1cf50acd8c1..3363997fc80 100644 --- a/optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/configuration/history-cleanup.md +++ b/optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/configuration/history-cleanup.md @@ -86,7 +86,7 @@ historyCleanup: ### Ingested event cleanup -The age of ingested event data is determined by the [`time`](../../../apis-tools/optimize-api/event-ingestion.md#request-body) field provided for each event at the time of ingestion. +The age of ingested event data is determined by the [`time`](##request-body) field provided for each event at the time of ingestion. To enable the cleanup of event data, the `historyCleanup.ingestedEventCleanup.enabled` property needs to be set to `true`. diff --git a/optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md b/optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md index aa3df00aabe..58477b9b4e1 100644 --- a/optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md +++ b/optimize_versioned_docs/version-3.11.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md @@ -44,7 +44,7 @@ The update should now successfully complete. ### Cannot disable import from particular engine -In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](./../configuration/clustering.md), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0. +In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](#), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0. ## Limitations diff --git a/optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/configuration/event-based-processes.md b/optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/configuration/event-based-processes.md index bf7b722bc6f..c8a0b781a7e 100644 --- a/optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/configuration/event-based-processes.md +++ b/optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/configuration/event-based-processes.md @@ -21,7 +21,7 @@ Configuration of the Optimize event-based process feature. Camunda 7 only -Configuration of the Optimize [event ingestion REST API](../../../apis-tools/optimize-api/event-ingestion.md) for [event-based processes](#). +Configuration of the Optimize [event ingestion REST API](#) for [event-based processes](#). | YAML path | Default value | Description | | ----------------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/configuration/history-cleanup.md b/optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/configuration/history-cleanup.md index bec76181dd8..62df0229dad 100644 --- a/optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/configuration/history-cleanup.md +++ b/optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/configuration/history-cleanup.md @@ -101,7 +101,7 @@ historyCleanup: -The age of ingested event data is determined by the [`time`](../../../apis-tools/optimize-api/event-ingestion.md#request-body) field provided for each event at the time of ingestion. +The age of ingested event data is determined by the [`time`](##request-body) field provided for each event at the time of ingestion. To enable the cleanup of event data, the `historyCleanup.ingestedEventCleanup.enabled` property needs to be set to `true`. diff --git a/optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md b/optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md index aa3df00aabe..58477b9b4e1 100644 --- a/optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md +++ b/optimize_versioned_docs/version-3.12.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md @@ -44,7 +44,7 @@ The update should now successfully complete. ### Cannot disable import from particular engine -In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](./../configuration/clustering.md), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0. +In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](#), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0. ## Limitations diff --git a/optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/configuration/event-based-processes.md b/optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/configuration/event-based-processes.md index bf7b722bc6f..c8a0b781a7e 100644 --- a/optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/configuration/event-based-processes.md +++ b/optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/configuration/event-based-processes.md @@ -21,7 +21,7 @@ Configuration of the Optimize event-based process feature. Camunda 7 only -Configuration of the Optimize [event ingestion REST API](../../../apis-tools/optimize-api/event-ingestion.md) for [event-based processes](#). +Configuration of the Optimize [event ingestion REST API](#) for [event-based processes](#). | YAML path | Default value | Description | | ----------------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/configuration/history-cleanup.md b/optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/configuration/history-cleanup.md index bec76181dd8..62df0229dad 100644 --- a/optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/configuration/history-cleanup.md +++ b/optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/configuration/history-cleanup.md @@ -101,7 +101,7 @@ historyCleanup: -The age of ingested event data is determined by the [`time`](../../../apis-tools/optimize-api/event-ingestion.md#request-body) field provided for each event at the time of ingestion. +The age of ingested event data is determined by the [`time`](##request-body) field provided for each event at the time of ingestion. To enable the cleanup of event data, the `historyCleanup.ingestedEventCleanup.enabled` property needs to be set to `true`. diff --git a/optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md b/optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md index aa3df00aabe..58477b9b4e1 100644 --- a/optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md +++ b/optimize_versioned_docs/version-3.13.0/self-managed/optimize-deployment/migration-update/2.7-to-3.0.md @@ -44,7 +44,7 @@ The update should now successfully complete. ### Cannot disable import from particular engine -In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](./../configuration/clustering.md), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0. +In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](#), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0. ## Limitations diff --git a/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/configuration/event-based-processes.md b/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/configuration/event-based-processes.md index bf7b722bc6f..c8a0b781a7e 100644 --- a/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/configuration/event-based-processes.md +++ b/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/configuration/event-based-processes.md @@ -21,7 +21,7 @@ Configuration of the Optimize event-based process feature. Camunda 7 only -Configuration of the Optimize [event ingestion REST API](../../../apis-tools/optimize-api/event-ingestion.md) for [event-based processes](#). +Configuration of the Optimize [event ingestion REST API](#) for [event-based processes](#). | YAML path | Default value | Description | | ----------------------------------------------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/configuration/history-cleanup.md b/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/configuration/history-cleanup.md index bec76181dd8..62df0229dad 100644 --- a/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/configuration/history-cleanup.md +++ b/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/configuration/history-cleanup.md @@ -101,7 +101,7 @@ historyCleanup: -The age of ingested event data is determined by the [`time`](../../../apis-tools/optimize-api/event-ingestion.md#request-body) field provided for each event at the time of ingestion. +The age of ingested event data is determined by the [`time`](##request-body) field provided for each event at the time of ingestion. To enable the cleanup of event data, the `historyCleanup.ingestedEventCleanup.enabled` property needs to be set to `true`. diff --git a/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-7/2.7-to-3.0.md b/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-7/2.7-to-3.0.md index 81c0db8fe39..f3372235561 100644 --- a/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-7/2.7-to-3.0.md +++ b/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-7/2.7-to-3.0.md @@ -44,7 +44,7 @@ The update should now successfully complete. ### Cannot disable import from particular engine -In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](./../../configuration/clustering.md), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0. +In 3.0.0, it is not possible to deactivate the import of a particular Optimize instance from a particular engine (via `engines.${engineAlias}.importEnabled`). In case your environment is using that feature for e.g. a [clustering setup](./.#), we recommend you to stay on Optimize 2.7.0 until the release of Optimize 3.1.0 (Scheduled for 14/07/2020) and then update straight to Optimize 3.1.0. ## Limitations diff --git a/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-7/3.10-to-3.11.md b/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-7/3.10-to-3.11.md index c455b994fba..f5611b19145 100644 --- a/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-7/3.10-to-3.11.md +++ b/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-7/3.10-to-3.11.md @@ -47,7 +47,7 @@ With this release, the minimum version of Java that Optimize supports is now Jav ### Plugins -Optimize now runs with Spring Boot 3. As a result, some plugin interfaces have been updated accordingly. More specifically, the [Engine Rest Filter Plugin](./../../plugins/engine-rest-filter-plugin.md) and the [Single-Sign-On Plugin](./../../plugins/single-sign-on.md) now import jakarta dependencies. If you use these plugins and are updating from version 3.10.3 or earlier, you will need to adjust your implementation accordingly. +Optimize now runs with Spring Boot 3. As a result, some plugin interfaces have been updated accordingly. More specifically, the [Engine Rest Filter Plugin](#) and the [Single-Sign-On Plugin](./../../plugins/single-sign-on.md) now import jakarta dependencies. If you use these plugins and are updating from version 3.10.3 or earlier, you will need to adjust your implementation accordingly. ### Logging diff --git a/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-7/3.9-to-3.10.md b/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-7/3.9-to-3.10.md index 5b203450a62..e8ded28f24a 100644 --- a/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-7/3.9-to-3.10.md +++ b/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-7/3.9-to-3.10.md @@ -40,7 +40,7 @@ From Optimize 3.10.4, the minimum version of Java that Optimize supports is now ### Plugins -From 3.10.4, Optimize runs with Spring Boot 3. As a result, some plugin interfaces have been updated accordingly. More specifically, the [Engine Rest Filter Plugin](./../../plugins/engine-rest-filter-plugin.md) and the [Single-Sign-On Plugin](./../../plugins/single-sign-on.md) now import jakarta dependencies. If you use these plugins, you will need to adjust your implementation accordingly. +From 3.10.4, Optimize runs with Spring Boot 3. As a result, some plugin interfaces have been updated accordingly. More specifically, the [Engine Rest Filter Plugin](#) and the [Single-Sign-On Plugin](./../../plugins/single-sign-on.md) now import jakarta dependencies. If you use these plugins, you will need to adjust your implementation accordingly. ### Logging diff --git a/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-8/3.9-to-3.10.md b/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-8/3.9-to-3.10.md index 862e36c8211..89be4e8541f 100644 --- a/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-8/3.9-to-3.10.md +++ b/optimize_versioned_docs/version-3.14.0/self-managed/optimize-deployment/migration-update/camunda-8/3.9-to-3.10.md @@ -49,7 +49,7 @@ From Optimize 3.10.4, the minimum version of Java that Optimize supports is now ### Plugins -From 3.10.4, Optimize runs with Spring Boot 3. As a result, some plugin interfaces have been updated accordingly. More specifically, the [Engine Rest Filter Plugin](./../../plugins/engine-rest-filter-plugin.md) and the [Single-Sign-On Plugin](./../../plugins/single-sign-on.md) now import jakarta dependencies. If you use these plugins, you will need to adjust your implementation accordingly. +From 3.10.4, Optimize runs with Spring Boot 3. As a result, some plugin interfaces have been updated accordingly. More specifically, the [Engine Rest Filter Plugin](#) and the [Single-Sign-On Plugin](./../../plugins/single-sign-on.md) now import jakarta dependencies. If you use these plugins, you will need to adjust your implementation accordingly. ### Logging diff --git a/sidebars.js b/sidebars.js index 8b38837ff95..56d9d106b4e 100644 --- a/sidebars.js +++ b/sidebars.js @@ -1219,10 +1219,6 @@ module.exports = { "Object and list variable support", "self-managed/optimize-deployment/configuration/object-variables/" ), - optimizeLink( - "Clustering", - "self-managed/optimize-deployment/configuration/clustering/" - ), optimizeLink( "Multi-tenancy", "self-managed/optimize-deployment/configuration/multi-tenancy/"