B2B Integration 10.2 | Administering and Monitoring B2B Transactions | Service Development Help | Working with Document Types | About Synchronizing Publishable Document Types | Combining Synchronization Action with Synchronization Status
 
Combining Synchronization Action with Synchronization Status
The effect of a synchronization action on a publishable document type or a provider definition depends on the synchronization status of the publishable document type. The following table describes the result of the push or pull action for each possible document type status.
Note: You can only pull from the messaging provider when the publishable document type uses Broker as the messaging provider.
Status
Action
Result
Updated Locally
Push to Provider
Updates the provider definition with changes made to the publishable document type.
Pull from Provider
Restores the publishable document type to the previously synchronized version. Any changes made to the publishable document type are overwritten.
Updated on Provider
Push to Provider
Restores the provider definition to the previously synchronized version. Any changes made to the provider definition are overwritten.
Pull from Provider
Updates the publishable document type with changes made to the provider definition (Broker document type).
Updated Both Locally and on the Provider
Push to Provider
Updates the provider definition with changes made to the publishable document type. Any changes made to the provider definition prior to synchronization are overwritten.
Pull from Provider
Updates the publishable document type with changes made to the provider definition (Broker document type). Any changes made to the publishable document type prior to synchronization are overwritten.
Created Locally
Push to Provider
If no associated provider definition exists, this action creates an associated provider definition. If an associated provider definition already exists, this action updates the definition with the changes in the publishable document type.
Note: If publishable document types for this provider definition exist on other Integration Servers, this action changes the synchronization status of those publishable document types to Updated on the Provider.
Pull from Provider
If an associated provider definition exists, this action establishes the association between the document type and the provider definition. If changes have been made to the provider definition, this action updates the publishable document type as well.
If an associated provider definition does not exist, this action deletes the publishable document type.
Note: If publishable document types for this provider definition exist on other Integration Servers, this action does not affect the synchronization status of those publishable document types.
Removed from Provider
Push to Provider
Recreates the provider definition.
Pull from Provider
Deletes the publishable document type.
In Sync with the Provider
Push to Provider
Pushes the publishable document type to the messaging provider. Even though no changes were made to the provider definition, if other Integration Servers contain publishable document types associated with the provider definition, the status of those publishable document types becomes “Updated on Provider”.
Tip: If a publishable document type is in sync with the provider definition, set the action to Skip.
Pull from Provider
Updates the publishable document type with the provider definition even though no changes are made.
Tip: If a publishable document type is in sync with the provider definition, set the action to Skip.
Note: For a publishable document type created for an adapter notification, you can select Skip or Push to Provider only. A publishable document type for an adapter notification can only be modified on the Integration Server on which it was created.

Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.