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 implementations
For each service declared in the service declaration file, there must be an implementation present inside the respective factoryClass.
Best approach selection
Although, it is possible to implement a service using either approaches, each approach has some advantages and limitations when it comes to the capabilities.

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.
      - 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.
        RESTful approach
        The com.example.service.rest.ExampleCustomService class helps you understand REST based service implementation.
        Functional approach
        Refer to the com.example.service.functional.ExampleCustomService class to understand the functional service implementation.
        Best approach selection
        Although, it is possible to implement a service using either approaches, each approach has some advantages and limitations when it comes to the capabilities.
  - 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

Best approach selection

Although, it is possible to implement a service using either approaches, each approach has some advantages and limitations when it comes to the capabilities.

RESTful approach
1. Advantages
  - Less verbose & reads closer to the typical HTTP interaction
  - Out of the box transport level error handling
  - Out of the box support for retrial in case of temporary outages
  - Out of the box support for proxied connectivity
  - Out of the box support for future enhancements in Content Integration Framework
2. Limitations
  - Cannot be used for non-RESTful or non-HTTP integrations, such as database or file system interactions
Functional approach
1. Advantages
  - Can be used for non-RESTful or non-HTTP integrations, such as database or file system interactions
2. Limitations
  - No out-of-the-box support available for transport level error handling, retrials, proxied connectivity, and any future enhancements from Content Integration Framework.
  - If required, the explicit implementation of missing out-of-the-box capabilities can make service implementations very verbose.

You can see that the Functional approach is well suited for non-RESTful or non-HTTP based integrations. Any service implemented using RESTful approach can also be implemented using Functional approach by taking care of all the necessary out-of-the-box capabilities provided by Content Integration Framework. While Functional approach gives flexibility in terms of implementation design, it takes away a few useful capabilities.

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.