Multi-tenant application using hierarchical bean factory container

• US 10,182,107 B2
• Filed: 06/09/2016
• Issued: 01/15/2019
• Est. Priority Date: 09/12/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Jain, Vikrant
• Primary Examiner(s): Reza, Mohammad W
• Application Number:
  US15/178,435
• Publication Number:
  US 20160323368A1
• Time in Patent Office: 950 Days
• Field of Search: 726 4
• CPC Class Codes: G06F 2009/45562 Creating, deleting, cloning virtual machine instances
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/14 for detecting or protecting against malicious traffic
• CPC Class Codes: H04L 65/40 Support for services or applications
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

Various embodiments provide on premise and cloud deployment support for components that may not be multi-tenant enabled. A single application in a highly non-intrusive way without effecting application functional logic. On premise deployments can run with fixed default tenant and no tenant information needs to be captured anywhere anytime. The application code accesses the hierarchical bean factory to get any tenant specific or shared resources seamlessly without knowledge of multi-tenancy in functional code anywhere.

Claims

1. A method comprising:

receiving, at a computing device having one or more processors, a hierarchical bean factory associated with an application in a multi-tenant environment of a cloud infrastructure system, a parent bean factory representing a shared application context that is shared by entities in the hierarchical bean factory and each child bean factory representing an entity specific application context that is specific to each child in the hierarchical bean factory;

receiving a request to invoke a function associated with the application from a tenant in the multi-tenant environment;

identifying tenant information from the request, wherein the tenant information is identified during login of a user of the tenant to the cloud infrastructure system;

adding the identified tenant information to a session context;

determining, by the computing device, an entity based on the tenant information in the request;

determining, by the computing device, a child bean factory in the hierarchical bean factory that is associated with the entity that is determined based on the tenant information in the request;

accessing the application using the child bean factory that is associated with the entity; and

invoking, by the computing device, the function associated with the application using the child bean factory specific to the entity and the parent bean factory associated with the child bean factory specific to the entity,

wherein the child bean factory comprises services available in the parent bean factory and the child bean factory, and

wherein the parent bean factory is shared by a plurality of different tenants and is configured to provision a service for a plurality of child bean factories, each of the plurality of child bean factories belonging to the plurality of different tenants, in order to enable sharing of services between a plurality of tenants in the multi-tenant environment.

2. The method of claim 1 further comprising:

storing entity information in a session context; and

accessing the entity information in order to determine the child bean factory.

3. The method of claim 2 further comprising:

generating the entity information in response to authenticating a user of the tenant in the cloud infrastructure system, the tenant being the determined entity.

4. The method of claim 1 further comprising:

defining one or more interfaces in the parent bean factory; and

restricting access to the one or more interfaces in the parent bean factory to the child bean factory.

5. The method of claim 1 further comprising:

defining one or more entity aware components in the child bean factory; and

sharing access to the entity aware components based on only loading each entity aware component once per entity.

6. The method of claim 1 further comprising:

defining one or more shared components in the parent bean factory; and

sharing access to the shared components based on only loading each shared component once per application instance.

7. The method of claim 1 wherein the computing device forms part of a multi-tenant cloud computing environment.

8. The method of claim 1 wherein the computing device forms part of a single-tenant on-premise computing environment.

9. The method of claim 1 wherein the application includes a Java®

service, a customer resource management (CRM) service, or a human capital management (HCM) service.

10. The method of claim 1, wherein the multi-tenant environment is a multi-tenant cloud computing environment that enables a plurality of separate tenants each having a separate identity domain to share a cloud infrastructure system.

11. The method according to claim 1, wherein beans in the child bean factory specific to the entity override beans in the parent bean factory.

12. The method according to claim 1, wherein the hierarchical bean factory comprises a plurality of bean factories that handle a content and shared resources of each tenant in the multi-tenant environment.

13. The method according to claim 1, wherein the multi-tenant environment comprises multiple separate tenants sharing an identity domain.

14. The method according to claim 1, wherein the function associated with the application is invoked in accordance with a utility service that identifies tenant information.

15. The method according to claim 1, wherein invoking the function associated with the application is authorized by an identity management module configured to provide identity services.

16. The method according to claim 1, wherein in response to a component being defined in the child bean factory, overriding the component as defined in the parent bean factory to be in accordance with the component as defined in the child bean factory, wherein the component enables provisioning of a service.

17. The method according to claim 1, wherein the service comprises one of an online data storage service, a data backup service, a Web-based e-mail service, a document collaboration service, a database processing service, and a technical support service.

18. The method according to claim 1, wherein the tenant information in the child bean factory is configured to be referenced throughout the session context.

19. A non-transitory computer-readable medium storing a computer program product which when executed by a processor of a computer systems causes the processor to:

receive a hierarchical bean factory associated with an application in a multi-tenant environment of a cloud infrastructure system, a parent bean factory representing a shared application context that is shared by entities in the hierarchical bean factory and each child bean factory representing an entity specific application context that is specific to each child in the hierarchical bean factory;

receive a request to invoke a function associated with the application from a tenant in the multi-tenant environment;

identify tenant information from the request, wherein the tenant information is identified during login of a user of the tenant to the cloud infrastructure system;

add the identified tenant information to a session context;

determine an entity based on the tenant information in the request;

determine a child bean factory in the hierarchical bean factory that is associated with the entity that is determined based on the tenant information in the request;

access the application using the child bean factory that is associated with the entity; and

cause the function associated with the application to be invoked using the child bean factory specific to the entity and the parent bean factory associated with the child bean factory specific to the entity,

wherein the child bean factory comprises services available in the parent bean factory and the child bean factory, and

wherein the parent bean factory is shared by a plurality of different tenants and is configured to provision a service for a plurality of child bean factories, each of the plurality of child bean factories belonging to the plurality of different tenants, in order to enable sharing of services between a plurality of tenants in the multi-tenant environment.

20. The non-transitory computer-readable medium of claim 19 wherein the computer program product further causes the processor to:

store entity information in a session context; and

access the entity information in order to determine the child bean factory.

21. The non-transitory computer-readable medium of claim 20 wherein the computer program product further causes the processor to:

generate the entity information in response to authenticating a user of a tenant in a cloud infrastructure system, the tenant being the determined entity.

22. The non-transitory computer-readable medium of claim 19 wherein the computer program product further causes the processor to:

receive one or more interfaces defined in the parent bean factory; and

restrict access to the one or more interfaces in the parent bean factory to the child bean factories.

23. The non-transitory computer-readable medium of claim 19 wherein the computer program product further causes the processor to:

receive information identifying one or more entity aware components in the child bean factory; and

share access to the entity aware components based on only loading each entity aware component once per entity.

24. The non-transitory computer-readable medium of claim 19 wherein the computer program product further causes the processor to:

receive information identifying one or more shared components in the parent bean factory; and

share access to the shared components based on only loading each shared component once per application instance.

25. The non-transitory computer-readable medium of claim 19 wherein the application includes a Java®

service, a customer resource management (CRM) service, or a human capital management (HCM) service.

26. A system comprising:

at least one processor;

a memory storing a computer program product which when executed by the processor causes the processor to;

receive a hierarchical bean factory associated with an application in a multi-tenant environment of a cloud infrastructure system, a parent bean factory representing a shared application context that is shared by entities in the hierarchical bean factory and each child bean factory representing an entity specific application context that is specific to each child in the hierarchical bean factory;

receive a request to invoke a function associated with the application from a tenant in the multi-tenant environment;

identify tenant information from the request, wherein the tenant information is identified during login of a user of the tenant to the cloud infrastructure system;

add the identified tenant information to a session context;

determine an entity based on the tenant information in the request;

determine a child bean factory in the hierarchical bean factory that is associated with the entity that is determined based on the tenant information in the request;

access the application using the child bean factory that is associated with the entity; and

cause the function associated with the application to be invoked using the child bean factory specific to the entity and the parent bean factory associated with the child bean factory specific to the entity,

wherein the child bean factory comprises services available in the parent bean factory and the child bean factory, and

wherein the parent bean factory is shared by a plurality of different tenants and is configured to provision a service for a plurality of child bean factories, each of the plurality of child bean factories belonging to the plurality of different tenants, in order to enable sharing of services between a plurality of tenants in the multi-tenant environment.

27. The system of claim 26 wherein the computer program product further causes the processor to:

receive information identifying one or more interfaces in the parent bean factory; and

restrict access to the one or more interfaces to the child bean factories.

28. The system of claim 26 wherein the computer program product further causes the processor to:

receive information identifying one or more entity aware components in the child bean factory; and

share access to the entity aware components based on only loading each entity aware component once per entity.

29. The system of claim 26 wherein the computer program product further causes the processor to:

receive information identifying one or more shared components in the parent bean factory; and

share access to the shared components based on only loading each shared component once per application instance.