XML header?

Hi experts,
I am generatig an xml file. I want to add FileID = "X123" before version="1.0" in the xml header.
For ex:
<?xml version="1.0" ?>
to
<?xml FileID="X123" Version="1.0">
Any idea?

NO. SAP XML parser are the tools created by SAP to work with XML.
Parsing XML
All modern browsers have a build-in XML parser that can be used to read and manipulate XML.
The parser reads XML into memory and converts it into an XML DOM object that can be accessed with JavaScript.
You will learn more about the XML DOM in the next chapter of this tutorial.
There are some differences between Microsoft's XML parser and the parsers used in other browsers. The Microsoft parser supports loading of both XML files and XML strings (text), while other browsers use separate parsers. However, all parsers contain functions to traverse XML trees, access, insert, and delete nodes (elements) and their attributes.
In this tutorial we will show you how to create scripts that will work in both Internet Explorer and other browsers.
Note: When we talk about parsing XML, we often use the term "Nodes" about XML elements.
In package SIXML you have the tools and examples for work with XML in an efficient way.

Similar Messages

Create a new line in the xml-header structure.

Hi,
Can any one tell me how to create a new line in the xml-header structure.
I am doing a IDOC-XI-HTTP scenario.
Actually my mapping create this file:
<?xml version="1.0" encoding="utf-8"?>
<ORDERS05>
<IDOC BEGIN="1">
 <EDI_DC40 SEGMENT="1"> 
The result must look like this.
<?xml version="1.0" encoding="utf-8"?>
<ORDERS05>
<IDOC BEGIN="1">
 <EDI_DC40 SEGMENT="1"> 
Thanks and Regards,
Eren

Hi,
thanks for you quick answer.
I found a xsl script.
It works fine.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" indent="yes"/>
 <xsl:template match="*">
 <xsl:param name="depth">0</xsl:param>
 
 <xsl:if test="$depth > 0">
 <xsl:text> </xsl:text>
 </xsl:if>
 <xsl:text>
</xsl:text>
 <xsl:element name="{name(.)}">
 <xsl:for-each select="@*">
 <xsl:attribute name="{name(.)}"><xsl:value-of select="."/></xsl:attribute>
 </xsl:for-each>
 <xsl:apply-templates>
 <xsl:with-param name="depth" select="$depth + 1"/>
 </xsl:apply-templates>
 </xsl:element>
 </xsl:template>
</xsl:stylesheet>
Best regards
Eren

Remove XML Header

I am developing a Java Servlet and would like to query the database multiple times. I have used OracleXMLQuery and an array to be able to run three separate queries. My problem is occuring in my returned XML Document. Each query comes back with a XML Header such as:
<?xml version = '1.0'?>
<Query_1>
<COL1>10</COL1>
</Query_1>
<?xml version = '1.0'?>
<Query_2>
<COL1>20</COL1>
</Query_2>
<?xml version = '1.0'?>
<Query_3>
<COL1>30</COL1>
</Query_3>
I have assigned the header separately and would just like to be able to turn off the generated header. My problem is coming when I am trying to use an applet and it does not like when it sees the XML header more than once. Any ideas or hints on how this can be done I would appreciate it.

Hello this did solve my issue. I have same issue infact. I used this xsl mapping as
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="no" omit-xml-declaration="yes"/>
</xsl:stylesheet>
But my output xml struıcture has broken. Should I do some changing in my xsl mapping and how ?
Regards,
Ceren.

Adding Encoding in XML header without mapping

Hi Gurus,
I am stuck in a situation where in a pass through scenario, I need to add encoding type in XML header.
Below is example -
Current Situation - <?xml version="1.0"?>
Expected result - <?xml version="1.0" encoding="UTF-8"?>
Can anybody help me in this regard? how to achieve this?
Regards
Vidhi S

Hi Vidhi
Use it in the below way in the receiver adapter.
Module name: AF_Modules/XMLAnonymizerBean
Parameter name: anonymizer.encoding
This will work. I have tested already.

Adding additional XML Header in Target XML structure

Hi all,
I have a requirement that i need add one additional XML header to target XML messages. At the moment i can see default XML header as ,
<?xml version="1.0" encoding="UTF-8" ?>
<Test>
<Add>Test Mesage</Add>
</Test>
But i would like to have one more additional header like below,
<?xml version="1.0" encoding="UTF-8" ?>
<?Siebel-Property-Set EscapeNames="false"?>
<Test>
<Add>Test Mesage</Add>
</Test>
Can some one help me to find a way to adding this additional header?
Thanks in advance.
Prasad Babu.

Hi Prasad,
Yes it is possible by Java Mapping. Please check my response for similar thread
Re: Add XML header?

XML header for WebServices (SOAP)

Hi all!
I have quite strange problem about XML header in SOAP message for WS. Usually I don't care about XML header in SOAP message, because so far I had no problems calling load of WS on different servers. Stnadard XML header that comes out looks like this (1.0 and UTF-8 are in single quotes): <?xml version='1.0' encoding='UTF-8'?>.
But this time, the webserver I'm trying to call accepts only double quotes, e.g. like this: <?xml version="1.0' encoding="UTF-8"?>, it doesn't understand single quotes at all and there is no way of changing it!
JDeveloper uses apache soap for standard and makes single quotes. I tried raw http call by wrapping all text into post method -> that works, so webservice is working.
I can't set anything except endpoint, parameters, method :(
How can I make call that uses double quotes?
Pseudo logic is like this:
Vector params = new Vector();
params.addElement(xxxx);
Call call=new Call("xxx", "xxx", params, xxx, Constants.NS_URI_SOAP_ENC);
Response response = call.invoke(endpointURL, "xxx");

Hacked Oracle (apache) classes and put right values in it.
It was hard coded string, who on earth could thought that :D

Encoding missing from XML header

I have to manipulate an XML document. Using Java 1.4.1, I build a Document object based on the XML file, manipulate the Document and output it as attached below.
The problem is that the xml header in the output does not contain the "encoding" information. I could of course manipulate the output afterwards, but it would not be a neat solution. Any ideas?
DOMSource domSource = new DOMSource(document);
StreamResult streamResult = new StreamResult(
new OutputStreamWriter(System.out , java.nio.charset.Charset.forName("UTF-8"))
TransformerFactory tf = TransformerFactory.newInstance();
Transformer serializer = tf.newTransformer();
serializer.transform(domSource, streamResult);

When you serialize your output to a Writer, the parser has no way to tell what encoding the Writer uses, so it's up to you to ensure that the parser knows what encoding the Writer is using. Otherwise it will not specify any encoding, essentially assuming the Writer is using either UTF-8 or UTF-16 encodings.
In your case you don't have a problem, because "no encoding" means that the document is encoded in UTF-8 or UTF-16; it's easy for a parser to examine the first few bytes of the file and tell which it is. Yours is encoded in UTF-8, so it's correct.

[svn:fx-trunk] 13383: Modify to include the xml header (with encoding) in the DITA xml files.

Revision: 13383
Revision: 13383
Author:   [email protected]
Date:     2010-01-08 12:04:00 -0800 (Fri, 08 Jan 2010)
Log Message:
Modify to include the xml header (with encoding) in the DITA xml files.
QE notes: None.
Doc notes: None
Reviewed By: Pete
Tests run: checkintests
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

Thats good news.

XML Validation: ignore non-XML-Header in XML-file(payload): any solutions?

Dear Experts,
after I finally managed to configure the XML Validation, we're facing the next problem:
The payload of the XML files looks like that:
Abcdef#ABCDEF
AbcDef#123
<?xml version="1.0" encoding="UTF-8"?><Document xmlns.....
as you can see, there's a header which is necessary. The XML Validation works fine if the header is removed manually for testing. If the header is not removed, the validation is not possible ("Content is not allowed in prolog.")
Is it possible to realise the validation WITH that header? Can I tell SAP PI to ignore the header? Or make any changes to the XSD file?
Thanks alot!

Hi Armin,
Armin Kern wrote:
> After leaving SAP PI, those 2 lines have to be in that exact place (before the XML part) for further processing. Just deleting it wouldn't be enought. Does the complex design you mentioned complay with this requirement?
You can put it into the message instead of deleting. And rebuild the "header" in the second step. So you can fullfill the requirement. As mentioned before: The design is complex, this will lead later on to problems. Any change will be difficult, as another developer had to read a long documentation.
An alternative would be to do all with one interface mapping (without validation):
1. ABAP / Java mapping deleting the "header" (put it to memory)
2. Messges Mapping 1:1 each field (will fail in case of wrong format and act as validator)
3. ABAP / Java mapping restoring the header
4. Alert will be raised in case of an error (to get the result of the validation)
Armin Kern wrote:
> I also thought about splitting the message, deleting those 2 rows in one of the messages, sending this one message to PI again, validate it and if it is correct, send the second message (without mapping) to the final destination. No idea if that is possible at all..
As well possible. You would need a virtual receiver for the first message, which is sending back a response. For example a servlett, a proxy or a RFC module. In that design you put some logic to the sender, what is actually not bad. But if you do so, why you dont validate there as well (for example with Java)? It would make your design much easier..
Regards,
Udo

Xml header in transformation strans

Hello,
I would like to create an xml file with the following header information:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:tem="http://tempuri.org/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<tem:mygesttem>
<tem:mytem>
So, I have created the following piece of code in transaction STRANS:
<?sap.transform simple?>
<tt:transform xmlns:tt="http://www.sap.com/transformation-templates">
<tt:root name="ROOT"/>
<tt:template>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:tem="http://tempuri.org/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<tem:mygestem>
<tem:mytem>
However, as soon as I launch it with CALL TRANSFORMATION in my ABAP program the xml file is different from I would expect:
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Body>
<tem:mygestem xmlns="http://tempuri.org/">
<tem:mytem>
Could anyone tell me why the header is different from expected?
Thank you,
Oscar

Any ideas? please.

Text to Xml-Header Line

Hi
In text to xml scenario...how to eliminate the headers in text file
Text file data is like
H1-header line1
H2-header line 2
E100 Rahul - Data
E101 Siva - Data.
I need only data in xml file..what setting i have to make in file content conversion parameters in sender side..In blogs it is given for text to xml..In those i am not getting regarding header line removal from text file (sender)
Give some suggestion to get this scenario
Regards
Prakash

Hi Prakash,
Create the Data type with all fields (Headr & Item) but while mapping do not map the header filds to target. But in your Content Conversion Define every thing (Header & Item filed lengths etc.) so this way your file will be ficked up by adapter and while mapping only Item values will be mapped and you will get only item data in your XML file.
Below is the example when you have HEADER & ITEM structure.
FCC is case sensitive, give all the names in FCC same as your Data Type.
In Recordset Structure = Header,1,Item,*
Header.fieldFixedLengths = (field lengths) e.g. 1, 4, 7
Header.fixedLengthTooShortHandling=ignore
Header.endSeperator='nl'
Item.fieldFixedLengths = give the item field length as shown above
Item.endSeparator = 'nl'
Item.lastFieldsOptional = YES
Regards,
Sarvesh
****Reward points, if found helpfull.

XML header Missing

Hi i am doing a File-XI-File scenario, using Content Conversion.
Sceanrio involves Multimapping.
The problem is The XML payload created by my Sender Communication Channel Does not match the XML-Strucure expected in MessageMapping, The header of the XML structure differs which results in a MAPPING RUNTIME EXCEPTION.
Below is the Strucure of the Source XML payload (Generated by my Sender Adapter)
<?xml version="1.0" encoding="utf-8" ?>
- <ns:MT_Source_ItemMaster xmlns:ns="http://Itemmaster/demo">
- <Records>
- <Recordset>
<Fileno>0000005265</Fileno>
<Item>00000000000000001</Item>
<Aendtyp /> ......so on
Now when i Check my Interface mapping with no data under Test tab, and see the XML Structure at Source it is like this
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
<ns1:MT_Source_ItemMaster_1 xmlns:ns1="http://Itemmaster/demo">
Please notice the header part indicated in bold.I am unable to figure out how i can change my source payload to look like this

Hi Thanks for all ur responses,
However it is not creating the header automatically i have run the scenario and get an error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <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="MAPPING">GENERIC</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_Source_to_Target_1_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
Not sure how it is happen any more ideas...wud be grateful

Genrate xml header in abap

I have to genrate a header xml file for using web service.it should be in this format
soapenv:Header>
wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
wsse:UsernameToken wsu:Id="UsernameToken-3" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsse:Username******/wsse:Username
wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText"********/wsse:Password
wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security1.0#Base64Binary"ZOgqLICgF/zcOQZ3gsVpXg==/wsse:Nonce
wsu:Created2010-03-29T15:45:35.597Z/wsu:Created
/wsse:UsernameToken
/wsse:Security
/soapenv:Header
As far as i can understand i feel only the username,password and password type are required in this formart.
wsse:Header
wsse:Security
wsse:Username******/wsse:Username
wsse:Password Type=PasswordText"********/wsse:Password
/wsse:Security
/soapenv:Header
i code i have written for the same is
DATA: l_header_prot TYPE REF TO if_wsprotocol_ws_header,
        lr_dom        TYPE REF TO if_ixml_element,
        lr_dom2       TYPE REF TO if_ixml_element,
        lr_dom3       TYPE REF TO if_ixml_element,
        lr_dom4       TYPE REF TO if_ixml_element,
        lr_dom5       TYPE REF TO if_ixml_element,
        lr_ixml       TYPE REF TO if_ixml,
        lr_document   TYPE REF TO if_ixml_document,
        lr_text       TYPE REF TO if_ixml_text,
        lr_text1       TYPE REF TO if_ixml_text,
        lr_text2       TYPE REF TO if_ixml_text.
lr_ixml = cl_ixml=>create( ).
lr_document = lr_ixml->create_document( ).
lr_dom = lr_document->create_element( name = 'Header' ).
lr_dom2 = lr_document->create_element( name = 'Security' ).
lr_dom3 = lr_document->create_element( name = 'username' ).
lr_text = lr_document->create_text( '******').
lr_dom4 = lr_document->create_element( name = 'password' ).
lr_text1 = lr_document->create_text( '*********').
lr_dom5 = lr_document->create_element( name = 'password type' ).
lr_text2 = lr_document->create_text( 'PasswordText' ).
CALL METHOD lr_dom->append_child( new_child = lr_dom2 ).
CALL METHOD lr_dom->append_child( new_child = lr_dom3 ).
CALL METHOD lr_dom2->append_child( new_child = lr_text ).
CALL METHOD lr_dom->append_child( new_child = lr_dom4 ).
CALL METHOD lr_dom2->append_child( new_child = lr_text1 ).
CALL METHOD lr_dom->append_child( new_child = lr_dom5 ).
CALL METHOD lr_dom->append_child( new_child = lr_text2 ).
i am still facing a issue with the header.
Any othe way in which i can directly generate the xml's??

I have to genrate a header xml file for using web service.it should be in this format
soapenv:Header>
wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
wsse:UsernameToken wsu:Id="UsernameToken-3" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsse:Username******/wsse:Username
wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText"********/wsse:Password
wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security1.0#Base64Binary"ZOgqLICgF/zcOQZ3gsVpXg==/wsse:Nonce
wsu:Created2010-03-29T15:45:35.597Z/wsu:Created
/wsse:UsernameToken
/wsse:Security
/soapenv:Header
As far as i can understand i feel only the username,password and password type are required in this formart.
wsse:Header
wsse:Security
wsse:Username******/wsse:Username
wsse:Password Type=PasswordText"********/wsse:Password
/wsse:Security
/soapenv:Header
i code i have written for the same is
DATA: l_header_prot TYPE REF TO if_wsprotocol_ws_header,
        lr_dom        TYPE REF TO if_ixml_element,
        lr_dom2       TYPE REF TO if_ixml_element,
        lr_dom3       TYPE REF TO if_ixml_element,
        lr_dom4       TYPE REF TO if_ixml_element,
        lr_dom5       TYPE REF TO if_ixml_element,
        lr_ixml       TYPE REF TO if_ixml,
        lr_document   TYPE REF TO if_ixml_document,
        lr_text       TYPE REF TO if_ixml_text,
        lr_text1       TYPE REF TO if_ixml_text,
        lr_text2       TYPE REF TO if_ixml_text.
lr_ixml = cl_ixml=>create( ).
lr_document = lr_ixml->create_document( ).
lr_dom = lr_document->create_element( name = 'Header' ).
lr_dom2 = lr_document->create_element( name = 'Security' ).
lr_dom3 = lr_document->create_element( name = 'username' ).
lr_text = lr_document->create_text( '******').
lr_dom4 = lr_document->create_element( name = 'password' ).
lr_text1 = lr_document->create_text( '*********').
lr_dom5 = lr_document->create_element( name = 'password type' ).
lr_text2 = lr_document->create_text( 'PasswordText' ).
CALL METHOD lr_dom->append_child( new_child = lr_dom2 ).
CALL METHOD lr_dom->append_child( new_child = lr_dom3 ).
CALL METHOD lr_dom2->append_child( new_child = lr_text ).
CALL METHOD lr_dom->append_child( new_child = lr_dom4 ).
CALL METHOD lr_dom2->append_child( new_child = lr_text1 ).
CALL METHOD lr_dom->append_child( new_child = lr_dom5 ).
CALL METHOD lr_dom->append_child( new_child = lr_text2 ).
i am still facing a issue with the header.
Any othe way in which i can directly generate the xml's??

How to change XML Header in file

Hi,
How to have the following XML output header XML with simple transformation:
<?xml version="1.0"> encording="ISO-8859-1"?>
When I used the following transformation template:
<tt:transform xmlns:tt="http://www.sap.com/transformation-templates">
I get the following output header and file is not readable.
<?xml version="1.0" encoding="utf-16" ?>
If i call tranformation without encoding option file is creted and readable. Does there is any impact on functionality if file is without header.
Thanks
anya

Hi,
you could use the below alternative solution also as some Web services do not accept the message , if Content type is application/XML in the HTTP Header, it will accept only Text/XML. So While calling the Web service, the content has to be changed, This is possible using Module of the adapter as shown in the screen shot.
HTTP Header field values before using the module
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
content-id: [email protected]
content-type: application/xml
Content-Length: 1280
Module name - localejbs/AF_Modules/MessageTranspormationBean
Type - Local Enterprise Bean Module - This is defined by the user, but the same name should be given in the module configuration for passing the parameters. In this case transform In the module configuration ,
Module key - In this case transform
Parameter name - Transform.ContenType
Parameter Value - text/xml;charset=utf-8
Here you could use the required parameters and pass the values....:-))
Thanks
Swarup

XML Header Output

Hello
Could some one please tell me how to have the following XML output with simple transformation:
<?xml version="1.0"> encording="ISO-8859-1"?>
When I used the following transformation template:
<tt:transform xmlns:tt="http://www.sap.com/transformation-templates">
I get the following output header:
<?xml version="1.0" encoding="utf-8" ?>
My problem is I would like to have the following output header:
<?xml version="1.0"> encording="ISO-8859-1"?>
Thank you for your input
Nina
Message was edited by:
nadin ram

Make sure you use .xsl mapping as the last mapping program in your mappings list, in the Interface Mapping.
Also, test the mapping in interface mapping test tab.
Execute the mapping and go to XML Source view of the target message.
Is it removed there?
- If yes, then probably the header is added in a later point, maybe in receiver adapter (could occurr with soap adapters, for example). Try a test scenario with a file receiver adapter.
- If not, try to revise the xsl mapping.
The key is the omit-xml-declaration="yes" attribute in the <xsl:output> tag.
You could alternatively, try to use method="text", also in the <xsl:output> tag (if you go for text output, then you don't need to set the omit-xml-declaration attribute).
Regards,
Henrique.

XML header?

Similar Messages

Maybe you are looking for