Preparing for a Deployment of JD Edwards EnterpriseOne On Premises on Microsoft Windows

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 Windows Servers Common Setup.

• General
• Obtain, Unzip, Assemble, and Extract the Provisioning Server Archive Files and Run the setupPr.ps1 Script

General

1. As specified in the Before You Begin section, ensure you have a 64-bit version of 7zip installed on the Provisioning Server.
2. Ensure that sufficient available storage for the Provisioning Server and the archive (compressed and extracted). Note that the recommended tool for extracting the archive is 7-zip.  
3. Ensure that Ruby 2.5.3 64-bit is installed as Administrator on the Provisioning Server. To obtain the code, refer to this link:
   
   https://rubyinstaller.org/downloads/
   
   
4. Ensure that Ruby is added to PATH environment variable.
5. Ensure that winrm is installed on the Provisioning Server.
   
   Open a command prompt window and ensure this command runs:
   
   gem install –v 1.8.1 –r winrm -f

   Note: Ensure your version of winrm is 1.8.1. Other versions of winrm are not supported in Oracle Cloud Infrastructure.

   It is possible that when the requisite RubyGems program is installed it delivers the latest winrm 2.2.3 version. In this case, the newer version must be uninstalled. Use this command to determine the version of winrm on your Microsoft Windows instance:

   gem list --local winrm

   If the return code displays as below, it indicates that multiple versions of winrm exist.

   retCode: 0 output: winrm (2.2.3, 1.8.1)

   Because only version 1.8.1 is supported, if there are multiple versions installed, you must uninstall the other versions. For example, to uninstall winrm version 2.2.3, use this command:

   gem uninstall winrm --version 2.2.3

6. Ensure that Microsoft Visual C++ 2017 Redistributable 32-bit is installed. To obtain the code, refer to this link;
   
   https://aka.ms/vs/15/release/vc_redist.x86.exe
   
   
7. Ensure that Microsoft Visual C++ 2012 Redistributable 32-bit is installed. To obtain the code, refer to this link:
   
   https://www.microsoft.com/en-us/download/details.aspx?id=30679

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 for Microsoft Windows and proceed to add the items to your cart. You should select the highest level of the combination of applications and tools releases which are prefaced with REL. For example:
   
   REL: JD Edwards One-Click Provisioning 3.1 for Apps 9.2 Tools 9.2.2.4
   
   
2. Click on Selected Software and then use the pull-down for JD Edwards One-Click Provisioning to choose Microsoft Windows.
3. To continue, review and agree to the license agreement.
4. A list of available download files is shown.  For example, for JD Edwards EnterpriseOne Applications Release 9.2.2 and Tools Release 9.2.2.4, you should locate files similar to these:
   
   V975784-01.zip
   V975785-01.zip
   V975786-01.zip
   V975787-01.zip
   V975788-01.zip
   V975789-01.zip
   V975790-01.zip
   V975850-01.zip
5. Download the items in your cart.
6. Using Windows Remote Desktop (RDP), connect to the Provisioning Server and upload the items you obtained from E-Delivery.
7. Using only the 7zip program (64-bit version), which is a prerequisite as specified in Before You Begin, unzip all the downloaded files.
8. At this point you must either delete or move the original Vxxxxxxx.zip files in this directory. This is because a subsequent batch process will process the unzipped files and extract additional .zip files to be used for reassembly. As part of the reassembly process it will inventory all the .zip files in this directory for processing, which cannot include the original Vxxxxxx.zip files or else it will fail on checksum verification.
9. From a Command prompt, run  rebuild.bat to unzip all the downloaded parts, reassemble them into a single file, and execute a checksum to ensure the reassembled single file is not corrupted. The batch file also checks to ensure the required zip program for unzipping, which is 7zip, is installed. If 7zip is not installed an error message is displayed and the batch file is terminated.
   
10. If the extraction and reassembly and checksum complete successfully, you should receive a message similar to this:
    
    

    

11. The recombined archive file will have a name similar to this:
    
    JDE_OCProv_9224_WINDOWS_18031_25GB
    
    
12. From the location specified when the rebuild.bat was run, for example, C:\JDE\PP, open Windows PowerShell as Administrator and run this command:
    
    .\setupPr.ps1
    
    Note: The setupPr.ps1 script automates the remaining required configuration of the Provisioning Server and performs these requisite tasks:
• Sets up permission and ownership of the extracted content
• Adds system files such as jdedwards, chkPort, and chkDNS
• Configures the Samba service
• Adds the Server Manager Console service
• Adds Provisioning Console service
• Creates and configures self-signed certificates
  

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

14. The Provisioning Server image is now ready for use by One-Click Provisioning as described in the OBE for Deploying One-Click Provisioning.
    
    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 original downloaded archive files 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.
    

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 Microsoft Windows Servers Common Setup.

• General
• Prerequisite Configuration for the Oracle Database Server

General

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.

Important: If you choose to use your own Oracle Database for the Database Server, 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.
  
  Important: The password for the database users of an Oracle database in an Oracle Cloud Infrastructure Compute instance can only include these special characters: _ # -
• 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 and service name 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 both Oracle Database because by default environment variables for the oracle user are not set.

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 775 /u01
   
   
2. Using sudo, change 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 and the service name 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. Assuming your pluggable database is named JDEORCL, verify it 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;

    where you if your database is named not JDEORCL, substitute that name in the above command.
    
    
18. Log in to the database using this command: sqlplus sys/<DB_ADM_PWD>@<CONTAINER_SID>as sysdba; For example, sqlplus sys/Jde_Admin1@orcl as sysdba;
19. Set the recovery space using this command:
    
    sql> ALTER SYSTEM SET db_recovery_file_dest_size=50G SCOPE=BOTH;
    
    The PDB is ready to be provisioned by the JD Edwards EnterpriseOne One-Click Provisioning Server.

Because this release of One-Click does not support Named Instances for SQL Server, as shown below you must select the Default instance radio button when you are setting up a SQL Server instance.

1. Ensure that sufficient available storage for the Enterprise Server. The minimum recommended values is 50 GB as specified in the section of this document entitled: What Do You Need?
2. Enable Remote Command Execution Through PowerShell by using below PowerShell command:

   winrm quickconfig –q

3. In order to enable Server Package Builds, you must install Visual studio 2013 or 2017 and Microsoft Software Development Kit (SDK) for Windows 8.1.

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 Microsoft Windows Servers Common Setup.

• General
• Install a JDK and Oracle WebLogic Server
• Post Installation of WebLogic Server
• Ensure WebLogic Server is Patch Current

General

Install Oracle WebLogic Server and a JDK

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

Important: The same user must be used to install WLS and the JDK for WLS.

Customers can then use JD Edwards One-Click Provisioning to deploy the JD Edwards EnterpriseOne web components into the pre-installed WLS domain.

The complete list of prerequisites are below:

• A supported version of WLS must be pre-installed.
  
  Important: The password for any WebLogic Server user cannot contain the $ or ! character. Using this character violates the Oracle Cloud password policy and will result in denied access.
• A supported version of a JDK must beinstalled.
• 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.

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
   

   Note: If the node manager machine is not in a reachable state:

1. Log into the WebLogic Server Admin Console.
2. Expand Environment
3. Click on Machines
4. Select your machine
5. Click on the Node Manager tab and make sure Type is set to Plain.
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.

To prepare your Microsoft Windows Deployment Server for orchestration and deployment of JD Edwards EnterpriseOne using One-Click Provisioning, you must enable remote command execution through PowerShell using the following PowerShell command:

winrm quickconfig –q