Xml.processFieldNames limitations

We are having some problems using the content conversion on the JMS adapter. Our legacy system sends fixed-width records to us via MQ series. Each record can contain hundreds of fields, also fixed-width. Although we are able to set up simple parsing, the 256 character limitation for the processFieldNames.fromConfiguration is preventing us from receiving about 75% of our interfaces, as they have more fields than we can fit. We looked at the fromFile configuration, which gets us past the names issue, but does not help with the same 256 character limitation in the fieldFixedLenghts paramter that comes after. Suggestions?

Hi,
For the XSL file, you need to use
<xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0" version="1.0">
instead of
<xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl">
We were able to parse the file with this modification. If this does not solve your problem, please provide us with some description of the error that you are getting.
Thank you,
Oracle XML Team

Similar Messages

XML Parser Limitations?

I'm having problems using the XML Parser from
Oracle. I've encountered this both in the
transviewer beans as well as my own implemenatation of the parser.
The problem occurs when I use an XSL document with a for-each declarative in it. Internet Explorer successfully parses an XML document using this XLS file, but when I use the Oracle Transviewer, the data from the XML document is not parsed into the output.
Is this an error of mine or a limitation of XML Parser?
Here are my XML and XLS docs:
<?xml version = '1.0'?><?xml-stylesheet type="text/xsl" href="cd.xsl"?>
<PatientSummary>
<PATIENT>
<PatName>JONES
</PatName>
<PatFirstName>FRED Z
</PatFirstName>
<PatGenderCode>M
</PatGenderCode>
<PatBirthDtm>06Jul1976
</PatBirthDtm>
<PatPrimAddressStreet>123 Main Street
</PatPrimAddressStreet>
<PatPrimAddressPost>498555
</PatPrimAddressPost>
<PatPrimAddressCity>Edmonton
</PatPrimAddressCity>
<PatPrimPhoneNum>6045374321
</PatPrimPhoneNum>
</PATIENT>
<PATIENT>
<PatName>JONES
</PatName>
<PatFirstName>FRED Z
</PatFirstName>
<PatGenderCode>M
</PatGenderCode>
<PatBirthDtm>06Jul1976
</PatBirthDtm>
<PatPrimAddressStreet>123 Main Street
</PatPrimAddressStreet>
<PatPrimAddressPost>498555
</PatPrimAddressPost>
<PatPrimAddressCity>Edmonton
</PatPrimAddressCity>
<PatPrimPhoneNum>6045374321
</PatPrimPhoneNum>
</PATIENT>
</PatientSummary>
<?xml version = '1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl">
<xsl:template match="/">
<html>
<body>
<xsl:for-each select="PatientSummary/PATIENT">
<table border="2" bgcolor="yellow">
<tr>
<td>
<xsl:value-of select="PatName"/>
</td>
</tr>
<tr>
<td>
<xsl:value-of select="PatFirstName"/>
</td>
</tr>
<tr>
<td>
<xsl:value-of select="PatGenderCode"/>
</td>
</tr>
<tr>
<td>
<xsl:value-of select="PatBirthDtm"/>
</td>
</tr>
<tr>
<td>
<xsl:value-of select="PatPrimAddressStreet"/>
</td>
</tr>
<tr>
<td>
<xsl:value-of select="PatPrimAddressPost"/>
</td>
</tr>
</table>
</xsl:for-each>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
null

Hi,
For the XSL file, you need to use
<xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0" version="1.0">
instead of
<xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl">
We were able to parse the file with this modification. If this does not solve your problem, please provide us with some description of the error that you are getting.
Thank you,
Oracle XML Team

XML load limited to 20 child nodes? Why?

I use the attached code to load the attached xml file, but it
will only load the first 20 nodes. I have moved the 20th to the
21st and the 21st up to the 20th and it will still load the first
20, so it isn't a formatting problem.

OK. The plot thickens. My onLoad continues to fire
indefinitely, so I modified the following onLoad function to trace
some info and I get the following in the output window.
XML Status = 0
XML Loaded = false
Percent Loaded = 0 of 7966 bytes loaded
XML Status = -9
XML Loaded = true
Percent Loaded = 7966 of 7966 bytes loaded
XML Status = -9
XML Loaded = true
Percent Loaded = 7966 of 7966 bytes loaded
xmlObject.onLoad = function (success){
if (success){
if (xmlObject.getBytesLoaded() == xmlObject.getBytesTotal())
xmlLoaded = true;
trace("XML Status = " + xmlObject.status);
trace("XML Loaded = " + xmlObject.loaded);
trace("Percent Loaded = " + xmlObject.getBytesLoaded() + "
of " + xmlObject.getBytesTotal() + " bytes loaded");

MessageTransformBean in sender JMS Adapter flat file to xml conversion

Hi All,
The scenario is MQ (Flat File ) --->PI -
>Idoc
The flat file structure is
112233
AABBCC
The expected XML Structure after using MessageTransformBean in the sender JMS adapter is
<Record>
<Row>
<f1>11</f1>
<f2>22</f2>
<f3>33</f3>
</Row>
<Row>
<f1>AA</f1>
<f2>BB</f2>
<f3>CC</f3>
</Row>
</Record>
But I am getting 2 SEPARATE xml messages each with only one Row in it like the following
1st XML:
<Record>
<Row>
<f1>11</f1>
<f2>22</f2>
<f3>33</f3>
</Row>
</Record>
2nd XML:
<Record>
<Row>
<f1>AA</f1>
<f2>BB</f2>
<f3>CC</f3>
</Row>
</Record>
I would like to have one xml message with all rows in it.It seems the MessageTransformBean is not recognizing the end of line in the flat file.Do i need to use endSeparator explicitly.
I followed the "How to use Content Conversion in JMS Adapter " and configured the adapter,still no luck..
Any Help greatly Appreciated
Thanks,
C

Hi Chirag,
The parameter name sequence changes alphabetically by itself when I save and activate it eventhough I enter as it is in the document.How to stop changing this sequence or put it the order as required in the Module Processor.
Currently my sequence is
Transform.Class
Transform.ContentType
xml.conversionType
xml.documentName
xml.documentNamespace
xml.fieldFixedLengths
xml.fieldNames
xml.processFieldNames
xml.structureTitle
Let me know how to change the sequence ,if that is the issue.
Thanks,
C

How to convert Mail attachment file Tab Delimited file to XML.

Hi PI Experts
    I have XI scenario: MAIL XI SAP (ABAP Proxy), the process is
1.     XI will receive tab delimited file as attachment in mail.
2.     XI will convert the tab delimited file into XML, then map to the target structure.
3.     Target will be posted into ECC through ABAP Proxy.
Can anyone help me how can I convert the attachment file (i.e. Tab delimited file) to XML while configuring the sender side.
Thanks in Advance

I just grabed what I answered from another thread. It should work.
Processing sequence as follows:
1. localejbs/AF_Modules/PayloadSwapBean Local Enterprise Bean swap1
2. localejbs/AF_Modules/MessageTransformBean Local Enterprise Bean tran1
3. sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean Local Enterprise Bean mail
Module Configuration as follows: Fill the XXXX part with your info.
swap1 swap.keyName payload-name
swap1 swap.keyValue MailAttachment-1
tran1 Transform.Class com.sap.aii.messaging.adapter.Conversion
tran1 Transform.ContentType ext/xml;charset=utf-8
tran1 xml.conversionType SimplePlain2XML
tran1 xml.documentName XXXXXXX_Mail
tran1 xml.documentNamespace http://XXXXX.com.au/XXXX
tran1 xml.fieldSeparator \t
tran1 xml.processFieldNames fromConfiguration
tran1 xml.structureTitle rows
Once you set up the above configuration, you will get one record at a time.
Create a souce message interface like the followings:
XXXXXXXXX_Mail
rows
record
Target message interface:
XXXXXXXXX
rows
field 1
field 2
field 3
Write a UDF function to remove the TAB space
public removeTABSpace(String record,Container container){
//write your code here
StringTokenizer st = new StringTokenizer(record,"\t",false);
String t="";
while (st.hasMoreElements()) t += st.nextElement();
return t;
Write another UDF to get the field 1 for example:
public String getField1(String input,Container container){
int counter=0;
int beginIndex=0;
int endIndex=0;
int i;
for (i=0;i<input.length();i++){
if (input.charAt(i)==34){
counter=counter+1;
if (counter==1){
beginIndex=i+1;
counter=0;
break;
for (i=0;i<input.length();i++){
if (input.charAt(i)==34){
counter=counter+1;
if (counter==2){
endIndex=i;
counter=0;
break;
input=input.substring(beginIndex,endIndex);
return input;
Get the mapping like the followings:
record - removeTABSpace - getField1 - field 1
If you need to get field 2, you will need to write another UDF similar to the above one to handle it.

Problem converting flat file to XML using JMS Adapter

I need to take an MQSeries message in a flat file format and convert it to XML before processing. I have configured the modules as described by the screenshot located here:
http://www.radesix.com/JMSConfig.jpg
The message is received however it isn't converting to XML. When I view the payload I get the message indicated by the screenshot located here:
http://www.radesix.com/JMSError.jpg
I am new to XI. Any ideas?

For simple plain conversion here is a config, which works in our system:
(left parameter key, right parameter value, module key always the same)
Transform.Class com.sap.aii.messaging.adapter.Conversion
TransformContentType text/xml;charset=utf-8
xml.conversionType SimplePlain2XML
xml.addHeaderLine 0
xml.processFieldNames fromConfiguration
xml.documentName SA02_Identnummer
xml.documentNamespace urn:mycompany-com:logistics:DFT:HWL
xml.structureTitle SA02_Identnummer_Satz
xml.fieldNames Satzart,Identnummer,Status
xml.fieldFixedLengths 2,10,3
Be aware, that you must delete all spaces in the config, especially when you copy and paste values.
For struct. conversion the entries are a little bit more complex.
Regards
Stefan

Conversion of Flat file to XML

Hi ,
        I have a scenario where i need to convert a FLAT File to XML ...
           Since I am using Seeburger Adapter the   usage FCC is ruled out.
           Is there any inbult Adapter Module available in SAP PI which can be used to convert a Flat file to XML.
         The Flat file has many rows... I just want a single record to repeat n times.
         Please help me on this.
Thanks,
Siva

Why don't try with Message Tran Bean
Check this below details out:
Processing Sequence:
1 localejbs/Seeburger/solution/sftp Local Enterprise Bean solutionid
2 localejbs/AF_Modules/MessageTransformBean Local Enterprise Bean mtb
3 localejbs/CallSapAdapter Local Enterprise Bean exit
Module Configuration:
mtb Transform.Class com.sap.aii.messaging.adapter.Conversion
mtb Transform.ContentType text/xml;charset=utf-8
mtb xml.conversionType SimplePlain2XML
mtb xml.documentName XXX_EXPENSES_mt
mtb xml.fieldContentFormatting trim
mtb xml.fieldNames FIELD1,FIELD2,FIELD3,FIELD4
mtb xml.fieldSeparator '0x09'
mtb xml.processFieldNames fromConfiguration
mtb xml.structureTitle RECORD
Regards
Pothana

How to do document offset in Simple Plain to XML for Zip file Sender side

Hi,
Scenario is .zip file to IDOC, A idoc per a record. .Zip file has simple Plain structure like below. Tab delimiter.
Name number   code   country   Rating Item
ABC    123        C4        IND           I2        PRD
ABD    123        C4        IND           I2        PRD
ABE    123        C4        IND           I2        PRD
I am using Adpater Module and Header is generating a IDOC (total 4 IDOCs) in ECC. I would like to use similar to file 'document offset ' option in Adapter Module to skip the header row. so, I need only 3 IDOCS.
plain2XML and using MsgTransfermationBean.
I tried with
xml.documentSkipFirstRows=1
xml.documentOffset=1
xml.addHeaderline=0
I came to know that above all for STRUCTURAL Plain parameters so no use.
I checked this http://forums.sdn.sap.com/thread.jspa?threadID=1223739
http://help.sap.com/saphelp_nw04/helpdata/en/70/f3cbad30ee479cb15672219f3405f0/frameset.htm
Could you please help me with proper parameter to skip the header/first record of the file.
Thanks
shoukat

Hi Shoukat,
Try with the following parameter:
xml.processFieldNames = fromFile
As of SAP Help: "means that the field name information is located in the header line of the file to be converted."
Hope this helps,
Greg

Conversion of XST file to XML file and vice a versa

Hello All,
I am working on one of the SAP-DMS issue.
Here my requirement is converting the XML file to XST file and vice a versa.
I tried to find out the possible solutioin but not succeed yet...
Please can anyone help with the solution?
Regards,
Reshma

Why don't try with Message Tran Bean
Check this below details out:
Processing Sequence:
1 localejbs/Seeburger/solution/sftp Local Enterprise Bean solutionid
2 localejbs/AF_Modules/MessageTransformBean Local Enterprise Bean mtb
3 localejbs/CallSapAdapter Local Enterprise Bean exit
Module Configuration:
mtb Transform.Class com.sap.aii.messaging.adapter.Conversion
mtb Transform.ContentType text/xml;charset=utf-8
mtb xml.conversionType SimplePlain2XML
mtb xml.documentName XXX_EXPENSES_mt
mtb xml.fieldContentFormatting trim
mtb xml.fieldNames FIELD1,FIELD2,FIELD3,FIELD4
mtb xml.fieldSeparator '0x09'
mtb xml.processFieldNames fromConfiguration
mtb xml.structureTitle RECORD
Regards
Pothana

Sender Mail adapter encounters MalformedInputException

I have a sender mail adapter that processes the attached .csv file. All is working fine. I use FCC in module to convert the attachment and pass to an IDOC adapter for processing in SAP system.
My problem is sometimes the sender mail CC fails with ...........
exception caught during processing mail message[1]; com.sap.aii.af.mp.module.ModuleException: Transform: failed to execute the transformation: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
It only fails with some files. At the moment when we test we FORWARD the email to our email account. If I detach the failed email attachment and attach it to a NEW email it will then work.
So why does it not work when forwarding emails? But it works when I attach the same file to a new email and send?
Other threads for this error seem to point to encoding. But how do I know which to use. I currently use the following in my module config:
Transfer.ContentType     application/octet-stream;charset="ISO-8859-1"

I have this in my configuration:
localejbs/AF_Modules/PayloadSwapBean   on local
TRANSFORM
localejbs/AF_Modules/MessageTransformBean   on local
txtxml
TRANSFORM   swap.keyName   payload-name
TRANSFORM   swap.keyValue   MailAttachment-1
txtxml   Transfer.ContentType   application/octet-stream;charset="ISO-8859-1"
txtxml   Transform.Class   com.sap.aii.messaging.adapter.Conversion
txtxml   Transform.ContentDescription   MailAttachment-1
txtxml   Transform.ContentDisposition   attachment;filename="MailAttachment-1.bin"
txtxml   xml.conversionType   SimplePlain2XML
txtxml   xml.documentName   MT_BCD_INVOICES
txtxml   xml.documentNamespace   urn://federalmogul.com/BCDTRAVEL/FINGLOBCD001/00
txtxml   xml.fieldNames   COST_CENTRE,EMPLOYEE_ID,PRODUCT_GROUP,COMP_CODE,BCD_ACCOUNT,INVOICE_DATE,TRAVELER_NAME,TRAVELER_FIRST_NAME,INVOICE_NO,AMOUNT_EXCL_VAT,CURRENCY1,AMOUNT_VAT,CURRENCY2,AMOUNT_DOC_CURRENCY,CURRENCY3
txtxml   xml.fieldSeparator   ;
txtxml   xml.lastFieldsOptional   YES
txtxml   xml.processFieldNames fromConfiguration
txtxml   xml.structureTitle   RECORDSET

Mapping problem in sap xi 2.0

Hi all,
I am also trying the same scenario. In mapping test, i have taken the payload data and tested it. But the source structure is not being populated into target structure without any errors. Can u plz explain how u didit?
This is source xml instance:
<?xml version="1.0" standalone="yes" ?>
<resultset>
<row>
<field0>GNCHETTYROAD</field0>
<field1>T.NAGAR</field1>
<field2>10101980</field2>
<field3>CHENNAI</field3>
<field4>U3</field4>
<field5>HEXRAM</field5>
<field6>M</field6>
<field7>NANDURI</field7>
<field8>US</field8>
<field9>US04</field9>
<field10>0001</field10>
<field11>875945621</field11>
<field12>oh</field12>
<field13>44412</field13>
</row>
</resultset>
This is target instance after test execution:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ZHRONBOARD_ACCEPT xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
<ADDRESS1 />
<BIRTHDATE />
<CITY />
<EMPLOYEESUBGROUP />
<FIRSTNAME />
<GENDER />
<LASTNAME />
<PAYROLLAREA />
<PERSONNELAREA />
<PERSONNELSUBAREA />
<SSN />
<STATE />
<ZIP />
</ns0:ZHRONBOARD_ACCEPT>
Can any one plz tell me where am doing mistake???
Are there any patches for sap xi 2.0 file adapter??
Rgds
Ramsri

Hi Vinod,
Thanks for your reply. Here is my file adapter configurtion. I am working on sap xi 2.0.
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
mode=FILE2XMB
#mode = file2xmbwithrowconversion
Integration Engine address and document settings (example, see docu)
XMB.TargetURL=http://ht56f4:8000/sap/xi/engine/?type=entry
#XMB.SLDConfiguration = SLDaccessor7
XMB.User = xiappluser
XMB.Password = xipass
XMB.SenderBusinessSystem = Intromoto_bus
XMB.SenderInterfaceNamespace = http://inttest.com
XMB.SenderInterfaceName = zminterface
#XMB.SenderBusinessSystem=ExtAdapterSender
#XMB.SenderInterfaceNamespace=http://sap.com/xi/xidemo
#XMB.SenderInterfaceName=ExtAdapterSenderIF
XMB.ContentKind=T
#XMB.ContentKind=T
#XMB.ContentType=application/xml
#XMB.ContentType=text/xml
XMB.ContentType=text/plain
XMB.QualityOfService=EO
#ftp server details
ftp.host = 102.52.12.17
ftp.port = 21
ftp.user = heass
ftp.password = a****a
ftp.connection = permanently
ftp.mode = Text
#file.sourceFilename = bank.txt
##File Adapter specific parameters (example, see docu)
file.sourceDir= \/test\/
file.sourceFilename = satya3.txt
#file.processingMode=setAttribute
#file.processingMode=archive
#file.archiveDir=c:/temp_archive
file.pollInterval= 60
file.pollIntervalMsecs= 10
#file.retryInterval = 30
file.logPollInterval=YES
file.processingMode=delete
##xml conversion properties if mode FILE2XMBWITHROWCONVERSION specified (example, see docu)
#xml.fieldFixedLengths=8,9,2
xml.processFieldNames=from configuration
xml.fieldNames=Address1,Address2,DateOfBirth,City,Personal Subarea,LastName,Gender,FirstName,PersonalArea,PayrollArea,SSN,State,zip
xml.fieldSeparator=,
xml.enclosureConversione = YES
Can u plz inform where i am doing mistake??
Rgds,
Ram Sri

Content conversion in Sender JMS Adapter

Hi,
Scenario is file to IDoc
My source file is   ' ; ' separated file coming from MQ via JMS adapter. now I need to convert this to XI.
Source DT looks like
Root
HEADER (Occurance 1)
     Field 1
     ISOCURCD
     TRANKODE
     IDENTIFIER
     DATO
     TIME
DETAIL(Occurance 1 to unbounded)
     ISOCURCD
     TRANKODE
     EFFDATE
     COMMDATE
     DKKVAL1
     USDVAL1
TRAILER(Occurance 1)
     ISOCURCD
     TRANKODE
      TRANCOUNT
According to How to use content conversion in JMS guide from SDN i have configured the content conversion parameters in the module of JMS sender adapter.
In the processing sequence given the module name as localejbs/AF_Modules/MessageTransformBean and module Key as Plain2XML.
And in module configuration
Parameter Name                      Parameter Value
Transform.Class                          com.sap.aii.messaging.adapter.Conversion
Transform.ContentType                     text/xml;charset=utf-8
xml.keyFieldName                          TRANKODE
xml.keyFieldType                          CaseSensitiveString
xml.recordsetName                          Root
xml.documentName                                   MT_ROOT
xml.documentNamespace                          http://XXX.XXX.XX/xi/XXXXX
xml.processFieldNames          fromConfiguration
xml.conversionType                                   StructPlain2XML
xml.recordsetStructure          HEADER,1,DETAIL,*,TRAILER,1
xml.HEADER.fieldNames           Field1,ISOCURCD,TRANKODE,IDENTIFIER,DATO,TIME
xml.HEADER.fieldSeparator                     ";"
xml.HEADER.keyFieldValue                     H
xml.fieldSeparator                                      ";"(if i don't use this then the file is not being picked and getting an error in the CC monitoring of RWB saying xml.field separator missing.)
Similarily for Detail and Trailer records as well.
But when I run the scenario, the file is being picked up but I am not getting any payload into the inbound message.
Can you please help me where I have configured wrongly. And one more thing will this configuration help for ; separated file .
Thanks & Regards,
Kumar
Edited by: Kumar on Dec 19, 2007 11:11 AM
Edited by: Kumar on Dec 19, 2007 11:15 AM

HI,
Have you gone through the below pdf i think it will help to find ur mistake.
How to use conversion modules in JMS - https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Thnx
Chiarg

Sender Mail Adapter Attachment

Hi All
The mail I get from the 3rd party has a body and attachment. I have done the TRANSORM module as described in some of the forums, and then the Plain2XML.
On sxmb_moni I see the MailMessage and MailAttachment-1, where the MailMessage is in XML format and MailAttachment in normal text. What should I do to completely ignore the MailMessage(body of the mail) and just send MailAttachment to the receiver.
I have tried to split the message to two receivers, but because the attachment message does not transform to xml, it gives me a mapping error. Is there anyway I can either ignore the body and just send the attachment to the receiver without doing JAVA code.
Thanks in advance
Clinton

Hi Jin
Thanks for your answer.
This is how I am using the module within the Sender Mail Adapter.
localejbs/AF_Modules/PayloadSwapBean           TRANSFORM
localejbs/AF_Modules/MessageTransformBean     Plain2XML
TRANSFORM     swap.keyName     Content-Description
TRANSFORM     swap.keyName     Content-Disposition
TRANSFORM     swap.keyValue     attachment;filename="MailAttachment-1.xml"
TRANSFORM     swap.keyValue     MailAttachment-1.xml
Plain2XML     Transform.Class          com.sap.aii.messaging.adapter.Conversion
Plain2XML     Transform.ContentType     text/xml;charset=utf-8
Plain2XML     xml.conversionType     SimplePlain2XML
Plain2XML     xml.documentName     MT_TEBA_Contractor_Details
Plain2XML     xml.documentNamespace     http://lonmin.co.za/TEBA_to_SAP
Plain2XML     xml.fieldNames          ENG_TYPE,INDUST_NO,COMPANY_NUMBER,SURNAME,INITIALS,NAME,REGISTERED,MALE,EXPERIENCE,RACE,MARITAL,DEPENDENTS,BIRTH_DATE,LANGUAGE,EDUCATION,SPOUSE,RELIGION,OFFICE,SERIAL_NO,REG_YEAR,SERV_START,SERV_EXPIRE,SERV_PER,LAST_CHANGE_DATE,LAST_CHNAGE_TIME,ID_DOC,ID_EFF_DATE,ID_EXP_DATE,PASSPORT,PASS_EFF_DATE,PASS_EXP_DATE,COUNTRY,DISTRICT,ADDR1,ADDR2,ADDR3,POSTCODE,PHONE,BI_1733_NO,REASON
Plain2XML     xml.fieldSeparator     |
Plain2XML     xml.processFieldNames     fromConfiguration
Plain2XML     xml.structureTitle     Details
Using it like this it does not do the swap correct and it still put the data within the body as xml, and leave the attachment as txt.
Can you see something wrong here.
Thanks
Clinton

Question about J2SE-File-Adapter

Hallo,
i would send with the J2SE-File-Adapter a *.CSV to SAP XI.
The structure in the SAP XI is:
PlaintMaintenanceMessagetype
......Datasource..................string
......Data
..........item
..............EquipmentID.............string
..............FunktionalLocation......string
..............Data....................string
..............Time....................string
The *.csv File structure is:
6ATESTDEMOYVES,
1234,
Limo,
20060105,
122030,
The configuration of the J2SE-File-Adapter is:
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
version=30
mode=FILE2XMBWITHROWCONVERSION
##File Adapter specific parameters (example, see docu)
##file.type=BIN
file.type=TXT
file.encoding=UTF-8
xml.documentName=ns:PlaintMaintenanceMessagetype xmlns:ns="http://doehler.com/sapxi/krausdemosender"
xml.structureTitle=6ATESTDEMOYVES
xml.processFieldNames=fromConfiguration
xml.fieldSeparator=;
xml.fieldNames=Datasource,EpuipmentID,FunctionalLocation,Data,Time
But it not runing! Can anybody help me? Are any How to guide to send a *.csv with the J2SE-File-Adapter.
Thanks laura
With the XML File it works. But there are ofer 40000 records in the *.csv, and i will not create this in *.xml!
The structure of the XML.File are:
<?xml version="1.0" encoding="UTF-8"?>
<ns:PlaintMaintenanceMessagetype xmlns:ns="http://doehler.com/sapxi/krausdemosender">
<Datasource>6ATESTDEMOYVES</Datasource>
<Data>
    <item>
      <EpuipmentID>1234</EpuipmentID>
      <FunctionalLocation>Limo</FunctionalLocation>
      <Data>20060105</Data>
      <Time>122030</Time>
    </item>
    <item>
      <EpuipmentID>1235</EpuipmentID>
      <FunctionalLocation>Bier</FunctionalLocation>
      <Data>20060106</Data>
      <Time>122031</Time>
    </item>
   </Data>
</ns:PlaintMaintenanceMessagetype>

Hi Laura,
You can navigate thru these links to get more information:
http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e698aa90-0201-0010-7982-b498e02af76b
Cheers,
Chandra

Installation and then Configuration of Plain J2se Adapter Engine

Hi All,
Actually we want to use JMS Adapter for that we had installed Plain J2SE Adapter Engine but after installing and following the initial steps of Adapter.pdf we are not able to access the Adapter Engine through URL.We are using the URL http://<hostname>:8200/MessagingSystem/receive/AFW/XI
this URL is there in our SLD but we are not able to access the page.
So Please can somebody help me to resolve this issue.
Thanks & Regards
Sathya

Hi Amol,
I am trying to send read data from MQSeries using JMS adapter. We are successful in opening the Adapter Engine and the GUI. We have cofigured the adpter as follows. But when we try to restart the adapter to get the changes get saved we are getting the following error
<b>"ERROR CALLING THE RESTART ADAPTER"</b>
Also status is shown is yellow and version is shown as not set.
Where ever I have changed the configuration data I have shown it in bold
JMS-Adapter Configurarion
This Configuration is a sample for a JMS sender channel (inbound, sends to XI IS)
Set XI message protocol version. This sample is designed for XI 3.0
version=30
JMS message receiver class
classname=com.sap.aii.messaging.adapter.ModuleJMS2Transport
set if a transacted JMS Session should be used (default: true)
#JMSSession.sessionTransacted=false
set delay in milliseconds before processing next message after an error (default: 0)
errorDelay=10000
#set delay in milliseconds before trying to reestablish the JMS Connection after a connection error (default: -1 (do not try to reconnect))
#reconnectDelay=10000
set the Message Formats you want to process (Formats only needed if they can not be evaluated at runtime)
TransportMessage Type can be set to TransportMessage of XMBMessage. It is used for sending and receiving Transport and XMBMessages
#TransportMessage.type=TransportMessage
TransportMessage.type=XMBMessage
uncomment and adjust parameters for Transformation Type (Binding of JMS-Transport Message),
insert your class here for an individual binding between JMS and Transport Message
uncomment the following line for using Bindings that belong to Tunneling
#transformClass=com.sap.aii.messaging.adapter.trans.JMSTunneling
uncomment the following line for using Bindings that belong to Single Payload Binding
transformClass=com.sap.aii.messaging.adapter.trans.JMSSinglePayloadBinding
ID Garbage Collector: For EO(IO) handling XI adapters store the JMS/XI message ID's in the ID logger
Uncomment the following lines and change the default values if you recognized "out of memory" problems due to
very large ..\tech_adapter\Data\*_ID.dat files which will be kept in the memory as well
eoExpirationAfterDays is the period of keeping the message ID in days. Afterwards the message ID might be used again
garbageCollectorInterval is the period in milliseconds when the ID garbage collector is started. It will however only
be started if messages are exchanged otherwise ID logs won't be created anyway
eoExpirationAfterDays=365
garbageCollectorInterval=86400000
<b>#
the following parameters are used in some Bindings that belong to Single Payload Binding needing XMBHeader Information
uncomment and adjust parameters according your requirements. Please note, that the party identfier needs not to be
configured in case of A2A scenarios.
#XI.SenderParty=Sender
XI.SenderService=MQSeries
#XI.ReceiverParty=Receiver
XI.ReceiverService=MTX
XI.InterfaceNamespace=http://xitest
XI.Interface=MI_Out_File
XI.TraceLevel=1
XI.LoggingLevel=1
XI.QualityOfService=EO
XI.QueueId=ABCD
XI.ContentType=text/xml
#</b> *************************************************************************************************************
<b>#
URL of XI IS to send the messages to
XI.TargetURL=http://bwxi:50000/sap/xi/engine?type=entry
XI.User=XIAF
XI.Password=XIPASS
#</b> *************************************************************************************************************
URL of file adapter if a loopback JMS to File should be configured
XI.TargetURL=//localhost:8210/file/receiver
<b># uncomment the following settings if needed (independent on JMS provider)
JMS.QueueConnectionFactoryImpl.user=xisuper
JMS.QueueConnectionFactoryImpl.password=xxx
#</b>
uncomment and adjust parameters for loading JMS administrated objects via JNDI
uncomment and adjust parameters if not the default context should be used
#JNDI.InitialContext.property.1=java.lang.String {javax.naming.Context.INITIAL_CONTEXT_FACTORY}, java.lang.String com.sap.engine.services.jndi.InitialContextFactoryImpl
#JNDI.InitialContext.property.2=java.lang.String {javax.naming.Context.PROVIDER_URL}, java.lang.String localhost:50004
#JNDI.InitialContext.property.3=java.lang.String {javax.naming.Context.SECURITY_PRINCIPAL}, java.lang.String Administrator
#JNDI.InitialContext.property.4=java.lang.String {javax.naming.Context.SECURITY_CREDENTIALS}, java.lang.String sap
set the Lookup Names
#JMS.JNDILookupNameQueueConnectionFactory=jmsfactory/default/joetest
#JMS.JNDILookupNameQueue=jmsQueues/default/sapDemoQueue
uncomment and adjust parameters for loading JMS administrated objects from filesystem ***
#JMS.FileNameQueueConnectionFactory=SAPQueueConnectionFactory.ser
#JMS.FileNameQueue=SAPQueue.ser
uncomment and adjust parameters for creating SonicMQ JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=progress.message.jclient.QueueConnectionFactory
JMS.QueueConnectionFactoryImpl.constructor=java.lang.String localhost:2506
JMS.QueueImpl.classname= progress.message.jclient.Queue
JMS.QueueImpl.constructor=java.lang.String SampleQ1
<b># uncomment and adjust parameters for creating MQSeries JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=com.ibm.mq.jms.MQQueueConnectionFactory
JMS.QueueConnectionFactoryImpl.method.setHostName=java.lang.String BWXI
JMS.QueueConnectionFactoryImpl.method.setChannel=java.lang.String JAVA.CHANNEL
JMS.QueueConnectionFactoryImpl.method.setTransportType=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP}
JMS.QueueConnectionFactoryImpl.method.setQueueManager=java.lang.String QM_BWXI
JMS.QueueImpl.classname= com.ibm.mq.jms.MQQueue
JMS.QueueImpl.constructor=java.lang.String postcard
JMS.QueueImpl.method.setTargetClient=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ}
#</b> *************************************************************************************************************
uncomment and adjust parameters for using a dispatcher ***
#Dispatcher.class=com.sap.aii.messaging.adapter.ConversionDispatcher
#Dispatcher.namespace=namespace1
#namespace1.ConversionDispatcher.logPayload=true
#namespace1.Service.1=Plain2XMLService
#namespace1.Plain2XMLService.class=com.sap.aii.messaging.adapter.Conversion
#namespace1.Plain2XMLService.xml.conversionType=SimplePlain2XML
#namespace1.Plain2XMLService.xml.processFieldNames=fromConfiguration
#namespace1.Plain2XMLService.xml.fieldNames=a,b,c
#namespace1.Plain2XMLService.xml.fieldSeparator=;
#namespace1.Service.2=XSLTService
#namespace1.XSLTService.class=com.sap.aii.messaging.adapter.XSLTConversion
#namespace1.XSLTService.XSLTConversion.XSLTFileName=Data/DemoConversion.xsl
Can you please help me in resolving the error.
Regards,

Xml.processFieldNames limitations

Similar Messages

Maybe you are looking for