DTD files as external Definition

Hi ,
Read lot of threads on this which are having same problem ,some of them got solved none of them posted how did they succeded on those.
i am getting error like Name "ds:Signature" is incorrect, when i tried to inport the .dtd file as external definition,so I did try converting dtd file to XSD ,it is creating the 3 xsd files and none of them are valid each one of them are error.But however the DTD file is valid .
Using Invoicedetail DTD file for my scenario.
you can download the file from http://cxml.org
Please let me knw on this.
Thanks,
Madhu

Hi,
Here are the errors for the 3 xsd's
1.     Value 'ds:Signature' is not allowed for attribute 'ref'.
          Hint: A valid value would be 'xml:lang'.
          Error location: xs:schema / xs:element / xs:complexType / xs:sequence / xs:element / @ref
2.     Value 'ds:Signature' is not allowed for attribute 'ref'.
          Hint: A valid value would be 'xml:lang'.
          Error location: xs:schema / xs:element / xs:complexType / xs:sequence / xs:element / @ref
3.                   Value 'xades:Identifier' is not allowed for attribute 'ref'.
          Hint: A valid value would be 'xml:lang'.
          Error location: xs:schema / xs:element / xs:complexType / xs:sequence / xs:element / @ref
these errors are coming in xml spy when i tried to validate .
Thanks,
Madhu
Edited by: madhu204 on Jul 23, 2009 4:54 PM
Edited by: madhu204 on Jul 23, 2009 4:55 PM

Similar Messages

"Messages" problem after importing .xsd file as external definition

Hello,
I received an .xsd file from a customer and need to import it as an "External Definition" in order to create the "Message Interface". The structure of the xsd looks like this:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
<xsd:element name="ORDER">
</xsd:element>
<xsd:element name="ADDRESS">
</xsd:element>
<xsd:element name="ARTICLE_ID">
</xsd:element>
</xsd:schema>
After importing and looking at the tab "Messages" I get numerous entries, for each <xsd:element> I get one message! But I basically only need one "Message" that holds my complete xsd-file.
I tried inserting <xsd:element name="COMPLETEORDER"> right after the <xsd:schema>-Tag but that didn't work either. Somehow I need to sum up all the <xsd:elements>.
Does anyone have an idea? Thank you very much!
Peter

Hello Prateek, Hello everyone,
I now know what the problem is. I downloaded XMLspy and checked on the structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
<xsd:element name="ORDER">
</xsd:element>
<xsd:element name="ADDRESS">
</xsd:element>
<xsd:element name="ARTICLE_ID">
</xsd:element>
<xsd:simpleType name="dtBOOLEAN">
</xsd:simpleType>
<xsd:simpleType name="dtCOUNTRIES">
</xsd:simpleType>
<xsd:element name="SUPPLIER_AID">
</xsd:element>
<xsd:simpleType name="typeSUPPLIER_AID">
</xsd:simpleType>
</xsd:schema>
Between the long list of <xsd:element> tags there are some simpleTypes on the same
level. Now if I insert
<xsd:element name="COMPLETEORDER">
<xsd:complexType>
<xsd:sequence>
on top, the <xsd:sequence> would be on the same level as the simpleTypes - which is not valid!
But can I just move all the simpleTypes, e.g. into an <xsd:element>??
That would be changing the customer's structure which I think is not a good thing!?
Thank you again for your help! I really appreciate it!
Best regards,
Peter

IDoc to File scenario (External Definition)

Hi
I have a scenario which is a Idoc to file scenario. Here I want to continue with mapping only if the field MATNR exists on the source side (Idoc) otherwise I should get a message on the target side that the "Mapping failed because MATNR field does not exist " and the mapping should fail.
There are two independant MATNR fields and mapping should fail if I either of them does not exist.Please keep in mind that there indepandant of each other.
Please help
Thanks in advance

You have to write an UDF with exception. In exception you can write your message (the reasone of failure).
something like this..
//Mapping trace will add the warning to show in MONI (if trace level is set to 1 atleast in Tcode SXMB_ADM).
MappingTrace trace = container.getTrace();
for (int i = 0; i < MATNR.length; i++)
          if(MATNR<i>.equals(""))
               trace.addWarning("MATNR is missing.");
               throw new RuntimeException("MATNR is missing.");
abvoe code is just an example, you have to modify and put the logic as per your need.
Regards,
Sarvesh

External definitions import into Message mapping

Hi,
I have a DTD message in external definitions to be imported into the message mapping. But I am not able to choose the object in the mapping editor. It does not allow even if the message is a valid WSDL. The only time it allows to import into the message editor is when its an XSD.I am not sure why the external definitions in DTD or WSDL formats are not able to be imported or am I missing something??
-Ken

Hi,
A conversion of the downloaded cXML DTD into XSD by using XMLSPY yields 3 XSD files. Using the initial XSD(which has the major fields) yields the same error(i.e cannot create messages or valid WSDL) in external definitions.
I also tried using one of the standard xml's from the cXML site and the funny part was XMLSPY validated them without errors and while importing them directly into the mapping editor, XI throws an error "XML NOT WELL FORMED". Its so weird.
Also is there a possibility to write a script to manipulate the payload message after passing through the adapters? For eg : Creating a script which will delete a valid tag in payload before it reaches the 3rd party. ...By adding the DOCTYPE in the prolog, the message would look like this :
"<?xml...utf-8>
<!DOCTYPE......'Cxml.org'>
<?xml.....utf-8>
<start tag></start tag>
Therefore some kind of a script that would remove the second <?xml tag on line 3>..
This is just a round about thinking
Any ideas..

Error importing xsd as external definition

I'm importing a wsdl file as external definition and it references some xsd files that I'm trying to import too. Specifically there are 2 of them that I can't import in PI, as I get the next error:
Error when loading XML document (Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.UnknownHostException: www.w3.org)
XSD files might be found under next urls:
[XAdES.xsd|https://www3.aeat.es/ADUA/internet/es/aeat/dit/adu/xades/XAdES.xsd]
[xmldsig-core-schema.xsd|https://www3.aeat.es/ADUA/internet/es/aeat/dit/adu/xades/xmldsig-core-schema.xsd]
and are meant to be used to sign the document.
I have validated the files using the service in the next url:
[http://www.w3.org/2001/03/webdata/xsv|http://www.w3.org/2001/03/webdata/xsv] as well as in Altova XML Spy.
Has anyone any idea of what the problem might be? It is really interfering in my development.
Thanks in advance.

Ok I think I might have solved it. First there was a pair of problems with the file xmldsig-core-schema.xsd.
1. The name couldn't be used in PI as '-' characters are not allowed.
I changed the name to xmldsig_core_schema.xsd
2. The file had these lines at the start:
<!DOCTYPE schema PUBLIC "-//W3C//DTD XMLSchema 200102//EN" "http://www.w3.org/2001/XMLSchema.dtd" [
     <!ATTLIST schema
     xmlns:ds CDATA #FIXED "http://www.w3.org/2000/09/xmldsig#"
>
     <!ENTITY dsig 'http://www.w3.org/2000/09/xmldsig#'>
     <!ENTITY % p ''>
     <!ENTITY % s ''>
]>
PI doesn't like that if you import the file as XSD because I guess that is DTD not XSD format.
I removed those lines.
With these two changes this file could be imported.
However I still had problems with the XAdES.xsd file. PI couldn't recognize the import of xmldsig-core-schema.xsd file:
<xsd:import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="http://www.w3.org/TR/2002/
REC-xmldsig-core-20020212/xmldsig-core-schema.xsd"/>
It didn't like the URL, so I changed it to make reference to my local file.
After this, it all worked. The question is, will it also work in runtime when I'll make use of these external definitions created? Or will my changes have an impact on the results? I guess it will work fine but perhaps I'm wrong.
Besides, when activated I got the next warning:
Name of '/schema/complexType("TimeStampType")/sequence/choice/element("XMLTimeStamp")' starts with 'xml'
There's an element name that starts by XML. Is this forbidden? Will I have problems if I activate and use it just as it is?
Thanks for the answers.

DTD file?

Hello,
I got one DTD file from Client and i exported that file in external definition.
when i check the message tab in external definition there is no message available.
I tired to import the external definition, its giving error as Shipment has no message.
Thanks and Regards,
Chinna

choose DTD as External format
Selection Options in Messages List Box:message from DOCTYPE.
A dtd can be referenced by other dtd.It is only possible to reference external definitions with the same namespace.see The External References tab page which lists the references found in the document .

External definition

Hi All,
I have imported xsd files as external definitions. They are showing messaages list without any space.While using them in message mapping they are not showing the fields. Even in the case of direct import into message mapping also the same result.I am not getting the problem. Any suggestions to solve this..
Thanks in advance,
Kartikeya

hi,
i think this helps..
some of the tags are not supported by message mapping...like choice and complex..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2089f29b-b10a-2a10-5297-e258df0c1bfc
Thanks,
vijaya.

Messages not adviced in extern definition after import wsdl-file from WAS

Hi friends,
after importing the three wsld-files in repository (extern definitions) the messages are not adviced. The referendes to the files are fine, because the name is shown at the tab externe...
But i´m not shure wheather i tool the right link ant Web Service Navigator. It is right to download the default SAP WSDL Files or the default one? Because in the SAP WSDL-files there will be an exception during import in XI repository (tag sap:useFeatur). What is the problem that the messages are not shown on the tab messages in externe definitions?
Thanks in advance,
Frank

I've the same problem. Here is my WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:intf="http://blablabla.de:8080/jboss-net/services/MyServices" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns1="blablabla.de" xmlns:tns2="http://net.jboss.org/jmx" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <wsdl:types>
          <schema targetNamespace="blablabla.de" xmlns="http://www.w3.org/2001/XMLSchema">
               <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
               <complexType name="MSOBean">
                    <sequence>
                         <element name="installationName" nillable="true" type="xsd:string"/>
                         <element name="requestId" nillable="true" type="xsd:string"/>
                         <element name="returnCode" type="xsd:int"/>
                         <element name="returnMessage" nillable="true" type="xsd:string"/>
                    </sequence>
               </complexType>
               <complexType name="MSIBean">
                    <sequence>
                         <element name="password" nillable="true" type="xsd:string"/>
                         <element name="project" nillable="true" type="xsd:string"/>
                         <element name="requestId" nillable="true" type="xsd:string"/>
                         <element name="userId" nillable="true" type="xsd:string"/>
                    </sequence>
               </complexType>
          </schema>
     </wsdl:types>
     <wsdl:message name="actualizeRequest">
          <wsdl:part name="inData" type="tns1:MSIBean"/>
     </wsdl:message>
     <wsdl:message name="actualizeResponse">
          <wsdl:part name="actualizeReturn" type="tns1:MSOBean"/>
     </wsdl:message>
     <wsdl:portType name="MSService">
          <wsdl:operation name="actualize" parameterOrder="inData">
               <wsdl:input message="impl:actualizeRequest" name="actualizeRequest"/>
               <wsdl:output message="impl:actualizeResponse" name="actualizeResponse"/>
          </wsdl:operation>
     </wsdl:portType>
     <wsdl:binding name="MyServicesSoapBinding" type="impl:MSService">
          <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="actualize">
               <wsdlsoap:operation soapAction=""/>
               <wsdl:input name="actualizeRequest">
                    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de" use="encoded"/>
               </wsdl:input>
               <wsdl:output name="actualizeResponse">
                    <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://blablabla.de:8080/jboss-net/services/MyServices" use="encoded"/>
               </wsdl:output>
          </wsdl:operation>
     </wsdl:binding>
     <wsdl:service name="MSServiceService">
          <wsdl:port binding="impl:MyServicesSoapBinding" name="MyServices">
               <wsdlsoap:address location="http://blablabla.de:8080/jboss-net/services/MyServices"/>
          </wsdl:port>
     </wsdl:service>
</wsdl:definitions>
No Idea.

Can External Definition be used or Receiver File content conversion (CSV)?

Hi Experts,
I'm a newbie to SAP PI and I started working on file to File(FCC) scenario in which I am provided with the receiver structure as an External definition. The structure is like
Name
Place
Designation
Salary
hike
Can I use the same structure (External Definition) for the receiver file content conversion or do I need to create another specific structure?
Can I convert the target CSV file to UTF-8 encoding?
Please help.
Regards,
Taro

Hi,
Can the above specified structure be used for receiver FCC? Does this work? Can this be converted to UTF-8?
If it can be used, how do we specify the parameters for FCC then as there's no root element?
Regards,
Taro

Issue while importing the WSDL file in the External Definitions - PI 7.0

Dear all Experts
After importing the WSDL file in the external External Definitions we are not able to view the " name and namespace " in the messages tab.
Request you to advise on the issue.
We are using the PI 7.0
Regards
Machindra Patade

Dear All
Got the answer"
The problem is in the namespace description LENGTH,
Note the following restrictions for XI or PI installations:
· Maximum length of repository namespaces and XML namespaces: 60 Characters. Due to this restriction, the import of XSD files and WSDL files prepares difficulties as an external definition; you can solve these difficulties using Note 901988.
· Maximum length of object names in the Integration Repository and Integration Directory: 120 characters
As of SAP NetWeaver Process Integration 7.10 Support Package 7, the enhancement of the maximum length of namespaces to 255 is supported in the configuration and runtime.
Please check the below SAP 2 notes in regards to above mail.
SAP Note 901988 - Integration Builder: Namespace of external definitions
SAP Note 870809 - Integration Builder: Length of namespaces and object names

External definition, dtd references

Hi,
My openTRANS_ORDER_1_0.dtd is refering to "openbase_1_0.dtd
When I create the external definition both dtds is imported
openTRANS_ORDER_1_0_dtd
openbase_1_0_dtd
openTRANS_ORDER_1_0.dtd has a External reference :
Source: openbase_1_0.dtd
Name: openbase_1_0_dtd
and openbase_1_0_dtd has also filled out the
Source : openbase_1_0_dtd
So the dtd reference should be OK now !
But when I try to create the Message Interfaces it is not possible to choose
Any Elements under the external definition openTRANS_ORDER_1_0_dtd.
I would expect to could choose the ORDER element
Here is the openTRANS_ORDER_1_0.dtd.:
<!ENTITY % OPENBASE SYSTEM "openbase_1_0.dtd">
%OPENBASE;
<!ELEMENT ORDER (ORDER_HEADER, ORDER_ITEM_LIST, ORDER_SUMMARY)>
<!ATTLIST ORDER....."standard">
<!ELEMENT ORDER_HEADER (CONTROL_INFO?, SOURCING_INFO?, ORDER_INFO)>
<!ELEMENT ORDER_INFO (ORDER_ID, ALT_CUSTOMER_ORDER_ID*, ORDER_DATE, ...)>
<!ELEMENT ORDER_ITEM_LIST (ORDER_ITEM)>
<!ELEMENT ORDER_SUMMARY (TOTAL_ITEM_NUM, TOTAL_AMOUNT?)>
Can any one explain why I cannot choose any elements when creating my message definition !
Frank

u will be able to choose only the message type in the message interface and not the elements of the message type in message interface.

Invalid Template Definition DTD file

The integration Admin API which allows creation of workflow tempaltes and template
definitions programmatically takes an XML. The XML is supposed to conform to
the DTD file referenced here:
http://e-docs.bea.com/wli/docs70/classdocs/com/bea/wlpi/common/doc-files/TemplateDefinition.dtd
The problem I have is that this DTD is not well-formed. Try to validate it in
your favorite XML editor (e.g. XMLSpy or XMLWriter) to confirm this.
Is there a newer VALID version of this DTD that could be published? I'd like
to believe that Integration is using some DTD or better yet some XSD or schematron
file to validate the XMLs passed into the Admin APIs.
Thanks,
Ira

Hi Ira,
I spoke with engineering and you are correct, the admin bean is not
performing validation checks and there are no current plans for
validation. Due to ambiguities of the DTD, a meaningful DTD cannot be
produced, and instead would have to use a schema definition. Is this an
urgent issue for you? I can raise your concerns to product management
and have them address this in a future release. Please let me know what
changes you would like addressed in this area of the product.
Cheers,
Chris
Ira Work wrote:
Thanks Chris but these links point to the same malformed definitions I had found.
There may not be a valid dtd available because I tested deploying an invalid xml
instance (missing some required elements) and no validation was done by the Admin
API that takes this XML to create a Template Definition. The error in the definition
is not apparent until one attempts to run the workflow instance when the exception
I expected is thrown. If validation of the XML was being done in the implementation
of the Admin method that takes this XML, the exception would have been thrown
at the time of that method call.
So it's no wonder that the published DTD is not well formed, since the implementation
is not even doing validation.
Ira
Chris Stead <[email protected]> wrote:
Hi Ira,
Please try the following link:
http://e-docs.bea.com/wli/docs70/devclient/appa.htm#1016929
Other DTD formats for BPM can be found at:
http://e-docs.bea.com/wli/docs70/devclient/appa.htm#1006326
Cheers,
Chris
Ira Work wrote:
Does anyone in BEA answer questions in this newsgroup???
Please offer a location of a well-formed Template DTD file that couldbe used
for validating a template definition xml before submitting it for deploymentusing
the Admin API.
Thanks,
Ira
"Ira Work" <[email protected]> wrote:
The integration Admin API which allows creation of workflow tempaltes
and template
definitions programmatically takes an XML. The XML is supposed to
conform
to
the DTD file referenced here:
http://e-docs.bea.com/wli/docs70/classdocs/com/bea/wlpi/common/doc-files/TemplateDefinition.dtd
The problem I have is that this DTD is not well-formed. Try to validate
it in
your favorite XML editor (e.g. XMLSpy or XMLWriter) to confirm this.
Is there a newer VALID version of this DTD that could be published?
I'd like
to believe that Integration is using some DTD or better yet some XSD
or schematron
file to validate the XMLs passed into the Admin APIs.
Thanks,
Ira

File to multiple Idocs using external definitions.

Hi all,
I have to create multiple idocs based on one field from source side.
Inorder to do this..I have decided to change the occurance of Idoc from 1 to 1..unbounded , in the xsd i have downloaded from standard Idoc.
which i have a plan to map to the filed , based on that i need to create new Idoc.
I have tried importing the modified xsd into external definition. but how i should relate it to standard idoc which I have mapped earlier?.
Thanks,
venu.

HI Venu,
<i>
I have tried importing the modified xsd into external definition. but how i should relate it to standard idoc which I have mapped earlier?.</i>
After changing the Idoc occurence , you have imported the xsd into external definition. So this will act as as new message type for you in the mapping.
You can not use old mapping here.
Regards,
Moorthy

External Definitions

Hi Friends,
There is a requirement for external definition to import. I got one file from client text file having xml data. So i have save as to .XSD format and tested in XI while uploading into external definitions.
As per my knowledge, .XSD/wsdl/dtd file can be used for external definitions. And, it acts as Message type so create MI .
So , if we request from client , is there specific format is there for .XSD??? Is it only message type else data type possible ???
How to guide the client to get the .XSD files?
Thank you
Deva

Hi Deva,
first convert XML file in to XSD,for that you can use XML Editors ALTOVA XML Spy or Styalus studio to conver XML to XSD.
you can get free trail versions available.
The XML to XSD conversion process very easy , just google it.
if you have XSD then you no need to create Data type and Message Type.
Regards,
Raj

External definition and used them as Data Type Templates

hi all
how to Develop external definition and used them as Data Type Templates .
Thank u
Swari

HI
External Definitions: If a definition of the message structure exists in wsdl, xsd, dtd formats, we can use it in the integration repository by importing it as an external definition.
External Definations:
An external definition enables you to import a local WSDL, XSD, or DTD file to the Integration Repository and specify which parts of the schema to extract as the description for a message. You can use these extracted message schema as:
Output or input messages in message interfaces
Source or target structures for message mappings
There is a series of standard schema for describing the message structure at runtime. WSDL (Web Service Description Language), XSD (XML Schema Definition Language), or DTDs (Document Type Definitions) are often used to describe message schema. If a description of the message structure already exists in one of the above formats, you can use it in the Integration Repository by importing it as an external definition rather than re-entering it manually using the data type editor.
Have a look at
http://help.sap.com/saphelp_nw04/helpdata/en/43/ce49ef1019087ae10000000a1553f6/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ba/d4c23b95c8466ce10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
cheers

DTD files as external Definition

Similar Messages

Maybe you are looking for