Restructure the section on how to administer composite db (#1586) (#1625)

NataliaIvakina · renetapopova · web-flow · commit cefed4aaadb5 · 2024-05-21T12:39:24.000+02:00
Co-authored-by: Reneta Popova &lt;reneta.popova@neo4j.com&gt;
diff --git a/modules/ROOT/content-nav.adoc b/modules/ROOT/content-nav.adoc
@@ -118,7 +118,9 @@
 *** xref:database-administration/aliases/remote-database-alias-configuration.adoc[]
 ** Composite databases
 *** xref:database-administration/composite-databases/concepts.adoc[]
-*** xref:database-administration/composite-databases/manage-composite-databases.adoc[]
+*** xref:database-administration/composite-databases/create-composite-databases.adoc[]
+*** xref:database-administration/composite-databases/list-composite-databases.adoc[]
+*** xref:database-administration/composite-databases/delete-composite-databases.adoc[]
 *** xref:database-administration/composite-databases/querying-composite-databases.adoc[]
 *** xref:database-administration/composite-databases/sharding-with-copy.adoc[]
 ** xref:database-administration/syntax.adoc[]
diff --git a/modules/ROOT/pages/backup-restore/copy-database.adoc b/modules/ROOT/pages/backup-restore/copy-database.adoc
@@ -13,7 +13,7 @@ However, the command will output Cypher statements, which you can run to recreat
 ====
 * `neo4j-admin database copy` preserves the node IDs (unless `--compact-node-store` is used), but the relationships get new IDs.
 * `neo4j-admin database copy` is not supported for use on the `system` database.
-* `neo4j-admin database copy` is not supported for use on xref:database-administration/composite-databases/manage-composite-databases.adoc[Composite databases].
+* `neo4j-admin database copy` is not supported for use on xref:database-administration/composite-databases/concepts.adoc[Composite databases].
 It must be run directly on the databases that are associated with that Composite database.
 * `neo4j-admin database copy` is an IOPS-intensive process.
 For more information, see <<copy-estimating-iops, Estimating the processing time>>.
diff --git a/modules/ROOT/pages/backup-restore/offline-backup.adoc b/modules/ROOT/pages/backup-restore/offline-backup.adoc
@@ -121,6 +121,6 @@ bin/neo4j-admin database dump <database> --to-path=s3://full/path/to/aws-s3-dump
 
 [NOTE]
 ====
-`neo4j-admin database dump` cannot be applied to xref:database-administration/composite-databases/manage-composite-databases.adoc[Composite databases].
+`neo4j-admin database dump` cannot be applied to xref:database-administration/composite-databases/concepts.adoc[Composite databases].
 It must be run directly on the databases that are associated with that Composite database.
 ====
diff --git a/modules/ROOT/pages/backup-restore/planning.adoc b/modules/ROOT/pages/backup-restore/planning.adoc
@@ -96,7 +96,7 @@ The recommended way to restore a database in a cluster is to xref:clustering/dat
 
 [NOTE]
 ====
-The Neo4j Admin commands `backup`, `restore`, `dump`, `load`, `copy`, and `check-consistency` are not supported for use on xref:database-administration/composite-databases/manage-composite-databases.adoc[Composite databases].
+The Neo4j Admin commands `backup`, `restore`, `dump`, `load`, `copy`, and `check-consistency` are not supported for use on xref:database-administration/composite-databases/concepts.adoc[Composite databases].
 They must be run directly on the databases that are associated with that Composite database.
 ====
 
diff --git a/modules/ROOT/pages/backup-restore/restore-dump.adoc b/modules/ROOT/pages/backup-restore/restore-dump.adoc
@@ -140,6 +140,6 @@ For more information, see xref:clustering/databases.adoc#cluster-seed[Seed a clu
 
 [NOTE]
 ====
-`neo4j-admin database load` cannot be applied to xref:database-administration/composite-databases/manage-composite-databases.adoc[Composite databases].
+`neo4j-admin database load` cannot be applied to xref:database-administration/composite-databases/concepts.adoc[Composite databases].
 It must be run directly on the databases that are associated with that Composite database.
 ====
diff --git a/modules/ROOT/pages/configuration/neo4j-conf.adoc b/modules/ROOT/pages/configuration/neo4j-conf.adoc
@@ -62,7 +62,7 @@ In Neo4j 5, the `fabric` scope is no longer available.
 All configuration settings identified by the `fabric` namespace in the `neo4j.conf` file are moved into the `system` database.
 The Cypher surface is extended to support the Fabric configuration.
 
-For more information, see xref:database-administration/composite-databases/manage-composite-databases.adoc[Composite databases].
+For more information, see xref:database-administration/composite-databases/concepts.adoc[Composite databases].
 ====
 Component::
 Component namespaces are used to group settings that affect similar systems.
diff --git a/modules/ROOT/pages/database-administration/aliases/manage-aliases-composite-databases.adoc b/modules/ROOT/pages/database-administration/aliases/manage-aliases-composite-databases.adoc
@@ -49,7 +49,7 @@ For a description of all the returned columns of this command, and for ways in w
 [[create-composite-database-alias]]
 == Create database aliases in composite databases
 
-Both local and remote database aliases can be part of a xref::database-administration/composite-databases/manage-composite-databases.adoc[composite database].
+Both local and remote database aliases can be part of a xref::database-administration/composite-databases/concepts.adoc[composite database].
 
 The database alias is made of two parts, separated by a dot: the namespace and the alias name.
 
diff --git a/modules/ROOT/pages/database-administration/aliases/manage-aliases-standard-databases.adoc b/modules/ROOT/pages/database-administration/aliases/manage-aliases-standard-databases.adoc
@@ -235,7 +235,7 @@ It is also possible to use `SKIP` and `LIMIT` to paginate the results.
 
 Database aliases can be created using `CREATE ALIAS`.
 The command supports the creation of both local and remote database aliases.
-For more information on local and remote database aliases as part of a composite database, see xref::database-administration/composite-databases/manage-composite-databases.adoc#create-composite-database-alias[Create database aliases in composite databases].
+For more information on local and remote database aliases as part of a composite database, see xref::database-administration/aliases/manage-aliases-composite-databases.adoc#create-composite-database-alias[Create database aliases in composite databases].
 
 The required privileges are described in the xref:authentication-authorization/dbms-administration.adoc#access-control-dbms-administration-alias-management[The DBMS ALIAS MANAGEMENT privileges].
 
diff --git a/modules/ROOT/pages/database-administration/composite-databases/create-composite-databases.adoc b/modules/ROOT/pages/database-administration/composite-databases/create-composite-databases.adoc
@@ -1,74 +1,23 @@
-:description: This page describes how to manage composite databases.
+:description: This page describes how to create, start, and stop composite databases.
 :page-aliases: fabric/configuration.adoc
 [role=enterprise-edition not-on-aura]
-[[composite-databases]]
-= Managing composite databases
+[[manage-composite-databases]]
+= Create, start, and stop composite databases
 
 Composite databases are managed using Cypher(R) administrative commands.
 Note that it is not possible to modify access options or database topologies for composite databases as these are inherited from the constituent databases.
 For information about modifying access options, see xref:database-administration/standard-databases/alter-databases.adoc#manage-databases-alter[Alter database access mode].
 For information about about topologies for databases, see xref:clustering/setup/deploy.adoc#cluster-example-create-databases-on-cluster[Create databases in a cluster].
-// The above two links will have to be changed when server management and access control sections are migrated from Cypher Manual.
 
-[[composite-databases-list]]
-== Listing composite databases
-
-////
-[source, cypher, role=test-setup]
-----
-CREATE COMPOSITE DATABASE `library`;
-CREATE DATABASE `sci-fi`;
-CREATE ALIAS `library`.`sci-fi` FOR DATABASE `sci-fi`;
-----
-////
-
-The `type` column returned by the `SHOW DATABASES` command will display which databases are composite databases.
-
-.Query
-[source, cypher]
-----
-SHOW DATABASES
-----
-
-.Result
-[role="queryresult"]
-----
-+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| name      | type        | aliases            | access       | address          | role      | writer | requestedStatus | currentStatus | statusMessage | default | home  | constituents       |
-+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| "library" | "composite" | []                 | "read-only"  | "localhost:7687" | NULL      | FALSE  | "online"        | "online"      | ""            | FALSE   | FALSE | ["library.sci-fi"] |
-| "neo4j"   | "standard"  | []                 | "read-write" | "localhost:7687" | "primary" | TRUE   | "online"        | "online"      | ""            | TRUE    | TRUE  | []                 |
-| "sci-fi"  | "standard"  | ["library.sci-fi"] | "read-write" | "localhost:7687" | "primary" | TRUE   | "online"        | "online"      | ""            | FALSE   | FALSE | []                 |
-| "system"  | "system"    | []                 | "read-write" | "localhost:7687" | "primary" | TRUE   | "online"        | "online"      | ""            | FALSE   | FALSE | []                 |
-+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-----
-
-For a description of all the returned column of this command, ways in which the `SHOW DATABASE` command can be filtered, and details about the privileges required for the command, see xref:database-administration/standard-databases/listing-databases.adoc#manage-databases-list[listing standard databases].
-
-For composite databases, the `constituents` column is particularly interesting as it lists the aliases that make up the composite database.
-
-.Query
-[source, cypher]
-----
-SHOW DATABASE library YIELD name, constituents
-----
-
-.Result
-[role="queryresult"]
-----
-+--------------------------------+
-| name      | constituents       |
-+--------------------------------+
-| "library" | ["library.sci-fi"] |
-+--------------------------------+
-----
+Drivers and client applications connect to composite databases just like standard databases.
+For more information, see the manuals for the different link:{neo4j-docs-base-uri}/create-applications/[Neo4j drivers and applications].
 
 [[composite-databases-create]]
 == Create a composite database
 
 Composite databases can be created using `CREATE COMPOSITE DATABASE`.
 
-Composite database names are subject to the same rules as xref:administration-databases-create-database[standard databases].
+Composite database names are subject to the same rules as xref:database-administration/standard-databases/naming-databases.adoc[standard databases].
 One difference is however that the deprecated syntax using dots without enclosing the name in backticks is not available.
 Both dots and dashes need to be enclosed within backticks when using composite databases.
 
@@ -211,23 +160,3 @@ SHOW DATABASE inventory YIELD name, requestedStatus, currentStatus
 | "inventory" | "online"        | "online"      |
 +-----------------------------------------------+
 ----
-
-[[composite-databases-delete]]
-== Delete composite databases
-
-Composite databases can be deleted using the command `DROP COMPOSITE DATABASE name`.
-This command will fail if the targeted database is not a composite database.
-
-.Query
-[source, cypher]
-----
-DROP COMPOSITE DATABASE inventory
-----
-
-It is also possible to use the shorter command `DROP DATABASE name` for composite databases, but this command will drop any database and not fail in case the targeted database is not a composite database.
-
-[[composite-databases-drivers]]
-== Drivers and applications
-
-Drivers and client applications connect to Composite databases just like standard databases.
-For more information, see the manuals for the different link:{neo4j-docs-base-uri}/create-applications/[Neo4j drivers and applications].
diff --git a/modules/ROOT/pages/database-administration/composite-databases/delete-composite-databases.adoc b/modules/ROOT/pages/database-administration/composite-databases/delete-composite-databases.adoc
@@ -0,0 +1,14 @@
+:description: This page describes how to delete composite databases.
+[role=enterprise-edition not-on-aura]
+[[composite-databases-delete]]
+= Delete composite databases
+
+You can delete composite databases using either the command `DROP COMPOSITE DATABASE name` or the more general one  `DROP DATABASE name`.
+However, keep in mind that the first command will fail if the target database is not composite, while the second one will not fail because it targets any database.
+
+.Query
+[source, cypher]
+----
+DROP COMPOSITE DATABASE inventory
+----
+
diff --git a/modules/ROOT/pages/database-administration/composite-databases/list-composite-databases.adoc b/modules/ROOT/pages/database-administration/composite-databases/list-composite-databases.adoc
@@ -0,0 +1,54 @@
+:description: This page describes how to list composite databases.
+[role=enterprise-edition not-on-aura]
+[[composite-databases-list]]
+= List composite databases
+
+////
+[source, cypher, role=test-setup]
+----
+CREATE COMPOSITE DATABASE `library`;
+CREATE DATABASE `sci-fi`;
+CREATE ALIAS `library`.`sci-fi` FOR DATABASE `sci-fi`;
+----
+////
+
+The `type` column returned by the `SHOW DATABASES` command displays which databases are composite.
+
+.Query
+[source, cypher]
+----
+SHOW DATABASES
+----
+
+.Result
+[role="queryresult"]
+----
++----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| name      | type        | aliases            | access       | address          | role      | writer | requestedStatus | currentStatus | statusMessage | default | home  | constituents       |
++----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| "library" | "composite" | []                 | "read-only"  | "localhost:7687" | NULL      | FALSE  | "online"        | "online"      | ""            | FALSE   | FALSE | ["library.sci-fi"] |
+| "neo4j"   | "standard"  | []                 | "read-write" | "localhost:7687" | "primary" | TRUE   | "online"        | "online"      | ""            | TRUE    | TRUE  | []                 |
+| "sci-fi"  | "standard"  | ["library.sci-fi"] | "read-write" | "localhost:7687" | "primary" | TRUE   | "online"        | "online"      | ""            | FALSE   | FALSE | []                 |
+| "system"  | "system"    | []                 | "read-write" | "localhost:7687" | "primary" | TRUE   | "online"        | "online"      | ""            | FALSE   | FALSE | []                 |
++----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+----
+
+For a description of all the returned columns of this command, ways in which the `SHOW DATABASE` command can be filtered, and details about the privileges required for the command, see xref:database-administration/standard-databases/listing-databases.adoc#manage-databases-list[List standard databases].
+
+For composite databases, the `constituents` column is particularly interesting as it lists the aliases that make up the composite database.
+
+.Query
+[source, cypher]
+----
+SHOW DATABASE library YIELD name, constituents
+----
+
+.Result
+[role="queryresult"]
+----
++--------------------------------+
+| name      | constituents       |
++--------------------------------+
+| "library" | ["library.sci-fi"] |
++--------------------------------+
+----
diff --git a/modules/ROOT/pages/database-administration/composite-databases/querying-composite-databases.adoc b/modules/ROOT/pages/database-administration/composite-databases/querying-composite-databases.adoc
@@ -43,7 +43,7 @@ CREATE ALIAS `cineasts`.`upcoming`
   PASSWORD 'password'
 ----
 
-For more information about composite databases and database aliases in composite databases, see xref:database-administration/composite-databases/manage-composite-databases.adoc[], and xref:database-administration/aliases/manage-aliases-composite-databases.adoc[].
+For more information about composite databases and database aliases in composite databases, see xref:database-administration/composite-databases/concepts.adoc[], and xref:database-administration/aliases/manage-aliases-composite-databases.adoc[].
 
 [[composite-databases-queries-graph-selection]]
 == Graph selection
diff --git a/modules/ROOT/pages/database-administration/index.adoc b/modules/ROOT/pages/database-administration/index.adoc
@@ -78,4 +78,4 @@ image::manage-dbs-enterprise.png[title="A multiple database Neo4j installation."
 
 A Composite database is a logical grouping of multiple graphs contained in other, standard databases.
 A Composite database defines an _execution context_ and a (limited) _transaction domain_.
-For more information, see xref:database-administration/composite-databases/manage-composite-databases.adoc[Composite databases].
+For more information, see xref:database-administration/composite-databases/concepts.adoc[Composite databases].
diff --git a/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc
@@ -34,7 +34,7 @@ For a detailed description and instructions on how to set up clustering, see xre
 Fabric technology is used to improve the setting and management of sharded and federated databases with dynamic compositions of databases.
 A new surface to administer Fabric databases, named Composite databases, is new in 5.0.
 Configuration settings have been removed and Composite databases are now administered via Cypher commands.
-For more information, see the new chapter on xref:database-administration/composite-databases/manage-composite-databases.adoc[Composite databases], which replaces the _Fabric_ chapter from previous versions.
+For more information, see the new chapter on xref:database-administration/composite-databases/concepts.adoc[Composite databases], which replaces the _Fabric_ chapter from previous versions.
 
 * `neo4j-admin` refresh.
 +
diff --git a/modules/ROOT/pages/routing-decisions.adoc b/modules/ROOT/pages/routing-decisions.adoc
@@ -23,7 +23,7 @@ Step 2: Reuse open transaction::
 * If not, then proceed to step 3.
 Step 3: Determine the type of the target database (execution context type)::
 * If the target database is a database in this DBMS, then the context type is _Internal_.
-* If the target database is a xref::database-administration/composite-databases/manage-composite-databases.adoc[Composite database], then the context type is _Composite_. +
+* If the target database is a xref::database-administration/composite-databases/concepts.adoc[Composite database], then the context type is _Composite_. +
 +
 [NOTE]
 ====
diff --git a/modules/ROOT/pages/tools/neo4j-admin/consistency-checker.adoc b/modules/ROOT/pages/tools/neo4j-admin/consistency-checker.adoc
@@ -193,6 +193,6 @@ bin/neo4j-admin database check --from-path=<directory-with-backup-or-dump> neo4j
 
 [NOTE]
 ====
-`neo4j-admin database check` cannot be applied to xref:database-administration/composite-databases/manage-composite-databases.adoc[Composite databases].
+`neo4j-admin database check` cannot be applied to xref:database-administration/composite-databases/concepts.adoc[Composite databases].
  It must be run directly on the databases that are associated with that Composite database.
 ====
diff --git a/modules/ROOT/pages/tutorial/tutorial-composite-database.adoc b/modules/ROOT/pages/tutorial/tutorial-composite-database.adoc
@@ -685,4 +685,4 @@ Then, using the returned product IDs, it queries both `db1` and `db2` *in parall
 
 You have just learned how to store and retrieve data from multiple databases using a single Cypher query.
 
-For more details on Composite databases, see xref:database-administration/composite-databases/manage-composite-databases.adoc[].
+For more details on Composite databases, see xref:database-administration/composite-databases/concepts.adoc[].
