JDE Servers

Monitoring → JDE Servers shows the JD Edwards servers as the last health check saw them: one row per instance, its state in Server Manager, the health result, the checks that failed and the action taken. The checks come from the nomajde-jde-health job, which queries Server Manager every five minutes once enabled.

---

At a glance

---

The grid

The grid is read-only and lists the latest check of each instance checked in the last 24 hours.

Column	Content
Host	The Server Manager agent host of the instance.
Instance	The instance name in Server Manager.
Server type	entserver (enterprise server), webserver (HTML server) or restserver (AIS server).
State	The state reported by Server Manager, e.g. RUNNING.
Health	passed, failed (a check did not pass, or its enterprise server is not healthy), down (the instance is not running) or error (Server Manager could not be queried for it, or the instance is unknown to Server Manager).
Failed checks	The Server Manager checks that did not pass, among the ones monitored (see Parameters).
Enterprise server	For an instance declared in a group, the enterprise server it depends on.
Action	stopped when the check stopped the instance, stop failed when the stop was refused.
Detail	The error message, or the reason of a failure inherited from the enterprise server.
Checked at	The time of the check.

The Host, Instance, Server type and Health columns can be filtered.

The history of an instance

Opening a row shows the instance in a dialog. The General tab repeats the fields of the grid; the History tab lists every check kept for the instance, most recent first: time, state, health, failed checks, enterprise server, action, detail.

---

On the overview

The Nomajde home page carries two JDE servers tiles, based on the last check of each instance over 24 hours:

• the number of healthy instances out of the instances monitored, with the time of the last check;
• the list of instances: the server type and host, the failed checks and the action taken, a status pill — OK, Failed, Down, Error —, the availability over 24 hours (the share of passed checks) and the number of checks. Instances in trouble come first; an instance whose last check is older than 30 minutes is shown in amber, tagged Late.

---

The collection job

The nomajde-jde-health job checks the servers through the Server Manager REST API. It ships disabled, scheduled every five minutes (Europe/Paris).

1. In Liberty Next → Build → Connectors, open the jde_server_manager connector and set the Server Manager address and the password of the jde_admin account.
2. In Nomaflow → Jobs, adjust the parameters of nomajde-jde-health if needed, then enable it.
3. Jobs → Check the JDE servers in the Nomajde menu runs the check at once, without waiting for the schedule.

Each run asks Server Manager for the list of instances and runs its health check on each running instance. The run fails — and triggers the job's alerts — when an instance did not pass; the rows are written beforehand, so the grid shows the failure.

Parameters

Parameter	Default	Meaning
checks	UBE, BSFN, Port Test, Login, Interactive App, OVR	The Server Manager checks that count; the others are ignored. Blank: every check counts.
groups	blank	The instances that depend on an enterprise server, as JSON: {"<host>-<enterprise server>": ["<host>-<instance>", …]}. When the enterprise server is down or not healthy, its instances are marked failed without being checked. When set, only the instances named here are monitored.
auto_stop	false	true stops a running instance that failed, and the running instances of a failed enterprise server.
keep_days	30	The number of days of checks kept; older rows are removed at each run.

Details of the job: nomajde-jde-health.

---

Related

• Jobs — the Nomajde jobs, including Check the JDE servers.
• Notifications — to be alerted when the check fails.
• Overview — the home page.