Developer Partner Community

  • May 1, 2016

WebLogic 12.2.1 Multi-Tenant by Raul Castillo

Juergen Kress
PaaS Partner Adoption

clip_image002As a weblogic administrator the interaction among the application server and the database is often strong. In fact, according to Confio Software (2013) approximately 70% of applications’ performance problems are caused by the dataWith the development of partitions on Weblogic, Oracle has developed an infrastructure that is similar to containers and that takes advantage of the Weblogic server’s capacities such as clustering, transaction management and security [1].

These are the advantages of using Weblogic Server Multitenant [1]:

Time to market is improved.

  1. The complexity of moving workload to the cloud and from the cloud is reduced.
  2. It is possible to convert monolithic applications to smaller services.
  3. It allows up to 3x hardware consolidation.
  4. Reduction of OPEX by up to 25%

Since Weblogic Multitenant is based on the concept of partitions or micro containers. It is important to remark that these partitions allow the portability of applications reducing the time to market and allowing the movement to the cloud or vice versa.

Multi-tenant allows group applications that are scattered through several domains, which helps to optimize the use of hardware, making possible the reduction of OPEX.

In addition, a partition does not have any Operating System or JVM component. Applications and configuration artefacts compose partitions or micro containers and each one of these micro containers could use a managed server or a cluster.

In the following diagram, the topology shows two partitions deployed on the same cluster, which allow them sharing the JVMs that are part of that cluster.

With this in mind, in this post, I will show you how to reach the topology described based on partitions. I have created a domain with a cluster and I have an Oracle Pluggable Database available so now these are the additional elements created in this post:

1. Virtual targets. According to [2] a virtual target is the target used by a resource group at the domain level and partition level. Virtual targets are targeted to managed servers or clusters and they define access points to resources. Virtual targets give a separate HTTP per each server as in the case of virtual hosts in Weblogic Server [2]. Since virtual targets set the access to resources and resources are group by resource groups, these require one or more virtual targets. When a resource group has a global scope (related to the domain) it is possible to select any virtual target that is not assigned to a partition. On the other hand, when a resource group is assigned to a partition, this can use only available virtual targets in the partition [2]. Read the complete article here.

WebLogic Partner Community

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.

Blog Twitter LinkedIn Forum Wiki

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.