This chapter contains these topics:
Section 4.1, "Downloading Software from the Oracle Software Delivery Cloud,"
Section 4.4, "Installing JD Edwards World Service Enablement,"
The Oracle Software Delivery Cloud is the preferred delivery mechanism for JD Edwards World software components.
For detailed installation instructions, refer to the JD Edwards World Quick Installation Guide.
This section describes how to install and configure the JD Edwards World Base product and additional components securely. Overall recommendations in this guide should be considered when following the Quick Installation Guide.
The base product is written mainly in RPG and processes on the IBM i. Oracle delivers JD Edwards World via download from the Oracle Software Delivery Cloud or DVD. The setup.exe does the transfer, it is not something the customer does manually. After the software is successfully transferred to the IBM i, you must securely archive or remove any Windows-based copies.
Before configuring the JD Edwards World Base product's security configuration, you should determine the overall security approach and be prepared to configure necessary features of IBM i security along with the JD Edwards security.
During the installation, three IBM User Profiles are created or modified for use during the installation: JDE, JDEINSTAL, and JDEPROD. In the past, these profiles were created with passwords that matched the user ID. Beginning with JD Edwards World release A9.3, you must supply a password for each if the profile does not already exist on your machine. These profiles are for the following purposes:
JDE – This is the user account that will own the installed objects.
JDEINSTAL – This is the user account to use when configuring the install.
JDEPROD – This is a sample production JD Edwards User. You may keep it after the install.
After installation and configuration, disposition of these profiles is as follows:
JDE – This profile typically owns the installed objects and it is used to sign into the pristine environment. Keep it, but disable it from signon.
JDEINSTAL – Disable it.
JDEPROD –The IBM Profile will be disabled from signing on by default.
For detailed installation instructions, refer to the JD Edwards World Web Enablement Installation and Configuration Guide.
This section describes how to install and configure the JD Edwards World Web Enablement securely. Overall recommendations in this guide should be considered when following the Web Enablement Installation and Configuration Guide.
JD Edwards World Web Enablement components are installed and run on the IBM i or on a Windows server running an HTTP server such as Apache. Oracle recommends that you install the HTTP server on a computer system that has restricted access, both physically and through the network.
For detailed installation instructions, refer to the JD Edwards World Service Enablement Installation and Configuration Guide. Overall recommendations in this guide should be considered when following the World Service Enablement Installation and Configuration Guide.
JD Edwards World Service Enablement components are installed and run on the Oracle WebLogic Server. Oracle recommends that you install the Oracle WebLogic Server on a computer system that has restricted access, both physically and through the network. Detailed Oracle WebLogic security practices are discussed in the Oracle Fusion Middleware Understanding Security for Oracle WebLogic Server guide.
For detailed installation instructions, refer to the JD Edwards World JDBC Driver Guide.
The World JDBC driver components are installed on any Windows platform or on an IBM i system and can be used in support of JD Edwards World Service Enablement, Oracle BI Publisher, or any application that needs to read JD Edwards World business data. The World JDBC driver uses your existing World security setup to secure the files and data that it accesses. In most cases, the existing World security setup is all that is necessary to secure the specific features provided by the JDBC driver. Specifically, the following existing security setup features are leveraged by the World JDBC driver:
Use IBM i security to identify and secure users and IBM i system objects, such as specific libraries and files.
Use JD Edwards World users, groups, and environments to control access to specific libraries and files.
Use business unit security to limit rows to specific business units in all files.
Use action code security to manage which SQL statements may be used against the database.
Use column security to manage which specific tables and columns may be queried or updated.
By default, any user who can log into JD Edwards World may use the JD Edwards JDBC driver to read data from JD Edwards data files.