Components of plugin

A typical plugin contains the following components:

The term Service represents a Java class, which either indirectly aids in consuming an external REST service, or directly interacts with external web service(s) or system(s) for a designated purpose. External system need not be a standard Content Management System and external services need not belong to any standard CMS. It can be any system or an API.

Any service implemented by the plugin must be declared in a centrally managed service declaration file. A service declaration file is an YML configuration file containing the list of services implemented by all the available plugins. The service declaration file must be named custom-plugin-services.yml. It should be available within the <ASSET_PICKER_HOME>/conf directory. Structure of custom-plugin-services.yml file must be similar to the plugin-services.yml file, which exists in the same directory. The plugin-services.yml file contains service declarations for out-of-the-box system integrations. A service can either be a standard service or a custom service.

Standard services carry special semantics and purpose in Unica Content Integration. Implementation of certain standard services is mandatory for Content Integration Framework to work with the content repository.