on 11-07-2008 8:19 AM
Hi!
We have a scenario where we pick up a file and process it and spits out a new file which is a lot larger. Still, the processing time is way to long for my understanding.
The file we have now is almost 4MB, the resultfile will be approx 18 MB. We have tweaked timeout parameters, but after 20 minutes, still no target file has been created.
Does anyone know how a "small" file like this can take so much time?? There are no peculiarities in the mapping, no RFC calls etc, only using the Message Mapping in XI...
Thanks in advance!
regards Marianne
Hi,
See the log file if some other application is not eating the hardware resources. Also your hardware configuration must be good like ram, free space, heap size etc..
btw what is your scenario?
Regards,
Sarvesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The scenario is a csv file picked up from an FTP location. The file is imported to the mapping (only normal Message Mapping), and it produces a file which is put on the application server. This file is (as stated earlier), bigger than the source file.
Content conversion is performed for both sender and receiver adapter, but this should not add any time constraints as I see it.
-M-
Could you please explain where exactly the size changes from 4MB to 18 MB.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
In the mapping, 12 lines are created in the source target file from one line in the original file.
If we strip the file down to 2 MB it takes maybe 5-10 minutes to process...Problem is that we cannot split the original file... But still: what if we get a file on 10MB - should we expect it to take hours? It doesn't make sense..
regards Marianne
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
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.