Synchronizing a Single Publishable Document Type
You can synchronize a single publishable document type with its corresponding provider definition. When you synchronize one publishable document type, keep the following points in mind:
If you want to
Pull from Provider, you need to have write access to the publishable document type and own the lock on it. For more information about locking elements and access permissions (ACLs), see
About Locking Elements and
Assigning ACLs.
When you
Pull from Provider,
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 you are importing to 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 messaging provider (
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 select
Push to Provider or
Skip only.
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.
When
Linked to source is true, the content and structure of the document type cannot be modified. For information about allowing editing of an element created from a source file, see
Allowing Editing of Derived Elements.
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 a single publishable document type
1. In Package Navigator view, select the publishable document type that you want to synchronize.
2. Select File > Sync Document Types > Selected. Designer displays the Synchronize dialog box. The Synchronize dialog box displays the synchronization status of the document type, as described in
Synchronization Status. 3. Under Action, do one of the following:
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. This option is available when the provider definition is a Broker document type only. |
4. If you select Pull from Provider, as the action, Designer enables the Overwrite existing elements when importing referenced elements check box.
5. If you want to replace existing elements in the Integration Server with identically named elements referenced by the provider definition (Broker document type), select the Overwrite existing elements when importing referenced elements check box. See
Importing and Overwriting References
During Synchronization for more information about this topic. 6. Click Synchronize to synchronize the document type and provider definition.
Related Topics