WebLogic Server implements the Java Platform, Enterprise Edition (Java EE) 7 specification. Java EE 7 includes a deployment specification, JSR-88, that describes a standard API used by deployment tools and application server providers to configure and deploy applications to an application server. For more information about application deployment, see Deploying Applications to Oracle WebLogic Server.
Note:
If you are logged into a domain partition, navigate from the Domain Partition menu.
This chapter includes the following sections:
When deploying an application, you select the scope in which you want to deploy that application: global (domain), a resource group template, or a resource group at the domain or partition level.
If an application is deployed to the domain, then you can target the application to the WebLogic Server instances and clusters within the domain.
The deployment menu options change depending on the scope and target of your application. The following deployment menus are available:
Domain Application Deployment
Application Deployment
Clustered Application Deployment
Domain Partition Application Deployment
To monitor all applications and modules deployed on this domain:
You can deploy applications and libraries to the domain, as well as redeploy or undeploy existing applications. You can also start and stop applications, override application configuration, and fetch deployment plans.
This section includes the following tasks:
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.
To deploy an application:
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:
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.
Note:
If you undeploy an application or module from a resource group template that is referenced by multiple resource groups, then the application or module is also removed from all referencing resource groups.
To undeploy an application:
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 start an application:
Stopping a running application makes it unavailable to WebLogic Server clients.
To stop an application:
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:
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:
Java EE enterprise applications, Web application modules, EJBs, and RMI applications can specify named Work Managers to use to manage their work requests.
To create an application-scoped Work Manager and associate them with your applications or with particular application components:
This section includes the following tasks:
To monitor a specific Coherence Grid Archive (GAR) module:
An EJB can be installed as a JAR
archive, as an exploded JAR
directory, or in a WAR
archive.
This section includes the following tasks:
This section includes the following tasks:
To configure general settings for a specific EJB application:
To view the persistence units defined for an EJB application:
This section includes the following tasks:
WebLogic Server includes the ability to configure the EJB container so that it automatically retries container managed transactions that have rolled back. On a per method basis, the EJB container can be instructed to retry a failed method up to a specified number of times using a new transaction if that method was originator of the transaction that rolled back.
To configure the retry count for a specific EJB module:
An enterprise application consists of one or more Web application modules, EJB modules, Web services, and resource adapters. It might also include a client application. An enterprise application is defined by an application.xml file, which is the standard Java EE deployment descriptor for enterprise applications. If the application includes WebLogic Server-specific extensions, then the application is further defined by a weblogic-application.xml
file. Enterprise applications that include a client module will also have a client-application.xml deployment descriptor and a WebLogic runtime client application deployment descriptor.
For both production and development purposes, Oracle recommends that you package and deploy even standalone Web applications, EJBs, Web services, and resource adapters as part of an enterprise application.
This section includes the following tasks:
For enterprise applications, Web applications, and Coherence archives, you can manually clear the caches and pools of idle beans in application-level caches.
To initialize caches in a specific application:
This section includes the following tasks:
To configure general settings for a specific enterprise application:
To view the persistence units defined for an enterprise application:
To specify a Work Manager to manage work requests for a specific enterprise application:
To configure instrumentation for a specific enterprise application:
To configure tags for a specific enterprise application:
To target a specific enterprise application deployed to the global scope:
This section includes the following tasks:
For standalone JDBC modules, you can manually control each instance of a JDBC data source.
To control JDBC data source instances:
This section includes the following tasks:
To configure general settings for a specific standalone JDBC module:
The connection pool within a JDBC data source contains a group of JDBC connections that applications reserve, use, and then return to the pool. The connection pool and the connections within it are created when the connection pool is registered, usually when starting WebLogic Server or when deploying the data source to a new target.
To configure the connection pool properties for a specific standalone JDBC module:
Before you begin
Additional configuration may be required to support Oracle parameters.
See Using GridLink Data Sources in Administering JDBC Data Sources for Oracle WebLogic Server.
To configure Oracle parameters for a standalone JDBC module:
Before you begin
Additional configuration may be required to support ONS client parameters.
See Using GridLink Data Sources in Administering JDBC Data Sources for Oracle WebLogic Server.
To configure ONS client parameters for a standalone JDBC module:
The transaction protocol for a JDBC data source determines how connections from the data source are handled during transaction processing.
See JDBC Data Source Transaction Options in Administering JDBC Data Sources for Oracle WebLogic Server.
Note:
If the data source uses an XA JDBC driver to create database connections, then connections from the data source will support the two-phase commit transaction protocol only. No other transaction options are available for data sources that use an XA JDBC driver.
To configure transaction options for a standalone JDBC module:
To select the security identity option used for a standalone JDBC module:
To target a specific standalone JDBC module deployed to the global scope:
To configure tags for a specific standalone JDBC module:
This section includes the following tasks:
To configure general settings for a specific JDBC module:
The connection pool within a JDBC data source contains a group of JDBC connections that applications reserve, use, and then return to the pool. The connection pool and the connections within it are created when the connection pool is registered, usually when starting WebLogic Server or when deploying the data source to a new target.
To configure the connection pool properties for a specific JDBC module:
The transaction protocol for a JDBC data source determines how connections from the data source are handled during transaction processing.
See JDBC Data Source Transaction Options in Administering JDBC Data Sources for Oracle WebLogic Server.
Note:
If the data source uses an XA JDBC driver to create database connections, then connections from the data source will support the two-phase commit transaction protocol only. No other transaction options are available for data sources that use an XA JDBC driver.
To configure transaction options for a JDBC module:
To select the security identity option used for a JDBC module:
This section includes the following tasks:
This section includes the following tasks:
To configure general settings for a specific standalone JMS module:
To target a specific standalone JMS module deployed to the global scope:
Java EE libraries provide an easy way to share one or more types of Java EE modules among multiple enterprise applications.
A Java EE library is a standalone EJB or Web application module, multiple EJB or Web application modules packaged in an enterprise application (EAR
), or a single plain JAR
file that is registered with the Java EE application container upon deployment. After the library has been registered, you can deploy enterprise applications that reference the library. Each referencing application receives a reference to the required library module(s) on deployment, and can use those modules as if they were packaged as part of the referencing application itself. The shared library classes are added to the classpath of the referencing application, and the referencing application's deployment descriptors are merged (in memory) with those of the Java EE library modules.
This section includes the following tasks:
A resource adapter is a system library specific to an Enterprise Information System (EIS) and provides connectivity to an EIS. A resource adapter is analogous to a JDBC driver, which provides connectivity to a database management system. The interface between a resource adapter and the EIS is specific to the underlying EIS. The resource adapter plugs into an application server, such as WebLogic Server, and provides seamless connectivity between the EIS, application server, and enterprise application.
A resource adapter is packaged and deployed like any other application. Its initial configuration can be specified in its deployment descriptor files, ra.xml
and weblogic-ra.xml
.
This section includes the following tasks:
This section includes the following tasks:
To monitor the message listener endpoints for all active resource adapters deployed to this domain:
For Web applications, resource adapters, and Coherence archives, you can start, stop, suspend, or resume a resource adapter connected with the application.
To control a resource adapter:
For Web applications, resource adapters, and Coherence archives, you can reset or force reset outbound connection pools associated with the application.
To control outbound connection pools:
For more information about these fields, see Configuration Options.
This section includes the following tasks:
To configure general settings for a specific resource adapter:
To configure outbound connection pools for a specific resource adapter:
To view administered object groups and instances for a specific resource adapter:
To specify a Work Manager to manage work requests for a specific resource adapter:
To configure instrumentation for a specific resource adapter:
This section includes the following tasks:
To monitor a specific resource adapter module:
Optionally, select View on any of the tables to access the following table options:
Columns: add or remove the columns displayed in the table
Detach: detach the table (viewing option)
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
Query by Example
To control a specific resource adapter module:
Optionally, select View on any of the tables to access the following table options:
Columns: add or remove the columns displayed in the table
Detach: detach the table (viewing option)
Sort: sort the columns in ascending or descending order
Reorder: change the order of the columns displayed
Query by Example
To configure general settings for a specific resource adapter module:
To configure properties for a specific resource adapter module:
To configure outbound connection pools for a specific resource adapter module:
To view administered objects for a specific resource adapter module:
This section includes the following tasks:
To configure general settings for a specific outbound connection pool:
To configure properties for a specific outbound connection pool:
To configure transaction support settings for a specific outbound connection pool:
To configure authentication parameters for a specific outbound connection pool:
A Web application can be installed as WAR
archive or exploded WAR
directory.
This section includes the following tasks:
This section includes the following tasks:
To configure general settings for a specific Web application:
To view the persistence units defined for a Web application:
To specify a Work Manager to manage work requests for a specific Web application:
To configure instrumentation for a specific Web application:
You can configure and monitor Web application modules that are deployed to this domain.
This section includes the following tasks:
To configure general settings for a specific Web application module:
To view the persistence units defined for a Web application module: