marklogic#40 Added example of reconfiguring App-Services server

examples/failover-project/build.gradle

@@ -9,4 +9,14 @@ buildscript {
 
 apply plugin: 'ml-gradle'
 
+/*
+ * The mlConfigureForestReplicas task exposes an instance of ConfigureForestReplicasCommand as the "command" attribute. 
+ * This allows us to easily modify the forestNamesAndReplicaCounts map, where each key is the name of a primary forest, 
+ * and the value of each key is the number of replicas to create on each host in the cluster (except the host that the
+ * primary forest resides on).
+ * 
+ * Note that this is usually most useful for supporting failover for MarkLogic apps such as Admin and App-Services. For
+ * failover for your own forests, you can use this approach, but you may also wish to create forest config files under
+ * src/main/ml-config/forests.
+ */
 mlConfigureForestReplicas.command.forestNamesAndReplicaCounts = [ "Security": 2, "Schemas": 1, "Meters": 1, "App-Services": 1]

examples/failover-project/src/main/ml-config/servers/app-services.xml

@@ -0,0 +1,9 @@
+<http-server-properties xmlns="http://marklogic.com/manage">
+  <server-name>App-Services</server-name>
+  <!-- By default, the App-Services server uses Documents and Modules as its content/modules databases. Keeping those and 
+    supporting failover for this server would require replicas of Documents and Modules. But if you're only really using qconsole, 
+    you can safely set the content database to App-Services and the modules-database to "filesystem" (i.e. 0), which means you 
+    only need replica forests for App-Services, which you need anyways for qconsole to work. -->
+  <content-database>App-Services</content-database>
+  <modules-database>0</modules-database>
+</http-server-properties>