Last modified on 22 August 2016, at 05:51

Injection Management

Revision as of 05:51, 22 August 2016 by KNO (Talk | contribs) (→‎See also)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The Injection Manamgent in UBIK® features the possibility to extend the standard functionality of UBIK® if necessary. The system can include project a/o customer specific implementations (like own Workflow activities) and supports a UBIK® administrator to manage project a/o customer specific requirements.

Supported Applications

Following UBIK® Applications support the Injection Management:

Supported Types

Two types of add-ons can be injected into UBIK® via this Injection Management techique:

  • UBIK® Plugin
  • UBIK® Module


An UBIK® Plugin is intended to provide features on a rather low level (methods used within code, workflow activities, web service). The scope of a plugin should not cover additional structures (Metaclasses, Metaproperties, Classifications).

An UBIK® Module can also include any kind of metastructures, additional to features as a UBIK® Plugin. Hence, a UBIK® Module is a much more comprehensive extension of the system.

Injection Folder(s)

Following folders are scanned for available plugins / modules:

  • [UBIK Installation Folder]\Injection
  • %LocalAppData%\Augmensys\UBIK\CUSTOM\[Project Folder]\Injection

These folders must be set in the privatePath parameter of the probing element in the config file:

<runtime>
   <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <probing privatePath="lib;Injection"/>
   <assemblyBinding
</runtime>
IC Attention.pngThe injection of plugins / modules requires that this folder is configured as probing path in the config file.

Loaded Plugins / Modules

A list of all currently loaded and available Plugins and Modules is shown in the View → Plugins dialog (UBIK® Studio only).

See also