8-14 Java EE Developers Guide for Oracle Application Development Framework
■
If a dependent ADF library JAR for the project contains seeded customizations, they will automatically be added to the MAR during MAR
packaging. They will not appear in the MAR profile.
■
If ADF Library customizations were created in the context of the consuming project, those customizations would appear in the MAR profile dialog by
default.
5. Click OK to exit the Edit MAR Deployment Profile Properties dialog.
6. Click OK again to exit the Application Properties dialog.
8.3.2.4 Creating an EJB JAR Deployment Profile
If you are using an EJB module in the model project, you need to create an EJB JAR deployment profile.
Before you begin: Create a model project that has an EJB module.
To create an EJB JAR deployment profile for an application: 1.
In the Application Navigator, right-click the web project that you want to deploy and choose New.
2. In the New Gallery, expand General, select Deployment Profiles and then EJB
JAR File
, and click OK. If you don’t see Deployment Profiles in the Categories tree, click the All
Technologies tab.
3.
In the Create Deployment Profile -- EJB JAR File dialog, enter a name for the deployment profile and click OK.
4.
In the Edit EJB JAR Deployment Profile Properties dialog, choose items in the left pane to open dialog pages in the right pane. Configure the profile by setting
property values in the pages of the dialog.
5. Click OK to exit the Edit EJB JAR Deployment Profile Properties dialog.
6. Click OK again to exit the Project Properties dialog.
8.3.2.5 Creating an Application-Level EAR Deployment Profile
The EAR file contains all the necessary application artifacts for the application to run in the application server. For more information about the EAR file, see
Section 8.4.5, What You May Need to Know About EAR Files and Packaging.
Before you begin:
■
Add classes into a JAR file, as described in Section 8.3.2.1, Adding Customization
Classes into a JAR.
■
Create the WAR deployment profiles, as described in Section 8.3.2.2, Creating a
WAR Deployment Profile.
To create an EAR deployment profile for an application: 1.
In the Application Navigator, right-click the application and choose New.
You will create an EAR profile for the application.
2. In the New Gallery, expand General, select Deployment Profiles and then EAR
File,
and click OK.
Deploying an ADF Java EE Application 8-15
If you don’t see Deployment Profiles in the Categories tree, click the All Technologies
tab.
3.
In the Create Deployment Profile -- EAR File dialog, enter a name for the application deployment profile and click OK.
4.
In the Edit EAR Deployment Profile Properties dialog, choose items in the left pane to open dialog pages in the right pane. Configure the profile by setting
property values in the pages of the dialog.
Be sure that you:
■
Select Application Assembly and then in the Java EE Modules list, select all the project profiles that you want to include in the deployment, including any
WAR or MAR profiles.
■
Select Platform, and select the application server you are deploying to, and then select the target application connection from the Target Connection
dropdown list.
5.
If you have customization classes in your application, configure these classes so that they load from the EAR-level application class loader.
a. In the Edit EAR Deployment Profile Properties dialog, select Application
Assembly .
b.
Select the JAR deployment profile that contains the customization classes, and enter lib in the Path in EAR field at the bottom of the dialog.
The JAR file containing the customization classes is added to the EAR file’s lib directory.
6. Click OK to exit the Deployment Profile Properties dialog.
7. Click OK again to exit the Application Properties dialog.
Note: If you are using custom JAAS LoginModule for authentication
with JAZN, the context root name also defines the application name that is used to look up the JAAS LoginModule.
Note: You should have created this JAR as described in
Section 8.3.2.1, Adding Customization Classes into a JAR.
Note: If you have customization classes in your application, you
must also make sure they are not loaded from the WAR. By default, customization classes that are added to the model projects Libraries
Classpath are packaged to the WAR class path.
To make sure customization classes from an extension project are not duplicated in the WAR, be sure to deselect any customization class
archive on the Library Dependencies page for the WAR.
If you created your customization classes in the model project of the consuming application, deselect any customization classes on the File
Groups WEB-INFclasses Filters page for the WAR.
