Home
Unica Content Integration
Content Integration facilitates easy integration with Content Management Systems and enables searching content from the Content Management Systems.
Developer Guide
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).

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
  - 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).
    - Overview of loggers
- User's Guide

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).

All the system onboarding configurations, mentioned in Unica Content Integration Administration Guide, are supported in the systems.properties using relevant properties. You must provide -Dspring.profiles.active=platform-disintegrated JVM argument for systems.properties to come into effect (you can always use Platform’s configurations instead of systems.properties by removing -Dspring.profiles.active=platform-disintegrated JVM argument).

Note: Currently, only Unica Centralized Offer Management and Unica Plan can access Content Integration.

After the plugin is deployed, and the system configurations are made, restart the Content Integration application.

Although, you can verify Content Integration using REST endpoints mentioned in previous section, we recommend you to check end-to-end integration by running through the relevant user interface in Unica Centralized Offer Management and Unica Plan. Please refer to the corresponding user guides to learn how to access Content Integration features in respective products.

Use developer tools provided by the supported browsers to troubleshoot the API calls, if required.

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.