App Delivery via App Market


After the enterprise selects Kato as the production delivery platform, how to deliver the developed application to the end user’s production environment has become a very important topic. Through the actual testing process, this article explains how to deliver applications through the Kato application market, and how to synchronize the upgraded content to other applications that have been deployed through the original version of the application market after the original application has been upgraded.

Based on the Process of Kato Application Market Delivery

Prepare in Advance

Two sets of Kato environments are required to complete this operation. One set is used as an application release platform for application release and upgrade; the other set is used as a deployment platform, where we will export/import market applications offline to achieve application delivery and upgrade operations.

At the time of this writing, two sets of Kato v3.7.2 were built as test environments to demonstrate and verify application delivery and upgrade through the application market.

Application Release and Export

This test selected a spring boot project based on Maven. It is combined with mysql to form a complete application. Next, publish it as an application in the application market and export it as a package. The [Test Application Package] ( exported this time is provided here for users to test .

Application Package Import

Next, we will import the application package we just exported in a new environment. This process corresponds to a delivery scenario based on the Kato application market in an offline environment.

After the import is complete, you can use Build from App Market to build the imported package into an application. The application delivery based on the Kato application market is complete.

Application Market Upgrade Operation

Application Re-release

How can I upgrade an application that has been released to the application market? This involves repeated releases of the same application. Here is an important point:

Don’t delete the original application after publishing the application to the application market. Future upgrades will be adjusted based on the original application. After the adjustment is completed, republish to the application market to complete the application upgrade in the application market.

Next, still based on spring boot, complete an upgrade operation. Before starting, deploy an application app_delivery as a test case through the unupgraded application market; and add a mark file new_file_for_test to the application source code repository to simulate the application source code changes.

After the addition is complete, rebuild to upgrade the original application

Re-release to upgrade apps in the app market

It should be noted that when re-publishing the same application, the version should be consistent with the original application to be considered as an upgrade to the original application; otherwise, a new application will be released.

Upgrading of applications deployed in the application market under the same Kato

For the application app_delivery deployed with the first version of the application in the application market, after the application is republished, the upgrade operation can be carried out. Kato will automatically detect the version of the application market application and reflect the application upgrade button.

Enter the container view from the application control interface –> Manage Container

Application market application upgrade under different Kato

For other Kato environments that have been delivered, how do we upgrade in the delivery environment after upgrading the application? We need to re-export the application, and then import it into the delivery environment. The export method and introduction have been introduced. Here is the exported Test Application Upgrade Package for users to test.

After successfully upgrading the application market application, the application that has passed the original version can be upgraded.