Reusable Application Templates
Learn how to publish the business system deployed by users to the application market provided by Kato through the documentation, and become a reusable application template.
The significance of this is that after the user’s own business system is released as a solution:
Other users within the enterprise can quickly copy this solution by installing application templates from the application market.
Application Template supports Online Delivery and Offline Export/Import, software can be delivered in these two ways.
Through practical operation, learn how to make reusable application templates by yourself, the application market finally provides enterprises with the ability to replicate.
Complete Deploy a service component from source code to get Java Demo Example.
Complete Deploy an application from the application market to get Mysql5.7 (stand-alone version).
Complete Establish dependency to get a complete solution example.
Next, let’s publish the application (the business level can be regarded as a complete solution) composed of Java demo example + Mysql5.7 (stand-alone version) as an application template.
Publish Application Template
Click Release in the left column of the application topology page to enter the Release Record Management page.
Click Publish to App Market to enter the App Template and Release Version Settings page.
Select or create an application template. If you create it, you must define the name of the application template** and the scope of sharing** (define the visible range of the application template, which is only visible to the current team or the enterprise).
Define version number, use a numeric definition such as 1.0, and follow up to determine the new and old version based on the size of the version number.
If necessary, fill in version alias (such as production version, pre-release version, etc.), version description (brief description).
Define the detailed settings of each component in the template in Release Component Model Configuration, including connection information, environment variables, and scaling rules.
Click Submit to enter the application synchronization page.
In this page, Kato will automatically synchronize applications, including image packaging and push. The user only needs to wait for the synchronization to be completed and see the following situation, that is, the synchronization is completed.
- Click Confirm Sharing to complete the release of the application template.
Application Template Display
Once the application template is successfully published, it will appear on the page of the application market. Depending on the publishing range selected when creating the application template, the visible range of the application template is different.
- If you select Team as the release range, we can only find the app template under the team tab that released the app template.
- The release range can only be found under the enterprise tab if you select Enterprise, otherwise it will not be visible. When the sample application template is released, the release scope is selected as Team, so it cannot be displayed on the corporate page.
Corresponding to the visible range, the current application template can only be installed in the team used at the time of release. Only when the release scope is Enterprise, the application template can be installed and used in all teams under the current enterprise.
Edit Application Template
The created application template can be edited. The edit entry is shown in the figure below:
Editable content includes:
Name, the name of the application template.
The scope of release can be modified to specified team or current enterprise.
Classification tags, adding tags can quickly classify and filter application templates.
Description, a brief introduction to the current application template.
LOGO, you can upload a picture as the logo of the application template.
Whether to release, a special label indicates the development status of the current application template.
Install Application Templates
This step is the same as deploy an application from the application market. The purpose is to verify whether the published sample application template can be installed successfully.
For specific operations, you can review the operations in deploy an application from the application market, which will not be repeated here.
The final effect is to replicate a new application based on the application market.
Next, we will explore how to upgrade the sample application template and apply the upgraded content to new applications copied from the application market.