Method and system for re-deploying metadata and associated data from a source organization to a destination organization
First Claim
1. A method for re-deploying metadata and data from a source organization of a first tenant of a multi-tenant database system to a destination organization of a second tenant of the multi-tenant database system that is different than the source organization, the method comprising:
- selecting, via a user system, metadata that is to be retrieved from the source organization;
automatically creating, via a metadata engine that executes at one or more hardware-based processors, a manifest file that comprises the selected metadata that is to be retrieved from the source organization;
storing the manifest file at a secure file storage where it is securely stored for re-deployment to the destination organization;
automatically retrieving, via a data engine that executes at one or more other hardware-based processors, data associated with the selected metadata, wherein the selected metadata and the data associated with the selected metadata collectively make up an application, wherein the selected metadata comprises;
customized content of the source organization; and
wherein the data comprises;
records held by an object;
re-deploying, in response to an input from the user system, the manifest file of the selected metadata to the destination organization that is different than the source organization; and
re-deploying, via a data engine that executes at one or more other hardware-based processors, the data associated with the selected metadata to the destination organization that is different than the source organization,wherein each organization has a unique identifier (ID) that defines a logical space provided to a particular tenant of the multi-tenant database system and represents data of that particular tenant so that data of that particular tenant data is separate from data of all other tenants of the multi-tenant data base system, andwherein redeploying, via the data engine that executes at the one or more other hardware-based processors, the data comprises;
automatically reconstructing, at the data engine when the manifest file has been re-deployed, relationships amongst the data that has been successfully migrated to the destination organization and a new identifier that is associated with the data at the destination organization.
1 Assignment
0 Petitions
Accused Products
Abstract
Methods and systems are provided for re-deploying metadata and it'"'"'s associated data from a source organization to a destination organization of a cloud-based computing environment. After metadata that is to be retrieved from the source organization is selected, a metadata engine can automatically create a manifest file that comprises the selected metadata that is to be retrieved. The manifest file can then be stored at secure file storage for re-deployment. A data engine can then automatically retrieve data associated with the selected metadata based, for example, on objects specified in the selected metadata. This data can be automatically saved and stored at a secured database for re-deployment. Thereafter, both the manifest file and the data associated with the selected metadata can be re-deployed to the destination organization.
177 Citations
14 Claims
-
1. A method for re-deploying metadata and data from a source organization of a first tenant of a multi-tenant database system to a destination organization of a second tenant of the multi-tenant database system that is different than the source organization, the method comprising:
-
selecting, via a user system, metadata that is to be retrieved from the source organization; automatically creating, via a metadata engine that executes at one or more hardware-based processors, a manifest file that comprises the selected metadata that is to be retrieved from the source organization; storing the manifest file at a secure file storage where it is securely stored for re-deployment to the destination organization; automatically retrieving, via a data engine that executes at one or more other hardware-based processors, data associated with the selected metadata, wherein the selected metadata and the data associated with the selected metadata collectively make up an application, wherein the selected metadata comprises;
customized content of the source organization; and
wherein the data comprises;
records held by an object;re-deploying, in response to an input from the user system, the manifest file of the selected metadata to the destination organization that is different than the source organization; and re-deploying, via a data engine that executes at one or more other hardware-based processors, the data associated with the selected metadata to the destination organization that is different than the source organization, wherein each organization has a unique identifier (ID) that defines a logical space provided to a particular tenant of the multi-tenant database system and represents data of that particular tenant so that data of that particular tenant data is separate from data of all other tenants of the multi-tenant data base system, and wherein redeploying, via the data engine that executes at the one or more other hardware-based processors, the data comprises;
automatically reconstructing, at the data engine when the manifest file has been re-deployed, relationships amongst the data that has been successfully migrated to the destination organization and a new identifier that is associated with the data at the destination organization. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A computing system, comprising:
-
a source organization of a first tenant of a multi-tenant database system; a user system configured to select metadata that is to be retrieved from the source organization; a destination organization of a second tenant of the multi-tenant database system that is different than the source organization; and a platform for re-deploying selected metadata and data associated with that metadata from the source organization to the destination organization, wherein the selected metadata and the data associated with the selected metadata collectively make up an application, wherein the selected metadata comprises;
customized content of the source organization; and
wherein the data comprises;
records held by an object, the platform comprising;secure file storage; a secured database; a metadata engine that executes at one or more hardware-based processors and being configured to;
automatically create, in response to inputs received from the user system that indicate selected metadata that is to be retrieved from the source organization, a manifest file comprising the selected metadata that is to be retrieved from the source organization;
store the manifest file at the secure file storage where it is securely stored for re-deployment to the destination organization; and
re-deploy the manifest file to the destination organization that is different than the source organization; anda data engine that executes at one or more other hardware-based processors and being configured to;
automatically retrieve data that is associated with the selected metadata from the source organization;
store the data at the secured database; and
re-deploy the data associated with the selected metadata to the destination organization that is different than the source organization, wherein each organization has a unique identifier (ID) that defines a logical space provided to a particular tenant of the multi-tenant database system and represents data of that particular tenant so that data of that particular tenant data is separate from data of all other tenants of the multi-tenant database system, andwhen the manifest file has been re-deployed, wherein the data engine is further configured to automatically reconstruct relationships amongst the data that has been successfully migrated to the destination organization and a new identifier that is associated with the data at the destination organization. - View Dependent Claims (9, 10, 11, 12, 13)
-
-
14. A computing system comprising one or more hardware-based processors and a memory, wherein the memory comprises computer-executable instructions that are capable of execution by the one or more hardware-based processors, and that when executed by the one or more hardware-based processors, cause the computing system to:
-
automatically create, via a metadata engine that executes at one or more hardware-based processors in response to a selection of metadata that is to be retrieved from a source organization of a first tenant of a multi-tenant database system, a manifest file that comprises selected metadata that is to be retrieved from the source organization; store the manifest file at a secure file storage where it is securely stored for re-deployment; automatically determine data from the source organization based on objects specified in the selected metadata, and store the data at a secured database for re-deployment, wherein the data is associated with the selected metadata, wherein the selected metadata and the data associated with the selected metadata collectively make up an application, wherein the selected metadata comprises;
customized content of the source organization; and
wherein the data comprises;
records held by an object;re-deploy, in response to input from a user system, the manifest file of the selected metadata to a destination organization of a second tenant of the multi-tenant database system that is different than the source organization; and re-deploy, via a data engine that executes at one or more other hardware-based processors, the data associated with the selected metadata to the destination organization that is different than the source organization, wherein each organization has a unique identifier (ID) that defines a logical space provided to a particular tenant of the multi-tenant database system and represents data of that particular tenant so that data of that particular tenant data is separate from data of all other tenants of the multi-tenant database system, and when the manifest file has been re-deployed, wherein the one or more other hardware-based processors of the data engine are further configured to automatically reconstruct relationships amongst the data that has been successfully migrated to the destination organization and a new identifier that is associated with the data at the destination organization.
-
Specification