CMIS Adapter Mapping for Native ECM Artifact Interoperability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing CMIS systems face challenges in integrating with ECM systems due to non-conformity between the CMIS domain model and the proprietary domain models of ECM systems, leading to limited access to the full suite of content services offered by ECM systems, especially when CMIS secondary types are used, which are created dynamically and unpredictably.

Innovation Solution

The integration is achieved by configuring ECM systems to recognize CMIS secondary types and update artifact configurations to create native ECM artifacts, maintaining distinct hierarchies and mapping relationships between CMIS and ECM structures, allowing access and interaction through both CMIS and ECM interfaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If CMIS client systems use the CMIS data model to access ECM systems, then interoperability between different content management systems is improved, but access to the full suite of ECM content services is limited due to non-conformity between CMIS and proprietary ECM domain models

Engineering Contradiction:

ImproveinteroperabilityVSAvoidaccess to full content services

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a CMIS adapter as an intermediary component that sits between the CMIS client system and the ECM system. This adapter translates CMIS operations into ECM-specific operations and maintains mappings between CMIS secondary types and ECM native artifacts, enabling full access to ECM content services while preserving CMIS interoperability.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the integration architecture into distinct layers: the CMIS client layer, the CMIS adapter layer, and the ECM native layer. This segmentation allows each layer to operate independently with its own domain model, while the adapter handles the translation and mapping between layers to ensure full functionality.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If ECM systems maintain their own proprietary domain models to offer enhanced functionality, then content management functionality is improved, but integration with CMIS client systems is complicated by non-conformity

Engineering Contradiction:

Improvecontent management functionalityVSAvoidintegration complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The CMIS adapter serves as a mediator that absorbs the complexity of proprietary domain models and presents a standardized CMIS interface to client systems. It handles the translation between CMIS and ECM-specific artifacts, shielding clients from integration complexity while preserving enhanced ECM functionality.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates virtual representations of ECM artifacts as CMIS secondary types. These virtual copies maintain the full functionality and characteristics of native ECM artifacts while conforming to the CMIS data model, allowing seamless interaction through CMIS without compromising ECM capabilities.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If CMIS secondary types are created dynamically at runtime, then adaptability to different object types is improved, but predictability and control over the domain model is reduced

Engineering Contradiction:

Improveruntime object type creationVSAvoiddomain model predictability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent establishes a configuration phase where ECM systems pre-define the mapping between CMIS secondary types and native artifacts before runtime operations occur. This preliminary configuration ensures that when dynamic object types are created at runtime, the mappings are already in place, maintaining predictability and control over the domain model.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where the CMIS adapter monitors and tracks the creation of secondary types and dynamically updates the artifact configuration. This feedback loop ensures that the domain model remains predictable by maintaining consistent mappings between CMIS types and ECM artifacts throughout the runtime lifecycle.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS12361073B2Systems and methods for enhanced content management interoperability services interfaces and repository integration

Publication Date: 2025.07.15 OPEN TEXT SA ULC

AI summary

Systems and methods related to the seamless integration of Content Management Interoperability Services (CMIS) client systems with native data models of repositories that may be utilized with such client systems are disclosed. In particular, certain embodiment of systems and methods for the integration of CMIS compliant client systems with CMIS compliant ECM systems by conforming CMIS secondary types utilized by CMIS clients to the native ECM artifacts utilized by the ECM system are disclosed.