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.
Note
In general, the database starts first, and then the instance. When you start the central instance, the database is therefore automatically also started. However, the database is not stopped 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 description is limited to the activities in the case of a central system that consists of a database and a central instance (ABAP, Java, ABAP + Java) on one host. Only Microsoft Windows and UNIX are considered at operating system level:
Note
In the case of an add-in installation (ABAP + Java), when you start and stop ABAP instances, the corresponding Java instances are automatically also started and stopped, by default. If you want to deactivate the automatic starting of the Java instances, you need to set the instance profile parameter rdisp/j2ee_start to the value 0 in transaction RZ10. You can then restart the Java instance as described in the section Restarting the Java Stack of an SAP NetWeaver Add-In Installation. When you stop an ABAP instance, however, the associated Java instance is always also stopped.
Additional Information
For additional 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.
CautionAdaptive Computing is only supported if you are using the Adaptive Computing Controller 1.0 for SAP NetWeaver Release ’04 (see SAP Note 725397). However, the Adaptive Computing Controller 1.0 can control all releases from SAP R/3 4.6C to SAP NetWeaver 7.0 (Managed Adaptive Landscape).
End of the caution.