Upgrading Third-Party Components
| Product | Deployment Servers (Windows Only) | Enterprise Servers (Windows, Linux, or Unix) | Development Client (Windows Only) |
|---|---|---|---|
| Java Runtime Environments (JREs) | Yes | Yes | Yes |
| Java Development Kit (JDK) | Yes | No | Yes |
| Database clients and drivers | Yes | Yes | Yes |
| Java Database Connectivity (JDBC) drivers | Yes | Yes | Yes |
| Microsoft Visual Studio Runtime libraries | Yes | Yes (Windows servers only) | Yes |
| Microsoft Visual Studio | Yes | Yes (Windows servers only) | Yes |
| Unix Compilers | No | Yes | No |
| Database | Yes | No | Yes |
| WebLogic Application Server (WLS) | No | No | Yes |
| WebSphere Application Server (WAS) | No | No | Yes |
Java Runtime Environment (JRE) and Java Development Kit (JDK)
A JDK provides tools to compile Java source files and to generate JAR files containing Java class files. Java-based programs run within a JRE. A JRE provides files that are necessary at runtime such as dynamic-linked Libraries (DLLs on Windows, shared libraries on UNIX platforms, and JAR files that contain compiled Java class files. If a JDK is installed, a JRE does not need to be installed separately because a JDK already contains a JRE. A WLS application server requires a JDK to be installed prior to the installation of WLS. A JDK is provided with a WAS installation.
The EnterpriseOne foundation included in a client package contains a JRE that is used
on the Development Client. The bitness of the JRE should match the bitness of the
foundation. To include a new JRE in a package, replace the JRE in the
system/jre folder on the Deployment Server before building the
package; be sure that the package includes the proper foundation.
Downloading
Click the following URL to download the JDK:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
- Under Java Platform, Standard Edition, you can download the JDK or JRE, depending on the particular EnterpriseOne component (Server Manager Console or Agent, Development Client, or Enterprise Server) for which the JDK or JRE is to be used. Each JDK includes a JRE. Some EnterpriseOne components require a JDK, but others require a JRE only. Do not use any non-supported version or edition of the Java JRE or JDK.
- Follow the navigation aids to download the JDK or JRE that is appropriate for your operating system.
- Follow the installation instructions that are provided with the JDK or JRE.
Verifying on UNIX
-
Access the command line of the operating system and enter:
cd <JDK_or_JRE_install_dir>/bin java -version -
Verify that the output shows the version that you downloaded.
Database Client and Drivers
The database client is used by EnterpriseOne on the Deployment Server, Enterprise Servers, and Development Clients to connect to databases. The database client must be at the same or lower release level as the database to which it is connecting. In addition, the database client must be of the same bitness as the EnterpriseOne foundation on the Deployment Server, Enterprise Server, or Development Client.
Download and install the database client of the proper bitness from the database vendor onto the proper EnterpriseOne platform.
If both 64-bit and 32-bit Oracle database clients exist on either a Deployment Server or a Development Client, the Windows operating system will find the proper database client DLLs based on the bitness of the EnterpriseOne system or foundation that is running.
ODBC Data Source Drivers
The ODBC database driver (64-bit or 32-bit) is used to connect to databases from each of the database vendors that EnterpriseOne supports: Oracle, SQL Server, and UDB. If ODBC data sources are used, their drivers and definitions may need to be updated to allow EnterpriseOne Deployment Server and Development Clients to connect to databases. The main reason for updating the ODBC data sources after they have been created is to change the bitness of the EnterpriseOne software.
The Development Client installer automatically handles the task of setting up ODBC data sources when a package is installed.
Before installing a 64-bit package on a Development Client, you must ensure that the 64-bit version of the database vendor’s ODBC driver exists. For example:
C:\Windows\System32\cwbodbc.dll
or
C:\Windows\System32\sqlsrv32.dll
JDBC Database Drivers
JDBC database drivers are copied to Development Clients when web clients (WLSH4A for WebLogic Server or WASH4A for WebSphere Application Servers) are installed on those Development Clients. These JDBC drivers must be updated to reflect the bitness of EnterpriseOne foundation on the target Development Client.
By default, the JDBC database drivers are copied from one of these directories, depending on the H4A installed to be run (WebLogic Server or WebSphere Application Server):
<EnterpriseOne_dep_svr_install_directory>\OneWorld
Client Install\WebDevFeature\WLSH4A\JDBCWebSphere Application Server
<EnterpriseOne_dep_svr_install_directory>\OneWorld Client
Install\WebDevFeature\WASH4A\JDBCMicrosoft Windows Development Tools and Libraries
Either Visual Studio (VS) or Visual Studio Runtime libraries must be installed on each Microsoft Windows platform. VS must be installed if you want to build (compile and link) EnterpriseOne business functions on the Windows platform. If you do not want to build EnterpriseOne business functions on a given Windows platform, instead of VS, install the Runtime libraries.
Microsoft Visual C Runtime libraries
Visual C++ Runtime libraries are dynamic-link libraries (DLLs) provided by Microsoft and are required by EnterpriseOne programs to run on Windows operating systems. The major release number of the runtime libraries that are installed on a Windows computer must match the major release number with which the EnterpriseOne software was built. The EnterpriseOne system or foundation and the business functions for 9.2.3.x were built with Visual C++ 2017 Runtime libraries. Runtime libraries for 2017 Visual C++ 2017 Runtime libraries must be installed on the computer system for EnterpriseOne to run.
Additionally, the bitness of the runtime libraries must match the bitness of the EnterpriseOne software that is running. Even though a Windows operating system may be 64-bit, programs of both 64-bit and 32-bit can run on the computer. You cannot mix 64-bit and 32-bit executables and DLLs in a running process space for a single program.
Windows operating systems come with certain releases of Visual C++ Runtime libraries (64-bit and 32-bit). If a given release of Windows does not include the Visual C++ Runtime libraries necessary by EnterpriseOne Deployment Server, Enterprise Server, or Development Client (either foundation or business functions), the proper Visual C++ Runtime libraries must be installed before installing EnterpriseOne.
The installers for the Visual C++ Runtime libraries are both release and bitness specific. These installers can be downloaded from the Microsoft Download Center and installed on EnterpriseOne Deployment Servers, Windows Enterprise Servers, and Development Clients. The EnterpriseOne Development Client installer requires the same release and bitness of Visual C++ Runtime libraries that the EnterpriseOne foundation uses. The Visual C++ Runtime libraries of the correct release and bitness must be installed prior to running the Development Client installer. However, the Development Client installer can install Visual C++ Runtime libraries of a different release but the same bitness as the EnterpriseOne business functions. This installation can be performed by adding a feature to the installable EnterpriseOne package that runs the Visual C++ Runtime installer.
Microsoft Visual C Runtime Libraries
Microsoft Visual Studio is used to build and debug EnterpriseOne business functions. Building can be performed on either a Deployment Server or Development Client. Debugging of business functions, however, is supported only on Development Clients.
To ensure that the proper instance of Visual Studio is used during an EnterpriseOne build or a debugging session, follow these steps:
- Install the version of Visual Studio specified in Oracle Certification.
- Ensure that the following
jde.inisetting indicates the proper version of Visual Studio:[JDE_CG] VisualStudioVersion=2017
jde.ini file referred to above is in
the C:\Windows directory of the Deployment Server or Development
Client in which the build or debugging will be performed.UNIX and Linux Development Tools and Libraries
See: JD Edwards EnterpriseOne 9.2.X Platform and Compiler Support Statement (Doc ID 2059885.1)
Application Server
During the development of an EnterpriseOne application, an EnterpriseOne developer can run and test the application in a web browser. An application server is used to produce the EnterpriseOne application objects (forms, buttons, and so on) that are displayed in the browser. The application server can be either WLS (from Oracle) or WAS (from IBM); however, as a best practice, all Development Clients installed from a given Deployment Server should use the same type of application server (WLS or WAS).
WebLogic Server
WebLogic Server is a Java Application Server developed by Oracle. It can be installed on an EnterpriseOne Development Client and used to process requests from a Development Client’s web client. WebLogic Server needs to be installed on a Deployment Server only if EnterpriseOne Server Manager Console is to be installed in the Deployment Server.
See the Oracle Certifications information to determine which JDK to use for WebLogic Server. You must install the JDK before installing WebLogic Server.
WebSphere Server
WebSphere Server is not used internally for EnterpriseOne development.
WebSphere Server is a Java Application Server developed by IBM. It can be installed on an EnterpriseOne Development Client and used to process requests from a Development Client’s web client. WebSphere Server needs to be installed on a Deployment Server only if EnterpriseOne Server Manager Console will be installed there as well.
See the Oracle Certifications information to determine which JDK to use for WebSphere Server. You must install the JDK before installing WebSphere Server.