My Oracle Support Banner

E1: ORCH Orchestrator Monitor Doesn't Open - P980060X Is Blank / Keep Spinning (Doc ID 2507356.1)

Last updated on SEPTEMBER 30, 2021

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

Symptom 1:  When attempting to test Orchestration monitoring application (P980060X), you get a blank screen.

Symptom 2:    Correct UDO is applied and UDO security is implemented, but the Orchestrator Monito application keeps spinning with blank info. 

Symptom 3:

The main symptom in the logs is that there are calls to get from:

RequestMonitorManager file

RequestMonitorManager.getFromFile()

Which always show a failure

RequestMonitorManager.setupFileName() - Failed Request file set up

AISDebug:

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
 Symptom 1:  When attempting to test Orchestration monitoring application (P980060X), you get a blank screen.
 Symptom 2:    Correct UDO is applied and UDO security is implemented, but the Orchestrator Monito application keeps spinning with blank info. 
 Symptom 3:
Changes
Cause
 CAUSE 1:   Missing UDO object (s) for Orchestrator Monitor 
 CAUSE 2:  "Display System Information" jas.ini setting under [OWWEB] set to false. 
 CAUSE 3:  Exception/Health Monitor's password became corrupted somehow
Solution
  SOLUTION 1:  Apply UDOs
 SOLUTION 2:  Make sure "Display System Information" jas.ini setting under [OWWEB] set to true.
 SOLUTION 3:  Follow the steps.
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.