Application Connectivity Determination via Metadata Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing ERP systems require content objects to be added to a central design time repository for data exchange, leading to inefficiencies and complexities in development, deployment, and maintenance, especially for developers unfamiliar with the repository's structure, and necessitate separate shipment channels for applications and metadata.
Innovation Solution
A system and method that automatically determine supported connectivity between applications, allowing metadata to be transferred and published only when necessary, either directly between applications or through a central design time repository, reducing the need for separate metadata channels and simplifying the setup and maintenance of distributed system landscapes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If content objects are added to the central design time repository for data exchange, then data exchange capability is improved, but device complexity and ease of operation deteriorate due to requiring separate metadata installation and multiple shipment channels
Solution Approach 1:
The patent combines the application installation and metadata installation into a single unified process. The content objects and their metadata are packaged together in a single shipment channel, eliminating the need for separate metadata installation steps and reducing system complexity while maintaining data exchange capability.
Solution Approach 2:
The central design time repository is enhanced to automatically process and register content objects with their embedded metadata. The system now serves multiple functions: storing content objects, managing metadata, and automatically establishing data exchange connections, reducing the need for manual configuration and multiple specialized channels.
2Reliability
If content objects are added to the central design time repository, then data exchange capability is improved, but loss of time increases due to additional metadata creation and installation steps
Solution Approach 1:
The metadata is prepared and packaged together with the content objects in advance during the application development phase. This preliminary action ensures that when the application is deployed, both the content objects and their metadata are installed simultaneously in a single step, eliminating the need for separate post-installation metadata configuration steps.
Solution Approach 2:
The system automatically detects, processes, and registers content objects and their metadata without requiring manual intervention. The automatic processing mechanism reduces development and deployment time by eliminating manual metadata creation and installation steps, allowing developers to focus on core application logic.
3Reliability
If developers create content object metadata manually, then data exchange capability is improved, but ease of manufacture deteriorates due to requiring familiarity with repository structure and programming
Solution Approach 1:
The system automatically generates and processes metadata from content objects without requiring manual intervention. This self-service mechanism allows developers to focus on application logic while the system handles metadata creation automatically, reducing the learning curve and making application development more accessible to developers regardless of their familiarity with repository structures.
Solution Approach 2:
An intermediary mechanism is introduced that automatically transforms content objects into the appropriate metadata format for the central design time repository. This intermediary layer abstracts the complexity of repository structure and programming from developers, allowing them to work with standard application development practices while the system handles the complex metadata transformation in the background.
Data Source
AI summary
A computer-implemented system and method that analyzes metadata of the first application to identify a first data object and one or more first fields of the first data object, the first data object and the first fields being part of the metadata of the first application, identifies one or more second applications having a second data object with one or more second fields, and determines, for at least one of the second applications, a supported connectivity with the first application and whether the supported connectivity is a point-to-point connectivity or a connectivity through a central design time repository.