Walkthrough: Deploying a UCMA Communications Workflow Application
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
To deploy a single Microsoft Unified Communications Managed API communications workflow application in a non-redundant deployment model, place the application executable on the same computer where the application was provisioned.
The application executable should not run on a computer running Microsoft Office Communications Server.
The prerequisites for the computer where a communications workflow application is installed are nearly the same as for a computer where those applications are developed. The one difference is that Microsoft Visual Studio 2008 development system is not required. For a list of prerequisites, see Walkthrough: Debugging a Communications Workflow Application.
To deploy a communications workflow application
Create the application. For more information, see Walkthrough: Hello World.
Provision and debug the application. For more information, see Establish Accounts on Office Communications Server and Walkthrough: Debugging a Communications Workflow Application.
Place the application executable on a computer other than the Office Communications Server computer. Some of the provisioning information is computer-specific and needs to be changed if the application is moved to a different computer for deployment. If the application is moved, provision the new computer, change the variables in Program.cs as needed, and then rebuild the application.