This chapter contains the following topics:
To download the EnterpriseOne ADF foundation, complete the following steps:
Access the Oracle Update Center.
Search for the ADF Par file, and download it to your destination server.
Search for Type EnterpriseOne ADF.
Download the appropriate version of the E1 ADF Container.
Unless otherwise noted, this will be the latest version.
The following files will be downloaded to the directory you choose.
Note:
The E1UserSession.jar provides classes required for creating E1 ADF applications. See the JD Edwards EnterpriseOne Tools Developing and Customizing EnterpriseOne Simplified User Applications Guide for more information.E1 ADF Container/build.xml
E1 ADF Container/build.properties
E1 ADF Application/build.xml
E1 ADF Application/build.properties
JDEADFContainer.ear
To locate the download on the JD Edwards Update Center, use the Type field to search on EntepriseOne ADF. The download is available in a package titled E1_ADF_Foundation_1.1.0. The download contains the following files:
Ant Build Scripts (Ant build/deploy scripts for EnterpriseOne ADF applications and JDEADFContainer.ear).
JDEADFContainer.ear (EnterpriseOne ADF Container web application)
E1UserSession.jar (Helper classes required for developing EnterpriseOne ADF applications)
To download the EnterpriseOne ADF applications, complete the following steps:
Access the Oracle Update Center.
Use Type EnterpriseOne ADF to see the list of available EnterpriseOne ADF applications.
Search for Type EnterpriseOne ADF.
Download the latest version of the EnterpriseOne ADF Applications, unless otherwise noted.
EnterpriseOne ADF applications are ADF bounded task flows packaged into ADF library jar files. They are not separate web applications and cannot run outside of the EnterpriseOne ADF Container (JDEADFContainer). Therefore, you must deploy EnterpriseOne ADF applications in a library WAR file on the same domain for them to run inside the EnterpriseOne ADF Container web application.
The build script uses the wldeploy task to deploy artifacts to server instances or clusters on a Weblogic server. The following list contains facts you need to know:
The scripts must execute on a machine with a Weblogic install to access the wldeploy task definition class. This install can be the integrated Weblogic instance included with a JDeveloper install, or a standalone Weblogic server.
Before executing the deploy targets from the Ant scripts using the command line, the environment must be setup to use the wldeploy task, according to instructions in the Basic Steps for Using wldeploy section of the "wldeploy Ant Task Reference" chapter in the Oracle® Fusion Middleware: Developing Applications for Oracle Weblogic Server12c Release 1(12.1.1) guide.
These scripts will only deploy to Weblogic servers.
The following instructions execute the build script from the command line. Alternatively, you can execute the build script from within JDeveloper. See Section 7.3, "Executing the Build Script from JDeveloper".
Build Directories and Contents
Prior to executing the build script to generate the library WAR file, the build location needs to include the following files and directory, where the directory contains the ADF library jar files to include in the library WAR file.
| Name | Type |
|---|---|
|
E1 ADF Application/ADFLibraryJARs |
File Folder |
|
E1 ADF Application/ build.properties |
PROPERTIES File |
|
E1 ADF Application/ build.xml |
XML Ant Script File |
The properties listed in the following table are located in the build.properties file. These properties should be populated prior to running the script to deploy so that the EnterpriseOne ADF applications library manifest file is updated with the correct settings.
| Ant Script Property | Description |
|---|---|
|
implementation.version |
Identifies the implementation version of the library WAR file |
|
specification.version |
Identifies the specification version of the library WAR file |
|
created.by |
Identifies the entity that created the library WAR file |
The build.properties file can be modified to point to a different JAR directory, if desired. However, you should not modify the extension-name property. The JDEADFContainer requires a library WAR file that matches the name specified for this property.
Once the properties are set in the build.properties file, you can execute the script at the command line using the following commands:
$ant
or
$ant build
These commands will execute the build target in the Ant script, which packages the bounded task flow library jar files from the ADFLibraryJARs directory into a deployable library WAR file created in the deploy directory.
| Name | Type |
|---|---|
|
E1 ADF Application/ADFLibraryJARs |
File folder |
|
deploy |
File folder |
|
build.properties |
PROPERTIES File |
|
build.xml |
XML Ant Script File |
The JDETaskFlowLibrary.war file in the deploy directory can then be manually deployed to a Weblogic server instance or cluster or can be automatically deployed, as described in section Section 5.1.2, "Using EnterpriseOne ADF Container Build Script to Install/Deploy the EnterpriseOne ADF Container to a Weblogic Server".
This section explains how to install and deploy EnterpriseOne ADF Applications Library to a Weblogic Server.
Build Directories and Contents
Prior to executing the build script to install/deploy the EnterpriseOne ADF Applications to a Weblogic server, the build location needs to include the files as described in Table 4-3.
The Ant script can also be used to immediately deploy the JDETaskFlowLibrary.war file to a Weblogic Server instance or cluster once the build process has completed.
The following table lists properties in the build.properties file that need to be populated prior to running the script to deploy:
| Ant Script Property | Description |
|---|---|
|
weblogic.server.host |
The host on which the Administration Server is running. |
|
weblogic.server.port |
The port which the Administration Sever is listening. |
|
weblogic.deploy.targets |
A comma-separated list of the target servers, clusters, or virtual hosts to which the JDE task flow library is deployed. |
|
weblogic.debug |
Enables wldeploy debugging messages. |
|
weblogic.verbose |
Specifies whether wldeploy displays verbose output messages. |
|
weblogic.remote.deploy |
Specifies if the server is located on a different machine. This affects how filenames are transmitted. The default value is true for this property. |
|
weblogic.upload.war |
Specifies if the JDETaskFlowLibrary.war file is copied to the Administration server's upload directory prior to deployment. The default value is true for this property. |
Once the properties are set in the build.properties file, you can execute the script at the command line in the directory that contains the build.xml script file using one of the following commands:
$ant deploy
or
$ant build-and-deploy
The first command will execute the script's deploy target only and attempt to deploy the JDETaskFlowLibrary.war to the specified Weblogic servers and/or clusters. If the library war file does not exist, an error message is displayed, instructing the user to run the build target first. The second command will first launch the script's build target and then the deploy target, if the JDETaskFlowLibrary.war file was successfully created. The user will be prompted to enter the Weblogic server username and password during deployment.
This section describes how to configure EnterpriseOne ADF applications.
Setting up Security for ADF/Proxy Applications
When you create an EnterpriseOne ADF application, you associate it with a proxy application, which is a standard EnterpriseOne application (Form Design Aid (FDA) application. You configure security on the proxy application through the Security Workbench (the same as all FDA applications).
You can create different versions of the proxy application associated with an EnterpriseOne ADF application. See the JD Edwards EnterpriseOne Tools Developing and Customizing EnterpriseOne Simplified User Applications guide for details about this.
You can define a different set of processing options for each version of an EnterpriseOne ADF application. See the JD Edwards EnterpriseOne Tools Developing and Customizing EnterpriseOne Simplified User Applications guide for details about this.