Help On schema validation

Hi,
I am a newbie in XML schema territory.
I generates a xml using 'SELECT XMLQuery( ...)' -- This finally works after upgrading to 10.2.0.3!
1) What methods do you recommend to validate the query result agaist the schema? The query result is first returned as 'XMLType' type, and then
I turned it into a CLOB.
At the end, I save the output into a file (via CLOB to String).
2) How do I register the schema in DB? Can I install the schema on the file system, instead? I am not sure which way is simpler and easier. I'd yearn for any simpler method, if any --- a common complaint from any beginner, I guess.
A few pointers will help me a great deal.
Sun

Sun,
You can take a look at an FAQ thread on this topic: How does XML DB handle XML Schema Validation ?
Regards,
Geoff

Similar Messages

Error in schema validation in XI. Please help!

Hi Experts,
I have a FILE to proxy scenario. In the sender agreement I have selected schema validation by Adapter. (Other option is by Integration Engine). Now when the file I get an error in sender file communication channel monitoring:
Error: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Schema DataIn.xsd not found in D:\usr\XXXXXXXXX\validation\schema\31f7c36098e411deadcae4d30a13c639\httptraining-00EIM_POC\DataIn_Async_Out\httptraining-00EIM_POC\DataIn.xsd (validation\schema)
Do I need to keep the schema file in some server location? Do I need to setup this path anywhere? Where do I need to place the schema file?
What is the difference between validation by adapter and by integration engine?
Please help!
Thanks
Gopal

>What is the difference between validation by adapter and by integration engine?
Both are same. One in Java engine and the other in the abap engine. If you set at one place that is good enough. In 7.1+ this becomes one of the pipeline steps.
>Do I need to keep the schema file in some server location? Do I need to setup this path anywhere? Where do I need to place the schema file
Yes you have to place schema in the server location.
Refer the Rajasekar document for the placing this file in the server location.

Urgent - please help with osb-service bus schema validation.

I have a proxyService runing on osb service bus, when I send wrong input to my proxyservices it react correctly by rejecting it, becuase the requestion is not conform to the schema, but I only get the error message saying that
the Input is does not much, is there a way to get more info about the error ?
like witch fields that cause the error ?

The fault variable in your stage error handler will have the approariate information. Just add a stage error handler in the stage you are doing schema validation (make sure that in validate action you are selecting "raise Error on validation failure") and the error handler log the $fault
Also refer -
Re: Validate each xml element against XML schema
Regards,
Anuj

Processing Schema Validation error in BPM?

Hi all,
We have a file to IDOC scenario where if the schema validation fails on the file adapter sender agreement, we want to pull the filename and send it in an error email. So, we are talking about the adapter specific message attribute "Filename".
unfortunately, this does not seem to be available as a container element for alert catagories in ALRTCATDEF. So, we are starting to look into using BPM to send a email via the email adapter. However, since the validation happens prior to BPM being called I am at a bit of a loss. Any ideas on how to get the email with the filename out to the suport group would be appreciated.
Thanks,
Chris

package com.validate;
import com.sap.aii.mapping.api.*;
import com.sap.aii.mappingtool.tf7.rt.Container;
import java.io.*;
import javax.xml.transform.stream.StreamSource;
import javax.xml.validation.*;
public class ValidateXML extends AbstractTransformation {
    public void transform(TransformationInput transformationInput, TransformationOutput transformationOutput) throws StreamTransformationException {
        OutputStream outputstream = null;
        try {
            InputStream inputstream = transformationInput.getInputPayload().getInputStream();
            outputstream = transformationOutput.getOutputPayload().getOutputStream();
            byte[] b = new byte[inputstream.available()];
            inputstream.read(b);
            String XMLinputFileContent = new String(b);
            // define the type of schema - we use W3C:
            String schemaLang = "http://www.w3.org/2001/XMLSchema";
            // get validation driver:
            SchemaFactory factory = SchemaFactory.newInstance(schemaLang);
            //Place XSD file in PI server same as http://help.sap.com/saphelp_nwpi711/helpdata/en/44/0bf1b3ec732d2fe10000000a11466f/frameset.htm
            //OR I think you can place any where on server.
            File XSDfile = new File("C:/xi/runtime_server/validation/schema/SchemaFile.xsd");
            // create schema by reading it from an XSD file:
            Schema schema = factory.newSchema(new StreamSource(XSDfile));
            Validator validator = schema.newValidator();
            // at last perform validation:
            validator.validate(new StreamSource(XMLinputFileContent));
            //If XML it not valid, exception will be thrown, if it is valid sent this PassOutputXML to output
            String PassOutputXML = "<?xml version=\"1.0\" encoding=\"UTF-8\"?><ns:MT_OutputXML xmlns:ns=\"http://sap.com/xi\"> <Name>FileName.txt</Name><Validation>Pass</Validation> </ns:MT_OutputXML>";
            outputstream.write(PassOutputXML.getBytes());
        } catch (Exception exception) {
            //Get File name using http://help.sap.com/saphelp_nwpi711/helpdata/en/43/03612cdecc6e76e10000000a422035/frameset.htm
            Container container = null;
            DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
            DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File", "FileName");
            String inputFileName = conf.get(key);
            String FailOutputXML = "<?xml version=\"1.0\" encoding=\"UTF-8\"?><ns:MT_OutputXML xmlns:ns=\"http://sap.com/xi\"> <Name>" + inputFileName + "</Name><Validation>Fail</Validation> </ns:MT_OutputXML>";
            try {
                outputstream.write(FailOutputXML.getBytes());
            } catch (IOException ex) {
                exception.printStackTrace();
                ex.printStackTrace();

JAXP API provides no way to enable XML Schema validation mode

I am evaluating XDK 9.2.0.5.0 for Java and have encountered another
problem with XML Schema support when using the JAXP API.
Using the classes in oracle.xml.jaxp.*, it appears to be impossible to
enable XML Schema validation mode. I can set the schema object, but
the parser does not use it for validation.
If I use DOMParser directly, I can call the setValidationMode(int)
method to turn on schema validation mode. There is no equivalient
means to enable XML Schema validation when using the JAXP API.
Test case for JAXP API:
=== begin OracleJAXPSchemaTest.java ======
package dfranklin;
import java.io.*;
import javax.xml.parsers.*;
import javax.xml.transform.*;
import javax.xml.transform.dom.*;
import javax.xml.transform.stream.*;
import oracle.xml.parser.schema.XMLSchema;
import oracle.xml.parser.schema.XSDBuilder;
import org.w3c.dom.*;
import org.xml.sax.*;
public class OracleJAXPSchemaTest
private final static String xsd = ""
+"<xsd:schema xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" targetNamespace=\"urn:dfranklin:test\">"
+" <xsd:element name=\"amount\" type=\"xsd:integer\"/>"
+"</xsd:schema>";
private final static String xml =
"<amount xmlns=\"urn:dfranklin:test\">1</amount>";
public static void main(String[] args)
throws Exception
System.setProperty("javax.xml.parsers.DocumentBuilderFactory",
          "oracle.xml.jaxp.JXDocumentBuilderFactory");
new OracleJAXPSchemaTest().run();
public void run()
throws Exception
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
dbf.setValidating(true);
dbf.setNamespaceAware(true);
XMLSchema xmlSchema = buildXMLSchema(new StringReader(xsd));
dbf.setAttribute("oracle.xml.parser.XMLParser.SchemaObject",
          xmlSchema);
DocumentBuilder docbldr = dbf.newDocumentBuilder();
Document doc = docbldr.parse(new InputSource(new StringReader(xml)));
print(doc);
private XMLSchema buildXMLSchema(Reader xsdin)
throws Exception
XSDBuilder xsdBuilder = new XSDBuilder();
XMLSchema xmlSchema = (XMLSchema)xsdBuilder.build(xsdin, null);
return xmlSchema;
private void print(Document doc)
throws
javax.xml.transform.TransformerConfigurationException,
javax.xml.transform.TransformerException
Transformer xformer = TransformerFactory.newInstance().newTransformer();
xformer.transform(new DOMSource(doc), new StreamResult(System.out));
System.out.println();
=== end OracleJAXPSchemaTest.java ======
Running that program:
java dfranklin.OracleJAXPSchemaTest
produces this output
Exception in thread "main" oracle.xml.parser.v2.XMLParseException: Element 'amount' used but not declared.
at oracle.xml.parser.v2.XMLError.flushErrors(XMLError.java:148)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:269)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:149)
at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:96)
at dfranklin.OracleJAXPSchemaTest.run(OracleJAXPSchemaTest.java:40)
at dfranklin.OracleJAXPSchemaTest.main(OracleJAXPSchemaTest.java:27)
This shows that the parser is not using the XML Schema to validate the
document. I think it's expecting to find a DTD.
Here is the equivalent program using DOMParser directly, and setting
validation mode to SCHEMA_VALIDATION.
=== begin OracleParserTest.java ====
package dfranklin;
import java.io.*;
import javax.xml.transform.*;
import javax.xml.transform.dom.*;
import javax.xml.transform.stream.*;
import oracle.xml.parser.schema.XMLSchema;
import oracle.xml.parser.schema.XSDBuilder;
import oracle.xml.parser.v2.DOMParser;
import oracle.xml.parser.v2.XMLParser;
import org.w3c.dom.*;
import org.xml.sax.*;
public class OracleParserTest
private final static String xsd = ""
+"<xsd:schema xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" targetNamespace=\"urn:dfranklin:test\">"
+" <xsd:element name=\"amount\" type=\"xsd:integer\"/>"
+"</xsd:schema>";
private final static String xml =
"<amount xmlns=\"urn:dfranklin:test\">1</amount>";
public static void main(String[] args)
throws Exception
new OracleParserTest().run();
public void run()
throws Exception
DOMParser dp = new DOMParser();
XMLSchema xmlSchema = buildXMLSchema(new StringReader(xsd));
dp.setXMLSchema(xmlSchema);
dp.setValidationMode(XMLParser.SCHEMA_VALIDATION);
dp.parse(new InputSource(new StringReader(xml)));
Document doc = dp.getDocument();
print(doc);
private XMLSchema buildXMLSchema(Reader xsdin)
throws Exception
XSDBuilder xsdBuilder = new XSDBuilder();
XMLSchema xmlSchema = (XMLSchema)xsdBuilder.build(xsdin, null);
return xmlSchema;
private void print(Document doc)
throws
javax.xml.transform.TransformerConfigurationException,
javax.xml.transform.TransformerException
Transformer xformer = TransformerFactory.newInstance().newTransformer();
xformer.transform(new DOMSource(doc), new StreamResult(System.out));
System.out.println();
=== end OracleParserTest.java ====
Running that program
java dfranklin.OracleParserTest
produces this output
<?xml version = '1.0'?>
<amount xmlns="urn:dfranklin:test">1</amount>
In this case, the parser has validated the document.
I also tried this with version 10.1.0.0.0 beta, and got the same
error.
Darin Franklin

Thanks for posting that. I tried that code and still got my problem. The big difference is that I'm reading a group of XML files each of which uses a large number of schema files. There are over 50 schema files organized so they can be included as needed. Each of the XML files has a noNamespaceSchemaLocation attribute specifying one of the ten top schma files, that includes many others.
However, I did solve the problem. I added one line --
       saxb.setFeature( "http://apache.org/xml/features/validation/schema",
                true);
        // next line is new
        saxb.setProperty( JAXPConstants.JAXP_SCHEMA_LANGUAGE,
                JAXPConstants.W3C_XML_SCHEMA );after the setFeature to turn on schema validation.
(It needs an import org.apache.xerces.jaxp.JAXPConstants; statement.)
Note:With the feature set to true and the setProperty commented out, the EntityResolver is called at construction tiem, and for each schema file, but each element is flagged as needing to be declared.
With the feature commented out, and the setProperty in place, the EntityResolver is not called, and there is no validation performed. (I added invalid content to one of the files and there were no errors listed.)
With both the setFeature and the setProperty in place, however, I get the calls from the EntityResolver indicating that it is processing the schema files, and for the good files, I get no errror, but for the bad file, I get an error indicating a bad validation.
Now I can make the EntityResolver quiet and get what I wanted. Maybe there are other ways to do this, but I've got one that works. :-)
Thanks to all who have helped.
Dave Patterson

Adapter Engine XML Schema Validation Error Surpression

We recently developed a number of web services that are called by 3rd parties outside our network. The web service request once made is picked up by a Web Dispatcher which then forwards the request to the de-central adapter. Both of these components reside within within a DMZ.
We have, as an additional security measure made use of the new Adapter Engine XML Schema validation available with PI 7.1, to ensure that the payload of incomming messages is checked to ensure that it is a known structure.
Now here is my problem, we recently had these services penetration tested by a 3rd party to ensure that they were secure and whilst the report was very good showing no major weaknesses they did pickup on a couple of items including that the fact that if the XSD to be used during payload message validation cannot be found an 'ADAPTER.JAVA_EXCEPTION' is returned to the web service consumer that highlights the path details of where the XSD should be (but could not be found).
This was viewed as useful to an attacker for a number of reasons:
1. Feedback in SQL injection attempts via verbatim DB error messages greatly improves attacker efficiency
2. Path information is useful to the attacker for OS fingerprinting, directory traversal attempts
3. Other miscellaneous stack trace information is useful to an attacker to understand how the application works
Is there anyway this can be surpressed so that the adapter does not show this information in the returned error message - see example message below ?
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Schema MaintenanceOrderByIDQuery_sync.xsd not found in E:\usr\sap\DPI\DVEBMGS40\j2ee\cluster\server0\validation\schema\f7cd3b50a87411e08830ed9d0af006a5\urnstw.contractor.wfm.workorderretrieval\MaintenanceOrderByIDQueryRequest_Out\httpsap.comxiSAPGlobal20~Global\MaintenanceOrderByIDQuery_sync.xsd (validation\schema)
     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)
     at sun.reflect.GeneratedMethodAccessor497.invoke(Unknown Source)
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Schema Schema1.xsd not found in E:\usr\sap\DPI\DVEBMGS40\j2ee\cluster\server0\validation\schema\f7cd3b50a87411e08830ed9d0af006a5\urnstw.contractor.wfm.workorderretrieval\MaintenanceOrderByIDQueryRequest_Out\httpsap.comxiEA-APPLSEGlobal\Schema1.xsd (validation\schema)
     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)

Hi,
We are having the same problem, so you are not alone.
I had an extensive call with Azure premium support and we where able to determine that:
- Nothing is missing or in the wrong place in my exported .xml file.
- Any changes to the VNET's using the web gui interface of https://manage.windowsazure.com is not possible when you have dns servers and use an gateway
- You can download the .xml configuration file of the network and make manual changes to it, then import it again , to add/remove dns servers and or subnet's.
I am currently waiting for an solution, i have let them lower the urgency from A to B (because i can make changes trough xml) and responded to the next support contact (saying he will continue with the issue) that the problems seems to be with azure and
he should speak with the previous person helping me. I have not heard from Azure support since.
SR Number:115021812414226
Open on:02/18/2015 09:28
> There are networks with and without gateways created and the issue is happening on all the networks.
> We are unable to add or remove the DNS servers. (by web gui)
> Also not able to add or remove any subnets. (by web gui)
> Every time the error message is same but the DNS server name is different. (from another subnet then the one we are changing)
> Created CRI- 3405931, but they said it will need WATS team.
> Confirmed with WATS engineer as well and moving case to WATS.
> Cx agreed to lower the severity of the case as they are able to make changes through the network configuration file.
> But they still want to get this resolved soon.
> Agreed and dropped off, reducing severity to B 24/7.
I hope microsoft is going to resolve this soon, as i do not want to edit my xml for little things like adding a subnet all the time. I have requested an status update in the issue.
Should anyone have more information on this, please share it here.

Schema validation errors in Portal 10.3

I downloaded, installed and configured a domain with an AdminServer and a ManagedServer for WebLogic Portal 10.3. When I start the AdminServer from NodeManager the following errors are reported:
<Sep 24, 2008 12:50:41 PM CDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/WL10gR3/user_projects/domains/web/config/config.xml - Invalid xsi:type qname: 'wsrp:wsrp-identity-asserterType' in element realm@http://www.bea.com/ns/weblogic/920/domain>
<Sep 24, 2008 12:50:41 PM CDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/WL10gR3/user_projects/domains/web/config/config.xml - /opt/Oracle/WL10gR3/user_projects/domains/web/<unknown>:13:9: error: failed to load java type corresponding to t=wsrp-identity-asserterType@http://www.bea.com/ns/wlp/90/security/wsrp>
When I start the AdminServer using startWebLogic.sh there are no errors. Please advise.

I have been at this for less than a month, so I may need a little more help. So are you saying that the product as installed has been reorganized and that all of the installed pieces may not reflect all of the changes?
I have continued cutting down my scripts and NodeManager does not seem to be a factor. Starting from WLST does not work.
This works:
/opt/Oracle/WL10gR3/user_projects/domains/web/bin/startWebLogic.sh.
JAVA Memory arguments: -Xms256m -Xmx768m
WLS Start Mode=Production
CLASSPATH=:/opt/Oracle/WL10gR3/patch_wlw1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/Oracle/WL10gR3/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/Oracle/WL10gR3/patch_wlp1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/Oracle/WL10gR3/patch_cie670/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/Oracle/WL10gR3/jrockit_160_05/lib/tools.jar:/opt/Oracle/WL10gR3/wlserver_10.3/server/lib/weblogic_sp.jar:/opt/Oracle/WL10gR3/wlserver_10.3/server/lib/weblogic.jar:/opt/Oracle/WL10gR3/modules/features/weblogic.server.modules_10.3.0.0.jar:/opt/Oracle/WL10gR3/wlserver_10.3/server/lib/webservices.jar:/opt/Oracle/WL10gR3/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/opt/Oracle/WL10gR3/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar::/opt/Oracle/WL10gR3/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar:/opt/Oracle/WL10gR3/wlserver_10.3/server/lib/xqrl.jar:/opt/Oracle/WL10gR3/wlserver_10.3/server/lib/xquery.jar:/opt/Oracle/WL10gR3/wlserver_10.3/server/lib/binxml.jar:
PATH=/opt/Oracle/WL10gR3/wlserver_10.3/server/bin:/opt/Oracle/WL10gR3/modules/org.apache.ant_1.6.5/bin:/opt/Oracle/WL10gR3/jrockit_160_05/jre/bin:/opt/Oracle/WL10gR3/jrockit_160_05/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://hostname:port/console *
starting weblogic with Java version:
x86_64 is not a supported Linux hardware platform for Autonomy.
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
BEA JRockit(R) (build R27.6.0-50_o-100423-1.6.0_05-20080626-2104-linux-ia32, compiled mode)
Starting WLS with line:
/opt/Oracle/WL10gR3/jrockit_160_05/bin/java -jrockit -Xms256m -Xmx768m -da -Dplatform.home=/opt/Oracle/WL10gR3/wlserver_10.3 -Dwls.home=/opt/Oracle/WL10gR3/wlserver_10.3/server -Dweblogic.home=/opt/Oracle/WL10gR3/wlserver_10.3/server -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=/opt/Oracle/WL10gR3/patch_wlw1030/profiles/default/sysext_manifest_classpath:/opt/Oracle/WL10gR3/patch_wls1030/profiles/default/sysext_manifest_classpath:/opt/Oracle/WL10gR3/patch_wlp1030/profiles/default/sysext_manifest_classpath:/opt/Oracle/WL10gR3/patch_cie670/profiles/default/sysext_manifest_classpath:/opt/Oracle/WL10gR3/wlportal_10.3/p13n/lib/system:/opt/Oracle/WL10gR3/wlportal_10.3/light-portal/lib/system:/opt/Oracle/WL10gR3/wlportal_10.3/portal/lib/system:/opt/Oracle/WL10gR3/wlportal_10.3/info-mgmt/lib/system:/opt/Oracle/WL10gR3/wlportal_10.3/analytics/lib/system:/opt/Oracle/WL10gR3/wlportal_10.3/apps/lib/system:/opt/Oracle/WL10gR3/wlportal_10.3/info-mgmt/deprecated/lib/system:/opt/Oracle/WL10gR3/wlportal_10.3/content-mgmt/lib/system -Dweblogic.alternateTypesDirectory=/opt/Oracle/WL10gR3/wlportal_10.3/portal/lib/security -Dweblogic.Name=AdminServer -Djava.security.policy=/opt/Oracle/WL10gR3/wlserver_10.3/server/lib/weblogic.policy weblogic.Server
<Sep 25, 2008 11:34:35 AM CDT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
/opt/Oracle/WL10gR3/wlportal_10.3/analytics/lib/system/analytics_sys.jar:/opt/Oracle/WL10gR3/wlportal_10.3/apps/lib/system/groupspace_system.jar:/opt/Oracle/WL10gR3/wlportal_10.3/content-mgmt/lib/system/content_system.jar:/opt/Oracle/WL10gR3/wlportal_10.3/info-mgmt/deprecated/lib/system/commerce_system.jar:/opt/Oracle/WL10gR3/wlportal_10.3/info-mgmt/lib/system/wlp-schemas.jar:/opt/Oracle/WL10gR3/wlportal_10.3/info-mgmt/lib/system/wlp_content_system.jar:/opt/Oracle/WL10gR3/wlportal_10.3/info-mgmt/lib/system/wps_system.jar:/opt/Oracle/WL10gR3/wlportal_10.3/light-portal/lib/system/netuix_common.jar:/opt/Oracle/WL10gR3/wlportal_10.3/light-portal/lib/system/netuix_schemas.jar:/opt/Oracle/WL10gR3/wlportal_10.3/light-portal/lib/system/netuix_system.jar:/opt/Oracle/WL10gR3/wlportal_10.3/light-portal/lib/system/wsrp-client.jar:/opt/Oracle/WL10gR3/wlportal_10.3/light-portal/lib/system/wsrp-common.jar:/opt/Oracle/WL10gR3/wlportal_10.3/p13n/lib/system/p13n-schemas.jar:/opt/Oracle/WL10gR3/wlportal_10.3/p13n/lib/system/p13n_common.jar:/opt/Oracle/WL10gR3/wlportal_10.3/p13n/lib/system/p13n_system.jar:/opt/Oracle/WL10gR3/wlportal_10.3/p13n/lib/system/wlp_services.jar:/opt/Oracle/WL10gR3/wlportal_10.3/portal/lib/system/netuix_system-full.jar>
<Sep 25, 2008 11:34:36 AM CDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.0-50_o-100423-1.6.0_05-20080626-2104-linux-ia32 from BEA Systems, Inc.>
<Sep 25, 2008 11:34:36 AM CDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for CR376251 Wed Aug 06 09:19:34 PDT 2008
WebLogic Server Temporary Patch for CR371247 Sat Aug 09 20:10:38 PDT 2008
WebLogic Server Temporary Patch for CR377673 Tue Aug 12 20:39:50 EDT 2008
WebLogic Server Temporary Patch for CR377673 Tue Aug 12 20:39:50 EDT 2008
WebLogic Server Temporary Patch for CR376759 Thu Aug 14 14:53:02 PDT 2008
WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
<Sep 25, 2008 11:34:38 AM CDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
This does not work:
. /opt/Oracle/WL10gR3/user_projects/domains/web/bin/setDomainEnv.sh
java weblogic.WLSTInitializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> startServer()
Starting weblogic server ...
WLST-WLS-1222359153099: <Sep 25, 2008 11:12:34 AM CDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.0-50_o-100423-1.6.0_05-20080626-2104-linux-ia32 from BEA Systems, Inc.>
WLST-WLS-1222359153099: <Sep 25, 2008 11:12:34 AM CDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for CR376251 Wed Aug 06 09:19:34 PDT 2008
WLST-WLS-1222359153099: WebLogic Server Temporary Patch for CR371247 Sat Aug 09 20:10:38 PDT 2008
WLST-WLS-1222359153099: WebLogic Server Temporary Patch for CR377673 Tue Aug 12 20:39:50 EDT 2008
WLST-WLS-1222359153099: WebLogic Server Temporary Patch for CR377673 Tue Aug 12 20:39:50 EDT 2008
WLST-WLS-1222359153099: WebLogic Server Temporary Patch for CR376759 Thu Aug 14 14:53:02 PDT 2008
WLST-WLS-1222359153099: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
WLST-WLS-1222359153099: <Sep 25, 2008 11:12:36 AM CDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/WL10gR3/user_projects/domains/web/config/config.xml - Invalid xsi:type qname: 'wsrp:wsrp-identity-asserterType' in element realm@http://www.bea.com/ns/weblogic/920/domain>
AdminServer.out:
<Sep 25, 2008 10:56:16 AM> <Info> <NodeManager> <Starting WebLogic server with command line: /opt/Oracle/WL10gR3/jrockit_160_05/jre/bin/java -Dweblogic.Name=AdminServer -Djava.security.policy=/opt/Oracle/WL10gR3/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path=/opt/Oracle/WL10gR3/jrockit_160_05/jre/lib/i386/jrockit:/opt/Oracle/WL10gR3/jrockit_160_05/jre/lib/i386:/opt/Oracle/WL10gR3/jrockit_160_05/jre/../lib/i386::/opt/Oracle/WL10gR3/wlserver_10.3/server/native/linux/i686:/opt/Oracle/WL10gR3/wlserver_10.3/server/native/linux/i686/oci920_8 -Djava.class.path=/opt/Oracle/WL10gR3/patch_wlw1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/Oracle/WL10gR3/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/Oracle/WL10gR3/patch_wlp1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/Oracle/WL10gR3/patch_cie670/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/Oracle/WL10gR3/jrockit_160_05/lib/tools.jar:/opt/Oracle/WL10gR3/wlserver_10.3/server/lib/weblogic_sp.jar:/opt/Oracle/WL10gR3/wlserver_10.3/server/lib/weblogic.jar:/opt/Oracle/WL10gR3/modules/features/weblogic.server.modules_10.3.0.0.jar:/opt/Oracle/WL10gR3/wlserver_10.3/server/lib/webservices.jar:/opt/Oracle/WL10gR3/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/opt/Oracle/WL10gR3/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar::/opt/Oracle/WL10gR3 -Dweblogic.system.BootIdentityFile=/opt/Oracle/WL10gR3/user_projects/domains/web/servers/AdminServer/security/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
<Sep 25, 2008 10:56:16 AM> <Info> <NodeManager> <Working directory is "/opt/Oracle/WL10gR3/user_projects/domains/web">
<Sep 25, 2008 10:56:16 AM> <Info> <NodeManager> <Server output log file is "/opt/Oracle/WL10gR3/user_projects/domains/web/servers/AdminServer/logs/AdminServer.out">
<Sep 25, 2008 10:56:17 AM CDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.0-50_o-100423-1.6.0_05-20080626-2104-linux-ia32 from BEA Systems, Inc.>
<Sep 25, 2008 10:56:17 AM CDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for CR376251 Wed Aug 06 09:19:34 PDT 2008
WebLogic Server Temporary Patch for CR371247 Sat Aug 09 20:10:38 PDT 2008
WebLogic Server Temporary Patch for CR377673 Tue Aug 12 20:39:50 EDT 2008
WebLogic Server Temporary Patch for CR377673 Tue Aug 12 20:39:50 EDT 2008
WebLogic Server Temporary Patch for CR376759 Thu Aug 14 14:53:02 PDT 2008
WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
<Sep 25, 2008 10:56:19 AM CDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/WL10gR3/user_projects/domains/web/config/config.xml - /opt/Oracle/WL10gR3/user_projects/domains/web/<unknown>:13:9: error: failed to load java type corresponding to t=wsrp-identity-asserterType@http://www.bea.com/ns/wlp/90/security/wsrp>

Schema validation error at startup

Configuration:
WL Portal 9.2
Linux Fedora Core 6
I just created a new portal domain and it just does not startup.
The reported exception is:
Schema validation errors while parsing /domains/portal/./config/config.xml - Invalid xsi:type qname: 'ext:wsrp-identity-asserterType' in element realm@http://www.bea.com/ns/weblogic/920/domain>
Schema validation errors while parsing /domains/portal/./config/config.xml - /domains/portal/<unknown>:13:9: error: failed to load java type corresponding to t=wsrp-identity-asserterType@http://www.bea.com/ns/wlp/90/security/wsrp
I can't find the schema 'http://www.bea.com/ns/wlp/90/security/wsrp.xsd' neither on the web nor the jars supplied with the product.
Any help would be appreciated.

Hi, I think you may be missing the binding-file.xml that should be in your mbean jar which should be in your WL_HOME/server/lib/mbeantypes/...
I am having similar problem and I get this error if I replace the 9.2 MBean jar (generated with MakeMBean) with 8.1 version. The 9.2 MakeMBean utility seems to bundle a bunch of additional jaxb binding files into the jar (xsb, binding-file.xml, *BeanImpl etc). Optionally you can run an 8.1 MBean through the 'weblogic.Upgrade -type securityprovider', this will convert your authentication mbean jar to 9.2 which also includes above mentioned files.
Once you have an MBean jar, generated with the 9.2 MakeMBean you will probably get a similar error in that the startup will fail with error below: If you know how to fix this please let me know as I have spent a day on this with no luck.
...config.xml - C:\...\mydomain\<unknown>:16:9: error: fail
ed to load java type corresponding to t=ucv-db-authenticatorType@http://www.bea.com/ns/weblogic/90/security/extension>
<Feb 15, 2007 9:26:29 AM NZDT> <Critical> WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141245]Schema Validation Error in :\...\server\mydomain\config\config.xml see log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblog
ic.configuration.schemaValidationEnabled=false>
PS: setting the -Dweblogic.configuration.schemaValidationEnabled=false option only causes the startup to fail as it cannot load the security provider (if this is your default provider I guess?)
Hope this helps.

XML Schema validation error in network configuration. Missing DnsRef

When ever we try to make changes to a Virtual network we receive
XML Schema validation
error in network configuration. Missing DnsRef
We can't make any changes to the Virtual network.
The DNS ref exists as well.
Considering exporting network config and re-importing however we have a lot of networks configured and want to be sure this is the correct way to proceed.
Any feedback much appreciated.
Thanks

Hi,
We are having the same problem, so you are not alone.
I had an extensive call with Azure premium support and we where able to determine that:
- Nothing is missing or in the wrong place in my exported .xml file.
- Any changes to the VNET's using the web gui interface of https://manage.windowsazure.com is not possible when you have dns servers and use an gateway
- You can download the .xml configuration file of the network and make manual changes to it, then import it again , to add/remove dns servers and or subnet's.
I am currently waiting for an solution, i have let them lower the urgency from A to B (because i can make changes trough xml) and responded to the next support contact (saying he will continue with the issue) that the problems seems to be with azure and
he should speak with the previous person helping me. I have not heard from Azure support since.
SR Number:115021812414226
Open on:02/18/2015 09:28
> There are networks with and without gateways created and the issue is happening on all the networks.
> We are unable to add or remove the DNS servers. (by web gui)
> Also not able to add or remove any subnets. (by web gui)
> Every time the error message is same but the DNS server name is different. (from another subnet then the one we are changing)
> Created CRI- 3405931, but they said it will need WATS team.
> Confirmed with WATS engineer as well and moving case to WATS.
> Cx agreed to lower the severity of the case as they are able to make changes through the network configuration file.
> But they still want to get this resolved soon.
> Agreed and dropped off, reducing severity to B 24/7.
I hope microsoft is going to resolve this soon, as i do not want to edit my xml for little things like adding a subnet all the time. I have requested an status update in the issue.
Should anyone have more information on this, please share it here.

XML binary storage format impairs schema validation?

I'm using Oracle 11g R1 on Windows Server 2003. I successfully registered schemas and created tables and indexes in the new binary storage format. However, when trying to load data, I'm running into problems. Schema validation behaves as if not the full feature set of XML Schema mysteriously isn't supported anymore.
There is probably more but at least wildcard elements (xs:any) and element references (xs:element ref="STH") are simply ignored in the schema definition and data is rejected even when it conforms to the schema.
Is there any solution for this or am I out of luck? I wanted to go back to CLOB storage as used in a previous installation but I'm running into problems when registering the schema. It complains about an empty SQL name although I don't have any defined. I'm pretty weirded out by all this.
I created the schema and table in a straightforward way:
begin
dbms_xmlschema.registeruri(
    schemaurl => 'http://www.xxxhello.com/archive_tsd.xsd',
    schemadocuri => '/public/user/archive_tsd.xsd',
    gentypes => FALSE,
    options => DBMS_XMLSCHEMA.REGISTER_BINARYXML
end;
CREATE TABLE archive OF xmltype XMLTYPE STORE AS binary xml XMLSCHEMA
"http://www.xxxhello.com/archive_tsd.xsd" ELEMENT "CompleteDocument";
create index idx_lastmodified_archive on archive t
(extractvalue(VALUE(t),'/CompleteDocument/DocContent/LastModified'));Because of xs:any or element references is ignored, I get errors like
LSX-00213: only 0 occurrences of particle "REFDELEM", minimum is 1.
Thanks for your help.

The schema is very large (>200kb). Where should I upload it or can I send it to you? I'm bit concerned about confidentiality of company data. However, the instance is not valid yet. I'm in the process of modifying the schema to match all instances, but it breaks on places that should be already okay. No, I didn't use SchemaValidate ever.
But I've made an example where at least xs:any doesn't work. Element references work, though.
Sample schema:
<?xml version = "1.0" encoding = "UTF-8"?>
<xs:schema
xmlns:tsd = "http://namespaces.softwareag.com/tamino/TaminoSchemaDefinition"
xmlns:xs = "http://www.w3.org/2001/XMLSchema">
<xs:annotation>
    <xs:appinfo>
      <tsd:schemaInfo name = "sbreak">
        <tsd:collection name = "sbreak"></tsd:collection>
        <tsd:doctype name = "CompleteDocument">
          <tsd:logical>
            <tsd:content>open</tsd:content>
            <tsd:systemGeneratedIdentity reuse = "false"></tsd:systemGeneratedIdentity>
          </tsd:logical>
        </tsd:doctype>
        <tsd:adminInfo>
          <tsd:server>4.4.1.1</tsd:server>
          <tsd:modified>2007-07-03T16:00:46.484+02:00</tsd:modified>
          <tsd:created>2007-07-03T15:29:04.968+02:00</tsd:created>
          <tsd:version>TSD4.4</tsd:version>
        </tsd:adminInfo>
      </tsd:schemaInfo>
    </xs:appinfo>
</xs:annotation>
<xs:element name = "CompleteDocument">
    <xs:complexType>
      <xs:choice minOccurs = "0" maxOccurs = "unbounded">
        <xs:element name = "ComplexNormal">
          <xs:complexType>
            <xs:choice minOccurs = "0" maxOccurs = "unbounded">
              <xs:element name = "NormalElem1" type = "xs:string"></xs:element>
              <xs:element name = "NormalElem2" type = "xs:string"></xs:element>
            </xs:choice>
          </xs:complexType>
        </xs:element>
        <xs:element name = "ComplexAny">
          <xs:complexType>
            <xs:choice minOccurs = "0" maxOccurs = "unbounded">
              <xs:any minOccurs = "0" maxOccurs = "unbounded"></xs:any>
            </xs:choice>
          </xs:complexType>
        </xs:element>
        <xs:element name = "ComplexRef">
          <xs:complexType>
            <xs:choice minOccurs = "0" maxOccurs = "unbounded">
              <xs:element ref = "RefdElem"></xs:element>
            </xs:choice>
          </xs:complexType>
        </xs:element>
        <xs:element name = "LastModified" type = "xs:string"></xs:element>
      </xs:choice>
    </xs:complexType>
</xs:element>
<xs:element name = "RefdElem">
    <xs:complexType>
      <xs:choice minOccurs = "0" maxOccurs = "unbounded">
        <xs:element name = "Elem1" type = "xs:string"></xs:element>
        <xs:element name = "Elem2" type = "xs:string"></xs:element>
      </xs:choice>
    </xs:complexType>
</xs:element>
</xs:schema>Sample instance:
<?xml version="1.0" encoding="UTF-8" ?>
<CompleteDocument>
     <ComplexNormal>
          <NormalElem1>Test1</NormalElem1>
          <NormalElem2>Test2</NormalElem2>
     </ComplexNormal>
     <ComplexAny>
          <AnyElem>Test3</AnyElem>
     </ComplexAny>
     <ComplexRef>
          <RefdElem>
               <Elem1>Test4</Elem1>
               <Elem2>Test5</Elem2>
          </RefdElem>
     </ComplexRef>
</CompleteDocument>Log of what I did. First I confirmed, that I could enter the instance using clob storage:
SQL> begin
2    dbms_xmlschema.registeruri(
3      schemaurl => 'http://www.xxxhello.com/sbreak_tsd.xsd',
4      schemadocuri => '/public/sbreak_tsd.xsd'
5    );
6 end;
7 /
PL/SQL-Prozedur erfolgreich abgeschlossen.
SQL> CREATE TABLE sbreak OF xmltype XMLTYPE STORE AS clob XMLSCHEMA
"http://www.xxxhello.com/sbreak_tsd.xsd" ELEMENT "CompleteDocument";
Tabelle wurde erstellt.
SQL> create index idx_lastmodified_sbreak on sbreak t (extractvalue(VALUE(t),
'/CompleteDocument/LastModified'));
Index wurde erstellt.
SQL> insert into sbreak values(xmltype(bfilename('DATA', 'sbreak/sbreakinstance.xml'),
NLS_CHARSET_ID('AL32UTF8')));
1 Zeile wurde erstellt.Then I deleted table and schema again:
SQL> drop index idx_lastmodified_sbreak;
Index wurde gelöscht.
SQL> drop table sbreak;
Tabelle wurde gelöscht.
SQL> begin
2    dbms_xmlschema.deleteschema(
3      schemaurl => 'http://www.xxxhello.com/sbreak_tsd.xsd'
4     ,delete_option => dbms_xmlschema.delete_cascade_force
5    );
6 end;
7 /
PL/SQL-Prozedur erfolgreich abgeschlossen.After that I created schema and table with binary XML storage and tried to insert the same instance again:
SQL> begin
2    dbms_xmlschema.registeruri(
3      schemaurl => 'http://www.xxxhello.com/sbreak_tsd.xsd',
4      schemadocuri => '/public/sbreak_tsd.xsd',
5      gentypes => FALSE,
6      options => DBMS_XMLSCHEMA.REGISTER_BINARYXML
7    );
8 end;
9 /
PL/SQL-Prozedur erfolgreich abgeschlossen.
SQL> CREATE TABLE sbreak OF xmltype XMLTYPE STORE AS binary xml XMLSCHEMA
"http://www.xxxhello.com/sbreak_tsd.xsd" ELEMENT "CompleteDocument";
Tabelle wurde erstellt.
SQL> create index idx_lastmodified_sbreak on sbreak t (extractvalue(VALUE(t),
'/CompleteDocument/LastModified'));
Index wurde erstellt.
SQL> insert into sbreak values(xmltype(bfilename('DATA', 'sbreak/sbreakinstance.xml'),
NLS_CHARSET_ID('AL32UTF8')));
insert into sbreak values(xmltype(bfilename('DATA', 'sbreak/sbreakinstance.xml'),
NLS_CHARSET_ID('AL32UTF8')))
FEHLER in Zeile 1:
ORA-31011: XML-Parsing nicht erfolgreich
ORA-19202: Fehler bei XML-Verarbeitung
LSX-00021: undefined element "AnyElem"
aufgetretenSorry about the non-english text, but I think it can be guessed easily what's going on. Next I'll try a modifed schema without the tsd namespace added by the schema editor I use (the original large schema has been migrated from the Tamino XML database).

Switching ON validate xml(Schema Validation) in BPEL Console for AIAtesting

While we were testing Oracle O2B pip, we have recently switched on schema validation by turning it on to 'Strict' so that we can Validate
XML in BPEL Console. Earlier when we were testing we had turned the schema validation as 'None' on BPEL console, and hence everything was working fine and
no errors we popping out while creating sales order in Siebel CRM. But the moment we put validate xml to ' Strict' it starts throwing validation errors.
So can you please help us to know whether it is right to test the Oracle O2B pip by putting validate xml to 'Strict'? If it is fair to test it by switching
ON Validate XML(putting validate xml to 'Strict') then we are getting below error.
We are creating a new sales order in Siebel CRM and when we check in BPEL console it was faulted at UpdateSalesOrderSiebelCommsProvABCSImpl (v. 1.0) .When we checked the BPEL flow it is throwing error at InvokeUpdateUpsert.
Error is According to the xml schemas, the xml document is invalid. The reason is: Error::cvc-complex-type.2.4.a: Invalid content was found starting with element 'xsdLocal1:Process_spcInstance_spcId'. One of '{"http://siebel.com/asi":Process_spcInstance_spcId}' is expected.
Steps for Switching on Validation ?
1)     Login to BPEL Console
2)     Go To Configuration section
3)     Schema Validation changes
a.     ON: populate validateXML with value strict
b.     OFF: populate validateXML with value none
Really appreciate if you can help..

hi
Indeed, the "Validate XML" menu option only shows "Validate XML: 0 errors, 0 warnings.".
But, if you look at the "Design" tab for your schema, the "invoices" element node contains an "xsd:invoice" sequence shown in red. If you change "xsd:invoice" to "invoice" this becomes white and the node can be expanded.
One other thing, registering an XML Schema in JDeveloper like the one you posted, isn't possible without an "oracle.xml.parser.schema.XSDException" (without further details).
regards
Jan Vervecken

How we can skip project level schema validation in BPEL

How we can skip project level schema validation in BPEL................... Because i have a requirement to send email with attachment. to send attachment i have to skip schema validation from EM console. so it will skip schema validation for all deployed application.it creates problem for other project so i want to do that thing at project level ....

Hi
It can be done by going opening the composite.xml in jdeveloper and than opening the properties window of the composite.There you will see a property Validate schema.Set that to no to overwrite the property set at the sever level.
The following property gets added in the composite.xml
<property name="validateSchema" type="xs:boolean" many="false">false</property>
Redeploy the composite and check.
Hope this helps!!!

Is schema validation on JDK 1.3.1 possible ?

Hi
I'm trying to get an XML parser to work on 1.3.1 with Schema validation.
API xerces.jar doesn't seem to handle schema validation in that version.
I tried my project with xercesImpl.jar on 1.4.2_09 => schema validation worked well.
I tried xerces.jar on 1.3.1 => doesn't run
Is there a .jar that can handle schema validation in 1.3.1 ?
Thanks
Montelieri

Hey.
In looking at their site, xerces 1.4.4 is the latest release, and is the one that provides support for XML Schema Version 1.0. This version likely requires JDK 1.4.x. You should double check the readme file in the dl.
http://xml.apache.org/xerces-j/index.html
Not a definate answer, but hope it helps anyway.
Cheers.

Catalog object schema validation failed(AGFIXBO2:EIRWWH9E)

Hi,
After copying my catalog from OBIEE 11.1.1.6.*0* (Build 120104.0800 64-bit) to 11.1.1.6.*7* (Build 121219.1257 64-bit).
Many of my report (particularly those with graphs) was not valid.
I have this message :
Catalog object schema validation failed: /shared/...
Error Details
Error Codes: AGFIXBO2:EIRWWH9E
Location: saw.httpserver.processrequest, saw.rpc.server.responder, saw.rpc.server, saw.rpc.server.handleConnection, saw.rpc.server.dispatch, saw.threadpool.socketrpcserver, saw.threads
The current xml is invalid with the following errors: Bad xml instance! <?xml version="1.0"?> <saw:report xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" .... Message:Value 'actual' is not in enumeration .
Please someone has any ideas to solve this issues.

Hello,
Check is post : Catalog object schema validation failed: 11.1.1.6.7 Patchset
Also check this note : OBIEE 11g: Error: "Catalog object schema validation failed...Error Codes: AGFIXBO2:EIRWWH9E" After Upgrade [ID 1247125.1]
Hope this helps. Pls mark if it does.
Thanks,
SVS

Schema validation of Incoming Messages

Does anyone know how to do Schema validation on incoming messages into XI 3.0? Its not clear to me.

Hi Dan,
You can find the documentation availability details at the following links:
http://help.sap.com/saphelp_nw04/helpdata/en/36/ef353e39011a38e10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/b6/8097f5a5edea4f8dfc87ac87082b22/content.htm
Regards,
Sridhar

Help On schema validation

Similar Messages

Maybe you are looking for