In this post, we are going to look at Oracle Weblogic Multitenancy. For those who are new, Multitenancy in WebLogic Server provides a shareable infrastructure for use by multiple organizations. These organizations are a conceptual grouping of your own choosing, which you can think of as tenants. To know in detail about Weblogic Multitenancy, go through the post below.
If you are a beginner and want to learn Oracle Weblogic Server Administration then check our blog post here where Atul covers about Weblogic Domain.
What is Weblogic Server MultiTenancy:
Multitenancy in WebLogic Server provides a shareable 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 Server MT improves density and achieves a more efficient use of resources while eliminating the hurdles typically present when trying to share multiple applications: runtime cross-application impact, security differences, data co-mingling, and administrative challenges.
WebLogic Server MT enables an end to end multitenant infrastructure, including multitenancy from the load balancer to the middle tier and cache tier, and to the database tier. WebLogic Server MT extends the Oracle WebLogic Server Enterprise Edition and Oracle WebLogic Suite products, and includes the following components:
- Oracle WebLogic Server MT, which enables the consolidation of applications into fewer domains (by allowing partitions within domains) while maintaining secure isolation
- WebLogic MT extensions to Java SE Advanced, which enables memory, CPU and I/O isolation, monitoring, and management for applications within a JVM
- Oracle WebLogic Coherence Enterprise Edition to Grid Edition option, which enables the consolidation of caches into fewer Oracle Coherence clusters while maintaining secure isolation
- Oracle Traffic Director, which provides WebLogic Server MT-aware and fully integrated tenant-aware local load balancing
Weblogic Server Domain Partitions:
WebLogic Server 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 Server itself, the Java virtual machine, and the operating system while isolating tenant-specific application data, configuration, and runtime traffic.
- Each domain partition has its own runtime copy of the applications and resources.
- Changes in how WebLogic Server handles class loading provide both application isolation and efficiency.
- Deploying to Multitenant environments requires no changes to your applications. For example, you could run multiple instances of a payroll application in different domain partitions without modifying the application.
When you deploy an application or library, you have four deployment scope options:
- Global. This is the equivalent of the domain level in a non-partitioned environment.
- Resource group template, which is always at the domain level. Whether the application or library you deploy to a resource group template is available at the domain level or a partition depends on the scope of the resource group that references the resource group template.
- Resource group in a partition. This is the only scope that is limited to a partition.
- Resource group at the domain level.
You cannot share an application or library between domain partitions: the application or library is available only within the partition. When you deploy the application or library, you specify the resource group in the partition. In FMW Control, applications and libraries that are deployed to a resource group in a partitioned display the name of the domain partition and the resource group within that partition where they are deployed.
The key difference between an application or class running at the domain level and an application or class running in the context of a partition is:
- Applications or classes running at the domain level are available across the domain and are not available in partitions.
- Applications or classes running in the context of a partition are available only within that partition.
So this is all in nutshell about Oracle Weblogic Introduction to Multitenancy. Please go through the blog to know in detail.
We cover this in one of the modules of our Oracle WebLogic Training, where we also cover Architecture, File System, JDBC, JMS, HA, Clustering, Security, Patching, Upgrade, Backup, and Recovery etc.
Did You Find this Blog useful?
Leave a Comment.
- [Video] Oracle Weblogic Server: Weblogic Admin Tasks & Tools. Click Here
- Troubleshooting Oracle Weblogic Server: Startup Issue: OutOfMemoryError PermGen Space.. CLick Here
- [Video] Oracle WebLogic Administration: Weblogic Domain Topology. Click Here
Join 3500+ Oracle Professionals like you to discuss Oracle Weblogic Server, Ask Questions or Help Others in Private Facebook Group for Oracle Weblogic Server.
Are you planning to Learn WebLogic Server or would like to check some of the common Oracle WebLogic Interview Questions then get them from here (sent over email)