Designer 10.7 | webMethods Service Development Help | Working with Publishable Document Types | About Synchronizing Publishable Document Types
 
About Synchronizing Publishable Document Types
 
Synchronization Status
Synchronization Actions
Combining Synchronization Action with Synchronization Status
Synchronizing a Single Publishable Document Type
Synchronizing Multiple Document Types Simultaneously
Synchronizing Document Types in a Cluster
Synchronizing Document Types Across a Gateway
Importing and Overwriting References During Synchronization
When you synchronize document types, you make sure that a publishable document type matches its associated provider definition. You will need to synchronize document types when:
*You make changes to the publishable document type, including changes to the messaging properties of the publishable document type.
*You made a document type publishable when Integration Server was not connected to the messaging provider (Broker or Universal Messaging).
*You install packages containing publishable document types on Integration Server.
*You make changes to the Broker document type. (This is usually the result of a developer on another Integration Server updating that server’s copy of the publishable document type and pushing the change to the Broker document type.)
*You change the client group for the Broker messaging connection alias.
When using Broker as the messaging provider, document type synchronization makes it possible to propagate changes to a publishable document type across multiple Integration Server by doing the following:
1. Make changes to the publishable document type on one Integration Server.
2. Push those changes to Broker, which updates the Broker document type associated with the publishable document type.
3. Update the publishable document type on another Integration Server by pulling the changes from the Broker.
When using Universal Messaging as the messaging provider, the work flow for propagating publishable document type changes to other Integration Servers is as follows:
1. Make changes to the publishable document type on one Integration Server.
2. Push those changes to Universal Messaging, which updates the Universal Messaging channel associated with the publishable document type.
3. Use package replication or webMethods Deployer to update another Integration Server with the modified publishable document type.
Note: 
Integration Server can only push publishable document type changes to the provider definition on Universal Messaging. Integration Server cannot pull changes made to the provider definition on Universal Messaging.
Related Topics
Synchronization Status
Synchronization Actions
Combining Synchronization Action with Synchronization Status
Synchronizing a Single Publishable Document Type
Synchronizing Multiple Document Types Simultaneously
Synchronizing Document Types in a Cluster
Synchronizing Document Types Across a Gateway
Importing and Overwriting References During Synchronization