In the Web section of the Server configuration panel you can configure various aspects of the DME server Web administration interface and of logging. In the Web section of the Server configuration panel you can configure various aspects of the DME server Web administration interface and of logging.
[ Expand All | Collapse All ]
The Web administration group of functions contains the following fields:
The default number of days for which statistics are shown on the Analyzer tab. You can change this value in the date filter in the Analyzer tab - see Finding information. Recommended value: 30.
The default number of days for which logs are searchable on the Log tab. You can change this value in the date filter in the Log tab - see Finding information. Recommended value: 30.
In this field you can specify the name of the installation managed by these administration pages. It is the name shown in title bar of the web browser, typically the name of your company. The name is initially entered by the DME Setup Wizard, but you can change it here.
Note that you can have multiple instances of DME running on the same machine, for instance a production instance and a test instance. Entering different names for different instances makes it easier to distinguish between them.
In this field you can specify the name of the server on which the current installation is run. If the server name is empty (default), DME uses the server hostname as defined in the server OS. In a cluster setup, we recommend that you change the name in this field to a short name, which helps you to identify the server easily.
The server name is printed on every entry in the server log, and can been seen on the entries visible in the Log tab. The server name is also added as the first part of the name of the different statistics you can see in the Monitor panel section.
The inclusion of the server name in log entries makes it easier for a load balancer to distribute the server load and for a fail-over system to cease using a defective server. In a cluster, you set up all servers (virtual or physical) with the same installation name, but different server names. For more information, please request special cluster setup documentation.
The way that individual devices are structured into groups is important when notification schedules have been set up for individual groups. For instance, if a user is member of the LDAP group Sales, and a special notification schedule has been set up for this group, then it is important that DME knows which users are member of Sales in order to notify the users' devices about new e-mail etc.
DME uses the group membership to help you release DME licenses that are no longer in use. When a user is removed from a group that gives access to using DME, then the user's license will be released when DME refreshes the user/group membership.
DME refreshes the relationship between users and groups by scanning the LDAP/AD system at regular intervals as defined in this field. You can either enter the number of minutes that should pass between each refresh, or you can enter a specific time of day in hh:mm format, and DME will then perform the user/group refresh at that time. You could for instance specify that DME should refresh the user/group memberships every night at 02:00.
If you want to make sure that the user/group memberships are up-to-date, click the Run now button to perform a manual refresh. You may want to do this if you change the relationship of a device to a group (by adding devices to or removing devices from a group, or by changing the priority of a group), or if you switch users in or out of groups in the LDAP/AD system.
In this field you can specify the path to the online documentation for the DME server. Excitor A/S maintains a website with the documentation for the different versions of the DME server and other documentation. By default, the server path is set to http://resources.excitor.com/manuals/server/[ServerVersion], where [ServerVersion] is the version of the current DME server, with underscores replacing the periods - for instance 5_0. In case firewall restrictions or other issues makes it impossible to access the Excitor documentation site, you can request a copy of the online documentation for installation on the local machine.
The online help is shown when you click a question mark icon 
in the page. For more information, see Online help.
With this setting, you can choose the port you want to use for accessing the DME web administration interface using HTTPS through the Nginx proxy server. By binding the web interface to a specific port, you exclude access from other ports which are used for other purposes, for instance the 5011 and 443 sync ports. The chosen port can for instance be configured by a firewall to be available from inside the company only (and not the internet).
The list of available ports is built from settings in the ..\dme\jboss\bin\standalone.bat configuration file which is generated during installation of DME. Typically you would choose to bind to port 5009 which is the default management port for the DME Web admin interface. Remember that all HTTPS traffic is terminated in the Nginx proxy server and proxied on to the DME Gateway server using HTTP. The configuration file for Nginx is ..\dme\nginx\conf\nginx.conf. By default the Nginx to DME "port translation list" is as follows:
When you connect to the web interface in a cluster setup, for instance using https://<path to load balancer>:8080, the load balancer will direct you to the next available server in the round-robin rotation. If you want to be able to manage a specific server node in the cluster, you must set up rules on the load balancer that forward you to the intended server. For instance, you can forward port 8081 to port 8080 on the DME-1 node, 8082 to DME-2:8080, and so on. Thus, entering the path above with port 8080 will show you a random server, port 8081 will show you DME-1, and so on.
It should be noted that in a cluster setup you can manage any server node in the cluster, and the node will immediately propagate your configuration changes to the other nodes. The only case where you need to see a specific node is when viewing statistics on the Monitor page on the Server tab, which can only be viewed from the master node. The master node is the node shown first when you view the Server properties subtab on the Monitor page.
The Log group of functions contains the following field:
The whois server is used for looking up the provider of the connecting device, translating IP addresses in the Log tab to human readable DNS names.
Click Save configuration to save the current configuration.
|
Next topic |
Web administration