Skip to main content

Server Manager

Monitoring → Server Manager shows what the JD Edwards Server Manager console knows, in six Nomajde grids: the instances and their state, who is connected, the load of the enterprise servers and of their processes, the business function calls and errors, the Java memory of the web and AIS servers. The screens read the console live each time they are opened or refreshed; nothing is stored in Nomajde.

For the health of the servers over time — checks every five minutes, availability, alerts — see JDE Health Check.


At a glance​

MONITORINGJDE Health Check▾ Server ManagerInstancesConnected usersEnterprise serversServer processesBusiness functionsWeb and AIS serversConnected usersSHOWSessions ▾Advanced filtersInstance = JAS_PD↻ RefreshUSERSESSIONINSTANCEENVIRONMENTROLEOPEN APPLICATIONSIDLE (S)JSMITHWeb sessionJAS_PDJPD920·ALLP01012, P421012MDUPONTWeb sessionJAS_PDJPD920AP_CLERKP0411340AMARTINWeb sessionJAS_PDJPY920·ALLP03B1158SVC_AISAIS sessionAIS_PDJPD920·ALL—3Read live from the Server Manager console — nothing is stored.Six live screensone grid for the whole platformEvery running instanceread togetherShowsessions, or also processesAdvanced filterspick-lists listed liveKind of sessionweb, AIS, server process

The six screens​

Every screen is read-only and loads when opened. Each one asks the console for its instances, then reads every running instance of the right kind together: one grid covers the whole platform. An instance that is stopped, or that the console refuses to answer for, keeps a row whose Note column says why — not running (STOPPED) for example.

Menu entryWhat it listsMain columns
InstancesEvery instance the console manages.Instance, Type, State, Tools release, Host, JDE home.
Connected usersThe web and AIS sessions — and, on request, the enterprise server processes each user is connected to.User, Session, Instance, Environment, Role, From, Open applications, Signed in at, Idle (seconds), Last active, Process.
Enterprise serversOne row per enterprise server.Instance, Host, Up for, Network jobs, Kernel jobs, Zombie processes, Security kernel users, Call object users, CPU, Memory.
Server processesEach kernel and network listener of the enterprise servers.Process, Process id, Instance, Kind, Users, Connected, Outstanding requests, Messages received, Memory, CPU, Threads, Database connections, Open transactions, Started, Last message.
Business functionsThe business function calls seen by each web server.Business function, Calls, Average (ms), Longest (ms), Timeouts, Application errors, System errors, Total (ms), Shortest (ms), Instance, Enterprise server.
Web and AIS serversEach web and AIS node.Instance, Node, Type, Up for, Online users, Sign-in, Java heap used (MB), Java heap maximum (MB), Java heap used (percent).

Figures are numbers: they sort, total and export as such.

Connected users​

The Show dropdown above the grid chooses between Sessions — the web and AIS sessions, the default — and Sessions and server processes, which adds the enterprise server processes each user is connected to. The grid is empty when nobody is signed in.


Filters​

Nothing is typed above the grids: the columns are in the advanced filters, with the same operators as any Nomajde grid. Where the values are known the filter is a pick-list:

FilterValues
StateRUNNING, STOPPED, UNKNOWN.
Session (Connected users)Web session, AIS session, Enterprise server process.
Kind (Server processes)Kernel Process, Network Listener.
InstanceThe instances of the console, listed live with their type.

A filter applies to the rows the console returned: it narrows what is shown, not what is asked from the console.


The Server Manager connection​

The screens use the jde_server_manager connector, the one the health check already uses. In Liberty Next → Data → Connectors, open it and set the address of the console and the password of its account (jde_admin by default). The account's rights in Server Manager decide what it may read.


The catalogue of Server Manager services​

Beyond the six screens, the connector carries a catalogue of the Server Manager REST services, written from Oracle's guide: each endpoint has its parameters explained, and its own permission, so that a role can be given one service and not the others. They can be called from the connector's Test tab, a screen action, a job step or the AI assistant.

HeadingContent
MonitoringInstances, homes and agents, path codes, WebLogic domains and servers, components and their versions, INI configuration, log files.
Runtime MetricsEnterprise server activity and processes, business function statistics, Java memory, JDBj connections and caches, connected users, user sessions.
Manage and Update OperationsStart or stop an instance, every instance or a WebLogic server, refresh the environments, clear the data caches.
Server Group, User Log Configuration, othersServer groups, saved configurations, the log level of a user.

Nine services change the platform — start and stop an instance, start and stop every instance, start and stop a WebLogic server, refresh the environments, change a log level, clear the data caches. They are marked as such: the AI assistant never calls one without showing a card to approve first, and only for a user allowed to change data through it.

Provisioning (create, register or delete an instance), passwords, TLS, users and groups, save and restore, and the updates of the agents and of the console are left out of the catalogue on purpose.


Access​

Each screen shows to the roles that hold its menu entry. A raw service of the catalogue needs the permission api:jde_server_manager:<service> (rule type API endpoint in a role's Beyond the menus rules): grant the reading ones widely, the nine that change the platform to the platform team only.


Tips & best practices​

  • Start with Instances: an instance that is not RUNNING explains an empty line in the other screens.
  • In Server processes, sort on Outstanding requests or CPU to find the kernel that holds a queue.
  • In Business functions, sort on System errors or Timeouts after a deployment: a function that fails on one web server only points at that server.
  • Web and AIS servers — a heap used close to its maximum over several refreshes is the signal to look at before the users call.