Preparing for a Deployment of JD Edwards EnterpriseOne On Premises on Linux

This sections describes these setup tasks which must be performed on each Linux-based server:

• General
  
• Disable Firewall Services
• Set Up Users and Groups
• Install Requisite YUM Packages

General

The following general prerequisites are required for each Linux server:

1. Ensure that the Host Name of a Linux server contains only alphanumeric values. For all servers, you cannot use special characters in the name, such as an underscore “_”.
2. If the /u01 mount point does not exist, create it using this command:
   
   cd / sudo mkdir u01
   
3. 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

4. Verify the /etc/ssh/sshd_configfile contains this setting:

   ClientAliveInterval 3600

   Ensure that the setting exists, is set properly to 3600, and is not commented out.

5. Verify the /etc/ssh/sshd_configfile has the SSH connection over IPV6 disabled by using this setting:

   AddressFamily inet

   Ensure the setting exists, is set properly to inet (not any), and is not commented out.

6. Verify the /etc/sudoers file does not contain this setting or if it does, that it is disabled:

   Defaults requiretty

7. You must disable IPV6 using the following commands:

   sudo vi /etc/sysctl.conf
   
   Ensure that these settings within the /etc/sysctl.conf file are set in order to disable IPV6 protocol:
   
   net.ipv6.conf.default.disable_ipv6=1
   net.ipv6.conf.all.disable_ipv6=1

8. Because DNS is not configured you must ensure that the Fully Qualified Domain Name in the /etc/hostname file does not include the localdomain suffix. For example, if a setting such as this exists in your /etc/hostname file:
   
   sqeweb111.localdomain
   
   You should edit the file to remove the ".localdomain" suffix.
   
9. Use this command to check the status of Security Enhanced Linux (SELINUX):

   sudo getenforce

   If the returned status is either Enforced or Permissive, you must temporarily disable the extra security restriction provided by SELINUX by modifying this file:
   
   /etc/selinux/config
    Edit the /etc/selinux/config file to change the SELINUX=setting to this value: 

   SELINUX=disabled
   

10. You must reboot the machine in order for the change to take affect any time you change the /etc/hostname file or when you change security settings.
    
    After the reboot is complete, run sudo getenforce to confirm that the status of SELINUX is Disabled.
    

    Important: This only needs to be disabled at the time of provisioning. As a recommended best practice, you should re-enable SELINUX after you have successfully completed JD Edwards EnterpriseOne One-Click Provisioning by changing the setting to be either of the following:

    SELINUX=Enforced
    SELINUX=Permissive
    

Disable Firewall Services

You must disable firewall services in order to enable the functionality of the Provisioning Server. Use this command to stop the firewall services:

sudo service firewalld stop

Note: Any time you make a change to the firewall, you must reload firewall rules using this command:

sudo firewall-cmd --reload

Note: You can enable the firewall after One-Click Provisioning completes the deployment. For instructions on how to do so, refer to the companion document entitled: Deploying One-Click Provisioning On Premises with Linux and Oracle Database.

Set Up Users and Groups

Perform these tasks to set up additional users and groups on each Linux server:

1. Create the dba and oracle groups using these commands:

   sudo groupadd -g nnnn dba
   sudo groupadd -g nnnn oracle

   where nnnn is the id value with which the group will be created. You must use a free value which ideally should be above 1000. You can determine used group ids with the id command.
   

2. Create the oracle and opc users and add them to the oracle group using these commands:
   

   sudo useradd -d /home/oracle -m -s /bin/bash -g oracle oracle
   sudo useradd -d /home/opc -m -s /bin/bash -g oracle opc
   

3. Add the oracle user to the dba group using this command:

   sudo usermod -a -G dba oracle

4. Set /u01 as owned by the oracle group using this command:

   sudo chgrp oracle /u01

5. Set the opc user to have passwordless sudo access by adding this entry in /etc/sudoers:

   opc ALL=(ALL) NOPASSWD: ALL

Install Requisite YUM Packages

You must install a specific set of packages from the YUM repository onto the One-Click Provisioning Server and each additional Linux-based Server in the JD Edwards EnterpriseOne environment which include:

• Provisioning Server
• Database Server
• Enterprise Server
• WebLogic Server

The following tables lists the required packages alphabetically (second column) while column 1 contains the YUM install command. This enables you to cut and paste the content of this table into an ASCII editor to create a script to install the packages one at a time, or all at once. In either case, but sure to confirm that when executed each command returns either of these:

Complete
or
Nothing to do

Note: If you choose to run all YUM packages at once, using a single command, you may encounter error conditions where a package may not install as expected due to dependency or other technical issues with the package or library. Further, this behavior is unpredictable and can vary according to system conditions. The resolution of such error conditions is the responsibility of your system administrator and is beyond the scope of this document. If you need help resolving YUM issues, your Linux Admin should open a SR with the Oracle Linux support team. Additionally, various Linux OS images may be delivered with some of these packages already installed by default. You can use the complete list in this table to cross-check which packages may already be installed and those that you will need to manually install.

Important: It is recommended that you run YUM install commands as the root user (sudo su).

 

Provisioning Server

YUM Command and Package

yum install –y bind-utils

yum install –y gcc.x86_64

yum install –y gcc-c++.x86_64

yum install –y ksh.x86_64

yum install –y nmap

yum install –y ruby.x86_64

yum install –y ruby-devel.x86_64

yum install –y samba.x86_64

yum install –y samba-yum install –y client.x86_64

yum install –y unzip.x86_64

yum install –y zip.x86_64

yum install –y zlib-devel.x86_64

 

 

Database Server

YUM Command and Package

yum install –y bind-utils

yum install –y compat-libcap1.x86_64

yum install –y compat-libstdc++-33.x86_64

yum install –y gcc.x86_64

yum install –y gcc-c++.x86_64

yum install –y glibc.i686

yum install –y glibc.x86_64

yum install –y glibc-devel.x86_64

yum install –y ksh.x86_64

yum install –y libaio.x86_64

yum install –y libaio-devel.x86_64

yum install –y libgcc.x86_64

yum install –y libstdc++.x86_64

yum install –y libstdc++-devel.x86_64

yum install –y libX11.x86_64

yum install –y libXau.x86_64

yum install –y libxcb.x86_64

yum install –y libXext.x86_64

yum install –y libXi.x86_64

yum install –y libXtst.x86_64

yum install –y make.x86_64

yum install –y nmap

yum install –y sysstat.x86_64

yum install –y unzip.x86_64

yum install –y zip.x86_64

 

Enterprise Server

YUM Command and Package

yum install –y bind-utils

yum install –y compat-libcap1.x86_64

yum install –y compat-libstdc++-33.i686

yum install –y compat-libstdc++-33.x86_64

yum install –y elfutils-libelf-devel.x86_64

yum install –y file

yum install –y gcc.x86_64

yum install –y gcc-c++.x86_64

yum install –y glibc.i686

yum install –y glibc.x86_64

yum install –y glibc-devel.i686

yum install –y glibc-devel.x86_64

yum install –y ksh.x86_64

yum install –y libaio.i686

yum install –y libaio.x86_64

yum install –y libaio-devel.i686

yum install –y libaio-devel.x86_64

yum install –y libgcc.i686

yum install –y libgcc.x86_64

yum install –y libstdc++.i686

yum install –y libstdc++.x86_64

yum install –y libstdc++-devel.x86_64

yum install –y libX11.i686

yum install –y libX11.x86_64

yum install –y libXau.i686

yum install –y libXau.x86_64

yum install –y libxcb.i686

yum install –y libxcb.x86_64

yum install –y libXext.i686

yum install –y libXext.x86_64

yum install –y libXi.x86_64

yum install –y libXtst.x86_64

yum install –y make.x86_64

yum install –y ncompress

yum install –y nmap

yum install –y sysstat.x86_64

yum install –y unixODBC.x86_64

yum install –y unixODBC-devel.x86_64

yum install –y vunzip.x86_64

yum install –y zip.x86_64

yum install –y zlib-devel.i686

yum install –y zlib-devel.x86_64

WebLogic Server

YUM Command and Package

yum install –y bind-utils

yum install –y glibc.i686

yum install –y glibc.x86_64

yum install –y glibc-devel.x86_64

yum install –y ksh.x86_64

yum install –y net-tools

yum install –y nmap

yum install –y unzip.x86_64

yum install –y zip.x86_64

yum install –y zlib-devel.x86_64

This section describes the setup tasks that must be performed on the Provisioning Server.

Important: These tasks are in addition to those tasks described in All Linux Servers Common Setup.

• General
• Install Requisite GEM Package
• Obtain, Unzip, Assemble, and Extract the Provisioning Server Archive Files
• Run the setupPr.sh Script as the Root User
• Verify Provisioning Console Necessary Services are Running

General

Ensure that there is sufficient storage available on the Provisioning Server for the YUM packages, and the Provisioning Server archive (compressed and extracted).

Install Requisite GEM Package

You must install the winrm program as a GEM package on the Provisioning Server to enable access to the Deployment Server using this command:

gem install -v 1.8.1 -r winrm

Obtain, Unzip, Assemble, and Extract the Provisioning Server Archive Files

Due to file size limitations for files available from the Oracle Software Delivery Cloud (also called E-Delivery), the requisite archive as a single entity cannot be posted. Instead you must download a series of files that have been split into allowable sizes and then assemble them into a single archive, and then extract the contents of that archive using the following procedure. 

1. Download the files for JD Edwards EnterpriseOne One-Click Provisioning from the Oracle Software Delivery Cloud using All Categories and JD Edwards One-Click Provisioning as the search criteria. From the displayed list, choose the combination of JD Edwards EnterpriseOne applications and tools releases and proceed to add the items to your cart.
2. Download the items in your cart.
3. From your download location, upload the files to any directory on the Provisioning Server.
4. Unzip the downloaded files, which will consist of several "zip" files and one (1) integrity check-sum file.
   
   For example, for JD Edwards EnterpriseOne Applications Release 9.2.2 and Tools Release 9.2.2.2, the unzipped files have these filenames:
   • JDE_OCProv_9222_APOL73_18031_73GB.tar.gz.DiskPart00
   • JDE_OCProv_9222_APOL73_18031_73GB.tar.gz.DiskPart01
   • JDE_OCProv_9222_APOL73_18031_73GB.tar.gz.DiskPart02
   • JDE_OCProv_9222_APOL73_18031_73GB.tar.gz.DiskPart03
   • JDE_OCProv_9222_APOL73_18031_73GB.tar.gz.DiskPart04
   • JDE_OCProv_9222_APOL73_18031_73GB.tar.gz_MD5SUMS
     
5. Assemble the unzipped DiskPartnn images into a single archive. Using the above filenames as an example, use this command:

   cat JDE_OCProv_9222_APOL73_18031_73GB.tar.gz.DiskPart* > JDE_OCProv_9222_APOL73_18031_73GB.tar.gz

6. Verify the integrity of the assembled archive by using the md5sums utility with this command:

   md5sum –c JDE_OCProv_9222_APOL73_18031_73GB.tar.gz_MD5SUMS

   If the utility returns OK as shown in the example below, the assembled image is valid and can be deployed:

   JDE_OCProv_9222_APOL73_18031_73GB.tar.gz: OK

   Note: To ensure that you do not run out of disk space on your Provisioning Server in later steps, at this point it is recommended that you delete the archive once you are sure all of the contents were successfully extracted. Alternately, if you have allocated greater than the recommended disk space for your Provisioning Server, you can wait to delete it until you are certain that all components are fully functional.

7. The archive must be extracted by the opc user and it must be extracted to the /u01 directory by preserving the existing permissions using this command:

   tar -P -C /u01 -x -f JDE_OCProv_9222_APOL73_18031_73GB.tar.gz

   Note: Be sure and use the -P switch to preserve permissions, and the -C switch to untar to the specified directory. The extraction process can take quite some time, perhaps as long as 10 to 20 minutes.

8. Once extracted, the /u01 should contain the following components:
   
   

   

Run the setupPr.sh Script as the Root User

As the root user, you must run the setupPr.sh script that was delivered when you extracted the Provisioning Server archive as described in the preceding section. This script automates the remaining required configuration of the Provisioning Server and performs these requisite tasks:

1. Sets up permission and ownership of the extracted content
2. Adds system files such as jdedwards, chkPort, and chkDNS
3. Configures the Samba service
4. Adds the Server Manager Console service
5. Adds Provisioning Console service
6. Creates and configures CA certificates

From the script location on /u01, as the root user, run this command:

./setupPr.sh

Once the command runs successfully, the Provisioning Console should be up and running. You can access the Provisioning Console using a URL with the following syntax:

https://<Public Ip Address>:3000

This section describes the setup tasks that must be performed on the Oracle Database Server.

Important: These tasks are in addition to those tasks described in All Linux Servers Common Setup.

• General
• Prerequisite Configuration for the Oracle Database Server

General

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

1. The database must be installed under the /u01 directory.

   Important: Installing the database on any mount point other than /u01 is not supported; provisioning cannot occur.

2. You must configure the semaphore parameter in the /etc/sysctl.conf file using this command:

   sudo vi /etc/sysctl.conf

   Ensure that this setting exists with the co

   kernel.sem = 1024 32000 100 1024

3. Ensure that sufficient available storage is available on /u01 for the Database Server.
   

   Use this command to view your available storage space on /u01:

   df -h

   where the minimum required space is specified in the section of this document entitled: What Do You Need?

Prerequisite Configuration for the Oracle Database Server

The JD Edwards EnterpriseOne One-Click deployment of the Oracle database supports both Oracle Enterprise Edition and Standard Edition 2 for the current supported release of Oracle Database. Refer to the Oracle Certifications for JD Edwards EnterpriseOne One-Click Provisioning for current updates on supported software versions and software prerequisites. The Certification page can be accessed through the Oracle Support Portal:

https://www.oracle.com/support/index.html

Important: You should have an Oracle DBA monitor the database relative to subsequent JD Edwards functions, such as Package Build. Database aspects such as Archive Logging can adversely affect disk space usage and could potentially cause database failures.

The following prerequisite configuration settings are applicable to a customer-installed Oracle database. These prerequisites must be met before the One-Click Provisioning Server can install a JD Edwards EnterpriseOne Database Server:

• Customer must have an Oracle Database Server instance installed
• Customer must make TNS entry of the pluggable database in the tnsnames.ora file on the Database Server instance (do not use a variable for ORACLE_HOME; it must be an absolute value). The hostname field should be updated with the hostname of the Database Server machine should be udpated with JDEORCL.
• Customer must create and configure a Pluggable Database (PDB) named JDEORCL
• You must install the Oracle database as the oracle user -- not as any other user such as opc.

• Customer must set the database character set to AL32UTF8

• Customer must set the database national character set for the Unicode page setting to AL16UTF16

  Important: The character set parameters are critical and must be set when the database is installed; they cannot be changed after installation.

• Minimum storage requirement for JD Edwards Shared Database is 10 GB
• Minimum storage requirement per pathcode is 20GB (Including demo data)
• Above mentioned storage should be made available for:

• OraDB install directory
• OraDB index directory
• OraDB table directory

• Customer must set the minimum required DB processes to provision the JD Edwards EnterpriseOne Database Server to a minimum value of 1500
• Customer must ensure the Files System IO option is SETALL
• Database must be running with PDB (JDEORCL) set to OPEN_MODE
• Set environment variables for the Oracle Database because by default environment variables for the oracle user are not set

The following is a detailed list of commands necessary to set up the prerequisites for the Oracle Database for use with JD Edwards EnterpriseOne One-Click Provisioning.

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

2. Sudo to the oracle user from the opc user using this command:

   sudo su - oracle

3. Make a TNS entry of the pluggable database in the listener.ora and tnsnames.ora files of the Database Server machine, where  hostname is the hostname of the Database Server machine is jdeorcl. Ensure the same port is also specified in each file. For example:
   
   ----------------
   listener.ora
   ----------------
   LISTENER_ORCL =
   (ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = 1521))
   
   ORCL =
   (DESCRIPTION =
   (ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = 1521))
   (CONNECT_DATA =
   (SERVER = DEDICATED)
   (SERVICE_NAME = jdeorcl)
   )
   )
   -------------------
   tnsnames.ora
   -------------------
   JDEORCL =
   (DESCRIPTION =
   (ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = 1521))
   (CONNECT_DATA =
   (SERVER = DEDICATED)
   (SERVICE_NAME = jdeorcl)
   )
   )
4. Connect to the database using this command:
   

   sqlplus '/as sysdba';

5. Verify the code page setting of the Oracle database using this command:

   SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_CHARACTERSET';

6. If the character set is not AL32UTF8, you will have to reinstall the database using the correct parameter to set it.
7. Verify the Unicode code page setting of the Oracle database by executing this command:

   SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_NCHAR_CHARACTERSET';

8. If the setting is not AL16UTF16, you will have to reinstall the database using the correct parameter to set it.
9. Determine the number of DB processes available using this command:

   select limit_value from v$resource_limit where resource_name='processes';

10. If the value is less than 1500 (which is the minimum recommended for use with JD Edwards EnterpriseOne, run this command to set to the minimum recommended value:

    alter system set processes=1500 scope=spfile;

11. Check the value of the filesystemio_option parameter using this command:

    show parameter filesystemio_options;

12. If the value of the filesystemio_option parameter is not SETALL (which is required), use this command to set it:

    alter system set filesystemio_options=setall scope=spfile;

13. Shutdown the database using this command:

    shutdown immediate;

14. Start the database using this command:

    startup;

15. Verify the databaset is open using this command:

    select OPEN_MODE from v$pdbs where NAME = 'JDEORCL';

    If the pluggable database you want to use is not named JDEORCL, you can issue this command to find the name of available PDBs (ignore PDF$SEED) and substitute that name for JDEORCL in the command above):

    NAME, OPEN_MODE from v$pdbs;

16. If the OPEN_MODE is set to READ WRITE then the PDB is ready to be provisioned by the JD Edwards EnterpriseOne One-Click Provisioning Server.
17. If the OPEN_MODE is not READ WRITE then the PDB is not open. Open the PDB using this command:

    alter pluggable database JDEORCL open;

    The PDB is ready to be provisioned by the JD Edwards EnterpriseOne One-Click Provisioning Server.
18. Use this procedure to set the environment variables for the Oracle Database because by default environment variables for the oracle user are not set.
1. Switch to the oracle user using this command:

   sudo su – oracle

2. Edit the bash_profile using this command:
   
   vi .bash_profile

3. Add the following lines in the .bash_profile:
   
   export ORACLE_HOME=path
   export ORACLE_SID=orcl
   PATH=path
   export PATH
   
   Note: You cannot use an environment variable when defining ORACLE_HOME, such as $ORACLE_HOME. You must use the absolute value.
   
   For example, a properly completed .bash_profile might look like this:
   
   export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
   export ORACLE_SID=orcl
   PATH=$ORACLE_HOME/bin:$PATH:$HOME/.local/bin:$HOME/bin
   export PATH

4. Save and close the .bash_profile file.

5. Execute the .bash_profile file for the variables to take effect.

This section describes the setup tasks that must be performed on the Enterprise Server.

Important: These tasks are in addition to those tasks described in All Linux Servers Common Setup.

The following general prerequisites are required for the One-Click Enterprise Server:

1. Create the oneworld group using this command:

   sudo groupadd -g nnnn oneworld

   where nnnn is the id value with which the group will be created. You must use a free value which ideally should be above 1000. You can determine used group ids with the id command.
   
   Note: You must reboot the machine any time you add groups in order for the changes to take affect.

2. Create the jde920 user and make the shell the default shell (using the -s switch with /bin/ksh), and add it to the oneworld group using this command:

   sudo useradd -d /home/jde920 -m -s /bin/ksh -g oneworld jde920
   
   Note: This specific user, with access to ksh, is required in order to start and stop the Enterprise Server.

3. Add the jde920 user to the oracle group using this command:

   sudo usermod -a -G oracle jde920

4. Ensure there is at least 35 GB free space on /u01.

This section describes the setup tasks that must be performed on the WebLogic Server.

Important: These tasks are in addition to those tasks described in All Linux Servers Common Setup.

• General
• Install a JDK and Oracle WebLogic Server
• Post Installation of WebLogic Server

General

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

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

   groups username

Install a JDK and Oracle WebLogic Server

You must manually pre-install Oracle WebLogic Server (WLS). Customers can then use JD Edwards One-Click Provisioning to deploy the JD Edwards EnterpriseOne web components into that WLS domain. The supported version of WLS is 12.2 Standard Edition or Enterprise Edition.

The complete list of prerequisites are below:

• A supported version of WLS must be pre-installed.
• A supported version of a JDK must be installed.
• WLS must be defined with at least one domain.
• WLS must be in a running state and able to connect to the Admin Console.
• WLS must have a running Node Manager process for the existing domain.
• WLS 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. The node manager machine must be created in the WebLogic Admin server and it must be in reachable state. 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.