Patent Application
20160094403
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
Embodiments of the invention are generally related to application servers and cloud environments, and are particularly related to a system and method for providing data sources for use in a multitenant application server environment.
Software application servers, examples of which include Oracle WebLogic Server (WLS) and Glassfish, generally provide a managed environment for running enterprise software applications. Recently, technologies have also been developed for use in cloud environments, which allow users or tenants to develop and run their applications within the cloud environment, and to take advantage of distributed resources provided by the environment. As such, application resources, for example data sources, in a traditional application server environment may have to be modified for such a cloud environment.
In accordance with an embodiment, described herein is a system and method for providing data sources in a multitenant application server environment. The system includes a an application server environment with a plurality of partitions and a resource group template referenced by a resource group in one or more of the plurality of partitions; and a data source configuration defined as part of the resource group template. The data source configuration can be overridden with attributes specific to a particular referencing partition. A data source subsystem can create a data source object in accordance with the overridden data source configuration, for use in creating connections to a database associated with the particular referencing partition, monitoring and diagnosing the data source object.
Multi-tenancy can reduce administrative overhead associated with managing multiple domains and application deployments, and improve density of deployments, such that operational and infrastructure costs are reduced. As heavily used application resources, data sources need to support partition-based configuration, runtime monitoring, security, diagnostics, etc. to meet the general goals of multi-tenancy.
In accordance with an embodiment, described herein is a system and method for providing data sources in a multitenant application server environment. The system includes a an application server environment with a plurality of partitions and a resource group template referenced by a resource group in one or more of the plurality of partitions; and a data source configuration defined as part of the resource group template. The data source configuration can be overridden with attributes specific to a particular referencing partition. A data source subsystem can create a data source object in accordance with the overridden data source configuration, for use in creating connections to a database associated with the particular referencing partition, monitoring and diagnosing the data source object.
As illustrated in
In accordance with an embodiment, the application server can include one or more partitions 104 that are defined for use at runtime. Each partition can be associated with a globally unique partition identifier (ID) and partition configuration, and can further include one or more resource groups 124, together with a reference to a resource group template 126 and/or partition-specific applications or resources 128. Domain-level resource groups, applications and/or resources 140 can also be defined at the domain level, optionally with a reference to a resource group template.
Each resource group template 160 can define one or more applications A 162, B 164, resources A 166, B 168, and/or other deployable applications or resources 170, and can be referenced by a resource group. For example, as illustrated in
Generally, a system administrator can define partitions, domain-level resource groups and resource group templates, and security realms; while a partition administrator can define aspects of their own partition, for example, by creating partition-level resource groups, deploying applications to the partition, or referencing specific realms for the partition.
As illustrated in
The resource group template illustrated in
In accordance with an embodiment, when a resource group within a partition (e.g., 202) references 220 a particular resource group template (e.g., 210), information associated with a particular partition can be used in combination with the referenced resource group template, to indicate a partition-specific information 230, for example a partition-specific PDB information. The partition-specific information can then be used by the application server to configure resources, for example a PDB resource, for use by the partition. For example, partition-specific PDB information associated with partition 202 can be used, by the application server, to con
Similarly, in accordance with an embodiment, a virtual target information associated with a particular partition can be used to define 239 a partition-specific virtual target 240, for use by the partition, e.g., baylandurgentcare.com, which can then be made accessible via a uniform resource locator (URL), e.g., http://baylandurgentcare.com.
In accordance with an embodiment, a system configuration such as a config.xml configuration file, is used to define a partition, including configuration elements for resource groups associated with that partition, and/or other partition properties. Values can be specified per-partition using property name/value pairs.
In accordance with an embodiment, a plurality of partitions can be executed within a managed server/cluster 242, or a similar environment which can provide access to a CDB 243, and which are accessible via a web tier 244. This allows, for example, a domain or partition to be associated with one or more of the PDBs (of the CDB).
In accordance with an embodiment, each of the plurality of partitions, in this example partition A 250 and partition B 260, can be configured to include a plurality of resources associated with that partition. For example, partition A can be configured to include a resource group 251 which contains an application A1252, application A2254, and JMS A 256, together with a datasource A 257 associated with PDB A 259, wherein the partition is accessible via a virtual target A 258. Similarly, partition B 260 can be configured to include a resource group 261 which contains an application B1262, application B2264, and JMS B 266, together with a datasource B 267 associated with PDB B 269, wherein the partition is accessible via a virtual target B 268.
While several of the above examples illustrate use of CDB and PDBs, in accordance with other embodiments, other types of multi-tenant or non-multi-tenant databases can be supported, wherein a particular configuration can be provided for each partition, for example through the use of schemas, or the use of different databases.
In accordance with an embodiment, a resource is a system resource, application, or other resource or object that can be deployed to a domain of the environment. For example, in accordance with an embodiment, a resource can be an application, JMS, JDBC data source, JavaMail, WLDF, or other system resource or other type of object that can be deployed to a server, cluster, or other application server target.
In accordance with an embodiment, a partition is a runtime and administrative subdivision or slice of a domain that can be associated with a partition identifier (ID) and configuration, and can contain applications and/or refer to domain-wide resources through the use of resource groups and resource group templates.
Generally, a partition can contain its own applications, refer to domain wide applications via resource group templates, and have its own configuration. Partitionable entities can include resources, for example JMS, JDBC, JavaMail, WLDF resources, and other components, such as JNDI namespace, network traffic, work managers, and security policies and realms. In the context of a multi-tenant environment, the system can be configured to provide tenant access to the administrative and runtime aspects of partitions associated with a tenant.
In accordance with an embodiment, each resource group within a partition can optionally reference a resource group template. A partition can have multiple resource groups, and each of them can reference a resource group template. Each partition can define properties for configuration data that is not specified in the resource group templates to which the partition's resource groups refer. This enables the partition to act as a binding of deployable resources defined in a resource group template, to specific values for use with that partition. In some cases, a partition can override configuration information specified by a resource group template.
In accordance with an embodiment, a partition configuration, as defined for example by a config.xml configuration file, can include a plurality of configuration elements, for example: “partition”, which contains the attributes and child elements that define the partition; “resource-group”, which contains the applications and resources deployed to the partition; “resource-group-template”, which contains applications and resources defined by that template; “jdbc-system-resource-override”, which contains a database-specific service name, user name, and password; and “partition-properties”, which contains property key values that can be used for macro replacement in resource group templates.
Upon startup, the system can use the information provided by the configuration file to generate partition-specific configuration elements for each resource, from the resource group template.
In accordance with an embodiment, a resource group is a named, fully-qualified collection of deployable resources that can be defined either at a domain or partition level, and can reference a resource group template. The resources in a resource group are considered fully-qualified in that the administrator has provided all of the information needed to start or connect to those resources, for example the credentials for connecting to a data source, or the targeting information for an application.
A system administrator can declare resource groups at the domain level, or at the partition level. At the domain level, a resource group provides a convenient way to group related resources. The system can manage resources declared in a domain-level resource group the same as ungrouped resources, so that the resources can be started during system start-up, and stopped during system shut-down. An administrator can also stop, start, or remove a resource in a group individually, and can act on all the resources in a group implicitly by operating on the group. For example, stopping a resource group stops all of the resources in the group that are not already stopped; starting the resource group starts any resources in the group that are not already started; and removing the resource group removes all of the resources contained in the group.
At the partition level, a system or partition administrator can configure zero or more resource groups in a partition, subject to any security restrictions. For example, in a SaaS use case, various partition-level resource groups can refer to domain-level resource group templates; while in a PaaS use case, partition-level resource groups can be created that do not refer to resource group templates, but instead represent applications and their related resources that are to be made available within that partition only.
In accordance with an embodiment, resource grouping can be used to group together applications and the resources they use as a distinct administrative unit within the domain. For example, in the medical records (MedRec) application described below, a resource grouping defines the MedRec application and its resources. Multiple partitions can run the same MedRec resource group, each using a partition-specific configuration information, such that the applications that are part of each MedRec instance are made specific to each partition.
In accordance with an embodiment, a resource group template is a collection of deployable resources that are defined at a domain level, that can be referenced from a resource group, and some of the information required to activate its resources may not be stored as part of the template itself, such that it supports the specification of partition level configuration. A domain can contain any number of resource group templates, each of which can include, for example, one or more related Java applications and the resources on which those applications depend. Some of the information about such resources may be the same across all partitions, while other information may vary from one partition to the next. Not all configuration need be specified at the domain level—partition level configuration can instead be specified in the resource group template through the use of macros, or property name/value pairs.
In accordance with an embodiment, a particular resource group template can be referenced by one or more resource groups. Generally, within any given partition, a resource group template can be referenced by one resource group at a time, i.e., not simultaneously by multiple resource groups within the same partition; however, it can be referenced at the same time by another resource group in a different partition. The object containing the resource group, e.g., the domain or partition, can use property name/value assignments to set the value of any tokens in the resource group template. When the system activates a resource group template using a referencing resource group, it can replace those tokens with values set in the resource group's containing object. In some cases, the system can also use statically-configured resource group templates and partitions to generate runtime configuration for each partition/template combination.
For example, in a SaaS use case, the system can activate the same applications and resources multiple times, including once for each partition that will use them. When an administrator defines a resource group template they can use tokens to represent the information that will be supplied elsewhere. For example, the username to use in connecting to a CRM-related data resource can be indicated in the resource group template as \${CRMDataUsername}.
In accordance with an embodiment, in a multi-tenant environment, such as a multi-tenant (MT) application server environment, a tenant is an entity that can be represented by, or otherwise associated with, one or more partitions and/or one or more tenant-aware applications.
For example, tenants can represent distinct user organizations, such as different external companies, or different departments within a particular enterprise (e.g., HR and Finance departments), each of which can be associated with a different partition. A tenant globally unique identity (tenant ID) is the association of a particular user, at a particular moment in time, with a particular tenant. The system can derive which tenant a particular user belongs to from the user identity, for example by referring to a user identity store. The user identity enables the system to enforce those actions that a user is authorized to perform, including, but not limited to, which tenant the user may belong.
In accordance with an embodiment, the system enables isolation of the administration and runtime of different tenants from each other. For example, tenants can configure some behaviors of their applications, and resources to which they have access. The system can ensure that a particular tenant cannot administer artifacts belonging to another tenant; and, at runtime, that the applications working on behalf of a particular tenant refer only to resources associated with that tenant, and not to resources associated with other tenants.
In accordance with an embodiment, a tenant-unaware application is one that contains no logic dealing with tenants explicitly, such that any resources that the application uses may be accessible regardless of what user submitted a request to which the application is responding. In contrast, a tenant-aware application includes logic that explicitly deals with tenants. For example, based on a user's identity the application can derive the tenant to which the user belongs and use that information to access tenant-specific resources.
In accordance with an embodiment, the system enables users to deploy applications that are explicitly written to be tenant-aware, so that application developers can obtain the tenant ID of a current tenant. The tenant-aware application can then use the tenant ID to handle multiple tenants that are using a single instance of the application.
For example, the MedRec application, which supports a single doctor's office or hospital, can be exposed to two different partitions or tenants, e.g., a Bayland Urgent Care tenant, and a Valley Health tenant, each of which is able to access separate tenant-specific resources, such as separate PDBs, without changing the underlying application code.
In accordance with an embodiment, applications can be deployed to a resource group template at the domain level, or to a resource group that is scoped to a partition or scoped to the domain. Application configuration can be overridden using deployment plans specified per-application, or per-partition.
In accordance with an embodiment, when the system starts a partition, it creates virtual targets (e.g., virtual hosts) and data sources, including one for each partition, to respective database instances, according to the provided configuration.
Typically, each resource group template can include one or more related applications and the resources on which those applications depend. Each partition can provide configuration data that is not specified in the resource group templates to which it refers, by providing a binding of the deployable resources in resource group templates to specific values associated with the partition; including, in some cases, overriding certain configuration information specified by the resource group template. This enables the system to activate an application represented by a resource group template differently for each partition, using the property values each partition has defined.
In some instances, a partition may contain resource groups that do not refer to resource group templates, or that directly define their own partition-scoped deployable resources. Applications and data sources that are defined within a partition are generally available only to that partition. Resources can be deployed so that they can be accessed from across partitions using partition:<partitionName>/<resource JNDI name>, or domain:<resource JNDI name>.
For example, a MedRec application can include a plurality of Java applications, a data source, a JMS server, and a mail session. To run the MedRec application for multiple tenants, the system administrator can define a single MedRec resource group template 286, declaring those deployable resources in the template.
In contrast to domain-level deployable resources, the deployable resources declared in a resource group template may not be fully configured in the template, or cannot be activated as-is, since they lack some configuration information.
For example, the MedRec resource group template may declare a data source used by the applications, but it may not specify a URL for connecting to the database. Partitions associated with different tenants, for example, partition BUC-A 290 (Bayland Urgent Care, BUC) and partition VH-A 292 (Valley Health, VH) can reference one or more resource group templates, by each including a MedRec resource group 293, 294 that references 296, 297 the MedRec resource group template. The reference can then be used to create 302, 306, the virtual targets/virtual hosts for each tenant, including a virtual host baylandurgentcare.com 304 associated with the BUC-A partition, for use by the Bayland Urgent Care tenant; and a virtual host valleyhealth.com 308 associated with the VH-A partition, for use by the Valley Health tenant.
In accordance with an embodiment, each partition 321, 331 can define a different virtual target on which to accept incoming traffic for that tenant environment, and a different URL 322, 332 for connecting to the partition and to its resources 324, 334, including in this example either a bayland urgent care database, or a valley health database respectively. The database instances can use compatible schemas, since the same application code will execute against both databases. When the system starts the partitions, it can create the virtual targets and data sources to the respective database instances.
In an application server, for example a WebLogic application server, a user can configure database connectivity by adding data sources to an application domain. A data source can be an object that provides database access and database connection management. Each data source can contain a pool of database connections that are created when the data source object is created or at server startup. Applications can reserve a database connection from the data source by looking up the data source in a Java Naming and Directory Interface (JNDI) tree or in the local application context.
In accordance with an embodiment, a data source object can be created using vendor-specific mechanisms, such as commands, from a data source configuration, which can be specified using annotations or a deployment descriptor.
A data source object can include a set of properties that identify and describe a real-world database that it represents. These properties can include information such as the location of the database server, the name of the database, security credentials, and the network protocol to use to communicate with the database server.
As heavily used application resources, data sources need to support partition-based configuration, runtime monitoring, security, diagnostics, etc. to meet the general goals of multi-tenancy, examples of which can include reducing administrative overhead associated with managing multiple domains and application deployments, and improving density of deployments to reduce operational and infrastructure costs.
In accordance with an embodiment, described herein is a system and method for providing data sources in a multitenant application server environment. The system includes a an application server environment with a plurality of partitions and a resource group template referenced by a resource group in one or more of the plurality of partitions; and a data source configuration defined as part of the resource group template. The data source configuration can be overridden with attributes specific to a particular referencing partition. A data source subsystem can create a data source object in accordance with the overridden data source configuration, for use in creating connections to a database associated with the particular referencing partition, monitoring and diagnosing the data source object.
In accordance with an embodiment, a data source configuration defined in the referenced resource group template can be scoped to the partition that includes the referencing resource group. However, the data source configuration may lack a database URL or have an incorrect URL; and/or database credentials. As such, the data source configuration may need to be qualified with partition-specific JDBC attributes, and have the appropriate overrides specified for deployment to a runtime of the partition.
In accordance with an embodiment, a given data source configuration can only be referenced by a single resource group in a partition. Having multiple resource group references can result in a naming conflict at deployment time, similar to referencing a deployment descriptor from multiple domain-level system resources.
In accordance with an embodiment, a data source configuration can additionally be referenced from a resource group, either a domain-level resource group or a partition-level resource group. Such a referenced data source configuration needs to be qualified with appropriate credentials, URL, driver properties of the database to be connected to, and attributes of the intended scope (i.e. partition scope or domain scope).
In accordance with an embodiment, when a data source configuration defined in a resource group template is referenced by a partition-level resource group, a bean component (for example, JDBCSystemResourceOverride MBean) per data source configuration can be used to qualify that data source configuration. In addition, a deployment plan can be specified at the partition-level to qualify the referenced data source configuration. During processing of override attributes, the deployment plan is processed before applying the override attributes to the referenced data source configuration. When a given data source attribute is specified in both a deployment plan and an overriding bean, the latter takes precedence.
In accordance with an embodiment, a given data source descriptor (for example, config/jdbc/datasourcename-jdbc.xml) at a domain level can only be referenced by a single domain-level resource group. Otherwise, the same system resource would be deployed two or more times, resulting in potential naming conflicts, binding errors, etc. For example, having two domain-level resource group definitions that refer to a same data source descriptor is comparable to defining two domain-level system resources that reference the same data source descriptor. Additionally, as an overriding bean or a deployment plan as described above is available only at a partition level, overriding capability at the domain level is not supported.
At runtime, a data source subsystem can create a data source object in according with a data source configuration that has been qualified for a particular partition. A connection pool can be created using the data source object, to contain one or more connections to a pluggable database associated with the particular partition. An identifier of the particular partition and the data source object can be used to generate statistics associated with the data source object, for monitoring and diagnostic purposes.
As shown in
In accordance with an embodiment, the domain can additionally include a resource group template 633, referenced 655, 657 respectively by a resource group (for example, resource group A 617 in partition A, and resource group B 623 in partition B in the domain).
As further shown in
In accordance with an embodiment, by referencing the resource group template, the referencing resource group in partition A and partition B can obtain at deployment time a copy (for example, data source configuration 636 and data source configuration 637) of the data source configuration defined in the resource group template. Each copy of the data source configuration can be qualified or overridden 649, 665 with partition-specific attributes using a configuration bean component (for example, JDBC system resource override Mbean 637 or JDBC system resource override Mbean 638).
For example, as each partition can be associated with a pluggable database, attributes such as the URL and settings of each PDB, a service to be connected to, and security credentials, can be overridden to be partition-specific.
In accordance with an embodiment, attributes in a JDBC system resource override Mbean instance can represent data source settings that can typically be qualified on a per-partition basis for SaaS use cases. In addition, the JDBC system resource override Mbean can qualify settings of databases from different vendors, for example MySQL and DB2, especially for PaaS use cases.
In accordance with an embodiment, each copy of the data source configuration can be additionally qualified or overridden 651, 631 with partition-specific attributes using a deployment plan (for example, deployment plan 648 and deployment plan 627). Each of the deployment plans can be specified for a resource group, and defined in an external file whose path is specified in a partition configuration. The deployment plans can be used to override arbitrary attributes of the data source configurations. During override processing, the deployment plans are processed before applying override MBean attributes to the data source configurations. If a given data source attribute is specified in both a deployment plan and an override MBean, the override MBean value takes precedence.
In accordance with an embodiment, a domain-level resource group can reference the data source configuration defined in the resource group template. As discussed above, only one domain-level resource group can reference this data source configuration. In addition, the domain-level resource group cannot override the data source configuration, as the two overriding approaches, i.e. using a deployment plan and using an override Mbean, are available only at a partition level.
In accordance with an embodiment, when an application-scoped data source configuration (for example, data source configuration) is defined in a partition-scoped resource group, the defining resource group needs to provide a deployment plan to appropriately qualify the data source attributes and driver properties for the partition.
Listing 1 illustrates how a JDBC system resource override Mbean is used in domain configuration file, to qualify a data source configuration, in accordance with an embodiment.
As shown in Listing 1, the JDBCSystemResourceOverride section of the partition configuration in the domain configuration file defines overrides of a data source (i.e. the MedRecGlobalDataSourceXA). The configuration of the data source is specified in a resource group template (i.e. MedRecResourceTemplate) which is referenced by a partition's resource group (i.e. ValleyHealthMedRec).
Listing 2 illustrates an example data source configuration specified in a source group template in accordance with an embodiment.
As shown in Listing 2, the data source configuration does not have all the attributes needed to connect to a database and may need to be overridden using partition-specific attributes.
For example, the URL, user and password are missing. The missing attributes can be provided using a deployment plan or an override bean component as discussed above.
Listing 3 below illustrates an example deployment plan in accordance with an embodiment.
The example deployment plan illustrated in Listing 3 is referenced by the domain configuration file illustrated in Listing 1, and demonstrates changing the MaxCapacity attribute of the data source configuration illustrated Listing 2.
In accordance with an embodiment, a data source subsystem 665 can create data source objects using 669, 671 the overridden data source configurations from partition A and partition B. The created data source objects can be used to create connections pools that include JDBC connections to configured databases.
In accordance with an embodiment, a data source object or instance can be bound into an appropriate JNDI context at deployment time under a name specified in the data source configuration.
For example, a data source defined in an application can be bound to an application JNDI namespace, and a data source defined in a domain-level resource group or referenced by the domain-level resource group can be bound to a global JNDI namespace.
In accordance with an embodiment, a data source object obtained from a JNDI namespace preserves its scope when accessed under a different partition context. As such, a partition cannot see a data source defined in another partition or at a domain level.
In accordance with an embodiment, a data source defined in one partition can be configured to enable the data source's JNDI binding visible in other partitions.
For example, a connection property (for example, weblogic.jdbc.crossPartitionEnabled) on a data source can be set to indicate that cross-partition JNDI access is allowed. Similarly, a JNDI binding of a domain-level data source can be made visible to individual partitions by setting the cross-partition connection property.
In accordance with an embodiment, each data source bound to a JNDI tree can be qualified by a partition name associated with the data source. This qualification can be used to look up a target data source.
For example, as further shown in
As shown in
In accordance with an embodiment, partition-scoped data source runtime MBeans can have a name attribute like com.bea:ServerRuntime=myserver,Name=ds1,Type=JDBCDataSourceRuntime,PartitionRuntime=p. The parent attribute of the name attribute can be set to com.bea:ServerRuntime=myserver, Name-p1, Type=PartitionRuntime. In the above examples, the partition-scoped data source name is “ds1”, the partition name is “p1” and the server name is “myserver”.
The name properties can be used 717 at a monitoring interface (for example, data source monitoring interface 719) at an administration console, to identify a data source object for monitoring. Runtime statistics of the identified data source object can be populated from the data source runtime bean for displaying at the monitoring interface.
For example, the runtime statistics can include the scope of the data source, the server instance the data source is deployed, its state (running or stopped), active connection counts, and current capacity.
As shown in
In accordance with an embodiment, a data source object (for example, data source object 815) can be created by the data source subsystem for the data source configurations in partition A. The created data object can include a connection pool (for example, connection pool 819).
As further shown in
As shown in
At step 913, a data source configuration can be defined as part of the resource group template.
At step 915, the data source configuration can be overridden with attributes specific to a particular referencing partition.
At step 917, a data source object can be created using the overridden data source configuration, for use in creating connections to a database associated with the particular referencing partition, monitoring and diagnosing the data source object.
The present invention may be conveniently implemented using one or more conventional general purpose or specialized digital computer, computing device, machine, or microprocessor, including one or more processors, memory and/or computer readable storage media programmed according to the teachings of the present disclosure. Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art.
In some embodiments, the present invention includes a computer program product which is a non-transitory storage medium or computer readable medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the present invention. The storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DVD, CD-ROMs, microdrive, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data.
The foregoing description of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations will be apparent to the practitioner skilled in the art. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalents.
This application claims the benefit of priority to U.S. Provisional Application titled “SYSTEM AND METHOD FOR DATA SOURCE IN A MULTITENANT APPLICATION SERVER ENVIRONMENT”, Application No. 62/055,853, filed Sep. 26, 2014; and is related to U.S. Provisional Application titled “SYSTEM AND METHOD FOR SUPPORTING MULTITENANCY IN AN APPLICATION SERVER, CLOUD, OR OTHER ENVIRONMENT”, Application No. 61/929,888, filed Jan. 21, 2014; and U.S. Patent Application titled “SYSTEM AND METHOD FOR SUPPORTING MULTI-TENANCY IN A APPLICATION SERVER, CLOUD, OR OTHER ENVIRONMENT”, application Ser. No. 14/601,883, filed Jan. 21, 2015; each of which above applications are herein incorporated by reference.
| Number | Date | Country | |
|---|---|---|---|
| 62055853 | Sep 2014 | US |
