Designer 10.7 | webMethods Service Development Help | Working with Publishable Document Types | About Synchronizing Publishable Document Types | Synchronizing Multiple Document Types Simultaneously
 
Synchronizing Multiple Document Types Simultaneously
You can synchronize multiple publishable document types with their corresponding provider definitions at one time. For each publishable document type, you can specify the direction of the synchronization. You can push the publishable document type to the messaging provider or pull the provider definition from the messaging provider. If you do not want to synchronize some publishable document types that are out of sync, you can skip them during synchronization.
When synchronizing multiple document types at once, you can do one of the following:
*Synchronize out-of-sync document types only. Use this option to view and synchronize all publishable document types that are out sync with their associated provider definition.
*Synchronize all publishable document types. Use this option to view and synchronize all publishable document types regardless of sync status.
Keep the following points in mind when synchronizing multiple document types at one time:
*If you want to Pull from Provider, you must have write access to the publishable document type. The publishable document type must be either unlocked, or you must have locked it yourself.
*The Pull from Provider action is available for publishable document types that use Broker as the messaging provider only. Pull from provider can be selected only when the corresponding provider definition is a Broker document type.
*When you pull document types from Broker, Designer gives you the option of overwriting elements with the same name that already exist on the Integration Server. The provider definition (Broker document type) might reference elements such as an IS schema or other IS document types. If the Integration Server to which you are importing already contains any elements with the referenced names, you need to know if there is any difference between the existing elements and those being imported from the Broker. If there are differences, you need to understand what they are and how importing them will affect any integration solution that uses them. For more information about overwriting existing elements, see Importing and Overwriting References During Synchronization.
*For a publishable document type created for an adapter notification, you can only select Push to Provider or Skip. A publishable document type for an adapter notification can only be modified on the Integration Server on which it was created.
*If the Linked to source property is set to true for the publishable document type, the action you can take depends on the source for the publishable document type. You can select:
*Pull from Provider only if the Source URI is a Broker document type.
*Push to Provider only if the Source URI is a URI other than a Broker document type.
Note:
When synchronizing multiple document types, Designer does not prevent Integration Server from overwriting publishable document types for which Linked to source is true.
*When you switch the Broker configured for Integration Server to a Broker in a different territory, Integration Server displays the synchronization status as it was before the switch. This synchronization status may be inaccurate because it does not apply to elements that exist on the second Broker.
*The result of a synchronization action depends on the document status. For more information about how the result of a synchronization status depends on the synchronization status, see Combining Synchronization Action with Synchronization Status.
*To generate additional logging information in the server log when Integration Server synchronizes document types that use protocol buffer encoding with Universal Messaging, set the logging level for the server log facility 0154 Protocol Buffer Encoding (Universal Messaging) to Debug or Trace. Increased logging can help you to locate problems that occur during protocol buffer encoding.
*To generate additional logging in the server log when Integration Server synchronizes document types with the Broker, increase the logging level for the server log facility 0097 Broker Document Type Synchronizer.
*To synchronize multiple document types
1. In Designer, do one of the following:
*To view and synchronize only out-of-sync document types, select File > Sync Document Types > All Out-of-Sync. Designer displays the Sync All Out of Sync Document Types dialog box.
*To view and synchronize all document types, regardless of sync status, select File > Sync Document Types > All. Designer displays the Sync All Document Types dialog box.
2. If you want to specify the same synchronization action for all of the publishable document types, do one of the following:
Select...
To...
Set All to Push
Change the Action for all publishable document types in the list to Push to Provider.
Note:
When you select Set All to Push, Designer sets the publication action for adapter notification document types to Skip.
Set All to Pull
Change the Action for all publishable document types in the list to Pull from Provider.
Set All to Skip
Change the Action for all publishable document types in the list to Skip.
3. If you want to specify a different synchronization action for each publishable document type, use the Action column to select the synchronization action.
Select...
To...
Push to Provider
Update the provider definition with the publishable document type.
Pull from Provider
Update the publishable document type with the provider definition.
Skip
Skip the synchronization action for this document type.
4. If you want to replace existing elements in Package Navigator view with identically named elements referenced by the Broker document type, select the Overwrite existing elements when importing referenced elements check box. For more information about importing referenced elements during synchronization, see Importing and Overwriting References During Synchronization.
5. Click Synchronize to perform the specified synchronization actions for all the listed publishable document types.
Related Topics
Synchronizing Document Types in a Cluster
Synchronizing Document Types Across a Gateway