I created a microservice pipeline with REST API Origin using the DataOps platform as per video: https://www.youtube.com/watch?v=wIZWMV1bMl4
Now, I am unable to invoke the pipeline using 3rd party tools like Postman. I have chosen default settings in SDC and headers as (X-SDC-APPLICATION-ID:sdc_microservice & Content-Type:application/json) yet I’m facing issue as “Error: connect ETIMEDOUT xx.xx.xx.xx:8000”.
However, when I use the same URL in a curl command where SDC container is running, I see, 200 OK response.
curl -i -X GET http://xx.xx.xx.xx:8000/rest/v1/user --header "X-SDC-APPLICATION-ID:sdc_microservice"
There is no connectivity issue. So, can anyone tell me why I am unable to use Postman tool or if I am missing anything here?
Below are the images showing the same:
Best answer by AkshayJadhavView original
@Kartik Medavarapu - Thank you for reaching out to the StreamSets Community.
I was able to get perform the api call from the postman application, here are the headers that I used:
Let us know how it goes.
Thank you - AkshayJ
Thank you for quick response. I have mentioned the same headers and tried, but no luck !!
We are using SDC 5.x installed as container in a local VM and SCH is DataOps platform. Any other specific env setting to be considered?
From your screenshot, I can see that postman is not able to reach to the IP address. If you are using the data collector in VM then mention the VM ip address and still it does not work then run ping <VM IP address> command to check the connectivity from host to VM is working.
Just added -p 8000:8000 in the docker startup script and send the request on 8000 port via Postman application.
Hope this helps.
Thank you - AkshayJ
@Kartik Medavarapu - Were able to perform the api call via postman to the docker host on 8000 port?
If yes, I would request you to mark the comment as best answer that will close the thread.
@AkshayJadhav - Apology for a delayed response. We tried using the “-p 8000:8000” but no luck.
Due to other priority tasks, I stopped checking on this. However, since we got the response by using curl command, we leveraged that instead. Thank you for all the support !
@Kartik Medavarapu .