Database Federation via Dynamic Invocation String Substitution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing configuration management databases face challenges in dynamically and automatically invoking external applications to manage and retrieve federated data, often requiring manual processes or custom integration logic, which limits scalability and complexity management.

Innovation Solution

A mechanism is introduced to register external applications within a database, allowing for the creation of an invocation string that combines static and dynamic portions, enabling automatic execution of external applications in response to database queries, with the ability to substitute attribute values from database entries into the invocation string.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual processes or custom integration logic are used to access federated data, then data access is possible, but scalability and complexity management are limited

Engineering Contradiction:
ImprovescalabilityVSAvoidcomplexity management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The database management system is enhanced with universal federation capabilities that allow it to access multiple external data sources through a unified interface. The system can dynamically invoke external applications and retrieve federated data without requiring separate custom integration logic for each data source, thereby improving scalability while maintaining manageable complexity through standardized access patterns.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Extent of automation

If custom integration logic is developed for each federated database, then automated interaction is achieved, but system complexity increases

Engineering Contradiction:
Improveautomated interactionVSAvoidsystem complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The database management system acts as an intermediary that mediates between the user and multiple external data sources. It provides automated interaction capabilities by handling the complexity of communicating with external applications internally, while presenting a simplified interface to users. This mediator approach enables automation without proportionally increasing user-facing system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If a separate application is used to manually search for federated data, then data access is possible, but productivity is reduced

Engineering Contradiction:
Improvedata access efficiencyVSAvoidoperation simplicity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent merges the data access functionality directly into the database management system, combining what were previously separate manual search operations with the database query mechanism. Users can now access federated data through the same interface used for native database queries, eliminating the need to switch to separate applications and significantly improving productivity while maintaining operational simplicity.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS10235435B2Database application federation
Publication Date: 2019.03.19 BMC HELIX INC
  • US10235435B2 patent drawing
  • US10235435B2 patent drawing
  • US10235435B2 patent drawing

AI summary

According to an aspect, a system for assisting a user with configuration management may include a configuration management database (CMDB) system having a plurality of configuration items, and an application external to the CMDB system. The CMDB system may associate an invocation string with a first configuration item and the application external to the CMDB system. The CMDB system may obtain information from the first configuration item, where the information from the first configuration item provides information for launching the application external to the CMDB system. The CMDB system may insert the information from the first configuration item into the invocation string to create an application execution command. The CMDB system may execute the application external to the CMDB system, independently from the CMDB system, based on the application execution command.