Professional Documents
Culture Documents
Prepared by:
Mohammed Azher Ul Haque, MCA, M.Tech.
Technical Lead – SAP Basis HANA Cloud Architect, Hyderabad, India. Mobile: +919346344403.
https://www.linkedin.com/in/mohammedazherulhaque/
The aim of this article is to provide details of the SAP NetWeaver Application Server for Java (AS Java) Startup and Control
Framework run-levels. It also dives into the logs that needs to be checked if a particular run-level fails. Performance
issues can encompass a single transaction or an entire SAP landscape. The aim is to identify the exact root cause of the
issue in order to help optimize the specific source of the performance issue. It should be noted that performance issues
can have more than one root cause, in which case two or more aspects of the landscape contribute to an overall
degradation (e.g. Network issues paired with DB issues).
More specifically, the following areas are covered:
Slow performance or hanging of AS Java in Startup phase, Running phase or during Deployment.
High CPU issues in relation to slow performance of AS Java server.
Memory issues of AS Java.
Determining the initial root cause can be achieved through answering the following questions.
1.General questions:
Is the Performance issue sporadic/random or does it occur at a fixed time?
If the performance issue is sporadic, run the /n/SDF/MON performance monitoring tool to check your overall
system performance, if this occurs at a specific time, always recommended to document this within the incident.
Is this issue with some transaction /job specific, a specific job or transaction can be analyzed with an ST12 trace
to further determine the root cause, Does the system performance degrade gradually throughout the day or is
this a spike in poor performance, have you recently implemented any changes to your system landscape?
This could indicate issues with your buffer areas. This can be checked in ST02. You should generally have no
more than 10,000 swaps per day, identify a time when the performance of the system degraded?
Is this isolated to a single server? Have you recently had an Early Watch service? If so, have the
recommendations been actioned? Does this concern a single user, or multiple users?
Do you have load balancing or logon groups configured, has there been a recent increase in system users?
“Best of luck”