The Exchange service is useful for exchanging documents or data that require constant connectivity (permanently listening for communication). EBA DMS currently uses the AS2 protocol. The AS2 protocol requires a server and a client on both the recipient and the sender side.
A similar example of constant connectivity is the FTP protocol. The Exchange service is not used for the execution of the send/receive function or for Microsoft Exchange.
If you do not use AS2 exchange to receive documents, then be sure to turn this service off!
- Quit after idle time: The 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 is 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.
- Server name or address: IP address or name of the server where the EBA application services are running.
For each Exchange Server, you need to set its port – you configure the protocols that use the Exchange Service in the EBA DMS Client in the Exchange>Anywhere menu.
Monitors all the activity of this service – from harvesting to processing.
This tab monitors, for each server or protocol, the requests received and the server’s response to them.
Overview of all requests, regardless of server or protocol.
Here we see the individual messages, or messages generated by the server that received the request.
If there is an error in the execution of 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
In this tab, information about all the executed requests that have been executed by this service is stored. This is where all the automation process information for the service is stored when the logging level is set to Debug.
This is where all activities related to the service itself are monitored. If the service is unresponsive or “crashes”, then it will be logged in these logs.
Messaging and Log setting
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.