Introduction to SonataFlow development
This guide showcases the SonataFlow Workflow CLI plugin and Apache KIE Serverless Workflow Visual Studio code extension to create, run & deploy SonataFlow projects on your local environment and walks you trhought the recommended development loop of workflow applications.
-
You have set up your environment according to the minimal environment setup guide.
Creating a workflow project with KN CLI
Use the create
command with kn workflow to scaffold a new SonataFlow project.
-
Navigate to your development directory and create your project.
kn workflow create -n my-sonataflow-project
-
This will create a folder with name
my-sonataflow-project
and a sample workflowworkflow.sw.json
cd ./my-sonataflow-project
-
Open the folder in Visual Studio Code and examine or the created
workflow.sw.json
using the editor provided by the extension.code workflow.sw.json
Now you can run the project and execute the workflow.
Running a workflow project with KN CLI
Use the run
command with kn workflow to build and run the SonataFlow project locally in development mode.
-
Run the project.
kn workflow run
-
The Development UI will be accessible at
localhost:8080/q/dev
-
You can now work on your project. Any changes will be picked up by the hot reload feature.
-
See Workflow instances guide on how to run workflows via Development UI.
-
Once you are done developing your project navigate to the terminal that is running the
kn workflow run
command and hitCtrl+C
to stop the development environment.
-
You can use any editor to develop your workflow to suit your use case. We recommend getting familiar with Serverless Workflow Specification and guides in Core
chapter first.
-
To test your running workflow project, access the Swagger UI on
localhost:8080/q/swagger-ui
to examine available endpoints. -
In order to execute the workflow once, run:
curl -X 'POST' \ 'localhost:8080/hello' \ -H 'accept: */*' \ -H 'Content-Type: application/json' \ -d '{ "workflowdata": {} }'
-
You should see a similar response:
{"id": "<UUID>", "workflowdata" : {"message":"Hello World"}}
To deploy the finished project to kubernetes cluster, proceed to the next section.
Deploying a workflow project with KN CLI
-
You are logged into your kubernetes cluster or started one locally according to the starting cluster for local development guide.
-
You have installed SonataFlow Operator in your kubernetes cluster according to operator installation guide.
Use the deploy
command with kn workflow to deploy the SonataFlow project into your local cluster.
-
Create a namespace for your application
kubectl create namespace my-sf-application
-
Deploy the workflow to the cluster in the default
dev
mode. The plugin uses settings located in./<home>/.kube/config
to access the cluster.kn workflow deploy --namespace my-sf-application
-
In a separate bash instance create a port mapping:
oc get route svc/hello --namespace my-sf-application
-
On openshift the route is generated for you in
dev
mode deployments. Use the URL of the generated route to access your workflow instances using the Developement interface.-
<RETURNED_URL>/q/dev-ui/org.apache.kie.sonataflow.sonataflow-quarkus-devui/workflows
-
minikube service hello --namespace my-sf-application --url
-
Use this URL to access your workflow instances using the Developer UI
-
<RETURNED_URL>/q/dev-ui/org.apache.kie.sonataflow.sonataflow-quarkus-devui/workflows
-
# Execute kubectl get services -n my-sf-application # You should see output like this, note the ports NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE hello ClusterIP 10.96.0.1 <none> <RANDOM_PORT>/80 39s # Execute kubectl port-forward service/hello <RANDOM_PORT>:80 -n my-sf-application
-
-
To update the image, run the
deploy
again, note that this may take some time. You can also direcly edit theSonataflow
resource in the cluster. Indev
mode, the operator will update the deployment with the changes.
-
-
To stop the deployment, use the
undeploy
command:kn workflow undeploy --namespace my-sf-application
Testing your workflow application
To test your workflow application you can use any capable REST client out there. All that is needed is the URL of your deployed workflow project, which is showcase in section above, You can also use the management console provided as part of the development interface. Please see the additional resources to proceed.
Found an issue?
If you find an issue or any misleading information, please feel free to report it here. We really appreciate it!