Maven is the easiest way to install the module. Add the following dependency to your bundle:
To be able to use CELUM remote api (api-remote-3.5.0-jar-with-dependencies.jar), it has to be available in your maven (i.e. company Nexus) repository or you will have to install it manually into your local repository.
You will need an account to connect to CELUM, that account is created in CELUM Configuration Management Application (CMA).
Depending on your needs, you might want to add access to the API user to some asset types, that will be done on CELUM app server in the administration feature.
Provides the root node id for the tree view.
Defines the connection string to CELUM remote API. i.e.
Remote clientId. Can be a path from the passwords app. i.e. /celum-credentials/clientId
Client secret. Can be a path from the passwords app. i.e. /celum-credentials/clientSecret
Server secret. Can be a path from the passwords app. i.e. /celum-credentials/serverSecret
Is the Passwords app path where we want to listen for credentials changes.
Locale to be used by default when getting Celum node names, defaults to "en".
Is a map of properties that maps the properties in the Magnolia asset object to properties in the fileProperties of the Celum remote asset. There are some extra properties provided by fileProperties in Celum asset that are automatically available to be used in dialogs, no need to declare them here.
In order to use the Passwords app to store the credentials for the remote connection to Celum, you need to create the folder with the items and set the paths in the config.yaml or the JCR configuration of the Celum connector module.
Sample of config.yaml
Deactivate Netty logs
Add the following lines to the log configuration file in your log properties file:
Once the module has been installed you can add assets to the website and/or apps by using the the default Dam link field,
Or using the dam link field with the dam chooser or adding your own celum-chooser,
In the templates you can access to the asset link by calling:
Some extra Dam templating functions can be added to access to the searchFilters functionality, the service provides a factory for classes that implement 'SearchFilter'. We provide a sample filter implementation 'AssetsByNodeIdFilte', the filter's implementations have to be configured in the module descriptor
To run this filter you need to call the service 'searchByFilter' method with the filter name and the parameters you want to send.
In order to use SSO credentials, you need to provide your own implementation of interface ImpersonationHandler and set the configuration option "impersonate" to true. The default implementation is empty.
- This module is at INCUBATOR level.
- Version 1.0 - Initial release of the extensions version of the module.
- Put links to relevant tickets to help others