on 12-08-2006 9:35 AM
I am doing a File to File.. I pick up a CSV file and drop of to a target. In my Content Conversion Parameters I have specified 1 Recordset per message.
Now my problem is that on the target side I only receive 1 file when the source file has about 6 recordsets and whats worse is that the target file doesn't have any values anyway...
I have checked the mapping in the test tool and it works fine... I looked in SXMB_MONI and I am definitely getting the payload into the pipeline (although all recordsets are coming in as one XML and not multiple as I want... or does it not split it into multimple messages until receiver determination?)
The payload is full in all steps of the pipeline up until the Request Message Mapping Step and here under this particular tree the payload is just
<?xml version="1.0" encoding="UTF-8" ?>
<ns36:GetQuotes xmlns:ns36="http://swanandmokashi.com" />
No fields what so ever... I thought at the very worst I would get all the recordsets in one file but not no recordsets at all...
Please can someone help?
By the way my source file is CSV... and the Payload that you can see in the first step of the pipeline (inbond message central) is:
<?xml version="1.0" encoding="utf-8" ?>
- <Recordset1>
- <RecordStructure>
<id>C05-000089</id>
<SampleDescription>Fully Cooked Pork Loin B/R with BBQ Sauce</SampleDescription>
<SampleComments />
<OperatingCompany>Refrigerated Foods</OperatingCompany>
<Division>527</Division>
<location>N/A</location>
<sourcefacility>06/08/2005 10:16</sourcefacility>
<upc>Compliance</upc>
<date>1260031</date>
<sampletype>2.12</sampletype>
<samplecode>g</samplecode>
<nutrientname>zws0042</nutrientname>
</RecordStructure>
- <RecordStructure>
<id>C05-000064</id>
<SampleDescription>Pork Patties</SampleDescription>
<SampleComments />
<OperatingCompany>Culinary Products</OperatingCompany>
<Division>9030</Division>
<location>4530026311</location>
<sourcefacility>06/07/2005 15:37</sourcefacility>
<upc>Verification</upc>
<date>238585</date>
<sampletype>619.5</sampletype>
<samplecode>mg</samplecode>
<nutrientname>zjs0146</nutrientname>
<testvalue>NA</testvalue>
</RecordStructure>
- <RecordStructure>
Message was edited by:
Alex Ong
Just to let you guys know I have completed the scenario now and it works...
It was quite a simple thing....
So what was wrong with it earlier I had the Recordset Structure field set to RecordStructure,* when it should have been RecordStructure,1.
Thanks for your input anyway
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bhavesh,
Do you have any Ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yup no problem....
<b>Content Conversion Parameters</b>
Document Name: MT_Source
Document Namespace: urn:text.com:xi
Recordset Name: Recordset1
Recordset Structure: RecordStructure,*
Recordset Sequence: Ascending
Recordsets per message: 1
Key Field Type: String (case sensitive)
RecordStructure.fieldSeparator ,
RecordStructure.endSeparator 'nl'
RecordStructure.fieldNames id,comments,etc,etc,etc,etc........
Does this look like it should look at the source file and only extract 1 recordset per message?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok I seemed to of found a solution to the no mapping...
I didn't add the dosument name or name space....
Now I have the problem where I am getting only one file out put when the structure has multuple recordsets and I have specified that I want 1 recordset per message...
So in theory I should get an out put of multiple files being delivered.... but its not?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Alex,
it seems that you want to do a message split from one source file to multiple files.
That case in the mapping in the messages tab change the occurance of the target message as 0..unbounded ...
you will see that the structure in the mapping editor had changed.
Carry out the mapping -- the payload will be split at the adapter only and not before that.
But also check .. not all adapter supports this.. I guess file supports...
Cheers,
Himadri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry guys... I didn't read your responses and your suggestions did help... regarding the name space.... So i will mark accordingly for this..
My last problem is the splitting....
I am aware of the splitting function but this is on SP14 am I correct?
Well we are on 12 which is why I am trying to do it within the sender adapter content conversion.... but it isn't splitting to multiple messages...
please help?
Hi,
User the Message mappin third tab(one source to multiple target or multiple sources to single target ) do the same thing in Interface Mapping.
Create the Integration Process.
Receive -> Transformation -> Many Send steps...
ID :
__
Create one Sender aggrement
Create one Receiver Determinartion as per your source and target
Create Integace deterimation as per your source and target
Create Receiver Aggrement as per your source and target
Regards,
Venu.
Hi I don't think you are right to say that
<b><ns34:MT_Source xmlns:ns34="urn:text.com:xi"></b>
Doesn't show up in sxmb_moni... I have checked other successful transactions and it does appear...
I think it must be something to do with my sender Content Conversion Parameters... Because for some reason when it gets transfered from the source dir to pipeline it is not added...
So what could be wrong?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OK i'll come to the content conversion in the minute....
I have found the problem with the Payload in SXMB_MONI but I don't know how to solve it
Basically when I add the following line
<b><ns34:MT_Source xmlns:ns34="urn:text.com:xi"></b>
to make the top of the payload look like this it works...
<?xml version="1.0" encoding="utf-8"?>
<ns34:MT_Source xmlns:ns34="urn:text.com:xi">
<Recordset1>
<RecordStructure>
However the SXMB_MONI payload look like this
<?xml version="1.0" encoding="utf-8"?>
<Recordset1>
<RecordStructure>
So you see the line I mentioned above is missing for the payload in the pipeline...
Could someone tell me what this line is and why the message doesn't map with out it....
Also any ideas on how to solve the problem so that the message that goes into the pipeline has this mentioned line init
Message was edited by:
Alex Ong
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Alex,
In Content Conversion Parameter Recordset per message remove the variable , it is converting hole message or not just check it scenario will word ..then you need check once again Content conversion parameter & Recordset per message variable.
Regards,
Venu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Alex,
Test your mapping by copying the payload in the MONI into the test tab. Check this blog for this,
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
Recorsets per message --> I have not seen an issue with this. Can you give the Source File format and the content conversion details?
Regards,
Bhavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
OK update...
When I try the incoming XML payload.... it doesn't map either... but it also doesn't give any error.. it says successful but no target field...
What could be wrong here... why is the incoming xml not working?
All the fields look good but it doesnt produce any target fields?
Message was edited by:
Alex Ong
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.