Architecture
Monitoring → Architecture draws the JD Edwards EnterpriseOne platform from what is found, not from a drawing kept by hand: the instances Server Manager declares, grouped by tier and by host, the database the JD Edwards connection points at, and the machines the database sees connected. What only the database side shows has a dashed outline; a line between two cards is drawn only when something proves it. The page reads Server Manager and the database live, each time it is opened or Read again is clicked, and changes nothing.
The same diagram is the Architecture tab of the Platform synthesis.
At a glance
The figures and the sources
Five figures head the page: instances running (out of those Server Manager declares), hosts in Server Manager, database, not declared in Server Manager (amber when there is one) and links with their evidence.
Under them, each source of the diagram says whether it was read: Server Manager instances, Business function calls, JD Edwards pool, Database instance, Database sessions — read, not read or not read on this database. A source that did not answer is named in a warning with the reason, and the rest is still drawn.
The diagram
One column per tier, left to right — a tier with nothing in it is not drawn:
| Tier | What it holds |
|---|---|
| Web and AIS | The web servers and the AIS servers, and the application server they run in — WebLogic or WebSphere, with its version (Application server · WebLogic 14.1.1). |
| Enterprise servers | The enterprise servers. |
| Database | The database the JD Edwards connection points at: its product and version, its sessions. |
| Other database clients | The other machines connected to the database — a tool, an interface: the busiest ones one by one, the rest gathered on one card (12 other machines). |
| Other servers | The instances of another type. |
| Administration | The Server Manager console. |
Inside a tier, the cards sit on their host: a machine is one host whatever a source calls it (ENT01.example.com, ent01 and EXAMPLE\ENT01 are the same machine). Each card gives its name, its kind, its state — Running, To review, Stopped, Not known — and a key fact (version, home, sessions).
What Server Manager does not declare
Server Manager declares servers, not databases. What the database side shows and the console does not list is drawn with a dashed outline: the database server when its host is none of the console's hosts, a machine that runs JD Edwards kernels without being an instance, the other machines connected to the database. The figure not declared in Server Manager counts them: a machine nobody declared is often the first thing an audit asks about.
The lines
A line is drawn only on evidence, and says which:
| Line | Evidence |
|---|---|
| Blue — business function calls | A web server's own counters of the calls it sent to an enterprise server (4,803 calls). |
| Purple — database sessions | The sessions open on the database at this moment, by machine (42 sessions). |
Nothing is drawn because it is usual: two servers without a line are servers between which nothing was measured.
A card's details
A click on a card opens, on the right, what is known of it: its State, whether it is Declared in Server Manager (no — found on the database side only for a dashed card), its Host, its Tier, then its own facts (version, home, type, port, sessions, programs, accounts…), and Its lines — each line from or to it, with its evidence. A second click closes it. The − / + buttons zoom the diagram.
Download and keep
| Button | What it does |
|---|---|
| Download as SVG | Reads the platform again and saves the picture as an SVG file (jde-architecture.svg), at the size of a landscape report page. |
| Keep for the audit report | Reads the platform again and keeps that reading for the licence audit report of the application on this JD Edwards pool: the report draws it on its architecture page, in its own language — unless a picture was put there by hand. Only the last reading is kept. |
The line under the header says what is kept: Nothing is kept for the audit report yet, or the date of the reading kept and its pool.
When a source does not answer
The diagram is drawn from what was read:
- Server Manager does not answer — the servers shown are those the database sessions name, and the page says that what is declared is not known;
- the database sessions are not read — who connects to the database is not shown;
- the database is not Oracle — the database audit is not read, but the pool still says where the database is;
- nothing answers — the page says that neither Server Manager nor the database answered.
Access
The page shows to the roles that hold its menu entry and the permissions plugin:nomajde.architecture:*. The predefined roles Platform operator and Administrator hold both (see Predefined roles). It reads Server Manager through the jde_server_manager pool (see Server Manager) and the JD Edwards database, with the statements the Database audit already sends: no new statement, no AWR, no ASH.
Tips & best practices
- A dashed card deserves a question: a machine that runs kernels or holds sessions on the database without being declared is either forgotten in Server Manager or not JD Edwards at all.
- Read the page at a busy hour: the database sessions are those of the moment, and a quiet platform draws fewer lines.
- Keep a reading for the audit report once the platform is complete — after a restart, servers not yet called draw no line.
Related
- Platform synthesis — the diagram with the points to review.
- Server Manager — the instances, one grid per subject.
- Database audit — the sessions by machine and program.