We are deploying a TW application in the Windows GUI at several of our customers.
Indicium is handling some background tasks, amongst other printing.
These tasks involve frequent polling of the SQL database.
Default, we deploy Indicium as a service for the background tasks because this is more simple and has less impact than a IIS installation with Indicium.
However, some of our customers also want to use the TW API for accessing the application database. So at these customers, we need to install and configure IIS for Indicium.
Should and can we, in those cases, then uninstall Indicium as a service, to avoid double handling of the background tasks? Or does the IIS Indicium process recognize that some roles (background tasks) beside API are handled by a second Indicium instance (the service instance)?
At least, I want to prevent double polling of the SQL database.
Solved
Indicium both as IIS- and service process?
+1- Sidekick
- 12 replies
This topic has been closed for comments
+1- Sidekick
- 12 replies
Hi
Yes, I think this answers my question 😊 !
Just to check:
when I include the ‘Agent/Enabled:false’ JSON code for the Indicium instance running under IIS, I can leave Indicium as service running for the scheduled system flows since the IIS instance will only handle the API requests. Right?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.