Forcing document types into the repositories

Once a document type is deployed to the OpenText StreamServe repositories, there are strict rules for how the document type can be modified in Design Center. Unless these rules are fulfilled, you cannot redeploy the Project in Control Center.

However, if a modification is necessary, you can force a modified document type into the enterprise repository and the runtime repository at redeploy.

Note:

Forcing a document type into the enterprise and the runtime repositories does not affect the document type in the Collector archive.

Note:

You cannot force a document type with a revision that is older than the one in the enterprise repository.

Prerequisites

•	Make sure you have a complete backup of the runtime repository.

•	Depending on how the document type is modified, you must make different preparations. For lists of the required preparations for different types of modifications, see Changes that require database manipulation in the Document types and metadata documentation.

At the preparations, you can use Database Administration Tool. You can launch this tool directly from Control Center by right-clicking the application domain and selecting Launch Database Administration Tool.

Post requisites

If the document type contains modified metadata used in StreamStudio, the metadata in StreamStudio must be updated accordingly. For example, if the metadata is used in texts and rules in Composition Center, these texts and rules must be updated.

To force a document type into the runtime repository

1	Right-click the StreamServer application and select Redeploy. The Compare Document Types tool opens.

2	Click Force update. The Force Document Type Update dialog box dialog box opens.

3	Click Start to force the document type into the repositories.