Redeploying the existing version of the Project

You can redeploy the updated Project to the same StreamServer application.

To avoid versioning conflicts, you must never simultaneously run the same version of a Project, with different versions of a template, on different StreamServer applications in the same application domain.

Impact control on application level

At redeployment, Control Center compares the template versions within the updated Project to the existing template versions in the enterprise repository. The impact control is performed separately for each StreamServer application.

•	If all template versions within the Project exceed the corresponding template versions in the enterprise repository, you can redeploy the Project.

•	If a template version within the Project is lower than the corresponding template version in the enterprise repository, you cannot immediately redeploy the Project.

•	If a template version within the Project is equal to the template version in the enterprise repository, but the layout of the template differs you cannot immediately redeploy the Project.

Redeployment is not allowed

If you cannot immediately redeploy the Project, the Compare Composition Center Templates tool opens in Control Center, informing about the required actions in StoryTeller:

•	If the layout of the redeployed template is identical to the layout of the current template, you must set the template version number equal to the template version number in the enterprise repository.

•	If the layout of the redeployed template differs compared to the layout of the current template, you must increase the template version number to exceed the template version number in the enterprise repository.

To redeploy the existing version of the Project

See Redeploying a Design Center Project in the Control Center documentation.

To update the template version number

1	Start StoryTeller from within Design Center.

2	In StoryTeller, click File > Processing Properties.

3	In the Processing Properties dialog, click Composition Center.

4	In the Composition Center template version field, modify the number.

5	Save the Process, export, and redeploy the Project.

Related topics

For information about how redeploying an existing version of a Project affects already paused Messages in the Message store, see Redeploying the existing version of the Project in the Ad Hoc Correspondence and Correspondence Reviewer documentation.