Deployed document types and metadata

Document types and metadata are configured in Design Center as described in the previous sections. When a Project is exported and deployed to a StreamServer application, all document types are stored the enterprise repository.

A schematic example of a document type stored in the enterprise repository is illustrated below.

<?xml version="1.0"?> <documentType ... name="doctypeInvoice" guid="..." revision="2"> <metadataGroup name="STATIC" guid="STATIC"> <metadataTypes> <metadata name="..." scope="..." type="..." guid="..." archived="false" message="false" default="true" postprocess="false"/> ... </metadataTypes> </metadataGroup> <metadataGroup name="Customer Data" guid="..."> <metadataTypes> <metadata name="Customer Number" scope="" type="xs:double" guid="..." archived="true" message="false" default="true" postprocess="false"/> <metadata name="Customer Name" scope="" type="xs:string" guid="..." archived="true" message="false" default="true" postprocess="false"/> </metadataTypes> </metadataGroup> </documentType>

The document types stored in the enterprise repository are the “master document types” that determine which document type and metadata information to store in the runtime repositories and Collector archives.

When deploying, the document type information in the exported Project is checked against the document type information stored in the enterprise repository. If any document types are modified before the export, a warning is issued before the document types are updated in the enterprise repository.