Warning |
---|
This page is only valid with ADS 1.5.5 ! |
NTP Protocol
...
Configuration
The server.xml file contains the bas configuration for the NTP server :
Code Block |
---|
<ntpServer id="ntpServer" ipPort="60123" nbThreads="2"/>
|
With such a configuration, the NTP server will listen to port 60123, with UDP and TCP transports selected.
Common Service Configuration Parameters
Here is the list of parameters you can set. The bold parameters are mandatory.
Parameter | Default value | Description | Optionnal | |||
---|---|---|---|---|---|---|
id | "ntpServer" | Do not change this value : it is used internally to identify the NTP server instance | NA | |||
serviceName | Apache NTP Service | The friendly name of this service. | yes | |||
enabled | true | Tells if the server is enabled or not. | yes | |||
ipAddress | localhost | The IP address for this service. | yes | |||
ipBacklog | 50 | The backlog size for both UDP and TCP transport | yes | enabled | false | Whether this service is enabled. |
ipPort | 123 | The IP port for this service. . It is valid for both UDP and TCP transports. | yes | |||
nbThreads | 2 | The number of thread used by the service IoProcessor | yes | |||
tcpBacklog | 50 | The backlog size for the TCP transport. | yes | |||
tcpPort | 123 | The TCP port | ipAddress | No default. | The IP address for this service. | yes |
serviceName nbTcpThreads | Apache NTP Service 2 | The friendly name of this service. | servicePid | org.apache.ntp | The PID for this service. A PID is a unique identifier for an instance of a service. PID's are used by OSGi's Config Admin service to dynamically inject configuration into a service when the service is startednumber of thread used by the TCP service IoProcessor | yes |
udpBacklog | 50 | The backlog size for the UDP transport | yes | |||
udpPort | 123 | The UDP port for this service. | yes | |||
nbUdpThreads | 2 | The number of thread used by the UDP service IoProcessor | yes |
Note |
---|
The last six parameters should be used only if one want to set up only a single transport, or when UDP and TCP transport don't share the same port. |
More Information
For help with more advanced configurations, check out our Interoperability Guide.