Web services are mainly used for integration with other information systems.
The service is designed to listen, receive and process requests sent via web services, set configuration, control data transfer and keep log files.
- Port: The default port is 9876. Please note if you already have this port busy or if you have multiple EBA Application Service instances installed. In this case each instance must have its own port.
- SSL Certificate. Before that, we have to import the certificate with the EBA DMS client into the Certificate Store.
- Check for database notification: is an option offered by some databases to send notifications. Here we turn on this option.
- WS server: Here we enter the address of the server where the web service is running.
- Server name or address: The IP address or name of the server where the EBA application services are running.
- Max. instance serve count. Set how many requests the service can process.
- Quit after idle time: default value is 60 seconds, which means that once the service accepts a request and processes it, and is idle for more than 60 seconds, then the request will be terminated or aborted.
- Initial pool size: This setting limits the processing of a configured number of requests running concurrently.
- Additional pool size: This setting is subordinate to the above one – if the above value (initial pool size) is reached and a new request comes in for processing – the system will consider the number of requests configured here until the amount of requests specified by the Initial pool size is released.
This tab is only available in the Multi tenant deployment of EBA application services.
Service ports can be set up on a per-database basis.
It is set in the same way as in the single tenant layout.
Monitors all the activity of this service – from harvesting to processing.
Provides a list of all processes that have been running since the Web service was started. Each process has its own PID, so it is easier to search for the relevant log files if necessary.
WS Request History
Works similarly to the Services monitor, except that there is a complete history of the running of the service. The history is logged for a maximum of 7 days.
If there is an error when executing a script, here we can see which project has the error and so we can more easily detect the error. In this tab we will find information about any error that occurred when executing a script via the EBA DMS client
This tab stores information about all the executed requests by the Web service. All information about the automation process for the service is stored here when the logging level is set to Debug.
This is where all activities related to the Web service itself are monitored. If the service is unresponsive or “crashes”, then it will be logged in these logs.
Messaging & Logging
Each service has a list of possible errors with a defined priority, and for each of these you can set the system to send you a notification if an error occurs.
In the Logging section you can configure where the logs are logged and for how many days they are kept.
You can also set the logging level, the default level is Debug.