...
Some operations are limited in time by defining a timeout. Without it, a user may have to wait a long time for a failing operation where an response is missing. A short timeout may break an operation where the processing takes a long time, but no error occurs. Depending on database size, configuration may need to ne can be changed to allow a longer waiting time.
Web.config
Configuration for AssertServer resides in IIS root folder of the application, normally in this folder. It defines SOAP bindings with timeout for send and receive of SOAP messages.
Code Block |
---|
C:\inetpub\wwwroot\AssertServer |
Server.config
Other configuration for the application is found in a different configuration file, normally here. It defines timeout values for publication and validation, for SOAP transactions and for database transactions.
Code Block |
---|
C:\ProgramData\Signifikant\Assert |
Start.exe.config
Manager client program timeout is defined in its configuration file.
SOAP operation timeout is defined in binding elements, name = AssertSoapServiceBinding or AssertSoapServiceBindingSSL depending on the schema used for client/server communication. I.e. HTTP or HTTPS address to the server.
Code Block |
---|
C:\Program Files (x86)\Signifikant\Manager\Start.exe.config |
SOAP interface
Generally one shall check binding elements in AssertServer’s web.config for SOAP interface timeout. But for validation a longer timeout may be defined. Publication is also a long running operation, but it is run as an asynchronous operation, so it has no SOAP timeout.
...