Modifying the Design Center Project > Deploying a new version of the Project

Deploying a new version of the Project
To make sure that Project modifications are not applied to any paused Messages in the Message storage, you can create a new, modified version of the Project and deploy this version to a separate StreamServer application in the application domain. For example, if you update a text in the StoryTeller document, but want already paused Messages to be completed with the original text.
You can then preview and release already paused Messages based on the original Project version, and at the same time create new documents based on the updated Project version.
To deploy a new version of the Project
See Deploying a new version of the Project in the Composition Center documentation.
Consequences for new documents
The Project modifications are applied to all future documents.
When increasing the Project version, the versions of all included StoryTeller templates are also increased. After starting the new StreamServer application, all document definitions based on these templates are automatically unpublished.
When the business user republishes a document definition, the document definition is tied to the StreamServer application that runs the latest Project version. This StreamServer application is the only one that can create new documents based on the document definition.
Note:
Note:
Consequences for already paused Messages
As long as the StreamServer application that originally created a paused Message is running, you can preview and release the Message using the original document definition based on the original StoryTeller template. No changes to the Project are reflected in the output.
Note:
OpenText StreamServe 5.6 Updated: 2013-03-01