| Author |
Message
|
| MrVMax |
 Posted: Sun Oct 12, 2014 6:39 am Post subject: SAPOutBound_* adapter abnormal behavior |
 |
|
Novice
Joined: 01 Aug 2013
Posts: 23
|
Hi all, I've found a very strange behavior into the adapters in the subject this post is a short resume of what happened version but still very boring ...
I'm working on a Websphere Message Broker 8.0.0.2 and have to communicate with SAP. Both servers are installed different wmware virtual Linux Redhat 64 bit boxes.
I've 3 different Websphere Message Broker Toolkits each one at a different level on different harware configuration:
1) level 8.0.0.2 that runs on a virtual windows seven box 32 bit
2) level 8.0.0.3 that runs on a physical windows seven 64 bit
3) level 8.0.0.4 that runs on a virtual windows seven box 32 bit
I did the discovery of the Idoc structure in the July 2013 and the adapters and the flows worked fine till last week.
The SAP people last week asked for some change in a flow that required a field that i couldn't find in the Idoc structure discovered in July. That was startling for me and i decided to delete, on a single Websphere Message Broker Toolkit, the adapters and the discovered Idoc structures to replay the discover process that took me to find out the missed Idoc fields and now I could change the requested flow.
All good till this point, but meanwhile I had to deploy in the production environment another flow that was under test on a different box. I rebuild the bar and deployed it into the production environment and this started a lot of trouble.
After the activity the Idoc sent to SAP have correctly filled the Control record and the main segment, but no evidence of about 50 other segments sons of the main segment. I put a trace node in the flow between the process node and the ALE Request that sends the Idoc to SAP, redeployed the flow and I saw that the missed Idoc segments are fully populated as the specifications says till the trace node and the flow receive the SAP transaction code, no excemption on the broker, no warn, nothing abnormal.
All the activity just described was made on the nr. 1 Websphere Message Broker Toolkit so I put all the code and flow on the nr. 2 Websphere Message Broker Toolkit rebuild the bar and redeployed the flow and everything is working fine in the production environment because on the nr. 2 box the discovered Idoc structure is still the one got in July.
I made from a snapshot of the Broker server another virtual machine calling it "scratch" to make some investigation and I deployed in two different moments the flow from the toolkit 1 and 2 sending the same mqseries message both the time and took two trace output one for toolkit. Both the traces cleared from the time at the start of the rows are identical but the Idoc on the SAP test box are different, one with all the segments and one with only control and main segments.
Figuring that the trouble could be in the sapjco or idocjco I upgraded on the check server both from sapjco3-linuxx86_64-3.0.9 and same level idocjco to sapjco3-linuxx86_64-3.0.11 and sapjidoc30P_11-10009485 with no difference at all from the previous behavior. Obviously, I did it both on the toolkit and the server making the discovery process another time creating a new empty workspace.
Now I'm about to update the "scratch" Websphere Message Broker to level 8.0.0.4 just to be in the best situation to open a PMR to Ibm, but i think the trouble is on SAP side.
Can anyone think of a different approach to the trouble? Any idea, suggestion or whatever? Anyone experimented trouble like this one ?
Thanks in advance for any comment ...
Best reward
B.T.W. I advised the SAP people to open a defect with SAP, but I've no rights to tell them what to do. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun Oct 12, 2014 7:16 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Check with IBM for APARS with the SAP adapter. I believe there's been a few.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| MrVMax |
| Posted: Sun Oct 12, 2014 10:15 am Post subject: |
|
|
Novice
Joined: 01 Aug 2013
Posts: 23
|
Many thanks fjb_saper,
but after the Fix Pack 8.0.0.4 for WebSphere Message Broker on Linux x86-64*
released on 03/31/2014 on the fix central site no fix results related with SAP ... am I missing something else ? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Oct 12, 2014 3:17 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
| MrVMax wrote: |
Many thanks fjb_saper,
but after the Fix Pack 8.0.0.4 for WebSphere Message Broker on Linux x86-64*
released on 03/31/2014 on the fix central site no fix results related with SAP ... am I missing something else ? |
I knew there were problems up to and including 8.0.0.3. Hopefully they've all been fixed in 8.0.0.4....
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| MrVMax |
| Posted: Sun Oct 12, 2014 10:13 pm Post subject: |
|
|
Novice
Joined: 01 Aug 2013
Posts: 23
|
Now I've updated the "scratch" box to 8.0.0.4 and tried with the same data message but still no change ...
Just to add some detail here is a a snip from the trace node that is just before the SAPRequest Node that sends the Idoc to SAP ...
********
* Root: *
********
( ['MQROOT' : 0x7f92b8b13820]
(0x01000000:Name ):Properties = ( ['MQPROPERTYPARSER' : 0x7f92b8253290]
(0x03000000:NameValue):MessageSet = '{}:SAPCremas05' (CHARACTER)
(0x03000000:NameValue):MessageType = '{}:FoamSap' (CHARACTER)
(0x03000000:NameValue):MessageFormat = 'XML1' (CHARACTER)
(0x03000000:NameValue):Encoding = 273 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 819 (INTEGER)
(0x03000000:NameValue):Transactional = TRUE (BOOLEAN)
(0x03000000:NameValue):Persistence = TRUE (BOOLEAN)
(0x03000000:NameValue):CreationTime = GMTTIMESTAMP '2014-10-06 18:27:32.600' (GMTTIMESTAMP)
(0x03000000:NameValue):ExpirationTime = -1 (INTEGER)
(0x03000000:NameValue):Priority = 0 (INTEGER)
(0x03000000:NameValue):ReplyIdentifier = X'414d5120514d475241202020202020207ada31549b990520' (BLOB)
(0x03000000:NameValue):ReplyProtocol = 'MQ' (CHARACTER)
(0x03000000:NameValue):Topic = NULL
(0x03000000:NameValue):ContentType = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceType = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceToken = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourcePassword = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceIssuedBy = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedType = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedToken = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedPassword = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedIssuedBy = '' (CHARACTER)
)
(0x01000000:Name ):MQMD = ( ['MQHMD' : 0x7f92b8160940]
(0x03000000:NameValue):SourceQueue = 'SAGI_2010_FOAMSAP_IN' (CHARACTER)
(0x03000000:NameValue):Transactional = TRUE (BOOLEAN)
(0x03000000:NameValue):Encoding = 273 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 819 (INTEGER)
(0x03000000:NameValue):Format = 'MQSTR ' (CHARACTER)
(0x03000000:NameValue):Version = 2 (INTEGER)
(0x03000000:NameValue):Report = 0 (INTEGER)
(0x03000000:NameValue):MsgType = 8 (INTEGER)
(0x03000000:NameValue):Expiry = -1 (INTEGER)
(0x03000000:NameValue):Feedback = 0 (INTEGER)
(0x03000000:NameValue):Priority = 0 (INTEGER)
(0x03000000:NameValue):Persistence = 1 (INTEGER)
(0x03000000:NameValue):MsgId = X'414d51205742524b3850524420202020cfd4315433a10720' (BLOB)
(0x03000000:NameValue):CorrelId = X'414d5120514d475241202020202020207ada31549b990520' (BLOB)
(0x03000000:NameValue):BackoutCount = 0 (INTEGER)
(0x03000000:NameValue):ReplyToQ = ' ' (CHARACTER)
(0x03000000:NameValue):ReplyToQMgr = 'HUBHA ' (CHARACTER)
(0x03000000:NameValue):UserIdentifier = 'mqm ' (CHARACTER)
(0x03000000:NameValue):AccountingToken = X'0332303300000000000000000000000000000000000000000000000000000006' (BLOB)
(0x03000000:NameValue):ApplIdentityData = ' ' (CHARACTER)
(0x03000000:NameValue):PutApplType = 6 (INTEGER)
(0x03000000:NameValue):PutApplName = ' ' (CHARACTER)
(0x03000000:NameValue):PutDate = DATE '2014-10-06' (DATE)
(0x03000000:NameValue):PutTime = GMTTIME '18:27:32.600' (GMTTIME)
(0x03000000:NameValue):ApplOriginData = ' ' (CHARACTER)
(0x03000000:NameValue):GroupId = X'000000000000000000000000000000000000000000000000' (BLOB)
(0x03000000:NameValue):MsgSeqNumber = 1 (INTEGER)
(0x03000000:NameValue):Offset = 0 (INTEGER)
(0x03000000:NameValue):MsgFlags = 0 (INTEGER)
(0x03000000:NameValue):OriginalLength = -1 (INTEGER)
)
(0x01000000:Folder):DataObject = ( ['Dataobject' : 0x7f92b8163cf0]
(0x01000000:Folder)http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/sapcremas05:SapCremas05 = (
(0x01000000:Folder):SapCremas05IDocBO = (
(0x01000000:Folder):SapIDocControlRecord = (
(0x03000000:PCDataField):RCVPOR = 'SAPSTG' (CHARACTER)
(0x03000000:PCDataField):SNDPRT = 'LS' (CHARACTER)
(0x03000000:PCDataField):SNDPRN = 'XXXXX2010' (CHARACTER)
(0x03000000:PCDataField):TABNAM = 'EDI_DC40' (CHARACTER)
(0x03000000:PCDataField):MANDT = '300' (CHARACTER)
(0x03000000:PCDataField):RCVPRN = 'STGCLNT300' (CHARACTER)
(0x03000000:PCDataField):SNDPOR = 'SAPSTG' (CHARACTER)
(0x03000000:PCDataField):RCVPRT = 'LS' (CHARACTER)
(0x03000000:PCDataField):IDOCTYP = 'CREMAS05' (CHARACTER)
(0x03000000:PCDataField):MESTYP = 'CREMAS' (CHARACTER)
)
(0x01000000:Folder):SapCremas05DataRecord = (
(0x01000000:Folder):SapCremas05E2lfa1m002 = (
(0x03000000:PCDataField):Lifnr = '41803 ' (CHARACTER)
(0x03000000:PCDataField):Datlt = '/' (CHARACTER)
(0x03000000:PCDataField):Kunnr = '41803 ' (CHARACTER)
(0x03000000:PCDataField):Land1 = 'NL ' (CHARACTER)
(0x03000000:PCDataField):Loevm = '/' (CHARACTER)
(0x03000000:PCDataField):Dtams = '3 ' (CHARACTER)
(0x03000000:PCDataField):Name1 = 'XXXXXXXXXXXXXXXXXXXXXXXXX. ' (CHARACTER)
(0x03000000:PCDataField):Name2 = ' ' (CHARACTER)
(0x03000000:PCDataField):Sortl = 'XXXXXXXXXX' (CHARACTER)
(0x03000000:PCDataField):Name3 = ' ' (CHARACTER)
(0x03000000:PCDataField):Name4 = ' ' (CHARACTER)
(0x03000000:PCDataField):Ort01 = '.XXXXXX ' (CHARACTER)
(0x03000000:PCDataField):Sperr = '/' (CHARACTER)
(0x03000000:PCDataField):Spras = 'I' (CHARACTER)
(0x03000000:PCDataField):Stras = 'XXXXXXX, 2 ' (CHARACTER)
(0x03000000:PCDataField):Telf1 = '+99999999999 ' (CHARACTER)
(0x03000000:PCDataField):Telfx = '+99999999999 ' (CHARACTER)
(0x03000000:PCDataField):Teltx = 'XXXXXXXXX@XXXXXXXXXXXXXXXXXXX.c' (CHARACTER)
(0x03000000:PCDataField):Telx1 = 'om ' (CHARACTER)
(0x03000000:PCDataField):Vbund = '/' (CHARACTER)
(0x03000000:PCDataField):Brsch = '01 ' (CHARACTER)
(0x03000000:PCDataField):Ktokk = 'ZMEU' (CHARACTER)
(0x03000000:PCDataField):Pstlz = '5107' (CHARACTER)
(0x03000000:PCDataField):Fiskn = '/' (CHARACTER)
(0x03000000:PCDataField):Stcd2 = '/' (CHARACTER)
(0x03000000:PCDataField):Stceg = '/' (CHARACTER)
(0x03000000:PCDataField):Stcd3 = 'NL999999999B99 ' (CHARACTER)
(0x01000000:Folder ):SapCremas05E2lfb1m005 = (
(0x03000000:PCDataField):Xverr = '/' (CHARACTER)
(0x03000000:PCDataField):Vzskz = '/' (CHARACTER)
(0x03000000:PCDataField):Zahls = '/' (CHARACTER)
(0x03000000:PCDataField):Busab = '/' (CHARACTER)
(0x03000000:PCDataField):Lnrzb = '/' (CHARACTER)
(0x03000000:PCDataField):Bukrs = 'S010' (CHARACTER)
(0x03000000:PCDataField):Zuawa = 'ZFO' (CHARACTER)
(0x03000000:PCDataField):Fdgrv = 'ZFO_20 ' (CHARACTER)
(0x03000000:PCDataField):Reprf = 'X' (CHARACTER)
(0x03000000:PCDataField):Sperr = '/' (CHARACTER)
(0x03000000:PCDataField):Akont = '/' (CHARACTER)
(0x03000000:PCDataField):Zwels = '/' (CHARACTER)
(0x03000000:PCDataField):Zterm = '1AT7' (CHARACTER)
(0x01000000:Folder ):SapCremas05E2lfb5m = (
(0x03000000:PCDataField):Lifnr = '/' (CHARACTER)
(0x03000000:PCDataField):Mahna = '/' (CHARACTER)
(0x03000000:PCDataField):Mansp = '/' (CHARACTER)
(0x03000000:PCDataField):Madat = '/' (CHARACTER)
(0x03000000:PCDataField):Mahns = '/' (CHARACTER)
(0x03000000:PCDataField):Lfrma = '/' (CHARACTER)
(0x03000000:PCDataField):Gmvdt = '/' (CHARACTER)
)
)
(0x01000000:Folder ):SapCremas05E2lfb1m005 = (
(0x03000000:PCDataField):Xverr = '/' (CHARACTER)
(0x03000000:PCDataField):Vzskz = '/' (CHARACTER)
(0x03000000:PCDataField):Zahls = '/' (CHARACTER)
(0x03000000:PCDataField):Busab = '/' (CHARACTER)
(0x03000000:PCDataField):Lnrzb = '/' (CHARACTER)
(0x03000000:PCDataField):Bukrs = 'S030' (CHARACTER)
(0x03000000:PCDataField):Zuawa = 'ZFO' (CHARACTER)
(0x03000000:PCDataField):Fdgrv = 'ZFO_20 ' (CHARACTER)
(0x03000000:PCDataField):Reprf = 'X' (CHARACTER)
(0x03000000:PCDataField):Sperr = '/' (CHARACTER)
(0x03000000:PCDataField):Akont = '/' (CHARACTER)
(0x03000000:PCDataField):Zwels = '/' (CHARACTER)
(0x03000000:PCDataField):Zterm = '1AT7' (CHARACTER)
(0x01000000:Folder ):SapCremas05E2lfb5m = (
(0x03000000:PCDataField):Lifnr = '/' (CHARACTER)
(0x03000000:PCDataField):Mahna = '/' (CHARACTER)
(0x03000000:PCDataField):Mansp = '/' (CHARACTER)
(0x03000000:PCDataField):Madat = '/' (CHARACTER)
(0x03000000:PCDataField):Mahns = '/' (CHARACTER)
(0x03000000:PCDataField):Lfrma = '/' (CHARACTER)
(0x03000000:PCDataField):Gmvdt = '/' (CHARACTER)
)
)
As You can see the Idoc structure is filled for:
- Control record
- SapCremas05DataRecord with:
one SapCremas05E2lfa1m002
a sequence of pair of segments of types SapCremas05E2lfb1m005 and SapCremas05E2lfb5m.
Inside SAP the idoc has only control record and SapCremas05E2lfa1m002 segment ... |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Oct 12, 2014 10:55 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Perhaps the structure of the message is not right
| Code: |
(0x01000000:Folder):SapCremas05DataRecord = (
(0x01000000:Folder):SapCremas05E2lfa1m002 = (
(0x03000000:PCDataField):Lifnr = '41803 ' (CHARACTER)
...
(0x03000000:PCDataField):Gmvdt = '/' (CHARACTER)
) <--- ends SapCremas05E2lfa1m002
) <--- ends SapCremas05DataRecord
(0x01000000:Folder ):SapCremas05E2lfb1m005 = (
(0x03000000:PCDataField):Xverr = '/' (CHARACTER)
....
)
)
|
I do not claim to know the details of SAP IDOCS as all the flows I have written that use SAP use XML but that bit I have marked (<---) might be the problem.
If it is not then great.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| MrVMax |
| Posted: Mon Oct 13, 2014 5:17 am Post subject: |
|
|
Novice
Joined: 01 Aug 2013
Posts: 23
|
Thanks smdavies99,
but it seems to me that You are wrong in two different ways:
the following rows are a little bit less confusing that the original output of the trace node and the structure seems right, but also if the structure wasn't right I'm not supposed to tampering with te result of the idoc discovery process and anyway the exactly same flow with the bars made in two different boxes one without a recent discovery and one with a discovery old only a week works differently on the same Websphere Message Broker 8.0.0.2 or 8.0.0.4:
the flow deployed from a box with an old version of Idoc structure works fine and the flow deployed from a box with the recent Idoc structure have the behavior described ...only control record and SapCremas05E2lfa1m002 segment while all the others appears as missed without any error signaled on Message broker side and getting the sap transaction code !
(0x01000000:Folder):DataObject = ( ['Dataobject' : 0x7f92b8163cf0]
(0x01000000:Folder)[color=red]http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/sapcremas05:SapCremas05 =
(
(0x01000000:Folder):SapCremas05IDocBO =
(
(0x01000000:Folder):SapIDocControlRecord =
(
(0x03000000:PCDataField):RCVPOR = 'SAPSTG' (CHARACTER)
(0x03000000:PCDataField):SNDPRT = 'LS' (CHARACTER)
(0x03000000:PCDataField):SNDPRN = 'FINIP2010' (CHARACTER)
(0x03000000:PCDataField):TABNAM = 'EDI_DC40' (CHARACTER)
(0x03000000:PCDataField):MANDT = '300' (CHARACTER)
(0x03000000:PCDataField):RCVPRN = 'STGCLNT300' (CHARACTER)
(0x03000000:PCDataField):SNDPOR = 'SAPSTG' (CHARACTER)
(0x03000000:PCDataField):RCVPRT = 'LS' (CHARACTER)
(0x03000000:PCDataField):IDOCTYP = 'CREMAS05' (CHARACTER)
(0x03000000:PCDataField):MESTYP = 'CREMAS' (CHARACTER)
)
(0x01000000:Folder):SapCremas05DataRecord =
(
(0x01000000:Folder):SapCremas05E2lfa1m002 =
(
(0x03000000:PCDataField):Lifnr = '41803 ' (CHARACTER)
<snip>
(0x03000000:PCDataField):Stcd3 = 'NL821955998B01 ' (CHARACTER)
(0x01000000:Folder ):SapCremas05E2lfb1m005 =
(
(0x03000000:PCDataField):Xverr = '/' (CHARACTER)
<snip>
(0x03000000:PCDataField):Zterm = '1AT7' (CHARACTER)
(0x01000000:Folder ):SapCremas05E2lfb5m =
(
(0x03000000:PCDataField):Lifnr = '/' (CHARACTER)
<snip>
(0x03000000:PCDataField):Gmvdt = '/' (CHARACTER)
)
)
(0x01000000:Folder ):SapCremas05E2lfb1m005 =
(
(0x03000000:PCDataField):Xverr = '/' (CHARACTER)
<snip>
(0x03000000:PCDataField):Zterm = '1AT7' (CHARACTER)
(0x01000000:Folder ):SapCremas05E2lfb5m =
(
(0x03000000:PCDataField):Lifnr = '/' (CHARACTER)
<snip>
(0x03000000:PCDataField):Gmvdt = '/' (CHARACTER)
)
)
(0x01000000:Folder ):SapCremas05E2lfb1m005 =
(
(0x03000000:PCDataField):Xverr = '/' (CHARACTER)
<snip>
(0x03000000:PCDataField):Zterm = '1AT7' (CHARACTER)
(0x01000000:Folder ):SapCremas05E2lfb5m =
(
(0x03000000:PCDataField):Lifnr = '/' (CHARACTER)
<snip>
(0x03000000:PCDataField):Gmvdt = '/' (CHARACTER)
)
)
(0x01000000:Folder ):SapCremas05E2lfb1m005 =
(
(0x03000000:PCDataField):Xverr = '/' (CHARACTER)
<snip>
(0x03000000:PCDataField):Zterm = '1AT7' (CHARACTER)
(0x01000000:Folder ):SapCremas05E2lfb5m =
(
(0x03000000:PCDataField):Lifnr = '/' (CHARACTER)
<snip>
(0x03000000:PCDataField):Gmvdt = '/' (CHARACTER)
)
)
<snip>
(0x01000000:Folder ):SapCremas05E2lfb1m005 =
(
(0x03000000:PCDataField):Xverr = '/' (CHARACTER)
<snip>
(0x03000000:PCDataField):Zterm = '1AT7' (CHARACTER)
(0x01000000:Folder ):SapCremas05E2lfb5m =
(
(0x03000000:PCDataField):Lifnr = '/' (CHARACTER)
<snip>
(0x03000000:PCDataField):Gmvdt = '/' (CHARACTER)
)
)
)
)
)
) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Oct 13, 2014 6:53 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Verify your discovery and have the SAP TEAM verify the latest IDOC setup.
They both work hand in hand. If the SAP team changed something to the IDOC setup that might explain this, and your input data might no longer conform ...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| MrVMax |
| Posted: Mon Oct 13, 2014 1:35 pm Post subject: |
|
|
Novice
Joined: 01 Aug 2013
Posts: 23
|
Thanks fjb_saper, I known that they are supposed to go in parallel evolution and this is the most strange thing that had happened:
1) We made the discovery process in July 2013
2) The SAP team changed the structure of the Idoc on November 2013 adding new fields
3) From November till last week the flows worked fine with no warning ad the SAP team got thousands of Idoc without trouble because also if they changed the structure they didn't ask us to fill the extras fields
4) last week the asked to use one new field among the fields inserted on November 2013 and never used
5) We did a new discovery
6) now we have the trouble.
It seems like the discovery process reads the structures from SAP using a view while the receive process of SAP match the incoming Idocs using another view that ha still the new fields disabled ... is that possible ? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Oct 13, 2014 1:46 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
It's totally possible. The new structure even though built, will need to be enabled (in SAP) before you can use it.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| MrVMax |
| Posted: Tue Oct 14, 2014 5:45 am Post subject: |
|
|
Novice
Joined: 01 Aug 2013
Posts: 23
|
I tried to get the maximum RFC trace level ( and I've discovered that between the running of the flow deployed with the old discovered Idoc structure (Toolkit 2 of the first post) and the running of the flow deployed with the new discovered Idoc structure (Toolkit 3 of the first post) there are a lot of differences in each of the rfc trace file pair while the broker trace node just before the SAPRequest node are identical but for the time strings and SAP transactions id.
So, is right to think that the trouble should be inside the SAPJco.jar Idocjco.jar or in any case into the "SAP area" ? And so ask to the SAP Team to investigate ?
Anyway I would like to understand better the RFC trace produced, anyone of You can suggest me something to read about the RFC trace produced by the adapters ?
Many thanks in advance. |
|
| Back to top |
|
|
| liuk |
| Posted: Wed Oct 15, 2014 6:48 am Post subject: |
|
|
Newbie
Joined: 15 Oct 2014
Posts: 1
|
| fjb_saper wrote: |
| It's totally possible. The new structure even though built, will need to be enabled (in SAP) before you can use it. |
Dear fjb_saper, do you know which SAP Notes describe this issue or better which SAP transactions can be used to verify if the new structure is enabled ?
Thank you very much in advance.
Luca |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 15, 2014 7:32 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
AFAIK the new structure will have to be enabled in environment n-1 before it can be transported to environment n.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
