A traditional WebLogic Server domain may contain many types of deployable resources: Java EE applications, JMS servers and queues, data sources, and such. In this traditional model, if an application suite contains multiple Java EE applications and various resources that support those applications, the administrator defines these resources and deploys these applications individually rather than as a coherent unit.
Oracle WebLogic Server Multitenant (MT) introduces resource groups, simply as a convenient way to group together Java EE applications and the resources they use into a distinct administrative unit within the domain. The resources and applications are "fully qualified" in that the administrator provides all the information needed to start or connect to those resources, including credentials for connecting to a data source and targeting information for Java EE applications. A resource group will either contain these deployable resources directly or refer to a resource group template which contains the resources. Resource groups can be defined at the domain level, or be specific to a domain partition.
All the resources in or referenced by a resource group are targeted together to the same target. That is, you define the targets at the resource group level, not at the individual resource level. Resource groups can be started and stopped.
For more information on WebLogic Server resource groups, see Using WebLogic Server MT.
Note:
If you are logged into a domain partition, navigate from the Domain Partition menu.
This chapter includes the following sections:
To create a new resource group:
If you did not create the resource group from a resource group template, the initial resource group configuration is a basic shell and you must configure it before you can use it.
You perform most of the configuration required for a partition when you configure the resource group or resource group overrides. The tasks include configuring JDBC system data sources, JMS servers and resources, foreign JNDI providers, and so forth.
These tasks are described in Configure resource groups and WebLogic Server Resource Overrides, respectively.
To create a new resource group from an existing partition:
If you did not create the resource group from a resource group template, the initial resource group configuration is a basic shell and you must configure it before you can use it.
You perform most of the configuration required for a partition when you configure the resource group or resource group overrides. The tasks include configuring JDBC system data sources, JMS servers and resources, foreign JNDI providers, and so forth.
These tasks are described in Configure resource groups and WebLogic Server Resource Overrides, respectively.
This section describes how to configure resource groups.
This section includes the following tasks:
To view and define general resource group settings:
For more information about these fields, see Configuration Options.
To view and define resource group deployment settings:
For more information about these fields, see Configuration Options.
Deploying an application makes its physical file or directory known to WebLogic Server.
To deploy an application to a 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 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.
To undeploy an application from a partition resource group:
This section describes how to configure resource group services settings. The following topics are described:
To view configuration settings for the JDBC system resources that have been created in this resource group:
This section describes how to configure resource group JMS settings.
This section includes the following tasks:
To view configuration settings for the JMS servers that have been created for this resource group:
To view configuration settings for the store-and-forward (SAF) agents that have been created for this resource group:
To configure the JMS bridge destination settings for a resource group:
To view configuration settings for the mail sessions that have been created in this resource group:
To view configuration settings for the persistent stores that have been created in this resource group:
To view configuration settings for the foreign JNDI providers that have been created in this resource group:
This section describes how to control resource groups. The following topics are described:
To view and define general resource group control settings:
For more information about these fields, see Configuration Options.
When you migrate a resource group, you change the virtual target used by the resource group from one physical target (cluster/server) to another. After migration, the virtual target will point to the new physical target (cluster/server).
Note that this change affects any partition-level or domain-level resource group that uses this virtual target.
To migrate a resource group:
To view and define resource group control JDBC settings:
For more information about these fields, see Configuration Options.
This section describes how to configure resource group control messaging settings.
This section includes the following tasks:
To view configuration settings for the JMS servers that have been created for this resource group:
To view configuration settings for the store-and-forward (SAF) agents that have been created for this resource group:
This section includes the following tasks:
To monitor all of the resource groups configured in a domain:
To monitor all applications deployed to a resource group template:
To control application deployments for this resource group, see Control application deployments.
For more information about these fields, see Configuration Options.
Optionally, select View to access the following table options:
Columns: add or remove the columns displayed in the table
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
To view configuration settings for the JDBC system resources that have been created in this resource group:
This section describes how to monitor resource group JMS settings.
This section includes the following tasks:
To view configuration settings for the JMS servers that have been created for this resource group:
To view configuration settings for the store-and-forward (SAF) agents that have been created for this resource group:
To view configuration settings for the mail sessions that have been created in this resource group:
To view configuration settings for the persistent stores that have been created in this resource group:
To view configuration settings for the foreign JNDI providers that have been created in this resource group: