Beruflich Dokumente
Kultur Dokumente
| SAP Blogs
Products
Products Industries
Industries Services and Support
Services Support Training
Training Community
Community Developer
Developer
Partner
Partner About
About
Juan Reyes
July 11, 2016 2 minute read
After writing Basic start-up troubleshooting – the logical sequence! I promised to deliver a Java version of it. It
has taken rather a long time but I nally put together my attempt to describe the basic ow of a Java System
startup and the possible areas where problems can occur.
This is not by any means perfect but I like to believe it gives a decent overview of the process.
Database Starts
https://blogs.sap.com/2016/07/11/basic-start-up-troubleshooting-java-the-logical-sequence/ 1/9
6/22/2019 Basic start-up troubleshooting JAVA – the logical sequel! | SAP Blogs
As on ABAP the rst step is to check and start the database. No dedicated developer trace is created in the
work directory as the database has its own logs. If the database does not start correctly it should be visible
within seconds and errors will be available within the DB logs.
Startup
JSTART is called next, it takes the role of the Java instance controller which analyzes its con guration and
initializes SAP signal handling and opens the control port.
There is very rarely an issue with the initial load of JSTART. If for some reason this fails you most likely have a
problem with your instance pro le.
O ine Deployment
The Java instance controller reads the instance de nition and creates a child process that initializes JVM and
starts the OFFLINE DEPLOYMENT program which performs the deployment steps in the Java database.
In the ‘business as usual’ scenario this is very unlikely to end up in an error. These days most deployments are
done automaticaly using SUM, the traces will be lled when the instance is stopped and started during the SUM
deployment phase.
Bootstrap
BOOTSTRAP synchronizes the binary data in the Java database with the local le system.
This is where you will most likely nd issues during your system startup. Errors during this phase are common
and usually caused by issues in one of the following areas;
1. Problems at DB Level
https://blogs.sap.com/2016/07/11/basic-start-up-troubleshooting-java-the-logical-sequence/ 2/9
6/22/2019 Basic start-up troubleshooting JAVA – the logical sequel! | SAP Blogs
There is a large number of reasons for this to fail going from DB availability to problems with listeners and DB
user authentication.
Bootstrap Stops Due to Database Problems – Con guration of SAP NetWeaver – SAP Library
Bootstrap Stops Due to File System Problems – Con guration of SAP NetWeaver – SAP Library
Bootstrap Stops Due to Con guration Problems – Con guration of SAP NetWeaver – SAP Library
The Java instance controller starts the processes for infrastructure nodes – the most important in my opinion is
ICM; ICM handles the HTTP request directed to the AS JAVA system.
If there is an issue with ICM you’ll see an error on screen while calling the java standard URL. http://<host>.
<fqdn>:<port> you will also nd the details on the ICM developer trace.
Server Node
https://blogs.sap.com/2016/07/11/basic-start-up-troubleshooting-java-the-logical-sequence/ 3/9
6/22/2019 Basic start-up troubleshooting JAVA – the logical sequel! | SAP Blogs
When all infrastructure processes are started, the Java instance controller starts the processes for the server
nodes.
Finally, your Java system is running and if there was an issue with any request dealt with by this server node you
will nd information about it on the developer trace.
Hope this is a good basic explanation of where to start when troubleshooting a Java Startup problem!
As a reference I have taken the freedom to borrow this lovely chart from SAP Help to ilustrate my case
(Image Source: Startup, Operation and Shutdown of an AS Java Instance – Administration – SAP Library)
https://blogs.sap.com/2016/07/11/basic-start-up-troubleshooting-java-the-logical-sequence/ 4/9
6/22/2019 Basic start-up troubleshooting JAVA – the logical sequel! | SAP Blogs
Alert Moderator
Assigned tags
NW AS Java Administrator (NWA) | Java | SAP NetWeaver | SAP NetWeaver Application Server for ABAP | SAP
NetWeaver Application Server for Java |
View more...
https://blogs.sap.com/2016/07/11/basic-start-up-troubleshooting-java-the-logical-sequence/ 5/9
6/22/2019 Basic start-up troubleshooting JAVA – the logical sequel! | SAP Blogs
Related Questions
11 Comments
Willi Eimler
Anurag Das
Very Nice Explanation and the picture is really very helpful for visualization.
Regards
Anurag
Former Member
With Regards
Ashutosh Chaturvedi
https://blogs.sap.com/2016/07/11/basic-start-up-troubleshooting-java-the-logical-sequence/ 7/9
6/22/2019 Basic start-up troubleshooting JAVA – the logical sequel! | SAP Blogs
Kaushik G
Clear explanation
Regards
kaushik G
Asad S Zafer
Thanks,
Asad Zafer
Sebastian Kayatas
It would have been even more awesome if you can explain brie y some of the process here:
https://blogs.sap.com/2016/07/11/basic-start-up-troubleshooting-java-the-logical-sequence/ 8/9
6/22/2019 Basic start-up troubleshooting JAVA – the logical sequel! | SAP Blogs
Java o ine deployment: What is being deployed here? How is the ow of deployment? SAP NetWeaver Java
DB started already and i am not clear on the ow of this process. what is being read and where java
components are being deployed? on NW DB? Aren’t the components already deployed? Can you please
elaborate on this process?
Java Bootstrap – What part of the le system and DB are synchronized? I know for fact no repository objects
are synched, and how is the ow of synchronization? from DB to le vs from le to DB?
Thanks a lot. I really appreciate if you can help clear these points
Add Comment
Sitemap Newsletter
https://blogs.sap.com/2016/07/11/basic-start-up-troubleshooting-java-the-logical-sequence/ 9/9