You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: user-guide/part_3/failover/Failover_configuration_in_Cube.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -80,6 +80,6 @@ To enable Failover using DataMiner version **10.1.7 or lower**:
80
80
> [!NOTE]
81
81
> - Both DMAs store the full Failover configuration in their *DMS.xml* file. Each time the Failover configuration is changed, a copy of the old *DMS.xml* file will be moved to the folder *C:\\Skyline DataMiner\\Recycle Bin*.
82
82
> - If the configuration is changed on only one of the DMAs because the other was unreachable, the newest configuration will be synchronized as soon as the DMAs can make contact again.
83
-
> - To avoid possible issues in case a NIC is unplugged, you can specify the order of the network adapters used by a DMA (the first being used for the corporate network, the second for the acquisition network). To do so, configure the *NetworkAdapters* tag in the file *DataMiner.xml* (see [Alphabetical overview of settings](xref:DataMiner_xml#alphabetical-overview-of-settings)). However, note that to do so, you will need to stop both Failover Agents and then restart them once the file has been modified. If you do this for an existing Failover setup, you will also need to make sure that the changes you make match the IP configuration in DMS.xml.
83
+
> - To avoid possible issues in case a NIC is unplugged, you can specify the order of the network adapters used by a DMA (the first being used for the corporate network, the second for the acquisition network). To do so, configure the *NetworkAdapters* tag in the file *DataMiner.xml* (see [DataMiner.NetworkAdapters](xref:DataMiner_xml#dataminernetworkadapters)). However, note that to do so, you will need to stop both Failover Agents and then restart them once the file has been modified. If you do this for an existing Failover setup, you will also need to make sure that the changes you make match the IP configuration in DMS.xml.
84
84
> - For Failover logging information, refer to the files *SLNet.txt* and *SLFailover.txt*.
Copy file name to clipboardexpand all lines: user-guide/part_3/failover/Preferred_configuration_using_virtual_IP_addresses__best_practice.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ Make sure to respect the order of the connections in the *Network Connections* l
21
21
- The second connection represents the acquisition network, which is mainly used for communication with data sources managed by DataMiner.
22
22
23
23
> [!NOTE]
24
-
> To avoid possible issues in case a NIC is unplugged, you can specify the order of the network adapters used by a DMA (the first being used for the corporate network, the second for the acquisition network). To do so, configure the *NetworkAdapters* tag in the file *DataMiner.xml* (see [Alphabetical overview of settings](xref:DataMiner_xml#alphabetical-overview-of-settings)). However, note that to do so, you will need to stop both Failover Agents and then restart them once the file has been modified. If you do this for an existing Failover setup, you will also need to make sure that the changes you make match the IP configuration in DMS.xml.
24
+
> To avoid possible issues in case a NIC is unplugged, you can specify the order of the network adapters used by a DMA (the first being used for the corporate network, the second for the acquisition network). To do so, configure the *NetworkAdapters* tag in the file *DataMiner.xml* (see [DataMiner.NetworkAdapters](xref:DataMiner_xml#dataminernetworkadapters)). However, note that to do so, you will need to stop both Failover Agents and then restart them once the file has been modified. If you do this for an existing Failover setup, you will also need to make sure that the changes you make match the IP configuration in DMS.xml.
Copy file name to clipboardexpand all lines: user-guide/part_7/SkylineDataminerFolder/ConnectionSettings_txt.md
+25-24
Original file line number
Diff line number
Diff line change
@@ -10,9 +10,7 @@ This file contains default connection settings to be used by DataMiner client ap
10
10
> - An update of this file does not require a restart of the DataMiner software.
11
11
> - This file is not synchronized throughout the DataMiner System.
12
12
13
-
- This file is located in the following folder:
14
-
15
-
*C:\\Skyline DataMiner\\Webpages\\*
13
+
- This file is located in the folder *C:\\Skyline DataMiner\\Webpages\\*.
16
14
17
15
- ConnectionSettings.txt format:
18
16
@@ -32,56 +30,59 @@ This file contains default connection settings to be used by DataMiner client ap
32
30
33
31
- **type=**
34
32
35
-
The type of connection. Possible values:
33
+
The type of connection. Possible values:
36
34
37
-
- RemotingConnection (.NET Remoting)
35
+
- RemotingConnection (.NET Remoting)
38
36
39
-
- WSConnection (Web Services - deprecated from DataMiner 10.0.11 onwards)
37
+
- WSConnection (Web Services - deprecated from DataMiner 10.0.11 onwards)
40
38
41
39
- **polling=**
42
40
43
-
Polling interval Possible values:
41
+
Polling interval Possible values:
44
42
45
-
- Number of milliseconds (minimum: 100)
43
+
- Number of milliseconds (minimum: 100)
46
44
47
-
- 0 (no polling)
45
+
- 0 (no polling)
48
46
49
47
- **serverport=**
50
48
51
-
Server port onto which the client has to connect. Possible values:
49
+
Server port onto which the client has to connect. Possible values:
52
50
53
-
- Port number
51
+
- Port number
54
52
55
-
- 0 (no override - connect to default port)
53
+
- 0 (no override - connect to default port)
56
54
57
55
- **zip=**
58
56
59
-
Whether or not the communication has to be zipped. Possible values:
57
+
Whether or not the communication has to be zipped. Possible values:
60
58
61
-
- true
59
+
- true
62
60
63
-
- false
61
+
- false
64
62
65
63
- **cache=**
66
64
67
-
The type of data that has to be cached on the client machine.
68
-
When this option is set to its default value (“objects”), a number of objects (e.g. DataMiner Protocols) are cached on the client machine. Once these objects are present on the client, data traffic between DMA and client drops substantially. Possible values:
65
+
The type of data that has to be cached on the client machine.
66
+
67
+
When this option is set to its default value (“objects”), a number of objects (e.g. DataMiner Protocols) are cached on the client machine. Once these objects are present on the client, data traffic between DMA and client drops substantially. Possible values:
69
68
70
-
- all
69
+
- all
71
70
72
-
- none
71
+
- none
73
72
74
-
- objects (default)
73
+
- objects (default)
75
74
76
-
- events
75
+
- events
77
76
78
77
- **resolve=**
79
78
80
-
Whether or not hostnames have to be resolved to IP addresses before the connection is set up. Possible values:
79
+
Whether or not hostnames have to be resolved to IP addresses before the connection is set up.
80
+
81
+
Possible values:
81
82
82
-
- true (default)
83
+
- true (default)
83
84
84
-
- false
85
+
- false
85
86
86
87
> [!NOTE]
87
88
> - If a client connects to a DataMiner Agent via a load balancing URL (i.e. a hostname redirecting to different IP addresses when resolved), by default the hostname will be explicitly resolved before the connection is set up. If, for some IP addresses, you want to prevent this from happening, in ConnectionSettings.txt specify “resolve=false” next to those IP addresses.
Copy file name to clipboardexpand all lines: user-guide/part_7/SkylineDataminerFolder/DBMaintenance_xml_and_DBMaintenanceDMS_xml.md
+10-10
Original file line number
Diff line number
Diff line change
@@ -96,7 +96,7 @@ Examples:
96
96
- To specify a period of 1 hour, you can use “1h”, “3600s” or “3600”.
97
97
98
98
> [!NOTE]
99
-
> - Strings without unit will be interpreted as a number of seconds.<br>For example, “3600” will be interpreted as 3600 seconds.
99
+
> - Strings without unit will be interpreted as a number of seconds.For example, “3600” will be interpreted as 3600 seconds.
100
100
> - For a logger table, the TTL value can be set to “-1” to indicate that the TTL value is specified in the protocol.
101
101
> - From DataMiner 9.5.13 onwards, if the TTL value is set to “0” for a particular type of data, no data of that type will be stored in the database.
102
102
> - For an indexing database, it is possible to specify “infinite”, in which case the data will be kept indefinitely.
@@ -157,7 +157,7 @@ Example of a *DBMaintenanceDMS.xml* file with protocol override:
157
157
158
158
From DataMiner 9.5.14 onwards, timetrace data for a service in the Cassandra database by default only contains the service properties that match with the service key. In earlier versions of DataMiner, the rows contained the service properties of all affected services.
159
159
160
-
It is possible to revert to the earlier behavior by adding the following tag in the *\<MaintenanceConfig>* tag of the *DBMaintenance.xml* or *DBMaintenanceDMS.xml* file: <br>*\<TimeTrace duplicateAllServiceProperties="True" />*.
160
+
It is possible to revert to the earlier behavior by adding the following tag in the *\<MaintenanceConfig>* tag of the *DBMaintenance.xml* or *DBMaintenanceDMS.xml* file: *\<TimeTrace duplicateAllServiceProperties="True" />*.
161
161
162
162
However, note that this can cause a significant increase in disk space usage, especially in systems with many services and service properties.
163
163
@@ -168,13 +168,13 @@ However, note that this can cause a significant increase in disk space usage, es
168
168
169
169
When you upgrade a DataMiner Agent without the two new configuration files to a version with these files, *DBMaintenance.exe* will copy a number of settings from the *DB.xml* and *MaintenanceSettings.xml* files to the new configuration files. See the following table:
When you downgrade to a DataMiner Agent without the two new configuration files, *DBMaintenance.exe* will revert the above-mentioned copy actions and update the settings in question in both the *DB.xml* and *MaintenanceSettings.xml* files.
0 commit comments