SAXException validation errors while querying MDM using MDM plugin 2.0.0 version in BW

SAXException validation errors while querying MDM using MDM plugin 2.0.0 version in BW

book

Article ID: KB0078621

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks Plug-in for MDM 2.0.0

Description

Validation errors are thrown while querying MDM using MDM plugin 2.0.0 version with the below error.

Cannot validate web service request XML due to: ''org.xml.sax.SAXException: Validation Errors [Warning Line 1: cvc-enumeration-valid: Value '' is not facet-valid with respect to enumeration '[MetaData, ValidValues, ValidValuesInit, Add, Modify, Records, Record, RelatedRecords, RelationshipTargets, DeleteAll, Record/NoProcess, RelationshipTargets/NoProcess, DeleteAll/NoProcess, Validate/Process, Validate/NoProcess, NoValidate/NoProcess, NoValidate/Process, Validate/ProcessOnDataChange, NoValidate/ProcessOnDataChange, FACTSHEET, CatEditChange, CatEditDelete, CatEditImport, CatEditAdd, CatEditAccepted]'. It must be a value from the enumeration.
, Warning Line 1: cvc-attribute.3: The value '' of attribute 'commandqualifier' on element 'ns:MasterCatalogRecord' is not valid with respect to its type, 'MasterCatalogRecordCommandQualifierType'

This is because of the empty string for command qualifier which is not a valid value as per the schema definition in plugin version 2.0.0.

Issue/Introduction

SAXException-validation-errors-while-querying-MDM-using-MDM-plugin-2-0-0-version-in-BW

Environment

All

Resolution

This issue is fixed in 6.3.1 MDM plugin version which allows the empty string for command qualifier. Moving to 6.3.1 plugin also requires a change in BW version which has a minimum requirement of 6.4.x.

So, in-order to avoid version changes. Please set the below property value in configValues.xml to "false" which is the default value and continue using 2.0.0 MDM plugin.

<ConfValue description="This property enables inbound web service request validation. The incoming request will be validated according to the XML Schema, which adds some overhead. Default is false." isHidden="false" isHotDeployable="true" name="Web Service Request Validation" propname="webservices.inbound.xmlvalidation" sinceVersion="7.0" visibility="Advanced">
                <ConfBool default="false" value="false"/>
            </ConfValue>