Cloud Landscape Directory for Seamless Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cloud networking management systems face challenges in seamlessly integrating cloud and on-demand software with existing on-premise applications, requiring efficient data management and service request processing across diverse landscapes.

Innovation Solution

A cloud landscape directory is maintained to store data on multiple individual landscapes, including cloud-based applications, allowing for access and use, and processing service requests by communicating access data and monitoring application accessibility, enabling integration with SAP and non-SAP applications, and supporting lifecycle management and monitoring tools.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If cloud-based applications are integrated with existing on-premise applications, then solution versatility and customer accessibility are improved, but system complexity and integration difficulty increase

Engineering Contradiction:
Improvesolution versatilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A landscape directory service acts as an intermediary between cloud-based applications and on-premise applications. The directory maintains structured data about multiple landscapes, applications, and their relationships, enabling seamless integration without direct complex point-to-point connections. This mediator resolves the technical contradiction by providing a standardized interface that simplifies integration while supporting diverse application types.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The landscape directory implements a universal data structure that can represent multiple types of applications (cloud-based, on-demand, on-premise) and multiple landscapes within a single system. This multi-functional approach allows the same infrastructure to handle diverse integration scenarios, improving versatility without proportionally increasing complexity for each specific case.

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

2Measurement precision

If comprehensive data about multiple landscapes and applications is maintained, then service request processing accuracy is improved, but data management complexity increases

Engineering Contradiction:
Improveservice request processing accuracyVSAvoiddata management complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The data management system is segmented into distinct functional components: landscape data storage, application registry, accessibility information management, and service request processing. Each component handles specific aspects of data, reducing overall complexity while maintaining comprehensive information. The segmentation allows precise service request processing by directing queries to appropriate data segments.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The landscape directory serves as an intermediary data structure that organizes complex information about multiple landscapes and applications in a standardized format. This mediator layer simplifies data access and management by providing a consistent interface to query and update information, reducing the complexity of handling comprehensive data while improving processing accuracy.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If monitoring and administration tools are implemented for cloud-based solutions, then system reliability and accessibility are improved, but implementation effort and cost increase

Engineering Contradiction:
Improvesystem reliabilityVSAvoidimplementation effort
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The landscape directory enables self-service monitoring and administration capabilities where applications can autonomously register themselves, report their accessibility status, and be discovered by service requests without manual configuration. This self-service approach improves system reliability through continuous automatic monitoring while reducing implementation effort by eliminating manual setup of administration tools.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms where applications continuously report their accessibility information and status to the landscape directory. This feedback loop enables automatic monitoring and reliability tracking without requiring complex external administration tools. The feedback-driven approach improves system reliability while keeping implementation effort low through automated information collection.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8751573B2Cloud-processing management with a landscape directory
Publication Date: 2014.06.10 SAP SE
  • US8751573B2 patent drawing
  • US8751573B2 patent drawing
  • US8751573B2 patent drawing

AI summary

Disclosed are methods, systems, apparatus and products, including a method that includes maintaining data in a cloud landscape directory, including data regarding multiple individual landscapes. Each landscape of the multiple individual landscapes identifying at least a set of applications, the set of applications of at least one of the multiple individual landscapes including at least one cloud-based application available for cloud-processing. The at least one cloud-based application is associated with the at least one of the multiple individual landscapes and is available for access and use. The method also includes processing at least one of a plurality of service requests based, at least in part, on the data regarding the multiple individual landscapes maintained in the cloud landscape directory.