Remove docs.hazelcast.com links (#1694)

JackPGreen · web-flow · commit 060277a4880d · 2025-05-13T18:06:33.000+01:00
Within our own documentation, links should be relative to follow versions and to improve compile-time checks. Updated links to use relative links _where possible_: - in documentation pages (not code samples) - `hz-docs`, `clc` & MC docs updated, no corresponding properties for operator or tutorials Fixes: #1183
diff --git a/docs/modules/ROOT/pages/list-of-metrics.adoc b/docs/modules/ROOT/pages/list-of-metrics.adoc
@@ -14,7 +14,7 @@ metric reflects the member's local view of the cluster (consider split-brain sce
 metric, and its value in the local member is obtained by communicating
 with the master member.
 
-NOTE: If you use Management Center to export cluster-wide metrics to Prometheus, Management Center reformats the metrics to align with Prometheus best practice recommendations. See link:https://docs.hazelcast.com/management-center/latest/integrate/prometheus-monitoring[Prometheus Monitoring].
+NOTE: If you use Management Center to export cluster-wide metrics to Prometheus, Management Center reformats the metrics to align with Prometheus best practice recommendations. See xref:{page-latest-supported-mc}@management-center:integrate:prometheus-monitoring.adoc[Prometheus Monitoring].
 
 .Streaming Engine Cluster-Wide Metrics
 [%collapsible]
diff --git a/docs/modules/clients/pages/client-overview.adoc b/docs/modules/clients/pages/client-overview.adoc
@@ -23,7 +23,7 @@ Hazelcast clients must be installed locally to communicate with the server.
 
 * Language flexibility: Hazelcast offers clients in multiple programming languages, allowing you to use Hazelcast in various environments. 
 Clients are available for xref:java.adoc[Java], xref:dotnet.adoc[.NET], xref:python.adoc[Python], xref:cplusplus.adoc[{cpp}], xref:go.adoc[Go], and xref:nodejs.adoc[Node.js]
-* Independent scaling: in client/server mode, you can scale the Hazelcast cluster independently from your application. For details, see: https://docs.hazelcast.com/hazelcast/latest/deploy/choosing-a-deployment-option[Choosing an Application Topology]
+* Independent scaling: in client/server mode, you can scale the Hazelcast cluster independently from your application. For details, see: xref:deploy:choosing-a-deployment-option.adoc[Choosing an Application Topology].
 * Polyglot applications: client/server mode allows you to write polyglot applications that can all connect to the same cache cluster
 * Decoupling application from data: the application and cached data are separated, which can be beneficial for management and security purposes
 
diff --git a/docs/modules/clients/pages/hazelcast-clients.adoc b/docs/modules/clients/pages/hazelcast-clients.adoc
@@ -32,6 +32,6 @@ Alternatively, you can use xref:memcache.adoc[Memcache] to communicate directly
 
 Additional tools are available to help operate and manage Hazelcast Platform clusters:
 
-* link:https://docs.hazelcast.com/management-center/latest/getting-started/overview[Management Center]
+* xref:{page-latest-supported-mc}@management-center:getting-started:overview.adoc[Management Center]
 * link:https://docs.hazelcast.com/operator/latest/[Platform Operator]
-* link:https://docs.hazelcast.com/clc/latest/overview[Command Line Client (CLC)]
+* xref:{page-latest-supported-clc}@clc::overview.adoc[Command Line Client (CLC)]
diff --git a/docs/modules/clients/pages/java.adoc b/docs/modules/clients/pages/java.adoc
@@ -2149,7 +2149,7 @@ For <<client-cluster-routing-modes, Client cluster routing modes>>, the behaviou
 * If set to `SINGLE_MEMBER`, `LoadBalancer` is ignored
 * If set to `MULTI_MEMBER`, best effort is made to route operations to the required member. If this can't be done for any reason, operations are routed as defined by the `LoadBalancer`
 
-NOTE: If you are using smart or unisocket client operation modes, see https://docs.hazelcast.com/hazelcast/5.4/clients/java#configuring-client-load-balancer[previous documentation on this topic].
+NOTE: If you are using smart or unisocket client operation modes, see xref:clients:java.adoc#configuring-client-load-balancer[previous documentation on this topic].
 
 For example configurations, see the following code samples:
 
diff --git a/docs/modules/data-structures/pages/map-config.adoc b/docs/modules/data-structures/pages/map-config.adoc
@@ -38,7 +38,7 @@ For details on in-memory format, refer to xref:setting-data-format.adoc[].
 When a map is created, if the map name matches an entry in the `hazelcast.xml`/`hazelcast.yaml` file, the values in the matching entry are used to overwrite the initial values
 discussed in the <<map-configuration-defaults,Map Configuration Defaults>> section.
 
-Maps that do not have any configuration defined use the default configuration. If you want to set a configuration that is valid for all maps, you can name your configuration as `default`. A user-defined default configuration applies to every map that does not have a specific custom map configuration defined with the map’s name. You can also use wildcards to associate your configuration with multiple map names. See the [configuration documentation](https://docs.hazelcast.com/hazelcast/5.5/configuration/using-wildcards) for more information about wildcards.
+Maps that do not have any configuration defined use the default configuration. If you want to set a configuration that is valid for all maps, you can name your configuration as `default`. A user-defined default configuration applies to every map that does not have a specific custom map configuration defined with the map’s name. You can also use wildcards to associate your configuration with multiple map names. See the xref:configuration:using-wildcards.adoc[configuration documentation] for more information about wildcards.
 
 When a map name does not match any entry in the `hazelcast.xml`/`hazelcast.yaml` file then:
 
diff --git a/docs/modules/data-structures/pages/reliable-topic.adoc b/docs/modules/data-structures/pages/reliable-topic.adoc
@@ -15,7 +15,7 @@ data structures, e.g., collection listeners,
 
 Use Reliable Topic when you need a robust, durable messaging system that can handle high throughput without losing messages, especially in scenarios where message delivery guarantees are crucial.
 
-For more information about the metrics provided by Reliable Topic, see https://docs.hazelcast.com/hazelcast/latest/maintain-cluster/monitoring#topic-statistics[Topic Statistics].
+For more information about the metrics provided by Reliable Topic, see xref:maintain-cluster:monitoring.adoc#topic-statistics[Topic Statistics].
 
 Here is an example for a publisher using Reliable Topic:
 
diff --git a/docs/modules/integrate/pages/feature-engineering-with-feast.adoc b/docs/modules/integrate/pages/feature-engineering-with-feast.adoc
@@ -16,7 +16,7 @@ image:ROOT:feast_batch.png[Feast batch wokflow]
 
 You will need the following ready before starting the tutorial:
 
-* Hazelcast CLC (see link:https://docs.hazelcast.com/clc/latest/install-clc[Install CLC])
+* Hazelcast CLC (see xref:{page-latest-supported-clc}@clc::install-clc.adoc[Install CLC])
 * A recent version of Docker and Docker Compose
 
 To set up your project, complete the following steps:
diff --git a/docs/modules/integrate/pages/streaming-features-with-feast.adoc b/docs/modules/integrate/pages/streaming-features-with-feast.adoc
@@ -15,7 +15,7 @@ image:ROOT:feast_streaming.png[Feast streaming wokflow]
 
 You will need the following ready before starting the tutorial:
 
-* Hazelcast CLC (see link:https://docs.hazelcast.com/clc/latest/install-clc[Install CLC])
+* Hazelcast CLC (see xref:{page-latest-supported-clc}@clc::install-clc.adoc[Install CLC])
 * A recent version of Docker and Docker Compose
 
 To set up your project, complete the following steps:
diff --git a/docs/modules/maintain-cluster/pages/dynamic-config-via-rest.adoc b/docs/modules/maintain-cluster/pages/dynamic-config-via-rest.adoc
@@ -149,7 +149,7 @@ my-value
 
 This action will create the map named `my-map` which matches the dynamically added config from the previous step.
 
-You can use https://docs.hazelcast.com/management-center/latest/data-structures/map[Management Center] to verify that the map was successfully created with the expected configuration properties.
+You can use xref:{page-latest-supported-mc}@management-center:data-structures:map.adoc[Management Center] to verify that the map was successfully created with the expected configuration properties.
 
 == Step 3. Create queue with new configuration
 
@@ -187,7 +187,7 @@ item-1
 
 This step will create a queue named `my-queue` which matches the dynamically added config from the previous step.
 
-You can use https://docs.hazelcast.com/management-center/latest/data-structures/queue[Management Center] to verify that the queue was successfully created with the expected configuration properties.
+You can use xref:{page-latest-supported-mc}@management-center:data-structures:queue.adoc[Management Center] to verify that the queue was successfully created with the expected configuration properties.
 
 == Step 4 (Optional) Dynamically add new map by reloading configuration from disk
 
diff --git a/docs/modules/maintain-cluster/pages/monitoring.adoc b/docs/modules/maintain-cluster/pages/monitoring.adoc
@@ -147,7 +147,7 @@ hazelcast:
 ----
 ====
 
-See the https://docs.hazelcast.com/management-center/latest/tools/console[Management Center documentation]
+See the xref:{page-latest-supported-mc}@management-center:tools:console.adoc[Management Center documentation]
 for more information.
 
 === Managing Data Access
@@ -510,7 +510,7 @@ which frees up the heap occupied by the blob once it is consumed.
 As mentioned earlier, the client metrics are also stored in these
 blobs on the member side with timestamps assigned to them on the client side.
 
-See the https://docs.hazelcast.com/management-center/latest/metric-persistence.html[Management Center documentation]
+See the xref:{page-latest-supported-mc}@management-center::metric-persistence.adoc[Management Center documentation]
 for more information .
 
 ==== Over JMX
@@ -551,7 +551,7 @@ Prometheus enabled on port 8080
 
 The metrics are available on `\http://localhost:8080`.
 
-NOTE: You will need to configure Prometheus to scrape each member individually, manage changes from scaling and restarts, and collate the metrics from all members. If you are an Enterprise customer, you can configure Prometheus to scrape metrics from Management Center to easily collect metrics for the whole cluster. See link:https://docs.hazelcast.com/management-center/latest/integrate/prometheus-monitoring[Prometheus Monitoring]. 
+NOTE: You will need to configure Prometheus to scrape each member individually, manage changes from scaling and restarts, and collate the metrics from all members. If you are an Enterprise customer, you can configure Prometheus to scrape metrics from Management Center to easily collect metrics for the whole cluster. See xref:{page-latest-supported-mc}@management-center:integrate:prometheus-monitoring.adoc[Prometheus Monitoring]. 
 
 For a guide on how to set up Prometheus server go to the
 https://prometheus.io/docs/prometheus/latest/getting_started[Prometheus website].
@@ -2516,22 +2516,22 @@ Management Center monitors your entire Hazelcast cluster, making it much easier
 Hazelcast Management Center can expose the metrics collected from cluster members to https://prometheus.io/[Prometheus]. This
 feature can be turned on by setting the `hazelcast.mc.prometheusExporter.enabled` system property to `true`.
 
-This is an {enterprise-product-name} feature. See link:https://docs.hazelcast.com/management-center/latest/integrate/prometheus-monitoring[Prometheus Monitoring] for details.
+This is an {enterprise-product-name} feature. See link:xref:{page-latest-supported-mc}@management-center:integrate:prometheus-monitoring.adoc[Prometheus Monitoring] for details.
 
 === AppDynamics
 
 You can use the xref:{page-latest-supported-mc}@management-center:jmx:jmx.adoc[Clustered JMX] interface to integrate the <<management-center, Hazelcast Management Center>>
 with *AppDynamics*. To perform this integration, attach the AppDynamics
 Java agent to the Management Center.
 
-This is an {enterprise-product-name} feature. See link:https://docs.hazelcast.com/management-center/latest/integrate/jmx#integrating-jmx-with-appdynamics[Integrating JMX with AppDynamics] for details. 
+This is an {enterprise-product-name} feature. See xref:{page-latest-supported-mc}@management-center:integrate:jmx.adoc#integrating-jmx-with-appdynamics[Integrating JMX with AppDynamics] for details. 
 
 === New Relic
 
 You can use the xref:{page-latest-supported-mc}@management-center:jmx:jmx.adoc[Clustered JMX] interface to integrate the <<management-center, Hazelcast Management Center>>
 with New Relic. To perform this integration, attach the New Relic Java agent
 and provide an extension file that describes which metrics will be sent to New Relic.
 
-This is an {enterprise-product-name} feature. See link:https://docs.hazelcast.com/management-center/latest/integrate/jmx#integrating-jmx-with-new-relic[Integrating JMX with New Relic] for details. 
+This is an {enterprise-product-name} feature. See xref:{page-latest-supported-mc}@management-center:integrate:jmx.adoc#integrating-jmx-with-new-relic[Integrating JMX with New Relic] for details. 
 
 
diff --git a/docs/modules/maintain-cluster/pages/rolling-upgrades.adoc b/docs/modules/maintain-cluster/pages/rolling-upgrades.adoc
@@ -15,7 +15,7 @@ Before starting a rolling upgrade, consider the following best practices:
 * Ensure that <<hazelcast-members-compatibility,Upgrade Compatibility>> covers your requirements
 * If the minimum version of JDK has changed between releases, <<updated-jdk,upgrade the JDK version>> before starting a rolling upgrade
 * If you used Hazelcast Operator to deploy your cluster, refer to the link:https://docs.hazelcast.com/operator/latest/scaling-upgrading#upgrading[Operator documentation, window=_blank]
-* If using Hazelcast Management Center to trigger your rolling upgrade, upgrade Management Center before upgrading your members. For information on upgrading Management Center, refer to the link:https://docs.hazelcast.com/management-center/latest/getting-started/install[Management Center documentation, window=_blank], or if you deployed Management Center using the Hazelcast Operator, refer to the link:https://docs.hazelcast.com/operator/latest/deploy-management-center[Operator documentation, window=_blank]
+* If using Hazelcast Management Center to trigger your rolling upgrade, upgrade Management Center before upgrading your members. For information on upgrading Management Center, refer to the xref:{page-latest-supported-mc}@management-center:getting-started:install.adoc[Management Center documentation, window=_blank], or if you deployed Management Center using the Hazelcast Operator, refer to the link:https://docs.hazelcast.com/operator/latest/deploy-management-center[Operator documentation, window=_blank]
 * If using the `hz-cluster-admin` script to update your cluster, enable the `CLUSTER_WRITE` endpoints in the REST API. For further information on the {open-source-product-name} REST API, see xref:maintain-cluster:rest-api.adoc#using-the-rest-endpoint-groups[{open-source-product-name} REST API]. For further information on the {enterprise-product-name} REST API, see xref:maintain-cluster:enterprise-rest-api.adoc#dynamic-configuration-update-rest-endpoint[{enterprise-product-name} REST API]
 * Plan sufficient time for the migration and upgrade to complete, and remember that the members cannot change during the upgrade
 * Avoid issues where an automatic upgrade is triggered before the last member has been upgraded by setting a <<enabling-auto-upgrading,minimum cluster size>>
diff --git a/docs/modules/mapstore/pages/configuring-a-generic-mapstore.adoc b/docs/modules/mapstore/pages/configuring-a-generic-mapstore.adoc
@@ -6,7 +6,7 @@
 
 NOTE: The objects created in the distributed map are stored as GenericRecord. You can use the `type-name` property to store the data in a POJO (Plain Old Java Object).
 
-IMPORTANT: GenericMapStore is designed to handle GenericRecord and does not support automatic transformation between stored data (GenericRecord) and domain objects (POJOs) in embedded mode. While the `type-name` property allows specifying a https://docs.hazelcast.com/hazelcast/latest/serialization/compact-serialization[Compact type name], it does not enable domain object mapping.
+IMPORTANT: GenericMapStore is designed to handle GenericRecord and does not support automatic transformation between stored data (GenericRecord) and domain objects (POJOs) in embedded mode. While the `type-name` property allows specifying a xref:serialization:compact-serialization.adoc[Compact type name], it does not enable domain object mapping.
 
 For a list of all supported external systems, including databases, see available xref:data-connections:data-connections-configuration.adoc#connectors[data connection types].
 
diff --git a/docs/modules/migrate/pages/data-migration-tool.adoc b/docs/modules/migrate/pages/data-migration-tool.adoc
diff --git a/docs/modules/migrate/pages/dmt-command-reference.adoc b/docs/modules/migrate/pages/dmt-command-reference.adoc
