Versioning of services in StreamServer applications

StreamServer applications can expose services for several reasons, for example:

•	To receive requests from StreamServe web applications to preview or publish Documents.

•	To receive requests from the jobsubmit web service.

To expose services, either:

•	the Message you configure in Design Center must be service enabled, or

•	a Service Request input connector is used.

For more info on service enabling and using Service request connector, see the Design Center documentation.

If you want to make changes to a Project that already has been deployed to a StreamServer application, you can let separate StreamServer applications run different versions of the Project, where the services exposed by each application have the same version as the Project. This means that:

•	The web application (or an application using the jobsubmit web service) can send requests to the correct version of the exposed services, thus documents are rendered using the correct version of the StreamServer application.

•	Halted messages in the Message store can be previewed and published with correct output even if you have changed and redeployed the Project, because the specific service version used when storing the message is still exposed by one version of the StreamServer application.

To deploy a new version of the same Project, you increase the version number when exporting the Project, and deploy the new export file. See the Design Center documentation.