on 02-23-2006 1:33 PM
hi
I just wanted to know that is it possible to do debugging in SAP XI, as we perform in ABAP.
The way we perform step by step process in ABAP, can we do the same way as in ABAp, Kindly let me know.
thanks and regards
sreddy
Hi Reddy,
As your requirement, the best possible way, you can test step by step in SAP XI can be done in "Integration Directory".
Choose "tools --> Test Configuration".
here give the required details of your scenario and test in which step your scenario has gone wrong.
may be this is wat u r looking for. And for more monitoring and other stuffs, there are lot of things as said by others previously.
regards,
P.Venkat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hey guys,XI we cannot debug ,its is monitoring and tracing the error,debugging is done for codes,I would like to add one thing to the above update ,the testing tool in ID is just for the name sake,it does not give u a clear picture if you have distributed environment consisting of numerous interfaces and also of the objects are re used,so follow the std procedure for checking errors
SXMB_MONI>open the error message>get the error message-->open the trace and scroll down to the buch of trace paragraph you see,u will get a clear picture of the error
If your error is not traced in Moni ,you can use RWB and check message monitoring for messages in error after hitting adapter or you can check component monitoring to check which compnent ie adapter engine,adapters,com channels in error ,accordingly u can take action
Hi Reddy,
You cannot do the kind of debugging you do in ABAP in SAP XI.The debugging in ABAP is quite powerfull and also step by step....All that you can do here is just monitoring, it indeed has very powerfull monitoring capabilities.and for the various monitoring capabilities of SAP XI, i think the previous answers would have helped you.
But one thing that i just wanted to add to is about the Debugging of RFC calls which you can do using XI.To know more about the same please go through the following link.
/people/michal.krawczyk2/blog/2006/01/17/xi-debugging-rfc-calls-from-the-xi-not-possible-who-said-that-
Regards,
abhy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The better term here in XI to use is Monitoring rather Debugging. Because XI provides rich set of Monitoring capabilities.
You can see your message at any stage in XI. This can be viewed with the help of Runtime WorkBench(RWB) i.e one of the component of XI.
Some options of Debugging/Monitoring are:
1)To debug your Mapping you have Test Tab in the Mapping
Editor.
2) To debug integration Process(BPM) go to Process Engine and debug the same. (Tcode SXMB_MONI_BPE)
I think many more are already discussed..
Hope this helps..
Regards,
Moorthy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think it´s imposible to debug step by step in XI. The best way I know is with SXMB_MONI transaction and the Runtime Workbench.
Regards,
RCV
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Check these,
/people/michal.krawczyk2/blog/2006/01/17/xi-debugging-rfc-calls-from-the-xi-not-possible-who-said-that-
cheers
Sameer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As far as I know, you cannot debug XI like ABAP. There is a possibility of debugging of ABAP mapping. Other than this, I do not think you can debug XI like ABAP.
Regards
Shravan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shrvan,
No offence intended here, but,I am not an ABAPer,and I ve got no idea as to how debugging in ABAP is done.
But, in the case of XI, at times ( not always ) I have found that the error message thrown by XI does help us in locating the source of error or reason as to why the error is occuring. Don't you think so too??
Regards,
Bhavesh
Hi Reddy,
XI does provide some debugging mechanisms.
1. T CODE - <b>SXMB_MONI</b> You can use this to see the entire flow of your message along with the payload and the graphical flow of your message processing.
2. <b>ADAPTER MONITORING</b> This allows you to trace out the errors and problems occuring in your Adapters running on the j2ee engine.
3. <b>END to END Monitoring</b> This is similar to your SXMB_MONI and allows you to monitor the entire message flow.
4. <b>PERFORMANCE MONITORING</b> This is used to monitor the performance of your entire XI server.
Options 2,3,4 are available under RunTimeWorkBench.
Also, go through these links for further info,
http://help.sap.com/saphelp_nw04/helpdata/en/41/b715045ffc11d5b3ea0050da403d6a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/96/0a2441509fa831e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5a/f72040599a8f5ce10000000a155106/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/25/9c2f3ffed33d67e10000000a114084/content.htm
Hope this helps,
Regards,
Bhavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.