You are on page 1of 2

Startup of the Java Instance

The following steps are involved in starting the Java instance: 1. JSTART is started (in Windows by the SAP Start Service; on UNIX platforms by the startsap script). It takes the role of the Java instance controller. 2. The Java instance controller analyzes its configuration (from the instance profile) and examines the details of the Java SDK defined there. 3. The Java instance controller initializes SAP signal handling to be able to receive signals and opens the control port. 4. The Java instance controller reads the instance description (from the list of files specified by the jstart/startupNodeFiles and jstart/instanceNodeFiles profile parameters) for the first time, searching for nodes with a runLevel=1 property. The OFFLINE DEPLOYMENT node in the startup.properties file matches this criterion. 5. The Java instance controller starts another JSTART process with the parameters from the OFFLINE DEPLOYMENT node and waits for the child process to terminate. 6. The child process acts as a Java process. It loads the Java Virtual Machine (JVM) into its own process, initializes the JVM and starts the OFFLINE DEPLOYMENT program, which performs the deployment steps in the Java database. 7. The Java instance controller reads the instance description again, searching for nodes with a runLevel=2 property. The BOOTSTRAP node in the startup.properties file meets this condition. 8. The Java instance controller starts another JSTART process with the parameters from the BOOTSTRAP node and waits for the child process to terminate. 9. The child process loads and initializes the JVM and starts the BOOTSTRAP program. BOOTSTRAP synchronizes the binary data in the Java database with the local file system, reads the Java instance description from the Java database and updates the instance.properties file. 10. The Java instance controller reads the instance description from the startup.properties and instance.properties files once more, this time focusing on nodes with a runLevel=3 property or without a runLevel property at all. These nodes form the productive instance. 11. The Java instance controller starts the processes for infrastructure nodes, such as ICM or DEBUGPROXY. 12. When all infrastructure processes are started, the Java instance controller starts the processes for the server nodes. 13. The JSTART child processes act as Java processes and execute a similar sequence as described before. They become the Java server processes.

the ABAP dispatcher. the Java instance controller terminates. When the server processes are finished. The Java instance controller updates the instance state and sends STOP commands to the server processes. 2. 4. 3. A process (for example. .An instance is stopped as follows: 1. Once all child processes have exited. a start script or SAP Start Service) sends a SIGINT signal or an appropriate command to the Java instance controller. the Java instance controller sends STOP commands to the infrastructure processes.