How to handle sync trigger misses of on-premise agent
Sync is a continuous process and with APPSeCONNECT, the sync is triggered at an interval or as per the schedule mentioned by the customer. If you are using on-premise agent and you have the necessary resources to increase parallelism, you have no option to handle it.
In this post, we will see how we can increase the level of parallelism in a machine such that the misfire could be minimized.
How to control count of Parallelism in Workflow Execution
Execution engine is called at the schedule defined by the account. Now generally to have real time update on the applications, the sync might have to be configured at an interval where a large number of workflows could execute parallelly. The requirement might become critical when the number of application increases.
Steps to increase the Thread Count of APPSeCONNECT Agent
- Open the environment where On Premise agent is installed.
- Go to C:\Program Files(x86)\Appseconnect or the installation directory where you have installed the agent.
- Open the file “InSync.eConnect.AutoSync.exe.config” file.
- Change the configuration of THREAD_COUNT to number of Cores installed multiplied by 4.
- Save changes.
The default value of THREAD_COUNT is 15, but depending on the requirement of parallelism required by the environment, you can adjust its value.
You might need to save the data to desktop and then replace the existing config file inside installation directory.
The thread count indicates the number of parallelism that an integration service can perform to operate on the tasks provided. The tasks in this case are the ProcessFlows which needs to be executed in parallel.