EWR for JAVA Based Systems

[Former Member]

I configured an Early Watch Report for 1 of our JAVA based Portal System including complete configuration for SMD and Wily.

We are on SP-15 on SolMan.

Now, when Report is Generated, it simply runs into 2 Pages and does not provide much detail.

Is this Normal ??. As EWR Reports for ABAP based System runs into many Pages with much more detail.

Thanks,

[former_member209604 · Accepted solution]

Hi Paresh,

2 pages MS Word report sounds very short.

Which sections can you see? Any information on missing data?

Ruediger

[Former Member · Accepted solution]

Hi Ruediger,

This is what I am getting.

=============================================================================

EarlyWatch Alert - Development Landscape

1 Service Summary

During the EarlyWatch Alert Service, we did not detect critical problems.

Note:

All recommendations provided in this report are based on our general experience. We advise that you test them before using them in your production system. Also note that EarlyWatch Alert is an automatic service.

Section Overview

Rating Checked Area

Java VM Memory Performance

Java VM Activity Reporting

Note: For more information about EarlyWatch Alert, a sample EarlyWatch Alert report with explanations is available in the Media Library on SAP Service Marketplace (http://service.sap.com/ewa). This provides an overview of the check rating strategy and the KPIs that trigger the EWA alerts.

Alert Message Overview

Note: If you need help investigating the alerts listed, order an EarlyWatch contract by contacting your local support organization or by creating a customer message under component SV-BO. If you already have such a contract, a detailed analysis can be performed during the next Service Session. Address the topic when preparing for the session.

Note:

If your system suffers from serious performance problems, create a customer message under component SV-BO with the priority "High" or "Very High".

2 Java Performance Data

Reporting Interval

Data displayed in this section of the report was collected for the time frame specified below.

System Start Time End Time

NPD Sun Mar 09 00:00:00 EST 2008 Sun Mar 16 00:00:00 EST 2008

2.1 Java VM Memory Performance

2.1.1 Garbage Collection Time

Time spent in Garbage Collections (GC) prevents the Java virtual machine from executing any other task. Over the interval reported, this time is not critical.

Average GC Time (Cluster wide) [%]

0.02

The table above displays the cluster-wide weekly average of Garbage Collection (GC) time. Garbage collections themselves have a direct impact on system performance. Furthermore, they may also be indicative of more substantial performance issues that may require further analysis.

Hostname Cluster Element ID Average [%] Max [%]

xxxdev.xxx.com

The table above lists the average and the maximum GC time for the server nodes calculated as defined above. You should investigate particularly high values since these can point to critical situations. As a starting point to analyze errors, you should analyze the log files of the particular server node for the given timeframe.

Recommendations:

If a high percentage of time is spent in garbage collections, you can measure its impact on performance directly. Thus, if the average value is particularly large, you need to analyze this from a general performance perspective. Temporarily high values of the GC time indicate critical situations. You should analyze these specific situations in comparison with other key performance indicators in this report to determine potential correlations.

2.1.2 Fraction of Full Garbage Collections

The maximum ratio of full garbage collection to all garbage collections is not critical in the reported interval.

Hostname Cluster Element ID Max [%]

xxxdev.xxx.com

In general, minor garbage collections must occur more frequently than full garbage collections. A consecutive number of full garbage collections is a clear indicator that the Java Virtual Machine (JVM) is not removing objects from the old space. If the dynamic behavior of the JVM is dominated by old space memory removal, insufficient resources are available to accept requests and their newly-created objects. In this case, the parameter below is analyzed. On a floating interval of all garbage collections, the fraction of full garbage collections is calculated.

2.1.3 Allocation Rate

The allocation rate quantifies the amount of memory allocated on the young generation each second. This therefore quantifies the input to the Java VM. Particularly high values indicate high JVM throughput and so should always be analyzed in parallel with the user load or the number of HTTP sessions.

Allocation Rate (Cluster wide)[KB/s]

1143

Hostname Cluster Element ID Average [KB/s]

xxxdev.xxx.com

2.1.4 Promotion Rate

The promotion rate quantifies the amount of memory transferred to the old space each second. Due to the infant mortality of Java objects, this value should always be much smaller than the allocation rate. One indicator of critical situations is a high ratio of promotion rate to allocation rate, since this implies efficient use of the Eden space cannot be made.

Promotion Rate (Cluster wide)[KB/s]

28

Hostname Cluster Element ID Average [KB/s]

xxx.xxx.com

=============================================================================

Do let me know if I am missing something.

Thanks,

[former_member209604 · Accepted solution]

Hi Paresh,

Is your SolMan on ST-SER 700_2008_1?

Ruediger

[Former Member · Accepted solution]

Hi Ruediger,

I am on 700_2007_1 Patch 0003 - SAPKITLOM3.

Do I need to go to the latest ??.

Thanks,

Paresh.

[former_member209604 · Accepted solution]

Hi Paresh,

Your SolMan runs with a not recommended (not tested) combination of Support Packages.

You should always apply the complete Stack (ABAP and JAVA) and not to patch single components (if they are linked to other components).

Maintenance for ST-SER 700_2007_1 ends on 31.03.2008, it has been replaced by ST-SER 700_2008_1.

My recommendation:

- apply the full SolMan Stack 15

- return to SAP or this forum, in case EWA does not work as expected.

See also SAP Note 976054.

Best regards,

Ruediger

[former_member209604 · Accepted solution]

Have you see the [Sample Report EWA Report for JAVA Systems|http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000034315&_SCENARIO=01100035870000000202&_OBJECT=011000358700000250462008E]?

This gives an impression, what you can expect.

Ruediger

[Former Member · Accepted solution]

Hi Ruediger,

I finally got the EWR running.

the "temp" directory under "SMDAgent" did not have write permission. I guess this is required.

I applied latest ST-SER.

Thanks for the Help