APAR status
Closed as program error.
Error description
When parsing a SAP IDoc using the the DataObject parser and the SAP ALE IDoc physical format in a message flow node the following errors can be observed for flows that use message set XSD schemas: BIP3450E RecoverableException throwableToMbException 'exception during IDOC Parsing' ['java.lang.NullPointerException at com.ibm.j2ca.sap.records.SAPParseRecord.getSegmentBO(SAPParseRec ord.java:601) at com.ibm.j2ca.sap.records.SAPParseRecord.buildIDoc(SAPParseRecord .java:396) at com.ibm.j2ca.sap.records.SAPParseRecord.parseInLineContent(SAPPa rseRecord.java:309) at com.ibm.j2ca.sap.records.SAPParseRecord.getNext(SAPParseRecord.j ava:248) at com.ibm.broker.adapter.deploy.MbAdapterDirector.parseIdoc(MbAdap terDirector.java:595) at com.ibm.broker.adapter.deploy.MbAdapterDirector.parseIdoc(MbAdap terDirector.java:535) '] MbErrorHandlerBase.java:195 BIP3472E ParserException parseIdoc 'exception caught in parseIDOC' MbAdapterDirector.java:639 <Nested: BIP3450E>
Local fix
In the Toolkit, copy the SapBusinessObjectMetadata.xsd file from a non-message set project to a known location and then add it to the XML Catalog in the Eclipse preferences pane and then re-build any affected BAR files.
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus v10 or IBM App Connect Enterprise v11 that employ the SAP IDoc gateway pattern. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When parsing a SAP IDoc using the the DataObject parser and the SAP ALE IDoc physical format in a message flow node the following errors can be observed for flows that use message set XSD schemas: BIP3450E RecoverableException throwableToMbException 'exception during IDOC Parsing' ['java.lang.NullPointerException at com.ibm.j2ca.sap.records.SAPParseRecord.getSegmentBO(SAPParseRec ord.java:601) at com.ibm.j2ca.sap.records.SAPParseRecord.buildIDoc(SAPParseRecord .java:396) at com.ibm.j2ca.sap.records.SAPParseRecord.parseInLineContent(SAPPa rseRecord.java:309) at com.ibm.j2ca.sap.records.SAPParseRecord.getNext(SAPParseRecord.j ava:248) at com.ibm.broker.adapter.deploy.MbAdapterDirector.parseIdoc(MbAdap terDirector.java:595) at com.ibm.broker.adapter.deploy.MbAdapterDirector.parseIdoc(MbAdap terDirector.java:535) '] MbErrorHandlerBase.java:195 BIP3472E ParserException parseIdoc 'exception caught in parseIDOC' MbAdapterDirector.java:639 <Nested: BIP3450E> This occurs because the SapBusinessObjectMetadata.xsd schema file has not been compiled into the message set correctly by the IBM Integration Toolkit. This can be seen by the following warning which will appear repeatedly in the user.log when compiling a BAR file containing affected message sets: BIP0342W The XSD file SapIDocControlRecord.xsd does not specify the location of the imported namespace "http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/metadata". If this namespace is provided by the XML Catalog, ensure the catalog entry defines the XSD schema location. If the namespace is provided by another XSD file, ensure this XSD file is available in a workspace project.
Problem conclusion
The DataObject parser will now compensate for the SapBusinessObjectMetadata.xsd schema file being missing from the message set at deploy time. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.19 v11.0 11.0.0.6 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT30210
Reported component name
INTEGRATION BUS
Reported component ID
5724J0540
Reported release
A00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-09-10
Closed date
2020-01-03
Last modified date
2020-01-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
INTEGRATION BUS
Fixed component ID
5724J0540
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
03 January 2020