Database integration of originally decoupled components
First Claim
Patent Images
1. A computer system to integrate persistency of multiple components deployed in different database schemas, comprising:
- a memory to store a program code;
a processor communicatively coupled to the memory, the processor configured to execute the program code, to;
upon deploying a first component from a plurality of components, create a first persistency of the first component assigned to a first database schema;
upon deploying a second component from the plurality of components, create a second persistency of the second component assigned to a second database schema, wherein the first persistency is in a decoupled state from the second persistency;
read metadata of the first component to identify one or more first required tables required by the first component from the second database schema;
read metadata of the second component to identify one or more second required tables required by the second component from the first database schema;
create a first table link database object residing in the first database schema and a second table link database object residing in the second database schema, wherein the first table link exposes for access from the first database schema a first set of fields of the one or more first required tables stored in the second database schema, and wherein the second table link exposes for access from the second database schema a second set of fields of the one or more second required tables stored in the first database schema; and
integrate the first persistency of the first component assigned to the first database schema and the second persistency of the second component assigned to the second database schema, wherein the integration of the first persistency and the second persistency provisions removing name collisions between a plurality of database objects stored in the first database schema and the second database schema.
1 Assignment
0 Petitions
Accused Products
Abstract
A first component originally has a persistency decoupled from a persistency of a second component. The second component requires a table from the persistency of the first component. The first component is assigned a first database schema and the second component is assigned a second database schema. A table link is created in the second database schema of the second component, wherein the table link refers to the required table from the first database schema of the first component.
28 Citations
16 Claims
-
1. A computer system to integrate persistency of multiple components deployed in different database schemas, comprising:
-
a memory to store a program code; a processor communicatively coupled to the memory, the processor configured to execute the program code, to; upon deploying a first component from a plurality of components, create a first persistency of the first component assigned to a first database schema; upon deploying a second component from the plurality of components, create a second persistency of the second component assigned to a second database schema, wherein the first persistency is in a decoupled state from the second persistency; read metadata of the first component to identify one or more first required tables required by the first component from the second database schema; read metadata of the second component to identify one or more second required tables required by the second component from the first database schema; create a first table link database object residing in the first database schema and a second table link database object residing in the second database schema, wherein the first table link exposes for access from the first database schema a first set of fields of the one or more first required tables stored in the second database schema, and wherein the second table link exposes for access from the second database schema a second set of fields of the one or more second required tables stored in the first database schema; and integrate the first persistency of the first component assigned to the first database schema and the second persistency of the second component assigned to the second database schema, wherein the integration of the first persistency and the second persistency provisions removing name collisions between a plurality of database objects stored in the first database schema and the second database schema. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A computer implemented method to integrate persistency of multiple components deployed in different database schemas, comprising:
-
upon deploying a first component from a plurality of components, creating a first persistency of the first component assigned to a first database schema; upon deploying a second component from the plurality of components, creating a second persistency of the second component assigned to a second database schema, wherein the first persistency is in a decoupled state from the second persistency; reading metadata of the first component to identify one or more first required tables required by the first component from the second database schema; reading metadata of the second component to identify one or more second required tables required by the second component from the first database schema; creating a first table link database object residing in the first database schema and a second table link database object residing in the second database schema, wherein the first table link exposes for access from the first database schema a first set of fields of the one or more first required tables stored in the second database schema, and wherein the second table link exposes for access from the second database schema a second set of fields of the one or more second required tables stored in the first database schema; and integrating the first persistency of the first component assigned to the first database schema and the second persistency of the second component assigned to the second database schema, wherein the integration of the first persistency and the second persistency provisions removing name collisions between a plurality of database objects stored in the first database schema and the second database schema. - View Dependent Claims (8, 9, 10, 11, 12)
-
-
13. A non-transitory computer readable medium storing instructions, which when executed by a processor of a computer, cause the computer to perform operations, comprising:
-
upon deploying a first component from a plurality of components, create a first persistency of the first component assigned to a first database schema; upon deploying a second component from the plurality of components, create a second persistency of the second component assigned to a second database schema, wherein the first persistency is in a decoupled state from the second persistency; read metadata of the first component to identify one or more first required tables required by the first component from the second database schema; read metadata of the second component to identify one or more second required tables required by the second component from the first database schema; create a first table link database object residing in the first database schema and a second table link database object residing in the second database schema, wherein the first table link exposes for access from the first database schema a first set of fields of the one or more first required tables stored in the second database schema, and wherein the second table link exposes for access from the second database schema a second set of fields of the one or more second required tables stored in the first database schema; and integrate the first persistency of the first component assigned to the first database schema and the second persistency of the second component assigned to the second database schema, wherein the integration of the first persistency and the second persistency provisions removing name collisions between a plurality of database objects stored in the first database schema and the second database schema. - View Dependent Claims (14, 15, 16)
-
Specification