Generic Enterprise SOA Data Archiving via XML Schema

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing enterprise service-oriented architecture data archiving methods require specific coding for different versions and types of business objects, making it difficult to archive and restore data in a generic fashion, and lack support for both online and archived data without distinction.

Innovation Solution

The method generates a schema and instance data for business objects in a platform-independent format like XML, allowing for the reconstruction of business objects without specific coding and enabling seamless support for both online and archived data, using an enterprise service repository to define data types and relationships among nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If specific coding is used for different versions and types of business objects, then data archiving can be performed with precise data structure control, but the system becomes difficult to operate in a generic fashion and requires special coding for each object type

Engineering Contradiction:
Improvedata structure controlVSAvoidgeneric archiving operation
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent creates a universal archiving system that can handle multiple business object types and versions through a single generic interface. The system uses schema generation from type definitions to create platform-independent XML representations that work across different business object variants, eliminating the need for special coding for each object type while maintaining precise data structure control through the schema definition process.

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

2Reliability

If special coding is required for different business object versions, then data accuracy is maintained, but the device complexity increases and reconstruction becomes difficult

Engineering Contradiction:
Improvedata accuracyVSAvoidcoding complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses template copying where a generic archiving framework is copied and adapted for different business object types through schema generation. Instead of writing special code for each object version, the system generates appropriate XML schemas from type definitions, copying the essential structure and validation rules while adapting to specific object characteristics automatically.

Inventive Principle:
Principle #26Copying

3Reliability

If online and archived data are treated separately, then data integrity is maintained, but the system loses the ability to show no distinction between them for reporting purposes

Engineering Contradiction:
Improvedata integrityVSAvoiddata handling flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent creates homogeneous data representation by converting both online and archived business objects into the same platform-independent XML format with standardized schemas. This homogenization allows the system to treat archived and online data uniformly for reporting and analysis while maintaining data integrity through schema-based validation, enabling seamless integration without special handling distinctions.

Inventive Principle:
Principle #33Homogeneity

Data Source

PatentUS7937410B2Generic archiving of enterprise service oriented architecture data
Publication Date: 2011.05.03 SAP SE
  • US7937410B2 patent drawing
  • US7937410B2 patent drawing
  • US7937410B2 patent drawing

AI summary

Methods and apparatus, including computer program products, for generic archiving of enterprise service oriented architecture data. In general, an identification of an instance of a business object to archive is received. Information defining the business object is retrieved. A schema for the type definition and a definition of the instances of the business object in accordance with the schema is generated. The schema may be in accordance with a platform-independent file format including information reflecting the hierarchy of the business object. The schema may include hierarchy levels that reflect each hierarchy level of the business object. Each hierarchy level, with the exception of hierarchy levels including references to stand-alone business objects, may have the respective attributes of the hierarchy level of the business object. Instance data may be generated to reflect the instance of the business object, the instance data being in accordance with the schema.