Transaction to monitor system performance in ECC & PI

[Former Member]

Hello! All

WE are in the process of executing some high volume interface loads and needed help in getting the list of transaction which help monitor the system performance during high volume executions.

1. PI: Usually monitor SMQ1, SMQ2 -> However can you please let us know of how these queues re-started or registered so that when messages are flowing through slower than usual and if there is anything we can do to increase the no.of message the Queue can hold?!
   • -> What other transaction can we trigger to monitor the performance during peak volume.
   • -> Transaction for prioritization of queues.
2. ECC: Similar to ST06 which is more on the system recourse utilization in , what other transaction can trigger to monitor the system during peak volume - especially peak volume of IDOC's. For example no.of dialog processes existing and the one which are being utilized - so that we can analyze scope for more dialog processes to be requested with Basis to increase the messages being processed in inbound & outbound Queue..

The above requested information would greatly help in getting us through the high volume loads by aiding us monitor and raise issue proactively with Basis folks. Please, reply with any info you have with previous experiences with high volume with regard to monitoring of bulk IDOCs flowing from ECC to PI ; your help is greatly appreciated!!

Thank you,

Ritu

[Former Member]

Hello,

for PI the management console is always a good point for viewing threads, heap, processes and much more. You can start the MMC via http://<hostname>:5xx13 (port 13). Here you become a good entry for checking java engine, abap stack and ICM.

Depending on your current version DBACOCKPIT is quite good TA- from there you can jump into DB02, ST04 and some other TAs.

Some other usefull ABAP-TAs might be:

• SM50/ SM66 for work processes (local and global)
• SM58 tRFC monitor
• ST03 system statistics
• ST02 buffers
• ST10 table access
• STAD/ STATTRACE statistics
• ST04/ DB02 database tables/ database activities
• WE07 IDoc statistics
• BD87 IDoc status monitor
• WEINBQUEUE IDoc inbound queue; WEOUTQUEUE IDoc outbound queue

BR,

Phillip

[Former Member]

Use DB02

[Former Member]

Hi,

I am sure this list of relevant transactions will help:-

http://wiki.sdn.sap.com/wiki/display/XI/XI+Transaction+Codes

Thanks,

Atul.

[baskar_gopalakrishnan2]

For message packaging implementation , you might want to go through this link

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b54994-f569-2a10-ad8f-cf5c68a94...

To understand and use various component of monitoring

http://help.sap.com/saphelp_nw70/helpdata/en/88/21bc3ff6beeb0ce10000000a114084/content.htm

How to prioritize XI messages

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972a...

Tuning PI message queues

http://scn.sap.com/community/pi-and-soa-middleware/blog/2011/01/26/tuning-the-pi-messaging-system-qu...

Hope that helps.

[Former Member]

Hi,

Please make use of the SAP NWA (http://<hostname>:50000/nwa) to monitor your Memory consumption, thread usage and memory usage in High peak load situation.

Also, you can use SAP Memory Analzer Tool.

Transactions : RZ20 (Health of J2ee Engine)

                      SMGW and SMICM.

From ECC Side :

SM50 and SM66 are useful transactions for Dialog Process.

[rajasekhar_reddy14]

Hi Ritu,

Consider implementing message packaging and queue prioritization for specific high volume interfaces

search in scn you will find use full docs on the same.

Queue prioritization SXMB_ADM -> Configure filter for Queue prioritization then give necessary details.

Sending bulk IDoc like 1 lacs IDoc to PI in hour time not possible like the performance depend on connectivity between PI and ECC, in your case you can keep on checking SMQ2 and Adapter engine at target side like how many messages were flowing to target system.

SAP ECC-PI IDoc commutation always gives good performance so i dont think you would face any problem at outbound side.

Regards,

Raj