cancel
Showing results for 
Search instead for 
Did you mean: 

XI monitoring

Former Member
0 Kudos

Hi Experts,

Please describe the Monitoring task that need to be folowed by the Production Support for the following scenarios:

FIle to File(FTP) using BPM

IDoc to JMS

JMS to IDoc

File to HTTP

For troubleshooting the message in and out of XI.

should they have to monitor the Memory and Performance issues ? If yes, how?

Are these issues will be monitored by Basis?.

Please answer my above questions/

Thanks in advance.

MK

Edited by: mk.xi on Feb 28, 2008 12:14 PM

Accepted Solutions (0)

Answers (3)

Answers (3)

aashish_sinha
Active Contributor
0 Kudos

HI,

>>>Please describe the Monitoring task that need to be folowed by the Production Support for the following scenarios:

FIle to File(FTP) using BPM

IDoc to JMS

JMS to IDoc

File to HTTP

Just logon to your Production environment's RWB and here you can see Message Monitoring, Communication Channel monitoring, end to end monitoring and also performance monitoring. Using all these things you will be able to monitor everything for above scenarios.

Regards

Aashish Sinha

PS : reward points if helpful

0 Kudos

Hi,

Generally in production support we have to do the monitoring using SMQ2, SMQ1 and SXMB_MONI for message related issues

For BPM Related issues we should monitor using SXMB_MONI_BPE if we find any error in bpm we should restart those messages.

For Adapter Specifimonitoring in the application we should use RWB in that we can check the performation for adapters.

Regarding memory issues we should monitor in event management which is available CMS tool in that we can check the performance issues.

Generally Application specific issues we can slove as a developer but regarding performance and other issues we should approach XI BASIS team

Hope the above message helps you.

nisarkhan_n
Active Contributor
0 Kudos

XI Monitoring is done using the CCMS alerts and Alert Definitatoin.

CCMS alerts will monitor your AE and IS as a whole so any error in the following components during runtime is captured in CCMS and sents a error mail to the respective mail id maintained.

for the below scenario

FIle to File(FTP) using BPM

IDoc to JMS

JMS to IDoc

File to HTTP

There are two things in monitoring...any error occuring on the system or in simple word any error in the pipeline steps you can leave it to CCMS.

In addition you can configure the CCMS to sent mail if any queues are also blocked.

Second: you can define the alerts using alert definitation this is more customized errors handling may be general or specific to interface.

Follow the links to perform the CCMS alerts:

CCMS ALERTS:

/people/sap.user72/blog/2005/11/24/xi-configuring-ccms-monitoring-for-xi-part-i

/people/sap.user72/blog/2005/12/05/xi-grmg-customizing-for-xi-ccms-heartbeat-monitoring-part-ii

/people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3

You can search in SDN for more links

************************************************************

For troubleshooting the message in and out of XI should they have to monitor the Memory and Performance issues ? If yes, how?

Are these issues will be monitored by Basis?.

Yes for trouble shooting related to the server performance they have to monitor the server mainly look into the memory paramters, if there are not enough dialog process available then the data will get stuck in the queue most of the times, int these cases they have to release few or increase number of queues, but for any interface releated troubleshooting develope should take care of it.

There are many more things which has to be taken care but these were few ex:

forex: they canuse ST06 to see the CPU usage, RWB allows to run the performance monitoring

For performance related links :

You need to fien tune the performance

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/sap%20excha...

4) check these threads-

See below link to trace the whole which affects the Performance

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/489f5844-0c01-0010-79be-acc3b522...

Performance monitoring of service calls

/people/soum.chatterjee/blog/2007/12/19/performance-monitoring-of-service-calls

NetWeaver Performance: A Customer Point of View

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e1a61c36-0301-0010-06be-d34e2f37...

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0b4580be-0601-0010-d3ad-bd6...

Former Member
0 Kudos

Thanks khan.

we need to monitor the interfaces without CCMS and Alerting, as they are not yet configured.

please explain the different monitoring task that need to be followed by the production support team for the mentioned scenarios above.

Former Member
0 Kudos

Hi,

Monitoring:

FIle to File(FTP) using BPM

IDoc to JMS

JMS to IDoc

File to HTTP

For all the above scenario u need to first check teh status of SXMB_MONI. if it is sucess full then

1) for file scenario check the target directory whetehr file is generated or not.

2) For IDOC: go to WE02 transaction ans see the IDOC status and see whether IDOC is generated or not.

3) JMS see the JMS queue for the message.

if it is not sucessful then debug the scenario

1) For file:

Check the RWB file adapter status.

Check the source file directory whether file is pcicked up or not.

If file is not picked up then check the file adapter configuration parameters.

Check the rights on FTP folder.

2) IDOC:

Check the configuration at R3 as well as XI end.

3) JMS see the configuration of JMS adapter.

Apart from Monitoring u need to troubleshoot the scenarios as well.

For support activity:

Refer the XI troubleshooting guide this will help you.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd5...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/108ba391-e826-2a10-608f-c1769c51...

SLD guide:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/652b1f46-0a01-0010-25ae-e7cb07b5...

HTTP error debugging:

/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

Troubleshooting File-to-IDOC Scenario in XI.

/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

troubleshooting SOAP:

/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi

Proxy:

Debugging Inbound Proxy:

/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation

SPROXY not working:

/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies

Thnx

Chirag

Edited by: Chirag Gohil on Feb 28, 2008 9:53 AM

Former Member
0 Kudos

Hi,

The XI Production support activities are classified into :

1.Monitoring and Operations Support

2.Bug fixing, patching and enhancements

3.Disaster Recovery

Please find here with you the details about it

/people/prashanth.azharuddin/blog/2006/11/24/some-errors-in-an-xi-production-environment

Thanks

Swarup