Ask Your Question

How to run multiple pipelines using orchestration stages?

asked 2020-11-25 01:25:20 -0500

Manimars gravatar image

updated 2020-11-25 04:50:00 -0500

Hi All, We are having 10 individual pipelines that retrieve data from different API's. To execute all the pipelines at once, we have defined all the pipeline id's along with the parameters in one of the orchestration stages called Start pipeline origin. When we try validating/preview/running the pipeline we get below exception. Can someone please help me to resolve this issue?image description

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2020-12-14 15:10:44 -0500

KateF gravatar image

It seems like from the error message that the problem isn't your pipeline definitions but the execution engine. Make sure your Execution Engine URL and port are correct, and that you've entered the correct username/password on the credentials tab.

edit flag offensive delete link more


@KateF Here my data collector execution engine works for other pipelines. It's the same URL & port we defined in the orchestration stages with correct credentials. When it works for other individual pipelines why not for orchestration stages?

Manimars gravatar imageManimars ( 2020-12-20 21:28:23 -0500 )edit

Hi Manimars, it sounds like this is still not working for you? Can you add more details about under what scenarios it is working and under what scenarios it is not working?

KateF gravatar imageKateF ( 2020-12-22 16:48:33 -0500 )edit

answered 2021-01-30 23:15:49 -0500

Manimars gravatar image

Hi @KateF, Thanks for asking. Yes it's still not working for us. Here in my case, please refer the points below. 1. I'm able to create a new pipeline & we can run it successfully under the port & data execution engine url. 2. We've similar pipelines which needs to be orchestrated under one pipeline, start pipeline & start job are the stages under orchestration. 3. In the start pipeline configuration, we have provide the pipeline id, parameters, url, respective port & credentials and tried executing it. Facing the above SSL exception. 4. Similarly with the start job configuration, we have published the pipeline and we have provided the respective job id, url & credentials. Still the same issue as in point 3. 5. I'm attaching the screenshot reference for you to how the pipeline looks alike.C:\fakepath\orchestration.PNG(/upfiles/16120699794516991.png) 6. please let us know in case if you need any further details.

Thanks in advance Mani

edit flag offensive delete link more
Login/Signup to Answer

Question Tools



Asked: 2020-11-25 01:25:20 -0500

Seen: 282 times

Last updated: Jan 30