1-2 Deploying Applications to Oracle WebLogic Server
■
Chapter 5, Exporting an Application for Deployment to New Environments, describes how to export an applications WebLogic Server deployment
configuration to a custom deployment plan, which administrators use in deploying the application into non-development environments.
■
Chapter 6, Deploying Applications and Modules with weblogic.Deployer, describes basic and advanced techniques for deploying applications to WebLogic
Server.
■
Chapter 7, Auto-Deploying Applications in Development Domains, describes
how to quickly deploy an application to a standalone server Administration Server for evaluation or testing in a single-server development environment.
■
Chapter 8, Redeploying Applications in a Production Environment, explains
how to safely update, redeploy, and reconfigure applications that you have deployed to a production environment.
■
Chapter 9, Managing Deployed Applications, describes common tasks that an
Administrator performs when managing deployed applications and modules.
■
Appendix A, weblogic.Deployer Command-Line Reference, provides a complete
reference for the weblogic.Deployer tool syntax.
■
Appendix B, weblogic.PlanGenerator Command-Line Reference, describes how
to use the weblogic.PlanGenerator utility to create a basic deployment plan.
1.3 Standards Compatibility
WebLogic Server implements the Java EE 5 specification. Java EE 5 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.
WebLogic Server implements both the JSR-88 Service Provider Interface SPI plug-in and model plug-in to comply with the Java EE 5 deployment specification. You can use
a basic Java EE 5 deployment API deployment tool with the WebLogic Server plug-ins without using WebLogic Server extensions to the API to configure, deploy, and
redeploy J2EE applications and modules to WebLogic Server. See Compatibility Statement for WebLogic Server.
1.4 Deployment Terminology
The following WebLogic Server deployment terms are used throughout this document:
■
application—One or more software programs, used collectively by an end user to perform computing tasks.
■
application installation directory—A WebLogic Server directory structure designed to help organize deployment files and generated deployment configuration artifacts
for an application or module. Also referred to as an application root directory.
■
application module—An XML document used to configure JMS or JDBC resources. An application module can be one of the following types:
–
standalone— Resources are bound to the global JNDI tree.
–
application-scoped—Bundled as part of an Enterprise application and scoped within the application itself.
Introduction and Roadmap 1-3
■
application version—A string value that identifies the version of a deployed application. Compatible applications that use version strings can use the
WebLogic Server production redeployment strategy.
■
deployment configuration—The process of defining the deployment descriptor values required to deploy an application to a particular WebLogic Server domain.
The deployment configuration for an application or module is stored in three types of XML document: J2EE deployment descriptors, WebLogic Server
descriptors, and WebLogic Server deployment plans.
■
deployment descriptor—An XML document used to define the J2EE behavior or WebLogic Server configuration of an application or module at deployment time.
■
deployment plan—An XML document used to define an applications WebLogic Server deployment configuration for a specific WebLogic Server environment,
such as development, test, or production. A deployment plan resides outside of an applications archive file and contains deployment properties which override an
applications existing WebLogic Server deployment descriptors. Use deployment plans to easily change an applications WebLogic Server configuration for a
specific environment without modifying existing deployment descriptors. Multiple deployment plans can be used to reconfigure a single application for deployment
to multiple, differing WebLogic Server environments.
■
distribution—The process by which WebLogic Server copies deployment source files to target servers for deployment.
■
production redeployment—A WebLogic Server redeployment strategy that deploys a new version of a production application alongside an older version, while
automatically managing HTTP connections to ensure uninterrupted client access.
■
staging mode—The method WebLogic Server uses to make deployment files available to target servers in a domain. Staging modes determine whether or not
files are distributed copied to target servers before deployment.
1.5 Related Documentation
