Synchronization Actions
When you synchronize document types, you decide for each publishable document type whether to push or pull the document type to the messaging provider. When you push the publishable document type to the messaging provider, you update the provider definition with the publishable document type on your Integration Server. When you pull the document type from the messaging provider, you update the publishable document type on your Integration Server with the provider definition.
The following table describes the actions you can take when synchronizing a publishable document type.
Action | Description |
Push to Provider | Update the provider definition with information from the publishable document type. |
Pull from Provider | Update the publishable document type with information from the provider definition. Note:
You can only pull from the messaging provider when the publishable document type uses Broker as the messaging provider. |
Skip | Skip the synchronization action for this document type. (This action is only available when you synchronize multiple document types at one time.) |
Integration Server does not automatically synchronize document types because you might need to make decisions about which version of the document type is correct. This is especially true when using Broker as the messaging provider. For example, suppose that Integration Server1 and Integration Server2 contain identical publishable document types named Customer:getCustomer. These publishable document types have an associated Broker document type named wm::is::Customer::getCustomer. If a developer updates Customer:getCustomer on Integration Server2 and pushes the change to the Broker, the Broker document type wm::is::Customer::getCustomer is updated. However, the Broker document type is now out of sync with Customer:getCustomer on Integration Server1. The developer using Integration Server1 might not want the changes made to the Customer:getCustomer document type by the developer using Integration Server2. The developer using Integration Server1 can decide whether to update the Customer:getCustomer document type when synchronizing document types with the Broker.
Note:
For a subscribing Integration Server to process an incoming document successfully, the publishable document type on a subscribing Integration Server needs to be in sync with the corresponding document types on the publishing Integration Server and the messaging provider. If the document types and/or provider definition are out of sync, the subscribing Integration Server may not be able to process the incoming documents. In this case, the subscribing Integration Server logs an error message stating that the “Broker Coder cannot decode document; the document does not conform to the document type, documentTypeName.”