This chapter describes how to deploy Oracle ADF applications packaged as an EAR file to a target application server. It also describes how to use scripts and Ant to automate the deployment process. This chapter focuses on deploying ADF applications for production and later stage testing. For information about deploying ADF applications for development, see the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.
This chapter includes the following sections:
Section 2.2, "Deploying Using Oracle Enterprise Manager Fusion Middleware Control"
Section 2.3, "Deploying Using WebLogic Scripting Tool (WLST) Commands"
Section 2.5, "Deploying Using Oracle WebLogic Server Administration Console"
Deployment is the process of packaging application files and artifacts and transferring them to a target application server to be run. During application development using JDeveloper, developers can test the application using the Integrated WebLogic Server that is built into the JDeveloper installation, or they can use JDeveloper to directly deploy to a standalone WebLogic Server.
After the application has been developed, administrators can deploy the application to production WebLogic Servers. The tools that the administrators use for production-level deployment are:
Oracle Enterprise Manager Fusion Middleware Control
WebLogic Scripting Tool (WLST) commands
Command scripts and Ant scripts
Oracle WebLogic Administration Console
This chapter describes the tools and methods that administrators use to deploy ADF applications. For information about deploying ADF applications for development and testing purposes using JDeveloper, see the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.
If your application uses customization, you may need to set up the MDS repository in Oracle WebLogic Server. For more information about MDS, see the Oracle Fusion Middleware Administrator's Guide.
Note:
Developers, Test, and QA personnel may also use these tools and the methods in this chapter to deploy ADF applications to staging WebLogic Servers.You can use Oracle Enterprise Manager Fusion Middleware Control to deploy the EAR file created in JDeveloper. Fusion Middleware Control is a Web browser-based, graphical user interface that you can use to monitor and administer a farm. For more information about deploying using Fusion Middleware Control, see the Oracle Fusion Middleware Administrator's Guide.
Applications or modules can be deployed from JDeveloper without starting the JDeveloper IDE. You can run WLST commands from the command line or sequence them in scripts to run as a batch.
Before deploying from the command line, there must be deployment profiles for the application (EAR) or project (JAR or WAR). JDeveloper creates these deployment profiles automatically for certain types of applications, but before using WLST commands for deployment, it is important to verify that the deployment profile(s) exist. To verify that the profiles exist, choose the Deployment node from either the Application Properties or Project Properties dialogs in JDeveloper. For more information about deployment profiles, see the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.
JDeveloper can also be used to deploy an application's EAR, WAR, or JAR files. The same WLST scripts that are used for deployment via a command line are also used to deploy via JDeveloper, but JDeveloper creates the WLST syntax and provides a user interface for the deployment.
There are specific WLST commands for working with ADF applications. For a list of these commands, see Chapter 4, "WLST Command Reference for ADF Applications."
For more information about using WLST scripts, see the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.
You can deploy the application using commands and scripts. You create a script to deploy the application using the ojdeploy command and use the ojaudit command to audit projects, workspaces, or source files of the application. You can also set up the script to run automatically, for instance, whenever a developer checks in new changes.
ojdeploy scripts and Ant scripts can be used together or separately:
Create an ojdeploy script to compile, package, and deploy the application.
Create an ojdeploy script to compile and package the application. Then use an Ant script (such as WLDeploy) to deploy the application.
Create an Ant script to compile, package, and deploy the application. The Ant does not need to use ojdeploy.
For more information about the ojdeploy and ojaudit commands, see the JDeveloper online help.
You can deploy to most application servers from JDeveloper, or use tools provided by the application server vendor. You may also use Ant to package and deploy applications. The build.xml file, which contains the deployment commands for Ant, may vary depending on the target application server.
For deployment to other application servers, see the application server's documentation. If your application server does not provide specific Ant tasks, you may be able to use generic Ant tasks. For example, the generic ear task creates an EAR file for you.
For information about Ant, see http://ant.apache.org.
You can use the Oracle WebLogic Server Administration Console to deploy the EAR file created in JDeveloper. For more information, see Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.