The ambition of enterprise content management systems to standardize on one content source has proved impossible in some situations. The reality is that content is stored in multiple repositories, such as cloud applications, legacy ECM systems, collaboration tools, WCM, PIM and DAM systems. But building integrations is time consuming, expensive, error prone and not really a core business for most software vendors. Yet there are situations where content integration makes more sense than content migration.
To facilitate analytics, search or access, to name a few, connectivity to content management systems is sometimes required. To support this, Xillio has developed the Xillio API, which unlocks various content systems in terms of data model and API calls.
With the uniform API it is possible to easily make connections with all content management systems. Unlike many other API middle layers, we specialize in content integration. Content that is stored in either cloud storage systems or legacy systems becomes accessible in every application.
The Translation & Localization industry uses our API so that users can select files from external content sources directly in the interface of the translation software. After the translation and approval process, the translated content is automatically stored back at the correct location in the source system.
It is possible to use the API to integrate other content systems real-time into a content repository. In this example, we see the integration of Liferay with external content sources, such as Dropbox, BitBucket and Egnyte.
Another example of integration between two content systems. In this video, we use M-files as an interface for access to content stored in a SharePoint environment.