Enterprise Content Management Cloning with Direct Database RPC

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloning tools for enterprise content management systems are inefficient, requiring weeks to complete the cloning process due to indirect interaction with databases through multiple layers of application program interfaces, leading to high costs and prolonged downtime.

Innovation Solution

A cloning tool that directly interacts with database management systems via remote procedure calls, enabling direct extraction and loading of data at the database level, significantly reducing the cloning time to days compared to weeks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing cloning tools interact with databases through multiple layers of application program interfaces, then the cloning process is more stable and reliable, but the cloning time increases to weeks and costs increase

Engineering Contradiction:
Improvecloning process stabilityVSAvoidcloning time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts the cloning operation from the upper-layer application program interfaces and performs it directly at the database level. By taking out the intermediate API layers and executing remote procedure calls directly against the database management system, the invention reduces cloning time from weeks to days while maintaining database integrity through direct controlled access.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a specialized cloning tool as an intermediary that bypasses the conventional multi-layer API architecture. This intermediary tool communicates directly with the database management system using remote procedure calls, eliminating the need to traverse multiple application program interface layers and thereby reducing cloning time while preserving data integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If existing cloning tools use multiple layers of application program interfaces to interact with databases, then the system architecture is more modular and maintainable, but the cloning cost increases and efficiency decreases

Engineering Contradiction:
Improvesystem modularityVSAvoidcloning efficiency
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The patent extracts the cloning function from the conventional modular API architecture and implements it as a direct database-level operation. By removing the cloning process from the multi-layer application program interface structure, the invention achieves significantly higher cloning efficiency (reducing time from weeks to days) while maintaining system modularity through the use of standardized remote procedure call interfaces.

Inventive Principle:
Principle #2Taking out (Extraction)

3Speed

If cloning tools directly interact with database management systems via remote procedure calls, then the cloning speed increases to days, but the complexity of direct database interaction increases

Engineering Contradiction:
Improvecloning speedVSAvoiddatabase interaction complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent uses the existing remote procedure call interface as a standardized copying mechanism to replicate database structures and data. By leveraging the established RPC protocol between the cloning tool and database management system, the invention achieves fast cloning (reducing time to days) without increasing complexity, as the RPC interface provides a familiar and manageable abstraction layer.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12393561B2Method and system for cloning enterprise content management systems
Publication Date: 2025.08.19 OPEN TEXT CORP
  • US12393561B2 patent drawing
  • US12393561B2 patent drawing
  • US12393561B2 patent drawing

AI summary

Cloning enterprise content management systems is described. A first remote procedure call is executed to a source database management system associated with a source enterprise content management system to retrieve a source object type from the source enterprise content management system. A second remote procedure call is executed to a target database management system associated with a target enterprise content management system to create a target object type in the target enterprise content management system, wherein the target object type is based on the source object type. Source metadata tables associated with the source object type are retrieved from the source enterprise content management system. The source metadata tables are stored as target metadata tables in the target enterprise content management system.