PI 7.1 XML Validation in Integration Engine.

Hi Experts,
In PI 7.1 XML vallidation in AAE what would be the proper path drectories structure?
Sri

Hi,
>> In PI 7.1 XML vallidation in AAE what would be the proper path drectories structure?
Create appropriate directories structure where you have to save our 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://sapxi.com/XI/FileToFile then folder name should be httpsapxi..comXI~FileToFile
Abid Mazhar

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.

How to remove XML messages from Integration Engine

Hi,
i had created file - XI -file scenario activated it and check messages using tcode SXMB_MONI .Error messages coming after every minute as i set polling intervals to 60 seconds .Now i had deleted related objects from IR and ID but still XML messages coming in ....please anyone can help to stop this scenario anyhow.

Dear Jai ,
i had checked everything before this and even i have checked now and i had created that scenaio by my own userid and passwd. Checked sender interface, reciever interface in SXMB_MONI it's the same which i had given name to them . Even we people are surprised that after deleting all the things in IR and ID . i don't know exactly why it is coming but what i am guessing is that after activating the scenarios it might get executed from XI runtime cache and there is no dependency on IR and ID objects . so what i had done that i completely refreshed the XI Runtime Cache by using tcode SXI_CACHE but it's still not working that way also.
Message was edited by:
ashwin dhakne
Message was edited by:
ashwin dhakne

XML Validation Not Working.

Hi Dear Experts.
I have an scenario Proxy to JDBC - Dual Stack , on Receiver Agreement I checked the option Validation by Integration Engine . I made a test in Test Message on NWA Task and the validation is fine. However when I sent the message from ABAP Proxy the validation is not working.
Can you help me?
Regards.

Can you see your xsd in NWA??
NWA → Cache Monitoring → Mapping Runtime.
or
PIMON → Monitoring → Mapping Runtime → Cache Monitor
@Sarojkanta Parida : IN PI 7.4 version we dont need to place xsd in any location, We just need to select Schema Validation option in Sender/Receiver Agreement, and it will be activated.
Regards
Osman

XML Validation with multiple XSD files (referenced)

Hello,
I know that XML validation with version 7.1 is possible now. However I was provided with a set of XSD files that have references to each other and need to be placed in a hierachical file system order so that references can be resolved.
An element <xsl:include schemaLocation="../../baseSchemas/baseSchema.xsd" /> is used for example. How can I handle that for XSD validation in PI? Can I create the same folder structure or do I need to put all XSD files in one directory and change the import manually?
But most important question: Is it possible it all to use more than one XSD for schema validation?

Dear Florian,
I had encountered such case in a project.
I was given 3 files. One main file and 2 others called Schema1.xsd and Schema2.xsd.
This happens because your data type is not in single namespace, but is being referred across namespaces and software components.
I am assuming that you have read the How to Guide for XML validations on PI 7.1
Best way to do this quickly is as follows.
1. Enable XML validation at adapter engine in the sender agreement.
2. Post a message using HTTP post. (http://sappihttpclient.codeplex.com)
3. Check communication channel in runtime workbench. There will be an error saying which is missing at what path.
4. Create the path mentioned and place the file at that path.
5. Repeat steps 2,3,4 for all the files.
When you are done with this, you will get a proper validation error in case XML file is not correct. And remember to generate XSD from message type and not data type.
Regards,
Vikas
Edited by: Vikas Aggarwal on Sep 2, 2009 8:45 PM
Edited by: Vikas Aggarwal on Sep 2, 2009 8:48 PM

Problems with namespace XML Parsing of ABAP PI 7.0 Integration Engine

Hi,
I discovered the following problem.
The customer sends a SOAP message with is forwarded through a SOAP Adapter in the integration engine.
The structure of the message is very simple:
<Envelope>
<Body>
<ORDERS05>...</ORDERS05>
</Body>
</Envelope>
The customer adds the namespace information a special way:
<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope">
<Body>
<orders05 xmlns="">...</orders05>
</Body>
<Envelope>
Here the namespaces is declared in the first element. It should be inherited into all child elements. The 'orders05' should not have the namespace ' xmlns="http://schemas.xmlsoap.org/soap/envelope" ', therefore the namespace is overwritten with ' xmlns="" '. However I don't know if this is a correct xml statement, the SAP system did not understand this.
The integration throws an error which is stated in the message in the adapter engine:
2008-11-06 17:31:44 Fehler SOAPFault empfangen vom Integration Server. ErrorCode/Category: XIProtocol/ITEM_MISSING; Params: /@mustUnderstand, ST: ST_XMS_MSGHDR30_RM; AdditionalText: Attribut 'mustUnderstand' erwartet; ApplicationFaultMessage: ; ErrorStack: Das XML-Element /@mustUnderstand fehlt im SOAP-Message Header (SAP XI Extension) Attribut 'mustUnderstand' erwartet
2008-11-06 17:31:44 Fehler Fehler beim Übertragen der Message zum Endpunkt http://kas052.hauni.koerber.de:8036/sap/xi/engine?type=entry über die Verbindung SOAP_http://sap.com/xi/XI/System. Grund: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header
If I changed the SOAP message to the common format, it is accepted by the integration engine.
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope">
<SOAP:Body>
<orders05>...</orders05>
</SOAP:Body>
</SOAP:Envelope>
Here the namespace ' xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope" ' is defined with a prefix and assigned to the elements 'envelope' and 'body'. The 'orders05' element has no namespace.
However due to the xml syntax both messages are the same, so why the integration engine handle the messages different?
Best regards,
Nils Kloth

The valid SOAP format supported by XI is as follows
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
    <m:MessageTypeName xmlns:m="Some-URI">
      <Price>34.5</Price>
    </m:MessageTypeName>
</SOAP:Body>
</SOAP:Envelope>
Ur sender system is not sending the data in correct Soap format and thats the cause of message rejection. The option you have to use the Soap adapter in "no soap" mode.
Regards,
Prateek

XML Validation with XSD in java mapping

Hi experts,
I have created an interface to send differents messages between bussines system, the bussiness system receiver is put in the message, to get this value I have a configuration file indicating the path of this field for each message type. In a java mapping I transform the message sent in this structure:
<document>
<message>HERE THE MESSAGE AS STRING</message>
<parameters>
<sender>HERE SENDER BUSSINESS SYSTEM</sender>
<receiver>HERE RECEIVER BUSSINESS SYSTEM</receiver>
</parameters>
</document>
the messaging interface works fine, but now I have to validate the XML vs XSD. I need doing in a java mapping because the messaging interface send the message and a email to sender in error case.
To do this validation I have implemented two java mappings that works fine in my local, the first way is with class Validator of java 5, but my system PI 7.1 return an error with this class. The second way is with SAX parse:
String schema = "XXXXXxsd";
DocumentBuilderFactory docBuilderFactory = DocumentBuilderFactory.newInstance();
docBuilderFactory.setNamespaceAware(true);
docBuilderFactory.setValidating(true);
docBuilderFactory.setAttribute("http://java.sun.com/xml/jaxp/properties/schemaLanguage","http://www.w3.org/2001/XMLSchema");
InputStream is = this.getClass().getClassLoader().getResourceAsStream(schema);
docBuilderFactory.setAttribute("http://java.sun.com/xml/jaxp/properties/schemaSource",is);
in my local works fine but in PI always return OK never fail.
For this moment the schema is hardcoded to do proofs, in the future will be loaded from my configuration file.
Any idea?
Thanks in advance
Jose

hi Jose,
PI 7.1 has a built in feature available called XML vaidations ..
your source xml can be validated against a XSD placed at a specific location on the PI server..
validation can be performed at adapter/integration engine
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06dff94-9913-2b10-6f82-9717d9f83df1?quicklink=index&overridelayout=true

Xml validation in File to RFC Sync Scenario with Validation fails message

Hi All,
We are using PI 7.4 (Dual Stack) the Requirement is File to RFC Sync Scenario(File <---> RFC).and need to do XML validation against XSD Schema. if any Validations fails Response message should send back to sender.RequestResponseBean standard module is using for File to RFC Sync scenario but how to send the response message to sender if any validation fails. adapter level XML validation is not helpful for this requirement. please help out me how to achieve the requirement with graphical mapping.
Thanks in advance.

to validate schema you cannot solve it with graphical mapping but validating the schema in the AAE or the integration engine.
y recomend you to use the AAE validation at sender side, coz the sender system will be notified in case of schema errors.
The response will be validated at Integration Server level.
you can search in the forum, you will get many document about how to configure it.
take a look to my blog: PI 7.3 - XML Validation

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

Java bean, works in Integration Engine but does not work in Adapter Engine.

In connection to the following thread:
PayloadZipBean - variable filename inside the archive
I am trying to use the same bean.
However I can see, that the bean is working correctly when I use Integration Engine.
But if I am using ICo (AAE) and using the same bean in the receiver, I can see, that the bean gets called but does not work correctly.
The audit log added to my bean shows, that the bean could read the filename correctly from the Dyanic Config in the message, but it cannot write the same into the message.
Could you please help on this?

Your above posted system details show multiple Java Console extensions.
You can uninstall (remove) the Java Console extensions and disable the Java Quick Starter extension, you do not need them to run Java applets.
See http://kb.mozillazine.org/Java#Multiple_Java_Console_extensions
See also http://www.java.com/en/download/help/quickstarter.xml - What is Java Quick Starter (JQS)? What is the benefit of running JQS? - 6.0
Disable the Java Quick Starter extension: Tools -> Addons -> Extensions
Control Panel -> Java -> Advanced tab -> Miscellaneous -> Java Quick Starter (disable)
You can try a direct connection: <br />
Control Panel > Java > General tab > "Network Settings...": "Direct Connection" (enable)

XML Validation - How to raise an alert

Hi PI Experts,
I enabled XML validation at "Validtion by Adapetr Engine". Its working fine. But how to integrate XML validation error with Alert Monitoring. Please advise.
Here below the error from Audit log:
2010-03-18 18:33:13     Information     The application tries to send an XI message asynchronously using connection File_http://sap.com/xi/XI/System.
2010-03-18 18:33:13     Information     Backward validation is enabled
2010-03-18 18:33:13     Error     Unable to validate the message with message ID b01d356e-1801-4b93-29fb-9ed84b25c6a3
2010-03-18 18:33:13     Error     Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: cvc-enumeration-valid: Value '11' is not facet-valid with respect to enumeration '[1, 2, 3, 4, 5, 6, 7]'. It must be a value from the enumeration. at line 15, column 34
2010-03-18 18:33:13     Error     MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: cvc-enumeration-valid: Value '11' is not facet-valid with respect to enumeration '[1, 2, 3, 4, 5, 6, 7]'. It must be a value from the enumeration. at line 15, column 34
2010-03-18 18:33:13     Error     File processing failed with com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: cvc-enumeration-valid: Value '11' is not facet-valid with respect to enumeration '[1, 2, 3, 4, 5, 6, 7]'. It must be a value from the enumeration. at line 15, column 34
Thanks...
Ravi Kanakam

Hi Ravi,
Are you getting other adapter engine alerts? Or only you are not getting xml validation ones? Also take a look at this:
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
Regards,
---Satish

Error in integration Engine

Hi All,
In integration Engine im getting error as "Exception occurred during XSLT mapping of the application".
when i tried to test the mapping its showing the warning as "javax.xml.transform.TransformerException: com.sap.engine.lib.xml.util.NestedException: Could not execute operation on Java Object. -> java.lang.reflect.InvocationTargetException at "
Please help me reagrding this issue to proceed further!!!

Hi,
Can u please explain the problem little detail...
Are u getting this error in SXMB_MONI??
If yes then can u copy the source payload and check it in the Message Mapping once??
If problem is coming from mapping... try to analyze.. else u can put now vtz exactly the prblm is..
Babu

HTTP error 403 from Integration engine

Hello,
Problem a)
While posing data from eSourcing to PI box by HTTP , we are getting HTTPerror 403.
The error message states:
ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL:
Problem b)
In another observation the sender file adapter after polling the file is unable to send the message to Integration engine and gives a Connection Time out error. it gives the following error.
Transmitting the message to endpoint http://<Host>:<Port>/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: Error transmitting the message over HTTP. Reason: java.net.ConnectException: Connection timed out: connect.
I believe that both the errors are for common cause and possibly the Integration engine is not accepting HTTP request.
It looks like these error due to security reason, it seems some authorization profile is missing or may be some other issue,kindly help us at that front.
Thanks and Regards,
Satish

Hi Suraj,
Thanks for the update.We had checked the URL before posting this message,it is picking up correct URL with namespoace, UID and PWD.Exact error that we are getting is as follows:
ID: E-Sourcing was unable to publish PROP-00090--2010 to ERP. class java.io.IOException Server returned HTTP response code: 403 for URL: http://MB1ES1025:50200/sap/xi/adapter_plain?namespace=http://frictionless.esource.com/v2.0&interface=MI_ESI_AWARD_PO&service=FCI_TENANT&QOS=BE&sap-user=pisuper&sap-password=sap$29&sap-client=001&sap-language=EN. Please contact your system administrator.
Here all information are correct.We have checked the SLD check, that is also working fine.Also it is not connectivity related issue, as we are able to transmit XML file to E-Sourcing.
It looks like security issue, but what authorization needs tobe given exactly for HTTP call, we need to know or may be some other issue.
Thanks and Regards,
Satish

XML Validation

Since there is no XML validation currently in the Flex/Flash framework, I've decided to start a class that parses a string in an effort to validate the markup, returning whether the XML is valid. I have a need for it in my non-server based application, and have read in numerous places where there is desire for it as well. I have built the class far enough to get the ball rollin', but figure it should be :
A) available to the community
B) able to be improved upon by the community
If you improve upon the code, please post your work here so everyone can benefit.
Here is the source code :
XML Validator : v0.2 - last edit by Justin Myers | J2 CREATIVE MEDIA DESIGN
NOTES:
Parser is a bit weak and needs work.
Still need to :
- Make sure tags are ended properly
- Make sure there is space between tag name and attribute
Parser currently handles :
- Making sure there is no space between tags (with exception to white space)
- Making sure that attributes open and close properly
- Making sure there is proper space after an attribute or that it is immediately followed with the tag closing
package community.classes.parsers
       public class XMLValidator
              public function XMLValidator()
              public static function validate(str:String , ignoreWhiteSpace:Boolean = true):Boolean
                      // validation defaults to true (innocent til proven guilty)
                      var valid:Boolean = true;
                      // minimum char length to be valid XML
                      if (str.length < 4)
                             valid = false;
                      var withinTag:Boolean;
                      var withinAttribute:Boolean;
                      var tags:Array = [];
                      var tag:String;
                      for (var i:uint = 0 ; i < str.length ; i++)
                             var char:String = str.charAt(i);
                             // if we are closing a tag
                             if (char == ">")
                                    // invalid if we never opened a tag, or if we never closed the last attribute
                                    if (!withinTag || withinAttribute)
                                           valid = false;
                                           break;
                                    else
                                           withinTag = false;
                                           tags.push(tag);
                             // invalid if last character is not a closing tag
                             else if (i == str.length - 1)
                                    valid = false;
                                    break;
                                    // if we are entering a tag
                             else if (char == "<")
                                    // invalid if we haven't closed the last tag
                                    if (withinTag)
                                           valid = false;
                                           break;
                                    else
                                           withinTag = true;
                                           tag = "";
                                    // all other characters
                             else
                                    if ((char != " " || char != "\n") || ((char == " " || char == "\n") && !ignoreWhiteSpace) )
                                           // invalid if there are any characters between tags
                                           if (!withinTag)
                                                  valid = false;
                                                  break;
                                           else
                                                  if (char == "\"")
                                                          // entering attribute
                                                          if (!withinAttribute)
                                                                 // invalid if = does not preclude ", or there is space before =
                                                                 if (str.charAt(i-1) != "=" || str.charAt(i-2) == " ")
                                                                        valid = false;
                                                                        break;
                                                                 else
                                                                        withinAttribute = true;
                                                                 // exiting attribute


961190 wrote:
so whats the best way to store Rules?
How to get the data validated with those rules given the source data is in a xml file
The "integrity rules"?
Since they have to be ececutable code I'd suggest Java classes...
How to get the data validated with those rules given the source data is in a xml file
as @hsc71 wrote, that each XML element select the rules this particular element should pass and run each rule with the current element as parameter.
This meight be easiser in the Rules have a common interface like
interface Rule{
public boolean isPassedBy(XmlElement theCurrentElement, XmlElement theRootElement);
You could use the ServiceRegistry class from the JVM to fetch the known rules, so that you can add new ones with minimum effort.
bye
TPD

Integration Engine Monitor with PI Payload Search (Tcode: ZMONI)

Hi Team,
Good day.
I have been trying to search the internet on how to use the PI Payload Search (PIPS) functionality of the Integration Engine Monitor (Tcode: ZMONI) but so far I did not find one.
Does anyone know how to use every functionality of the PI Payload Search? Is there a manual or a how-to document for this function?
The PI Payload Search tab contains the following fields:
Sender
     Idoc Number
     Idoc Message Type
Message Version
     Message version
     Content To Be Searched
     Mime Type
     Payload Sequence Number
Message Size Selection
     Message Bytes
Content Search
     Namespace
     XML Element Name
     XML Search Value
Output Format
     Output to ZIP
     Filename
     GUI Download Path
     HTTP_POST URL
     FTP Server
     FTP User
     FTP Pwd (scrambled)
     FTP Directory
When executing Variant
     Change TVARV for dates
I could send you an email if you need more information or screenshot. Thank you in advance
KR,
Carlo
Edited by: Carlo Borja on Dec 23, 2011 5:20 AM

Hi. Carlo
Correct me if I wrong, this tx is customized , it's not standard.
However , you can search using
TREX . :
       http://help.sap.com/saphelp_banking60/helpdata/en/47/06b054c7750e8ae10000000a155369/content.htm
WithOut TREX :
       Payload Searching without TREX
Regards.
Luis Ortiz

PI 7.1 XML Validation in Integration Engine.

Similar Messages

Maybe you are looking for