In the Client section of the Server configuration panel you can configure various aspects of the clients' communication with the server. In the Client section of the Server configuration panel you can configure various aspects of the clients' communication with the server.
[ Expand All | Collapse All ]
The Client software database group of functions contains the following field:
When software is pushed to the device by SMS or WAP, it is sent in the form of a link to the software on the server. This link will be valid for the specified number of minutes. If you specify "0", the link will always be valid. For information about installing software on clients, see Installing DME on existing devices. Default value: 60 minutes.
The Connection group of functions contains the following fields:
To keep the DME server from overloading the collaboration server, a mechanism exists to prevent excessive pulling in case of unstable GPRS connections. This setting defines the number of seconds that data to the client should be cached on the server. If a user tries to synchronize before the cache is flushed, the user will get the results from the cache instead of performing an actual synchronization, thus saving a connection to the collaboration server. Default value: 300 seconds. For more information about the cache, see Clients online.
The maximum amount of time in seconds that a synchronization request can exist before it is returned to the client as a timeout error. This typically happens if the collaboration system fails to respond. Default value: 300 seconds.
This setting defines the maximum number of concurrent client connections from the DME server against the collaboration server. Please note this setting only has effect if set higher than maxThreads in server.xml. Note also that apart from this number of processes, the collaboration server needs to be able to handle the number of notification processes defined in the Process section of the Notifications setup panel. For more information, see Process. Default value: 100.
With these two settings, you define a range of seconds. If a client process has been denied access to the server because the number of concurrent client processes has been exceeded (see above), the server tells the process to try again after a random number of seconds between the minimum and maximum number of seconds specified in these fields.
In this field you can set the minimum time the server should wait before sending a keep-alive signal through the network push port. Default value is 3 minutes. In some configurations, this value and especially the maximum keep-alive time value can cause problems in connection with firewalls, proxies and other network equipment. For more information, see Appendix F: AdaptivePush™.
In this field you can set the maximum time the server should wait before sending a keep-alive signal through the network push port. Default value is 30 minutes. The maximum value is 35 minutes. If the server waited longer than 35 minutes, Symbian devices would crash due to a limitation in the Symbian OS.
In some cases, a large DME communication batch size is required to be able to show complex HTML e-mail on the client. This batch size is set by the client (version 4.1.3 and above).
However, Domino installations perform poorly with large batch sizes. For this reason, you can use this setting to control the batch size here, if the client sets the batch size too high. The default setting is Value from DME Client.
The DM server group of functions contains the following field:
In this field you can specify the network port you want to use for OMA DM traffic. If the field is blank, DME uses the same port as for synchronization traffic (5011 by default). In a DME cluster setup, you may be required to use a separate OMA DM port, if the load balancer cannot handle multiple types of rules (both cookie and URL stickiness in this case). The load balancer needs to keep a persistent connection between the client and the DME server node providing the software requested by the DM engine.
If you change the port in this field, we recommend using port 5031 - this is the port used in the cluster configuration documentation, which is available at the Excitor Partner website. Note that you may need to change your firewall configuration as well.
Click Save configuration to save the current configuration.
|
Next topic |
Client software database