solidDB Help : Samples : HotStandby sample : Watchdog sample application : [Watchdog] section of the solid.ini configuration file
  
[Watchdog] section of the solid.ini configuration file
The solid.ini file for the Watchdog sample application contains a [Watchdog] configuration section to specify parameters that are specific to the Watchdog sample application.
Important The parameters in the [Watchdog] section of the solid.ini file are NOT all predefined by solidDB. Depending upon how you write your watchdog application and whether you want it to read parameter information from the solid.ini file, you can use any mix of the parameters defined here and parameters that you have defined. You can also ignore parameters. The parameters shown here are for the Watchdog sample program that is provided with solidDB.
 
[Watchdog]
Description
Factory value
AutoSwitch
Determines whether the Watchdog sample application can switch the states of the servers.
If AutoSwitch is set to YES, the Watchdog sample application automatically does the following actions:
▪ If the secondary server fails, then the Watchdog sample application tells the primary server to switch to PRIMARY ALONE state (rather than stay in PRIMARY UNCERTAIN) state.
▪ If the primary server fails, then the Watchdog sample application tells the original secondary server to become the new primary server and switch to PERIMARY ALONE state.
If AutoSwitch is set to NO, the Watchdog sample application does not switch server states, instead it writes a message to the Watchdog log to notify the user to switch server states.
This parameter is optional.
YES
Connect1
Enables the Watchdog sample application to connect to the primary or secondary server.
This is a required parameter that defines the protocol and network address for the first HSB server.
For example:
connect1 = tcp primarymachine 1313
None
Connect2
Enables the Watchdog sample application to connect to the primary or secondary server.
This is a required parameter that defines the protocol and network address for the second HSB server.
For example:
connect2 = tcp secondarymachine 1313
None
DualSecAutoSwitch
Determines what happens if both servers are secondary servers.
If DualSecAutoSwitch is set to YES, then the Watchdog sample application automatically selects one of the two secondary servers to be a new primary server and switch it to a primary state.
If DualSecAutoSwitch is set to NO then the system administrator must switch one server to be the primary server.
Note DualSecAutoSwitch applies whether the Watchdog sample application is in normal mode or failure mode.
YES
NumRetry
Number of attempts (made by the Watchdog sample application) to connect to a primary or secondary server before the connection attempt is considered a response failure or error.
For example:
NumRetry = 3
The retries are in addition to the original try. If number of retries is set to 3, then the total number of attempts is 4. Note that the retries are immediate. The Watchdog sample application does not wait for an interval of time (such as PingTimeout) in between retries when there is a failure.
This parameter is optional.
0
Password1 Password2
See descriptions for the Username1 and Username2 parameters.
No factory value.
PingInterval
Interval (in milliseconds) between querying status connect information when Watchdog sample application is working in normal mode.
For example:
PingInterval = 5000
This parameter is optional.
Note that the PingInterval parameter for the Watchdog sample application is different from the PingTimeout parameter for the servers.
Important In previous versions of solidDB, the Watchdog sample application specified the value for the PingInterval parameter in seconds. If you have upgraded from a previous version, check the value that is set in solid.ini.
1000
(1 second)
Username1 Username2
User names and passwords for using the servers.
For example:
Username1 = Tom
Password1 = dr17xy
Username2 = Jerry
Password2 = M89tvt
If (for security reasons) these parameters are not specified in the solid.ini configuration file, the Watchdog sample application prompts the administrator to provide them when the application starts.
No factory value.
WatchdogLog
Path and file name of the Watchdog sample application log file.
The Watchdog log is created in the current working directory and used to record Watchdog messages that alert administrators of the need to run commands.
For example:
WatchdogLog = Watchdog.log
The path can be an absolute path or relative to the solidDB working directory and must use the conventions of your operating system. For example, in Windows environments, if the path contains white space characters, the path must be enclosed in double quotation marks. If the server runs on a UNIX operating system, path separators must be slashes instead of backslashes.
This parameter is optional.
Watchdog.log
Go up to
Watchdog sample application