Configuration Stencils for System Integration Contradictions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems face challenges in efficiently configuring message flows for system integration, particularly when application developers lack integration knowledge, leading to errors and overhead, and integration experts may not adhere to organizational policies or best practices.

Innovation Solution

A computer-implemented method using configuration stencils with defined configuration points and constraints, allowing for flexible configuration of message flows without requiring extensive integration knowledge, enabling application developers to create and manage integration configurations while ensuring compliance with organizational policies and best practices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If application developers define message flows and integration configuration themselves, then integration knowledge gap is reduced, but error rate increases and compliance with organizational policies decreases

Engineering Contradiction:
Improveintegration knowledge accessibilityVSAvoidconfiguration accuracy
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces configuration stencils as an intermediary artifact between integration experts and application developers. These stencils contain pre-defined integration patterns, constraints, and best practices that guide developers in creating compliant message flows without requiring deep integration expertise. The stencil acts as a mediator that translates complex integration requirements into developer-friendly templates with built-in validation rules.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent transforms the configuration process by changing parameters from free-form input to constrained input through stencils. Configuration points within stencils define specific parameters that must be filled with values meeting predetermined constraints (data types, formats, validation rules). This parameter transformation ensures compliance while maintaining developer autonomy, resolving the contradiction between accessibility and accuracy.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If integration experts define message flows, then compliance with organizational policies is improved, but overhead and complexity increases

Engineering Contradiction:
Improvepolicy complianceVSAvoidconfiguration process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates reusable configuration stencils that copy proven integration patterns and best practices from expert configurations. Instead of requiring experts to manually define each message flow, their expertise is captured once in stencil templates that can be copied and instantiated multiple times. This copying mechanism preserves policy compliance while eliminating repetitive manual work, reducing overhead and complexity.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The stencils serve multiple functions simultaneously: they document integration patterns, enforce organizational policies, provide validation rules, and guide developers. This multi-functionality consolidates what would otherwise require separate processes (expert definition, policy enforcement, documentation), simplifying the overall configuration process while maintaining compliance.

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

3Adaptability or versatility

If training is provided to application developers for integration configuration, then self-sufficiency improves, but time and resource overhead increases

Engineering Contradiction:
Improvedeveloper self-sufficiencyVSAvoidtraining overhead
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent performs preliminary action by pre-configuring integration patterns, constraints, and validation rules within stencils before developers need them. Instead of requiring extensive training to teach developers integration concepts, the stencils already contain embedded expertise and best practices. Developers can immediately use these pre-prepared templates, eliminating the need for time-consuming training while maintaining self-sufficiency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The stencils enable developers to self-serve integration configuration needs without requiring expert intervention or extensive training. The constrained input mechanisms and built-in validation provide self-guiding functionality that helps developers create compliant configurations independently, transforming the training investment into a self-service capability through reusable templates.

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If flexible configuration is allowed without constraints, then adaptability to different scenarios improves, but error rate and non-compliance increases

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidconfiguration quality
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The patent applies local quality by implementing constraints at specific configuration points within stencils rather than applying uniform restrictions throughout. Each configuration point has tailored constraints (data types, formats, validation rules) appropriate to its specific purpose. This localized constraint application maintains flexibility where needed while ensuring quality and compliance at critical points, resolving the contradiction between adaptability and precision.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8739124B2Configuring integration capabilities for system integration
Publication Date: 2014.05.27 SAP SE
  • US8739124B2 patent drawing
  • US8739124B2 patent drawing
  • US8739124B2 patent drawing

AI summary

Configuring integration capabilities includes: receiving a configuration stencil that is a configuration artifact of a message flow, the configuration stencil comprising at least one configuration point, the configuration point currently having no assigned value, and at least one constraint for the configuration point, the constraint being a rule or type for a value to be assigned to the configuration point; receiving, using one or more processors, input comprising at least one configuration point value for the configuration point, the configuration point value having been selected based on first and second systems to be integrated using the message flow; determining whether the received configuration point value violates the constraint and if so requesting another configuration point value from the input; and generating a configuration stencil instance based on the configuration stencil and the input, the configuration stencil instance representing the message flow in an integration of the first and second systems.