Difference between revisions of "HowTo:Provide system definitions with a custom plugin"
(→See also) |
(→See also) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | This tutorial explains how to provide any kind of preconfigured {{UBIK}} | + | This tutorial explains how to provide any kind of preconfigured {{UBIK}} system definitions using a custom plugin (or more specific: module). |
== General concept == | == General concept == | ||
| Line 19: | Line 19: | ||
= Big Picture = | = Big Picture = | ||
| − | The | + | The Module implementation hosts a System Definition Provider, which in turn gives access to a set of versioned System Definitions. The latter can contain any kind of {{UBIK}} data like MetaClasses, MetaProperties, instances of any type and scripts to execute when the package is installed or initialized. |
[[File:Systemdefinitions2.drawio.png]] | [[File:Systemdefinitions2.drawio.png]] | ||
| Line 1,058: | Line 1,058: | ||
* [[Injection_Management]] | * [[Injection_Management]] | ||
* [[Plugins]] | * [[Plugins]] | ||
| + | * [[UBIK_Plugin_Design]] | ||
[[Category:How-To|Provide system definitions with a custom plugin]] | [[Category:How-To|Provide system definitions with a custom plugin]] | ||
| − | |||
[[Category:Injecting|Provide system definitions with a custom plugin]] | [[Category:Injecting|Provide system definitions with a custom plugin]] | ||
| + | [[Category:Module|Provide system definitions with a custom plugin]] | ||
[[Category:Plugin|Provide system definitions with a custom plugin]] | [[Category:Plugin|Provide system definitions with a custom plugin]] | ||
Latest revision as of 07:46, 6 October 2025
This tutorial explains how to provide any kind of preconfigured UBIK® system definitions using a custom plugin (or more specific: module).
General concept
When rolling out a UBIK® customizing into a (productive) environment, there is always the challenge regarding the transportation of the data model and basic data. The sustainable solution is to deliver versioned packages of system definitions in plugins, because that allows for easy deployment and upgrade, and for the direct application of state-of-the-art software development strategies for plugin development.
UBIK® plugins are detected when an Environment is initialized, and the user is prompted with a database upgrade if necessary. The technical maintenance of the database is automatic and allows for arbitrary adaptations. The plugin developer can decide whether to make meta definitions immutable (as system design objects in the System namespace) or further customizable by the user (as regular content). Custom scripts can be executed every time the Environment is connected or just during an upgrade.
Prerequisites
To understand the code, knowledge about the UBIK® ER-model and the plugin injection mechanism is required.

