Step 6: (Optional) Update an Application Version

you can update an application version in the primary marketplace catalog and initiate a sync from the secondary marketplace catalog to pull the new changes before you begin make sure to finish steps 1 step 5 of deploy edge applications to multiple sites using marketplace catalog sync docid\ z8r 5mvu1pezfxvsenhqu before proceeding step 6a add new application release version in primary catalog to add a new application release version in the primary catalog go to the primary marketplace catalog you created in step 1 create primary catalog with list of applications docid\ qbozmpgvaqv8 jm5vyv and select analytics application to add a new release version click the + icon to open the add release dialog box enter a suitable name for the release enter a description for the release version enter a readme for the release version click save you can add launch variables or docker container configurations to the draft application release see step 3 step 5 in add a draft application release docid\ pujqcf4jl0due8xjhsjmz note a docker application release is always in one of two states released (submitted) or draft when a docker application release is in a released state, it cannot be further modified likewise, when it is in draft , it can be modified in this guide and in real world settings, it is recommended that the secondary site always syncs to the draft application release to allow for further modifications specific to their site needs step 6b synchronize the secondary catalog to the primary catalog once the primary site (canada) uploads the new version of the application into the primary catalog, the secondary site (japan) manually initiates a sync with the primary catalog to pull the new application version to synchronize the secondary catalog with the primary catalog using the new application release version from the secondary marketplace catalog's synchronization page, navigate to the synchronization secondary catalog pane click sync to pull the new version updates in the catalog note there is no need for approval of a primary catalog sync request this time a secure connection has been established using a bootstrap file in step 3 establish secure connection between primary and secondary catalog docid\ s8jgesigupfpehtdb cfv to verify if the application(s) have received the new release version, go to the applications pane in the secondary marketplace catalog and confirm the release update note to make changes to the pulled release version before deploying it to the edge device, see manage application releases docid\ fozmtmxkxei6y gpzaevg