Starting and Stopping the J2EE
Engine
Purpose
You can start, stop, and monitor the J2EE Engine using the Java startup and control framework. This framework provides centralized management of the cluster nodes and monitors their life cycle. In case of cluster node failure, the framework automatically restarts the corresponding node.
Features
The Java startup and control framework provides the following set of features:
● Serves as a single point of administration (starting, restarting, stopping, and monitoring) of the J2EE Engine nodes, the Message Server and Enqueue Server processes, and the database.
● In case of cluster node failure, it restarts the corresponding node.
● Allows adding remote instances to the SAP MMC snap-in.
● Provides options for thread dump monitoring.
This option is critical for the analysis of problem situations (for example, the J2EE Engine is hanging, 100% CPU load, and so on).
● Provides options for viewing the JVM output (useful in case of J2EE Engine crash situations).
● Provides options for configuring the J2EE Engine and exporting that configuration in a file for future use (Windows).
● Allows viewing the trace files, the system environment, and the SAP system environment.
The procedure for starting and stopping the J2EE Engine depends on the underlying operating system. For more information, see the relevant information:
● Starting and Stopping the SAP Web AS ABAP+J2EE System
● Starting and Stopping the SAP Web AS J2EE System (Windows)
● Starting and Stopping the SAP Web AS J2EE System (UNIX)
For more information about the Java startup and control framework, see the following topics:
Architecture