Database Module for Cross-Platform BPM Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing business process management (BPM) systems are limited to operating with a specific set of databases that support the same data types and properties, making it inconvenient and costly for customers to either replace their existing databases or find a compatible BPM system, as seen with tools like jBPM which is operable with HSQL and MySQL but not with other databases.
Innovation Solution
A BPM system is developed to be portable across various database types, including MySQL, HSQL, PostgreSQL, Sybase, and Oracle, using a database module that maps object data requests to database elements recognizable by all supported databases, allowing users to choose their database without needing to know the differences, and generates a uniform schema for database access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a BPM system is designed to work with multiple different database types, then adaptability is improved, but device complexity increases due to the need for mapping layers and schema generation
Solution Approach 1:
The patent introduces a database module as an intermediary layer between the BPMN engine and various database systems. This module contains a schema generator that creates database-specific schemas based on a universal process model, and database access managers that handle type-specific database operations. This mediator approach allows the BPM system to work with multiple database types (Oracle, MySQL, PostgreSQL, Sybase, HSQL) without requiring the core engine to know database-specific details, thus improving adaptability while managing complexity through abstraction.
2Manufacturing precision
If database-specific features and data types are supported, then manufacturing precision is improved, but ease of operation worsens due to the need for users to know database differences
Solution Approach 1:
The patent implements parameter changes by allowing the schema generator to automatically adapt database schema parameters based on the target database type. When a user selects a specific database (e.g., Oracle vs. MySQL), the system generates appropriate schemas with database-specific data types, constraints, and features. This automatic parameter adaptation ensures that each database receives optimally configured schemas while users interact with a统一的 interface, eliminating the need for users to manually adjust parameters or understand database-specific differences.
3Ease of operation
If a uniform schema is generated for all databases, then ease of operation is improved, but manufacturing precision worsens due to loss of database-specific features
Solution Approach 1:
The patent segments the schema generation process into two distinct phases: first, a universal process model is created that ensures consistency across all databases; second, the database access manager segments the schema generation to create database-specific implementations. This segmentation allows the system to maintain a uniform interface for users while generating optimized, database-specific schemas that utilize each database's unique features and data types. The universal model ensures operational ease, while the segmented database-specific generation preserves manufacturing precision.
Data Source
AI summary
A business process management (BPM) system operable with various database types. The BPM system may include a BPM process engine to execute business processes and request database access during execution, and a database module to access a database having one or more unique features that are inapplicable to other database types supported by the BPM system.