Why it take so long to start the SAP Web Application Server?

Question

As I read from the doc that starting the SAP Web Application Server will take from 25 to 40 minutes, I don't believe. But as I try it on my machine, it does take really so long. Isn't it a wonder?
I am used to work with Tomcat, JBoss, BEA etc. None of them will take so long.

Answer 1

Hi Chen,
In a WAS I assume that it has dual stack (ABAP + JAVA)
For the startup of a ABAP Stack it generally takes about 2 minutes or so.
And for the WAS JAVA STACK should take around 8 to 15 minutes depending on the application, services and hardware sizing.
The reason for the long time required for a WAS Java Stackis:
JAVA Stack depends on three diffrent components: a) dispatcher(java) b)SDM c) Server0 process.
Now before the execution of all these the first thing what happens is the initializastion of jcontrol which inturn initiates the java bootstrap process.
At this moment of time the JVM environment takes some time for the loading and memory management. Once the JVM is loaded successfully then only the three compnents (SDM, dispatcher and server0) are initiated to run.
The SDM and dispatcher do started up with a couple of services and hence require not toomuch of time.
But the main component i.e Server0 process consumes a lot of time to startup at it requires many of the Java stack services to start before it reaches running state.
Again the port configuration for HTTP for SDM , dispatcher , server0 and java process also takes place.
So this was an overview for the Time required for a WAS Stack to come up in operational condition.
Apart from this , seeing specifically to your scenario, wherein it takes 25 - 40 minutes could be an issue with the Hardaware sizing of the Server and the Sofware compnents / tools loaded. We might need to analyze it in more detail to get a clear picture.
I hope this helps you!
Regards,
Prem