This appendix contains the following topics:
Before using the downloaded ADF application JDeveloper projects, perform the following tasks:
Review the ADF application development processes found in Part III, "EnterpriseOne ADF Application Development Resources"of this guide.
Download the JD Edwards EnterpriseOne ADF application (.zip) files from the JD Edwards Update Center on My Oracle Support:
Ensure that you have the correct version of JDeveloper (12.1.3 or 12.2.1) installed.
Important:JD Edwards EnterpriseOne ADF applications were developed using JDeveloper versions 12.1.3 or 12.2.1. If the application was developed with JDeveloper 12.1.3, then both 12.1.3 and 12.2.1 source .zip files are provided on the JD Edwards Update Center. If the application was developed in 12.2.1, then this is the only source provided. Source written in JDeveloper 12.2.1 cannot be migrated backward to version 12.1.3.
JD Edwards EnterpriseOne ADF applications are built using JDeveloper. An EnterpriseOne ADF application archive is a specially built JDeveloper project that enables developers to take an existing EnterpriseOne ADF application, customize it to suit their particular business needs, and generate their own .jar file.
The ADF application source is delivered as part of the download from the Update Center. The download contains a .zip file, in which you will find the application source project. See Appendix A, "Creating a Sample EnterpriseOne ADF Application" for references when making any specific, necessary changes to the source code.
In order for the project to compile, you need to attach five .jar files that are provided by Oracle. These steps are referenced in step 7 of Section A.2.1, "Getting Started" and in Section A.2.2, "Creating a New EnterpriseOne ADF Application". The five .jar files are located in the AIS_Client_Java_API_XXX and the E1_ADF_Foundation_XXX downloads in the Update Center. You should remove any older references to these .jar files before attaching the new ones.
If you are deploying the ADF Server using Server Manager and plan to include custom ADF applications on your ADF Server, you need to bundle the scf-manifest.xml file with your custom ADF application so that Server Manager recognizes it as an ADF application component, which can be used for the creation of an ADF Server Instance. If a valid scf-manifest.xml file is available in the ADF application component JAR file, the provided version, description, and componentName appear in the Server Manager Console.
You can use the existing scf-manifest.xml files as a reference for creating the scf-manifest.xml file for your ADF application. Here is an example of the scf-manifest.xml file from the EnterpriseOne ADF Visual Bill of Material application:
<scf-manifest targetType="adfAppComponent" version="92" componentName="E1_ADF_VisualBillOfMaterial_92" description="E1 ADF VisualBillOfMaterial v92" minimumAgentLevel="131"> </scf-manifest>
After acquiring the scf-manifest.xml file from the Update Center, modify the file to identify your application in Server Manager. Update the values for the following fields:
version - Corresponds to the version shown in the Server Manager Console.
componentName - Provides a descriptive name of your application in the Server Manager Console.
description - Provides additional details about the application.
The scf-manifest.xml file should reside in your view controller project path within the \adfmsrc\META-INF\ folder. When you build a new .jar file, this file will get bundled.
After completing your modifications, follow the steps in Section A.3.10, "Creating ADF Library JAR File" to generate a .jar file from your source code. The new file will then be used instead of the one provided in the download from the Update Center.