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


Options



Before You Begin

Oracle Support

This Oracle By Example (OBE) shows how to prepare for a deployment of JD Edwards EnterpriseOne Release 9.2 On Premises with Microsoft Windows and an Oracle or Microsoft SQL Server Database using One-Click Provisioning. It is important to note that this document is primarily concerned with the basic requirements for an installation of JD Edwards EnterpriseOne. It is not intended as a blueprint for operations in typical environments such as Development, Test, or Production.

Purpose

These topics are covered:

  • Port Restrictions 
  • Create a Pre-Install Worksheet
  • Set Up the Microsoft Windows Servers
    • All Microsoft Windows Servers Common Setup
    • Provisioning Server Setup
    • Oracle Database Server Setup
    • Microsoft SQL Server Database Server Setup
    • Enterprise Server Setup
    • WebLogic Server Setup
    • Deployment Server Setup
  • Provisioning Next Steps

Time to Complete

2-4 hours

Note that this estimate completion time is not the elapsed time. That is, it does not account for machine runtime functions.

Background

You can deploy JD Edwards EnterpriseOne using the JD Edwards One-Click Provisioning Server.

Scenario

JD Edwards EnterpriseOne Release features a One-Click Provisioning Server. This server features a web-based JD Edwards Provisioning Console interface that enables the provisioning of a fully functional suite of interconnected servers. The required core servers are the Database Server, the Enterprise Server, the HTML Web Server, and the Application Interface Service (AIS) Server. The One-Click Provisioning Server includes the JD Edwards Server Manager Console (SMC).

The following servers are deployed by One-Click Provisioning:

  • A single Database Server
  • One or more Enterprise Servers
  • One or more HTML Servers (as standalone instances within WebLogic, not clustered)
  • One or more AIS Servers (as standalone instances within WebLogic, not clustered)
  • A single Deployment Server

Note:  You must have a Deployment Server in order to apply ESUs (updates), perform Package Builds and commit to future upgrades.

Prior to deploying web components using One-Click, users must separately install their own licensed version of WebLogic Server. This document includes the WebLogic prerequisite setup settings for use with JD Edwards EnterpriseOne.

Oracle Software Delivery Cloud

Visit the Oracle Software Delivery Cloud (also called E-Delivery) to download the components required for deploying JD Edwards EnterpriseOne to an On Premises environment. Select All Categories and search on JD Edwards One-Click Provisioning.

If you have questions regarding the download process, please review the Frequently Asked Questions document available from the Oracle Software Delivery Cloud welcome page: Oracle Software Delivery Cloud

Supported Software Versions

The following table lists the supported software versions for Oracle and Microsoft components for deploying JD Edwards EnterpriseOne using One-Click Provisioning On-Premises:

Supported Software Versions

Operating System

·      Provisioning Server

Microsoft Windows Server 2016 Standard   

·      Oracle Database Server

·      Microsoft SQL Server Database Server

·      Enterprise Server

·      Oracle WebLogic Server

·      Deployment Server

Oracle Database

12.2.0.1

Microsoft SQL Server Database

SQL Server 2016

Oracle WebLogic Server

12.2.1.3

Oracle WebLogic Server Patches for 12.2.1.3

p26045997, p27342434

Java Development Kit (JDK) (Required for Oracle WebLogic Server)

Version 1.8.0 CPU update 212 or lower

What Do You Need?

To perform the steps in this tutorial, you must have:

  • You must have the 64-bit version of the zip program 7zip installed on your Provisioning Server in order to unzip the files required to create the Provisioning Server.
  • The table below specifies the minimum resource requirements to install and run JD Edwards. Your environment may require additional resources based on transaction volumes, number of users, availability requirement, integrations, and business requirements.

JD Edwards EnterpriseOne Server Type

Minimum Recommended

Notes

CPU

Memory (GB)

Storage (GB)

Required JD Edwards Components

One-Click Provisioning Server

2

30

100

Includes Server Manager

Deployment Server

2

30

210 GB for all four (4) pathcodes

Using One-Click, customers must install all four (4) path codes. There is no automated way to add additional path codes post deployment.

Oracle Database Server

2

30

50 GB for a single pathcode and shared data

20 GB is required for each additional pathcode

These numbers are for demo data only and should be adjusted for expected required business data space.

SQL Server Database Server

2

30

50 GB for a single pathcode and shared data

20 GB is required for each additional pathcode

These numbers are for demo data only and should be adjusted for expected required business data space.

Enterprise Server

2

30

75

 

WebLogic Server

-

-

30

For the OS and WebLogic Server

·         HTML Server for Web Client

2

30

20

Per Web Instance

·         HTML Server for AIS Server

2

30

20

Per Web Instance

·         AIS Server

2

30

20

Per Web Instance

Optional JD Edwards Components1

 

Business Services Server (BSSV)

2

30

50

Per Web Instance

Transaction Server for Real Time Events (RTE)

2

30

50

Per Web Instance

Application Development Framework Server (ADF)

2

30

50

Per Web Instance

One View Reporting (OVR) Server /  BI Publisher Server (BIP)

2

30

50 GB is required for a single pathcode

10 GB is required for each additional pathcode

Development Client 

2

30

100

Per each Development Client installation

Note: Optional components are not deployed by One-Click. However the Web Components can be manually added through Server Manager and the Development Client can be added in a new Microsoft Windows instance using the traditional on-premise methodology.

Port Restrictions

You should be aware of restricted ports that cannot be defined or used while creating any web component and/or server. These specific port restrictions for any One-Click Provisioning deployment of JD Edwards EnterpriseOne are grouped as follows:

  • One-Click Provisioning Console for JD Edwards
  • All Internet Browsers
  • Google Chrome and Mozilla Firefox Browsers

One-Click Provisioning Console for JD Edwards

Any port below 1024 is restricted.

All Internet Browsers

The following are restricted ports enforced by the rules of any Internet Browser:

  • 2049
  • 4045
  • 6000

Google Chrome and Mozilla Firefox Browsers

In addition to the above mentioned restricted ports for any Internet browser, the Google Chrome and Mozilla Firefox browsers block specific ports which they deem as unsafe to use on HTTP/HTTPS protocol. Below are these restricted ports:

  • 3659, // apple-sasl / PasswordServer
  • 6665, // Alternate IRC [Apple addition]
  • 6666, // Alternate IRC [Apple addition]
  • 6667, // Standard IRC [Apple addition]
  • 6668, // Alternate IRC [Apple addition]
  • 6669, // Alternate IRC [Apple addition]

Note: It may be possible to configure Chrome and/or Firefox to change these restrictions.

Create the Pre-Install Worksheet

A Pre-Install Worksheet is provided in this guide to gather information about your planned installation prior to beginning the deployment of the One-Click Provisioning Server. Using this worksheet decreases the chances for data entry errors and makes for a documented and repeatable process.

The Pre-Install Worksheet that you create as part of the tutorial is a record of the server names assigned during the installation; you must use those exact server names throughout the process.

Important: Some environments will allow multiple servers to start using the same hostname, but network traffic is unpredictable. You can avoid this potential issue by choosing your own unique hostnames for each server instance.

For any Windows server accessed by JD Edwards EnterpriseOne, machine names are limited to a maximum of 15 UPPER-CASE alphanumeric characters as limited by the JD Edwards EnterpriseOne database table and application design. You cannot use special characters in the name, with the exception of a hyphen “-”, which is allowed.

If the existing hostname does not conform to these requirements, runtime of JD Edwards EnterpriseOne will fail. If a hostname does not conform to these restriction, you should permanently change the hostname for your system.


Pre-Install Worksheet

Machine

IP Address

Provisioning Server and Server Manager (same machine)

https://___.___.___.___:3000

 

where https is the only supported browser protocol, and

where 3000 is always the port, which you must include as part of the address

Machine

Hostname

Database Server

 

Enterprise Server

 

HTML Server

 

AIS Server

 

Deployment Server

Hostname: _______________________________________

Location Name: 

Warning: Use a fully qualified domain name for hostname if DNS is enabled. Otherwise you should only specify the first node of the domain name.

Machine names are limited to a maximum of 15 lower-case alphanumeric characters as limited by the JD Edwards EnterpriseOne database table and application design.

You cannot use special characters in machine name, with the exception of a hyphen “-”, which is allowed. The user interface will enforce this restriction.

User Account

Password



sys, system

 

weblogic

 

JDE

 

jde_admin

 

Initial Microsoft Windows Machine Administrator (temporary)

 

Site Key Passphrase

 

Server Manager Console

 

Warning - Special Password Restrictions

Microsoft Windows.
The password for any Windows user on any Windows machine can only include these special characters:
_ @ ~ ! # % * + ( ) { } [ ] . ?

Oracle Database. The password for the database users of an Oracle database in an Oracle Cloud Infrastructure Compute instance can only include these special characters: _ # -

SQL Server Database.  The password for the database users of a SQL Server database in an Oracle Cloud Infrastructure instance can only include these special characters: _ @ ~ + - *

WebLogic Servers. The password for the WebLogic servers in Compute cannot contain these characters: $ or !

Set Up the Microsoft Windows Servers

This chapter contains these sections:

  • All Microsoft Windows Servers Common Setup
  • Provisioning Server Setup
  • Oracle Database Server Setup
  • Microsoft SQL Server Database Server Setup
  • Enterprise Server Setup
  • WebLogic Server Setup
  • Deployment Server Setup

All Microsoft Windows Servers Common Setup

These sections describe the setup tasks which must be performed on each JD Edwards EnterpriseOne server:

  • General
  • Run Commands to Change Microsoft Windows Settings
  • Enable Inbound Ports in the Firewall
  • Enable Outbound Ports in the Firewall
General
  1. Ensure that hostname for the server contains only alphanumeric values. Special characters are not allowed, with the exception of a hyphen “-”, which is allowed. Refer to the section of this guide entitled: Special Naming Restrictions.
  2. All servers in provisioning cycle must be configured with same Microsoft Windows user name and credentials, where the user name must be opc. This common user must have administrator rights.; that is, it must be part of the Administrator group.

    Note: JD Edwards EnterpriseOne One-Click Provisioning specifically supports only these special characters for Windows user passwords:

    _@~!#%*+(){}[].?

  3. If you change the password on any single machine in the provisioning cycle, you must likewise change the password on all other machines in with the new password and reboot the Provisioning Server to recognize those changes.
Run Commands to Change Microsoft Windows Settings

This section provides the commands that you must run to change these Microsoft Windows settings to enable One-Click Provisioning:

  • Enable Remote Command Execution Through PowerShell
  • Enable Inbound Ports in the Firewall
  • Enable Outbound Ports in the Firewall
  • Change Security Option
Enable Remote Command Execution Through PowerShell

From PowerShell, use this command to enable remote command execution:

winrm quickconfig –q

Enable Inbound Ports in the Firewall

If you have the Microsoft Windows firewall enabled for any profile (public, private, default), which is recommended, in order for One-Click Provisioning to deploy to the Deployment Server in the Microsoft Windows instance in Oracle Cloud Infrastructure and for JD Edwards EnterpriseOne runtime to function properly, you will need to explicitly open Inbound and Outbound ports.

Use this procedure to open the Inbound ports for each Microsoft Windows instance.

  1. Go to Administrative Tools > Windows Firewall with Advanced Security.
  2. In the left pane, highlight Inbound Rules.
  3. In the right pane, Actions, Inbound Rules, click New Rule …
  4. On Rule Type, select the Port radio button as the type of rule to create.
  5. Click the Next button.
  6. On Protocol and Ports:
    • You can accept the default value of TCP for the protocol to which this rule applies.
    • Choose the radio button for Specific local ports and, for each Windows Server, enter each of the ports shown in the following table, separated by a comma.

    • Windows Server Firewall Port List

      Component

      Inbound Ports to Open

      Provisioning Server

      445

      3000

      3389

      5150

      5985

      8998-8999

      7000-7001

      14501-14502

      Database Server

      445

      3389

      5150

      5985

      <DB_PORT> Note: For SQL Server database, this is the value the user provides using the Provisioning Console.

      14502-14510

      Enterprise Server

      445

      3389

      5150

      5985

      6017-6022

      14502-14510

      Web Server

      445

      3389

      5150

      5985

      <WLS_ADMIN_PORT> See Note 1

      <SSL_ACCESS_PORT> See Note 2

      <SSL_ACCESS_PORT-1> See Note 3

      14502-14520

      Deployment Server

      445

      3389

      5150

      5985

      6017-6022

      14502-14510


      Note 1: This is the Admin Port on which the Admin Server is running. This value is set by the user while creating a WebLogic domain.

      Note 2: This SSL port must be opened to enable the Server Manager Console to complete the tasks.

      Note: 3: This port number is equal to value of the SSL port minus one. This port must be opened to enable the Server Manager to complete the provisioning tasks. For example, if you have specified the port value as 8081 in the One-Click Provisioning Console, you must open 8080 port (8081-1).


      Also, you must open a port for each of the WebLogic Servers on Oracle Cloud Infrastructure. For example, if you have the following environments and server combinations, you should open eight ports: four ports for SSL for the port numbers specified by using the Provisioning Console, and four ports for non-SSL. The value of the ports for non-SSL should be the value of the SSL port minus one.

      • DV HTML
      • PD HTML
      • DV AIS
      • PD AIS

        The following example shows the ports you should specify for the Provisioning Server, where the complete list is truncated by the visible input field.

      Example: Troubleshooting nslookup
      Windows Firewall - Inbound Ports
    • Click the Next button.
    • On Action, you can accept the default value which is Allow the connection.
    • Click the Next button.
    • On Profile, select all firewall profile options (Domain, Private, Public).
    • Specify a name for the rule. For example, JDESMC_RDP
    • Click the Finish button to save the rule and exit the wizard.
Enable Outbound Ports in the Firewall

If you have the Microsoft Windows firewall enabled for any profile (public, private, default), which is recommended, in order for One-Click Provisioning to deploy to the Deployment Server in the Microsoft Windows instance and for JD Edwards EnterpriseOne runtime to function properly, you will need to explicitly open Inbound and Outbound ports.

Use this procedure to open the Outbound ports in your Microsoft Windows instance.

  1. Go to Administrative Tools > Windows Firewall with Advanced Security.
  2. In the left pane, highlight Outbound Rules.
  3. In the right pane, Actions, click New Rule …
  4. On Rule Type, select the Port radio button as the type of rule to create.
  5. Click the Next button.
  6. On Protocol and Ports:
    1. You can accept the default value of TCP for the protocol to which this rule applies.
    2. Choose the radio button for All remote ports.
  7. Windows Firewall - Outbound Ports
    Windows Firewall - Outbound Ports
  8. On Action, you can accept the default value which is Allow the connection.
  9. Click the Next button.
  10. On Profile, select all firewall profile options (Domain, Private, Public).
  11. Specify a name for the rule.
  12. Click the Finish button to save the rule and exit the wizard.
Change Security Option

If you chose a user other than opc when for the One-Click Provisioning deployment of your Deployment Server, use this procedure to change the Microsoft Windows security option so that user will be recognized by JD Edwards EnterpriseOne.

  1. Log in to the Deployment Server as the user you configured, which is other than the opc user.
  2. Open the Microsoft Windows Local Security Policy program from Start > Run, or from a Command Prompt:

    secpol.msc

  3. On Local Security Policy, navigate to Local Policies > Security Options.
  4. Locate and edit this setting:

    Network Security: LAN Manager authentication level

  5. Use the pulldown to select this setting:

    Send NTLM V2 response only

    Local
                          Security Policy
    Local Security Policy
  6. Click the Apply button to save the setting.

Provisioning Server Setup

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:

    Example: Successful Extraction of the Windows Archive for the Provisioning Server
    Example: Successful Extraction of the Windows Archive for the Provisioning Server
  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.

Oracle Database Server Setup

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
Ensure that sufficient available storage is available on the Database Server. The minimum recommended value is 50 GB as 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.

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
These are the directories that you will specify during Orchestration.

Important: Best practice is to use different mount points for creating these directories. Otherwise you may encounter database deployment issues.

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

Microsoft SQL Server Setup

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.

SQL Server Default Instance
SQL Server Default Instance

Enterprise Server Setup

  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.

WebLogic Server Setup

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
You must enable command execution through PowerShell.
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.

Deployment Server Setup

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

Provisioning Next Steps

Refer to the companion Oracle by Example (OBE) documents for Deploying:

These documents describes these tasks:

  • Access the JD Edwards Provisioning Console
  • Orchestrate Using Quick Start Mode
  • Orchestrate Using Advanced Mode
  • Orchestrate Using Advanced Mode to Adding Web Servers and Enterprise Servers Post Deployment
  • Deploy an Orchestration
  • Export and Import a Deployment Plan
  • Complete Post Installation for the Deployment Server
  • Complete Post Installation for the Standalone Deployment Server
  • Complete Post Installation for the Enterprise Server
  • Complete Post Installation for the Development Client
  • Obtain and Install CA Certificates in Oracle WebLogic Servers and the Deployment Server
  • Access the JD Edwards EnterpriseOne Servers Using Their Public IP Address
  • Complete Post-Provisioning Tasks
  • Troubleshooting

Want to Learn More?

Refer to the companion tutorial entitled: Deploying JD Edwards EnterpriseOne Release 9.2 Using One-Click Provisioning On Premises with Microsoft Windows. In this tutorial you will how to:
  • Configure your Server Manager Account
  • Orchestrate and Deploy a Quick Start Deployment Plan
  • Orchestrate and Deploy an Advanced Deployment Plan

Refer to the companion Oracle by Example (OBE) document entitled: Administering Your JD Edwards EnterpriseOne Release 9.2 One-Click Deployment. This document provides information on these topics:

  • Start or Stop Services
  • Configure Public IP Address/Internal Hostname on Client Machine
  • About JD Edwards EnterpriseOne Security
  • AIS Server Post Provisioning Configuration
  • Access the Oracle Traffic Director (OTD)
Server Manager for JD Edwards EnterpriseOne is a web based application used to manage the complete life cycle of the JD Edwards EnterpriseOne server products. Refer to the JD Edwards EnterpriseOne Tools Server Manager Guide.

The JD Edwards EnterpriseOne Tools Security Administration Guide contains comprehensive instructions and recommendations for setting up a secure EnterpriseOne environment. It contains pre- and post-installation security considerations, as well as instructions on how to use EnterpriseOne security applications to ensure only authorized individuals have access to EnterpriseOne applications, features, and data. This guide also contains instructions on using security certificates.

Refer to the JD Edwards EnterpriseOne Applications Release 9.2 Installation Guide for Oracle on UNIX for more information on these topics:

  • Working with Installation Planner for an Install
  • Working With Installation Workbench
  • Copying an Environment to Another Environment
  • Adding a Server to an Existing Configuration
  • Understanding JD Edwards Environments and their Relationship with the Database
For more information regarding the One-Click Provisioning integration with the Oracle Enterprise Manager, refer to these resources:
Back to top