Multi-tenancy (MT) in WebLogic Server (WLS) provides a sharable infrastructure for use by multiple organizations. These organizations are a conceptual grouping of your own choosing, which you can think of as tenants. By allowing one domain to support multiple tenants, WebLogic-MT improves density and achieves a more efficient use of resources.
WebLogic-MT provides resource isolation within a domain partition, an administrative and runtime slice of a WebLogic domain that is dedicated to running application instances and related resources for a tenant. Domain partitions achieve greater density by allowing application instances and related resources to share the domain, WebLogic itself, the Java virtual machine (JVM), and the operating system, while isolating tenant-specific application data, configuration, and runtime traffic. Read more about WebLogic-MT here.
A premium feature in WebLogic-MT 12.2.1, Resource Consumption Management (RCM) provides resource isolation and tries to ensure that resources are allocated fairly to the partitions. It provides a policy infrastructure to limit usage of the shared resources and take appropriate actions when those specified limits are breached. It can also help maximize resource utilization in consolidated deployments.
As we saw, in WebLogic-MT there can be one or more co-located partitions in a single JVM. When partitions are co-located, they may consume or compete for the low-level resources offered by the OS/JVM. Low-level resources are often limited in nature. The (over-) consumption of these resources by one partition may (adversely) impact the other co-located partitions. Therefore, in WLS-MT, where partitions are co-located, it is important to isolate these partitions and the resources consumed by these partitions.
For example: If there are 100 file-descriptors available on a particular OS running WebLogic-MT that has 2 co-located partitions, one partition may end up consuming most of the available file-descriptors, leaving absolutely nothing for the other partition (implying the affected partition cannot function as expected). The affected partition has to bear the cost of being co-located with
As we can see, the Blue tenant is affected adversely because the Red tenant consumed most of the shared resources. The solution is to enforce policies through the RCM, so that one partition does not end up consuming all the low-level resources. With RCM, the system admin can define policies so the consumption of resources by one partition does not adversely affect the other co-located partitions. Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.