Prototype for moving List procedures page to Ops Manual (neo4j#3003)

See corresponding Cypher Manual PR:

neo4j/docs-cypher#1531

---------

Co-authored-by: Reneta Popova <reneta.popova@neo4j.com>
Co-authored-by: Therese Magnusson <scout.therese@gmail.com>

Author: 3 people

modules/ROOT/content-nav.adoc

@@ -243,7 +243,7 @@
 ** xref:monitoring/connection-management.adoc[]
 ** xref:monitoring/background-jobs.adoc[]
 // ** xref:monitoring/cluster/index.adoc[]
-// *** xref:monitoring/cluster/procedures.adoc[]
+// *** xref:monitoring/cluster/procedures/built-in-procedures.adoc[]
 // *** xref:monitoring/cluster/http-endpoints.adoc[]
 
 * xref:tools/index.adoc[]
@@ -260,7 +260,10 @@
 *** xref:tools/neo4j-admin/validate-config.adoc[]
 ** xref:tools/cypher-shell.adoc[]
 
-* xref:procedures.adoc[]
+* Procedures
+** xref:procedures/call-procedures.adoc[]
+** xref:procedures/show-procedures.adoc[]
+** xref:procedures/built-in-procedures.adoc[]
 
 * xref:tutorial/index.adoc[]
 //** xref:tutorial/local-causal-cluster.adoc[]

modules/ROOT/images/call-procedure.svg

@@ -65,7 +65,7 @@ this LDAP group will fail authentication, even if their credentials are correct.
 |===
 
 All settings are defined at server startup time in the default configuration file _xref:configuration/neo4j-conf.adoc[neo4j.conf]_ or can be modified at
-runtime using xref:procedures.adoc#procedure_dbms_setConfigValue[`dbms.setConfigValue()`].
+runtime using xref:procedures/built-in-procedures.adoc#procedure_dbms_setConfigValue[`dbms.setConfigValue()`].
 
 
 [[auth-ldap-configure-provider]]

modules/ROOT/pages/authentication-authorization/ldap-integration.adoc

@@ -68,7 +68,7 @@ For example, if only four servers exist, the command fails with an error.
 Also, it fails if two servers are set up with a mode constraint of primary, and three servers are set up with a mode constraint of secondary.
 
 If `TOPOLOGY` is not specified, the database is created according to xref:configuration/configuration-settings.adoc#config_initial.dbms.default_primaries_count[`initial.dbms.default_primaries_count`] and xref:configuration/configuration-settings.adoc#config_initial.dbms.default_secondaries_count[`initial.dbms.default_secondaries_count`] specified in _neo4j.conf_.
-After cluster startup, you can overwrite these values using the xref:procedures.adoc#procedure_dbms_setDefaultAllocationNumbers[`dbms.setDefaultAllocationNumbers()`] procedure.
+After cluster startup, you can overwrite these values using the xref:procedures/built-in-procedures.adoc#procedure_dbms_setDefaultAllocationNumbers[`dbms.setDefaultAllocationNumbers()`] procedure.
 
 A `CREATE DATABASE` command allocates the database, therefore there is no requirement to run `REALLOCATE DATABASES` (described in xref:clustering/servers.adoc#_hosting_databases_on_added_servers[Hosting databases on added servers]).
 
@@ -172,9 +172,9 @@ By default, a newly created database has both read and write access.
 
 To relieve the load of a specific server(s), you can use one of the following procedures to deallocate databases, causing the databases to be removed from the server(s) under pressure:
 
-* xref:procedures.adoc#procedure_dbms_cluster_deallocateDatabaseFromServer[`dbms.cluster.deallocateDatabaseFromServer("server-name", "database-name")`]
-* xref:procedures.adoc#procedure_dbms_cluster_deallocateDatabaseFromServers[`dbms.cluster.deallocateDatabaseFromServers(["server-name1", "server-name2"\], "database-name")`]
-* xref:procedures.adoc#procedure_dbms_cluster_deallocateNumberOfDatabases[`dbms.cluster.deallocateNumberOfDatabases("server-name", number)`]
+* xref:procedures/built-in-procedures.adoc#procedure_dbms_cluster_deallocateDatabaseFromServer[`dbms.cluster.deallocateDatabaseFromServer("server-name", "database-name")`]
+* xref:procedures/built-in-procedures.adoc#procedure_dbms_cluster_deallocateDatabaseFromServers[`dbms.cluster.deallocateDatabaseFromServers(["server-name1", "server-name2"\], "database-name")`]
+* xref:procedures/built-in-procedures.adoc#procedure_dbms_cluster_deallocateNumberOfDatabases[`dbms.cluster.deallocateNumberOfDatabases("server-name", number)`]
 
 [NOTE]
 ====
@@ -227,7 +227,7 @@ To rebalance all database allocations across the cluster, for example, because y
 [[reallocate-databases-procedure]]
 === Reallocate databases using a procedure
 
-You can use the procedure xref:procedures.adoc#procedure_dbms_cluster_reallocateDatabase[`dbms.cluster.reallocateDatabase`] to rebalance a specific database across the cluster, or xref:procedures.adoc#procedure_dbms_cluster_reallocateNumberOfDatabases[`dbms.cluster.reallocateNumberOfDatabases`] to rebalance a number of database allocations across the cluster and relieve overloaded servers.
+You can use the procedure xref:procedures/built-in-procedures.adoc#procedure_dbms_cluster_reallocateDatabase[`dbms.cluster.reallocateDatabase`] to rebalance a specific database across the cluster, or xref:procedures/built-in-procedures.adoc#procedure_dbms_cluster_reallocateNumberOfDatabases[`dbms.cluster.reallocateNumberOfDatabases`] to rebalance a number of database allocations across the cluster and relieve overloaded servers.
 Note that if the cluster is already balanced, no reallocations will happen when running these procedures.
 These procedures do not require a server name and can be executed with or without a dry run.
 
@@ -267,7 +267,7 @@ This command can also be used with `DRYRUN` to preview the new allocation of dat
 [CAUTION]
 ====
 `REALLOCATE DATABASES` on a large cluster with many databases has the potential to move a lot of allocations at once, which might stress the cluster.
-Consider starting with more limited reallocations, such as xref:procedures.adoc#procedure_dbms_cluster_reallocateNumberOfDatabases[`dbms.cluster.reallocateNumberOfDatabases`] with a small number, and let the databases complete their reallocation before calling it again, until no more reallocations are necessary.
+Consider starting with more limited reallocations, such as xref:procedures/built-in-procedures.adoc#procedure_dbms_cluster_reallocateNumberOfDatabases[`dbms.cluster.reallocateNumberOfDatabases`] with a small number, and let the databases complete their reallocation before calling it again, until no more reallocations are necessary.
 ====
 
 [NOTE]
@@ -445,7 +445,7 @@ If the default database is initially created for you with a topology different t
 [[change-default-database]]
 === Change the default database
 
-You can use the procedure xref:procedures.adoc#procedure_dbms_setDefaultDatabase[`dbms.setDefaultDatabase("newDefaultDatabaseName")`] to change the default database for a DBMS.
+You can use the procedure xref:procedures/built-in-procedures.adoc#procedure_dbms_setDefaultDatabase[`dbms.setDefaultDatabase("newDefaultDatabaseName")`] to change the default database for a DBMS.
 
 . Ensure that the database to be set as default exists, otherwise create it using the command `CREATE DATABASE <database-name>`.
 . Show the name and status of the current default database by using the command `SHOW DEFAULT DATABASE`.

modules/ROOT/pages/clustering/databases.adoc

@@ -4,7 +4,7 @@
 [[monitoring-replication]]
 = Monitor replication status
 
-Neo4j 5.24 introduces the xref:procedures.adoc#procedure_dbms_cluster_statusCheck[`dbms.cluster.statusCheck()`] procedure, which can be used to monitor the ability to replicate in clustered databases.
+Neo4j 5.24 introduces the xref:procedures/built-in-procedures.adoc#procedure_dbms_cluster_statusCheck[`dbms.cluster.statusCheck()`] procedure can be used to monitor the ability to replicate in clustered databases.
 In most cases this means a clustered database is write available.
 The procedure identifies which members of a clustered database are up-to-date and can participate in successful replication.
 Therefore, it is useful in determining the fault tolerance of a clustered database.

modules/ROOT/pages/clustering/monitoring/status-check.adoc

@@ -117,11 +117,12 @@ A server in a _cordoned_ state cannot be assigned to host any newly created data
 
 This state is primarily used for <<server-error-handling, error handling>>.
 
-To transition a server from the _enabled_ to the _cordoned_ state, run the xref:procedures.adoc#procedure_dbms_cluster_cordonServer[`dbms.cluster.cordonServer()`] procedure.
+To transition a server from the _enabled_ to the _cordoned_ state, run the xref:procedures/built-in-procedures.adoc#procedure_dbms_cluster_cordonServer[`dbms.cluster.cordonServer()`] procedure.
 Keep in mind that when decreasing the number of allocations of a database, allocations on cordoned servers are removed first.
 
 A server in the _cordoned_ state can be transitioned to _deallocating_ state or back to _enabled_.
 To re-enable a server, run the `ENABLE SERVER` command.
+You can also use the xref:procedures/built-in-procedures.adoc#procedure_dbms_cluster_uncordonServer[`dbms.cluster.uncordonServer()`] procedure.
 
 You can also use the xref:procedures.adoc#procedure_dbms_cluster_uncordonServer[`dbms.cluster.uncordonServer()`] procedure.
 However, note that the procedure is deprecated in Neo4j 5.23.
@@ -146,9 +147,9 @@ Once a server is in a deallocating state, it subsequently cannot have databases
 
 However, you can deallocate databases from a server in a *reversible manner* by running one of the following procedures:
 
-* xref:procedures.adoc#procedure_dbms_cluster_deallocateDatabaseFromServer[`dbms.cluster.deallocateDatabaseFromServer("server-name", "database-name")`]
-* xref:procedures.adoc#procedure_dbms_cluster_deallocateDatabaseFromServers[`dbms.cluster.deallocateDatabaseFromServers(["server-name1", "server-name2"\], "database-name")`]
-* xref:procedures.adoc#procedure_dbms_cluster_deallocateNumberOfDatabases[`dbms.cluster.deallocateNumberOfDatabases("server-name", number)`] 
+* xref:procedures/built-in-procedures.adoc#procedure_dbms_cluster_deallocateDatabaseFromServer[`dbms.cluster.deallocateDatabaseFromServer("server-name", "database-name")`]
+* xref:procedures/built-in-procedures.adoc#procedure_dbms_cluster_deallocateDatabaseFromServers[`dbms.cluster.deallocateDatabaseFromServers(["server-name1", "server-name2"\], "database-name")`]
+* xref:procedures/built-in-procedures.adoc#procedure_dbms_cluster_deallocateNumberOfDatabases[`dbms.cluster.deallocateNumberOfDatabases("server-name", number)`] 
 
 For details, see xref:clustering/databases.adoc#deallocate-databases[Managing databases in a cluster -> Deallocate databases].
 

modules/ROOT/pages/clustering/servers.adoc

@@ -20,7 +20,7 @@ This server always only hosts those databases in `SECONDARY` mode.
 
 | xref:configuration/configuration-settings.adoc#config_initial.dbms.automatically_enable_free_servers[`initial.dbms.automatically_enable_free_servers`]
 | This setting allows for auto-enable of servers in the `FREE` state.
-After startup, it can be changed with the xref:procedures.adoc#procedure_dbms_cluster_setAutomaticallyEnableFreeServers[`dbms.cluster.setAutomaticallyEnableFreeServers`] procedure.
+After startup, it can be changed with the xref:procedures/built-in-procedures.adoc#procedure_dbms_cluster_setAutomaticallyEnableFreeServers[`dbms.cluster.setAutomaticallyEnableFreeServers`] procedure.
 
 | xref:configuration/configuration-settings.adoc#config_server.cluster.system_database_mode[`server.cluster.system_database_mode`]
 | Every cluster member hosts the `system` database.

modules/ROOT/pages/clustering/settings.adoc

@@ -69,10 +69,10 @@ Points to consider:
 
 * Any setting with the `initial` prefix is effective on the first startup of the DBMS and/or when a new server joins the cluster and has to be explicitly xref:clustering/servers.adoc#server-enabled-state[`ENABLED`].
 
-* Changing the default number of primaries and secondaries dynamically can only be done with the xref:procedures.adoc#procedure_dbms_setDefaultAllocationNumbers[`dbms.setDefaultAllocationNumbers`] procedure.
+* Changing the default number of primaries and secondaries dynamically can only be done with the xref:procedures/built-in-procedures.adoc#procedure_dbms_setDefaultAllocationNumbers[`dbms.setDefaultAllocationNumbers`] procedure.
 See xref:clustering/databases.adoc#create-database[`CREATE DATABASE`] for more information.
 
-* To view the current default settings, use the xref:procedures.adoc#procedure_dbms_showTopologyGraphConfig[`dbms.showTopologyGraphConfig`] procedure.
+* To view the current default settings, use the xref:procedures/built-in-procedures.adoc#procedure_dbms_showTopologyGraphConfig[`dbms.showTopologyGraphConfig`] procedure.
 
 
 [CAUTION]

modules/ROOT/pages/clustering/setup/deploy.adoc

@@ -42,7 +42,7 @@ Client-side routing means that the application decides which cluster server to s
 Typically, this ensures that write operations are sent to the server currently acting as the `writer` for the target database, while read operations are sent to other servers.
 
 Client-side routing is based on getting a routing table from a cluster server, and then using that information to make the routing decisions.
-Use the xref:procedures.adoc#procedure_dbms_routing_getRoutingTable[`dbms.routing.getRoutingTable()`] procedure to obtain a routing table.
+Use the xref:procedures/built-in-procedures.adoc#procedure_dbms_routing_getRoutingTable[`dbms.routing.getRoutingTable()`] procedure to obtain a routing table.
 
 A routing table contains information about the servers and their roles as `writers`, `readers`, and `routers` for a specific database.
 There is usually one `writer`, though there may be none if the database is read-only or unhealthy.

modules/ROOT/pages/clustering/setup/routing.adoc

@@ -12,7 +12,7 @@ For general information about the `SHOW` command, see the link:{neo4j-docs-base-
 To retrieve settings on a specific server, you need to directly connect to it using `bolt` scheme.
 For more information, see the link:{neo4j-docs-base-uri}/bolt/current/bolt[Bolt protocol documentation].
 
-* Configurations settings can also be listed using the xref:procedures.adoc#procedure_dbms_listConfig[`dbms.listConfig()`] procedure.
+* Configurations settings can also be listed using the xref:procedures/built-in-procedures.adoc#procedure_dbms_listConfig[`dbms.listConfig()`] procedure.
 ====
 
 [[syntax]]