RDoc-2354 Client configuration view (Server wide) v7.1

Author: Danielle9897

docs/studio/database/settings/client-configuration-per-database.mdx

@@ -11,21 +11,30 @@ import TabItem from '@theme/TabItem';
 import CodeBlock from '@theme/CodeBlock';
 import LanguageSwitcher from "@site/src/components/LanguageSwitcher";
 import LanguageContent from "@site/src/components/LanguageContent";
+import ContentFrame from '@site/src/components/ContentFrame';
+import Panel from '@site/src/components/Panel';
 
-# Client Configuration (for database)
 <Admonition type="note" title="">
 
-* You can override the [client-configuration](../../../studio/server/client-configuration.mdx) that is set server-wide __per database__:
-  
- * From the Studio - as described in this article
- * From the Client API - see [put client-configuration operation](../../../client-api/operations/server-wide/configuration/put-serverwide-client-configuration.mdx#put-client-configuration-(server-wide))
-
-* Setting the client-configuration from the studio sets the configuration on the RavenDB server.  
-  This enables administrators to dynamically control the client behavior even after it has started running.  
-  e.g. manage load balancing of client requests on the fly in response to changing system demands.
-
+* You can **override** the [server-wide client configuration](../../../studio/server/client-configuration.mdx) per database:  
+  You can do this using:  
+  * The Studio - as described in this article  
+  * The Client API - see [Put client configuration operation](../../../client-api/operations/maintenance/configuration/put-client-configuration.mdx)  
+    
+* When set from the Studio, the client configuration is stored directly on the RavenDB server  
+  and applies to any client that connects to the specific database.
+   
+* These settings override the client's own configuration,  
+  which was initially set in your application code when initializing the _DocumentStore_.  
+  This enables administrators to dynamically control client behavior, even after the client has started running.  
+  For example, adjusting load balancing behavior on the fly in response to changing system demands.
+
+* In this article:
+  * [Set the client configuration (for database)](../../todo)
+    
 </Admonition>
-## Set the client-configuration (for database)
+
+## Set the client configuration (for database)
 
 ![Figure 1. Client Configuration Per Database](./assets/client-configuration-database-1.png)
 
@@ -63,12 +72,9 @@ import LanguageContent from "@site/src/components/LanguageContent";
 
   * For a detailed explanation see: [Read Balance Behavior](../../../client-api/configuration/load-balance/read-balance-behavior.mdx).  
 
-
-
 <Admonition type="info" title="Note" id="note" href="#note">
 
 This view will be as in the above image when the general server [Client Configuration](../../../studio/server/client-configuration.mdx) is not yet defined.  
 If a general server client-configuration is defined then this view will show the __effective configuration__ for the specific database.
 
-</Admonition>
-
+</Admonition>

docs/studio/server/assets/client-configuration-1.png

@@ -11,59 +11,70 @@ import TabItem from '@theme/TabItem';
 import CodeBlock from '@theme/CodeBlock';
 import LanguageSwitcher from "@site/src/components/LanguageSwitcher";
 import LanguageContent from "@site/src/components/LanguageContent";
+import ContentFrame from '@site/src/components/ContentFrame';
+import Panel from '@site/src/components/Panel';
 
-# Client Configuration (server-wide)
 <Admonition type="note" title="">
 
-* Set the client-configuration for __all__ databases in the cluster:  
-
-  * From the Studio - as described in this article
-  
-  * From the Client API - see [put client-configuration operation](../../client-api/operations/server-wide/configuration/put-serverwide-client-configuration.mdx)
-
-* These default values can be overwritten __per database__ in [client-configuration (for database)](../../studio/database/settings/client-configuration-per-database.mdx)
-
-* Setting the client-configuration from the studio sets the configuration on the RavenDB server.  
-  This enables administrators to dynamically control the client behavior even after it has started running.  
-  e.g. manage load balancing of client requests on the fly in response to changing system demands.
+* The client configuration can be set for **ALL** databases in the cluster.  
+  You can do this using:  
+  * The Studio - as described in this article  
+  * The Client API - see [Put client configuration operation](../../client-api/operations/server-wide/configuration/put-serverwide-client-configuration.mdx)  
+    
+* When set from the Studio, the client configuration is stored directly on the RavenDB server  
+  and applies to any client that connects to any database in the cluster.
+   
+* These settings override the client's own configuration,  
+  which was initially set in your application code when initializing the _DocumentStore_.  
+  This enables administrators to dynamically control client behavior, even after the client has started running.  
+  For example, adjusting load balancing behavior on the fly in response to changing system demands.
+    
+* To override these global values and define a separate client configuration for a specific database,  
+  see: [Client configuration (for database)](../../studio/database/settings/client-configuration-per-database.mdx)    
+
+* In this article:
+  * [Set the client configuration (server-wide)](../../studio/server/client-configuration.mdx#set-the-client-configuration-server-wide)
 
 </Admonition>
-## Set the client-configuration (server-wide)
-
-![Figure 1. Client Requests Configuration](./assets/client-configuration.png)
-
-**1. Identity parts separator**  
-
-  * Changes the default **separator** for automatically generated document IDs.  
-    You can use any `char` except `|` (pipe).  
-    Default value: `/`  
-
-**2. Max number of requests per session**  
-
-  * Set this number to restrict the number of requests (***Reads*** & ***Writes***) per session in the client API.  
-    Default value: 30  
-
-**3. Use Session Context for Load Balancing**  
-
-  * Allow client sessions to select their topology by tag, 
-    so they'd be able to load-balance their requests.  
-  
-  * Optionally, select a hash seed to fix the topology that clients would use.  
-
-  * For a detailed explanation see: [Load Balance Behavior](../../client-api/configuration/load-balance/load-balance-behavior.mdx).
-
-**4. Read balance behavior**  
-
-  * Set the load-balance method that the client will use when accessing a node with ***Read*** requests.  
-    The method selected will also affect the client's decision of which node to failover to in case of issues with the ***Read*** request.  
-    Note: ***Write*** requests will always access the [preferred node](../../client-api/configuration/load-balance/overview.mdx#the-preferred-node) calculated by the client.  
-
-  * Available options are:  
-     * _None_  
-     * _Round Robin_  
-     * _Fastest Node_  
-
-  *  For a detailed explanation about each option see: [Read Balance Behavior](../../client-api/configuration/load-balance/read-balance-behavior.mdx). 
-
-
 
+<Panel heading="Set the client configuration (server-wide)">
+
+![Server-wide client configuration](./assets/client-configuration-1.png)
+
+1. Go to **Manage Server > Client Configuration**
+    
+2. **Identity parts separator**  
+   Set the **separator character** for automatically generated document IDs of type **identity**.  
+   You can use any single character except `|` (pipe).  
+   Default value: `/`  
+   This setting affects only IDs for identity documents created by the server.  
+   Learn more about identities in [Document identifier generation: Identity](../../server/kb/document-identifier-generation.mdx#strategy-identity). 
+
+3. **Maximum number of requests per session**  
+   Set this number to restrict the number of requests (***Reads*** & ***Writes***) allowed per session when using the Client API.  
+   Default value: `30`  
+
+4. **Load balance behavior**  
+    Set the Load balance method for ***Read*** & ***Write*** requests.  
+    For a detailed explanation see: [Load balance behavior](../../client-api/configuration/load-balance/load-balance-behavior.mdx).  
+    
+    Available options:  
+    * [None](../../client-api/configuration/load-balance/load-balance-behavior.mdx#none-default-option):  
+      Read requests - the node the client will target will be based on the "Read balance behavior" configuration.  
+      Write requests - will be sent to the [preferred node](../../client-api/configuration/load-balance/overview.mdx#the-preferred-node).  
+    * [Use session context](../../client-api/configuration/load-balance/load-balance-behavior.mdx#usesessioncontext):  
+      Sessions that are assigned the same context will have all their _Read_ & _Write_ requests routed to the same node.  
+      The session context is hashed from a context string (given by the client) and an optional `seed`.  
+      ![Using session context](./assets/client-configuration-2.png)
+
+5. **Read balance behavior**  
+   Set the "Read_ balance method" the client will use when accessing a node with ***Read*** requests.
+   The method selected will also affect the client's decision of which node to failover to in case of issues with the ***Read*** request.  
+   For a detailed explanation see: [Read balance behavior](../../client-api/configuration/load-balance/read-balance-behavior.mdx).  
+   
+    Available options:  
+     * [None](../../client-api/configuration/load-balance/read-balance-behavior.mdx#none-default-option)  
+     * [Round Robin](../../client-api/configuration/load-balance/read-balance-behavior.mdx#roundrobin)  
+     * [Fastest Node](../../client-api/configuration/load-balance/read-balance-behavior.mdx#fastestnode)  
+
+</Panel>