1. Deploying JD Edwards EnterpriseOne on Linux Learning Path
  2. Setting Up the WebLogic Server

Setting Up the WebLogic Server

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

Prerequisite

You must have performed the functions described in the module "All Servers Common Setup" 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.

These are the prerequisites for Oracle WebLogic Server:

  1. Ensure that you have performed all the tasks described in module "All Linux Servers Common Setup" of this Learning Path including the steps to create groups and users as well as assigning proper permissions to /u01.
  2. Use this command to ensure that the /u01 mount point has proper permissions to allow the One-Click Provisioning process to subsequently create the requisite folders:

    sudo chmod 770 /u01

  3. Ensure the user with which Oracle WebLogic Server was installed is part of the oracle group. Use this command to verify:

    groups username

Install Oracle WebLogic Server and a JDK

You must manually pre-install Oracle WebLogic Server (WebLogic Server) and a JDK for use by WebLogic Server.

Important: You must ensure that the JDK is installed under the /u01 mount point. Further you must 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 vice versa depending on the order you install these products.

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

The complete list of prerequisites is provided below:

  • A supported version of WebLogic Server must be pre-installed.
    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.

  • A supported JDK version must be installed.
  • WebLogic Server must be defined with at least one domain.
  • WebLogic Server must be in a running state and able to connect to the Admin Console.
  • WebLogic Server must have a running Node Manager process for the existing domain.
  • WebLogic Server must be installed as a user that is part of the oracle group.

Post Installation Tasks for WebLogic Server

After you have installed the WebLogic Server, prior to using the Provisioning Console for JD Edwards EnterpriseOne, you must manually configure 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 must be set exactly same as value of ListenAddress property of nodemanager.properties file. You must set the listen port 5556, which is non-secure (instead of 5557, which is secure ) in both Node Manager properties file and in node manager using the WebLogic Server user interface. For instructions refer to this procedure: Changing the Oracle HTTP Server Listen Ports.

  5. 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.