Appendix A: Custom Workflow Development Guidelines : Orchestrated vCloud Environments : Developer Environment
Developer Environment
The recommended development environment is as follows:
*Allocate one development server per developer. Sharing a single development server among different developers is not recommended for the following reasons:
*The server may have to be restarted to install or upgrade plug-ins under development, thus creating downtime.
*The server may have to be configured for a particular environment for a given developer.
*Two or more developers hanging the same element—for example, editing a workflow—at the same time is not supported and can result in data being overwritten.
*Use the developer workstation as the vCenter Orchestrator development server:
*Provides integration within the development tool chain. For example, the plug-in development environment.
*The vCenter Orchestrator client used to develop the workflows relies on its connection to the server. If the network connection is lost, the changes since the last save are lost.
*For unit testing purposes, the developer server should be configured in a vCloud development environment, with the components defined in the reference architecture plus additional integrations as required. This can either be a simple, small environment for each developer or shared among developers. Ideally, this environment should be local, but it can be remote. For example, a vCenter Orchestrator client and server can be installed on a laptop and used to connect to vCloud Director over a WAN.
*The vCenter Orchestrator client is not optimized for connecting to a vCenter Orchestrator server over a WAN or through a firewall. If remote access to a vCenter Orchestrator server is required, use Remote Desktop Connection (RDC) to start a vCenter Orchestrator client installed on the same server as the vCenter Orchestrator server.