23 WebLogic Server Domain Partitions
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.
For more information on WebLogic Server domain partitions, see Using WebLogic Server MT.
Note:
If you are logged into a domain partition, navigate from the Domain Partition menu. Note that WebLogic Server Multitenant domain partitions, resource groups, resource group templates, and virtual targets are deprecated in WebLogic Server 12.2.1.4.0 and will be removed in the next release.
This chapter includes the following sections:
Creating domain partitions: prerequisites
Before you can create a domain partition, you must satisfy the following prerequisites:
-
If you have not already done so, then create the domain you plan to use.
Use the Oracle Enterprise Manager - Restricted JRF template to create the domain. This template automatically includes several other necessary templates.
The best practice is to create a new domain.
If you plan to upgrade an existing domain, then you must still create a new security realm.
-
If you are using OTD for load balancing, then configure the OTD runtime configuration. See Configuring Oracle Traffic Director in Using WebLogic Server MT for the steps to follow.
-
If you have not already done so, then create one or more virtual targets. See WebLogic Server Virtual Targets for the steps to follow.
-
If you want to use a resource group template with this domain partition, then create the resource group template first. See WebLogic Server Resource Group Templates for the steps to follow.
-
If you have not already done so, then create the security realm for the domain partition. Each domain partition must have a security realm. The security realm can be unique to this domain partition, or shared by multiple domain partitions. See WebLogic Server Security for the steps to follow.
Configure domain partitions
This section describes how to configure your domain partition. This section focuses on the management tasks you perform on the domain partition itself, and not on the associated resource groups.
The following topics are described:
Configure domain partition general properties
To configure general properties for a domain partition:
For more information about these fields, see Configuration Options.
Configure domain partition virtual targets
To select virtual targets to use with this domain partition:
- From the Domain Partition menu, select Administration, then select Available Targets.
- From the Available Targets page, you can select the virtual targets that will be available to use with this domain partition. Virtual targets can be used only by one domain partition, so only available virtual targets are listed.
- Select the Set As Default control to use this domain partition with a resource group that does not explicitly set a virtual target.
- Click Save.
Configure domain partition resource groups
To view and configure the resource groups in the domain partition:
Configure load balancer configuration
You must first configure the OTD runtime configuration before you can use it with a domain partition. See Configuring Oracle Traffic Director in Using WebLogic Server MT for the steps to follow.
To configure the load balancer configuration:
- From the Domain Partition menu, select Administration, then select Load Balancing Configuration.
- Click Use OTD for Load Balancing.
- From the OTD Runtime dropdown, select the OTD runtime configuration.
- Click Save.
Configure domain partition resource overrides
To override properties for resources in this domain partition:
Configure domain partition Coherence caches
To add or delete Coherence caches in the domain partition:
Monitor domain partitions
This section includes the following tasks:
Monitor domain partition deployments
To monitor the status of all deployments in a domain partition:
Monitor domain partition JDBC data sources
To monitor the status of all JDBC data sources created in a domain partition:
Monitor domain partition Store-and-Forward agents
To monitor Store-and-Forward agents created in this domain partition:
Monitor domain partition JMS resources and modules
This section includes the following topics:
Monitor domain partition JMS resources
You can view all the resources from all the JMS system modules created in the current domain partition. You can also view monitoring information, including the resource's system module, JNDI name, targeted subdeployment resources, and the resource group on which the resource is targeted.
For certain resources, you can monitor detailed statistical information or perform control operations.
To monitor all JMS system resources in the domain partition:
Monitor domain partition messaging bridges
To monitor the messaging bridge instances that have been configured for the domain partition:
Monitor domain partition JMS bridge destinations
To monitor JMS bridge destinations created in this domain partition:
Monitor domain partition asynchronous tasks
This page allows you to monitor the completion status of all tasks. To monitor asynchronous tasks created in this domain partition:
Monitor diagnostic images
The diagnostic image functionality provided by the WebLogic Server Diagnostic Service gathers the most common sources of key server state used in diagnosing problems and packages that state into a single file, or "diagnostic image." You can specify the default destination directory where diagnostic images for a server are saved, and you can initiate an immediate capture of an image for a server.
To monitor the diagnostic images in a domain partition:
Control domain partitions
This section includes the following tasks
Start and stop domain partitions
To start and stop domain partitions:
-
From the WebLogic Domain menu, select Environment, then select Domain Partitions.
The Domain Partition table displays information about the domain partitions in this domain.
-
In the summary of domain partitions table, select the domain partition you want to control:
-
To start a partition, from the Control menu, select Start.
All of the resource groups—and all of the applications deployed to those resource groups—are started.
-
To suspend a running partition, from the Control menu, select Suspend and select whether to suspend the partition gracefully (When work completes) or forcibly (Force suspend now).
The suspend operation transitions the partition from the
RUNNING
toADMIN
state. -
To resume a suspended partition, from the Control menu, select Resume.
The resume operation transitions the partition from the
ADMIN
toRUNNING
state. -
To shut down a partition:
From the Control menu, select Stop and select whether to shut down the partition gracefully (When work completes) or forcibly (Force stop now).
Optionally, from the Control menu, select Halt. When a partition is in the
HALTED
state, all resource groups in the partition are shutdown and the partition is fully shutdown on all targets.
-
See About Partition Lifecycle States and Transitions in Using WebLogic Server MT.
Export domain partitions
Exporting a domain partition creates a partition backup and stores it in an archived format. You can easily move the archived partition from one domain to another, including the applications that are deployed to the partition.
Before you begin:
Prior to exporting a domain partition, you must first have created or imported one. See Create domain partitions and Import domain partitions.
To export a domain partition:
Import domain partitions
While importing a partition archive, you may need to update the dependencies on the domain (like targets and security realms) and also optionally update other attributes in the partition configuration to make it valid. See Exporting and Importing Partitions in Using WebLogic Server MT.
Before you begin:
Prior to importing a domain partition:
-
You must have previously exported a domain partition (the source domain) to a partition archive file. See Export domain partitions.
-
The server instance must already have a domain configured (the target domain).
To import a domain partition:
Control domain partition JDBC data sources
To control all JDBC data sources created in a domain partition:
Control domain partition Store-and-Forward agents
To control Store-and-Forward agents created in this domain partition:
Control domain partition JMS resources and modules
This section includes the following topics:
Control domain partition JMS resources
You can view all the resources from all the JMS system modules created in the current domain partition. You can also view monitoring information, including the resource's system module, JNDI name, targeted subdeployment resources, and the resource group on which the resource is targeted.
For certain resources, you can monitor detailed statistical information or perform control operations.
To control all JMS system resources in the domain partition:
Control domain partition application deployments
You can start, stop, deploy, redeploy, and undeploy applications deployed to resource groups in the domain partition. You can also fetch deployment plans and override the application configuration defined in a resource group template.
This section includes the following tasks:
Start applications in a partition
Starting an application makes it available to WebLogic Server clients. Before you can start an application, you must first deploy it. See Deploy applications to a partition resource group.
To start an application on a partition resource group:
Stop applications in a partition
Stopping a running application makes it unavailable to WebLogic Server clients.
To stop an application on a partition resource group:
Deploy applications to a partition resource group
Deploying an application makes its physical file or directory known to WebLogic Server. After you have deployed the application, you can start it so that users can begin using it. See Start applications in a partition.
To deploy an application to a partition resource group:
Redeploy applications to a partition resource group
Redeploying an application redeploys the archive file or exploded directory. Redeploy an application if you have made changes to it and want to make the changes available to WebLogic Server clients.
To redeploy an application or module to a partition resource group:
Undeploy applications from a partition resource group
Undeploying an application removes it from every target of the domain to which the application is deployed. Once you undeploy an application from the domain, you must deploy it again if you want to make it available to WebLogic Server clients. To temporarily make applications unavailable to WebLogic Server clients, you can stop them instead of undeploying them.
Before you begin
Before you can undeploy an application, you must stop it to ensure that it is not servicing client applications. See Stop applications in a partition.
To undeploy an application from a partition resource group:
Override application configuration
When a resource group references a resource group template, you can override the default application configuration for applications and modules defined to the resource group template by specifying a different deployment plan. The application or module is then redeployed using the new deployment plan for its application configuration.
To override the configuration for an application or module:
Fetch deployment plans
A deployment plan is a file that contains the deployment settings as well as post-deployment configuration changes of an application. You can fetch and save the deployment plan of an application, and then deploy or redeploy that application later using the saved deployment plan.
To fetch a deployment plan for an application:
View the JNDI tree
The JNDI browser is a central location where you can find the JNDI names of all the WebLogic Server resources. Typically, while writing WLS client programs, you would search the JNDI browser for JNDI names. The JNDI browser displays a tree of resources in the domain, a server, or a partition. Selecting a node or an object in the tree, displays JNDI information including Binding Name, Object Class, Object Hash Code, and Object to String Results entries.
To view objects in a domain partition's JNDI tree:
For more information about JNDI, see Understanding WebLogic JNDI in Developing JNDI Applications for Oracle WebLogic Server.