Skip to main content

Server sizes

Monitoring → Server sizes holds the size of each machine of the JD Edwards EnterpriseOne platform: its processors, physical cores, memory and disk. Nothing is collected on the machines — Server Manager says what a server uses, not how large the machine is — so the size is stated, one line per machine. What is left empty is filled from what the database says of its own server, else from a standard configuration.

These sizes are what the Capacity and Improvements tabs of Platform synthesis read, and what the OCI target sizes production from.


At a glance​

Server sizesThe size of each server, as you know it: what is left empty is measured or standard.+ Add rowBulk edit⚡ List the serversSERVERROLEPROCESSORSPHYSICAL CORESMEMORY (GB)DISK (GB)NOTECHANGED BYJDEDB01Database serverJSMITHJDEENT01Enterprise server16864300VM, 2025JSMITHJDEWEB01Web and AIS server8432JSMITHJDEDEP01Deployment server4216250added by handJSMITHAn empty cell: the database's own figure for its server, else the standard configuration of the role.List the serversa line per machine foundOne line per machineits name and its roleAdded by handa machine the reading missesLeft emptymeasured, else standardStated figuresalways win, field by field

The grid​

ColumnContent
ServerThe machine's name. It is matched with the names the Architecture reading finds without the case, the DNS domain or a port: JDEENT01.example.com, jdeent01 and jdeent01:6017 are one machine.
RoleDatabase server, Enterprise server, Web and AIS server, Deployment server, Several roles on one machine or Other.
Processors (threads, vCPU)What the system counts as processors.
Physical coresThe cores of the machine.
Memory (GB)The machine's memory.
Disk (GB)The machine's disk.
NoteFree text — where the figures come from, for example.
Changed by, Changed onWho saved the line last, and when. Read-only.

Add row adds a machine by hand; the grid's usual tools — Bulk edit, filters, export — apply.


List the servers​

List the servers adds a line for each machine the architecture reading finds that has none yet, with its name and its role; the sizes are left for you to type. A line that exists is never changed, so the action can be run again after a new server is installed.

A machine the reading does not show — a deployment server, typically — is added by hand with Add row, with its role. It then counts with the others, marked stated only — the architecture reading does not show it in Platform synthesis.


Where each figure comes from​

Each figure is taken, field by field, from the first source that has it:

OriginWhere it comes from
statedThe value typed in this grid. A stated value always wins.
measured by the databaseFor the database server only: the processors, cores and memory the Oracle database reports of its own host.
standard configurationOracle's published minimum for JD Edwards EnterpriseOne 9.2 on Oracle Cloud Infrastructure (One-Click Provisioning), per role the machine carries: 2 cores and 30 GB per server; the disk by role — 50 GB for the database, 75 GB for an enterprise server, 20 GB for a web or AIS server, 30 GB more for the application server, 100 GB for Server Manager, 210 GB for a deployment server.
counted from the other figureWhen only one of processors and cores is known, the other follows it — two processors per core.

A machine that carries several roles adds up the standard of each role it carries. The Role column says what a machine carries when the reading does not show it; Several roles on one machine keeps what the reading found.

The standard configuration is a floor to start from, not a sizing: Platform synthesis and the OCI target say how many machines still rest on it.


Edit dialog​

A double click on a line, or Add row, opens the form, one tab Size in two columns.

New · Server sizesSIZESERVER (REQUIRED)JDEENT01ROLEEnterprise server ▾PROCESSORS (THREADS, VCPU)16PHYSICAL CORES8MEMORY (GB)64DISK (GB)300NOTEVM, 2025SaveCancelServerits name, matched to the readingProcessors · coresone given, the other followsNotewhere the figure comes fromRolesets the standard configurationMemory · diskin GB; empty = not known
FieldNotes
ServerRequired. The name as the architecture reading shows it, or the machine's own name for a machine added by hand.
RoleFrom the list of roles; it decides the standard configuration of what is left empty.
Processors (threads, vCPU), Physical coresOne of the two is enough: the other is counted from it.
Memory (GB), Disk (GB)Empty when not known.
NoteOptional.

Access​

The screen shows to the roles that hold its menu entry; saving a line needs the right to change it (edit:nomajde:server_sizes), and List the servers the functions plugin:nomajde.sizing:*. The predefined roles Platform operator and Administrator hold them (see Predefined roles).


Tips & best practices​

  • Run List the servers first, then type the sizes from the virtualisation console or the system: the names then match the reading.
  • Write in Note where the figures come from (the hypervisor, an inventory, a date): a sizing is discussed on its sources.
  • Add the deployment server by hand: the reading does not see it, the OCI target counts one.
  • For the database server, leave the line empty if the database is Oracle: its own figures are taken.