After customizing existing artifacts, JDeveloper can be used to deploy the customizations to Oracle Weblogic Server.

The default customization workspace as described in Section 3.1, About Using JDeveloper for Customization, contains a MAR profile. By default, the name of the MAR profile is application_name_customizations. It will automatically include the customizations that are implemented. This profile can be used to package the customizations for deployment.

When customizations are packaged from the customization workspace, the MAR file should include only library customizations. Do not include the User Metadata or HTML Root Dir for Project in the MAR profile, unless explicitly directed to do so by product documentation.

If the application is extended with new custom artifacts, JDeveloper can be used to package them into an ADF Library JAR and place them into the proper location within the application directory structure.

Task: Deploy the Customizations

JDeveloper can be used to deploy the customizations directly or to create a MAR, and then load the MAR using WLST commands or the WebLogic Server Administration Console.

When customizations are deployed on ADF Business Component objects (such as entity objects and view objects), the server must be restarted for the customizations to be picked up.

Task: Package New Artifacts into ADF Library

If the application is extended with new custom artifacts (or new artifacts are supplied with), these artifacts must be packaged into an ADF library JAR and place the JAR files in the proper location within the application.

The ADF library JAR for the new model artifacts (such as entity objects and view objects) should be placed into the /APP-INF/lib directory. The ADF Library JAR for the new user interface artifacts (such as pages) should be placed in the /WEB-INF/lib directory.