Deployment, redeployment, and solution upgrades

How you deploy a solution and upgrade it depends on the type of the target server. The type of server that you use depends on whether your solution is in a development, test, or production stage.

Single-server development environment

You can test that a solution works as expected by deploying it on cisDev or another single-server development environment. Depending on the results of your test, you might want to redeploy or upgrade your solution for further testing.

Table 1. Single-server development environment
   
Deploy a new solution The most convenient way to deploy a solution and solution connectivity on a test server is from Insight Designer. To do so, you must create a deployment configuration for each solution.

You can also deploy a solution by using commands: To deploy a solution, export the .esa archive and then use the solutionManager script. If your solution contains connectivity, you must also use the connectivityManager script.
Redeploy a solution If a version of your solution is deployed, you can deploy a modified solution with the same solution version number (example: my_solution-v1.0) by using a saved deployment configuration in Insight Designer. Alternatively, you can use the solutionManager redeploy command without changing the name and version of your solution (my_solution-v1.0). You can also use the deploy command if you do not have a running test on the solution.
Upgrade a solution A version of your solution is deployed, and you want to deploy in its place a modified version of the solution. To upgrade your solution (example: my_solution-v1.0), increment the solution number and then use a saved deployment configuration in Insight Designer.

You can also use the solutionManager deploy command to deploy the new version of your solution (example: my_solution-v2.0).

If you want to change the connectivity configuration, to add a new endpoint for example, upgrade the solution with the modified connectivity configuration (.cdef), export the solution archive (.esa file), and then run the connectivityManger deploy command to activate the new endpoint. To remove an unwanted endpoint, update the generated connectivity configuration (.cdef) and then run the connectivityManager deploy command to deactivate the endpoint. You can remove the endpoint from the solution connectivity configuration when you next upgrade the solution.

Multiple server test environment

After you complete tests in the development phase, you can test your solution in a multiple server environment.

Table 2. Multiple server test environment
   
Deploy a new solution To deploy a solution, export the .esa archive and then use the solutionManager script on each runtime server in a topology. If your solution contains connectivity, you must also use the connectivityManager script on the servers that host your inbound and outbound connectivity.
Redeploy a solution To redeploy the same solution version (example: my_solution-v1.0), use the solutionManager redeploy command without changing the name of your solution (my_solution-v1.0).
Upgrade a solution A version of your solution is deployed, and you want to deploy in its place a modified version of the solution. To upgrade your solution, increment the solution version number in Insight Designer (example: my_solution-v2.0). Use the solutionManager deploy command to deploy the new version of your solution to each runtime server in your test environment. Activate the new version of your solution from any one of the runtime servers by using the solutionManager activate command.

If you want to change the connectivity configuration, to add a new endpoint for example, upgrade the solution with the modified connectivity configuration (.cdef), export the solution archive (.esa) file, and then run the connectivityManger deploy command to activate the new endpoint. To remove the endpoint, update the solution connectivity configuration (.cdef) and then run the connectivityManager deploy command to deactivate the endpoint. You can remove an endpoint from the connectivity configuration when you next upgrade the solution.

Multiple server production environment

When you are confident that your solution works as you expect it to, you can deploy it to a production server.

Table 3. Multiple server production server
   
Deploy a new solution To deploy a solution, export the .esa archive and then use the solutionManager script on all of the runtime servers in your topology. If your solution contains connectivity, you must also use the connectivityManager script on the servers that host your inbound and outbound connectivity.
Upgrade a solution A version of your solution is deployed, and you want to deploy in its place a modified version of the solution. To upgrade your solution, increment the solution version number in Insight Designer (example: my_solution-v3.0), use the solutionManager deploy command to deploy the new version of your solution to each runtime server in your production environment. Activate the new version of your solution from any one of the runtime servers by using the solutionManager activate command.

If you want to change the connectivity configuration, such as to add a new endpoint, upgrade the solution with the modified connectivity configuration (.cdef), export the solution archive (.esa) file, and then run the connectivityManger deploy command to activate the new endpoint. To remove an unwanted endpoint, update the generated connectivity configuration (.cdef) and then run the connectivityManager deploy command to deactivate the endpoint. You can remove the endpoint from the solution connectivity configuration when you next upgrade the solution.