UDDI Data Migration Tool Preserving Entity Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current UDDI implementations lack interoperability, making it impossible to migrate user data from one UDDI V3 compliant repository to another without preserving entity keys and user names, as there is no universal tool available for this purpose.
Innovation Solution
A system and method for migrating UDDI V3 data from a source repository to a destination repository, preserving user names and entity keys where possible, and generating new ones with mapping to ensure seamless data transfer, using pure UDDI v3 SOAP requests and supporting mandatory APIs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a universal data migration tool is implemented to transfer UDDI data between different vendor repositories, then interoperability and data mobility are improved, but device complexity and implementation difficulty increase due to the need to handle multiple proprietary formats and APIs
Solution Approach 1:
The patent implements a universal migration tool that can transfer UDDI data between any two UDDI-compliant repositories from different vendors. The tool is designed to work with multiple proprietary implementations (IBM UDDI, GLOBE UDDI, etc.) through a unified interface, making it adaptable to various source and destination systems without requiring vendor-specific customization.
Solution Approach 2:
The migration tool acts as an intermediary between source and destination UDDI repositories. It retrieves data from the source repository using standard UDDI v3 APIs, transforms the data into a universal format, and then publishes it to the destination repository. This intermediary approach abstracts the complexity of dealing with different vendor-specific formats and APIs.
2Reliability
If entity keys and user names are preserved during migration, then data ownership and referential integrity are maintained, but conflicts arise when the same keys already exist in the destination repository
Solution Approach 1:
The migration tool performs preliminary checks before migrating data to identify conflicts with existing entity keys and user names in the destination repository. It retrieves the list of existing keys and names in advance, compares them with the source data, and prepares a conflict resolution plan before actual data transfer begins.
Solution Approach 2:
Instead of forcing preservation of original keys and names which causes conflicts, the tool inverts the approach by generating new unique keys and names for destination repository while maintaining referential integrity through mapping. The mapping table stores the correspondence between original and new identifiers, allowing the system to preserve data integrity without direct key conflicts.
3Reliability
If optional Security API Set is required for migration, then security and authentication are improved, but compatibility decreases as not all UDDI products support these optional APIs
Solution Approach 1:
The migration tool implements security functionality partially - it requires only the mandatory UDDI v3 APIs which are supported by all UDDI-compliant products. The optional Security API Set is not required, allowing the tool to work with any UDDI implementation while still providing basic authentication and authorization through the standard APIs.
Solution Approach 2:
The tool is designed to work universally with any UDDI repository that implements the mandatory v3 APIs, regardless of whether optional security extensions are available. It uses the standard UDDI authentication mechanisms that are present in all compliant implementations, ensuring broad compatibility while maintaining security.
4Ease of operation
If data is migrated with new user names and entity keys, then conflicts with existing destination data are avoided, but loss of information occurs in the form of broken references and lost ownership context
Solution Approach 1:
The migration tool creates a copy of the source data in the destination repository with new user names and entity keys. Instead of directly transferring references, it copies the data and generates new identifiers, then creates a mapping table that copies the relationship information between original and new identifiers.
Solution Approach 2:
The mapping table acts as an intermediary between the original and migrated data. It stores the correspondence between source and destination user names and entity keys, allowing the system to maintain referential integrity indirectly. When data needs to be accessed or updated, the mapping table translates references from the new identifiers back to the original context.
Data Source
AI summary
A system and method are described for Universal Description Discovery and Integration (UDDI) data migration exporting existing UDDI V3 data from a UDDI V3 compliant repository (a source repository) and importing this data into another UDDI V3 compliant repository (a destination repository). The data from the source repository is migrated into the destination repository and remains in the custody of the destination repository. The method preserves the user name and entity key associated with the data during the process. If that is not possible, the method generates new user names and/or entity keys and creates a mapping between the original and the generated user names and/or keys in order to dispatch the requests properly during runtime. Source repository is required to support the mandatory UDDI v3 APIs and may need to support the optional Security API Set. Destination repository is required to support the mandatory UDDI v3 API and the optional Security API Set. Other optional APIs (as replication and subscription for example) are not required to be supported by any of the repositories.