Fail-over Configuration (Primary/Secondary) - Revision history

Bppause at 18:48, 14 February 2018

2018-02-14T18:48:00Z

2018-02-14T11:50:53Z

2015-04-01T22:01:02Z

‎Configuration

2015-04-01T22:00:49Z

2015-04-01T22:00:18Z

2014-12-02T15:28:21Z

‎Introduction

2014-12-02T15:25:03Z

‎Configuration

2014-10-31T15:55:11Z

‎Configuration

2014-10-15T09:12:41Z

‎Configuration

2014-10-15T09:11:54Z

‎Configuration

@@ Line 16: / Line 16: @@
 -Dorg.rifidi.failover.failurecount=6               number of consecutive failures before secondary determines the primary has failed
-Note: The Port number (8111 in this example and default) needs to match Restlet port # on primary server (found in [[Edge_Server_Configuration]]
+Note: The Port number (8111 in this example which is also the default Restlet port) needs to match Restlet port # on primary server found in the [[Edge_Server_Configuration|Edge_Server_Configuration]]
 </pre>
 These settings will cause the server to act as a secondary node and try to connect to the primary, getting the "readers" command
 every 10 seconds. 6 failures in a row will mean the application launch
 will continue on.

@@ Line 10: / Line 10: @@
-Edge Sever Configuration required to support Failover
+Example Edge Sever Configuration required to support Failover
 <pre>
--Dorg.rifidi.failover.primary=192.168.0.12:8111 as example -if set then means its secondary if null of not set then primary
+-Dorg.rifidi.failover.primary=192.168.0.12:8111    IP and Port of the Primary Edge Server
-node
+-Dorg.rifidi.failover.frequency=10                 how often to call The Primary Server's rest ping command in seconds
-Note: The Port number (8111 in this example and default) needs to match Restlet port # on primary server (found in [[Edge_Server_Configuration]] -Dorg.rifidi.restlet.port=8111)
+-Dorg.rifidi.failover.failurecount=6               number of consecutive failures before secondary determines the primary has failed
--Dorg.rifidi.failover.frequency=10 - how often to call rest ping command in seconds
--Dorg.rifidi.failover.failurecount=6- number of consecutive failures
+Note: The Port number (8111 in this example and default) needs to match Restlet port # on primary server (found in [[Edge_Server_Configuration]]
 </pre>
 These settings will cause the server to act as a secondary node and try to connect to the primary, getting the "readers" command
 every 10 seconds. 6 failures in a row will mean the application launch
 will continue on.

@@ Line 7: / Line 7: @@
 =Configuration=
-rifidiserver.ini in windows and rifidi-server in linux/unix
+rifidiserver.ini in windows and rifidi-server in linux/unix -- A full list of Rifidi Edge configuartion parameters can be found [[Edge_Server_Configuration]]
- -- A full list of Rifidi Edge configuartion parameters can be found [[Edge_Server_Configuration]]

@@ Line 7: / Line 7: @@
 =Configuration=
-In rifidiserver.ini - - A full list of Rifidi Edge configuartion parameters can be found [[Edge_Server_Configuration]] - rifidiserver.ini in windows and rifidi-server in linux/unix
+rifidiserver.ini in windows and rifidi-server in linux/unix
 Edge Sever Configuration required to support Failover

@@ Line 7: / Line 7: @@
 =Configuration=
-In rifidiserver.ini - - A full list of Rifidi Edge configuartion parameters can be found [[Edge_Server_Configuration]]
+In rifidiserver.ini - - A full list of Rifidi Edge configuartion parameters can be found [[Edge_Server_Configuration]] - rifidiserver.ini in windows and rifidi-server in linux/unix
 Edge Sever Configuration required to support Failover

@@ Line 2: / Line 2: @@
 Starting in 3.1 Failover Configuration (Primary/Secondary) feature is available.
-This enables a Rifidi Edge server to be defined as a secondary node based on configuration described below. The secondary server will start and load the basic libraries. In the even a failure is detected based on thresholds configured the server will continue loading starting the necessary Rifidi Apps and connecting to the required sensors/readers to continue processing events.
+This enables a Rifidi Edge server to be defined as a secondary node based on configuration described below. The secondary server will start and load the basic libraries. In the event a failure is detected based on thresholds configured the server will continue to load the  necessary Rifidi Apps and connecting to the required sensors/readers to continue processing events.
 =Configuration=

@@ Line 7: / Line 7: @@
 In rifidiserver.ini - In rifidiserver.ini  - A full list of Rifidi Edge configuartion parameters can be found [[Edge_Server_Configuration]]
-JVM settings  - Full List[[Edge_Server_Configuration]]
+Edge Sever Configuration required to support Failover
 <pre>
 *-Dorg.rifidi.failover.primary=192.168.0.12:8111 as example -if set then means its secondary if null of not set then primary

@@ Line 11: / Line 11: @@
 *-Dorg.rifidi.failover.primary=192.168.0.12:8111 as example -if set then means its secondary if null of not set then primary
 node
-Note: Port number needs to match Restlet port # on primary server (found in [[Edge_Server_Configuration]] -Dorg.rifidi.restlet.port=8111)
+Note: The Port number (8111 in this example and default) needs to match Restlet port # on primary server (found in [[Edge_Server_Configuration]] -Dorg.rifidi.restlet.port=8111)
 *-Dorg.rifidi.failover.frequency=10 - how often to call rest ping command in seconds
 *-Dorg.rifidi.failover.failurecount=6- number of consecutive failures