36 Deploying Fusion Web Applications

36.1.1 Developing Applications with Integrated WebLogic Server

If you are developing an application in JDeveloper and you want to run the application in Integrated WebLogic Server, you do not need to perform the tasks required for deploying directly to Oracle WebLogic Server or to an archive file. JDeveloper has a default connection to Integrated WebLogic Server and does not require any deployment profiles or descriptors. Integrated WebLogic Server has a preconfigured domain that includes the ADF libraries, as well as the -Djps.app.credential.overwrite.allowed=true setting, that are required to run Oracle ADF applications. You can run an application by choosing Run from the JDeveloper main menu.

You debug the application using the features described in Chapter 31, "Testing and Debugging ADF Components."

36.1.2 Developing Applications for Standalone Application Server

Typically, you test and develop your application by running it in Integrated WebLogic Server. You can then test the application further by deploying it to standalone Oracle WebLogic Server in development mode to more closely simulate the production environment.

In general, you use JDeveloper to prepare the application or project for deployment by:

• Creating a connection to the target application server

• Creating deployment profiles (if necessary)

• Creating deployment descriptors (if necessary)

• Updating application.xml and web.xml to be compatible with Oracle WebLogic Server (if required)

• Enabling the application for Real User Experience Insight (RUEI) in web.xml (if desired)

• Migrating application-level security policy data to a domain-level security policy store

• Configuring the Oracle Single Sign-On (Oracle SSO) service and properties in the domain jps-config.xml file when you intend the web application to run using Oracle SSO

You must already have an installed Oracle WebLogic Server. If you do not, you can use the Oracle 11g Installer or the Oracle Fusion Middleware 11g Application Developer Installer to install one.

You also must prepare Oracle WebLogic Server for ADF application deployment by:

• Installing the ADF runtime into the Oracle WebLogic Server installation:

  • If you installed Oracle WebLogic Server together with JDeveloper using the Oracle 11g Installer for JDeveloper, the ADF runtime should already be installed.

  • If the ADF runtime is not installed and you want to use Oracle Enterprise Manager to manage standalone ADF applications (which are applications without Oracle SOA Suite or Oracle WebCenter components), use the Oracle Fusion Middleware 11g Application Developer Installer. This installer will install the necessary Oracle Enterprise Manager components into the Oracle WebLogic installation.

  • If the ADF runtime is not installed and you do not need to install Enterprise Manager, use the Oracle 11g Installer for JDeveloper.

• Extending Oracle WebLogic Server domain to be ADF-compatible using the ADF runtime

• Setting the Oracle WebLogic Server credential store overwrite setting as required (-Djps.app.credential.overwrite.allowed=true setting)

• Creating a global JDBC data source for applications that require a connection to a data source

After the application and Oracle WebLogic Server have been prepared, you can:

• Use JDeveloper to:

  • Directly deploy to Oracle WebLogic Server using the deployment profile and the application server connection.

  • Deploy to an EAR file using the deployment profile. For Oracle ADF applications, WAR and MAR files can be deployed only as part of an EAR file.

• Use Enterprise Manager, WLST scripts, or the Oracle WebLogic Server Administration Console to deploy the EAR file created in JDeveloper. For more information, see the Oracle Fusion Middleware Administrator's Guide for Oracle Application Development Framework.

36.2.1 How to Run an Application in Integrated WebLogic Server

You can test an application by running it in Integrated WebLogic Server. You can also set breakpoints and then run the application within the ADF Declarative Debugger.

To run an application in Integrated WebLogic Server:

1. In the Application Navigator, select the project, unbounded task flow, JSF page, or file as the run target.

2. Right-click the run target and choose Run or Debug.

36.2.2 How to Deploy a MAR Deployment Profile to Integrated WebLogic Server

When an application is running in Integrated WebLogic Server, the MAR profile itself will not be deployed to a repository, but a simulated MDS repository will be configured for the application that reflects the metadata information contained in the MAR. This metadata information is simulated, and the application runs based on this location in source control.

Any customizations or documents created by the application that are not configured to be stored in other MDS repositories are written to this simulated MDS repository directory. For example, if you customize an object, the customization is written to the simulated MDS repository. If you execute code that creates a new metadata object, then this new metadata object is also written to the same location in the simulated MDS repository. You can keep the default location for this directory (ORACLE_HOME\jdeveloper\systemXX.XX\o.mds.dt\adrs\Application\AutoGeneratedMar\mds_adrs_writedir), or you can set it to a different directory. You also have the option to preserve this directory across different application runs, or to delete this directory before each application run.

If your workspace has different working sets, only the metadata from the projects defined in the working set and their dependent projects will be included in the MAR. You can view and change a project's dependencies by right-clicking the project in the Application Navigator, choosing Project Properties, and then selecting Dependencies. For instance, an application may have several projects but workingsetA is defined to be viewcontroller2 and viewcontroller5; and viewcontroller5 has a dependency on modelproject1. When you run or debug workingsetA, only the metadata for viewcontroller2, viewcontroller5, and modelproject1 will be included in the MAR for deployment.

Before you begin:

There should already be a MAR profile, either generated automatically by JDeveloper, or manually generated by a user.

To deploy the MAR profile to Integrated WebLogic Server:

1. In the Application Navigator, right-click the application and choose Application Properties.

2. In the Application Properties dialog, expand Run and choose MDS.

3. In the Run MDS page:

   • Select the MAR profile from the MAR Profile dropdown list

   • Enter a directory path in Override Location if you want to customize the location of the simulated MDS repository.

   • Select the Directory Content option. You can chose to preserve the customizations across application runs or delete customizations before each run.

   Select the MAR profile from the MAR Profile dropdown list. Figure 36-1 shows Demometadata1 selected as the MAR profile.

   Figure 36-1 Setting the Run MDS options

   
   

36.3.1 How to Create a Connection to the Target Application Server

You can deploy applications to Oracle WebLogic Server via JDeveloper application server connections. If your application involves customization using MDS, you should register your MDS repository with the Oracle WebLogic Server domain.

For more information about registering MDS, see the Oracle Fusion Middleware Administrator's Guide.

To create a connection to an application server:

1. Launch the Application Server Connection wizard.

   You can:

   • In the Application Server Navigator, right-click Application Servers and choose New Application Server Connection.

   • In the New Gallery, expand General, select Connections and then Application Server Connection, and click OK.

   • In the Resource Palette, choose New > New Connections > Application Server.

2. In the Create AppServer Connection dialog Usage page, select Standalone Server.

3. In the Name and Type page, enter a connection name.

4. In the Connection Type dropdown list, choose WebLogic to create a connection to Oracle WebLogic Server.

5. Click Next.

6. On the Authentication page, enter a user name and password for the administrative user authorized to access Oracle WebLogic Server.

7. Click Next.

8. On the Configuration page, enter a host name for Oracle WebLogic Server.

   The Oracle WebLogic host name is the name of the WebLogic Server instance containing the TCP/IP DNS where your application (.jar,.war,.ear) will be deployed.

9. In the Port field, enter a port number for the Oracle WebLogic Server instance on which your application (.jar,.war,.ear) will be deployed.

   If you don't specify a port, the port number defaults to 7001.

10. In the SSL Port field, enter an SSL port number for the Oracle WebLogic Server instance on which your application (.jar,.war,.ear) will be deployed.

    Specifying an SSL port is optional. It is required only if you want to ensure a secure connection for deployment.

    If you don't specify an SSL port, the port number defaults to 7002.

11. Select Always Use SSL to connect to the Oracle WebLogic Server instance using the SSL port.

12. Optionally enter a WebLogic Domain only if Oracle WebLogic Server is configured to distinguish nonadministrative server nodes by name.

13. Click Next.

14. On the Test page, click Test Connection to test the connection.

    JDeveloper performs several types of connections tests. The JSR-88 test must pass for the application to be deployable. If the test fails, return to the previous pages of the wizard to fix the configuration.

15. Click Finish.

36.3.2 How to Create Deployment Profiles

A deployment profile defines the way the application is packaged into the archive that will be deployed to the target environment. The deployment profile:

• Specifies the format and contents of the archive file that will be created

• Lists the source files, deployment descriptors, and other auxiliary files that will be packaged

• Describes the type and name of the archive file to be created

• Highlights dependency information, platform-specific instructions, and other information

You need a WAR deployment profile for each web view-controller project that you want to deploy in your application. If you want to package seeded customizations or place base metadata in the MDS repository, you need an application-level metadata archive (MAR) deployment profile as well. For more information about seeded customizations, see Chapter 34, "Customizing Applications with MDS." If the application has customization classes, you need a JAR file for those classes and you need to add that JAR when you create the EAR file. Finally, you need an application-level EAR deployment profile and you must select the projects you want to include from a list, such as WAR and MAR profiles and customization classes JAR files. When the application is deployed, the EAR file will include all the projects that were selected in the deployment profile.

For Oracle ADF applications, you can deploy the application only as an EAR file. The WAR and MAR files that are part of the application should be included in the EAR file when you create the deployment profile.

<?xml version="1.0" encoding="UTF-8" ?>
 <adf-settings xmlns="http://xmlns.oracle.com/adf/settings"
 xmlns:wap="http://xmlns.oracle.com/adf/share/http/config">
    <wap:adf-web-config xmlns="http://xmlns.oracle.com/adf/share/http/config">
        <web-app-root rootName="order"/>
    </wap:adf-web-config>
</adf-settings>

36.3.3 How to Create and Edit Deployment Descriptors

Deployment descriptors are server configuration files that define the configuration of an application for deployment and that are deployed with the Java EE application as needed. The deployment descriptors that a project requires depend on the technologies the project uses and on the type of the target application server. Deployment descriptors are XML files that can be created and edited as source files, but for most descriptor types, JDeveloper provides dialogs or an overview editor that you can use to view and set properties. If you cannot edit these files declaratively, JDeveloper opens the XML file in the source editor for you to edit its contents.

You can specify deployment descriptors that are specific to your target Oracle WebLogic application server.

In addition to the standard Java EE deployment descriptors (for example, application.xml and web.xml), you can also have deployment descriptors that are specific to your target application server. For example, if you are deploying to Oracle WebLogic Server, you can also have weblogic.xml, weblogic-application.xml, and weblogic-ejb-jar.xml.

Make sure that the application EAR file includes a weblogic-application.xml file that contains a reference to adf.oracle.domain, and that it includes an ADFApplicationLifecycleListener to clean up application resources between deployment and undeployment actions. Example 36-2 shows a sample weblogic-application.xml file.

<weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-application.xsd"
 xmlns="http://www.bea.com/ns/weblogic/weblogic-application">
  <listener>
    <listener-class>oracle.adf.share.weblogic.listeners.
          ADFApplicationLifecycleListener</listener-class>
  </listener>
  <listener>
    <listener-class>oracle.mds.lcm.weblogic.WLLifecycleListener</listener-class>
  </listener>
  <library-ref>
    <library-name>adf.oracle.domain</library-name>
       <implementation-version>11.1.1.1.0
       </implementation-version>
    </library-ref>
</weblogic-application>

If you are deploying web services, you may need to modify your weblogic-application.xml and web.xml files as described in Section 11.2.19, "How to Deploy Web Services to Oracle WebLogic Server."

If you want to enable the application for Real User Experience Insight (RUEI) monitoring, you must add a parameter to the web.xml file, as described in Section 36.3.3.5, "Enabling the Application for Real User Experience Insight."

During deployment, the application's security properties are written to the weblogic-application.xml file to be deployed with the application in the EAR file. For more information, see Section 30.8.2, "What Happens When You Configure Security Deployment Options."

Because Oracle WebLogic Server runs on Java EE 1.5, you may need to modify the application.xml and web.xml files to be compatible with Oracle WebLogic Server.

<context-param>
  <description>This parameter notifies ADF Faces that the 
               ExecutionContextProvider service provider is enabled.
               When enabled, this will start monitoring and aggregating
               user activity information for the client initiated
               requests. By default this param is not set or is false.
  </description>
  <param-name>
         oracle.adf.view.faces.context.ENABLE_ADF_EXECUTION_CONTEXT_PROVIDER
  </param-name>
  <param-value>true</param-value>
</context-param>

36.3.4 How to Deploy Applications with ADF Security Enabled

If you are developing an application in JDeveloper using Integrated WebLogic Server, application security deployment properties are configured by default, which means that the application and security credentials and policies will be overwritten each time you redeploy for development purposes. You can change the default behavior in the Application Properties dialog, as described in Section 30.8.1, "How to Configure, Deploy, and Run a Secure Application in JDeveloper."

In a development environment, JDeveloper will automatically migrate application-level credentials, identities, and policies to the remote WebLogic Server instance only if the server is set up to be in development mode. Integrated WebLogic Server is set up in development mode by default. You can set up a remote WebLogic Server to be in development mode during Oracle WebLogic Server domain creation using the Oracle Fusion Middleware Configuration Wizard. For more information about configuring Oracle WebLogic Server domains, see Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.

JDeveloper will not migrate application-level security credentials to WebLogic Server setup in production mode. Typically, in a production environment, administrators will use Enterprise Manager or WLST scripts to deploy an application, including its security requirements.

When you deploy an application to WebLogic Server, credentials and policies (in the cwallet.sso and jps-config.xml and jazn-data.xml files) will either overwrite or merge with the WebLogic Server's domain-level credential and policy stores, depending on whether the domain-level store is in OVERWRITE or MERGE mode. In production-mode WebLogic Server, to avoid security risks, only MERGE mode is allowed. For development-mode WebLogic Server, you can set the mode to OVERWRITE to test user names and passwords. You can set the mode by running setDomainEnv.cmd or setDomainEnv.sh with the following option added to the command (usually located in ORACLE_HOME/user_projects/domains/MyDomain/bin).

For setDomainEnv.cmd:

set EXTRA_JAVA_PROPERTIES=-Djps.app.credential.overwrite.allowed=true 
    %EXTRA_JAVA_PROPERTIES%

For setDomainEnv.sh:

EXTRA_JAVA_PROPERTIES="-Djps.app.credential.overwrite.allowed=true
     ${EXTRA_JAVA_PROPERTIES}"
export EXTRA_JAVA_PROPERTIES

If the Administration Server is already running, you must restart it for this setting to take effect.

You can check to see whether WebLogic Server is in production mode by using the Oracle WebLogic Server Administration Console or by verifying the following line in WebLogic Server's config.xml file:

<production-mode-enabled>true</production-mode-enabled>

By default, JDeveloper sets the application's credential, identities, and policies to OVERWRITE mode. That is, the Application Policies, Credentials, and Users and Groups options are selected by default in the Application Properties dialog Deployment page. However, an application's credentials, identities, and policies will be migrated only if the target WebLogic Server instance is set to development mode with -Djps.app.credential.overwrite.allowed=true

When your application is ready for deployment to a production environment, you should remove the identities from the jazn-data.xml file or disable the migration of identities by deselecting Users and Groups from the Application Properties dialog. Application credentials must be manually migrated outside of JDeveloper.

For information about setting credentials in a production enviroment using Enterprise Manager Fusion Middleware Control or WLST scripts, see the Oracle Fusion Middleware Administrator's Guide for Oracle Application Development Framework.

For more information about migrating application credentials and other jazn-data user credentials, see the Oracle Fusion Middleware Security Guide.

<propertySet name="props.auth.uri">
    <property name="login.url.FORM" value="/${app.context}/adfAuthentication"/>
    <property name="logout.url" value=""/>
</propertySet>

<login-config>
  <auth-method>CLIENT-CERT,FORM</auth-method>
  <realm-name>myrealm</realm-name>
  <form-login-config>
     <form-login-page>/login.html</form-login-page>
     <form-error-page>/error.html</form-error-page>
  </form-login-config>
</login-config>

<login-config>
   <auth-method>CLIENT-CERT,BASIC</auth-method>
   <realm-name>myrealm</realm-name>
</login-config>

36.3.5 How to Replicate Memory Scopes in a Clustered Environment

If you are deploying an application that is intended to run in a clustered environment, you need to ensure that all managed beans with a lifespan longer than one request are serializable, and that the ADF framework is aware of changes to managed beans stored in ADF scopes (view scope and page flow scope).

For more information, see Section 20.4.3, "How to Set Managed Bean Memory Scopes in a Server-Cluster Environment."

36.3.6 How to Enable the Application for ADF MBeans

An ADF application uses many XML files for setting configuration information. Three of these configuration files have ADF MBean counterparts that are deployed with the application. After the application has been deployed, you can change configuration properties by accessing the ADF MBeans using the Enterprise Manager Fusion Middleware Control MBean browser.

To enable ADF MBeans, you must register them in the web.xml file. Example 36-4 shows a web.xml file with listener entries for connections, configuration, and business components.

<listener>
   <listener-class>
        oracle.adf.mbean.share.connection.ADFConnectionLifeCycleCallBack
   </listener-class>
</listener>
<listener>
   <listener-class>
        oracle.adf.mbean.share.config.ADFConfigLifeCycleCallBack</listener-class>
</listener>
<listener>
   <listener-class>
        oracle.bc4j.mbean.BC4JConfigLifeCycleCallBack</listener-class>
</listener>

Additionally, ADF connection MBeans require the application to be configured with an MDS repository. ADF Business Components MBeans do not require MDS, but business components configuration is limited to updating the underlying bc4j.xcfg file in the exploded EAR location. MDS configuration entries in the adf-config.xml file for a file-based MDS are shown in Example 36-5. For more information about configuring MDS, see the Oracle Fusion Middleware Administrator's Guide.

<adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config">
   <mds-config xmlns="http://xmlns.oracle.com/mds/config" version="11.1.1.000">
      <persistence-config>
         <metadata-store-usages>
            <metadata-store-usage 
                default-cust-store="true" deploy-target="true" id="myFileStore">
                  <metadata-store name="myReposName"
                       class-name=
                          "oracle.mds.persistence.stores.file.FileMetadataStore">
                       <property name="metadata-path" value="C:\Temp\"/>
                       <property name="partition-name" value="myAppName"/>
                  </metadata-store>
            </metadata-store-usage>
         </metadata-store-usages>
      </persistence-config>
   </mds-config>
</adf-mds-config>

In a production environment, an MDS repository that uses a database is required. You can use JDeveloper, Enterprise Manager Fusion Middleware Control, or WLST commands to switch from a file-based repository to a database MDS repository.

Additionally, if several applications are sharing the same MDS configuration, each application can achieve distinct customization layers by defining a adf:adf-properties-child property in the adf-config.xml file. JDeveloper automatically generates this entry when creating applications. If your adf-config.xml file does not have this entry, add it to the file with code similar to that of Example 36-6.

<adf:adf-properties-child xmlns="http://xmlns.oracle.com/adf/config/properties">
     <adf-property name="adfAppUID" value="Application3-4434"/>
     <adf-property name="partition_customizations_by_application_id"
            value="true"/>
</adf:adf-properties-child> 

The value attribute is either generated by JDeveloper or you can set it to any unique identifier within the server farm where the application is deployed. This value can be set to the value attribute of the adfAppUID property.

When adf-property name is set to adfAppUid, then the corresponding value property should be set to the name of the application. By default, JDeveloper generates the value property using the application's package name. If the package name is not specified, JDeveloper generates the value property by using the workspace name and a four digit random number.

For more information about configuring ADF applications using ADF MBeans, see the Oracle Fusion Middleware Administrator's Guide for Oracle Application Development Framework.

36.4.1 How to Install the ADF Runtime to the WebLogic Server Installation

Oracle WebLogic Server requires the ADF runtime to run Oracle ADF applications.

Installing the ADF runtime is not required if you are using JDeveloper to run applications in Integrated WebLogic Server.

You can install the ADF runtime using the following installers:

• Oracle 11g Installer for JDeveloper: Installs JDeveloper, the ADF runtime, and Oracle WebLogic Server. It does not install Oracle Enterprise Manager.

• Oracle Fusion Middleware 11g Application Developer Installer: Installs the ADF runtime and Oracle Enterprise Manager. You should use the Oracle Fusion Middleware 11g Application Developer Installer if you want to use Oracle Enterprise Manager to manage standalone ADF applications (without Oracle SOA Suite or Oracle WebCenter components). You must have already installed Oracle WebLogic Server before you can use this installer.

If you installed Oracle WebLogic Server together with JDeveloper 11g using the Oracle 11g Installer for JDeveloper (or if you installed it with the Application Development Framework Runtime option selected), the ADF runtime is installed as part of the Oracle WebLogic Server installation. You can proceed to Section 36.4.2, "How to Create and Extend Oracle WebLogic Server Domains."

36.4.2 How to Create and Extend Oracle WebLogic Server Domains

You need to create and configure the Oracle WebLogic Server domain to accept Oracle ADF applications. If you do not already have a domain, you need to create one. If you already have a domain, you must extend the domain before it can run Oracle ADF applications.

If you are using Managed Servers to run your applications, you may need to configure your Managed Server. For more information about configuring a Managed Server on Oracle WebLogic Server, see Oracle Fusion Middleware Creating Domains Using the Configuration Wizard.

If you are setting up Managed Servers for Oracle ADF where the Managed Servers are on the same host as the Administration Server, follow the instructions described in this section.

If you are setting up to deploy to Managed Servers that are on a different host than the Administration Server, perform the additional steps described in Section 36.4.2.3, "Setting Up Remote Managed Servers for Oracle ADF."

36.4.3 How to Create a JDBC Data Source for Oracle WebLogic Server

Oracle ADF applications can use either a JDBC data source or a JDBC URL for database connections. You use the Oracle WebLogic Server Administration Console to configure a JDBC data source. For more information about database access, see Chapter 9, "Configuring Your Application Module Database Connection."

The ADF application module in the data model project can be configured to use a JDBC URL connection type, a JDBC data source connection type, or a combination of both types. By default, ADF application modules use a JDBC URL connection. A component that uses a JDBC URL will attempt to connect directly to the database using the JDBC URL, and it will ignore any JDBC data sources (global or application-level) that are available in WebLogic Server. For more information about migrating JDBC URL security information (user names and passwords) from the application to WebLogic Server, see Section 36.3.4, "How to Deploy Applications with ADF Security Enabled."

An ADF application can use a JDBC data source to connect to the database. A JDBC data source has three types: global, application level, and application level with password indirection. You generally set up a global JDBC data source in WebLogic Server. Any application that requires access to that database can use that JDBC data source. An application can also include application-level JDBC data sources. When the application is packaged for deployment, if the Auto Generate and Synchronize weblogic-jdbc.xml Descriptor During Deployment option is selected, JDeveloper creates a connection_name-jdbc.xml file for each connection that was defined. Each connection's information is written to the corresponding connection_name-jdbc.xml file (entries are also changed in weblogic-application.xml and web.xml). When the application is deployed to WebLogic Server, the server looks for application-level data source information before it looks for the global data source.

If the application is deployed with password indirection set to true, WebLogic Server will look for the connection_name-jdbc.xml file for user name information and it will then attempt to locate application-level credential maps for these user names to obtain the password. If you are using JDeveloper to directly deploy the application to WebLogic Server, JDeveloper automatically creates the credential map and populates the map to the server using an MBean call.

However, if you are deploying to an EAR file, JDeveloper will not be able to make the MBean call to WebLogic Server. You must set up the credential maps using the Oracle WebLogic Administration Console. Even if you have a global JDBC data source set up, if you do not also have credential mapping set up, WebLogic Server will not be able to map the credentials with passwords and the connection will fail. For more information about JDBC data sources, password indirection, and how to set up application credential mappings, see "JDBC Data Sources" in the "Deploying Applications" section of the JDeveloper online help.

To configure Oracle WebLogic Server for a JDBC data source:

1. Start Oracle WebLogic Server (if not already started) by choosing Oracle Fusion Middleware > User Projects > Domain > Start Admin Server for WebLogic Server Domain from the Windows Start menu.

   For Linux, log in as the root user and navigate to:

   <ORACLE_HOME>/user_projects/domains/MYSOADomain/bin
   

   Run the following command:

   ./startWebLogic.sh
   

   Or, from the Application Server Navigator, right-click an Oracle WebLogic Server instance and choose Launch Admin Console.

2. Start the Oracle WebLogic Server Administration Console by choosing Oracle Fusion Middleware > User Projects > Domain > Admin Server Console from the Windows Start menu.

3. Log in to the Oracle WebLogic Server Administration Console.

4. In the WebLogic Server Administration Console page, select JDBC > Data Sources.

5. Click New.

6. In the JDBC Data Source Properties page:

   • In the Name field, enter the name of the JDBC data source.

   • In the JNDI field, enter the name of the connection in the form jdbc/connection DS.

   • For the Database Type, select Oracle.

   • For the Database Driver, select Oracle Driver (thin), and click Next.

7. In the Transactions Options page, accept the default options and click Next.

8. In the Connection Properties page:

   • For Database Name, enter the Oracle SID. For example, orcl.

   • For Host Name, enter the machine name of the database.

   • Enter the port number used to access the database.

   • Enter the user name and password for the database and click Next.

9. In the Test Database Connection page, click Test Configuration to test the connection.

10. In the Select Targets page, select the server for which the JDBC data source is to be deployed.

11. Click Finish.

Once the data source has been created in Oracle WebLogic Server, it can be used by an application module.

36.5.1 How to Deploy to WebLogic Server from JDeveloper

Before you begin:

Create an application-level deployment profile that deploys to an EAR file.

To deploy to the target application server from JDeveloper:

1. In the Application Navigator, right-click the application and choose Deploy > deployment profile.

2. In the Deploy wizard Deployment Action page, select Deploy to Application Server and click Next.

3. In the Select Server page, select the application server connection.

4. Click Finish.

   During deployment, you can see the process steps displayed in the deployment Log window. You can inspect the contents of the modules (archives or exploded EAR) being created by clicking on the links that are provided in the log window. The archive or exploded EAR file will open in the appropriate editor or directory window for inspection.

   If the adf-config.xml file in the EAR file requires MDS repository configuration, the Deployment Configuration dialog appears for you to choose the target metadata repository or shared metadata repositories, as shown in Figure 36-3. The Repository Name dropdown list allows you to choose a target metadata repository from a list of metadata repositories registered with the Administration Server. The Partition Name dropdown list allows you to choose the metadata repository partition to which the application's metadata will be imported during deployment. You can use WLST commands or the Oracle WebLogic Server Administration Tool to configure and register MDS. For more information about managing the MDS Repository, see the Oracle Fusion Middleware Administrator's Guide.

   Figure 36-3 MDS Configuration and Customization for Deployment

   
   

   Note:

   If you are deploying a Java EE application, click the application menu next to the Java EE application in the Application Navigator.

   For more information on creating application server connections, see Section 36.3.1, "How to Create a Connection to the Target Application Server."

   Tip:

   You may get an exception in JDeveloper when trying to deploy large EAR files. The workaround is to deploy the application using the Oracle WebLogic Server Administration Console.

36.5.2 How to Create an EAR File for Deployment

You can also use the deployment profile to create an archive file (EAR file). You can then deploy the archive file using Enterprise Manager, WLST scripts, or Oracle WebLogic Server Administration Console.

Although an ADF application is encapsulated in an EAR file (which usually includes WAR, MAR, and JAR components), it may have parts that are not deployed with the EAR. For instance, ADF Business Services can be deployed as a JAR. For more information about business services, see Section 11.2.19, "How to Deploy Web Services to Oracle WebLogic Server."

To create an EAR archive file:

• In the Application Navigator, right-click the application containing the deployment profile, and choose Deploy > deployment profile > to EAR file.

  If an EAR file is deployed at the application level, and it has dependencies on a JAR file in the data model project and dependencies on a WAR file in the view-controller project, then the files will be located in the following directories by default:

  • ApplicationDirectory/deploy/EARdeploymentprofile.EAR

  • ApplicationDirectory/ModelProject/deploy/JARdeploymentprofile.JAR

  • ApplicationDirectory/ViewControllerProject/deploy/WARdeploymentprofile.WAR

36.5.3 What You May Need to Know About ADF Libraries

An ADF Library is a JAR file that contains JAR services registered for ADF components such as ADF task flows, pages, or application modules. If you want the ADF components in a project to be reusable, you create an ADF Library deployment profile for the project and then create an ADF Library JAR based on that profile.

An application or project can consume the ADF Library JAR when you add it using the Resource Palette or manually by adding it to the library classpath. When the ADF Library JAR is added to a project, it will be included in the project's WAR file if the Deployed by Default option is selected.

For more information, see Chapter 33, "Reusing Application Components."

36.5.4 What You May Need to Know About EAR Files and Packaging

When you package an ADF application into an EAR file, it can contain the following:

• WAR files: Each web-based view controller project should be packaged into a WAR file.

• MAR file: If the application has customizations that are deployed with the application, it should be packaged into a MAR.

• ADF Library JAR files: If the application consumes ADF Library JARs, these JAR files may be packaged within the EAR.

• Other JAR files: The application may have other dependent JAR files that are required. They can be packaged within the EAR.

36.5.5 How to Deploy the Application Using Scripts and Ant

You can deploy the application using commands and automate the process by putting those commands in scripts. The ojdeploy command can be used to deploy an application without JDeveloper. You can also use Ant scripts to deploy the application. JDeveloper has a feature to help you build Ant scripts. Depending on your requirements, you may be able to integrate regular scripts with Ant scripts.

For more information about commands, scripts, and Ant, see the Oracle Fusion Middleware Administrator's Guide for Oracle Application Development Framework.

36.5.6 What You May Need to Know About JDeveloper Runtime Libraries

When an application is deployed, it includes some of its required libraries with the application. The application may also require shared libraries that have already been loaded to WebLogic Server as JDeveloper runtime libraries. It may be useful to know which JDeveloper libraries are packaged within which WebLogic Server shared library. For a listing of the contents of the JDeveloper runtime libraries, see the Oracle Fusion Middleware Administrator's Guide for Oracle Application Development Framework.

36.6.1 How to Migrate an Application

If you want to migrate an ADF application from one WebLogic Server to another WebLogic Server, you may need to perform some of the same steps you did for a first time deployment.

In general, to migrate an application, you would:

• Load the ADF runtime (if it is not already installed) to the target WebLogic Server. For instructions, see Section 36.4.1, "How to Install the ADF Runtime to the WebLogic Server Installation.".

• Configure the target WebLogic Server with the correct database or URL connection information. For instructions, see Section 36.4.3, "How to Create a JDBC Data Source for Oracle WebLogic Server."

• Migrate security information from the source to the target. For instructions, see Section 36.3.4, "How to Deploy Applications with ADF Security Enabled."

• Deploy the application using Enterprise Manager, Oracle WebLogic Administration Console, or scripts. For more information, see the Oracle Fusion Middleware Administrator's Guide for Oracle Application Development Framework.

36.6.2 How to Configure the Application Using ADF MBeans

If ADF MBeans were enabled and packaged with the deployed application, you can configure ADF properties using the Enterprise Manager MBean Browser. For instructions to enable an application for MBeans, see Section 36.3.6, "How to Enable the Application for ADF MBeans."

For information on how to configure ADF applications using ADF MBeans, see the Oracle Fusion Middleware Administrator's Guide for Oracle Application Development Framework.