| Author |
Message
|
| ghoshly |
 Posted: Mon Oct 24, 2011 2:40 pm Post subject: Unable to configure SAP adapter for a new BAPI call. |
 |
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
Hi,
I seek help to identify if I am missing any step or doing any wrong to configure SAP adapter to call a new SAP BAPI.
Steps I performed.
1. Extracted the structure for the BAPI call and kept all xsds in the SAP adapter repository directory.
2. Restart the SAP adapter instance.
3. Call the SAP BAPI method by sending the request message through the Request Queue.
Error I am receiving is mentioned below.
| Quote: |
[Time: 2011/10/24 22:27:46.452] [System: Server] [Thread: EAI.SAP_BAPI.QUERYJmsThreadPool.thread5 (#2144898487)] [Type: Error] [MsgID: 0] [Mesg: Unable to find version "*.*.*" of business object definition "sap_z_bapi_price_update".]
[Time: 2011/10/24 22:27:46.453] [System: ConnectorAgent] [SS: SAPBAPIQUERYConnector] [Thread: EAI.SAP_BAPI.QUERYJmsThreadPool.thread5 (#2144898487)] [Type: Error] [MsgID: 9068] [Mesg: The received message cannot be converted to BO Message. The message is not valid and is NOT processed. The response will be sent to the ReplyToQueue if it is set. Otherwise, the message will be sent to the fault queue. Message ID: ID:505249435f32303131313032343232323734363839343534]
|
Message Broker 6.0
AIX
SAP Adapter 6.0.9
jCO Version = 2.1.9 (2010-01-2
WebSphere Business Integration Adapter Framework version = 2.6.0.12 |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Mon Oct 24, 2011 2:45 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Seems that your input message is not matching exactly the format needed by the BO. Recheck your parsing.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| ghoshly |
| Posted: Mon Oct 24, 2011 2:46 pm Post subject: Input message validation |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
I forget to mention the step of including the BOs as supported BOs in the cfg file, which I did and replaced the existing cfg file.
I have tried to validate the input message I am sending to SAP Request Queue against the sap_z_bapi_price_update.xsd and it seems to be valid.
I checked the access permission on those xsds as same as all other working xsds there.
Please help. |
|
| Back to top |
|
|
| ghoshly |
| Posted: Mon Oct 24, 2011 2:50 pm Post subject: How adapter picks up the correct xsd to validate |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
Please help me to understand how SAP adapter picks up the correct xsd to validate the incoming message.
Is it based on the root element name of the incoming message , or identifies the xsd based on the Message Set ID value present in MQRFH2 header and cfg file?
Thanks again for responding to my question. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Oct 24, 2011 7:33 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Seems to me that the name of the business object / BAPI is not quite right.
Are you sure it is "sap_z_bapi_price_update" and not just "z_bapi_price_update" ? and IIRC that would be in capitals... and not lower case... but as it is a "Z" object you better verify... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| ghoshly |
| Posted: Tue Oct 25, 2011 4:06 pm Post subject: BO name |
|
|
Partisan
Joined: 10 Jan 2008
Posts: 333
|
I verify the BO names listed in the supported BO list, others already present there are like sap_Z_****.
I put the message set id in the cfg file Message Set ID column and it picked up the xsd which confuses me more.
What I found is OutputRoot.Properties.MessageSet is overriding any value I set in OutputRoot.MQRFH2.mcd.Set. Can you please confirm me is this is expected behavior?
Thanks in advance |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Oct 25, 2011 7:49 pm Post subject: Re: BO name |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| ghoshly wrote: |
I verify the BO names listed in the supported BO list, others already present there are like sap_Z_****.
I put the message set id in the cfg file Message Set ID column and it picked up the xsd which confuses me more.
What I found is OutputRoot.Properties.MessageSet is overriding any value I set in OutputRoot.MQRFH2.mcd.Set. Can you please confirm me is this is expected behavior?
Thanks in advance |
Yes I would expect the OutputRoot.Properties to override any other value of the same type and meaning.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
