Service Manager for SOA Transaction and Debugging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing business software applications face challenges in providing flexible and consistent service management across different components, particularly in ensuring data consistency, concurrency, and debugging within a service-oriented architecture.

Innovation Solution

A method and system that utilize a service manager to collect requests, execute methods based on semantic descriptions from a repository, add tracing functionality, and manage transactions, allowing for flexible construction of services across application server components with consistent functionalities like transaction and concurrency management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a service-oriented architecture is implemented with multiple application components, then service flexibility and reusability are improved, but ensuring data consistency and managing transactions across components becomes more complex

Engineering Contradiction:
Improveservice flexibilityVSAvoidtransaction management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a service manager as an intermediary component that coordinates transactions across multiple application components. The service manager receives service requests, identifies the involved components, and manages the transaction lifecycle including setting transaction attributes, committing transactions, and handling rollbacks. This mediator approach resolves the contradiction by centralizing transaction management while preserving component flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The service manager is designed as a universal component that handles multiple functions: service request routing, transaction management, concurrency control, and debugging coordination. By consolidating these diverse functions into a single multi-functional component, the system achieves transaction consistency across flexible service-oriented architecture without proportionally increasing complexity.

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

2Difficulty of detecting and measuring

If tracing functionality is added to monitor method execution across components, then debugging capability is improved, but system complexity and overhead increase

Engineering Contradiction:
Improvedebugging capabilityVSAvoidsystem complexity
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

The service manager acts as an intermediary that collects and coordinates tracing information from multiple application components during method execution. Rather than each component implementing its own complex tracing system, the service manager centralizes the collection and management of tracing data, improving debugging capability while avoiding the complexity of distributed tracing implementation across all components.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If semantic descriptions are checked against service requests, then service consistency and correctness are improved, but request processing time increases

Engineering Contradiction:
Improveservice consistencyVSAvoidrequest processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-compiling service requests and pre-fetching semantic descriptions before actual service execution. The service manager prepares the matching criteria and available service information in advance, so that when a service request arrives, the semantic matching can be performed more efficiently. This reduces the time penalty of consistency checking while maintaining service correctness.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7685568B2Service management of a service oriented business framework
Publication Date: 2010.03.23 SAP SE
  • US7685568B2 patent drawing
  • US7685568B2 patent drawing
  • US7685568B2 patent drawing

AI summary

Methods and apparatus, including computer program products, for providing services by an application server, the method including collecting a request from a consumer software component for a service from a provider software component, and checking the request against a set of semantic descriptions in a manifest of methods provided by objects in the provider software component.