Enterprise Services Description Language for Business Object Interaction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Web Services Description Language (WSDL) provides a basic mechanism for defining Web services, which is insufficient for describing services with business objects, leading to a need for an enhanced language that can fully define interactions with business objects and their nodes.

Innovation Solution

The introduction of Enterprise Services Description Language (ESDL) extends WSDL to allow for the description of services with business objects, enabling complete definition of interactions, including associations and properties, through a SOAP message formatted according to ESDL, thereby instantiating business objects and nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If WSDL is used to define Web services, then the basic service definition capability is provided, but the ability to describe services with business objects and their nodes is insufficient

Engineering Contradiction:
Improveservice description capabilityVSAvoidlanguage complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges WSDL with business object descriptions by integrating business object node definitions directly into the WSDL structure. This allows the language to simultaneously handle basic service definition and complex business object interactions, resolving the contradiction between enhanced adaptability and language complexity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The enhanced WSDL language is designed to serve multiple functions: it can describe basic Web services, define business objects, specify business object nodes, and outline interactions between them. This multi-functionality addresses the insufficiency of original WSDL while managing complexity through a unified framework.

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

2Productivity

If multiple separate calls are used to access business objects and nodes, then each call can be simple and direct, but the overall process becomes complex and inefficient

Engineering Contradiction:
Improveservice interaction efficiencyVSAvoidcall process complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent combines multiple separate calls into a single call by enabling one request to simultaneously access business objects, business object nodes, and their interactions. This merging approach dramatically improves productivity while the structured nature of the language keeps the call process manageable.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The WSDL description is prepared in advance to include all necessary business object definitions, node associations, and interaction specifications. This preliminary action allows the system to handle complex interactions in a single call without requiring multiple sequential requests, thereby improving efficiency.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If a basic WSDL mechanism is used, then the language remains simple and easy to implement, but it cannot fully define interactions with business objects and their nodes

Engineering Contradiction:
Improvelanguage ease of useVSAvoidbusiness object interaction capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments the enhanced WSDL into distinct but integrated components: basic service definitions, business object definitions, business object node definitions, and interaction specifications. This segmentation maintains ease of operation by organizing complexity into manageable sections while enabling comprehensive business object interaction capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a nested structure where business object nodes are defined within business objects, which are in turn defined within the WSDL service description. This nesting approach allows the language to maintain simplicity at each level while achieving comprehensive adaptability for defining business object interactions.

Inventive Principle:
Principle #7Nested doll (Nesting)

Data Source

PatentUS7480920B2Systems and methods for providing an enterprise services description language
Publication Date: 2009.01.20 SAP SE
  • US7480920B2 patent drawing
  • US7480920B2 patent drawing
  • US7480920B2 patent drawing

AI summary

Methods and apparatus, including computer program products, are provided for providing a language for defining a service. In one embodiment, there is provided a method for making a call to the service having a business object. Moreover, the method may include formatting a message based on a language, the language defining an interaction with the business object at the service and an association between the business object and a business object node, the association enabling an instantiation of the business object including the business object node; and calling the service using the formatted message, such that the formatted message instantiates the business object.