JDE CNC Environment Health Check Checklist

0%

0 of 31 items complete

8 critical items still open - these are the highest-risk gaps.

Download checklist:

Enterprise server and JDENET

Enterprise server processes (JDENET and kernel processes) are running and no unexpected restarts in the last weekCRITICALWork with Servers shows expected kernel counts and no stuck processesjde.log and jdedebug.log sizes checked and old logs archived or rotatedDisk space on log, spec and print queue directories above your thresholdCRITICALJDE.INI settings reviewed against the baseline for each serverServer Manager agent shows each managed instance as running

Web tier: JAS, HTML and AIS

Each HTML server instance responds and users can sign inCRITICALAIS server and Orchestrator endpoints respond for integrationsApplication server (WebLogic or WebSphere) heap and thread usage reviewedTLS certificates expiry checked at least 60 days aheadCRITICALLoad balancer health checks and session affinity confirmedServer Manager reports no unresolved alerts on web instances

Database

Last full backup completed and a restore test performed this quarterCRITICALTransaction log or redo and archive space healthyTablespace or filegroup growth reviewed for F0911, F4111, F4211 and F43121Index maintenance and statistics jobs ran successfullyODBC data sources and database credentials for each path code verifiedBlocking, long running queries or deadlocks reviewed

Batch processing and scheduling

Submitted jobs reviewed for errors, stuck jobs and long run timesCRITICALScheduled UBE jobs ran at the expected times and none are stuck in waitPrint queue and output (PDF) cleanup runJob Control Status Master growth reviewed and purge job in placeIntegrated Testing and UBE queue settings match business needs

Security and change control

Inactive and terminated users disabled, shared accounts reviewedCRITICALSecurity Workbench changes since last review approved and documentedPath code and package deployments recorded for each environmentObject Management Workbench check-ins match approved change requestsOracle critical patch updates and tools release support dates reviewed

Documentation and recovery

Disaster recovery plan lists steps to restore enterprise server, deployment server and databaseCRITICALServer inventory with release, tools release and path code mapping is currentOn call contacts for Oracle support, DBA and network teams verified

Complete all critical items first. Any unchecked critical item is a finding to resolve before the next change window.

JDE log analysis on-prem

Optional: discuss summarising JDE logs and batch failures with a private model.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Work through each group, tick items off and note findings. Export to PDF or Excel to keep an audit trail. Run the critical items weekly and the full list monthly, and before major events such as a tools release upgrade or package deployment.

What good looks like

A healthy environment has no unexplained restarts, logs that are rotated, a tested backup, no stuck batch jobs and a security review on a regular cadence. It also has current documentation, because the person who knows the JDE.INI details is not always the person on call.

Where problems usually hide

Most incidents come from disk space filling with logs and print output, expired certificates, a database that grew past its allocated space, and a stuck kernel process that silently stops batch work. These items sit at the top of the list for that reason.

Check logs before users report slowness
Keep monitoring thresholds written down
Test restores, not just backups

Tailoring the list

Add site specific items such as integrations to your EDI network, orchestrations used by shop floor devices, or third party reporting tools. Remove items that do not apply to your architecture, for example a managed cloud setup where Oracle runs the infrastructure layer.

Frequently Asked Questions

How often should a JDE health check run?

Critical items weekly and the full list monthly is a common pattern. Add a run before and after tools release upgrades, package deployments and any database or operating system patching window.

Who owns the checklist?

Normally the CNC administrator, with the DBA owning the database items and the security administrator owning user and Security Workbench items. Name an owner per group so findings are actioned.

Does this apply to JDE in Oracle Cloud?

Partly. If Oracle manages infrastructure, items about operating system, database and patching shift to the provider, but package, security, batch and integration items remain with you.

What is the most important item?

A tested restore. A backup that has never been restored is an assumption. After that, watch disk space and certificate expiry, since both cause outages that are entirely preventable.

If your CNC team is stretched, we can help set up monitoring and log analysis, including on-prem AI that summarises JDE logs without sending data outside your network.

Talk to an Expert Explore More Free Tools

Related Tools

Oracle

More Oracle tools

See all

JD Edwards EnterpriseOne CNC Environment Health Check Checklist