SCA Generator Converting Tuxedo Metadata to SCDL Files

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The integration of Tuxedo® Service Metadata with Service Component Architecture (SCA) is hindered by the need for knowledge of both Tuxedo® and SCA frameworks, making it difficult for SCA servers to access Tuxedo® services and vice versa, due to differences in philosophy and programming models, and the complexity of XML-based files.

Innovation Solution

An SCA generator is configured to analyze input instructions, match service identifiers with metadata in the Tuxedo® Metadata Repository, generate parser trees, and produce output files that allow SCA servers to access services without requiring knowledge of the SCA framework, thereby facilitating the conversion of Tuxedo® Service Metadata into SCA SCDL files and schema files.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If Tuxedo Service Metadata is directly used by SCA server, then service access is enabled, but knowledge of both Tuxedo and SCA frameworks is required increasing complexity

Engineering Contradiction:
Improveservice access capabilityVSAvoidframework knowledge requirement
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary tool that automatically converts Tuxedo Service Metadata into SCA composite files. This mediator translates between the two different metadata formats and programming models, allowing SCA servers to access Tuxedo services without requiring developers to know both frameworks. The intermediary handles the complexity of dual-framework knowledge internally while presenting a simplified interface to users.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If XML-based composite and component files are used for SCA, then service description is achieved, but tedious file creation process increases development time

Engineering Contradiction:
Improveservice description accuracyVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-defining the conversion rules and mappings between Tuxedo Service Metadata and SCA composite file structures. The system prepares the transformation logic in advance, so when conversion is needed, it can automatically generate the XML-based composite and component files without requiring manual creation. This preliminary preparation of conversion mechanisms significantly reduces development time while maintaining description accuracy.

Inventive Principle:
Principle #10Preliminary action

3Manufacturing precision

If manual creation of SCA composite files is performed, then precise service configuration is achieved, but complexity of file generation increases

Engineering Contradiction:
Improveservice configuration precisionVSAvoidfile generation complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent uses copying by creating template-based composite file structures that can be automatically instantiated from Tuxedo Service Metadata. Instead of manually crafting each XML element, the system copies and adapts the service definition structure, preserving the precise configuration information while automating the file generation process. This copying approach maintains manufacturing precision through structured templates while reducing the perceived complexity for users.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8239419B2Generating service component definition language from metadata
Publication Date: 2012.08.07 ORACLE INT CORP
  • US8239419B2 patent drawing
  • US8239419B2 patent drawing
  • US8239419B2 patent drawing

AI summary

An SCA generator is configured to use data in a Metadata repository to generate files that can be used by an SCA server. The SCA generator includes an instruction analyzing module configured to analyze input instructions and to determine the Metadata repository from the input instructions. The SCA generator also includes a matching module configured to match a service identifier received with the input instructions to service metadata stored in the Metadata repository and a retrieving module configured to retrieve service parameters for the matched service. The SCA generator further includes a tree generating module configured to generate a parser tree based on the retrieved service parameters and an output file generation module configured to recursively walk through the parser tree and to generate target output files. The target output files generated by the output generation module are configured such that the SCA server can access services that have associated service metadata stored in the Metadata repository.