Fix links to other guides are in the GlassFish 7 documentation (#24308)

* #24303 Fix broken OpenMQ links in the GF guides.
Introduce new Asciidoc variables for each OpenMQ document.
They all point to the same URL now because links to the specific 
documents contain OpenMQ version number and thus may become obsolete.
Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>

* #24303 Fix malformed link: links
Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>

* #24303 Fix links to the App development guide
Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>

* #24303 Fix link:GXXXXXX links
Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>

* #24303 Fix add-on-component-development-guide links in the GF guides.

Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>

* #24303 Fix administration-guide links in the GF guides.
Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>

* #24303 Fix application-deployment-guide links in the GF guides.
Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>

* #24303 Fix ha-administration-guide links in the GF guides.
Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>

* #24303 Fix installation-guide links in the GF guides.
Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>

* #24303 Fix reference-manual links in the GF guides.
Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>

* #24303 Fix release-notes links in the GF guides.
Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>

* #24303 Fix security-guide links in the GF guides.
Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>

docs/add-on-component-development-guide/src/main/asciidoc/adding-configuration-data.adoc

@@ -558,10 +558,10 @@ element.
 
 Creating a transaction to update configuration data enables the data to
 be updated without the need to specify a dotted name in the
-link:reference-manual/set.html#set[`set`] subcommand. You can make the transaction
+xref:reference-manual.adoc#set[`set`] subcommand. You can make the transaction
 available to system administrators in the following ways:
 
-* By adding an link:reference-manual/asadmin.html#asadmin[`asadmin`] subcommand. If you are adding
+* By adding an xref:reference-manual.adoc#asadmin[`asadmin`] subcommand. If you are adding
 an `asadmin` subcommand, include the code for the transaction in the
 body of the subcommand's `execute` method. For more information, see
 xref:extending-asadmin.adoc#extending-the-asadmin-utility[Extending the `asadmin` Utility].
@@ -646,8 +646,8 @@ import org.jvnet.hk2.config.TransactionFailure;
 
 === Dotted Names and REST URLs of Configuration Attributes
 
-The {productName} administrative subcommands link:reference-manual/get.html#get[`get`],
-link:reference-manual/list.html#list[`list`], and olink:GSRFM00226[`set`] locate a
+The {productName} administrative subcommands xref:reference-manual.adoc#get[`get`],
+xref:reference-manual.adoc#list[`list`], and xref:reference-manual.adoc#set[`set`] locate a
 configuration attribute through the dotted name of the attribute. The
 dotted name of an attribute of a configuration element is as follows:
 

docs/add-on-component-development-guide/src/main/asciidoc/adding-monitoring-capabilities.adoc

@@ -414,12 +414,12 @@ To enable system administrators to access statistics for all components
 in the same way, you must provide statistics for an add-on component by
 updating the monitorable object tree. Statistics for the add-on
 component are then available through the {productName} administrative
-commands link:reference-manual/get.html#get[`get`], olink:GSRFM00145[`list`], and
-link:reference-manual/set.html#set[`set`]. These commands locate an object in the tree
+commands xref:reference-manual.adoc#get[`get`], xref:reference-manual.adoc#list[`list`], and
+xref:reference-manual.adoc#set[`set`]. These commands locate an object in the tree
 through the object's dotted name.
 
 For more information about the tree structure of monitorable objects,
-see "link:administration-guide/monitoring.html#how-the-monitoring-tree-structure-works[How the Monitoring Tree Structure Works]" in
+see "xref:administration-guide.adoc#how-the-monitoring-tree-structure-works[How the Monitoring Tree Structure Works]" in
 {productName} Administration Guide.
 
 To make an add-on component a monitorable object, you must add the
@@ -802,8 +802,8 @@ public class TransactionManagerImpl {
 
 === Dotted Names and REST URLs for an Add-On Component's Statistics
 
-The {productName} administrative subcommands link:reference-manual/get.html#get[`get`],
-link:reference-manual/list.html#list[`list`], and olink:GSRFM00226[`set`] locate a statistic
+The {productName} administrative subcommands xref:reference-manual.adoc#get[`get`],
+xref:reference-manual.adoc#list[`list`], and xref:reference-manual.adoc#set[`set`] locate a statistic
 through the dotted name of the statistic. The dotted name of a statistic
 for an add-on component is determined from the registration of the event
 listener that defines the statistic as follows:

docs/add-on-component-development-guide/src/main/asciidoc/extending-asadmin.adoc

@@ -15,7 +15,7 @@ you to provide administrative interfaces for an add-on component that
 are consistent with the interfaces of other {productName} components.
 A user can run `asadmin` subcommands either from a command prompt or
 from a script. For more information about the `asadmin` utility, see the
-link:reference-manual/asadmin.html#asadmin[`asadmin`(1M)] man page.
+xref:reference-manual.adoc#asadmin[`asadmin`(1M)] man page.
 
 The following topics are addressed here:
 
@@ -120,7 +120,7 @@ creating, deleting, and listing HTTP listeners:
 You must also ensure that the name of your subcommand is unique.
 To obtain a complete list of the names of all `asadmin` subcommands that
 are installed, use the
-link:reference-manual/list-commands.html#list-commands[`list-commands`] subcommand.
+xref:reference-manual.adoc#list-commands[`list-commands`] subcommand.
 For a complete list of `asadmin` subcommands that are supplied in
 {productName} distributions, see the
 xref:reference-manual.adoc#GSRFM[{productName} Reference Manual].
@@ -180,7 +180,7 @@ of the subcommand.
 
 * Options control how the `asadmin` utility performs a subcommand.
 * Operands are the objects on which a subcommand acts. For example, the
-operand of the link:reference-manual/start-domain.html#start-domain[`start-domain`] subcommand is the domain
+operand of the xref:reference-manual.adoc#start-domain[`start-domain`] subcommand is the domain
 that is to be started.
 
 The following topics are addressed here:
@@ -905,7 +905,7 @@ The brand in the {productName} command-line interface (CLI) consists
 of the product name and release information that are displayed in the
 following locations:
 
-* In the string that the link:reference-manual/version.html#version[`version`] subcommand displays
+* In the string that the xref:reference-manual.adoc#version[`version`] subcommand displays
 * In each entry in the `server.log` file
 
 If you are incorporating {productName} into a new product with an

docs/add-on-component-development-guide/src/main/asciidoc/introduction.adoc

@@ -169,7 +169,7 @@ you to provide administrative interfaces for an add-on component that
 are consistent with the interfaces of other {productName} components.
 A user can run `asadmin` subcommands either from a command prompt or
 from a script. For more information about the `asadmin` utility, see the
-link:reference-manual/asadmin.html#asadmin[`asadmin`(1M)] man page.
+xref:reference-manual.adoc#asadmin[`asadmin`(1M)] man page.
 
 For more information, see xref:extending-asadmin.adoc#extending-the-asadmin-utility[Extending the
 `asadmin` Utility].
@@ -233,7 +233,7 @@ session manager extensible because you can implement a new persistence
 type without having to modify the web container code.
 
 For information about other high-availability, session persistence
-solutions, see "link:ha-administration-guide/session-persistence-and-failover.html#configuring-high-availability-session-persistence-and-failover[Configuring High Availability Session
+solutions, see "xref:ha-administration-guide.adoc#configuring-high-availability-session-persistence-and-failover[Configuring High Availability Session
 Persistence and Failover]" in {productName} High
 Availability Administration Guide.
 

docs/add-on-component-development-guide/src/main/asciidoc/preface.adoc

@@ -75,7 +75,7 @@ your system and enterprise.
 
 |xref:administration-guide.adoc#GSADG[Administration Guide]
 |Explains how to configure, monitor, and manage {productName} subsystems and components
-from the command line by using the link:reference-manual/asadmin.html#asadmin[`asadmin`(1M)] utility.
+from the command line by using the xref:reference-manual.adoc#asadmin[`asadmin`(1M)] utility.
 Instructions for performing these tasks from the Administration Console are provided
 in the Administration Console online help.
 
@@ -120,26 +120,26 @@ scalability through failover and load balancing.
 |Provides reference information in man page format for {productName} administration commands, utility
 commands, and related concepts.
 
-|link:../openmq/mq-release-notes.html#GMRLN[Message Queue Release Notes]
+|xref:{mq-release-notes-url}[Message Queue Release Notes]
 |Describes new features, compatibility issues, and existing bugs for Open Message Queue.
 
-|link:../openmq/mq-tech-over.html#GMTOV[Message Queue Technical Overview]
+|xref:{mq-tech-over-url}[Message Queue Technical Overview]
 |Provides an introduction to the technology, concepts, architecture, capabilities, and features of
 the Message Queue messaging service.
 
-|link:../openmq/mq-admin-guide.html#GMADG[Message Queue Administration Guide]
+|xref:{mq-admin-guide-url}[Message Queue Administration Guide]
 |Explains how to set up and manage a Message Queue messaging system.
 
-|link:../openmq/mq-dev-guide-jmx.html#GMJMG[Message Queue Developer's Guide for JMX Clients]
+|xref:{mq-dev-guide-jmx-url}[Message Queue Developer's Guide for JMX Clients]
 |Describes the application programming interface in Message Queue for
 programmatically configuring and monitoring Message Queue resources in
 conformance with the Java Management Extensions (JMX).
 
-|link:../openmq/mq-dev-guide-java.html#GMJVG[Message Queue Developer's Guide for Java Clients]
+|xref:{mq-dev-guide-java-url}[Message Queue Developer's Guide for Java Clients]
 |Provides information about concepts and procedures for developing Java messaging
 applications (Java clients) that work with {productName}.
 
-|link:../openmq/mq-dev-guide-c.html#GMCCG[Message Queue Developer's Guide for C Clients]
+|xref:{mq-dev-guide-c-url}[Message Queue Developer's Guide for C Clients]
 |Provides programming and reference information for developers working with
 Message Queue who want to use the C language binding to the Message
 Queue messaging service to send, receive, and process Message Queue messages.

docs/add-on-component-development-guide/src/main/asciidoc/session-persistence-modules.adoc

@@ -17,7 +17,7 @@ session manager extensible because you can implement a new persistence
 type without having to modify the web container code.
 
 For information about other high-availability, session persistence
-solutions, see "link:ha-administration-guide/session-persistence-and-failover.html#configuring-high-availability-session-persistence-and-failover[Configuring High Availability Session
+solutions, see "xref:ha-administration-guide.adoc#configuring-high-availability-session-persistence-and-failover[Configuring High Availability Session
 Persistence and Failover]" in {productName} High
 Availability Administration Guide.