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
Execution context
Almost every method in service implementation contract receives an instance of com.hcl.unica.system.model.request.ExecutionContext class.
User data source
Unica Platform uses user data sources to store sensitive information, such as API credentials, security tokens, database user credentials, etc. Plugins often need to store such configuration details. Content Integration provides the relevant configuration to specify the name of user data source and the associated Unica user while oboarding systems using Unica Platform configuration.

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.
    - 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.
      - User data source
        Unica Platform uses user data sources to store sensitive information, such as API credentials, security tokens, database user credentials, etc. Plugins often need to store such configuration details. Content Integration provides the relevant configuration to specify the name of user data source and the associated Unica user while oboarding systems using Unica Platform configuration.
    - Standard services and specialized types
      The plugin developer needs to implement RestService/HttpService or FunctionalService interface to create an individual service.
    - 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

User data source

Unica Platform uses user data sources to store sensitive information, such as API credentials, security tokens, database user credentials, etc. Plugins often need to store such configuration details. Content Integration provides the relevant configuration to specify the name of user data source and the associated Unica user while oboarding systems using Unica Platform configuration.

Use the ExecutionContext to obtain applicable user data source (credentials) by navigating through SystemConfig object:

executionContext.getSystemConfig().getDataSourceCredentials()

The DataSourceCredentials object returned by the getDataSourceCredentials method contains the selected data source based on the strategy set up for User credentials in Platform configuration. Hence, plugins need not make any logical decision pertaining to the right selection of the user data source.

Similarly, the getUnicaToken method called on SystemConfig object returns an UnicaToken object containing the Unica Token required for invoking APIs of Unica applications.

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.