| Author |
Message
|
| whydieanut |
 Posted: Wed Nov 23, 2011 1:32 am Post subject: SAP Adpter Issue after Fix Pack 3 |
 |
|
Disciple
Joined: 02 Apr 2010
Posts: 186
|
Hi all,
I had version 7.0.0.1 of the Broker Runtime ad corresponding Toolkit.
I had been using the SAP Adapter for Inbound and Outbound processing.
I could successfully use the Outbound Adapter in ALE mode to sendIDOCs to SAP.
Since I had issues using the Passthrough Adapter for Inbound, I upgraded the Broker Runtime to 7.0.0.3 (http://www-01.ibm.com/support/docview.wss?uid=swg24030627)
The Inbound Passthrough Adapter issue was resolved.
But then the Outbound Adapter stopped working.
I then upgraded the Toolkit to 7.0.0.3 (http://www.ibm.com/support/docview.wss?rs=849&uid=swg24031096)
I then created another Outbound ALE Adapter with the new Toolkit.
So I now have 2 Adapters (one created with the old Toolkit and one with the Fix Pack). Here's is the behaviour I am getting when using each of them, using the same input message:
Old Adapter:
I get the following Exception, the message is rolled back, but the IDOC is created on SAP.
| Code: |
RecoverableException
File:CHARACTER:MbErrorHandler.java
Line:INTEGER:110
Function:CHARACTER:execute
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3449
Text:CHARACTER:adapter returned null from StructuredRecord.execute()
|
New Adapter:
I get the following Exception, the message is rolled back and no IDOC is created.
| Code: |
RecoverableException
File:CHARACTER:MbErrorHandler.java
Line:INTEGER:286
Function:CHARACTER:throwableToMbException
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3450
Text:CHARACTER:Caught Throwable
Insert
Type:INTEGER:5
Text:CHARACTER:failed in initialization
org.eclipse.emf.ecore.resource.Resource$IOWrappedException: Feature 'IDocVersion' not found. (http:///temp.xml, 3, 21)
Feature 'IDocVersion' not found. (http:///temp.xml, 3, 21)
Feature 'IDocVersion' not found. (http:///temp.xml, 3, 21)
|
The only thing I can conclude from this is that after the Fix Pack for the Toolkit, the adapter is not being created right. Also I can find any reference to the above mentioned error "Feature 'IDocVersion' not found".
Any help in this regard would be greatly appreciated!
Thanks in advance... |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Nov 23, 2011 4:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| whydieanut |
| Posted: Thu Nov 24, 2011 1:39 am Post subject: |
|
|
Disciple
Joined: 02 Apr 2010
Posts: 186
|
Is there anything that can be tried out first before opening a PMR?
Like re-installing the Toolkit, maybe? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Nov 24, 2011 3:08 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I'd downgrade my toolkit to 7.0.0.2 but keep one system on 7.0.0.3.
If mqjeff says raise a PMR then I'd take his advice. He works alongside the product developers at IBM Hursley.
Raise the PMR and don't forget to mention this thread in it.
I've already held back from going to 7.0.0.3 because of this issue. I may however find some time next week to try the same test as you with 7.0.0.3
_________________
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 |
|
|
| whydieanut |
| Posted: Thu Nov 24, 2011 3:14 am Post subject: |
|
|
Disciple
Joined: 02 Apr 2010
Posts: 186
|
Thanks, mqjeff and smdavies99.
Will do that, and also keep this thread updated with the results. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Nov 25, 2011 7:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| smdavies99 wrote: |
| If mqjeff says raise a PMR then I'd take his advice. |
Generally I do not suggest raising a PMR unless something looks very much like a bug.
| smdavies99 wrote: |
| He works alongside the product developers at IBM Hursley. |
If only it were that straightforward... |
|
| Back to top |
|
|
| Bravo |
| Posted: Thu Dec 01, 2011 9:56 am Post subject: |
|
|
Centurion
Joined: 03 Oct 2005
Posts: 146
|
Had same problem, applied ifix resolved the issue.
_________________
Bravo |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Dec 01, 2011 10:00 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Would you care to share the iFix number etc with us so that others who experience this issue can ask IBM for it?
_________________
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 |
|
|
| mqjeff |
| Posted: Thu Dec 01, 2011 10:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| smdavies99 wrote: |
| Would you care to share the iFix number etc with us so that others who experience this issue can ask IBM for it? |
I suspect he or she just means the most recent iFix level of Toolkit 7.0.0.3... |
|
| Back to top |
|
|
| Bravo |
| Posted: Thu Dec 01, 2011 11:09 am Post subject: |
|
|
Centurion
Joined: 03 Oct 2005
Posts: 146
|
I am not sure about number. This ifix provided to us by IBM Webpshere Adapter Support team as a fix for the PMR.
And it worked 
_________________
Bravo |
|
| Back to top |
|
|
| whydieanut |
| Posted: Mon Dec 26, 2011 9:26 pm Post subject: |
|
|
Disciple
Joined: 02 Apr 2010
Posts: 186
|
|
| Back to top |
|
|
| whydieanut |
| Posted: Mon Dec 26, 2011 11:45 pm Post subject: |
|
|
Disciple
Joined: 02 Apr 2010
Posts: 186
|
No success with V7.0.0.3 Interim Fix 002 either, gives the same error.
@Bravo, can you give some more info abou the fix pack?
Was it for the Broker run time or the Toolkit? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Dec 27, 2011 12:21 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| whydieanut wrote: |
No success with V7.0.0.3 Interim Fix 002 either, gives the same error.
@Bravo, can you give some more info abou the fix pack?
Was it for the Broker run time or the Toolkit? |
I thought the latest was Ifix 03? Go to the latest and if it is not fixed there open a PMR and reference the thread. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| whydieanut |
| Posted: Sun Jan 01, 2012 9:54 pm Post subject: |
|
|
Disciple
Joined: 02 Apr 2010
Posts: 186
|
|
| Back to top |
|
|
| whydieanut |
| Posted: Wed Jan 18, 2012 3:36 am Post subject: |
|
|
Disciple
Joined: 02 Apr 2010
Posts: 186
|
Here's what we got as a reply to our PMR:
| Quote: |
From the traces provided we can see that IDocVersion field is not recognised by the runtime/toolkit.
This field is read from SapBusinessObjectMetadata.xsd, that is bundled in that adapter rar project.
<element name="IDocVersion" type="string" minOccurs="0" maxOccurs="1"/>
Are trying to generate the artifacts newly into a workspace where already an adapter existed.
This error is seen when the latest metadata xsd is not loaded.
Can you please try to import the project interchange to a new workspace where there is only one adapter rar in the workspace, generate
the bar file and try out the tests?
|
Using a fresh workspace worked for us.
UPDATE: closing all the earlier Connector Projects before starting with a new one worked too.
The problem seems to be the 'SapBusinessObjectMetadata.xsd' file that the Toolkit uses to create the bar file.
In my old connector projects (CWYAP_SAPAdapter_Tx), the SapBusinessObjectMetadata.xsd file is missing the IDocVersion field.
But ths is present in the newer connector projects that shipped with SAP IF14 as part of FixPack 3.
Now since I had a few adapter connection projects in my workspace, any new Adapter I create in the same workspace, with IF14, uses the existing SapBusinessObjectMetadata.xsd from one of the older connector projects.
I can see that the new connector projects does have IDocVersion in the SapBusinessObjectMetadata.xsd, but it's not being used when the bar file is created and the SapBusinessObjectMetadata.xsd file inside the .xsdzip file of the bar file is still the old SapBusinessObjectMetadata.xsd file without the IDocVersion field in it.
Last edited by whydieanut on Wed Jan 18, 2012 4:09 am; edited 1 time in total |
|
| Back to top |
|
|
|
|
