JD Edwards Support Tools Overview
(Doc ID 1610380.1)
Last updated on JULY 09, 2019
JD Edwards EnterpriseOne Tools Information in this document applies to any platform.
This document is intended to give an overview of important Support Tools available to JD Edwards EnterpriseOne users. The document begins with a "links-at-a-glance" table to quickly find resources and additional information about each tool. Click on the link for the tool in the table and it will take you to more details and screenprints of the tool within the document.
The EnterpriseOne toolkit includes tools leveraged by any different types of users, for example: technical users, functional users, system administrators, developers, and project managers. Within your team, you likely have a variety of users accessing and using these tools to support your JD Edwards installed products. You may not personally use each and every tool available to you in the EnterpriseOne toolkit, but this document will provide a good foundational understanding of their use in your organization. Here is a table to give you a quick introduction to the tool, types of user that might use it, a use case of what it may be used for and then a specific example.
Technical; System Administrators
Manage and update servers; Troubleshooting
System administrator uses to monitor system uptime, all network jobs and kernel jobs, and check for zombie processes that might need to be identified and ended.
Simplified Diagnostics Collector
Technical; System Administrators
Gather troubleshooting files and logs
System administrator is asked to gather troubleshooting files to provide to Oracle Support for issue resolution.
Application Functional; Technical
Locate published patches. Install ESUs and configurations
Developer uses a saved query to proactively search for patches that affect objects with customizations. Identify functionality changes or bug fixed that E1 developers have provided in ESUs.
Technical; Business Partners
Package EnterpriseOne configuration objects and data
Business Partner packages up all items of an OMW project along with table data that can then be installed on to a customer's system.
Troubleshooting; Performance issue identification
System administrator, troubleshooting an application reported to have slow performance, captures a log over the process and uses PW to look for timing gaps, excessive table opens or memory leaks caused by tables being opened but not closed.
Functional; Technical; Project Managers
Review application net change between releases
Project manager considering applying a large software Update, such as Update 2 for 9.1, uses Product Features to determine new features and application functionality changes from application release 9.1 to release 9.1 WITH Update 2. Shares information across team to build a business case for undertaking the patching project and determine level of testing and retrofitting that will be needed.
Technical; Developers; Project Managers
Review structural net change between releases; data models
Upgrade project manager gathers information about structural changes to provide reports to developers for determining table and index changes that might impact customizations. Help to identify potential impacts to customizations and retrofitting efforts that may be required in the upgrade project.