Understanding WebLogic Server Deployment 2-7
the enclosing application an application-scoped resource. Using application-scoped resources ensures that an application always has access to required resources, and
simplifies the process of deploying the application into new environments.
In contrast to system modules, application modules are owned by the developer who created and packaged the module, rather than the Administrator who deploys the
module. This means that the Administrator has more limited control over JDBC, JMS, and WLDF application modules. When deploying an application module, an
Administrator can change resource properties that were specified in the module, but cannot add or delete resources.
System modules are created by the Administrator via the WebLogic Administration Console, and can be changed or deleted as necessary by the Administrator. Similarly,
standalone application modules created by the Administrator can be used to recreate global resources in multiple WebLogic Server environments simply by deploying the
modules into new domains.
For more information on how to deploy and use JDBC, JMS, and WLDF modules, see:
■
Section 6.8, Deploying JDBC, JMS, and WLDF Application Modules
■
Configuring and Managing JMS for Oracle WebLogic Server
■
Configuring and Managing JDBC for Oracle WebLogic Server
■
Configuring and Using the Diagnostics Framework for Oracle WebLogic Server
2.4.9 Client Application Archive
The J2EE specification enables you to include a client application archive file within an Enterprise application. A J2EE client application module contains the Java classes that
execute in the client JVM Java Virtual Machine and deployment descriptors that describe EJBs Enterprise JavaBeans and other WebLogic Server resources used by the
client. This enables both the server-side and client-side components to be distributed as a single unit. You define client modules in an EAR using the J2EE standard
application-client.xml deployment descriptor and WebLogic Server weblogic-appclient.xml descriptor.
2.5 Deployment Tools
WebLogic Server provides the following tools to help you configure and deploy applications:
■
Section 2.5.1, weblogic.Deployer
■
Section 2.5.2, Administration Console
■
Section 2.5.3, WLST
■
Section 2.5.4, Deployment Tools for Developers
2.5.1 weblogic.Deployer
weblogic.Deployer provides a command-line based interface for performing both basic and advanced deployment tasks. Use weblogic.Deployer when you want
command-line access to WebLogic Server deployment functionality, or when you need to perform a deployment task that is not supported using the Administration Console.
2-8 Deploying Applications to Oracle WebLogic Server
2.5.2 Administration Console
The Administration Console provides a series of Web-based Deployment Assistants that guide you through the deployment process. The Administration Console also
provides controls for changing and monitoring the deployment status, and changing selected deployment descriptor values while the deployment unit is up and running.
Use the Administration Console when you need to perform basic deployment functions interactively and you have access to a supported browser.
2.5.3 WLST
The WebLogic Scripting Tool WLST is a command-line interface that you can use to automate domain configuration tasks, including application deployment configuration
and deployment operations. See Oracle WebLogic Scripting Tool for more information.
2.5.4 Deployment Tools for Developers
WebLogic Server provides several tools for deploying applications and standalone modules:
■
wldeploy is an Ant task version of the weblogic.Deployer utility. You can automate deployment tasks by placing wldeploy commands in an Ant
build.xml file and running Ant to execute the commands.
■
weblogic-maven-plugin is a Maven plug-in for WebLogic Server that you can use to perform deployment operations similar to those supported by
weblogic.Deployer. The plug-in lets you deploy, redeploy, update, and such, applications built using Maven to WebLogic Server from within the Maven
environment.
■
weblogic.PlanGenerator is a command-line tools that enables developers to export an applications configuration for deployment to multiple WebLogic Server
environments.
■
The deployment API allows you to perform deployment tasks programmatically using Java classes.
■
The autodeploy domain directory allows you to deploy an application quickly for evaluation or testing in a development environment.
3
Preparing Applications and Modules for Deployment 3-1
3
Preparing Applications and Modules for Deployment
The following sections provides information on key topics required to prepare applications for deployment:
■
Section 3.1, Packaging Files for Deployment
