Skip to main content

Platform analysis

Monitoring → Platform analysis reads what Server Manager measures now and reads it as an analysis: the figures, then what the figures say — the points to review first —, then the details by subject in four tabs. Nothing is kept: the figures are those of the console at the moment the page is read.


At a glance​

Platform analysisThe JD Edwards servers as Server Manager measures them now, and what the figures point at.Read againOverviewThe figures, what they say, the instancesServersWeb and AIS nodes, processesBusiness functionsCalls, times, timeouts and errorsINI settingsAn instance's INI, read or compared4 / 4INSTANCES RUNNING36SERVER PROCESSES2ZOMBIE PROCESSES18SESSIONS12,480BUSINESS FUNCTION CALLS0OF THEM IN ERRORWHAT THE FIGURES SAYENTERPRISE SERVER2 zombie process(es) on ENT_PD: … to review with the enterprise server's logs.BUSINESS FUNCTIONSB4200310 takes 41 ms on average over 920 calls — the others' median is 3 ms.INSTANCESThe 4 instances are running.WEB AND AISThe 2 web / AIS node(s) have room in their Java heap.INSTANCESINSTANCETYPESTATEVERSIONENT_PDentserverRUNNING9.2.xHTML_PDwebserverRUNNING9.2.xAIS_PDrestserverRUNNING9.2.xFour tabsa tab says what is to reviewSix figureslive from Server ManagerWhat the figures sayamber to review, green nothingINI settingsread one, or compare twoRead againnothing is keptInstancesone not running shows amber

The four tabs​

Each tab says, beside its description, how many of its points are to review.

TabContent
OverviewSix figures — instances running, server processes, zombie processes, sessions, business function calls, of them in error —, What the figures say and the list of Instances (instance, type, state, version).
ServersThe Web and AIS nodes — up for, users online, Java heap used against its maximum, with a bar — and the enterprise server Processes: waiting requests, open transactions, database connections, threads, memory, users; the busiest first.
Business functionsCalls, average and longest time, timeouts, system and application errors; the ones in error or the slowest first.
INI settingsAn instance's INI, read or compared with another's.

What the figures say​

Each line names its area and is marked amber (to review), blue (to know) or green (nothing to flag):

  • an instance that is not running;
  • zombie processes on an enterprise server — to review with its logs;
  • a kernel with requests waiting, or many transactions open;
  • a business function that times out, fails, or is far slower than the others' median;
  • a Java heap above 80 % of its maximum, a web server restarted a moment ago.

An area with nothing to flag says so: The 4 instances are running.


INI settings​

Pick An instance, optionally another under Compared with, then Read its INI. Alone, the INI is listed by section and setting; compared, only the settings that differ are listed, with the value of each instance. Find a section or a setting… narrows the list as you type. Server Manager takes a few seconds to answer an INI; the result stays in place when you switch tabs.


Access​

The page shows to the roles that hold its menu entry and the permissions plugin:nomajde.platform:*. It reads Server Manager through the jde_server_manager connector for the user: the permissions of the Server Manager services do not apply here.


Tips & best practices​

  • Read the Overview tab after a deployment or a restart: an amber line is where to start.
  • Compare the INI of two enterprise servers that should be identical: a difference is often the cause of a behaviour seen on one server only.
  • The server log files are not read — the console only lists the signed-in user's own logs.