Deploying solutions

When you are ready to test your solution, you can deploy it to a development server from Insight Designer. You can also export a solution archive and then run scripts to deploy the solution and its connectivity to a development server or a production server.

In Insight Designer, you can deploy your solution only to a local Insight Server. The solutionManager and connectivityManager scripts can be used to deploy solutions to a local host or a remote host.

Deployment to a production server requires some knowledge of the topology; how many runtime servers there are and where these servers are hosted. In production, a new version of a deployed solution is placed on hold so that you can deploy the new version on all the runtime servers in the topology before you make it active. Deployed solutions are functionally isolated, regardless of whether the model contains entities that are used by other solutions. Therefore, when you increment the version of one solution it has no impact on the version of another. However, if two solutions have a view of a common customer entity for example, the information each solution has of that entity is the result of agent processing in that solution. It is possible that different agents have different values for the same entity.

In development, you can use Insight Designer or solutionManager deploy and redeploy to test your solutions without updating the version number each time you deploy a new copy of the solution.

The following diagram summarizes the paths that you can use to deploy a solution. Your choice is determined by the type of the target server.