Overview of the Simplified Diagnostics Collector for JD Edwards EnterpriseOne

-

The Simplified Diagnostics Collector (Collect and Generate Diagnostics) provides a simple interface to efficiently and automatically collect diagnostic data and system information using Server Manager. You have the flexibility to collect data pertaining to Deployment Server, Enterprise Server, HTML Server, and Server Manager Console. The Simplified Diagnostics Collector is now available with Tools Release 9.2.3.4.

We are going to cover the below in this blog:

   
  1. What Simplified Diagnostics Collector is
  2. The files and tables that Simplified Diagnostics collects
  3. Where the files that Simplified Diagnostics collects are located
  4. The layout and use of the application.

Simplified Diagnostics Collector with Deployment Server

There are five different options to choose from when using a Deployment Server. If you are collecting logs and UBE files related to ESU activity, then you will choose ESU Install Issue. OneWorld Client Install Files is chosen if you are wanting to collect relevant files under the OneWorld Client install directory. Package Build Files collects all of the relevant files related to the specified package name. UBE Output collects that last five PDF files for the specified UBE report name. Finally, the Server Management Agent Issue collects the SM Agent logs for the Deployment Server.
When using a Deployment Server, each server section has a Collect and Generate button and one or more links in the lower-left corner. For a given section, once the applicable selections and details have been populated, click the Collect and Generate button. This will kick off a process to collect all the requested information from the requested server. The collected data will be bundled into a zip file and the most recent zip file can then be opened or downloaded by clicking on the applicable link below the button.
The image below shows the Deployment Server files and logs.
deployment-server-files-and-logs

Simplified Diagnostics Collector with Enterprise Server

There are four different options to choose from when using the Enterprise Server:
  1. Enterprise Servers (dropdown list) selects the Enterprise Server.
  2. Enterprise Server Configuration and Logs collect logs and .ini files from the specified Enterprise Server.
  3. UBE Output collects that last five PDF files for the specified UBE report name.
  4. Sever Management Agent Issue collects the SM Agent logs for the Enterprise Server.

Simplified Diagnostics Collector with HTML Server

There are three important pieces of information in regard to HTML Servers:
  1. The HTML Servers (dropdown list) selects the HTML Server.
  2. HTML Logs collect the HTML logs from the specified HTML Server.
  3. Server Management Agent Issue collects the SM Agent logs for the HTML Server.

Simplified Diagnostics Collector with Server Manager Console

There are also three important pieces of information in regard to the Server Manager Console:
  1. The Server Manager Console (dropdown list) choose the Server Manager Console. It collects the data from 28 tables from the system data source in those four categories.
  2. It is important to remember that since the system data source is being accessed, the user will be prompted for the database username and password.
  3. The Server Management Console Issue collects the Server Manager Console Logs.
The image below shows the Server Manager Console tables.
server-manager-console

Previous Versions of Zip Files

It is important to take notice of several pieces of information in relation to the maintenance and location of previous zip files. Previous versions of the zip files are archived in their respective server locations. Periodic purging of these files is recommended.
The folder locations for each of the four server types are:
  • Deployment server- <Deployment Server install path>\CaptureDiagnosticsZip
  • Enterprise Server- <Enterprise Server instance install path>\CaptureDiagnosticsZip
  • HTML Server- <Install location of Server Manager Agent>\CaptureDiagnosticsZip
  • Server Manager Console- <Install location of Server Manager Console>\CaptureDiagnosticsZip

Data Security and Privacy

There are two primary facts to remember in regard to Data Security and Privacy.
  1. Some of the logs, reports, or data may contain information deemed confidential or security-related.
  2. A good faith effort was made to remove all password type of information from the files, but ultimately it is still the responsibility of the user to ensure they are not collecting or sharing files that might contain this type of information.

Simplified Diagnostics Collector Resources:

 

Some helpful resources to check out if you’re interested in learning more about the Simplified Diagnostics Collector include:
  • JD Edwards EnterpriseOne Diagnostics Tools: Simplified Diagnostics Collector (Doc ID 2551882.1)
  • JD Edwards: Simplified Diagnostics Collector – Collect and Generate in Server Manager (Doc ID 2564285.2)
  • JD Edwards EnterpriseOne Simplified Diagnostics Collector for 9.2.3.4 (Doc ID 2565402.1)

Comments

Post a Comment

Popular posts from this blog

Oracle Cloud Infrastructure(OCI) - Part2

-
Image
In my earlier post (OCI -Part1 ), we have gone through OCI basic details, let's dive deep more into it. Before that, we need to u nderstand the following concepts and terminology to help you get started with Oracle Cloud Infrastructure.  Note: OCI is re-branding of Bare Metal Cloud Service (BMCS) BARE METAL HOST Oracle Cloud Infrastructure provides you control of the physical host (“bare metal”) machine. Bare metal compute instances run directly on bare metal servers without a hypervisor. When you provision a bare metal compute instance, you maintain sole control of the physical CPU, memory, and network interface card (NIC). You can configure and utilize the full capabilities of each physical machine as if it were hardware running in your own data center. You do not share the physical machine with any other tenants. REGIONS AND AVAILABILITY DOMAINS  Oracle Cloud Infrastructure is physically hosted in regions and availability domains. A region is a localized geographic area, an...
Read more

Script to display the SQL text for a specific SQL_ID

-
--> Purpose:    Script to display the SQL text  for a specific SQL_ID. -->             It returns the SQL_TEXT. --> Parameters: sql_id --> To Run:     @sqltext.sql sql_id --> Example:    @sqltext.sql 27b3qfm5x89xn --> --> Copyright 2020@The Ultimate SQL Tuning Formula set echo off set define '&' set verify off define _sql_id=&1 set verify off set feedback off set linesize 200 set heading on set termout on col sqltext format a100 word_wrapped select  sql_text as sqltext from gv$sqltext where sql_id = '&_sql_id' order by piece; **************************************************************************************** --> Purpose:    Script to display the SQL text  for a specific SQL_ID. -->             It returns the SQL_TEXT. --> Caution:  ...
Read more

How to Change Your EnterpriseOne Environment Color

-
Image
Sometimes users start working and then forget which EnterpriseOne environment they are logged into. Can you tell which environment you are logged into? Luckily, there is a new UDC that allows you to change your EnterpriseOne environment color. You can now set up environments to be color-coded for when you need a clear visual distinction as to which environment you are logged into. This enables you to quickly identify the non-production environments by color. The new UDC is 98/CO and is available in EnterpriseOne Tools Release 9.2.4 with Applications Release 9.1 and 9.2. The image below shows the default EnterpriseOne environment color. However, you can easily change the color to reflect different environments. For example, DV could be red, PY could be green, and PD could be yellow, as shown below. To do so, just add a new row in the User Defined Codes section, enter the EnterpriseOne environment name and the HEX value of the color you want the environment to be, and ...
Read more