Hi Vamshi,
Your question is quiet OPEN, becuase as such we have a lot of options for monitoring the J2ee stack.
As far as T-Code is concerned you might have it in the system where in ABAP stack too exists.
Because the T-Code work only for an ABAP system and they no way exist for a standalone J2EE stack based systems.
So Based on certain Assumptions, For Java Stack monitoring you could use the following options as per your Setup:
Incase of a Dual Stack, (ABAP + J2EE stack), you have the following options available:
Few useful T-Code: SMICM to monitor your J2EE status and its port and service active
ST11 to analyze your dev_server, debv_dispatcher , dev_icm, dev_jcontrol, dev_bootstrape and so on.
SICF : to check for ur service status on the j2ee based system
SLDCHECK: to chck the SLD config and its.
Apart from these we have the J2ee startup page (http://hostname:(50000+SysNr*100)),
There we have NWA , System information.
For NWA (Netweaver admin) you have a preety good monitoring setup guide available on Service Market Place.
On OS Level we have jcmon tool to monitor and troubleshoot your j2ee stack main processes.
Better would be you first do a first level reading on different things and then decide on what exactly fits your requirement and proceed further:
Regards,
Prem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.