1. Deploying JD Edwards EnterpriseOne on Oracle Cloud Infrastructure on Linux with Autonomous Database 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 on the Oracle Cloud Infrastructure.

Prerequisite

  • You must have created a Linux VM for the WebLogic Server.
  • The Linux VM for the WebLogic Server must be allocated with storage volume space, the amount of which is specified in the module of this Learning Path Entitled: Before You Begin.
  • You must have performed the functions described in the module of this Learning Path entitled: All Servers Common Setup.
  • If you are installing WebLogic Server in a Compute instance, complete sections 1 through 4.
  • If you have installed WebLogic Server using an image provided by Oracle Cloud Infrastructure, complete sections 1 through 5.

General

The following general prerequisites are required for the Oracle WebLogic Server:

  1. Ensure you have performed all the tasks described in module of this Learning Path entitled: Performing Common Setup for All Linux Servers 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 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: For the JDK installation, you must ensure that it 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 WebLogic Server. For example, if you use the oracle user to install the JDK, you must use the oracle user to install WebLogic Server, or vice versa depending on the order you install these products.

Customers 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 on OCI for details on supported versions of WebLogic Server.

The complete list of prerequisites are below:

  • Compute instance must have a supported version of WebLogic Server 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.
  • 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 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 of WebLogic Server

After you have installed 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 so 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 WebLogic Server.

Configuring a WebLogic Server Instance Installed from the Marketplace of Oracle Compute Infrastructure

This section is only required if you have installed WebLogic Server from the Marketplace of Oracle Cloud Infrastructure.

The following describes feature support for an installation of WebLogic Server from the Marketplace for Oracle Cloud Infrastructure:

  • Standard or Enterprise Edition

    Both of these editions are supported.

  • Number of Nodes

    Only a single node is supported.

  • Load Balancer

    This feature is not supported by JD Edwards One-Click Provisioning.

After the WebLogic Server is installed from the Marketplace of Oracle Cloud Infrastructure, you must perform further configuration as described below.

  1. Connect to your instance of WebLogic Server.
  2. Access the WebLogic Admin Console.
  3. Navigate to Environments, Machines.
  4. Select the tab for Configuration, Node Manager.
  5. Set Type as PLAIN.
  6. Save the selection.
  7. Log in to WebLogic Server instance and edit the /etc/hosts file to add these two lines:

    <Private ip> localhost localhost.localdomain localhost4 localhost4.localdomain4

    <Private ip> <FQDN> <short host name>

  8. Run this command to enable root account:

    sudo usermod -s /bin/bash root