2 Configuring Oracle WebLogic Server Multitenant

Configuring and managing Oracle WebLogic Server Multitenant (MT) may involve several Oracle Fusion Middleware tools and products, including Oracle Fusion Middleware Control, Oracle WebLogic Scripting Tool (WLST), Oracle Coherence, and Oracle Traffic Director.

The following information describes a high-level view of managing and configuring Oracle WebLogic Server Multitenant (MT):

How to Manage WebLogic Server MT

You can use your choice of the following tools to manage WebLogic Server MT: Oracle Enterprise Manager Fusion Middleware Control (FMWC), which is the preferred graphical user interface, Oracle WebLogic Server Administration Console, WebLogic Scripting Tool, and Representational State Transfer (REST) APIs.

For each task, this chapter presents:

The main steps for accomplishing a given task, with a link to the related Fusion Middleware Control online help topic
A WLST example

In some instances, there is a difference in how a feature is presented by Fusion Middleware Control and the WebLogic Server Administration Console. This chapter identifies those instances, and includes a link to the WebLogic Server Administration Console online help where appropriate.

Configuring WebLogic Server MT

Configuring a WebLogic Server MT environment encompasses several main steps, including installing WebLogic Server MT and, optionally, Oracle Traffic Director, creating domains, virtual targets, and domain partitions, configuring resource groups, deploying applications, and more.

This high-level view of WebLogic Server MT shows the relationship of domain partitions, Oracle Traffic Director, a WebLogic Server domain, and Oracle Coherence. Consider the graphic shown in Figure 2-1.

Figure 2-1 WebLogic Server MT High-Level View

Description of "Figure 2-1 WebLogic Server MT High-Level View"

To configure WebLogic Server MT:

Install WebLogic Server for MT, as described in Installing Oracle WebLogic Server and Oracle Coherence for WebLogic Server MT in Installing and Configuring Oracle WebLogic Server and Coherence.

Note:

If you plan to use Oracle Traffic Director to manage traffic to applications running in partitions, then you must install WebLogic Server in the same path on any remote host where Managed Servers will run. New lifecycle management facilities require access to plug-in Java Archive (JAR) files that must be available at the same relative path as installed on the Administration Server host.
To use Oracle Traffic Director to manage traffic to your partitions, install it in collocated mode as described in Oracle Traffic Director Installation Guide.

You can install Oracle Traffic Director and WebLogic Server in different Oracle_Home locations on different systems (as shown in Figure 2-1), or in the same Oracle_Home location on a single system.
To use Oracle Traffic Director to manage traffic to your partitions, use the Configuration Wizard to create an Oracle Traffic Director domain, as described in Creating the Domain for Oracle Traffic Director.

Use the Oracle Traffic Director - Restricted JRF template to create the domain. This template automatically includes several other necessary templates.
Create a new domain, as described in Creating a WebLogic Server domain in Creating WebLogic Domains Using the Configuration Wizard.

Use the Oracle Enterprise Manager - Restricted JRF template to create the domain, as described in Installing Oracle WebLogic Server and Coherence for WebLogic Server Multitenant in Installing and Configuring Oracle WebLogic Server and Coherence. This template automatically includes several other necessary templates.
To use the WebLogic Server lifecycle manager (LCM) to coordinate partition configuration changes with Oracle Traffic Director, use WLST to enable the LCM on the WebLogic Server domain:
```
edit()
startEdit()
cd("/")
lcmConfig=cmo.getLifecycleManagerConfig();
lcmConfig.setDeploymentType("admin")
lcmConfig.setOutOfBandEnabled(true)
```
Create any clusters and Managed Servers that you want to use for domain partitions.

If you use Fusion Middleware Control or the WebLogic Server Administration Console, then there is nothing partition-specific when creating a cluster. See Setting up WebLogic Clusters in Administering Clusters for Oracle WebLogic Server.

However, if you use WLST to create Managed Servers (configured or dynamic), then the required Oracle Java Required Files (JRF) template is not applied. Fusion Middleware Control requires the JRF template to enable domain monitoring.

Therefore, for the WLST use case:
1. Use WLST to create the cluster or Managed Server.
2. Use the applyJRF command to apply the JRF template to the Managed Servers. See WLST Command Reference for Infrastructure Components.
Create one or more virtual targets, as described in Configuring Virtual Targets.
Create and configure a resource group template, as described in Configuring Resource Group Templates.
Optionally, deploy applications to the resource group template, as described in Deploying Applications. Your applications might require partition-specific database connections.
Create a new security realm as described in Configuring Security.
To use Oracle Traffic Director to manage traffic to your partitions, use Fusion Middleware Control to create an Oracle Traffic Director instance, as described in Creating an Oracle Traffic Director MT Configuration and Instance.
Create domain partitions, as described in Configuring Domain Partitions.
Override resources such as Java Database Connectivity (JDBC) connections, as described in Configuring Resource Overrides.
Optionally, configure Oracle Coherence, as described in Configuring Oracle Coherence.
Optionally, configure resource managers, as described in Configuring Resource Consumption Management.
Monitor your domain partitions, as described in Monitoring and Debugging Partitions.