Important Processes 

The processes involved are started and controlled using the J2EE Startup and Control Framework. The JControl program starts a JLaunch process for each Java process that loads the JVM and then represents the dispatcher or server process.

See the graphic from Startup and Control Framework.

The following processes must be running for the simplest installation (one dispatcher, one server):

·        Message Server ( msg_server or msg_server.exe)

·        Enqueue Server ( enserver or enserver.exe)

·        Dispatcher and server process (two jlaunch.exe)

·        Software Deployment Manager (SDM, jlaunch.exe)

Under Windows you can use the SAP Management Console to monitor the processes.

Under UNIX you can view the processes with the command:

ps -ef | grep jlaunch

At least three processes should be displayed: dispatcher, server, and SDM.

With the command

ps -ef | grep java | grep <SID>adm

you can filter the processes by user.

Since under Linux each thread runs in a separate process, the command

ps ‑ef | grep java | wc ‑l

results in about 300 processes, alone for the dispatcher/server of the J2EE Engine. So this method can only be used here to see if the J2EE Engine is running at all.