The goal of error identification is to ensure the operating readiness of the J2EE Engine and the deployed applications through regular and automated checks.
The following checks can be regularly performed:
Task |
More Information |
Describes how you can view the JLaunch traces using the SAP Management Console (MMC). |
|
Helps you to check whether the J2EE Engine and the individual components are running? |
|
Describes how you can check the availability of your monitored systems and the associated instances. |
|
Describes how you can work with the CCMS Alert Monitor (transaction RZ20) |
|
This regular task can help you find answers to the following questions: · Are the servers of the Java cluster running? · Is the database running? · Is the Web Container running? · Can I connect to the Visual Administrator? |
|
Describes how you can display monitoring data from a central monitoring system (CEN) in a simple and clear interface in the NWA. |
|
Describes how you can use the NWA to monitor the J2EE Engine cluster, observe the performance of the selected Java system, analyze and detect the root of problems in J2EE Engine performance degradation situation, and to make motivated tuning for productive use with J2EE Engine. This procedure describes how you can monitor the performance of your J2EE system using the NWA. However, if you need to do make some adjustments and additional configuration to your performance analysis system, you have to use the Visual Administrator. For more information, refer to the next task from this table – Monitoring Performance and Resource Usage.
|
|
Use this task to check whether the system resources are overloaded and the performance is acceptable. The described procedures are performed in the Visual Administrator. |
|
Use this task to make constant checks for error messages. |