Before you deploy Oracle Fusion Middleware applications, such as Java EE applications, you should understand the deployment process, such as designing and developing applications and deploying those applications to Managed Servers.
This chapter describes the following sections:
A user in the role of deployer is responsible for deploying applications, such as Java EE applications, and ADF applications, to WebLogic Server instances or clusters.
A user who is functioning as a deployer should be granted the Oracle WebLogic Server deployer security role. The deployer security role allows deployment operations, as well as viewing the server configuration and changing startup and shutdown classes. To grant this role to a user, use the Oracle WebLogic Server Administration Console. See "Managing Security Roles" in the Oracle WebLogic Server Administration Console Help for more information.
This section describes the general procedures involved in moving from application design and development to deployment in a production environment. It contains the following topics:
In many cases, developers use Oracle JDeveloper to create their applications. Oracle JDeveloper is an integrated development environment (IDE) for building service-oriented applications using the latest industry standards for Java, XML, Web services, portlets, and SQL. JDeveloper supports the complete software development life cycle, with integrated features for modeling, coding, debugging, testing, profiling, tuning, and deploying applications.
In this environment, you use the integrated Oracle WebLogic Server, which is packaged with Oracle JDeveloper for testing your applications.
For information about developing your applications, see:
After you have designed and tested your application with the integrated Oracle WebLogic Server, you can deploy the application to a Managed Server instance. For example, you may have installed Oracle WebLogic Server and configured a domain, including a Managed Server, in your production environment and you want to deploy the application to that Managed Server.
The following books provide specific information about deploying the different types of applications:
For Java EE applications, see Deploying Applications to Oracle WebLogic Server
For Oracle ADF, see Administering Oracle ADF Applications
This section provides an outline of the major steps involved when you migrate your application from the integrated Oracle WebLogic Server to an environment separate from the development environment. Those general steps are:
Package the application:
For Java EE applications, you package the application in an EAR file. See "Preparing Applications and Modules for Deployment" in Deploying Applications to Oracle WebLogic Server
For Oracle ADF, you package the application in an EAR file. See "What You May Need to Know About EAR Files and Packaging" in Developing Fusion Web Applications with Oracle Application Development Framework
Set up your environment. This includes:
Installing and configuring a domain and a Managed Server that is configured with the correct domain template. The appropriate domain template is applied when you create the domain using the Configuration Wizard.
For more information about installing and configuring for specific components, see:
For Oracle ADF: "How to Install the ADF Runtime to the WebLogic Installation" in Administering Oracle ADF Applications
Creating any necessary schemas in an existing database. See Creating Schemas with the Repository Creation Utility.
Registering the MDS Repository with the Oracle WebLogic Server domain, if your application uses the MDS Repository. For example, some ADF applications involve customizations using MDS. See Section 188.8.131.52.1 for information about registering the MDS Repository.
If your application uses a database, set up the JDBC data sources.
For more information about setting up the JDBC data sources, see:
For pure Java EE applications: Administering JDBC Data Sources for Oracle WebLogic Server
For Oracle ADF: "How to Create a JDBC Data Source for Oracle WebLogic Server" in Administering Oracle ADF Applications
Create a connection to the target Managed Server.
From Oracle JDeveloper, you can deploy your applications to Managed Server instances that reside outside JDeveloper. To do this, you must first create a connection to the server instance to which you want to deploy your application.
For more information, see:
For Oracle ADF: "How to Create a Connection to the Target Application Server" in Developing Fusion Web Applications with Oracle Application Development Framework
Create a configuration plan or deployment plan, which contains information about environment-specific values, such as JDBC connection strings or host names of various servers. For more information, see:
For pure Java EE applications: "Creating a New Deployment Plan to Configure an Application" in Deploying Applications to Oracle WebLogic Server
Migrate application security, such as credentials, identities, and policies. For more information, see:
Create a deployment profile. A deployment profile packages or archives a custom ADF and associated files so that the application can be deployed to an Oracle WebLogic Server Managed Server instance. Deployment profiles are created at the project and application level.
For more information, see:
For Oracle ADF: "How to Create Deployment Profiles" in Developing Fusion Web Applications with Oracle Application Development Framework
Deploy the application to a Managed Server.
For more information, see:
For pure Java EE applications: "Exporting an Application for Deployment to New Environments" in Deploying Applications to Oracle WebLogic Server
For Oracle ADF: "Deploying the Application" in Developing Fusion Web Applications with Oracle Application Development Framework
You can automate the migration of an application by using WLST or ant scripts. This makes it easier to deploy your application to multiple environments or Managed Servers and to deploy updated versions of the application.
For more information about using scripts to migrate an application to other environments, see:
The following describes some of the typical problems that you may encounter when you deploy an application to a Managed Server: