This chapter contains the following topics:
This section describes how to install EnterpriseOne ADF Container.
Important:
You must have completed the steps to install the JDETaskFlowLibrary.war file outlined in Chapter 4.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 Server 12c 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 Ant script to update the e1adf.ini values, the build location needs to include the following files:
Table 5-1 Build Location Files
| Name | Type |
|---|---|
|
E1 ADF Container/build.xml |
XML Ant Script File |
|
E1 ADF Container/ build.properties |
PROPERTIES File |
|
E1 ADF Container/JDEADFContainer.ear |
EAR File |
Before the JDEADFContainer.ear file can be deployed, the e1adf.ini file needs to be configured so the web application can communicate with the EnterpriseOne JAS. An Ant script is used to update the following values in the e1adf.ini file:
| e1adf.ini Property | An Script Property | Description |
|---|---|---|
|
aisServer |
ais.server |
The URL of the AIS server used to populate data in the ADF applications. Usually this AIS server is configured to point to the same JAS server where Simplified UI is configured. Use the URL you kept track of from section 2.2 for this property. |
|
deviceName |
device.name |
The device name sent with every request to the AIS Server (AIS requires it). |
|
jasWhitelist |
jas.whitelist |
Comma-delimited list of JAS URLs that are allowed to imbed this EnterpriseOne ADF Container when Simplified User Interface is configured on the JAS server. The whitelist needs a comma-delimited list of server URLs for JAS. The server URL should be of the form <Protocol>://<IP Address/Fully Qualified Domain Name>:<Port>. The IP Address/Fully Qualified Domain Name value depends on how the server has been set up and what URL the client (browser) sees as the server's origin. There is no penalty for an incorrect value being part of the whitelist, as long as the correct value is also present. |
|
injectIframeBustingHeaders |
inject.framebusting.headers |
When set to true Content Security Policy (CSP) headers are included on every response from the ADF server, false indicates no CSP headers are added. The recommended setting is True. |
|
sessionTimeout |
session.timeout |
The amount of time the E1 ADF Container session stays alive while the user is not interacting with it, expected in milliseconds - recommended to be longer than E1 HTML Server. Be sure to define the EnterpriseOne ADF Container session timeout following this guideline: EnterpriseOne HTML server session timeout < EnterpriseOne ADF Container session timeout < AIS server session timeout |
You need to update the build.properties file for each of the Ant Script Property entries listed in Table 5-2.
You execute the script at the command line from the directory that contains the build.xml script file using either of the following commands:
$ant
or
$ant build
These commands execute the build target in the Ant script, which unpackages the JDEADFContainer.ear file, updates the e1adf.ini file, and repackages the .ear file in a new deploy directory, as listed in the following table:
| Name | Type |
|---|---|
|
E1 ADF Container/deploy |
File Folder |
|
E1 ADF Container/build.properties |
PROPERTIES File |
|
E1 ADF Container/ build.xml |
XML Ant Script File |
|
JDEADFContainer.ear |
EAR File |
The JDEADFContainer.ear file in the deploy directory can then be manually deployed to a Weblogic server instance or cluster, or follow the instructions in section Section 4.3.2, "Using EnterpriseOne ADF Application Build Script to Install/Deploy the EnterpriseOne ADF Applications Library to a Weblogic Server".
Prior to deploying the EnterpriseOne ADF Container to a Weblogic server, you must have followed the instructions in section Section 5.1.1, "Using EnterpriseOne ADF Container Build Script to Update the e1adf.ini Settings".
Build Directories and Contents
Prior to executing the Build script to install/deploy the EnterpriseOne ADF Container to a Weblogic server, the build location needs to include the files as described in Table 5-3.
Use the build script to deploy the updated JDEADFContainer.ear 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 JDEADFContainer web application is deployed. |
|
weblogic.debug |
Enables wldeploy debugging messages. |
|
weblogic.verbose |
Specifies whether wldeploy displays verbose output messages. |
|
weblogic.remote.deploy |
Specifies whether the server is located on a different machine. This affects how filenames are transmitted. The default value is true for this property. |
|
weblogic.upload.ear |
Specifies whether the JDEADFContainer.ear 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 JDEADFContainer.ear file to the specified Weblogic servers and/or clusters. If the ear file does not exist, an error message displays 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 JDEADFContainer.ear file was successfully created. The user will be prompted to enter the Weblogic server username and password during deployment.