Starting and Stopping SAP NetWeaver ABAP and Java 

When you start SAP NetWeaver, you start the system database, the application servers, and the respective processes of which the system consists.

In general, the database starts first, and then the instance. When you start the central instance, the database starts automatically. However, the database does not stop when you stop the central instance.

The following sections describe how you start and stop SAP NetWeaver ABAP, Java, and the add-in installation (ABAP + Java). The procedures assume a central system that consists of a database and a central instance (ABAP, Java, ABAP + Java) on a single host.

●      Starting and Stopping SAP NetWeaver ABAP Under Microsoft Windows

●      Starting and Stopping SAP NetWeaver Java Under Microsoft Windows

●      Starting and Stopping SAP NetWeaver ABAP Under UNIX

●      Starting and Stopping SAP NetWeaver Java Under UNIX

●      Starting and Stopping SAP NetWeaver ABAP on IBM i5/OS

●      Starting and Stopping SAP NetWeaver Java on IBM i5/OS

For an add-in installation (ABAP + Java), when you start and stop ABAP instances, the corresponding Java instances start and stop automatically, by default. To deactivate the automatic start of the Java instances, set the instance profile parameter rdisp/j2ee_start to 0 in transaction RZ10. You must then restart the Java instance separate from the ABAP instance. However, when you stop an ABAP instance, the associated Java instance always stops, too.

For more information, see Restarting the Java Stack of an SAP NetWeaver Add-In Installation.

Additional Information

●      For more information about starting and stopping, see Starting and Stopping SAP Systems and Instances.

●      For more information about starting and stopping Application Services (such as SAP instances) with Adaptive Computing, see Starting and Stopping Application Services with Adaptive Computing.