Setting Up the WebLogic Server

This section shows you how to set up the WebLogic Server for JD Edwards EnterpriseOne.

Prerequisites

• You must have a Microsoft Windows VM or server for the WebLogic Server.
• You must have performed the steps described in the module "Performing Common Setup for All Microsoft Windows Servers" of this Learning Path.

General

Important:

The deployment of the JDK using One-Click Provisioning Console removes the string anon, NULL from the property jdk.tls.disabledAlgorithms in the file \jre\lib\security.

Enable remote command execution through PowerShell by using this command:

winrm quickconfig –q

Install the Oracle WebLogic Server and a JDK

You must manually preinstall the Oracle WebLogic Server (WebLogic Server) and a JDK to be used for the WebLogic Server.

Important:

For the JDK installation, ensure that the JDK is installed by the same user that has been or will be used to install the WebLogic Server. For example, if you use the oracle user to install the JDK, you must use the oracle user to install the WebLogic Server, or conversely depending on the order in which you install these products.

Customers can then use JD Edwards One-Click Provisioning to deploy the JD Edwards EnterpriseOne web components into the preinstalled WebLogic Server domain. Refer to the Oracle Certifications for JD Edwards EnterpriseOne One-Click Provisioning on Oracle Cloud Infrastructure for details on the supported versions of the WebLogic Server.

The complete list of prerequisites are below:

• Compute instance must have a supported version of WebLogic Server preinstalled.

  The password must be 8 to 30 characters long, must contain at least one number, and optionally any number of either the Pound Sign (#) or Underscore (_) special characters.

  Important:

  The password for any WebLogic Server user cannot contain these special characters:

    Dollar Sign ($)
    Exclamation Mark (!)
    Ampersand (&)

  Using any of the above special characters violates the Oracle Cloud password policy and will result in denied access.

• Compute instance must also have a supported JDK version installed.
• WebLogic Server must be defined with at least one domain.
• WebLogic Server must be in a running state and be able to connect to the Admin Console.
• WebLogic Server must have a running Node Manager process for the existing domain.

Postinstallation of WebLogic Server

After you have installed the WebLogic Server, prior to using the Provisioning Console for JD Edwards EnterpriseOne, you must manually configure the WebLogic Node Manager to disable SSL. Otherwise the provisioning will fail.

1. Locate the nodemanager.property file which is typically found in this location:

   <ORACLE_HOME>/user_projects/domains/<DOMAINNAME>/nodemanager/nodemanager.properties

2. Edit the nodemanager.property file to set this property to disable SSL:

   SecureListener=false

3. Save the nodemanager.property file.

4. You must set the listen address to have the same value as the ListenAddress property of the nodemanager.properties file. You must set the listen port 5556, which is non-secure (instead of 5557, which is secure ) in both the Node Manager properties file and in the Node Manager using the WebLogic Server user interface. For instructions, refer to this procedure: Changing the Oracle HTTP Server Listen Ports.

   Note: If the Node Manager machine is not reachable, perform these steps:

   • Log in to the WebLogic Server Admin Console.
   • Expand Environment.
   • Click Machines.
   • Select your machine.
   • Click the Node Manager tab and make sure that Type is set to Plain.
   • Restart the WebLogic Node Manager for the setting to take effect.

Ensure WebLogic Server is Patch Current

Refer to the Oracle Certifications for One-Click for WebLogic Server to verify that the latest available patches are applied. Such patches can affect the ability of One-Click Provisioning to deploy web components into the WebLogic Server.