Componentized Resource Adapter Architecture for Enterprise Connectivity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current middleware systems face challenges in achieving standard connectivity to Enterprise systems across different runtime environments due to incompatible interfaces and the need for costly CPU-intensive data and format conversions, leading to high development and maintenance expenses and user inconsistencies.
Innovation Solution
A componentized resource adapter architecture that configures adapters to be specific to data sources, provides communication links, and converts data and metadata formats to standard formats, enabling reusable and efficient connectivity by using a single adapter for multiple products and environments, based on the J2EE Connector Architecture with extensions for metadata handling and efficient data exchange.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple adapters are built using various technologies to provide access to the same resources, then connectivity to Enterprise systems is achieved, but development costs and maintenance costs increase tremendously
Solution Approach 1:
The patent implements a universal adapter architecture where a single adapter can serve multiple runtime environments and middleware systems. The adapter is designed with configurable interfaces and metadata-driven connectivity that allows it to adapt to different targets (databases, transaction systems, etc.) without requiring separate adapters for each combination, thereby reducing the total number of adapters needed while maintaining broad connectivity capabilities
Solution Approach 2:
The adapter is segmented into distinct functional components including a configuration layer, metadata layer, and execution layer. This segmentation allows the adapter to be configured for different runtime environments through metadata without requiring structural changes, enabling one adapter to serve multiple purposes across different systems
2Adaptability or versatility
If data and format conversions are performed to achieve compatibility between different runtime environments, then connectivity is enabled, but CPU performance is degraded due to the costliness of conversions
Solution Approach 1:
The adapter performs preliminary actions by pre-configuring metadata and interface mappings during adapter initialization and deployment, rather than performing conversions at runtime. The metadata stores pre-defined format mappings and interface configurations that allow the adapter to directly invoke target system functions without requiring CPU-intensive data transformations during actual operations
Solution Approach 2:
The patent uses metadata as a copy mechanism to represent target system interfaces and data formats. Instead of physically transforming data between different formats, the adapter uses metadata descriptions to map source data structures to target structures, allowing direct data passage with minimal transformation overhead while achieving format compatibility
3Reliability
If current standards are defined for specific environments like Java EE, then standard connectivity is achieved within that environment, but adapter reuse between different runtime environments is not permitted
Solution Approach 1:
The patent extends the J2EE Connector Architecture by implementing a universal adapter framework that can operate across multiple runtime environments (Application Server, Information Management, System Management). The adapter uses environment-agnostic metadata and configurable interfaces that allow the same adapter to be deployed in different runtime contexts without modification, achieving both standard connectivity and cross-environment reusability
Solution Approach 2:
The adapter architecture is designed to be dynamic and configurable rather than static and environment-specific. The metadata-driven configuration allows the adapter to adapt its behavior and interface definitions based on the target runtime environment, enabling the same adapter binary to function correctly across different platforms without requiring environment-specific versions
4Adaptability or versatility
If interfaces are made incompatible or foreign infrastructure is utilized to share adapters between products, then adapter sharing is attempted, but additional complexity and conversion costs are introduced
Solution Approach 1:
The patent merges the configuration and metadata management functions directly into the adapter component itself, rather than requiring separate foreign infrastructure systems. The adapter contains embedded metadata repositories and configuration mechanisms that allow it to self-describe its capabilities and interfaces, eliminating the need for external configuration systems and reducing overall system complexity while enabling adapter sharing
Data Source
AI summary
A computer program product comprises a computer useable medium. The computer useable medium has a computer readable program such that when the computer readable medium is executed on a computer, the computer is caused to configure an adapter such that the adapter is specific to a data source, provides a communication link to the data source, converts a format of the data source to a format native to a middleware system, and converts a format of metadata of the data source to a standard metadata format. Further, the computer is caused to configure an application interface component to convert an invocation of a function in the middleware system to an invocation of a function provided by an Enterprise Information System through the adapter, convert the data format of the middleware system to a format native to the Enterprise Information System accessed through the adapter, and maintain metadata describing a message format and a function provided by the adapter.