External platform extensions in a multi-tenant environment
US-2015033365-A1 · Jan 29, 2015 · US
US9621673B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9621673-B2 |
| Application number | US-201314103879-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 12, 2013 |
| Priority date | Dec 12, 2013 |
| Publication date | Apr 11, 2017 |
| Grant date | Apr 11, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Customer initiated tenant operations are presented that are provided within a work center of a client cloud application. System supported tenant operations combined with automatic validations and determinations are exposed directly to the customer via the work center. Customers are able to coordinate and initiate tenant operations using a specific work center called a service control center, which is added to other work centers that build the cloud enterprise applications or products the customers are using. The enterprise application embedded service control center is connected to a central service control center, which is located in a service provider cockpit system. The central service control center enables the execution of customer specific tenant operations that are tailored to the customer's landscape and guarantees the tenant isolation.
Opening claim text (preview).
What is claimed is: 1. A computer implemented method comprising: receiving a request to initiate a tenant operation from a work center of a cloud application, wherein the tenant operation includes provisioning of a new tenant; triggering a validation procedure to check permissions for executing the requested tenant operation; receiving source tenant data to be used for the provisioning of the new tenant via the requested tenant operation; and triggering the provisioning of the new tenant in a service provider cockpit system from the requested tenant operation based on the received source tenant data. 2. The method of claim 1 , further comprising: creating the new tenant based on the received source tenant data; and sending an update to the work center of the cloud application with the created new tenant. 3. The method of claim 1 , further comprising: automatically determining a source tenant for the provisioning of the new tenant by the service provider cockpit system; and automatically determining the source tenant for the provisioning of the new tenant by receiving a selection of the source tenant from the work center. 4. The method of claim 1 , wherein receiving the source tenant data comprises: receiving a data source selection for the new tenant that specifies the source tenant for obtaining application data for the new tenant; receiving a data source tenant identifier; and receiving a solution profile source tenant identifier that specifies the source tenant for obtaining configuration data for the new tenant. 5. The method of claim 4 , wherein the data source tenant identifier is different from the solution profile source tenant identifier. 6. The method of claim 1 , wherein the validation procedure checks the permissions based on information collected from a global invoicing and billing system. 7. The method of claim 1 , wherein the tenant operation includes a request to terminate an existing tenant. 8. A computer system providing bundle-to-bundle authentication in modular systems, comprising: a processor; a memory in communication with the processor, the memory storing instructions related to: a service provider cockpit system running on a cloud platform; a service control center backend engine to receive a request to initiate a tenant operation from a work center of a cloud application, wherein the tenant operation includes provisioning of a new tenant; and a tenant operations engine that triggers a validation procedure to check permissions for executing the requested tenant operation, determines source tenant data to be used for the provisioning of the new tenant, and creates the new tenant. 9. The computer system of claim 8 , further comprising a tenant communications adapter that determines from which tenant and user the request was sent and which data can be accessible from the tenant and the user. 10. The computer system of claim 8 , further comprising a tenant data collector that stores collects and stores replicated data. 11. The computer system of claim 8 , further comprising a global invoicing and billing system that maintains data used in the validation procedure to check permissions for executing the requested tenant operation. 12. The computer system of claim 8 , wherein the source tenant data comprises: a data source selection for the new tenant that specifies the source tenant for obtaining application data for the new tenant; a data source tenant identifier; and a solution profile source tenant identifier that specifies the source tenant for obtaining configuration data for the new tenant. 13. The system of claim 12 , wherein the data source tenant identifier is different from the solution profile source tenant identifier. 14. A non-transitory computer-readable medium storing instructions, which when executed cause a computer system to: receive a request to initiate a tenant operation from a work center of a cloud application, wherein the tenant operation includes provisioning of a new tenant; trigger a validation procedure to check permissions for executing the requested tenant operation; receive source tenant data to be used for the provisioning of the new tenant via the requested tenant operation; and trigger the provisioning of the new tenant in a service provider cockpit system from the requested tenant operation based on the received source tenant data. 15. The computer-readable medium of claim 14 , further comprising instructions that cause the computer system to: create the new tenant based on the received source tenant data; and send an update to the work center of the cloud application with the created new tenant. 16. The computer-readable medium of claim 14 , further comprising instructions that cause the computer system to: automatically determine a source tenant for the provisioning of the new tenant by the service provider cockpit system; and automatically determine the source tenant for the provisioning of the new tenant by receiving a selection of the source tenant from the work center. 17. The computer-readable medium of claim 14 , further comprising instructions that cause the computer system to: receive a data source selection for the new tenant that specifies the source tenant for obtaining application data for the new tenant; receive a data source tenant identifier; and receive a solution profile source tenant identifier that specifies the source tenant for obtaining configuration data for the new tenant. 18. The computer-readable medium of claim 17 , wherein the data source tenant identifier is different from the solution profile source tenant identifier. 19. The computer-readable medium of claim 14 , wherein the validation procedure checks the permissions based on information collected from a global invoicing and billing system. 20. The computer-readable medium of claim 14 , wherein the tenant operation includes a request to terminate an existing tenant.
User profiles · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.