TimeService
The TimeService finds is used in cluster and other distributed installations (e.g. DMZ scenarios), where a uniform time within log entries is necessary.
One Integration Server is defined as the time server, which return the current time when addressed using the MessageService.
XML configuration
Note: If you want to modify the configuration file for a service directly in the file system, you will find the appropriate file in the configuration file ./etc/factory.xml. Details about the configuration can be found in the respective documentation of a service. Otherwise, you can edit the configuration file directly via the respective service in the GUI.
The following XML fragment with all possible base settings can be used for the configuration of the TimeService.
<
Set
name
=
"messageService"
>MessageService</
Set
>
<
Set
name
=
"timeServer"
>127.0.0.1</
Set
>
The parameters have the following meaning.
Parameter |
Description |
messageService |
The name of the MessageService via which requests should be sent or received. |
timeServer |
The IP of the timeserver. If this is the local server, the entry can also be omitted. |
Activating the "TimeService" as timeserver
In order for the local TimeService to be addressed by other Integration Servers, the corresponding MessageSubscriber must be added to the MessageService. This is done with the following XML fragment, which has to be inserted into the configuration file ./etc/message.xml of the MessageService.
<
Call
name
=
"addConsumerQueue"
>
<
Arg
>
<
New
class
=
"com.ebd.hub.services.message.ConsumerQueue"
>
<
Arg
>System</
Arg
>
<
Arg
>time</
Arg
>
<
Call
name
=
"addConsumer"
>
<
Arg
>com.ebd.hub.services.time.TimeSubscriber</
Arg
>
<
Arg
>consume</
Arg
>
</
Call
>
</
New
>
</
Arg
>
</
Call
>
The two parameters describe the message context and the message queue on which time requests from other Integration Servers are to be expected. The remaining settings must be adopted as specified.
It should also be noted that for a successful request from other systems, the remote interface of the MessageService must be enabled.
General settings
(1) The name of the MessageService that is used for requests.
(2) The IP of the Integration Server that serves as time server. If it is the local server, the entry can be omitted.
(3) The current time received from the server. Refresh updates the time.
Log level dependencies
Changes to the log level of the LogService have no influence on the logging behaviour of the TimeService. Similarly, setting the verbose mode has no effect.