SAP Java monitoring Check list
This article answers the following queries :
- How to perform daily monitoring of Java stack in SAP ?
- What are the daily checks for Java applications of SAP ?
- How to access management console in SAP ?
- How to perform session monitoring in JAVA stack of SAP ?
- How to view various java reports in JAVA stack of SAP?
- What are the various java reports available in Java stack of SAP and what is their significance?
- How to view log and traces in java stack of SAP?
- Where to view default trace in java stack of SAP?
- What is the use of management console in SAP ?
JAVA Monitoring
Contents :
- 1. Checking the java stack/portal accessibility
- 2. Actioning, in case portal not accessible
- 3. User load analysis
- 4. Java Reports – Navigation and usability
- 5. Memory consumption and Threads report
- 6. Session Monitoring
- 7. Logs and Traces (Default trace, Server0 log etc)
- 8. Accessing Management Console
- 9. Checking System availability using Management Console(SDM, Msg server, Enqueue server, Java nodes etc)
- 10. Check various logs(work directory logs, jcontrol, default trace, application log etc)
Java Monitoring :
Place the link of the respective java application in the browser and check whether the java application is opening:
For example:
http://baakaprd.company.com:50000/irj/portal
If java is up and running, a screen similar to below will open.
If the page did not open,
i) Check whether there are network issues
ii) Check tablespaces occupancy levels at Oslevel and make sure sufficient space is there and if any tablespace is 100% full, action the same
iii) Check the default trace for any critical errors
iv) Check application log to determine any memory related issues
v) Check server node status at oslevel or through management console and action and bring up the java again.
To estimate the user load and to check the number of users logged onto the java portal :
Navigate to User Administration -> Activity Reports
i) Check “Number of users in the last 3 hours” report
ii) To figure out most active users,
Java Reports :
Java Memory Consumption Report and Threads Reports :
These reports includes a chart of the memory usage of a cluster node and a chart related to the system and application thread pool.
Then navigate to Monitoring -> Java System Reports :
Here following reports can be taken by selecting the respective report from the drop down provided:
- Capacity Planning : This report includes a chart representing the requests sent to J2EE Engine, a chart for the number of http and security sessions, and a chart of the communication between J2EE nodes
- Resource Consumption : This report includes a chart of the memory usage of a cluster node, and a chart related to the system and application thread pool
- Application Activities : This report includes a chart that represents the history of the activities of deployed applications
- Slowest requests
- Slowest components
- User activities
- Current activities
However from monitoring perspective, resource consumption report is most important to analyse the memory consumption.
Select resource consumption from the dropdown to view the memory statistics as below:
Click on Go to Detailed Chart link of the respective report to view detailed chart as below
Click Hint on charts link to analyse the report better.
Select the respective Instance, Cluster node and Time period from the provided dropdown boxes to view the reports belonging to the same
Table view for Threads report:
There are 2 types of views: Chart view and Table view. You can change the view by selecting the respective radio button.
Please find below table view for Memory Consumption report
Session Monitoring:
Hi VS,
this is a nice article and a subject I have seen many companies cross.
But really, in the year 2014, the monitoring of Enterprise Software should be by automated tools and not humans shouldn't it.
There are many possibilities for monitoring Java stacks using and extending Solution Manager and other tools with automated incident generation etc.
Best regards,
Andy.
Hi Andy,
you are right, but it's always better to be able to monitor a system without "little magic helpers". There is no need to do monitoring without these "little magic helpers", but it's better to have the skill to do it without them!
Best regards
Willi Eimler
Ohh I forgot: Good work vs akondi.
Hi VS,
yes, in that respect it is nice sharing of information.
Perhaps, suggest, you make it clear that this is for NW7.0x EP7, and for NW 7.1 (CE/NWDI), 7.2 (CE/NWDI), 7.3 and 7.4 the navigation is different, subtle changes to the NWA and Portal navigation.
Best regards,
Andy.
hello All,
is there same monitoring features available in NW Java 750 version.