VMware recommends several best practices for developing Orchestrator workflows by multiple users and in a clustered environment.

  • Each developer has a dedicated test standalone Orchestrator instance for creating and developing workflows.

  • Workflows are saved as maven projects on a shared source code control system.

  • To ensure optimal performance of the Orchestrator production deployment, it is best to import workflows in a scheduled window.

  • When importing workflows to an Orchestrator cluster, connect the Orchestrator client to one of the nodes by using their local host name or IP address, instead of the address of the load balancer virtual server.


    Any modifications of a workflow take effect with the next workflow run.