Hi,
I have following situation:
One Master Repository with two Work/Execution repositories.
The Master repository and the Work Repository are on the same database, the second Repository - an execution repository is on a different Databbase.
We have several Agents in the Master repository, and one of them is running on a server that does not have access to the Database where the Execution repository is.
This agent is trying to connect to the Executionrepository but fails, which is causing the agent to be slowed down to an extend that he produces timeouts at most of the executions.
The question is: Is it possible to tell the agent, or ODI in general, this agent is not available for the Execution repository but only for the work repository?
The purpose of this idea is that the agent while no longer available for the Execution repository runs more stable for the work repository.
In fact I'm looking for any solution where the agent works fine for the Work Repository, regardless of how he behaves in the Execution repository.
Thanks for any thoughts tipps or advices.