Impact on the Target Instance Due to Application Synchronization

As per the App Volumes application synchronization behavior, changes to the applications and packages on the source App Volumes instance are synchronized to the target App Volumes instance. The information presented here helps you understand how these changes affect the target instance.

To understand the application synchronization behavior, see Configure Multiple App Volumes Instances for Application Synchronization and Criteria for Application Synchronization.

Changes on the App Volumes Source Instance	Impact to the App Volumes Target Instance
A new application is created and packaged on the source Note: Only captured packages are replicated. Packages in Unpackaged or Packaging status are not replicated.	Replicated package from the source is available on the target after an import Note: Such applications and packages can be managed only from the source instance. For more information about managing applications packages from the source, see Manage a Synchronized App Volumes Application at the Source.
An application package is imported to the source	If the application does not exist on the target, the impact on the target is similar to when a new application or package is created on the source. If the application already exists on the target, the package and the corresponding application are automatically in a synchronized relationship with the source. Note: Applications and packages in a synchronized relationship can be managed only from the source instance. For more information about managing applications packages from the source, see Manage a Synchronized App Volumes Application at the Source.
An application or package is edited	Application and package are updated on the target (s) to match the source.
An application or package is deleted	If the synchronization relationship exists, application and package also are deleted on the target For more information about the synchronization behavior, see Delete a Package and Delete an Application.
A package is moved from one application to another application	Package moves to the destination application if the application exists on the target. If the application does not exist on the target, then the source instance creates that application on the target and then the package move is synchronized to the target.