CSNCurrent en:Sub-Tab "Domine-Server setting"

This tab specifies the maximum number of concurrent agents the CS4N&D application should use. One agent is required for each concurrent file transfer from the Domino server to the Cryptshare server. This setting prevents CS4N&D from interfering with the execution of agents in other applications when a large number of file uploads to the Cryptshare server occur.

Example

According to the Domino server documentation, four agents can run in parallel. For CS4N&D, a maximum of two agents should be used if necessary. This setting ensures that at least two agents are always available for the ongoing operation of other applications.

The button "Refresh" imports the current information on the number and runtime length of the agents into the document for display.

The button "Open sever document" opens the Domino server document in the Domino Directory. There you can see how many parallel agents are currently set up on your Domino server (recommended: at least 2, one of which should be used for CS4N).

Label	Comment
Domino Server Name	Name of the selected Domino server.
Domino Server Version	Version status of the selected Domino server.
Maximum number of agents running in parallel for Cryptshare file transfer	Maximum number of agents to be used by CS4N. The maximum number of agents should always be less than the maximum number of agents running in parallel according to the Domino server documentation. This ensures that the Domino system is not blocked, even when large files are uploaded.
Maximum runtime length reached by the file transfer agent for starting new file uploads.	The agent processes all files ready for transmission one after the other until this queue has been processed or the set runtime length (in % of the total runtime length for agents according to the Domino server document) has been reached. This is to prevent an active file transfer to the Cryptshare server from being interrupted when the maximum runtime length of the agent according to the Domino server document is reached. If there are still transfers in the queue after the interruption, these will be processed in the next run of the periodic transfer agent.