Endeca Cluster Setup

Endeca Gives Very Easy Way by Which we can configure the Cluster, So that it may be updating Multiple Dgraphs When Indexing is Happening Successful.

I am Going to Setup the Endeca With 4 Dgraphs ( DgraphA1,DgraphA2 ) in One machine.

(Dgraph B1,Dgraph B2) in another machine. (ADgraph) in another machine.

Go to C:\Endeca\Apps\ATGen\config\script

open file AuthoringDgraphCluster.xml

Edit with ADgraph Host name and EAC port.

<!--

  ########################################################################

  # Authoring MDEX Hosts - The machines used to host all MDEX processes

  # for the 'authoring environment' MDEX cluster.

  #

 -->

 <host id="AuthoringMDEXHost" hostName="@@HOST@@" port="@@EAC_PORT@@" />  

For DgraphA1 and DgraphA2

Setting Go to 

LiveDgraphCluster.xml

by Default it is Commented other than one DgraphA1.

Edit the following with the Host Names of the Machine and  port Where EAC is running, endeca is installed as Cluster.

<!--

  ########################################################################

  # Live MDEX Hosts - The machines used to host all MDEX processes

  # for the 'live environment' MDEX cluster.

  #

 -->

 <host id="LiveMDEXHostA" hostName="@@DGRAPH_HOST1@@" port="@@EAC_PORT@@" />

 <host id="LiveMDEXHostB" hostName="@@DGRAPH_HOST2@@" port="@@EAC_PORT@@" />

 <!--

 <host id="LiveMDEXHostB" hostName="TODO" port="@@EAC_PORT@@" />

 -->

Comment out the Following.

<!--

  ########################################################################

  # Live Dgraph Cluster - The 'live environment' MDEX cluster.

  #

  -->

  <dgraph-cluster id="LiveDgraphCluster" getDataInParallel="true" enabled="true" configSnapshotDir="./data/dgraphcluster/LiveDgraphCluster/config_snapshots">

  <dgraph ref="DgraphA1" />

  <dgraph ref="DgraphA2" />

  <dgraph ref="DgraphB1" />

  <dgraph ref="DgraphB2" />

  </dgraph-cluster>

Comment out the Following.

<!--

  ########################################################################

  # Live Dgraph Process Definitions

  #

  -->

  <dgraph id="DgraphA1" host-id="LiveMDEXHostA" port="@@DGRAPH_1_PORT@@"

  post-startup-script="LiveDgraphPostStartup">

  <properties>

  <property name="restartGroup" value="1" />

  <property name="DgraphContentGroup" value="Live" />

  </properties>

  <log-dir>./logs/dgraphs/DgraphA1</log-dir>

  <input-dir>./data/dgraphs/DgraphA1/dgraph_input</input-dir>

  <update-dir>./data/dgraphs/DgraphA1/dgraph_input/updates</update-dir>

  </dgraph>

  <dgraph id="DgraphA2" host-id="LiveMDEXHostA" port="@@DGRAPH_2_PORT@@"

  post-startup-script="LiveDgraphPostStartup">

  <properties>

  <property name="restartGroup" value="2" />

  <property name="DgraphContentGroup" value="Live" />

  </properties>

  <log-dir>./logs/dgraphs/DgraphA2</log-dir>

  <input-dir>./data/dgraphs/DgraphA2/dgraph_input</input-dir>

  <update-dir>./data/dgraphs/DgraphA2/dgraph_input/updates</update-dir>

  </dgraph>

  <dgraph id="DgraphB1" host-id="LiveMDEXHostB" port="@@DGRAPH_1_PORT@@"

  post-startup-script="LiveDgraphPostStartup">

  <properties>

  <property name="restartGroup" value="1" />

  <property name="DgraphContentGroup" value="Live" />

  </properties>

  <log-dir>./logs/dgraphs/DgraphB1</log-dir>

  <input-dir>./data/dgraphs/DgraphB1/dgraph_input</input-dir>

  <update-dir>./data/dgraphs/DgraphB1/dgraph_input/updates</update-dir>

  </dgraph>

  <dgraph id="DgraphB2" host-id="LiveMDEXHostB" port="@@DGRAPH_2_PORT@@"

  post-startup-script="LiveDgraphPostStartup">

  <properties>

  <property name="restartGroup" value="2" />

  <property name="DgraphContentGroup" value="Live" />

  </properties>

  <log-dir>./logs/dgraphs/DgraphB2</log-dir>

  <input-dir>./data/dgraphs/DgraphB2/dgraph_input</input-dir>

  <update-dir>./data/dgraphs/DgraphB2/dgraph_input/updates</update-dir>

  </dgraph>

When we are defining here like this we will be getting below in the Experience Manager>EAC Admin Console.

We can start /stop using this EAC admin Console.