| Author |
Message
|
| sebastia |
 Posted: Wed Dec 24, 2008 5:16 pm Post subject: SAP data trace |
 |
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Some time ago ( ) I was working with ICS (Interchange Server)
and the product had a RFC trace of the data sent/received to/from SAP
(see some sample at bottom)
My question is : is there anything similar in MB 6.1 ?
Thanks. Seb.
+++
>>> RfcDispatch [9] ...
Received RFCHEADER [9]: 01/LIT/IEEE/SPACE/1100
UUID: ab_rfccheck_uuid take uuid over {E7A2AC89-E5D2-49C9-ABFF-E90086DBDEF7}
>>>> [9] Dispatch call to:RFC_PING
>>> RfcGetData [9] ...
*> RfcGetData
handle = 9
parameter = <NULL>
tables = <NULL>
Data conversion On
UUID: ab_rfccheck_uuid compare uuid's {E7A2AC89-E5D2-49C9-ABFF-E90086DBDEF7}
***Discarding unrequested T:RFCTAB40
<* RfcGetData [9] : returns 0:RFC_OK
>>> RfcSendData [9] ...
*> RfcSendData
handle = 9
parameter = <NULL>
tables = <NULL>
>>>> [9] < accepted > : REG <ac: 329> L hepere >>> FLUSH (READ) (84095902)
-{E7A2AC89-E5D2-49C9-ABFF-E90086DBDEF7}
Send RFCHEADER: 01/LIT/IEEE/SPACE/1100
Send UNICODE-RFCHEADER: cp:1100/ce:IGNORE/te:REJECT/cs:1/rc:0x00000023
Transport RFC Enqueue-Key 5FA103E4FDD34BEFA8DA9BC65B74931E
UUID: send_rfcuuid {E7A2AC89-E5D2-49C9-ABFF-E90086DBDEF7}
UUID: RfcBackNew send the uuid to the partner {E7A2AC89-E5D2-49C9-ABFF-E90086DBDEF7}
>>>> [9] < accepted > : REG <ac: 330> L hepere >>> WRITE (84095902)
-{E7A2AC89-E5D2-49C9-ABFF-E90086DBDEF7}
000000 | 01010008 01010101 01010000 01010103 |................|
000010 | 00040000 020B0103 0106000B 01010000 |................|
000020 | 01000100 00002301 06000700 0F313932 |......#......192|
000030 | 2E313638 2E323534 2E313436 00070011 |.168.254.146....|
000040 | 00015200 11001200 04363430 20001200 |..R......640 ...|
000050 | 13000436 34302000 13000800 20736572 |...640 ..... ser|
+++ |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Dec 24, 2008 6:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I believe that this has little to do with MB and more with SAP. Did you try turning on the trace on the SAP JCO ? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sebastia |
| Posted: Thu Dec 25, 2008 2:42 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Hi again, mr Saper.
I need a toll to be able to know what I am sending to SAP,
so I can not rely on their tools ..
On the ICS, there was this RFC trace,
which looks ok to me,
but I cant find it in MB.
I agree I am quite new to MB, so ... maybe it is there
This is why my answer to your
"Did you try turning on the trace on the SAP JCO ?"
is NO,
because I dont know what you are talking about, sorry.
Give me just one pointer, pls (beside "Google), ) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Dec 25, 2008 6:48 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You need to talk to your SAP folks. They can tell you where to find the SAP connection tools (JCO) and relevant documentation. AFAIK the connector uses SAP JCO. You can get an RFC trace from the SAP JCO, but this will not show the data passed. It is more a tool to determine connection problems. See your adapter documentation on how to set the trace and trace level.
If you need a list of IDOCs SAP can give you that information using transactions like WB05 or W?05..., not using it every day my memory gets a little bit hazy there. This will show all Idocs received or sent per time period grouped by status, time frame (day/hour?) etc....
If your adapter is sending the IDOCs in a transactional manner there should be no discrepancy on either side. (See adapter documentation and JCO documentation to understand what is happening behind the scene)
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sebastia |
| Posted: Fri Dec 26, 2008 10:35 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
mr Saper : my schema is as follows - correct me if I am wrong
So, in "machineA" area there is np SAP boy involved ....
They receive (at B machine) a nive IDOC or reject it
I want to see it at "A", and that was available with ICS,
data included (in HEX)
so i guess i have some right o request it on MB v 6.1
( )
+++
<-- machine A --> <- machine B ->
.------.----------. .--------.
| | | | |
| | SAP | (1) | |
| MB | Adapter | <------> | SAP | (1) XML over HTTP using JCO RFC [1] | | | | |
| | | | |
.------.---------. .--------.
+++ |
|
| Back to top |
|
|
| sebastia |
| Posted: Fri Dec 26, 2008 10:41 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
let me re-draw it :
+++
<-- machine A --> <- machine B ->
#======#==========#.............#========#.
|...............|........................|..............|....................|
|...............|.........SAP.........|.....(1).....|................... |
|.....MB......|.....Adapter.......|.<------>.|....SAP...........|...(1)
|...............|........................|..............|....................|
|...............|........................|..............|....................|
#======#==========#.............#========#
+++ |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 26, 2008 11:23 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Like I said the SAP RFC connection between the SAP adapter and SAP can be debugged by setting the log level on the SAP Adapter (JCO).
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sebastia |
| Posted: Fri Dec 26, 2008 11:33 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
mr Saper - many thanks for your patience.
Now I got it : the trace is to be set "ON THE SAP ADAPTER"
(whatever "JCO" means),
so it has to be in "our" part of the connection.
Will try some "InfoCenter" search - I never never liked it (InfoCenter),
but have to agree sometimes it provides incredible (search) results.
HNY ! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 26, 2008 11:44 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| sebastia wrote: |
mr Saper - many thanks for your patience.
Now I got it : the trace is to be set "ON THE SAP ADAPTER"
(whatever "JCO" means),
so it has to be in "our" part of the connection.
Will try some "InfoCenter" search - I never never liked it (InfoCenter),
but have to agree sometimes it provides incredible (search) results.
HNY ! |
SAP also has the capability do debug an incoming RFC communication. However that will help little if the communication never makes to the SAP box. You're on the right path there. Check the adapter doc for the log level setting. If you do not find it, and as the Adapter uses the JCO (Java Connector) behind the scenes you can also set that flag on the JCO. How to do this should be specified in the SAP JCO documentation available from the SAP site.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sebastia |
| Posted: Fri Dec 26, 2008 11:49 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Thanks, mr Saper - you are right : everything has to be done
on MY part of the connection.
The guys on the "host" or "SAP" computer ...
... just sit there and say :
"what you send is not properly formatted,
so we just reject it and can't say anymore".
JeJeje - I am only 1/2 of the time joking.
Next objective : adapter doc, looking for "(RFC) trace" |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 26, 2008 4:41 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| sebastia wrote: |
Thanks, mr Saper - you are right : everything has to be done
on MY part of the connection.
The guys on the "host" or "SAP" computer ...
... just sit there and say :
"what you send is not properly formatted,
so we just reject it and can't say anymore".
JeJeje - I am only 1/2 of the time joking.
Next objective : adapter doc, looking for "(RFC) trace" |
Tell them to be more precise. If the IDOC got accepted even though it is badly formatted it should still go into an error status and you could check for the reasons in the status detail messages.
If the IDOC never got accepted you should have some kind of status message at the adapter saying the IDOC did not make it to SAP.
Debugging the connection will help this part.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sebastia |
| Posted: Sat Dec 27, 2008 3:46 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
A bit more serious this time, mr Saper,
I have to say that the "problem" with SAP people
may start when they are a consultant from another company that I am,
so I have no way to put any pressure on them.
Last time, by example, the SAP guy was a "developer",
but had al most no idea about communications, RFC, BAPI, etc.
We were worried about the size of a IDOC,
and there was no way they could tell us this value !!!
A high level guru of their company said "500 KB",
and 2 months later I found it to be ... 5 KB
I am sure you already know what I am talking about.
Many thanks for your support and ideas. |
|
| Back to top |
|
|
| Maximreality |
| Posted: Tue Dec 30, 2008 5:47 am Post subject: Re: SAP data trace |
|
|
Acolyte
Joined: 04 Jun 2004
Posts: 65
Location: Copenhagen
|
This information is available Ãn SAP transaction st11
I am pretty sure you can config the SAP adapter to provide the same information as the ICS has. There is probably a setting in the config file.
In MB v6.1 you can configure the build in SAP nodes to save the rfc trace in a local file.
I don't think this would be a good idea in a production environment, since it is there only for debugging purposes
/Rasmus |
|
| Back to top |
|
|
| sebastia |
| Posted: Wed Jan 07, 2009 11:23 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Maxim - I think this is what I am looking for ...
"configure the build in SAP nodes to save the rfc trace in a local file"
Can you provide any kind of pointer on HOW IS IT DONE ?
Sebastia. |
|
| Back to top |
|
|
| Maximreality |
| Posted: Mon Jan 12, 2009 3:28 am Post subject: |
|
|
Acolyte
Joined: 04 Jun 2004
Posts: 65
Location: Copenhagen
|
Go to your adapter component in the workspace
Press "Show Advanced"
Go to "SAP RFC trace configuration"
Then you can check mark "RFC trace on", set the trace level and choose folder to save the RFC trace files in. |
|
| Back to top |
|
|
|
|
