Using an Existing Deployment Plan to Configure an Application
4.5 Using an Existing Deployment Plan to Configure an Application
Applications that you receive for deployment may come with varying levels of configuration information. If you have an existing deployment plan for an application, simply prepare the application as described in Section 4.3.1, Preparing the Deployment Files and place the deployment plan in the plan subdirectory of the application root. Then install the application using the instructions in Section 4.3.2, Installing the Application Archive . The Administration Console automatically uses a deployment plan named plan.xml in the \plan subdirectory of an application root directory if one is available. If multiple plans are available for your application, they are placed in their own \plan subdirectories for example \plan1 and \plan2, and the Administration Console cannot identify them. Therefore, the config.xml must specify the plan you want to use. For information on config.xml, see Domain Configuration Files in Understanding Domain Configuration for Oracle WebLogic Server. After you install a new application and existing deployment plan, the Administration Console validates the deployment plan configuration against the target servers and clusters that were selected during installation. If the deployment plan contains empty null variables, or if any values configured in the deployment plan are not valid for the target server instances, you must override the deployment plan before you can deploy the application. You can also configure tuning parameters to better suit the target environment in which you are deploying the application, as described in Section 4.3.2.1, Saving Configuration Changes to a Deployment Plan . Changes you make to the applications configuration are saved to a new deployment plan. If you have a valid deployment plan that fully configures an application for the environment in which you are deploying, you can use either the Administration Console or the weblogic.Deployer utility to deploy an application with a deployment plan to use for deployment.4.6 Generic File Loading Overrides
Parts
» Oracle Fusion Middleware Online Documentation Library
» Document Scope and Audience Guide to This Document
» Standards Compatibility Deployment Terminology
» Related Documentation New and Changed Features in This Release
» Overview of the Deployment Process Java EE 5 Deployment Implementation
» Enterprise Application Web Application Enterprise JavaBean Resource Adapter
» Web Service J2EE Library Optional Package
» JDBC, JMS, and WLDF Modules Client Application Archive
» weblogic.Deployer Administration Console WLST Deployment Tools for Developers
» Understanding Default Deployment Names Understanding Application Naming Requirements
» Steps for Creating an Application Installation Directory
» How FastSwap Deployment Works Supported FastSwap Application Configurations
» Enabling FastSwap In Your Application Application Types and Changes Supported with FastSwap
» Limitations When Using FastSwap
» Understanding Deployment Version Strings Best Practices for Preparing Deployment Files
» Deployment Configuration Life Cycle
» Understanding Application Deployment Descriptors Understanding WebLogic Server Deployment Plans
» Benefits of a Single Deployment Plan Workflow Single Deployment Plan Ownership and Limitations
» Benefits of a Multiple Deployment Plan Workflow Multiple Deployment Plan Ownership and Limitations
» Understanding Deployment Plan Contents
» Using an Existing Deployment Plan to Configure an Application
» How It Works Directory Structure
» Additional Configuration Tasks Best Practices for Managing Application Configuration
» Goals for Exporting a Deployment Configuration Tools for Exporting a Deployment Configuration
» Understanding Deployment Property Classifications
» Steps for Exporting an Applications Deployment Configuration Staging Application Files for Export
» Generating a Template Deployment Plan using weblogic.PlanGenerator
» Overview of Common Deployment Scenarios
» Deploying to a Single-Server Domain Deploying an Application with a Deployment Plan
» Understanding Deployment Targets Deploying to One or More Targets
» Deploying to a Cluster Target Enforcing Consistent Deployment to All Configured Cluster Members
» Module-Targeting Syntax Targeting Web Application Modules
» Staging Mode Descriptions and Best Practices
» Using Nostage Mode Deployment Syntax for Nostage Mode Using Stage Mode Deployment
» Syntax for Stage Mode Using External_stage Mode Deployment Syntax for external_stage Mode
» Understanding Deployment Behavior for Shared Libraries
» Registering Libraries with WebLogic Server Specifying Library Versions at Deployment
» Production Redeployment Overview of Redeployment Strategies
» Limitations of Auto-Deployment Understanding When to Use Different Redeployment Strategies
» How Production Redeployment Works
» Development Requirements Requirements and Restrictions for Production Redeployment
» Steps for Distributing a New Version of an Application Making an Application Available to Clients
» Redeploying Applications and Modules In-Place
» Stopping an Application to Restrict Client Access
» Undeploying an Application or Module
Show more