Resources and Required Components

This page lists down resources that discuss required components for installation and configuration of EnterpriseOne, Oracle Software Delivery Cloud, and the resources required for upgrading only the Tools release.


Required Components

The components listed in the Required Components documents are necessary for the installation and configuration of JD Edwards EnterpriseOne Tools 9.2.x with JD Edwards EnterpriseOne Applications 9.2, 9.1, and 9.0.

Install the components in the order shown using the JD Edwards EnterpriseOne Installation reference guides that support the Tools 9.2.x release.

The Required Components documents also provide information on additional ESUs that need to be applied to your system to support any new features and functionality that require an Applications component.

Required Components Documents


Oracle Software Delivery Cloud

Visit the Oracle Software Delivery Cloud to download Oracle software products. If you have questions regarding the download process, please review the Frequently Asked Questions document available from the Oracle Software Delivery Cloud welcome page.

For information on how to locate and download JD Edwards EnterpriseOne 9.2 files from the Oracle Software Delivery Could, see the How to Download JD Edwards 9.2 Setup File From New Oracle Software Delivery Cloud Website document located on My Oracle Support.

Oracle Software Delivery Cloud


Tools Only Upgrade Resources

The resources available under this tab support the upgrading of your EnterpriseOne Tools release while maintaining the same Applications release.

There are some significant changes in Tools Release 9.2 that impact your Tools Only Upgrade. Please review the changes described on the pages available under this tab before beginning the upgrade process.

Before you begin a Tools Only Upgrade, download Change Assistant:

Change Assistant

Documentation

Quick Tours

Tools Only Upgrade Resources

Objects in the Database

Tools 9.2: Objects reside in a file system.

Tools 9.2.1: Objects are inserted into the database. This enhancement inserts all object librarian type records into a database repository. This repository will be the source of truth for JD Edwards objects.

Action: Run UBE (R98MODAT) to copy media objects to the database. For more information, see:


Tools Release

Tools 9.1: Tools release is installed using Install Manager.

Tools 9.2: Tools release is installed using Server Manager.

Action: You must install a Server Manager Agent on the Deployment Server.

You must register the Deployment Server with Server Manager.

Use Server Manager to deploy a Tools Release as a software component in the same manner as you would use other JD Edwards EnterpriseOne servers, such as Enterprise Servers and HTML Servers. For more information, see Using Server Manager to Install the Tools Release in the JD Edwards EnterpriseOne Applications Upgrade Guide.


Microsoft Visual studio

Tools 9.1: Microsoft Visual Studio runtime libraries are bundled with the installer; these libraries are used by EnterpriseOne Tools.

Tools 9.2: Microsoft Visual Studio runtime libraries are not bundled with the installer. These libraries are required for EnterpriseOne Tools and EnterpriseOne Applications as described below.

Action: Ensure that you have these required 32-bit versions of Microsoft Visual Studio installed:

  • VS/2010 runtime for EnterpriseOne Tools

    This version of Visual Studio may already be installed on some systems. You can determine if this version exists on your system by accessing Control Panel > Programs and Features > Microsoft Visual Studio C++ 2010 x86 Redistributable.

For more information, see Working with Microsoft Windows Visual Studio and Windows SDK in the JD Edwards EnterpriseOne Applications Upgrade Guide.


Local Oracle Database Enhanced Encryption

Tools 9.1: Reconfiguremsde.exe is the utility that encrypts/decrypts the local database user password.

Tools 9.2: ReconfigureDB.exe is the utility that encrypts/decrypts the local database user password.

Starting with EnterpriseOne Tools Release 9.2.0.0 using an Oracle local database, the method of creating passwords has changed. The previous method is referred to as using Legacy encryption; by contrast, the new method uses Enhanced encryption.

Enhanced encryption is applicable only to an Oracle local database when using Tools Release 9.2.0.0 and greater.

Legacy encryption is used with an Oracle local database when using Tools Releases prior to 9.2.0.0 or with SQL Server Express (using any supported Tools Release).

Action: For Oracle 12c, run the ReconfigureDB.bat utility to use enhanced encryption/decryption.

For Oracle releases prior to 12c, and for SSE, run the ReconfigureDB.bat utility to choose between legacy or enhanced encryption/decryption.

For more information, see these topics in the JD Edwards EnterpriseOne Applications Upgrade Guide:

WebLogic 12.1.3 Replaces OAS (OC4J) for the Server Manager Console

Tools 9.1: The Server Manager console is available for either OAS (OC4J) or WAS.

Tools 9.2: The Server Manager console is available for WebLogic Server and WebSphere. OC4J was removed and OAS was deprecated.

Action: You must obtain and install either WebLogic Server (WLS) or WebSphere (WAS).

For WLS, a 64-bit JRE must be installed as a prerequisite.

For WAS, the product includes its own JRE.

Important: There is no upgrade path from OC4J to WebLogic. For 9.2, if you want to use Oracle Middleware for Server Manager, you must perform a fresh install of WebLogic.

For more information, see Installing the Management Console on WebLogic Server Tools in the JD Edwards EnterpriseOne Server Manager Guide.


Java Runtime Engine (JRE) for the Server Manager Agent

This refers to the JRE used by JD Edwards EnterpriseOne on the Enterprise Server on which the Server Manager Agent is installed. Note that the Oracle Universal Installer (OUI) includes its own JRE that is used only by the OUI.

Tools 9.1: The JRE for use by EnterpriseOne runtime is bundled with Server Manager Agent installer.

Tools 9.2: The JRE for use by EnterpriseOne runtime is not bundled with the Server Manager Agent installer.

Action: You must obtain and install a 32-bit JRE on the target Enterprise Server prior to running the Server Manager Agent installer. The installer prompts for and validates the location of the JRE for EnterpriseOne and ensures that it is the requisite 32-bit version.

Supported JRE versions are specified on Oracle Certifications.

For more information, see Run the Management Agent Installer in the JD Edwards EnterpriseOne Server Manager Guide.


Deployment Server as a Managed Server

Tools 9.1: Deployment Servers are not managed by Server Manager.

The Tools Release on the Deployment Server is delivered by InstallShield.

Tools 9.2: Deployment Server is a Server Manager Managed Instance.

The Tools Release is installed on the Deployment Server using standard Server Manager functionality.

Action: You must install a Server Manager agent on the Deployment Server.

You must register the Deployment Server with Server Manager.

You must deploy the Tools Release component to the managed Deployment Server.

For more information, see these topics in the JD Edwards EnterpriseOne Server Manager Guide:


SiteKey

Tools 9.1: Not applicable.

Tools 9.2: Provided functionality to encrypt sensitive data in the .ini files used by JD Edwards EnterpriseOne.

Starting with EnterpriseOne Tools Release 9.2, the EnterpriseOne encryption system uses a site key to add a higher level of security for sensitive data stored in configuration files and databases. The site key is combined with other values to create an AES key. The encryption system then uses the AES key to encrypt individual data items. Encryption using AES is the industry-standard for achieving a highly secure encryption.

The site key values are not stored in the program code. Because site keys are stored and encrypted in the JDE.INI file, each customer has a unique site key, which provides a higher level of security.

Legacy encryption is used with an Oracle local database when using Tools Releases prior to 9.2.0.0 or with SQL Server Express (using any supported Tools Release).

Action: Set up encryption before an EnterpriseOne installation using a command line utility program on the Deployment Server. You can also set up encryption after an installation through Server Manager. Both methods involve using a site key for encryption.

For more information, see Encrypting Sensitive Data in EnterpriseOne in the JD Edwards EnterpriseOne Security Administration Guide.

Default Output Location (9.2.1)

Tools 9.2: Not applicable.

Tools 9.2.1: Use the new Work with Default Output Location application (P98617) to configure the default file location for your UBEs.

For more information, see Defining a Default Output Location (Tools Release 9.2.1) in the JD Edwards EnterpriseOne Installation Guides.


SiteKey

Tools 9.1: Not applicable.

Tools 9.2: Provided functionality to encrypt sensitive data in the .ini files used by JD Edwards EnterpriseOne.

Starting with EnterpriseOne Tools Release 9.2, the EnterpriseOne encryption system uses a site key to add a higher level of security for sensitive data stored in configuration files and databases. The site key is combined with other values to create an AES key. The encryption system then uses the AES key to encrypt individual data items. Encryption using AES is the industry-standard for achieving a highly secure encryption.

The site key values are not stored in the program code. Because site keys are stored and encrypted in the JDE.INI file, each customer has a unique site key, which provides a higher level of security.

Legacy encryption is used with an Oracle local database when using Tools Releases prior to 9.2.0.0 or with SQL Server Express (using any supported Tools Release).

Action: Set up encryption before an EnterpriseOne installation using a command line utility program on the Deployment Server. You can also set up encryption after an installation through Server Manager. Both methods involve using a site key for encryption.

For more information, see Encrypting Sensitive Data in EnterpriseOne in the JD Edwards EnterpriseOne Security Administration Guide.

WebLogic Server Version Deprecated

Tools 9.1: WebLogic Server versions 10.3.5 and 12.1.2 are supported.

Tools 9.2: WebLogic Server versions 10.3.5 and 12.1.2 are deprecated.

Action: Customers using deprecated WebLogic Server versions should upgrade to supported versions.

Supported WebLogic Server versions are specified on Oracle Certifications.

Local Oracle Database Enhanced Encryption

Tools 9.1: ReconfigureMSDE.exe is the utility that encrypts/decrypts the local database user password.

Tools 9.2: ReconfigureDB.exe is the utility that encrypts/decrypts the local database user password.

With EnterpriseOne Tools Release 9.2.0.0 and later using an Oracle local database, the method of creating passwords has changed. The previous method is referred to as using Legacy encryption; whereas, the new method uses Enhanced encryption.

Enhanced encryption is applicable only to an Oracle local database when using Tools Release 9.2.0.0 and greater.

Legacy encryption is used with an Oracle local database when using Tools Releases prior to 9.2.0.0 or with SQL Server Express (using any supported Tools Release).

Action: For Oracle 12c, run the ReconfigureDB.exe utility to use enhanced encryption/decryption.

For Oracle releases prior to 12c, and for SSE, run the ReconfigureDB.exe utility to choose between legacy or enhanced encryption/decryption.

For more information, see:


WebLogic 12.1.3 Replaces OAS

Tools 9.1: The Development client can be installed on OAS or WAS.

Tools 9.2: The Development client can be installed on WebLogic Server and WebSphere (Express or Developer Editions). Server Manager console can be installed on WebLogic Server and WebSphere.

The Standalone client can only be installed on WebLogic Server.

Action: You must obtain and install either WebLogic Server or WebSphere (Express or Developer Editions).

For WebLogic Server, a 32-bit JRE must be installed as a prerequisite.

For WebSphere, the product includes its own JRE.

For more information, see:

OH4A Replaced by WLSH4A

Tools 9.1: OH4A Web Dev installer is supported.

Tools 9.2: OH4A Web Dev installer is deprecated and replaced by WLSH4A.

Action: If you are using WebLogic, you must use the new WLSH4A Web Dev installer.

For more information, see:

Objects in the Database (9.2.1)

Tools 9.2: Objects reside in a file system.

Tools 9.2.1: Objects are inserted into the database.

This enhancement inserts all object librarian type records into a database repository. Every object will have a record with a PAR file.The first full package build inserts the files into the database. Management of history records is performed using the new Work with Repository History Application

For more information, see JD Edwards EnterpriseOne Tools Package Management Guide (9.2.1)


Security Overrides

Tools 9.1: Setting up security overrides is optional.

Tools 9.2: Setting up security overrides is required.

Action: The Package Build process creates tables due to the requirement for metadata. Therefore, you must manually set up security overrides for any user who will be doing the package build.

For details on adding a security override for running packages, refer to the chapter in the Applications Install or Upgrade guides entitled Working With Signon Security and Table Creation Security.

For more information, see:


Tools 9.1: A ZIP file is available.

Tools 9.2: A Data.CAB file replaces the ZIP file.

After applying Tools 9.2, the Data.CAB file needs to be compressed for the first full package for any path code where you are building a client package.Failure to do this will result in errors during the Client Install, as the system will not be able to decompress the Data.cab file.

Action: Perform this action only for the first package for each path code.

When assembling and defining the full package, select Compress Data from the Compression Options on the Compression tab.

If you did not take the Tools Release through Server Manager, select Compress Foundation.

For more information, see Defining a Package Build in the JD Edwards EnterpriseOne Tools Package Management Guide.

Local Oracle Database Enhanced Encryption

Tools 9.1: Reconfiguremsde.exe is the utility that encrypts/decrypts the local database user password.

Tools 9.2: ReconfigureDB.exe is the utility that encrypts/decrypts the local database user password.

With EnterpriseOne Tools Release 9.2.0.0 and later using an Oracle local database, the method of creating passwords has changed. The previous method is referred to as using Legacy encryption; by contrast, the new method uses Enhanced encryption.

Enhanced encryption is applicable only to an Oracle local database when using Tools Release 9.2.0.0 and greater.

Legacy encryption is used with an Oracle local database when using Tools Releases prior to 9.2.0.0 or with SQL Server Express (using any supported Tools Release).

Action: For Oracle 12c, run the ReconfigureDB.bat utility to use enhanced encryption/decryption.

For Oracle releases prior to 12c, and for SSE, run the ReconfigureDB.bat utility to choose between legacy or enhanced encryption/decryption.

For more information, see these topics in the JD Edwards EnterpriseOne Applications Upgrade Guide:



Deployment Server as a Managed Server

Tools 9.1: Not applicable.

Tools 9.2: Provided functionality to encrypt sensitive data in the .ini files used by JD Edwards EnterpriseOne.

Starting with EnterpriseOne Tools Release 9.2, the EnterpriseOne encryption system uses a site key to add a higher level of security for sensitive data stored in configuration files and databases. The site key is combined with other values to create an AES key. The encryption system then uses the AES key to encrypt individual data items. Encryption using AES is the industry-standard for achieving a highly secure encryption.

The site key values are not stored in the program code. Because site keys are stored and encrypted in the JDE.INI file, each customer has a unique site key, which provides a higher level of security.

Action: Set up encryption before an EnterpriseOne installation using a command line utility program on the Deployment Server. You can also set up encryption after an installation through Server Manager. Both methods involve using a site key for encryption. For more information, see Encrypting Sensitive Data in EnterpriseOne in the JD Edwards EnterpriseOne Security Administration Guide.


JMX Security

Tools 9.1: Not applicable.

Tools 9.2: The Java Management Extension (JMX) protocol is now used to communicate with deployed Server Manager agents through a socket connection.

Action: A new installation of EnterpriseOne Tools 9.2 automatically includes an additional layer of security for JMX. However, if you are upgrading Server Manager to EnterpriseOne Tools Release 9.2, you must manually implement the additional security for JMX after performing the upgrade. For more information, see Implementing Security for JMX in the JD Edwards EnterpriseOne Server Manager Guide.


Long User ID

Tools 9.1: Not applicable.

Tools 9.2: As with releases prior to EnterpriseOne Tools 9.2, out of the box, EnterpriseOne user IDs (sometimes referred to as 'short' user IDs) are limited to a maximum of 10 characters. Starting with EnterpriseOne Tools 9.2, administrators have the OPTION to enable the Long User ID feature to enable users to sign in to EnterpriseOne with a user ID that has a minimum of six characters and a maximum of 254 characters. This feature provides flexibility to support longer formats such as an email address format.

Action: Enable the 'Long User ID' feature setting. This setting enables all EnterpriseOne systems that require credentials to accept long user IDs.

Note: Once enabled, the Long User ID feature cannot be disabled. However, if you enable the Long User ID setting but then decide not to create long user IDs, EnterpriseOne will still accept short user IDs as sign-in credentials. For more information, see Setting Up Long User IDs in EnterpriseOne in the JD Edwards EnterpriseOne Security Administration Guide.


Long Password

Tools 9.1: Not applicable.

Tools 9.2: As with releases prior to EnterpriseOne Tools 9.2, out of the box, EnterpriseOne passwords are limited to a maximum of 10 characters (sometimes referred to as 'short' passwords). With EnterpriseOne Tools 9.2, administrators have the OPTION to enable the Long Password feature, which enables users to create case-sensitive passwords with up to a maximum of 40 characters.

Action: Enable the "Long Password" feature setting. This setting enables all EnterpriseOne systems that require credentials to accept long passwords.

Note: When the Long Password feature is enabled, users can continue to use their existing 'short' passwords for sign-in, as long as their passwords meet the criteria defined in the password policies. For more information, see Enabling Long Passwords in EnterpriseOne in the JD Edwards EnterpriseOne Security Administration Guide.


User Defined Object Security

Tools 9.1: Not applicable

Tools 9.2: Administrators can enable or disable the user defined object (UDO) features, as well as set up security for viewing, creating, and modifying individual UDOs.

EnterpriseOne provides UDO security features in the Security Workbench to enable administrators to control:

  • Which UDO features are available in EnterpriseOne.
  • Who can create UDOs for their own personal use.
  • Who can request to publish (or share) UDOs with other users.
  • Who can view/use shared UDOs created by other users.
  • Who can modify shared UDOs created by other users.

Action: Enable access to the user defined object security and administration applications, then set up security for user defined object features and user defined objects. For more information, see Managing Security for User Defined Objects in the JD Edwards EnterpriseOne Security Administration Guide.


Secure FTP (SFTP) for Media Objects

Tools 9.1: Only non-secure FTP is available.

Tools 9.2: Secure FTP (SFTP) for media object access on the HTML Server and Business Services Server is configurable using Server Manager.

Action: Oracle recommends using SSH file transfer protocol, otherwise referred to as Secure FTP (SFTP), for accessing media objects as a more secure alternative to FTP. When EnterpriseOne is configured to use SFTP for media objects, users can securely upload, download, and delete media objects. For more information, see these topics in the JD Edwards EnterpriseOne Security Administration Guide (for HTML Server):

Action: Oracle recommends using SSH file transfer protocol, otherwise referred to as Secure FTP (SFTP), for accessing media objects as a more secure alternative to FTP. When EnterpriseOne is configured to use SFTP for media objects, users can securely upload, download, and delete media objects. For more information, see these topics in the JD Edwards EnterpriseOne Security Administration Guide (for HTML Server):