JMS Adapter Content conversion using Webspear MQ

Hi All,
I have a scenario where I have to pick a flat file from WebSpear JMS Q.In turn I should convert flat structure into xml structure to parse to the RFC structure(YOTCS_I090_INV_S) and map to the traget structure.
Below is the Source structure:
Messages
->Message1
-->YOTCI_I090_INV_SYNC
--->YOTCS_I090_INV_SYNC
>item
>ZDATE
>TIME
>TZONE
>WERKS
>MATNR
>LGORT
>CHARG
>SOBKZ
>INSMK
>LIFNR
>ZMENGE
>ZMEINS
>LOT_NUMBER
>CODE_DATE
Source file look's as below:
YOTCS_I090_INV_S                                                                                4928
YOTCS_I090_INV_S                                                                                3
YOTCS_I090_INV_S                                                                                3
YOTCS_I090_INV_S                                                                                1
I am doing the file contact conversion as below in JMS Adapter:
Module Key      ParameterName                           ParameterValue
Plain2XML        Transform.Class                           com.sap.aii.messaging.adapter.Conversion
Plain2XML        Transform.ContentType                 text/xml;charset=utf-8
Plain2XML        xml.conversionType                      StructPlain2XML
Plain2XML        xml.documentName                      YOTCI_I090_INV_SYNC
Plain2XML        xml.documentNamespace            urn:sap-com:document:sap:rfc:functions
Plain2XML        xml.item.fieldFixedLengths           8,8,6,4,18,4,10,1,1,10,13,3,10,8
Plain2XML        xml.item.fieldNames ZDATE,TIME,TZONE,WERKS,MATNR,LGORT,CHARG,SOBKZ,INSMK,LIFNR,ZMENGE,ZMEINS,LOT_NUMBER,CODE_DATE
Plain2XML        xml.processFieldNames             fromConfiguration
Plain2XML        xml.recordsetStructure               item,*
Can any one help me in configuring the Content conversion? Hope you got my issue.
Thanks in Advance.
Best Regards,
Jose

Joseph,
Go thru the Below Link
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
Cheers
Agasthuri Doss

Similar Messages

JMS Adapter Content Conversion

Hi,
I am looking for some help on JMS Receiver content conversion, to put a delimited file on MQ series queue.
I tried the below link, but not able to access the document.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/how to use the content conversion module with the xi 3 j2ee jms adapter
If anyone has a copy of the pdf document on JMS content conversion, could you please email it to me at my id : [email protected]
Rgds
R Chandrasekhar

I had send the required PDF
Regards
Arpit seth

Complex XML to Plain in JMS adapter "Content conversion module"

Hi!
I have read the document on "How To use the content conversion module with XI3.0 J2EE JMS Adapter", and it says only SimpleXML can be converted in the receiver channel.
I had hoped for a solution at least as good as in the File/ftp adapter, where complex XML can be transformed to files.
Are there plans to include complex XML conversion in the JMS adapter?
I can not use the file adapter as I need to change the file name and destination, and that can not be done by adding own module to its single module.
Any idea how I can achieve what I want?
To only way I can find, is to create a file using the file/ftp adapter, and then pick it up again and treat all the lines as the same structure (one row = one xml field). Then output this new xml message to file, using the JMS adapter and add any modules with name and destination determination.
Appreciate any help!
Regards,
Oeystein Emhjellen

Hello,
Have you tried to use an XSLT mapping within the IE?
I have, at one customer site, created a XSLT message mapping which converts the XML to a fixed length ASCII file format. I than added the XSLT message mapping as a second mapping step on the interface mapping.
In this case I was able to publish a fairly complex fixed length file format to MQ Series via the JMS adapter.
/Johan

Receiver JMS Adapter Content Conversion issue

Scenario :
R/3 -->XI -->MQ(XML2Plain)
Hi
We are using Receiver JMS Adapter to send the Message from XI to MQ.
The XML has to be converted to plain file. And Content conversion is
being done.
With the new development, the message type defined consist of 8 fields
with fixed length. The XML message goes successfully from XI to MQ
without any content conversion. But once simple content conversion is
being done for Receiver JMS adapter, even though the message is
received but its empty (without any data records). The adapter
monitoring everything seems fine and it gives the status that message
converted to binary and the message is delivered to MQ. Though on
checking the messages there is no data records.
Below is my content conversion configuration done in Module tab. Kindly
revert back what can be the problem as have done exactly the same way
as described in Content Conversion How to Guide for receiver JMS.
localejbs/AF_Modules/MessageTransformBean Local Enterprise Bean XML2Plain
localejbs/SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin
localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService Local Enterprise Bean exit
XML2Plain Transform.Class com.sap.aii.messaging.adapter.Conversion
XML2Plain TransformContentType text/plain;charset=utf-8
XML2Plain xml.addHeaderLine 0
XML2Plain xml.addHeaderLine SimpleXML2Plain
XML2Plain xml.fieldFixedLengths 8,10,10,20,40,40,8,8
XML2Plain xml.fixedLengthTooShortHandling Cut
regards.
santosh.

Hi,
check localejbs/SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin
this is not CallJMSService.
And also check the receiver Structure, if it is falt structure its ok, else
see the below link if it has the complex structure , how to handle..
See the below links
/people/alessandro.guarneri/blog/2006/01/04/jms-sender-adapter-handling-too-short-lines
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
content conversion
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Regards
Chilla..

Receiver JMS adapter content conversion

Hi All,
Can anyone provide me guidelines on how to do content conversion for the receiver JMS adapter??
Thx
Navin

Hi,
Based on your structure , you need to configure the JMS CC parameters.
see the below link
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
regards
Chilla

Receiver File adapter content conversion using StrictXml2PlainBean

Hi All,
For receiver file adapter i am using the module StrictXml2PlainBean, and also i mentioned the module configuration like this
parameter name                              parameter value
recordTypes                                  Header,TransactionHeader,TransactionDetail,TransactionTrailer,FileTrailer
FileTrailer.endSeparator                |\n
FileTrailer.fieldSeparator               |
Header.endSeparator                   |\n
Header.fieldSeparator                  |
TransactionDetail.endSeparator   |\n
TransactionDetail.fieldSeparator |
TransactionHeader.endSeparator |\n
TransactionHeader.fieldSeparator |
TransactionTrailer.endSeparator |\n
TransactionTrailer.fieldSeparator |
But when i send the idoc, The receiver CC is throwing an error
Message processing failed. Cause: com.sap.aii.af.modules.conversion.xml2plain.ConversionException: Invalid structure name encountered during conversion: Transaction at XML element MT_DeliveryOrder,Transaction
My actual structure is
MT_DelvOrder
   Header 0...1
   Transaction 0....Unbounded
      TransactionHeader 1..1
       TransactionDetail     0...unbounded
        TransactionTrailer 1...1
   FileTrailer 0...1
The module is checking for the Transaction node,but i require the rest 3.
Same configuration i have done successfully with FCC without using the module....
So can any one suggest me where i am missing... why the module is pointint towards, the Transaction cant i ignore this node . and continue with the rest???
Regards,
Sridhar
Edited by: sridhar reddy kondam on Aug 10, 2009 12:35 AM

Hi Rajesh,
The same FCC configuration was working fine with FCC and when i am using this module configuration i am getting the prob...
In the file i need the Header,TransactionHeader,TransactionDetail,TransactionTail,Filetrailer
my sample output file is
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_DeliveryOrder>
<Header>
</Header>0...1
<Transaction>0...Unbounded
    <TransactionHeader> 1..1
     </TransactionHeader>
     <TransactionDetail> 0...Unbounded
     </TransactionDetail>
      <TransactionTrailer>1...1
       </TransactionTrailer>
</Transaction>
<FileTrailer> 0...1
</FileTrailer>
Any suggestions will be great help...
I think i need to go with other options without using this module....
Regards,
Sridhar
Edited by: sridhar reddy kondam on Aug 10, 2009 6:03 AM

MQ Message content conversion using JMS

I want to use JMS content conversion to convert MQ messages into XML (Idoc). We currently use the R/3 link application to send data to/from MQ to SAP.
Each MQ message is one continuous stream of data with no carriage returns or line feed between the header and lines. When I set-up the JMS mapping commands, it sees the message as one string of data and does not map out the separate idoc segments. Can I use JMS file content conversion or will I need some type of JAVA mapping module to handle the mapping for each different type of Idoc segment? If it;s JAVA, could you provide an example. Thanks Jim

Hi Jim,
Go through the following link which disscusses the JMS Content Conversion.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Amaresh

JMS like content conversion in Seeburger

Hi,
Can you have JMS like content conversion in Seeburger?
In Seeburger adapter if username/password is used, instead of public private keys, can you use JMS like content conversion in Seeburger. (the one which you specify as module parameters)
Regards,
Anirudh.

Depending on what solutions you have: you may use seeburger bic module to convert from csv to xml or other formats. best thing usually is to follow the 2 step mapping strategy of seeburger where bic is doing a non-xml<->xml conversion and the target (XML-) format is mapped to in the SAP Message Mapping.

Sender Mail Adapter Content Conversion

Hi All,
     I just want to know if we can send a flat file(Rather Than the XML) with content conversion using Mail Adapter. If yes then what are all the possible ways for this.
I have tried but i am sucessful in sending the complete payload as a XML file, but i want the file with the content conversion, so that this should be able to picked by the third party systems.
Will be oblidge if any supported blog or pdf is provided for the same.
Thanks in Advance.
Jay

Hi,
Now for the negative items, i want to send them back to business as flat file format
using the mail adapter as attachment. This will help them to process the file as for there
requirement.
Since you need to send an email message you have to use the format mentioned here: (S-UserID required)
https://websmp205.sap-ag.de/~sapidb/012006153200000361852004E/ximail30_xsd.txt
Save this file as an XSD in you local system and upload it as an External Definition in your XI server.
Develop MI based on this External Definition (IN, ASYNC)
Create an Interface Mapping with Source as the file containing Negative items and target as the above developed MI
Now you need to develop an XSLT mapping (can use StylusStudio to do it) between the source and target Message Types
This XSLT mapping has to be designed in such a way that it extracts the payload out of the Negative Items message and maps it to the target (Content) field....you need to use CDATA element of XSLT here.
In this mapping itself you can define to what email-id you want to send the message.....
Everything happens on the XI --> Business service side...so it is not the sender channel but is the receiver channel:)
Your XSLT mapping will look something like:
<Mail>
     <Content>
          XSLT CODE
     </Content>
</Mail>
where Mail and Content are the tags in the email message format...the External definition one.....
If you are new to XSLT then refer to my answer in this thread...
Re: JAVA MAPPING
regards,
Abhishek.

JMS Adapter and Conversion Agent

Hi,
Has anyone worked on JMS adapter and Conversion module? JMS adapter is working fine without the conversion agent module.
processing sequence is as follows
1 SAP XI JMS Adapter/ConvertJMSMessageToBinary Local Enterprise Bean convert_JMS2Bin
2 SAP XI JMS Adapter/ConvertBinaryToXMBMessage Locl Enterprise Bean convert_Bin2XI
3 sap.com/com.sap.nw.cm.xi/CMTransformBean Local Enterprise Bean 0
4 CallSapAdapter Local Enterprise Bean call_AF_MS
Also I have given the Parameter Name and value.
Let me know if i am missing something.

I have done the configuration in sender JMS channel. I even created file sender and it is not working.
when i went and checked the initialization events in http://xxxx:50000/CMViewer, I can see some errors under service Initialization.

File content conversion using SOAP adapter

Hi,
     I'm using a receiver SOAP adapter in my IDOC to file scenario and need to do file content conversion in the receiver side.
Are any standard modules available for file content conversion in the SOAP adapter or do I need to write custom EJB modules for this.
Please note that I have to use a SOAP adapter, can't use any other adapter.
Thanks in advance
Shiladitya

Hi,
XML Document Conversion Type
●      Enter recordTypes as the parameter name.
Under Parameter Value, enter the complete, comma-separated list of all names of recordset types that occur in the document to be converted.
If you decide to use this method, you can define a different conversion type for each recordset type that occurs in the XML document.
For example, you could name the recordset types as follows: RecordType1,RecordType2,RecordType3.
●      Enter singleRecordType as the parameter name.
Under Parameter Value, enter the name of a recordset type that is to be used to convert all elements that occur in the XML document.
If you decide to use this method, define the same conversion type for each recordset type that occurs in the XML document.
You must enter exactly one parameter only. Whichever parameter you choose, you automatically exclude the second parameter.
You define further parameters for each recordset type.
In the remainder of this documentation the parameters are specified by the prefix <RecordType>. In your configuration, replace this name with the name of the recordset type.
Conversion Type List with Separators
●      <RecordType>.fieldSeparator
Enter the field separator that is written between the individual fields of a record.
This specification is mandatory.
Conversion Type List with Fixed Field Length
●      <RecordType>.fieldLengths
Specify a character string that contains a list of fixed field lengths that are separated by commas and which determines the number and the length of fields generated in the text file.
For example, you want to write a recordset with three elements that have field widths of five, ten, and fifteen characters. Enter:
<RecordType>.fieldLengths = 5,10,15
This specification is mandatory.
●      <RecordType>.fieldLengthExceeded
Specify how you want to handle fields that exceed the configured field length. Permitted values for the parameter value are:
○       error (default)
Interrupts processing of message with error
○       cut
Cuts off superfluous characters
○       ignore
Ignores the field length restriction
Further Entries
●      <RecordType>.beginSeparator
Enter a string. The string is placed in front of the first field of a recordset.
●      <RecordType>.endSeparator
Enter a string. The string is appended to the last field of a recordset as a concluding character. The default is \r\n.
●      contentType
Enter the MIME type of the converted payload. The default value is text/plain.
●      addHeaderLine
Only define this parameter if you have already defined singleRecordType.
Define whether a header line is to be added to the result of the conversion.
○       none (default)
Does not insert a header line
○       fromXML
The header line is generated from the element name of the first recordset of the XML document
○       fromConfiguration
The header line is determined by the configuration parameter headerLine.
●      headerLine
Only define this parameter if you have already set addHeaderLine=fromConfiguration.
The value that you define is placed in front of the result of the conversion as a header line.
●      fixedLineWidth
Enter the maximum line length n (in characters) that can be written to the resulting document. The separator specified by lineSeparator is inserted in the resulting document every n characters.
●      lineSeparator
Only define this parameter if you have already defined fixedLineWidth.
Specify the string that is written to the resulting document at the end of each line that is written with fixedLineWidth. The default is \r\n.
Use of Special Characters
You can use special characters in the following parameters: <RecordType>.fieldSeparator, <RecordType>.beginSeparator, <RecordType>.endSeparator, headerLine, and lineSeparator.
●      Tabulator: \t
●      Carriage Return (CR): \r
●      Line Feed (LF): \n
●      Arbitrary character: \x<code>
<code>indicates the hexadecimal character code of the character to be displayed.
Regards,
Phani

Query regarding file content conversion using file adapter

Hi All
I have a question regarding file content conversion in file adapter.
I have a file coming in the following format.
AA,111,222,333
BB,444,555,666
CC,777,888,999
My incoming message structure has a hierarchy. The CC record is a structure part of BB record. BB record is a structure part of AA record. It is like this:
AA,111,222,333
<<BB,444,555,666>>
<<<<CC,777,888,999>>>>
After file content conversion, in the resulted xml, i am getting a flat hierarchy instead of nested hierarchy.
Is it possible to get a nested hierarchy as a result of file content conversion?
Please let me know
Thanks
Chandra

Hi Udo
According to your suggestion, I am trying to use mapping.
I am getting a flat file and i am reading it.
This is my source structure:
AA,11,22,33
BB,44,55,66
CC,77,88,99
This is my required targer structure:
AA,11,22,33
<<BB,44,55,66>>
<<<<CC,77,88,99>>>>
To explain this, BB record can have multiple records of CC records.
AA records can have multiple records of BB record.
I am using removecontext node function.
CC (Source) (removecontext)-> CC (target structure)
But here, when i rightclick on source CC field in the mapping editor, i cannot see any other context except root node. So, how can i proceed here??
Many Thanks
Chandra

JMS sender adapter content conversion error

Hi,
Kindly find the error report from MONI.. and have followed this document for sender JMS content configuration
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-adapters/how%20to%20use%20the%20content%20conversion%20module%20with%20xi%203.0%20j2ee%20jms%20adapter.pdf
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_NFEIN_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException:</SAP:P2>
<SAP:P3>Content is not allowed in prolog.</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_NFEIN_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Content is not allowed in prolog.</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

hi folks i have resolved that issue it was mapping change...
Now i'm facing another problem .. I m gettin only header record but i don see me items...
my structure is like this field fixed length
HEADER ( 1 )
OrderDetail(Min - 1 and Max - Unbounded)
Trailer(Min - 1 and Max - Unbounded)
configuration of my JMS adapter :
Transform.Class                              :com.sap.aii.messaging.adapter.Conversion
Transform.ContentType                 :text/xml;charset=utf-8
xml.conversionType                      :StructPlain2XML
xml.processFieldNames                :fromConfiguration
xml.documentName                     : MyDocument
xml.documentNamespace           : http://xi.com/test
xml.recordsetStructure               : Header,1,OrderDetail,,Trailer,
xml.recordsetName                     : Dataset
xml.Header.keyFieldName            :abc
xml.Header.keyFieldValue            :x1
XML xml.keyFieldType                 :CaseSensitiveString
xml.Header.fieldFixedLengths     :1,2,3..
xml.Header.fieldNames                :abc,cde,fgh...
Similarly for order and trailer
Kindly help in this regard.. i was not able to find in search

Ignore record in JMS sender content conversion

Hi,
I am using JMS sender adapter with content conversion.
In the input text file, I have to ignore the first record.
for this, in Module tab I have given parameter like this:
Plain2XML -> documentOffset -> 1
so that it will not read the first record in the text file.
But it is not working
Please suggest the right way.
Regards,
Anil.

It should be:
xml.documentSkipFirstRows
Regards
Stefan

JMS Adapter - data conversion xml- structured data has extra characters

Further to [Using MQ / JMS adapter with legacy system to talk to SAP;, I am using the Module tab on my receiver JMS Adapter to convert the xml payload to a structured format. It converts to the mainframe ebcdic code set. I am on PI 7.11, and the MQ Series (which JMS interacts with) is 6.0. The code I have is comparable to the wiki:[http://wiki.sdn.sap.com/wiki/display/XI/HowTo...ContentconversionmodulewithJ2EEJMS+adapter], i.e. the example at the very bottom of that article.
The issue we are having is that an extra character gets inserted at the end of each structure (within the message), i.e. our message contains 4 structures, but when we view the structured data on our mainframe system (that arrives from PI), the entire message is shifted by 4 characters... by 1 after the end of each structure. On the mainframe, this extra character appears as '.'. It must be an end-of-line or something...
Has anyone had the same issue? If so, were you able to resolve? I could probably set up my message data type to just be one big declare (thus eliminating the use of structures within it), but that is something I'd rather not do.
We are in the process of reviewing Note 856346, #6 but not sure if it applies.
Regards,
Keith

Hi,
check localejbs/SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin
this is not CallJMSService.
And also check the receiver Structure, if it is falt structure its ok, else
see the below link if it has the complex structure , how to handle..
See the below links
/people/alessandro.guarneri/blog/2006/01/04/jms-sender-adapter-handling-too-short-lines
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
content conversion
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Regards
Chilla..

JMS Adapter Content conversion using Webspear MQ

Similar Messages

Maybe you are looking for