---
canonical: "https://safekit.eviden.com/wp-content/uploads/documents/NEDAP_AEOS_CLUSTER_SAFEKIT.pdf"
llms_index: "https://safekit.eviden.com/llms.txt"
llms_section: "Datasheets & White Papers"
topics: "Nedap Security Management: setting up a SafeKit failover cluster with AEOS and SQL"
---

# PDF Converted to Markdown

## Page 1

```
Nedap Security Management 
Setting up a SafeKit failover cluster with 
AEOS and SQL
```

## Page 2

```
Setting up a SafeKit failover cluster with AEOS & SQL 
2 
 
nedapfrance.fr 
 
Summary 
 
 About this document ................................................................................................... 4 
 Prerequisites .............................................................................................................. 6 
 SafeKit ....................................................................................................................... 7 
3.1. Servers A & B: Installation ................................ ................................ ................................ ......... 7 
3.2. Server A & B: Configuring the hosts file ................................ ................................ ................... 10 
3.3. Serveur A & B: Editing AEOS certificates................................ ................................ .................. 11 
3.4. Server A: Configuration of the failover cluster ................................ ................................ ......... 12 
3.4.1. Node addresses ................................ ................................ ................................ ............... 13 
3.4.2. nedap.safe configuration ................................ ................................ ................................  15 
3.5. Cluster validation ................................ ................................ ................................ ...................... 21 
3.5.1. Check service states ................................ ................................ ................................ ........ 21 
3.5.2. Manual failover ................................ ................................ ................................ ................ 22 
3.5.3. Server failure ................................ ................................ ................................ .................... 25 
3.6. Activation of HTTPS for the SafeKit console ................................ ................................ ............ 26 
 Configuration of client and hardware components ...................................................... 27 
4.1. AEOS Classic and Dashboard ................................ ................................ ................................ ... 27 
4.2. Virtual AEPU "client" ................................ ................................ ................................ ................ 28 
4.3. Physical AEPU ................................ ................................ ................................ ...........................  30 
4.4. Virtual AEPU "server" ................................ ................................ ................................ ............... 32 
4.5. Socket Interface - RMI ................................ ................................ ................................ ............. 37 
4.6. AEOS Capture – AEOS Cardprinter ................................ ................................ ...........................  38 
4.7. Nedap SQL import ................................ ................................ ................................ .................... 39 
4.8. Nedap SQL export ................................ ................................ ................................ ..................... 43 
4.9. AppVision ................................ ................................ ................................ ................................ .. 47 
4.10. SQL script................................ ................................ ................................ ................................ .. 52 
 Miscellaneous SafeKit ............................................................................................... 55 
5.1. Licence ................................ ................................ ................................ ................................ ...... 55 
5.2. Logs................................ ................................ ................................ ................................ ........... 56 
5.3. Backup ................................ ................................ ................................ ................................ ...... 57
```

## Page 3

```
Setting up a SafeKit failover cluster with AEOS & SQL 
3 
 
nedapfrance.fr 
5.4. More information on SafeKit ................................ ................................ ................................ ..... 57 
 Document history ...................................................................................................... 58
```

## Page 4

```
Setting up a SafeKit failover cluster with AEOS & SQL 
4 
 
nedapfrance.fr 
 About this document 
This manual presents the step-by-step installation for configuring a SafeKit failover cluster with 
AEOS and SQL Server. 
 
The SafeKit failover cluster functionality ensures high availability of one or more services as well as 
synchronous replication. 
 
The software solution allows: 
• Synchronous real-time file replication 
• Automatic restart of an application upon failure 
• Automatic reintegration of a server after failure 
 
Block diagram of the SafeKit mirror cluster: 
 
• Step 1. Real-time replication: 
Server A (PRIM) runs the AEOS and SQL application. Users are connected to a virtual IP address. Only 
modifications made by the application within files are continuously replicated across the network.  
 
 
 
Replication is synchronous without data loss in the event of a failure unlike asynchronous replication.  
 
You just need to configure the names of the directories to be replicated in SafeKit. There are no 
prerequisites on disk organization. Directories can be located on the system disk.
```

## Page 5

```
Setting up a SafeKit failover cluster with AEOS & SQL 
5 
 
nedapfrance.fr 
• Step 2. Automatic failover: 
When server A fails, SafeKit switches the virtual IP address to server B and automatically restarts the 
AEOS and SQL application. The application finds the updated replicated files on server B.  
 
The application continues its execution on server B by locally modifying its files which are no longer 
replicated to server A. 
 
 
 
The failover time is equal to the failure detection time (30 seconds by default) and the application 
restart time. 
 
• Step 3. Reintegration after failure: 
When server A recovers from a failure (server A reintegration), SafeKit automatically resynchronizes 
the files of this server from the other server. 
 
Only files modified on Server B while Server A is inactive are resynchronized.  
 
 
 
The reintegration of server A is done without stopping the execution of the AEOS and SQL application 
on server B. 
 
• Step 4. Return to normal: 
After reintegration, the files are again in mirror mode as in step A. The system is in high availability 
with the AEOS and SQL application running on server B and with real -time replication of changes to 
server A. 
 
 
 
If the administrator wants his application to run on server A as a priority, he can execute a failover 
command, either manually at a convenient time or automatically by configuration.  
 
Information source: Nedap AEOS: the simplest high availability cluster between two redundant 
servers - SafeKit
```

## Page 6

```
Setting up a SafeKit failover cluster with AEOS & SQL 
6 
 
nedapfrance.fr 
 Prerequisites 
• The configuration must be at least the following: 
• Install AEOS + SQL Server on both servers (virtual machines or physical servers)  
• The installation directories must be identical between the two servers  
• Provide disk storage of approximately 4GB for SafeKit in the system disk 
• AEOS licenses must have the “virtual IP address” cluster (mentioned in the 
documentation) 
• The license for SafeKit (without a license the software shuts down every 3 days) 
 
• Define the network mapping as below (example to adapt): 
 
Network name (hostname) IP Address Feature 
SRV-AEOS-A 192.168.1.101 (ip1) AEOS + SQL 
SRV-AEOS-B 192.168.1.102 (ip2) AEOS + SQL 
SRV-AEOS-A 192.168.1.101 SafeKit administration console  
cls.nedap.fr 192.168.1.250 (vip) Virtual IP Address in the same subnet (alias) 
 
  
vip 
 ip1 
 ip2 
SECOND 
Ready 
PRIM 
Ready 
AEOS 
+ SQL 
= 
…/folder 
Up to date 
…/folder 
Automatically 
updated 
SRV-AEOS-B 
SRV-AEOS-A
```

## Page 7

```
Setting up a SafeKit failover cluster with AEOS & SQL 
7 
 
nedapfrance.fr 
 SafeKit 
3.1.  Servers A & B: Installation 
• Start installation of the safekit_windows_x86_x_x_x_x.msi package 
• Accept the terms in the License Agreement and click on the "Install" button 
 
• At the end of the installation, select "Set console credentials and firewall rules now."  
 
• Click on "Finish" and SafeKit 
o configures Microsoft Windows Firewall for SafeKit.  
o opens a window to enter the password for the admin user of the SafeKit web 
console. Set the same password on all nodes.
```

## Page 8

```
Setting up a SafeKit failover cluster with AEOS & SQL 
8 
 
nedapfrance.fr 
 
• Copy the module “nedap.safe (get it here)” (AEOS and SQL basic configuration) to the 
C:\safekit\Application_Modules\generic\ folder. 
• Copy the license file "license.txt" to the c:\safekit\conf\ folder. 
Three licensing modes are available: 
• Without a license key, the software will shut down every 3 days 
• With a one-month temporary license key 
• With a definitive license linked to the machine (hostname and OS) 
 
• Launch the "SafeKit Web Console" from the desktop shortcut. And login with admin and the 
password previously set.
```

## Page 9

```
Setting up a SafeKit failover cluster with AEOS & SQL 
9 
 
nedapfrance.fr 
• After authentication, the administration console appears 
 
 
Important :  
• Reproduce the installation operation on server B and set the same password. 
• SafeKit configuration is only made from a single browser (for example: server A).
```

## Page 10

```
Setting up a SafeKit failover cluster with AEOS & SQL 
10 
 
nedapfrance.fr 
3.2.  Server A & B: Configuring the hosts file 
• In the absence of DNS, you must configure the local “DNS” of each machine (servers and 
client workstations) 
• Go to the C:\Windows\System32\drivers\etc\ folder, open the hosts file and add the servers 
and virtual IP 
 
  
 
Important :  
• Perform this step on both servers A & B
```

## Page 11

```
Setting up a SafeKit failover cluster with AEOS & SQL 
11 
 
nedapfrance.fr 
3.3.  Serveur A & B: Editing AEOS certificates 
• When using Nedap self-signed certificates, it is imperative to include the cluster in the DNS.  
• Launch a command prompt as administrator from the c:\aeos\utils\ folder 
 
 
 
• Run the following query: C:\AEOS\jre\bin\java -jar keystorebuilder.jar update 
"C:\AEOS\AEserver\standalone\certs\server.jks" ****** web default "srv-aeos -a srv-aeos-b 
cls.nedap.fr" 
 
 
 
Note: If you are using your own authority please do not follow this step. On the other hand, the 
update must be done via a CSR. 
 
Important:  
• Perform this step on both servers A & B
```

## Page 12

```
Setting up a SafeKit failover cluster with AEOS & SQL 
12 
 
nedapfrance.fr 
3.4.  Server A: Configuration of the failover cluster 
• Launch the "SafeKit Web Console" from the desktop shortcut. And login with admin and the 
password set during installation.
```

## Page 13

```
Setting up a SafeKit failover cluster with AEOS & SQL 
13 
 
nedapfrance.fr 
• After authentication, the administration console appears 
 
 
3.4.1. Node addresses 
• Enter IP address of Server A in "Node address" and then press Tab key to fill "Node name" 
• Click on + and do the same with Server B. 
Note: Red color indicates a connection error.
```

## Page 14

```
Setting up a SafeKit failover cluster with AEOS & SQL 
14 
 
nedapfrance.fr 
• Click on "Save and apply" to save the cluster configuration (on both servers). 
 
 
 
• Check result. 
 
  
SRV-AEOS-A 
SRV-AEOS-B 
192.168.1.101 
192.168.1.102
```

## Page 15

```
Setting up a SafeKit failover cluster with AEOS & SQL 
15 
 
nedapfrance.fr 
3.4.2. nedap.safe configuration 
• Click on "Modules configuration" tab → "New module" button → nedap.safe. And click on the 
configure icon. The console finds nedap.safe in the Application_Modules/generic/ directory on 
the server side if you dropped the module there during installation. 
 
 
• Define a module name and "Confirm" (example nedap).
```

## Page 16

```
Setting up a SafeKit failover cluster with AEOS & SQL 
16 
 
nedapfrance.fr 
• Configure module parameters.
 
• Module startup at boot: Startup type: Automatic, Startup delay: 0 
• Macros / SERVICES: MSSQLSERVER, AEOS Application Server, AEOS Lookup Server  
• Heartbeat networks: default 
• Virtual IP addresses: 192.168.1.250 (example to adapt) 
• Replicated directories: define SQL & AEOS directories (example to adapt): 
o SQL Log: C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\Log 
o SQL Data: C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA 
o AEOS Configuration: C:\AEOS\data\aemon\configurations 
• Checkers → Processes/services:  
o AEOS_appl.exe process 
o sqlservr.exe process
```

## Page 17

```
Setting up a SafeKit failover cluster with AEOS & SQL 
17 
 
nedapfrance.fr 
• Edit scripts (optional): click directly on Next step. 
o This step is optional and can be skipped in most cases, as the restart scripts are already 
pre-configured to restart services defined in the previous step. 
o So, click directly on Next step. 
o start_prim.ps1 starts all services in the order specified in the SERVICES list, while 
stop_prim.ps1 stops all services in the reverse order. 
o Additionally, start_prim.ps1 checks the startup of each service and stops the module if 
any service fails to start correctly. 
o During module configuration, the boot startup of services will automatically be set to 
‘Manual’. This ensures that services do not start automatically upon system boot, but 
instead, they will be initiated only when the module itself is started.  
 
 
• Encryption: keep the default "Enable" value
```

## Page 18

```
Setting up a SafeKit failover cluster with AEOS & SQL 
18 
 
nedapfrance.fr 
 
• Click on "Save and apply" to configure the module on both nodes. 
 
 
 
• Check result: the result must be success on both nodes.
```

## Page 19

```
Setting up a SafeKit failover cluster with AEOS & SQL 
19 
 
nedapfrance.fr 
• Go in the monitoring and start server A as primary server (server A is supposed to be the server 
with the up-to-date data).  
 
 
 
 
Note: Server B can be chosen if its data is more recent than server A. 
 
• Wait for the server to move from WAIT (orange) state to ALONE (green). 
Note: Check the server A log (by clicking on SRV-AEOS-A) if ALONE (green) is not 
reached. 
 
• Start server B.  
 
 
 
SRV-AEOS-A 
SRV-AEOS-B 
SRV-AEOS-A 
SRV-AEOS-A 
nedap 
SRV-AEOS-A 
SRV-AEOS-B 
SRV-AEOS-B 
SRV-AEOS-A 
nedap
```

## Page 20

```
Setting up a SafeKit failover cluster with AEOS & SQL 
20 
 
nedapfrance.fr 
• Server B stays in the SECOND (orange) state while resynchronizing replicated folders. 
And ends in the state SECOND (green). 
Note: Check the server B log (by clicking on SRV-AEOS-B) to see resynchronization 
progress. 
 
 
 
 
 
  
nedap 
SRV-AEOS-A 
SRV-AEOS-B
```

## Page 21

```
Setting up a SafeKit failover cluster with AEOS & SQL 
21 
 
nedapfrance.fr 
3.5.  Cluster validation 
3.5.1. Check service states 
• Initial cluster state 
 
• Windows service states: 
Service name SRV-AEOS-A SRV-AEOS-B 
AEOS Application Server Started  Stopped 
AEOS Lookup Server Started Stopped 
SQL Server (MSSQLSERVER) Started Stopped 
 
• Validate that AEOS is working on server A by connecting to the cluster URL (virtual IP) 
https://cls.nedap.fr:8443/ 
 
 
 
  
nedap 
SRV-AEOS-A 
SRV-AEOS-B
```

## Page 22

```
Setting up a SafeKit failover cluster with AEOS & SQL 
22 
 
nedapfrance.fr 
3.5.2. Manual failover 
• Stop server A from the contextual menu by clicking on Stop  
 
• Server B should go into ALONE (green) state and server A into STOP (red) state. 
 
  
SRV-AEOS-A 
SRV-AEOS-B 
SRV-AEOS-A 
SRV-AEOS-A 
nedap 
SRV-AEOS-A 
SRV-AEOS-B 
nedap
```

## Page 23

```
Setting up a SafeKit failover cluster with AEOS & SQL 
23 
 
nedapfrance.fr 
• Windows service states: 
Service name SRV-AEOS-A SRV-AEOS-B 
AEOS Application Server Stopped Started 
AEOS Lookup Server Stopped Started 
SQL Server (MSSQLSERVER) Stopped Started 
 
• Validate that AEOS is working on server B by connecting to the cluster URL (virtual IP) 
https://cls.nedap.fr:8443/
```

## Page 24

```
Setting up a SafeKit failover cluster with AEOS & SQL 
24 
 
nedapfrance.fr 
• If all the tests are correct, start server A using its contextual menu.  
  
 
• Server A stays in the SECOND (orange) state while resynchronizing replicated folders. And 
ends in the state SECOND (green). The cluster is then operational again. 
 
  
SRV-AEOS-A 
SRV-AEOS-B 
SRV-AEOS-A 
SRV-AEOS-A 
nedap 
SRV-AEOS-A 
SRV-AEOS-B 
nedap
```

## Page 25

```
Setting up a SafeKit failover cluster with AEOS & SQL 
25 
 
nedapfrance.fr 
3.5.3. Server failure 
• Start the console on server B. Before the outage, the initial status of the servers is: 
 
• Server A suffered a power outage (for example), server B takes over automatically without 
user action. 
 
• Windows service states: 
Service name SRV-AEOS-A SRV-AEOS-B 
AEOS Application Server Hardware failure Started 
AEOS Lookup Server Hardware failure Started 
SQL Server (MSSQLSERVER) Hardware failure Started 
 
  
SRV-AEOS-A 
SRV-AEOS-B 
nedap 
SRV-AEOS-B 
nedap
```

## Page 26

```
Setting up a SafeKit failover cluster with AEOS & SQL 
26 
 
nedapfrance.fr 
• Validate that AEOS is working on server B by connecting to the cluster URL (virtual IP) 
https://cls.nedap.fr:8443/ 
 
 
 
• Following the reboot of server A, server A is automatically reconnected and synchronized. It 
then becomes the secondary server. 
 
 
 
3.6.  Activation of HTTPS for the SafeKit console 
More information: SafeKit User's Guide / 11. Securing the SafeKit web service 
 
  
SRV-AEOS-A 
SRV-AEOS-B 
nedap
```

## Page 27

```
Setting up a SafeKit failover cluster with AEOS & SQL 
27 
 
nedapfrance.fr 
 Configuration of client and hardware components 
4.1.  AEOS Classic and Dashboard 
AEOS Classic: 
• Create a web shortcut on the client with the following URL: 
https://cls.nedap.fr:8443/aeos/ to allow a connection to the primary server  
 
AEOS Dashboard : 
• Create a web shortcut on the client with the following URL: 
https://cls.nedap.fr:8443/dashboard/ to allow a connection to the primary server 
 
Note: Before, the "hosts" file of the client workstation must be filled in with the cluster name 
(cls.nedap.fr) and virtual IP (192.168.1.250).
```

## Page 28

```
Setting up a SafeKit failover cluster with AEOS & SQL 
28 
 
nedapfrance.fr 
4.2.  Virtual AEPU "client" 
• Virtual AEPU as a client on the network: 
 
• Restart a setup and define the cluster name in AEOS server name
```

## Page 29

```
Setting up a SafeKit failover cluster with AEOS & SQL 
29 
 
nedapfrance.fr 
• Set both lookup servers to allow connection to the active one 
 
• When starting the service, it must be present in AEmon
```

## Page 30

```
Setting up a SafeKit failover cluster with AEOS & SQL 
30 
 
nedapfrance.fr 
4.3.  Physical AEPU 
• AEPU on the network : 
 
 
• Set to AEconf with the following settings: 
o AEServer host name: Name of the cluster "cls.nedap.fr" 
o AEServer IP address: Virtual IP "192.168.1.250"
```

## Page 31

```
Setting up a SafeKit failover cluster with AEOS & SQL 
31 
 
nedapfrance.fr 
• Open AEmon and define 2 lookup servers in the contextual menu → Properties → Lookup 
services 
 
• Check the presence of the AEPU in automatic mode.
```

## Page 32

```
Setting up a SafeKit failover cluster with AEOS & SQL 
32 
 
nedapfrance.fr 
4.4.  Virtual AEPU "server" 
• Virtual AEPU installed on each server with a single active: 
 
• Restart a setup and define the name of the virtual AEPU
```

## Page 33

```
Setting up a SafeKit failover cluster with AEOS & SQL 
33 
 
nedapfrance.fr 
• Set the cluster name and click Next 
 
• Set both lookup servers to allow connection to the active one 
 
Important:  
• Perform this step on both servers A & B with the same AEPU name
```

## Page 34

```
Setting up a SafeKit failover cluster with AEOS & SQL 
34 
 
nedapfrance.fr 
 
• Start the SafeKit console and authenticate. 
 
                     
 
• Before reconfiguring the nedap module, first stop it. Stop first the SECOND to avoid a failover. 
Use the "Stop" command in "…"  
 
                   
 
• Click on "Modules configuration" tab → "Installed Modules" → nedap configure icon  
 
 
 
• Click on "Advanced configuration" to access userconfig.xml 
  
nedap 
SRV-AEOS-A 
SRV-AEOS-B 
SRV-AEOS-A 
SRV-AEOS-B 
nedap
```

## Page 35

```
Setting up a SafeKit failover cluster with AEOS & SQL 
35 
 
nedapfrance.fr 
• In userconfig.xml, add in the SERVICES macro at the end and separated by a comma: AEOS 
aepu service 
• Uncomment the replication of the virtual AEPU directory (optional). And configure the 
process monitoring of AEOS_aepu.exe (optional, still in comment in the screenshot).
```

## Page 36

```
Setting up a SafeKit failover cluster with AEOS & SQL 
36 
 
nedapfrance.fr 
• Click on "Save and apply" to reconfigure the module on both nodes. 
 
• Restart the nedap module with the "Start" command in "…" 
 
                                   
 
  
SRV-AEOS-A 
SRV-AEOS-B 
nedap 
 nedap 
SRV-AEOS-A 
SRV-AEOS-B
```

## Page 37

```
Setting up a SafeKit failover cluster with AEOS & SQL 
37 
 
nedapfrance.fr 
4.5.  Socket Interface - RMI  
• Hypervisor connected as a client over the network: 
 
• Configure the driver with the cluster name “cls.nedap.fr” and the port 8035 (default)  
 
 
 
 
 
Note: The utility presented is an example for simulating a driver. Its use is only for testing and not for 
production.
```

## Page 38

```
Setting up a SafeKit failover cluster with AEOS & SQL 
38 
 
nedapfrance.fr 
4.6.  AEOS Capture – AEOS Cardprinter 
• AEOS Capture and AEOS Cardprinter are connected as a client on the network: 
 
• Launch the setup and define the cluster name "cls.nedap.fr" 
AEOS Cardprinter: 
 
AEOS Capture: 
 
• Check the presence of applications in the taskbar
```

## Page 39

```
Setting up a SafeKit failover cluster with AEOS & SQL 
39 
 
nedapfrance.fr 
4.7.  Nedap SQL import 
• The Nedap SQL Import utility is installed on each server with a single one active:  
 
• Define the profile(s) with the cluster name “cls.nedap.fr” 
 
 
Important:  
• Perform this step on both servers A & B 
• Start the SafeKit console and authenticate. 
 
                     
 
• Before reconfiguring the nedap module, first stop it. Stop first the SECOND to avoid a failover. 
Use the "Stop" command in "…"  
 
                   
 
• Click on "Modules configuration" tab → "Installed Modules" → nedap configure icon  
nedap 
SRV-AEOS-A 
SRV-AEOS-B 
SRV-AEOS-A 
SRV-AEOS-B 
nedap
```

## Page 40

```
Setting up a SafeKit failover cluster with AEOS & SQL 
40 
 
nedapfrance.fr 
 
 
 
• Click on "Advanced configuration" to access userconfig.xml
```

## Page 41

```
Setting up a SafeKit failover cluster with AEOS & SQL 
41 
 
nedapfrance.fr 
• In userconfig.xml, add in the SERVICES macro at the end and separated by a comma: 
NSI_Service 
• Uncomment the replication of the Nedap SQL Import directory to enable profile replication 
(optional). And configure the process monitoring of NSI_Service.exe (optional, still in 
comment in the screenshot).
```

## Page 42

```
Setting up a SafeKit failover cluster with AEOS & SQL 
42 
 
nedapfrance.fr 
• Click on "Save and apply" to reconfigure the module on both nodes. 
 
• Restart the nedap module with the "Start" command in "…" 
 
                        
  
SRV-AEOS-A 
SRV-AEOS-B 
nedap 
 nedap 
SRV-AEOS-A 
SRV-AEOS-B
```

## Page 43

```
Setting up a SafeKit failover cluster with AEOS & SQL 
43 
 
nedapfrance.fr 
4.8.  Nedap SQL export 
• The Nedap SQL Export utility is installed on each server with a single one active: 
 
• Define the profile(s) with the cluster name “cls.nedap.fr” 
 
 
Important:  
• Perform this step on both servers A & B  
• Start the SafeKit console and authenticate. 
 
                     
 
• Before reconfiguring the nedap module, first stop it. Stop first the SECOND to avoid a failover. 
Use the "Stop" command in "…"  
 
                   
 
• Click on "Modules configuration" tab → "Installed Modules" → nedap configure icon  
 
nedap 
SRV-AEOS-A 
SRV-AEOS-B 
SRV-AEOS-A 
SRV-AEOS-B 
nedap
```

## Page 44

```
Setting up a SafeKit failover cluster with AEOS & SQL 
44 
 
nedapfrance.fr 
 
 
• Click on "Advanced configuration" to access userconfig.xml
```

## Page 45

```
Setting up a SafeKit failover cluster with AEOS & SQL 
45 
 
nedapfrance.fr 
• In userconfig.xml, add in the SERVICES macro at the end and separated by a comma: 
NSX_Service 
• Uncomment the replication of the Nedap SQL Export directory to enable profile replication 
(optional). And configure the process monitoring of NSX_Service.exe  (optional, still in 
comment in the screenshot).
```

## Page 46

```
Setting up a SafeKit failover cluster with AEOS & SQL 
46 
 
nedapfrance.fr 
• Click on "Save and apply" to reconfigure the module on both nodes. 
 
• Restart the nedap module with the "Start" command in "…" 
 
                        
  
SRV-AEOS-A 
SRV-AEOS-B 
nedap 
 nedap 
SRV-AEOS-A 
SRV-AEOS-B
```

## Page 47

```
Setting up a SafeKit failover cluster with AEOS & SQL 
47 
 
nedapfrance.fr 
4.9.  AppVision 
• The AppVision hypervisor is installed on each server with a single one active: 
 
• Set the AppDriverAEOS driver connection with the cluster IP address 192.168.1.250  
 
 
Note: The databases must be in SQL Server and the connection can be done locally or on cls.nedap.fr  
(cluster name/virtual IP) 
 
• Start the SafeKit console and authenticate. 
 
                     
 
• Before reconfiguring the nedap module, first stop it. Stop first the SECOND to avoid a failover. 
Use the "Stop" command in "…"  
 
                   
 
• Click on "Modules configuration" tab → "Installed Modules" → nedap configure icon  
nedap 
SRV-AEOS-A 
SRV-AEOS-B 
SRV-AEOS-A 
SRV-AEOS-B 
nedap
```

## Page 48

```
Setting up a SafeKit failover cluster with AEOS & SQL 
48 
 
nedapfrance.fr 
 
 
 
• Click on "Advanced configuration" to access userconfig.xml
```

## Page 49

```
Setting up a SafeKit failover cluster with AEOS & SQL 
49 
 
nedapfrance.fr 
• In userconfig.xml, add in the SERVICES macro at the end and separated by a comma: 
AppVision Service 
• Uncomment the replication of the AppVision Configurations directory to allow replication of 
plans, layouts, etc. (optional). And configure the process monitoring of AppServer.exe 
(optional, still in comment in the screenshot).
```

## Page 50

```
Setting up a SafeKit failover cluster with AEOS & SQL 
50 
 
nedapfrance.fr 
• Click on "Save and apply" to reconfigure the module on both nodes. 
 
• Restart the nedap module with the "Start" command in "…" 
 
                        
  
SRV-AEOS-A 
SRV-AEOS-B 
nedap 
 nedap 
SRV-AEOS-A 
SRV-AEOS-B
```

## Page 51

```
Setting up a SafeKit failover cluster with AEOS & SQL 
51 
 
nedapfrance.fr 
• Client tools must connect to “cls.nedap.fr” (virtual IP) 
 
AppVision configurator: 
 
 
 
AppVision client:
```

## Page 52

```
Setting up a SafeKit failover cluster with AEOS & SQL 
52 
 
nedapfrance.fr 
4.10.  SQL script 
 
The SQL script will allow you to modify a value in a table before starting the application. For example 
for the operation of TrakaWeb in “Active & Passive Switchover” mode . 
 
• Place the SQL script in a folder C:\safekit\script\ClusterTraka.sql (for example) 
 
Note: The details of the script are documented in “TD0183 - TrakaWEB Active & Passive Switchover 
- V1_4.pdf”. 
 
• Start the SafeKit console and authenticate. 
 
                     
 
• Before reconfiguring the nedap module, first stop it. Stop first the SECOND to avoid a failover. 
Use the "Stop" command in "…"  
 
                   
 
• Click on "Modules configuration" tab → "Installed Modules" → nedap configure icon  
 
 
 
  
nedap 
SRV-AEOS-A 
SRV-AEOS-B 
SRV-AEOS-A 
SRV-AEOS-B 
nedap
```

## Page 53

```
Setting up a SafeKit failover cluster with AEOS & SQL 
53 
 
nedapfrance.fr 
• Edit module scripts: click on start_prim.ps1. 
o Note that start_prim.ps1 starts all services in the order specified in the SERVICES list, 
while stop_prim.ps1 stops all services in the reverse order. 
 
 
• Edit the script start_prim.ps1 and uncomment the two lines below (remove #).
```

## Page 54

```
Setting up a SafeKit failover cluster with AEOS & SQL 
54 
 
nedapfrance.fr 
• Click on "Save and apply" to reconfigure the module on both nodes.
 
• Restart the nedap module with the "Start" command in "…" 
 
                        
  
SRV-AEOS-A 
SRV-AEOS-B 
nedap 
 nedap 
SRV-AEOS-A 
SRV-AEOS-B
```

## Page 55

```
Setting up a SafeKit failover cluster with AEOS & SQL 
55 
 
nedapfrance.fr 
 Miscellaneous SafeKit 
5.1.  Licence 
• Start the SafeKit console and authenticate. 
 
                     
 
• Click on "Cluster configuration" tab
```

## Page 56

```
Setting up a SafeKit failover cluster with AEOS & SQL 
56 
 
nedapfrance.fr 
5.2.  Logs 
 
• Click on SRV-AEOS-A to see the log of events 
 
• Click on a Script message to see the output messages
```

## Page 57

```
Setting up a SafeKit failover cluster with AEOS & SQL 
57 
 
nedapfrance.fr 
5.3.  Backup 
 
• Back up the following elements to allow restoration if necessary:  
o C:\safekit\var\cluster\cluster.xml 
o C:\safekit\Application_Modules\generic: original configuration (*.safe) 
o C:\safekit\modules\lastconfig: the last 3 configurations (*.safe) 
o C:\safekit\web\conf\ (user authentication, https certificate…) 
 
Notes:  
• The files are available on both servers. 
• A ".safe" file is a zip file containing the module configuration: userconfig.xml and scripts. 
• A ".safe" file can be reinstalled with the SafeKit console.  
 
5.4.  More information on SafeKit 
• SafeKit quick installation guide with Nedap (nedap.safe mirror module)   – the article includes a 
free trial and the nedap.safe module. 
• SafeKit quick installation guide with Hyper-V (hyperv.safe mirror module)  – an alternative 
solution where Nedap AEOS is put inside a virtual machine fully replicated and restarted by 
SafeKit. No need to define services, application folders and virtual IP per application in this 
solution. Other applications can be put in other VMs also replicated and restarted by SafeKit 
(active-active cluster). 
• SafeKit on-line training – a set of videos and demonstrations of SafeKit.
```

## Page 58

```
Setting up a SafeKit failover cluster with AEOS & SQL 
58 
 
nedapfrance.fr 
 Document history 
Date Modification Version Author 
08/03/2024 Document creation 1 D.S. 
10/05/2024 Translation in English + Adaptation to SafeKit 8.2 2 B.R. 
16/05/2025 Adaptation to SafeKit 8.2.4 (SERVICES macro) 3 B.R.
```

## Page 59

```
Setting up a SafeKit failover cluster with AEOS & SQL 
59 
 
nedapfrance.fr 
 
 
 
 
 
Copyright 
Copyright© Nedap 2025 
Nedap AEOS is a registered trademark of N.V. Nederlandsche 
Apparatenfabriek ''Nedap''. Specifications and availability of products 
mentioned in this document are subject to change without notice. 
 
 
Nedap France 
8-10 Chemin d’Andrésy 
95610 Eragny sur Oise 
+33 (0)1 61 03 03 00 
infoaeos@nedap.fr 
www.nedapfrance.fr
```