Database Reference
In-Depth Information
to start the Java instance faster. The bootstrap property element.resynch has three possible
values to alter the behavior of the bootstrap process, which are detailed in OSS Note
710663. Please note that disabling bootstrapping should be considered only in a steady-state
system. During Java updates and patching the application bootstrap process should be en-
abled, which it is by default.
Verifying the SAP Java System Started Properly
You can use the following ways to make sure your SAP Java system started correctly and is
operational. The verification steps are explained in detail under subsequent sections.
• Verify if the JControl process is started at the operating system level.
• Verify if the JLaunch processes are started at the operating system level.
• Verify if the dispatcher, SDM, and Server 0 … n are in “Running” status in JCMON.
• Verify using the URL http://<server>:<port>/index.html (e.g., http://venus:50000/in-
dex.html) | System Information.
• For dual-stack systems, the Java system status can be verified by using SMICM trans-
action code (SMICM | Goto | HTTP Server | Display Data).
• The last entry in the /usr/sap/<SID>/<Instance>/work/available.log shows the current
status of the server.
JControl
The JControl process can be verified by issuing the process command shown here. You
should see one JControl process running at the operating system level.
JLaunch
The JLaunch process can be verified by issuing the process command as shown here. You
should see one JLaunch for each of the Java cluster elements. In the example there are four
JLaunch processes running at the operating system level. The first JLaunch is for the Solu-
tion Manager Diagnostic (SMD), the second JLaunch is for the Java dispatcher process, the
third JLaunch is for the server process, and the fourth JLaunch process is for the Software
Deployment Manager (SDM). You will notice more JLaunch processes if there are more
Java server processes configured in the system.
