Is there someone in your team who could suggest me a better approach towards this issue.
My use case being:
I have a Camunda Application and a separate Custom Application which calls the process engine and initiates or executes BPMN related tasks using Rest API calls. Initially I continued using the inbuilt h2 database for Camunda and Sql Server database for Custom application and everything worked fine. But now I need to switch to Sql Server database for Camunda as well. And as described in the docs, when I do so I am able to successfully create a connection and use it for Camunda. But the problem arises when I also need to login to my Custom application and I am unable to do so because the sqljdbc_auth.dll(used for integrated authentication) is already in use as per the database configurations specified in the
How should I handle such a situation?
As I understand, web.xml and config.xml files can be used for specifying independent properties of applications and shareable or default properties are specified in server.xml file of tomcat server So shall I create these files for the camunda-engine provided in the Camunda Apache Tomcat distribution? How should the server.xml file be changed then? Is there any other way to avoid such an issue?
Please guide me through this because normally I would have considered this a Tomcat server issue or an SQL Server issue but in the Camunda packaged distribution, I am unable to figure out where and when the database calls are being made and hence am unable to come out with a different approach.
Your support is deeply appreciated.