Quiet nights for your JDE servers.
OperoOps monitors servers, services and jobs of your JD Edwards environment and steps in at night by fixed rules. In the morning the report is waiting.
A night without OperoOps
When a job stalls at night, we notice at eight, when the delivery notes are missing.
On call means: someone sleeps with the phone next to the pillow.
We piece together what happened overnight from log files.
Fixed rules instead of calls at night.
Agents on the JDE servers report services, jobs and resources. Countermeasures are defined for known faults. No AI, every action logged.
The same night with OperoOps
- Install the agent
On every JDE server, connected to OperoOps.
- Set the rules
What counts as a fault and what happens then.
- Act at night
OperoOps carries out the defined action.
- Report in the morning
What happened and what was done.
| Faults surface in the morning | Action during the night |
| On call by phone | The rule acts first |
| Searching log files | Report with timeline |
- OperationOn your premises or as a service by Suppora; the agents run on your JDE servers
- DecisionsFixed rules, no AI
- TraceableEvery action logged
- ScopeMonitoring, alerting and planned maintenance
Everything OperoOps does
15 features
Agent on every server
Enterprise, HTML, AIS and database servers report regularly.
JDE log errors by pattern
Identical errors are grouped and counted; a real incident stands out from the noise.
Database metrics
Connections and load in view.
Alert rules
Per server type, severity and category, with thresholds per period.
Defined countermeasures
e.g. freeing disk space when a disk fills up.
Effect measured
After every action OperoOps checks on the system whether the problem is really solved.
No AI
Fixed rules, every action logged.
Shutdown in the right order
Web, then enterprise, then database; start in reverse, each step only after the previous one is confirmed.
Informing users
Message to signed-in users, ending sessions, waiting for running reports.
Maintenance windows and schedules
Plannable as recurring.
Maintenance record
Who was online, which sessions ended, which reports ran.
On your premises
OperoOps runs in your data centre, the data stays in-house.
As a service by Suppora
We run OperoOps; the agents on your servers report over a connection of their own.
Sign-in with a second factor
Roles for reading and administering.
Report by mail
What happened and what was done.
Nothing found. Ask us directly whether OperoOps can do it.
Your path with OperoOps
Every morning the night report shows what happened, what OperoOps did and whether it worked.
- Stage 1
Visible
Agents on all servers, log errors grouped.
Your progressYou see what really matters. - Stage 2
Rules
Known faults get a fixed countermeasure.
Your progressNights without a call. - Stage 3
Maintenance planned
Patching with shutdown and restart in the right order.
Your progressNo full log after the patch. - Stage 4
Proof
Maintenance record and night report for every action.
Your progressOperations you can prove.
OperoOps in 30 seconds
Animated illustration with fictional sample data: the problem, the solution, the four steps. We are happy to show you the real system.
See OperoOps in your environment?
Tell us briefly what it is about. We will get back to you within two working days.