Database Reference
In-Depth Information
T
ABLE
3-2
JStart in NW 7.1
Since we now know the responsibilities of the JSTART program's two different roles, let
us examine the steps of the Java start framework. This understanding will help you
troubleshoot any system startup problems.
Step 1:
• The startsap command will start the JSTART process.
• JSTART takes the role of Java instance controller (JIC).
Step 2:
• JIC will read the instance profile and get Java SDK details.
• JIC starts signal handling and opens the control port to receive any system stop sig-
nals.
Step 3:
• JIC first starts reading the profile parameters jstart/startupNodeFiles and jstart/in-
stanceNodeFiles from the instance profile, searching for runLevel = 1 property.
• “OFFLINE DEPLOYMENT” corresponds to runLevel = 1.
• jstart/startupNodeFiles profile parameter provides the name of the file that contains
the node definitions for the bootstrap and offline deployment phases. The default
value of this parameter is $(DIR_EXECUTABLE)/startup.properties.
• jstart/instanceNodeFiles profile parameter provides the node list that will constitute
the Java instance. This is derived at runtime.
Step 4:
• JIC starts another JSTART process as a child process with parameters from the
OFFLINE DEPLOYMENT node and waits.
