"semantic checks during XML Validation"

What did SAP pepole ment saying the above subject in the XML validation page of PI 7.3?
Does PI supprots only "shallow" validation of structure rather then "deep validaiton" of data type patterns for example?
if not duiring validation then when?
http://help.sap.com/saphelp_nw74/helpdata/en/44/0bf1b3ec732d2fe10000000a11466f/frameset.htm
Appreciate your insights.

This is a basic problem. When you define a field as integer you cannot declare blank space which represents String type.
So for your case make the value 'zero' instead of blank, if you want do declare the field as integer and as below...
<xs:element name="Num">
<xs:simpleType>
 <xs:restriction base="xs:integer">
 <xs:pattern value="[0-3]"/>
 </xs:restriction>
</xs:simpleType>
</xs:element>
Also refer this page for further reference.
http://www.w3schools.com/schema/schema_facets.asp

Similar Messages

Java.lang.Exception error during XML validation by Integration Engine

Hi professionals,
We are trying to use XML validation by the Integration Engine.
Step 1:
We created an appropriate directory structure where we had to store the structure (xsd).
\usr\sap\<system id>\SYS\global\xi\runtime_server\A\B\C\D\E\F
A - validation
B - schema
C - GUID of the SWCV where service interface reside.
D - Repository Namespace where Service Interface is created.
E - Service Interface Name
F - Repository Namespace where Message Type or External Definition is
assigned.
Step 2:
We also changed the references in the xsd to exclude all the subdirectory references.
e.g folder1/folder2/abc.xsd is become abc.xsd only
Step 3:
We stored both xsdu2019s (schema xsd and referenced xsd to the directory created in step 1)
Step 4:
We changed the directory and xsdu2019s permissions to 777 (we chose 777 for testing purpose).
Step 5:
We changed the property schema validation of the sender agreement to Validation by Integration Engine.
Step 6:
We checked RFC destination for AI_VALIDATION_JCOSERVER on AS ABAP and AS Java and establish an successful connection test.
RESTULTS
The result of those steps is an error message in the message monitor of PI with the error tekst:
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="XML_VALIDATION_INB">CX_XMS_SYSERR_VALIDATION</SAP:Code>
<SAP:P1>java.lang.Exception</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>not used at the moment.</SAP:AdditionalText>
<SAP:Stack>System error occurred during XML validation</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please assist in how to solve this issueu2026.
Regards, Sjaak.

I would suggest follow Appendix A to know the exact path and since you have one XSD referring other XSD check the steps mentioned in Appendix B .... there seems to be some error in referencing ...Appendix A and B are on page 12 & 13 of this document:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06dff94-9913-2b10-6f82-9717d9f83df1?quicklink=index&overridelayout=true
Regards,
Abhishek.

Handling empty values during xml validation

Hello experts,
I have a file to file scenario in PI 7.1. I am using xml validation to validate the incoming source file. There are various types of fields in the incoming file including int, decimal and string. They can have a certain enumeration of values but can also have a blank value.
For example field 'Num' of type int can have values 1,2,3 or a blank value.
But I am not able to define a blank value for the field in the enumeration during definition. Therefore a blank value in the input file fails during the validation stage.
Is there any workaround for this?
Thanks!
RR

This is a basic problem. When you define a field as integer you cannot declare blank space which represents String type.
So for your case make the value 'zero' instead of blank, if you want do declare the field as integer and as below...
<xs:element name="Num">
<xs:simpleType>
 <xs:restriction base="xs:integer">
 <xs:pattern value="[0-3]"/>
 </xs:restriction>
</xs:simpleType>
</xs:element>
Also refer this page for further reference.
http://www.w3schools.com/schema/schema_facets.asp

XML validation in WS adapter

Hi experts,
I get the following error message in SXMB_MONI while processing a message through a WS sender adapter:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<n0:Fault xmlns:n0="http://schemas.xmlsoap.org/soap/envelope/">
 <faultcode>n0:Server</faultcode>
 <faultstring xml:lang="en">SRT: Failure in SOAP processing occurred</faultstring>
 <detail>
 <ns:SystemFault xmlns:ns="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/">
 <Host>Integration Server Entry</Host>
 <Component>COREMSG</Component>
 <ChainedException>
 <Exception_Name>CX_XMS_XI_SYS_ERR</Exception_Name>
 <Exception_Text>System error</Exception_Text>
 </ChainedException>
 <ChainedException>
 <Exception_Name>CX_XMS_SYSERR_VALIDATION</Exception_Name>
 <Exception_Text>System error occurred during XML validation</Exception_Text>
 </ChainedException>
 </ns:SystemFault>
 </detail>
</n0:Fault>
This is strange, because I didn't configure any XML validation. I didn't configure that explicitly.
However, I noticed that the step "XML Validation Inbound Channel Request ( CENTRAL )" is executed every time I send messages to PI. Normally this is successful, so the message flow is not interrupted. But even in the successful case the xml header is always cut off (so the line "<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>" in the beginning). I checked other messages with different adapters, and this step is never executed.
I would like to know whether this step can be switched off somewhere or whether it is performed by default. Does anybody know more about this topic?
Best regards,
Jörg

Hi Hema,
As per understanding you need to check one or few fields value is integer or not.
You can achieve in 2 ways :
Case1:Using inbuilt xml validation options.
For 7.11 and below
1)In ESR/Message type/Export the xsd to local machine.
2)Insert the xsd file in the below loc
/usr/sap/<sid>/DVEBMGS00/j2ee/cluster/server0/validation/schema/
<guid>/<namespace1>/<service_interface_name>/<namespace2>
<sid>: System ID of the server instance.
<guid>: The GUID of the SWCV.
<namespace1> : The namespace within which the service interface is defined.
<service_interface_name> : The name of the service interface.
<namespace2>
: The namespace of the Message Type used by the service interface. In many
instances, namespace1 and namespace2 are the same.
Italic path folders need to create by you.
For 7.3 and above
Michal's PI tips: XML validation - changes in 7.3
Case 2 :Handling using simple UDF.
Input-->UDF-->Output
try {
 Integer.parseInt(input);
 return input ;
catch(NumberFormatException e) {
throw new StreamTransformationException( "Input field value for xyz field "+input+"is not in integer format.Plz correct it");
Regards
Venkat

Regarding error in xml validation 7.1

Hi
I am doing file to idoc scenario. In the sender agreement i selected validation by Adapter and uploaded the particular xsd.after executing the scenario in runtime workbench it is showing sucessfully processed but in the MDT audit log I am getting following error.without validation the file is posting in target system.but when I check the validation by adapter it is giving following error.
Received XI System Error. ErrorCode: CX_XMS_SYSERR_VALIDATION ErrorText: not used at the moment. ErrorStack: System error occurred during XML validation
Transmitting the message to endpoint http://orcdapp1.edfapps.edfenergy.net:51100/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: CX_XMS_SYSERR_VALIDATION:not used at the moment..
Please give me your inputs.
Regards
venkat.

Hi Venky,
This error due to incorrect path So please check whether you have used the correct path or not?
Create appropriate directories structure where we have to save your structure (xsd).
\usr\sap\<system id>\SYS\global\xi\runtime_server\A\B\C\D\E\F
A - validation
B - schema
C - GUID of the SWCV where service interface reside.
D - Repository Namespace where Service Interface is created.
E - Service Interface Name
F - Repository Namespace where Message Type or External Definition is assigned.
Note: if your ESR namespace contains special character then do replace it with u201C~u201D in folder name.
If namespace is http://abc.com/XI/FileToFile then folder name should be replace with httpabc.comXI~FileToFile
Export schema from the ESR and save it in folder u201CFu201D with name <<RootElementOfMessageType>>.xsd. So in this case it is MT_File_Sender.xsd
Regards,
Sameer
Edited by: sameer Khanna on May 27, 2009 10:14 AM

How to obtain XML error node after XML validation

Hello,
We are developing a web application which uses XML documents.
We try to obtain the exact error which occurs during XML validation against a schema in order to alert users with a proper message - for example: "Invalid value for element date".
We validate our XML documents using DBMS_xmlparser. But it only retuns a string message indicating there is an error and document cannot be validated. What can we use to reference to the node object which contains the error?
We develop our application under Oracle 9.2.0.4.
Any help will be appreciated.

Validate with a DOMParser or a SAXParser.
Set a ErrorHandler on the parser.
The custom ErrorHandler class should override the startElement & endElement methods of the DefaultHandler class.
private class Validator extends DefaultHandler
       public boolean validationError = false;
       public SAXParseException saxParseException=null;
       public void error(SAXParseException exception) throws SAXException
           validationError = true;
           saxParseException=exception;
       public void fatalError(SAXParseException exception) throws SAXException
            validationError = true;
            saxParseException=exception;
       public void warning(SAXParseException exception) throws SAXException
       public void startElement(String uri,
                         String localName,
                         String qName,
                         Attributes attributes)
                  throws SAXException{
         System.out.println("Start Element: "+qName);
         public void endElement(String uri,
                       String localName,
                       String qName)
                throws SAXException{
         System.out.println("End Element: "+qName);

XML validation in sender file adapter

Hi
I am using FCC on the sender file adapter ....i need to make sure that one of the fields should always be integer else the sender adapter should give error
Can i use xml validation with FCC on the sender file adapter?

Hi Hema,
As per understanding you need to check one or few fields value is integer or not.
You can achieve in 2 ways :
Case1:Using inbuilt xml validation options.
For 7.11 and below
1)In ESR/Message type/Export the xsd to local machine.
2)Insert the xsd file in the below loc
/usr/sap/<sid>/DVEBMGS00/j2ee/cluster/server0/validation/schema/
<guid>/<namespace1>/<service_interface_name>/<namespace2>
<sid>: System ID of the server instance.
<guid>: The GUID of the SWCV.
<namespace1> : The namespace within which the service interface is defined.
<service_interface_name> : The name of the service interface.
<namespace2>
: The namespace of the Message Type used by the service interface. In many
instances, namespace1 and namespace2 are the same.
Italic path folders need to create by you.
For 7.3 and above
Michal's PI tips: XML validation - changes in 7.3
Case 2 :Handling using simple UDF.
Input-->UDF-->Output
try {
 Integer.parseInt(input);
 return input ;
catch(NumberFormatException e) {
throw new StreamTransformationException( "Input field value for xyz field "+input+"is not in integer format.Plz correct it");
Regards
Venkat

The user name or password is incorrect in the CRM system checks during installation

Hi everyone
I'm installing CRM 2013 on 2 servers (server 2012) - CRM Full server + SQL Server 2012.
I created 2 service accounts for this - CRMSVC + CRMSANDBOX (one for sandbox and another one for all the rest).
I'm getting the following error in the system checks during setup:
I've verified a billion times that the service accounts and passwords are valid - I even tried using different service accounts - same problem. As for now I also added the service accounts to the local admins groups just to be sure that it's not some permissions
issue (I also added them to the 'log on as service' & performance logs groups).
If i try to use NETWORK SERVICES instead of a service account - the installation goes through flawlessly - no issues at all.
I'm also gonna say that i tried another installation on a fresh server - SAME ISSUE.
So for now my ideas are either it's a GPO somehow blocking the service accounts - or some kind of other security issue.
I also found out that the security event log shows these two errors when these show up in the system checks:
Inside i found 'NULL SID' entry - it does not recognize the service accounts account and 0xC0000064 in the Sub
Status Codes
It's not a typo issue so don't bother - if i write a wrong password in purpose - it actually says that the password i typed for domain\service account is incorrect - here it seems that the service account is not being recognized.
Any ideas anyone?
Thanks
Please vote if you find my post helpful - Thanks

Not sure you understood my point.
The installation process necessarily runs under the account of the installing user. The installation will query AD to identify information about the service accounts, and will add them to the relevant CRM AD groups. It is possible that the installing user
account does not have sufficient privileges on the AD objects for the service accounts to be able to identify them, and to add them to groups. This scenario is consistent with the errors that you get, and also with being able to install CRM to run under NetworkServices
(which doesn't have its own AD object)
Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk
Hi David
I understand this, but as far as i know running it under NETWORK SERVICES will add the machine names to the OU security groups - hence the user installing still needs to have delegated permissions on that OU. Anyway as mentioned above - ignoring the checks
and running the installation solved this and also added the accounts to the security groups - so this whole mess looks like some bug to me - not sure i will ever find out what it was :)
Please vote if you find my post helpful - Thanks

XML validation error while parsing MXI Manifest

Hi,
I have created an hybrid extension for Photoshop. I want to upload my extension on Adobe Exchange. during the upload process I get an error,
"XML validation error while parsing MXI Manifest: Declarations can only occur in the doctype declaration. Line: 19 Position: 791 Last 80 unconsumed characters".
The error description specifies that description in MXI file is not valid. Below are the contents of my MXI file.
<macromedia-extension
 name="yyy"
 id="com.yyy"
 version="1.0.0"
 type="object"
 requires-restart="true">
 <author name="abcd" />
 <products>
 <product familyname="Photoshop" maxversion="" primary="true" version="12.0"/>
 </products>
<description>
 <![CDATA[
abcd qwertyuioipafgjhkjljljklkjl
 
Open Extension via: Photoshop top menu > Window > Extensions > abcd.
 
Online support at: <a href="http://www.abcd.com/help.php">http://www.abcd.com/help.php</a>
 ]]>
</description>
<ui-access>
 </ui-access>
<license-agreement>
</license-agreement>
<files>
 <file destination="$ExtensionSpecificEMStore/com.abcd/html/abcd.html" products="" source="zxp-support/Description/abcd.html"/>
 <file destination="$ExtensionSpecificEMStore/com.abcd/html/abcd.png" products="" source="zxp-support/Description/abcd.png"/>
 <file destination="" file-type="CSXS" products="" source="abcd.zxp"/>
 <file destination="$automate" file-type="plugin" platform="mac" products="Photoshop" source="mac/abcd.plugin"/>
 <file destination="$automate" file-type="plugin" platform="win" products="Photoshop32" source="win32/abcd.8li"/>
 <file destination="$automate" file-type="plugin" platform="win" products="Photoshop64" source="win64/abcd.8li"/>
</files>
</macromedia-extension>
Can anyone please point out why am I getting the error?
Thanks

Hi CarlSun,
Thanks for the reply. I have made the changes suggested by you.
I have few queries:
1. Can we use attribute "source" in the description tag?
 I have created a local html page and specified it in source attribute. but the Extension Manager CS6 did not render the local html page and displayed the following:
 No description avaliable. Click the following link for more details.
 "http://www.abcd.html". Is it possible to display a local html page in Extension Manager CS6?
2. Can I display an image (png) in CDATA under description tag? If yes, then can you please guide me how can I do so?
3. As suggested in tech notes MXI file must include UTF-8 encoding as header (<?xml version="1.0" encoding="UTF-8"?>). The MXI I am using does not have this header. Do I need to include the header?
Thanks

PARSE_APPLICATION_DATA Error during XML = ABAP conversion: Response Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SAS0446CC11CC6EC1AD4789 Line 24 An error occurred when deserializing in the simple transformation program /1SAI/SAS0446CC11CC6EC1AD4789

Hi Experts ,
i have a scenario proxy to soap where i am getting error while getting the response .
we are sending the request successfully and getting response .some times we are getting in proxy level error below
PARSE_APPLICATION_DATA Error during XML => ABAP conversion: Response Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SAS0446CC11CC6EC1AD4789 Line 24 An error occurred when deserializing in the simple transformation program /1SAI/SAS0446CC11CC6EC1AD4789 (Cha
Please help us to fix this bug in proxy response.
Regards
Ravi

Hello Ravinder,
Can you please post the complete stack trace, it seems to be some fields are getting truncated i,e data sent from the program to the proxy object might be violating some length restrictions.
Please check your message interface field lengths and what is being passed to the proxy.
Regards,
Ravi.

Xml validation ---- file system of PI ???

hi all ,
i read the xml validation concept of PI7.1 . iam unable to find any practical explanation about the following
"To validate the structure of a PI message payload, you should export the schemas from the ESR and save them in the file system of PI. "
save them in the file system of pi ... where does this mean to be stored ?.
will it be necessary for both the ADAPTER ENGINE & INTEG ENGINE VALIDATION?
Please give any other important aspect of this validation concept which u came across during ur practical implementation
THANKS IN ADVANCE

Hi Netaji,
Validating the XML documents is a new feature introduced in SAP NetWeaver Process Integration 7.1. The validation can be performed at two different locations - Integration Server or the Adapter Engine. Validations can be done in both synchronous and asynchronous operations.
In the synchronous scenario or using an adapter that can handle synchronous messages (e.g. HTTP and SOAP adapters), when a validation error occurs, the error message will be returned to the sender. In the case of asynchronous scenarios (e.g. file adapter), the error message will be logged to the SXI_MONITOR when the validation is done in the Integration Server or to the Runtime Workbench (RWB) when the validation is done in the Adapter Engine. In both cases, the messaging will be terminated with error.
Both Integration Server and Adapter Engine can be used for validating XML from the sender. However, only the Integration Server can be used to validate the XML when sending to the receiver. The XML validation configurations are done in either the Sender Agreement or the Receiver Agreement.
In the current release, as of PI 7.1, the XML schema (or XSD) to be used for the XML validation has to reside in a file directory under the JEE. The XSD file has to be explicitly copied into a specific directory, depending on where the validation is to be performed.
Regards,
Leela

XML Validation with Java

I have created a XML file with dom4j and the file confirmed to be valid when I read the file with Internet Explorer, a online XML validator and a free XML editor called "CookTop". However, when I attemp to read the XML file during the execution of an ant task I always get the XML parsing exception that one of my tag is not closed. I have even wrapped that test inside the tag as CDATA but that does not help as well. Do any one know what's happening? Here's my environment:
JDK: 1.4.2_05
Xerces: 2.6.2
Ant: 1.5.3
Thanks so much in advance.
I've been pumping my head into the wall for hours : p

Can i know where to download the CookTop?or CookTop2?

XML VALIDATION WITH EXTERNAL DTD

I've the following problem:
I've stored a dtd into the xdb repository(with createresource function) and all seems work.
In this DTD i've declared some element and one entity in this way :
<!ENTITY emsp " " >
When i try to store or extract my xml (with sql extract function) i get :
ORA-19202 Error during xml processing
LPX-00217 : invalid character 8195 (\u2003)
I've to declare the entity in a different way ?
Thanks in advance
Giovanni

You might want to check out the XML DB forum FAQ rather than ask XML questions on the SQL and PL/SQL forum:
XML DB FAQ

XML validation with StAX

Hi,
I have a requirement to validate XMLs during JAXB unmarshalling and during StAX parsing. The schema is packaged in a jar. I am able to successfully read the schema, and validate the XML during unmarshalling by setting the schema in the unmarshaller (through setSchema()).
However, I am not able to validate it with StAX using the same schema and same XML.
Here is the code snippet for StAX:
StringReader stringReader = new StringReader(inputXMLStr);
XMLEventReader xmlEventReader = XMLInputFactory.newInstance().createXMLEventReader(stringReader);
EventFilter filter = new EventFilter() {
public boolean accept(XMLEvent event) {
return event.isStartElement();
XMLEventReader xmlFilteredEventReader = xmlif.createFilteredReader(xmlEventReader, filter);
Schema mySchema = getSchema(); // this method retrieves the schema by reading the schema files as
stream source and calling schemaFactory.newSchema(...)
Validator validator = mySchema.newValidator();
validator.setErrorHandler(new SchemaErrorHandler());
Source xmlSource = new StAXSource(xmlFilteredEventReader);
validator.validate(xmlSource);
I get a SAX Parse exception saying "cvc-elt.1: Cannot find the declaration of element 'myElement'"
And I also see the following exception:
Caused by: java.lang.NullPointerException
     at com.sun.org.apache.xalan.internal.xsltc.trax.StAXEvent2SAX.bridge(StAXEvent2SAX.java:171)
     at com.sun.org.apache.xalan.internal.xsltc.trax.StAXEvent2SAX.parse(StAXEvent2SAX.java:118)
     at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transformIdentity(TransformerImpl.java:651)
     at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:708)
     at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313)
     at com.sun.org.apache.xerces.internal.jaxp.validation.StAXValidatorHelper.validate(StAXValidatorHelper.java:89)
     at com.sun.org.apache.xerces.internal.jaxp.validation.ValidatorImpl.validate(ValidatorImpl.java:114)
     at javax.xml.validation.Validator.validate(Validator.java:127)
I am not able to figure out why the validation would work with UnMarshaller but not with StAX.
Any help appreciated.
Thanks
Meera

Have u tried the Stream STAX parser instead?
something like:
SchemaFactory factory = SchemaFactory
                         .newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI);
File schemaLocation = new File(XSD_FILE_PATH);
               Schema schema = factory.newSchema(schemaLocation);
// 3. Get a validator from the schema.
Validator validator = schema.newValidator();
ErrorHandler lenient = new ForgivingErrorHandler(fw);
validator.setErrorHandler(lenient);
XMLInputFactory staxFactory = XMLInputFactory.newInstance();
staxFactory.setProperty(XMLInputFactory.IS_REPLACING_ENTITY_REFERENCES,
                         Boolean.TRUE);
staxFactory.setProperty(XMLInputFactory.IS_SUPPORTING_EXTERNAL_ENTITIES,
                         Boolean.FALSE);
staxFactory.setProperty(XMLInputFactory.IS_NAMESPACE_AWARE,
                         Boolean.TRUE);
staxFactory     .setProperty(XMLInputFactory.IS_COALESCING, Boolean.TRUE);
FileInputStream fis = new FileInputStream(XML_FILE_PATH);
XMLStreamReader xmlr = staxFactory.createXMLStreamReader(fis);
validator.validate(new StAXSource(xmlr));

Xml Validation & XQuery Update

Hello,
I have a question on xml validation in Berkeley DB XML (2.5.16).
I read in documentation that an xml can be validated against an xml DTD or Schema when is loaded into a container. However, when an XQuery Update is to be executed is there any configuration that allows checking if the XQuery Update leads to an xml that does not conform with the DTD/Schema? If so, how this case is managed? The XQuery is executed, or not? Is there any exception thrown?
I made a test over this: I wrote an xml (and a related DTD) where an element contains an id attribute and another element a referencing attribute to the aforementioned id. Then, an XQuery Update 'delete' expression deletes the element with the id attribute. The element is indeed deleted, the xml is left in an inconsistent state and I am allowed of making more update operations to this document...
I was wondering if there is any way of handling this case, except from being careful with what updates you choose, so that the xml is kept in a valid state. Is there something I am missing?
thank you in advance,
theo

Hello,
I believe that XQuery execution does not support DTD yet. I'll investigate further and let you know what else I can find.
Thanks,
Sandra

"semantic checks during XML Validation"

Similar Messages

Maybe you are looking for