Home
Unica Content Integration
Content Integration facilitates easy integration with Content Management Systems and enables searching content from the Content Management Systems.
Developer Guide
Plugin development overview
Unica Content Integration facilitates easy integration with new content repositories without having to alter the core Content Integration framework.
Components of plugin
A typical plugin contains the following components:
Service declarations
Reference service declarations can be found inside asset-integration-starter project within dev-kits\asset-integration-starter\src\main\resources\META-INF directory.

Unica Content Integration
Content Integration facilitates easy integration with Content Management Systems and enables searching content from the Content Management Systems.
- Release Notes
- Installation and Configuration Guide
- Developer Guide
  - Overview
    Unica Content Integration facilitates easy integration with Content Management Systems and enables searching content from them.
  - Plugin development overview
    Unica Content Integration facilitates easy integration with new content repositories without having to alter the core Content Integration framework.
    - Components of plugin
      A typical plugin contains the following components:
      - Service declarations
        Reference service declarations can be found inside asset-integration-starter project within dev-kits\asset-integration-starter\src\main\resources\META-INF directory.
        Service declaration file
        Service declaration file contains services element, which is an array of individual service declarations. A service declaration is a dictionary containing three mandatory elements named systemId, serviceName, and factoryClass, and one optional element named params. Details of the elements are as follows:
      - Standard services
        The following table introduces the standard services of Unica Content Integration. Hence, none of the service names listed herein should be used for any custom service implementation. Content Integration SDK provides standard interfaces and types to implement these standard services. These interfaces and types are discussed in more detail in subsequent sections.
      - Service implementations
        For each service declared in the service declaration file, there must be an implementation present inside the respective factoryClass.
  - Plugin Development SDK
  - Setting up the development environment
    Set up the development environment in Eclipse IDE for writing your plugins. Use any Java EE IDE of your choice and make the required configurations mentioned in this topic. You need certain artifacts from <ASSET_PICKER_HOME> to complete the environment setup. This topic will provide information about project building and packaging using Apache Maven so ensure that you have Apache Maven installed.
  - Verification and troubleshooting
    To verify end-to-end integration, place the JAR file, containing the plugin implementation, in the class path of the application server where the Content Integration is deployed. Additionally, configure the corresponding content repository in <ASSET_PICKER_HOME>/conf/systems.properties file (you can refer to the sample-systems.properties file within the <ASSET_PICKER_HOME>/dev-kits/asset-integration-starter project).
- User's Guide

Service declarations

Reference service declarations can be found inside asset-integration-starter project within dev-kits\asset-integration-starter\src\main\resources\META-INF directory.

The following are example service declarations from asset-integration-starter project:

services:
  -
    systemId: Foo
    serviceName: simple-search
    factoryClass: com.example.service.rest.SimpleSearchService
    params:
      supportedContentTypes: # Standard parameter, applicable only for simple-search service
        Images: Images
      customParam1: p1Value # String parameter
      customParam2: 1234.56 # Numeric parameter
      customParam3: # Key-value/Dictionary/Map parameter
        p3Key1: p3Value1
        p3Key2: p3Value2
        p3Key3: p3Value3
      customParam4: # Array parameter
        - p4Value1
        - p4Value2
        - p4Value3
     
  -
    systemId: Foo
    serviceName: resource-loader
    factoryClass: com.example.service.rest.ResourceLoaderService
    params:
      customParam1: p1Value # String parameter
      customParam2: 1234.56 # Numeric parameter
      customParam3: # Key-value/Dictionary/Map parameter
        p3Key1: p3Value1
        p3Key2: p3Value2
        p3Key3: p3Value3
      customParam4: # Array parameter
        - p4Value1
        - p4Value2
        - p4Value3    
  -
    systemId: Foo
    serviceName: asset-selection-callback
    factoryClass: com.example.service.rest.ContentSelectionCallbackService
    params:
      customParam1: p1Value # String parameter
      customParam2: 1234.56 # Numeric parameter
      customParam3: # Key-value/Dictionary/Map parameter
        p3Key1: p3Value1
        p3Key2: p3Value2
        p3Key3: p3Value3
      customParam4: # Array parameter
        - p4Value1
        - p4Value2
        - p4Value3
  -
    systemId: Foo
    serviceName: custom-service
    factoryClass: com.example.service.rest.CustomService
    params:
      customParam1: p1Value # String parameter
      customParam2: 1234.56 # Numeric parameter
      customParam3: # Key-value/Dictionary/Map parameter
        p3Key1: p3Value1
        p3Key2: p3Value2
        p3Key3: p3Value3
      customParam4: # Array parameter
        - p4Value1
        - p4Value2
        - p4Value3

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.