Managed libraries

About managed libraries

The managed libraries feature enable you to automate the lifecycle for the provisioning of data integration libraries.  With this feature, you can:

  • Install libraries (Apache Camel components and Axway custom components, for example, Decision table) and automatically download associated jar files.
  • When a new library version is available, you can update the library and all its dependencies in one click.

The managed libraries retrieve the latest version of your libraries from a repository hosted by Axway that contains all information and items needed to guarantee the integrity and availability of the feature. 

To be able to use the Managed libraries feature, the url  should be accessible from Decision Insight.

Managed libraries repository

To access the managed library repository, on the main menu,  click Data Integration. On the left menu, click Libraries, then click the Repository button. 

The repository lists all the available managed libraries in DI. When you select a library from the list, you can see additional information: 

  • camel-version – Displays the  Apache Camel that is compatible with the managed library.
  • description – Describes the features provided by the library.
  • changeLog – Lists every modification of the managed library.

Managed libraries dependencies

One managed library can be dependent of another managed library. In that case, the dependent library is referred to as a library dependency.

When you install a manged library that has library dependencies, all the dependencies are automatically installed as well. 

Managed libraries workflow


Managed libraries

In order to use the managed libraries feature, the url: should be accessible from Decision Insight.


To install a managed library, from the Managed library repository screen, click the Install button.

All resources necessary to install the managed library and its dependencies are downloaded.

Successful library installation

After a completed installation, the icon of the managed library changes from  to .

The Details area displays the following additional information:

  • Name – The managed library name
  • Revision – The revision number
  • Dependencies – Dependencies to other managed libraries
  • Library jar files – All jar files included in the library


Managed libraries are versioned with:

  • camel-version – A managed library is compatible with one version of Apache Camel only.
  • revision – In case of security or functional updates in a managed library, a new revision is posted on the repository.

Updates are available when a new camel version is used or when a new revision of a managed library is available on the repository.

When an update is available the icon of the managed libraries change from  to .

To update a library, do one of the following:

  • Update all libraries in the managed library repository  – Any library that has an update available is updated. This is recommended when a new version of camel is installed.
  • Update only one library from the list in the Libraries screen or the managed library repository screen  – This updates only the library that you selected. None of the already installed dependencies are updated. Any new linbrary dependency is installed in their last version. To update only one library, click the  icon next to the library you want to update.

For DI to take your managed library update into account, you must do one of the following: 

  • Quick but could impact performance – Restart the node.
  • Thorough method:
    • Update the associated Data integration connectors (saves the connectors again).
    • Restart the associated Data Integration routes (stop and start).


To use an old revision of a managed library, click the Rollback button in the repository. A list of previous available version of the managed library is displayed.


To uninstall a managed libraries, use the trash button  in the libraries list.

Some managed libraries cannot be uninstalled . This happens when the managed library:

After clicking on the trash button, if the managed library has dependencies, all its unused dependencies are displayed and can be deleted by clicking the Delete with dependencies button. 

Disable managed libraries

To disable the managed libraries feature, add in conf/

com.systar.aluminium.libraries.repository.enabled=false   // default value is 'true'

Related Links