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 SDK
Standard services and specialized types
The plugin developer needs to implement RestService/HttpService or FunctionalService interface to create an individual service.
Specialized types
Presentable
To be able to render an individual content returned by the simple-search, list-contents & get-content-details services , the domain entity class used by these services must implement the com.hcl.unica.system.model.presentation.Presentable interface and override the getPresentationDetails() method. The com.hcl.unica.system.model.presentation.Presentable$PresentationDetails object returned by the getPresentationDetails() method must provide the TextualPresentation as well as MultimediaPresentation details.

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.
  - Plugin Development SDK
    - Generic type parameters
      Generic type parameters are used for implementing service interfaces. For more information on service interfaces, see ContentIntegration/DeveloperGuide/service_implementations.html.
    - I18n support
    - Service invocation
      The asset-integration-starter project contains a com.example.service.client.CustomServiceClient class to illustrate the service invocation.
    - Execution context
      Almost every method in service implementation contract receives an instance of com.hcl.unica.system.model.request.ExecutionContext class.
    - Standard services and specialized types
      The plugin developer needs to implement RestService/HttpService or FunctionalService interface to create an individual service.
      - Invocation of standard services
        Once declared in service declaration file, and implemented using either RESTful or Functional approach, Content Integration Framework invokes the standard services in following scenarios:
      - Specialized types
        Derivatives of RestService
        Derivatives of RestService interface facilitates creation of RESTful implementation of standard services.
        Derivatives of HttpService
        Only resource-loader standard service is implemented as an HttpService as it relates to the standard HTTP GET operation. You can also use RestService without losing any capability.
        Derivatives of FunctionalService
        Derivatives of FunctionalService interface facilitates creation of functional implementation of standard services. Functional service is just an object with a public method which takes a certain input and generates the desired output.
        Derivatives of InboundHttpService
        AbstractEntity
        The com.hcl.unica.system.model.AbstractEntity class represents a general domain entity. For the current release, this abstract class does not contain any implementation.
        Presentable
        To be able to render an individual content returned by the simple-search, list-contents & get-content-details services , the domain entity class used by these services must implement the com.hcl.unica.system.model.presentation.Presentable interface and override the getPresentationDetails() method. The com.hcl.unica.system.model.presentation.Presentable$PresentationDetails object returned by the getPresentationDetails() method must provide the TextualPresentation as well as MultimediaPresentation details.
        Builder API
        Almost all the standard types discussed in previous sections provide the builder API for the ease of constructing objects.
    - Request Validation
    - Standard exceptions
    - Loggers
      Content Integration Framework provides logging interface using the slf4j library. By adding dependency for the slf4j library, the plugins can use its API for adding loggers inside service implementations.
  - 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

Presentable

To be able to render an individual content returned by the simple-search, list-contents & get-content-details services , the domain entity class used by these services must implement the com.hcl.unica.system.model.presentation.Presentable interface and override the getPresentationDetails() method. The com.hcl.unica.system.model.presentation.Presentable$PresentationDetails object returned by the getPresentationDetails() method must provide the TextualPresentation as well as MultimediaPresentation details.

TextualPresentation contains following particulars:

Note: The highlighted fields are mandatory. For the other fields, provide details, if available.
heading – Title of the content
subheadings – List of subheadings for the content
summary – Summary or description of the content
name – Should be used for filename associated with the content
tags – Tags associated with the content (out of the box plugins use this to convey MIME type or category of the content)

Whereas MultimediaPresentation contains following particulars:

Note: The highlighted fields are mandatory. For the other fields, provide details, if available.
id - Unique identifier of the content
folderId - Unique identifier of the folder respective content belongs to
mimeType - MIME type of the original content
size - Size of original content in bytes
resourceUrl - Absolute URL to the original content
thumbnailUrl - Absolute URL to the content thumbnail, if available
fileName - File name associated with the original content
type – Type/category identifier of the content (must be one of the values from supported content types set up using any of the applicable alternatives provided by Content Integration framework)
list of variants – Each variant supports almost same details as the primary MultimediaPresentation details except thumbnailUrl (it can only have its own resourceUrl), folderId and variants (variant cannot have any further variants)

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.