Cloud Database Integration via Service Management Engine

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud computing environments face challenges in integrating databases effectively, particularly in provisioning enterprise software applications that require database access within these environments.

Innovation Solution

A system and method that utilize a service management engine (SME) to access database coordinates and authentication information, enabling the creation of a pluggable database (PDB) within a container database (CDB) when requested by a service deployed in the cloud environment, with the SME managing database schema creation and association.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a service deployed to the cloud environment requests use of a database, then the database can be created with a schema for use by the service, but the complexity of integrating database provisioning into the cloud environment increases

Engineering Contradiction:
Improvedatabase integration capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a service management engine (SME) as an intermediary component that mediates between deployed services and the database system. The SME receives service requests, translates them into database provisioning operations, and manages the creation of databases and schemas. This intermediary layer simplifies the overall system architecture by centralizing the complex integration logic in a dedicated component rather than distributing it across multiple service and database interfaces.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual database provisioning is used for each service, then database access can be established, but the time required to provision databases increases

Engineering Contradiction:
Improvedatabase access reliabilityVSAvoidprovisioning time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by having the service management engine automatically initiate database creation and schema provisioning as soon as a service is deployed and requests database access. Instead of waiting for manual configuration, the system proactively creates the necessary database infrastructure in advance, including generating schemas, tables, and other database objects automatically based on service requirements. This eliminates the time delay associated with manual provisioning while ensuring reliable database access is established.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If automated database creation is implemented, then provisioning efficiency is improved, but the risk of authentication errors increases

Engineering Contradiction:
Improveprovisioning efficiencyVSAvoidauthentication reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The service management engine implements feedback mechanisms to monitor and verify authentication credentials during automated database creation. The system validates authentication information against the deployed service, checks for consistency and correctness, and provides feedback loops to detect and correct potential authentication errors. This feedback control ensures that while automation increases provisioning efficiency, the reliability of authentication remains high through continuous verification and error detection.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9817994B2System and method for integrating a database with a service deployed on a cloud platform
Publication Date: 2017.11.14 ORACLE INT CORP
  • US9817994B2 patent drawing
  • US9817994B2 patent drawing
  • US9817994B2 patent drawing

AI summary

Described herein are systems and methods for integrating a database into a cloud computing environment. In accordance with an embodiment, a system includes a service management engine (SME) configured to execute in the cloud environment and to access a provider type including coordinates to a database and authentication information for the database. When a service deployed to the cloud environment requests use of a database, the provider type can trigger creation of the database and a schema for use by the associated provider. In accordance with an embodiment, the provider type can include coordinates to a container database (CDB) and authentication information for the CDB. When a service deployed in the cloud environment requests a database, the provider type can trigger creation, via the CDB, of a pluggable database (PDB), with a schema for use by the service.