GitHub user adityaluffy added a comment to the discussion: How to handle Workflows/Pipelines via REST API on Windows?
Hi Marvin, Thanks a lot for the detailed guidance β the approach with the separate project and environment configuration worked perfectly π ### What I ended up implementing Based on your suggestions, I set up the following: * Created a dedicated project (`default`) and environment (`Development`) for remote execution * Configured an **Async Web Service** in metadata: * Service name mapped to the workflow * Set up `hop-server-config.xml` with basic authentication (port 8181, username/password) * Started Hop Server with the project context: --> hop-server.bat -e Development -j default config\hop-server-config.xml ### Results Everything is working as expected: - Triggering workflows via REST API: http://localhost:8181/hop/asyncRun/?service=test-service - Async execution returns execution IDs for tracking ### Question about service management patterns My real project has a **fairly complex structure**: * Multiple parent workflows * Each parent workflow calls several child pipelines * Some workflows call other workflows * Nested dependencies like: workflow β workflow β pipeline β pipeline Given this setup, whatβs the recommended way to manage Async Web Services? --> Create a separate Async Web Service for each *parent workflow* that should be exposed as an API endpoint --> Do you add or register the workflow or pipeline through the URL? Thanks again β really appreciate the help! GitHub link: https://github.com/apache/hop/discussions/6264#discussioncomment-15477115 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
