This chapter contains the following topics:
Section 7.1, "Manually Deploying the EnterpriseOne Container and ADF Application to Weblogic"
Section 7.4, "EnterpriseOne ADF Deployment Additional Information"
Section 7.7, "Host Verification Errors, or Failure to Open ADF Application"
This section describes how to deploy the JDEADFContainer .EAR file.
Open the Weblogic Server application.
In the Domain Structure area located on the left side of the screen, click Deployments.
In the Change Center area located on the left side, above the Deployments area, click the Lock & Edit button.
In the Summary of Deployments area, click the Install button.
The Install Application Assistant displays.
In the Deployment Archive section, click the Choose File button.
Locate the JDEADFContainer.ear file, select it, and then click the OK button.
Click the Next button.
Click the Next button.
Click the Next button.
In the Available targets for JDEADFContainer-2 section, select the ADF server to which you want to install the JDEADFContainer.ear file, and then click the Next button.
Click the Finish button.
The JDEADFContainer.ear file installs on the ADF server.
After the JDEADFContainer.ear file installs, in the Change Center area located on the left of the screen, click the Activate Changes button.
On the Control tab located in the center of the screen, select the ADF Server you just installed, and then select the Servicing all Request option located on the corresponding drop-down menu.
Click the Yes button to start the JDEADFContainer.ear file.
The Start Deployments screen displays.
Click the Yes button.
Verify that final state of the container is Active.
There are two Ant scripts required to install and deploy ADF libraries on a Weblogic server. Both Ant scripts use the wldeploy task to deploy artifacts to server instances or clusters on a Weblogic server. Both of the Ant scripts provide these additional targets:
| Ant Script Target | Description |
|---|---|
| clean | Removes the build and deploy directories. |
| usage | Displays a list of command line options that will provide additional information about Ant or the build scripts. |
| undeploy | Removes the JDEADFContainer.ear or the JDETaskFlowLibrary.war from Weblogic server, depending on which ant script is executed. |
The JDE Ant build files can be executed from within JDeveloper by adding the Ant targets to the Tools menu as External Tool executables.
To execute Ant Targets from JDeveloper menu
In JDeveloper, click Tools, then External Tools, and then select New from the External Tools dialog box.
Click Next.
Browse to the Ant build file you want to run, and click Next.
Move the build-and-deploy target to the Selected Targets field, and then click Next.
Set the Weblogic username and password properties needed for the build-and-deploy, deploy, and undeploy targets only. For any other Ant target in the script, these properties are not used.
The administrative username - weblogic.username
The administrative password - weblogic.password
Select the Use Default Ant Version option, and then click Next.
Specify the options for the Ant process, and then click Next.
The Weblogic.jar includes the class definition for the wldeploy Ant task used to deploy/undeploy files to/from a Weblogic server. The Weblogic.jar file can be found in the <Weblogic_HOME>/server/lib directory, where Weblogic_HOME is the top-level directory of your Weblogic Server installation. This step is not necessary for any other Ant target in the build scripts.
Enter a caption for the menu item, and then click Next.
Select the Tools Menu option for the Add Items to Menus list, and then click Next.
Select Always, and then click Finish.
Once the Ant target is added, it can be executed from the Tools menu. During execution, the Apache Ant log will display the Ant target's status and display messages if any exceptions are thrown.
EnterpriseOne ADF application deployment supports clustering.
This section describes error messages you may see and provides an explanation of what they mean:
Error: System issues prevent the application from opening. Please contact your system administrator.
The EnterpriseOne HTML server Jas log would contain additional information: "The external application launch has failed. The handshake id is null or never completed its initialization. Verify that your system is running and its ini settings are properly configured."
As the message notes, the handshake ID is either null or blank. Potential reasons for this situation could be 1. jasWhitelist on ADF server is not configured correctly and 2. AIS or ADF server(s) is (are) down.
Error: Invalid application data. Please contact your system administrator.
Ensure that the proxy application associated with the EnterpriseOne ADF application is properly defined and secured. Users could see this error message if the EnterpriseOne task containing the EnterpriseOne ADF application lacks a proxy app and/or task flow path/url. See the JD Edwards EnterpriseOne Tools Solution Explorer guide for additional details on this EnterpriseOne ADF application task).
The ADF charts continue trying to load when there is not a monitor associated with the server. When this happens, the following error appears in the Weblogic Server Diagnostic logs:
Can't connect to X11 window server using '10.111.111.150:0.0' as the value of the DISPLAY variable.
To fix this circumstance, configure the server instances with the following Java property set to "true":
-Djava.awt.headless=true
Setting this property to "true" prevents the Java runtime from attempting to find a monitor to get the DISPLAY variable.
To configure this property in WebLogic Server:
On the Server Start tab, add -Djava.awt.headless=true in the Arguments field.
Click Save.
Restart the managed instance.
If you have configured a reverse proxy and enabled Secure Sockets Layer (SSL), ensure that the Host Verification setting is set to None. You can locate this setting on your Web Logic Server, on the SSL tab, in the Advanced section.