| Author |
Message
|
| smeunier |
 Posted: Fri Sep 02, 2011 11:40 am Post subject: Invalid BO's attribute order |
 |
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
I have configured a SAP adapter and am posting messages to it from WebSphere Message broker V6. I create a well-formed XML message in using the BO schema. I have a segment created for every REQUIRED segment as defined by the BO. I have validated the XML message format against a XSD generated XML template using XMLspy. The formats are the same as far as I can tell, bit get the following message from the adapter
ThreadPool.thread5 (#1773128130)] [Type: Error] [MsgID: 0] [Mesg: Invalid BO's attribute order]
I have scoured the internet looking for this error and possible hints as to what may be the issue and from what I can tell, it is an order issue (segment order vs the BO schema). However, is there a way to get more detailed information on what "attribute" the adapter thinks is out of sequence? Or any other way to debug this. Its frying my brain!!!!!
I have also tried rebuilding and deploying the BO....but no luck.
Any experience with this?! |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Fri Sep 02, 2011 12:01 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
The error is telling you that you are presenting the Business Objects attributes in a sequence that the adapter is not expecting.
You could try re-importing the XSDs. Then rebuild/clean all projects in your workspace.
It used to be that when the business object schema and XML sequence is different, the business object would still be processed and passed to the application. This was a bug in the adapter code which was fixed in 2008.
When this happens now, the error you have seen is thrown. Basically it means that the XSD you are using and the Business Object it maps to are not the same version.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Sep 03, 2011 4:24 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Broker v6 is out of support.
The standalone WBI adapter is mostly out of support.
You should upgrade to Broker v7 and the SAP nodes that are built in. |
|
| Back to top |
|
|
| smeunier |
| Posted: Tue Sep 06, 2011 6:15 am Post subject: |
|
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
| That does not address my problem. While there is a strategy to push to the V7 broker by the customer, it does not help the customer support current needs of the business. Your response does not address the current problem. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Sep 06, 2011 6:24 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
did you re-discover the BO from SAP again, if not please give a try.
if you have already done it..did you get a chance to compare the old and new one. or if you try to merge it will prompt when the changes are made.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 06, 2011 6:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| smeunier wrote: |
| That does not address my problem. While there is a strategy to push to the V7 broker by the customer, it does not help the customer support current needs of the business. Your response does not address the current problem. |
You appear to be doing new development. New development should be done using the supported product set...
You should be able to enable tracing on the existing adapter to get a better idea of what it is specifically complaining about - although I was never successful enough with the WBI adapters so I can't guarantee that based on personal experience.
You should be able to examine a Trace node output of the message as produced by Broker, and compare this with the BO schema to identify the incorrect ordering. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Sep 06, 2011 6:36 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
oh yes..i agree with Jeff
do a mqsitrace, we will come to know more details 
even activate the RFC trace as well in the adapter node too.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Sep 06, 2011 7:00 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| smeunier wrote: |
| That does not address my problem. While there is a strategy to push to the V7 broker by the customer, it does not help the customer support current needs of the business. Your response does not address the current problem. |
Open a PMR.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| smeunier |
| Posted: Wed Sep 07, 2011 5:28 am Post subject: |
|
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
-> MQJeff: I don't disagree with your statement on developing on V7. The customer is slow to move to this version, but in the mean time needs to support on going business needs. With that said, life goes on with V6 and the associated risks. The comparison between broker generated message and BO Schema was compared and I found one data element out of order. This corrected the BO attribute order but generates a null pointer exception on a different segment now. This is a 3 level segment, so it may be the iteration level, but a generated XML sample from the BO schema and a generated message via the broker, produces similar structures.
-> Gaya3: I have run trace against the broker, as well as have Level 5 tracing enabled for the adapter, along with RFC tracing. These provide no indicator of where the BO attribute is would have been.
-> lancelotlinc: I feel this is a developmental issue and not a product issue. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Sep 07, 2011 5:40 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| smeunier wrote: |
| -> lancelotlinc: I feel this is a developmental issue and not a product issue. |
Why would this preclude you from opening a PMR? By opening a PMR, you get official IBM support on this issue.
mqseries.net is an informal information exchange and does not replace the need for official IBM support.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Sep 07, 2011 5:42 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| lancelotlinc wrote: |
The error is telling you that you are presenting the Business Objects attributes in a sequence that the adapter is not expecting.
You could try re-importing the XSDs. Then rebuild/clean all projects in your workspace.
It used to be that when the business object schema and XML sequence is different, the business object would still be processed and passed to the application. This was a bug in the adapter code which was fixed in 2008.
When this happens now, the error you have seen is thrown. Basically it means that the XSD you are using and the Business Object it maps to are not the same version. |
Did you try these steps? What was the outcome? Did you re-import the XSD? Did you turn on user trace? What do the logs show? Have you collected the must gather documentation?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
