Monitore database accessibility
A mechanism is available that checks whether reading data from the Alfabet database and writing data to the Alfabet database is currently possible without causing any issues. The test is executed via a monitoring event that creates a test object, reads data about the test object, updates it, and deletes it. If errors occur during one of the processes, these will be logged.
The monitoring event can either be run once or scheduled to be executed in regular intervals of ten minutes.
- The one-time execution of the event requires a running database server hosting the Alfabet database, and a running Alfabet Web Application connected to the Alfabet database.
- The cyclic execution of the event requires a running database server hosting the Alfabet database, a running Alfabet Web Application connected to the Alfabet database., and a running Alfabet Server connected to the Alfabet database.
The RESTful services of the Alfabet Web Application must be implemented and a user must be selected for execution of self-reflective events. The API access Has MonitoringAPI Access option must be activated for that user and in the server alias of the Alfabet Web Application.
- Central logging is enabled in the Server Settings > Logging tab of the server alias and the Monitoring log option is activated in the table of the Server Settings > Logging Details tab.
The execution of monitoring events can be triggered and stopped via the command line tool AlfaAdministratorConsole.exe.
To trigger a one-time execution of a monitoring event, run AlfaAdministratorConsole.exe with the following command line:
- AlfaAdministratorConsole.exe -trigger_monitoring_event -msalias <alias name> -DbUser <database user name> [-DbPassword <database user password> -timeout <seconds>]
To start the recurring execution of monitoring events, run AlfaAdministratorConsole.exe with the following command line:
- AlfaAdministratorConsole.exe -trigger_monitoring_event_chain -msalias <alias name> -DbUser <database user name> [-DbPassword <database user password>]
To stop the recurring execution of monitoring events, run AlfaAdministratorConsole.exe with the following command line:
- AlfaAdministratorConsole.exe -stop_monitoring_event_chain -msalias <alias name> -DbUser <database user name> [-DbPassword <database user password>]
The table below displays the command line options:
| Command Line Option | Mandatory/ Default | Explanation |
|---|---|---|
| -<action type> | Mandatory | Set the action type to one of the following:
|
| -msalias <alias name> | Mandatory | Enter the server alias name as specified in the AlfabetMS.xml configuration file for access to the database. |
| -msaliasesfile <Alfabet configuration file path> | Optional | If the AlfabetMS.xml configuration file that contains the specification of the alias is not located in the same directory as the executable, the path to the AlfabetMS.xml file must be specified with this parameter. |
| -DbUser <database user name> | Mandatory | Specify the user name for access to the Alfabet database on the database server. For Oracle® databases, the user name is identical to the schema name. |
| -DbPassword <database user password> | Mandatory | Specify the password for access to the Alfabet database on the database server. |