E1: ORCH: Orchestrator Monitor Only Shows Data for DefaultEnv for Multiple HTML Servers With Shared Pathcodes
(Doc ID 2786187.1)
Last updated on OCTOBER 04, 2021
Applies to:JD Edwards EnterpriseOne Orchestrator - Version 9.2 and later
Information in this document applies to any platform.
Orchestrator Health Monitor in environments with shared pathcodes
There are three custom environments sharing the same pathcode. Each environment has its own business data and control tables, but sharing the same Central Objects.
There is one HTML server and one AIS server serving all those 3 environments.
The Default Environment defined for HTML / AIS is JDV1920 .
When orchestrator object is executed in any environment, records for health status and exceptions are updated in "default" environment tables, not in the tables where orchestrator object was executed.
If AIS default environment is "JDV1920", but the orchestration is executed in "JDV2920", records for F980060 and F980061 are updated in JDV1920 Control tables, not JDV2920.
No matter in what environment the orchestrations are run, ALL the records are inserted in the same F980060/61 Control Tables JDV1920, Default Environment.
The issue can be reproduced at will with the following steps:
1. Default Env setup as JDV1920 in INI
2. Run the Orchestration in JDV2920
3. Check Orch Monitor in JDV2920 - no records for the previous run orch. The records can be seen from web JDV1920
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