Shulou(Shulou.com)06/03 Report--

This article focuses on "how to configure zero code development software component management", interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let the editor take you to learn "how to configure zero code development software component management"!

Silver bullet Valley Zero Code Development platform: all the components used by the application server and the content related to the components are in this menu.

1. Local component management

This menu lists basic information about all the artifacts in the application server.

It includes system components and user components.

Each component has its own function button.

System components: stop, update, download.

User widget: stop, update, download, uninstall.

Description of component status:

UNINSTALLED (uninstalled)

INSTALLED (installed)

RESOLVED (resolved)

STARTING (starting)

STOPPING (stopping)

ACTIVE (activated)

Click the component name to expand the details of the component.

View the list of user components: because of the large number of system components, this button allows you to quickly locate user components.

View a list of abnormal components: view all components except that the component status is ACTIVE (active).

Install / update: custom .jar artifacts can be installed and updated.

Bulk install / update: bulk install and update custom .jar artifacts.

A compressed package composed of multiple .jar artifacts in zip format.

two。 Deployment permission Settings

The function of this module is to dynamically set whether deployment permissions should be enabled or not.

Check: verify permissions. That is, the account that logs in to the application designer must be the same as the account that started the application server in order to publish business components to this application server.

Do not check: do not verify permissions. That is, all the application designers logged in by accounts can publish business components to this application server.

3. Power platform component warehouse

The function of this module is to install and update specified components from vstore.

Note: after installing or upgrading components under this module, the service needs to be restarted to take effect.

Enter the module and show a list of components.

You can switch between the configuration Class widget and the Code Class widget.

Select the component library that needs to be installed and upgraded, and use stable version (release) to install and upgrade.

Note: the development library or test library is unstable, install and upgrade carefully!

Check to set up a common library for easy selection.

Fuzzy search component identification and quick filter component buttons.

1. Single component operation

Each component has its own function button.

Installation: components that exist in vstore but are not yet installed in the application server can be installed by clicking the install button.

During installation, the dependencies of components are analyzed and a list of dependent components is displayed to determine whether to install or not.

Upgrade: components that have been installed in the application server, and there is an updated version in vstore, you can click the upgrade button to upgrade the components.

When upgrading, the dependencies of components will be analyzed first, and the list of dependent components will be displayed to determine whether to upgrade or not.

View dependencies: view the dependencies of the current component.

View historical versions: view a list of historical versions of the current component.

two。 Batch operation

You can install and upgrade multiple components through "batch installation" and "batch upgrade".

Enter the component ID in the input box (enter to wrap each line), for example:

Com.toone.v3.platform-01core

Com.toone.v3.platform-08util

Click the button "Select according to the input list", and the relevant components will be checked.

Or, after you find the component yourself, check it manually.

Click the "start batch upgrade" or "start batch installation" button to bulk install and upgrade multiple components.

Note: it is not recommended to switch libraries to install upgrade components under this module. If it is really necessary, after switching the library, install the updated components under "batch installation" or "batch upgrade".

4. Dynamic installation of components (dynamic upgrade)

The function of this module is to dynamically install and update specified components from vstore.

The mode of operation is the same as that of 3 power platform component warehouse

Dynamic installation and upgrade: it means that the component can take effect immediately after installing the update, and there is no need to restart the service to take effect.

Of course, not all components can support dynamic installation and dynamic upgrade.

For "configuration class" artifacts, they generally take effect dynamically.

For "code class" artifacts, in general, these code artifacts of rule function controls can take effect dynamically, while those that generally have service definition service dependencies may not take effect immediately.

Note: this module is generally provided to developers.

Maintainers of the system do not recommend using this module alone or under the guidance of developers.

5. Private inventory management

The operation of installing and upgrading private library components in the new way of private library list.

Select the project and phase.

Select the required list and install.

View the artifacts in the list.

6. Private inventory management (old)

The operation of installing, upgrading and deleting private library components in the old way of private library list.

Select your private library, select the required list, and install it.

View the artifacts in the list.

7. Cluster component installation update

The function of this module is to support the installation of update artifacts in a cluster environment.

If the update component is installed on one node in the cluster environment, it will be automatically distributed to each node to install the update component.

Of course, this module is also available if it is not in a clustered environment, so it just installs the update artifacts on this service.

Install / update: custom .jar artifacts can be installed and updated, radio.

Bulk install / update: bulk install and update custom .jar artifacts.

A compressed package composed of multiple .jar artifacts in zip format.

Note: the zip package is either full of code artifacts or all business artifacts, so don't mix them up.

During the installation of the update, you can click the button to refresh to view the results of the installation update.

At this point, I believe you have a deeper understanding of "how to configure zero code development software component management". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.