3
8/18/2015 PI Application Support Daily Checklist | SCN http://scn.sap.com/docs/DOC39556 1/3 Getting Started Newsletters Store Products Services & Support About SCN Downloads Industries Training & Education Partnership Developer Center Lines of Business University Alliances Events & Webinars Innovation Log On Join Us Hi, Guest Search the Community Activity Communications Actions Browse 0 Tweet 0 created by Suseelan Hari on Mar 22, 2013 11:31 AM, last modified by Suseelan Hari on Mar 22, 2013 11:48 AM This blog shows PI Application Support Daily Checklist: Note: This checklist is for the application support team to ensure that SAP PI and B2B server are running smoothly. There is error alerting built in, but is still in the initial stages of configuration and as a result does not catch everything. This checklist should be completed daily at least until the team has confidence in the alerting from PI. Integration Engine: ABAP Commands: 1) SXMB_MONI (“Integration Engine: Monitoring”) → “Monitor for Processed XML Messages” – check for any errors that may have happened since the previous check was completed (putting 48 hours should ensure this). 2) SMQ1 (“qRFC Monitor (Outbound Queue)”) – check to see if there are any queues stuck. An indicator of this would be seeing multiple entries in a queue. Ideally, you would see “Nothing selected”. 3) SMQ2 (“qRFC Monitor (Inbound Queue)”) – same as the outbound queue. 4) SM58 (“Transactional RFC”) – Fill the User Name field with “*” and execute. Ideally you would see “Nothing was selected”. If not, try refreshing to see if things are processing. 5) SXMB_MONI_BPE : check for failed processes under a. Restart Process After Error:. if any process found analyze and restart as applicable b. Restart Process After System Crash: Check for any process failed, these processes are restart able, restart such a process Adapter Engine: Runtime Workbench Monitoring: 1) Component Monitoring 2) Message Monitoring (Integration Server) – check for messages with Status: To Be Delivered, Waiting, Holding, System Errors, All Containing Errors. 3) Alert Inbox – check for alerts which are not confirmed, and if any are found, resolve the triggering cause of the PI Application Support Daily Checklist Share 0 Like Version 2

PI Application Support Daily Checklist _ SCN.pdf

Embed Size (px)

Citation preview

Page 1: PI Application Support Daily Checklist _ SCN.pdf

8/18/2015 PI Application Support Daily Checklist | SCN

http://scn.sap.com/docs/DOC39556 1/3

Getting Started Newsletters Store   

Products Services & Support About SCN Downloads

Industries Training & Education Partnership Developer Center

Lines of Business University Alliances Events & Webinars Innovation

Log On Join UsHi, Guest Search the Community

Activity Communications Actions

Browse

0 Tweet 0

created by Suseelan Hari on Mar 22, 2013 11:31 AM, last modified by Suseelan Hari on Mar 22, 2013 11:48 AM

This blog shows PI Application Support Daily Checklist: 

 Note: This checklist is for the application support team to ensure that SAP PI and B2B server are running smoothly.  There iserror alerting built in, but is still  in the initial stages of configuration and as a result does not catch everything.  Thischecklist should be completed daily at least until the team has confidence in the alerting from PI.   Integration Engine:

ABAP Commands: 1)       SXMB_MONI (“Integration Engine: Monitoring”) → “Monitor for Processed XML Messages” – check for any errorsthat may have happened since the previous check was completed (putting 48 hours should ensure this).       2)       SMQ1 (“qRFC Monitor (Outbound Queue)”) – check to see if there are any queues stuck.  An indicator of thiswould be seeing multiple  entries in a queue.  Ideally, you would see “Nothing selected”. 3)       SMQ2 (“qRFC Monitor (Inbound Queue)”) – same as the outbound queue. 4)       SM58 (“Transactional RFC”) – Fill the User Name field with “*” and execute.  Ideally you would see “Nothing wasselected”.  If not, try refreshing to see if things are processing.5)       SXMB_MONI_BPE : check for failed processes undera.       Restart Process After Error:. if any process found analyze and restart as applicableb.       Restart Process After System Crash: Check for any process failed, these processes are restart able, restart sucha process Adapter Engine: Runtime Workbench Monitoring:        1)       Component Monitoring2)       Message Monitoring (Integration Server) – check for messages with Status: To Be Delivered, Waiting, Holding,System Errors, All Containing Errors. 3)       Alert Inbox – check for alerts which are not confirmed, and if any are found, resolve the triggering cause of the

PI Application Support Daily Checklist

Share 0Like

Version 2

Page 2: PI Application Support Daily Checklist _ SCN.pdf

8/18/2015 PI Application Support Daily Checklist | SCN

http://scn.sap.com/docs/DOC39556 2/3

Average User Rating

(6 ratings)

0 Tweet 0

alert.

1422 Views  

Share 0Like

7 Comments

Like (0)

Samiullah Qureshi Apr 17, 2013 6:40 AM

Hi Suseelan Hari, It there was server crash/shut down, it is also suggested to check SXI_MONITOR and SM58 of ECCsystem. If there was any message/Idoc sent to PI during the outage then you will see its entry there.  Regards,Sami.

Like (0)

Suseelan Hari Apr 17, 2013 6:31 AM (in response to Samiullah Qureshi)

Hi Sami,     Whenever there is application shutdown, background jobs in ECC will be stopped.For example, if it is IDOC to File Scenario, Messages/ IDoc will not follow through PI. Youwill not see any messages in PI system. After the outage, all the messages will processsuccessfully. Regards,Hari Suseelan

Like (1)

Samiullah Qureshi Apr 17, 2013 6:52 AM (in response to Suseelan Hari)

Yes. You are right. Message will not reach to PI during outage. However, message/ Idoc may trigger from ECC system and will not reach to PI due to outage.Therefore, it will be a good idea to check SM58 and SXI_MONITOR of ECCsystem for any unplanned outage. Thanks.

Like (2)

Aaron Myers Apr 29, 2013 10:21 PM

This is a nice check sheet Hari. From performance section of RWB, you could also record average message size / speed. This mighthelp you confirm that speed and volume have been consistent.

Like (0)

Suseelan Hari May 8, 2013 8:35 AM (in response to Aaron Myers)

Thanks Aaron!

Like (1)

Raja S Malledi May 8, 2013 8:55 AM

Hi Hari,Good work,we have to check background job overview with sm37,and we have clear cache with sxi_cache. RegardsRaja

Page 3: PI Application Support Daily Checklist _ SCN.pdf

8/18/2015 PI Application Support Daily Checklist | SCN

http://scn.sap.com/docs/DOC39556 3/3

Follow SCNSite Index Contact Us SAP Help PortalPrivacy Terms of Use Legal Disclosure Copyright

Like (0)

Suseelan Hari May 8, 2013 10:25 AM (in response to Raja S Malledi)

Thanks Raja. Yes. You are correct!