In the Data section of the Server configuration panel you can view the amount of data used by the DME database, configure the DME data cleanup thread, specify directories for data storage, determine the volume of log entries, set the maximum size of file uploads, and configure the obfuscation of phone numbers in the statistics database.
[ Expand All | Collapse All ]
The Database usage group of fields shows the current size of three tables in the DME database. The size is shown as a ratio between the current size and the maximum amount available for the table in question. On systems based on the MySQL database, the maximum size is typically 4 GB. On systems based on MS SQL Server, the table size can usually be expanded dynamically, and you must ask your database administrator for information about the maximum size of each table.
A graphical view of the ratio between the actual and the maximum amount of data in the log.
A graphical view of the ratio between the actual and the maximum amount of data in the statistics table.
A graphical view of the ratio between the actual and the maximum amount of data in the voice statistics table.
The Log configuration section contains one option:
If this field is set to True, only information about DME is shown in the log.
If this field is set to False, information from a number of third-party applications will also be included in the log, such as information about JBoss, Domino, CORBA and so on, as configured in the jboss-log4j.xml file on the connector. This information is also available elsewhere, that is in other log files. See the documentation for the third-party application in question.
Default: True.
The settings in the Surveillance log group of fields are used to specify options for the Surveillance log type. For more information about which events are tracked and how this operational logging is configured, see System. This group of functions contains the following fields:
If this field is set to Yes, DME will monitor its internal state of health and output any error messages in a uniform and readable way.
The Surveillance type of monitor checks for errors at various intervals (see System). The shortest of these intervals is by default 10 seconds, but you can change that here. This frequent check applies to DME database and Central Services availability.
Please note that for a change in this setting to take effect, a DME server restart is required.
If an error situation arises, the Surveillance monitor will wait for the period of time entered here (in seconds) before a message is written in the log. This is to allow for any planned interruption of service. By default, DME waits 5 minutes (300 seconds) before entering an error message pertaining to database and Central Services availability. Enter 0 in this field if you want the monitor to log a message immediately.
The settings in the Database maintenance group of fields are used by the internal cleanup thread, which cleans out old log entries and statistics that have lost their relevance. This group of functions contains the following fields:
This setting specifies how old a log entry must be to be cleaned out of the database automatically. Default is 180, which is about six months. However, if you run an active system with many users, it is a good idea to reduce the number of days to 90 or even 30 days, as the database log table will otherwise grow very large.
The functionality of this field is similar to that of the field field Delete log older than (days) above, but applies to statistics entries.
In this field you can specify (in hours) how often the cleanup thread should be launched to clean out old log and statistics entries. Default is 24 hours, meaning that the server will clean out log entries and statistics older than the number of days specified above daily.
Data storage directories (including custom graphics for Android and iOS)
The Data storage directories group of functions contains the following fields:
This is the directory in which DME stores local data, including files for synchronization, device images, device statistics, and custom (white-label) images for Android and iOS clients.
For information about how to add custom graphics to Android and iOS clients (version 4.0 and up), see Appendix J: Custom graphics on Android and iOS.
The directory in which DME stores temporary data, such as files being uploaded, temporary cache data, etc.
The Data limits group of functions contains the following field:
In this field you can specify the maximum size of files uploaded to the server. This limit applies to all files uploaded to the server. A file can be uploaded as a result of a file synchronization rule or as an attachment to an e-mail sent from a DME client, or it can be a DME client uploaded to the Provisioning tab.
If your DME database is a MySQL database, and you increase this value to above the default value of 16 MB, you will probably need to change the configuration the max_allowed_packet value for your database accordingly in order to prevent errors. For instance, if you change the value here to 32 MB, enter the following command in the database shell:
mysql ‑‑max_allowed_packet=32M
For more information, see the following article on the MySQL home page: Packet too large.
The Statistical data group of functions contains the following field:
In statistical reports using the BIRT reporting framework it is possible to create reports that allow drill-down to individual phone calls. In many countries, it is not permitted to display the entire phone number in such reports for reasons of privacy.
In this field, you can enter the number of digits that DME should hide from the phone numbers stored in the statistics database. The phone numbers are obfuscated by replacing the digits with an X. The digits are replaced from right to left. If you enter 0 in this field, the phone numbers will be fully displayed.
Click Save configuration to save the current configuration.
|
Next topic |