SqlService
The SqlService represents the interface between the DatabaseService and applications that want to address databases connected via this service.
Additionally, the service provides replication mechanisms for other Integration Servers.
XML configuration
Important note: The availability of a service depends on the license purchased and whether the service has been registered in the configuration file ./etc/factory.xml of the Service Factory (changes require server restart!). There you will also find the responsible configuration file for a service, otherwise you can also edit the configuration file of the service directly in the GUI of the service (changes require a service restart!).
Setting the "DatabaseService"
The following XML fragment sets the DatabaseService to be used.
<Set name="connectionService">DatabaseService</Set>Setting the replication data
If replication from other Integration Servers is to be possible, the replication data required for authentication can be set with the following XML fragment.
<Set name="ReplicateUser">user</Set><Set name="ReplicatePassword">password</Set>General settings
(1) Name of the used DatabaseService.
(2) Replication login data for replication with other Integration Servers.
Active SQL sessions
(1) List of active sessions. The session ID, the time of the start of the sessions and the set maximum lifetime for the session are displayed (0 = unrestricted). A session can be ended and details for the respective session can be displayed via the context menu, e.g. the stack trace of the generation of the session (This can be used to check which class has generated the session in which method).
Log level dependencies
Changes to the log level of the LogService have no influence on the logging behaviour of the SqlService.
If the service is set to verbose mode, all SQL statements and stored procedures executed via an SQL session are reported, including the parameters used.
Likewise, messages are generated during a data replication.