Shared Resource Discovery and Configuration via Landscape Directory

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current networked solutions lack automated methods for discovering, configuring, and consuming shared resources within a system landscape, leading to inefficient integration and utilization of available resources across different networked solutions and vendors.

Innovation Solution

A discovery, configuration, and consumption module (DCCM) is integrated into each networked solution to automate the discovery of available shared resources, retrieve configuration settings, and establish peer-to-peer communication channels, enabling seamless integration and utilization of shared resources without requiring significant user interaction or configuration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If automated discovery and configuration of shared resources is implemented, then integration efficiency and resource utilization improve, but system complexity and implementation difficulty increase

Engineering Contradiction:
Improveintegration efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a landscape directory as an intermediary component that centralizes information about shared resources and their configurations. This mediator enables automated discovery and configuration by providing a standardized interface between networked solutions and shared resources, reducing the complexity of direct integration while improving integration efficiency.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The landscape directory serves multiple functions: it stores information about shared resources, manages configuration settings, enables automated discovery, and facilitates peer-to-peer communication. This multi-functional approach consolidates what would otherwise require multiple separate systems, improving productivity while managing system complexity.

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

2Loss of time

If manual configuration of shared resources is used, then system complexity remains low, but time and effort required for resource provisioning increase

Engineering Contradiction:
Improveresource provisioning timeVSAvoidconfiguration automation
Core Design Contradiction:
Loss of timeVSExtent of automation

Solution Approach 1:

The system performs preliminary actions by pre-configuring and registering shared resources in the landscape directory before they are needed. Configuration settings are stored in advance, enabling automated retrieval and peer-to-peer connection establishment without requiring manual configuration at the time of resource provisioning, thus reducing resource provisioning time while implementing configuration automation.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If peer-to-peer communication channels are established for each networked solution, then resource access efficiency improves, but configuration management complexity increases

Engineering Contradiction:
Improveresource access efficiencyVSAvoidconfiguration management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The landscape directory acts as a mediator that manages configuration settings for all peer-to-peer communication channels. Instead of each networked solution independently managing its own configuration, the centralized directory stores and manages all configuration information, enabling efficient peer-to-peer resource access while simplifying configuration management through centralization.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8375130B2Shared resource discovery, configuration, and consumption for networked solutions
Publication Date: 2013.02.12 SAP SE
  • US8375130B2 patent drawing
  • US8375130B2 patent drawing
  • US8375130B2 patent drawing

AI summary

A networked solution offering a software-based service via a networked architecture having a system landscape can discover a shared resource within the system landscape, for example by accessing a landscape directory comprising information about a plurality of shared resources available in the system landscape. The information about the discovered shared resource can include a second networked solution within the system landscape that has previously configured the discovered shared resource. Configuration settings can be retrieved for the discovered shared resource from the second networked solution. Using the retrieved configuration settings, a shared resource-specific communication channel can be determined for the networked solution to access the discovered shared resource in a peer-to-peer manner. A resource type-specific application programming interface can be provided to the software-based service to enable consumption of the discovered shared resource by the software-based service. Related methods, systems, and articles of manufacture are described.