I'm following these instructions https://help.talend.com/reader/KxVIhxtXBBFymmkkWJ~O4Q/EkhB6yygX9efCBXfoy4KhQ and all works as expected.
However I'm wondering the best way to use this in production and in a Route?
tSAPIDocReceiver is a DI component so it would have to be called by a cTalendJob component. However, to do this I would need to have a tRouteInput before the tSAPIDocReceiver and the studio would not allow this.
If tSAPIDocReceiver can not be incorporated into a route then I guess you keep it in a DI job and run from the TAC in the usual way?
What seems a bit odd is that the tSAPIDocReceiver has 2 modes. Keep running forever or Batch.
Can you run a DI job for ever? Is this a way of making a DI job into a always listening route? And there are any issues with this or should I just go ahead and do it?
Thanks for any advice
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Learn how to use an API-First Approach to Modernize your Applications
Take a look at this technical overview video of Talend API Designer
Find out how to get started with APIs