| Author |
Message
|
| SSachdeva |
 Posted: Wed Mar 03, 2004 8:26 am Post subject: mySAP.cpm Adapter with WMQI - RFCServer |
 |
|
Apprentice
Joined: 04 Apr 2002
Posts: 33
|
Hi,
I am trying to have the mySAP.com adapter send messages to WMQI using the RFCServer module. THe things is that the BO created by the SAPODA needs to have COllab= set in the request BO for processing. The documentation says set theis value to a dummy value - which I did, the message request is processed successfully by the adapter. Now when I send the same BO as reply back the adapter gives me an error saying that the Collab DUMMY does not exist and so it fails. How can I tell the adapter on the recieving side not to try to instantiate the collaboration since I am working with WMQI not ICS. Please help - i have tried a whole bunch of things  . Heres some more info on the error:
[Time: 2004/03/03 10:47:07.517] [System: ConnectorAgent] [SS: AppConn] [Thread:
JCO.ServerThread (#1728130923)] [Type: Trace] [Mesg: :consumeSync returning 22♥R
eturnStatusDescriptor7♥4.2.0.02♥-14♥null]
[Time: 2004/03/03 10:47:07.517] [System: ConnectorAgent] [SS: AppConn] [Thread:
JCO.ServerThread (#1728130923)] [Type: Trace] [Mesg: :ConsumeSync: BusinessObjec
t after executing Collaboration :DUMMY<StartHeader>
<Version = 3.0>
<EndHeader>
<StartBO:sap_z_rfc_reservationrebook>
BusinessObject = sap_z_rfc_reservationrebook
Verb = Create
Locale = en_US
Field_of_length_16 = CxBlank
Field_of_length_161 = CxBlank
Character_field_length___10 = 0101
Character_field_length___101 = PATRWU
Character_field_length___102 = FSR
Character_field_length___103 = WLRG
Not_More_Closely_Defined_Area__Possibly_Used_for_Patchlevels = ZZZZ
Character_field_length___104 = CxBlank
Character_field_length___105 = X
Short_text = AAAAAAAAAAAAA
Character_field_of_9_digits = CxBlank
Character_field_length___106 = 1111111111
Field_of_length_162 = CxIgnore
Field_of_length_163 = CxIgnore
Character_field_length___107 = CxIgnore
Character_field_length___108 = CxIgnore
Character_field_length___109 = CxIgnore
Version_number_components = CxIgnore
Char_80 = CxIgnore
Character_field_length___1010 = CxIgnore
Char_801 = CxIgnore
Not_More_Closely_Defined_Area__Possibly_Used_for_Patchlevels1 = CxIgnore
Character_field_length___1011 = CxIgnore
Character_field_of_9_digits1 = CxIgnore
Field_of_length_164 = CxIgnore
Short_text1 = CxIgnore
Character_field_of_9_digits2 = CxIgnore
Character_field_length___1012 = CxIgnore
Version_number_components1 = CxIgnore
ObjectEventId = AppConn_1078277690047_1
<EndBO:sap_z_rfc_reservationrebook>]
[Time: 2004/03/03 10:47:07.627] [System: ConnectorAgent] [SS: AppConn] [Thread:
JCO.ServerThread (#1728130923)] [Type: Error] [MsgID: 28011] [Mesg: Thread JCO.S
erverThread: Business Object sap_z_rfc_reservationrebook Collaboration execution
Error message : DUMMY. This error may occur if the collaboration : {4} is not r
unning or due to the collaboration name given in the verb Application-specific i
nformation of the busObj being incorrect. Validate object's verb Application-spe
cific information matches the actual collaboration name.] |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Wed Mar 10, 2004 3:16 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
Did you resolve this already?
I know nothing about the mySAP.com adapter, but worked with SAP before, but currently don't have anything to do with SAP...
still I find this an interesting problem, so would like to offer my help, if still needed.
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| SSachdeva |
| Posted: Wed Mar 10, 2004 3:25 pm Post subject: |
|
|
Apprentice
Joined: 04 Apr 2002
Posts: 33
|
Well not really resolved so much as hacked my way through it. I had to change the Business Object handler code that gets generated for an RFC by the mySAP.com connector Object Discovery Agent. I pretty much put in code that ignored that specific error.
Shamsher |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Mar 11, 2004 11:05 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
ok just downloaded the WS BI mySAP adapter manual ...
it says:
| Quote: |
The RFC Server-specific business object handler passes the business object to the integration broker.
In the RFC Server Module, since SAP makes the synchronization calls, when a WebSphere message broker
is the integration broker, the RFC Server Module uses SynchronousRequestQueue and SynchronousResponseQueue
to communicate with the WebSphere message broker. |
which leads me to believe the request (to the broker) and reply (from the broker) is correlated using the correlation id.
Did you copy the msgid to the correlid in your response from the broker and used the MQreply node?
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| SSachdeva |
| Posted: Thu Mar 11, 2004 11:15 am Post subject: |
|
|
Apprentice
Joined: 04 Apr 2002
Posts: 33
|
Yeah I did - but that really was not the problem. The reply message was getting picked up by the adapter, but when it was picked it - it tries to execute a collaboration - since my broker is WBIMB - there is no collaboration to run - and so it fails. I thiink IBM failed to remove this logic from the adapter before shipping it - but ofcourse I cannot be sure about that.
Shamsher |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Mar 11, 2004 12:27 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
well from what I read sofar I don't think so.
You need to know that the Crossworlds communication is synchronous between broker and adapter, whereas communication with WMQI and the adapter is asynchronous using messaging.
did you also read up on the dummy_key tag generated by the SAPADO and the import you need to do into the WMQI to understand the incoming message?
There are a lot of references to WMQI in the manual, so there must be some little bit you just missed.
Sorry I can just ask questions to point you into a direction and not having an SAP system and adapter to try it myself, I only have the manual to go on...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| SSachdeva |
| Posted: Thu Mar 11, 2004 12:48 pm Post subject: |
|
|
Apprentice
Joined: 04 Apr 2002
Posts: 33
|
| Thats ok, yes i did read the part aboput the dummy_key value for the SAPODA - but that is for a key value in the business object not the application specific information of the verb. All BO's created require a key value - if the RFC I am calling does not have a key value then the SAPODA creates one for you - which is refered to as a dummy_key. Crossworlds works like WMQI in the sense that it talks to its adapters asynchronously - this is only different in a few adpaters - the mySAP.com RFCServer module being one of them. I want the adapter to wait till it gets a reply - hence i need it to be synchronous in nature. The problem is that when a reply does come back - the adapter is reading the app specific info of the BO which has a dummy value for the Collab= in it. It takes this dummy value and tries to execute a collaboration with that name - and fails ofcourse. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Mar 11, 2004 1:03 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
Ok just re-read your post.
You mention sending the BO back as a reply, do you mean the exact content without modification?
If so SAP might think this a new request from another SAP as the outgoing one it created is a request aswell and not an answer to a question...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| SSachdeva |
| Posted: Thu Mar 11, 2004 1:16 pm Post subject: |
|
|
Apprentice
Joined: 04 Apr 2002
Posts: 33
|
| Hmmm not actually ... the mySAP.com adapter assigns a thread that services the request/reply transaction - so when it sends a request it waits for a reply based on the correlation identifier of the message. When a message with the right correlation identifier arrives - it knows that the message is a reply to the request that was sent and so processes that message as a reply. I changed the data in the message to contain valid data for a reply - but it still failed with the same error. The issue has not got to do with the content of the message as much as the processing by the adapter. I know this cause everything posts fine into sap when i change the code to ignore the error that i am getting. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Mar 11, 2004 1:24 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
sounds like you did everything right then sofar.
Did you already report this problem to IBM tech support?
I don't think I can help you much further other then being a bouncing wall for new ideas..
please let me know the result from IBM tech support.
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jlalbor |
| Posted: Wed Aug 17, 2005 9:28 am Post subject: Check the MQRFH2.usr structure |
|
|
Apprentice
Joined: 18 Feb 2003
Posts: 38
|
| SSachdeva wrote: |
Yeah I did - but that really was not the problem. The reply message was getting picked up by the adapter, but when it was picked it - it tries to execute a collaboration - since my broker is WBIMB - there is no collaboration to run - and so it fails. I thiink IBM failed to remove this logic from the adapter before shipping it - but ofcourse I cannot be sure about that.
Shamsher |
The problem here is that you must change the content of the MQRFH2.usr structure of the message you are sending as reply to mySAP adapter.
The incoming request from de Adapter to the Broker has the following fields in the MQRFH2.usr structure
WSDLBinding
RequestType
WSDLOperation
You must delete these fields an create a field name Status with value 0 or value 1.
Status=0 Indicates that the operation was sucessfull
Status=1 Indicates that there was an error on the operation.
When the adapter recives the reply, it checks for the field MQRFH2.usr.Status and if it exists, then the adapter continues the process, if this field is not present, the adapter tries to execute the collaboration specified in the BO. |
|
| Back to top |
|
|
|
|
