on 10-17-2006 7:45 PM
Can anyone tell me, what the are things that are really increasing the size of the message when it comes into XI.
Is it due to SOAP Header that is added to the message...or anything else...
Please Expalin
Hi,
One of the reason is once the file is converted into XML in XI the size of the file is increased.
Regards
Agasthuri Doss
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Its all because of the XML tags. As you say message we need to take ony the Payload into account.. Just thing of saying just Employee ID it would be like this 123456 just 6 characters.. But if you say the same in XML it would be
<EmployeeID>123456</EmployeeID> simillarly thing of for all the fields and whole message.
The SOAP message are all for standards and for internal purpose and ofcourse that too occupy dose'nt come size, but that does'nt come under message I believe.
Regards,
Prakash
Here my motes about the file adapter:
Q: Which memory requirements does the File Adapter have? Is there a restriction on the maximum file size it can process?
A: The maximum file size that can be processed by the File Adapter depends on a number of factors:
The most important one is the size of the Java heap, which is shared among all messages processed at a certain point in time. In order to be able to process larger messages without an out of memory error (OOM), it is recommended to increase the size of the available Java heap and/or to reduce the concurrency in the system so that fewer messages are processed in parallel.
Another factor negatively influencing the maximum message size in releases up to and including XI 3.0 SP 13 is an enabled charcter set (encoding) conversion if the message type is set to "Text".
Using the transport protocol "File Transfer Protocol (FTP)" also uses more memory for processing than the transport protocol "File System (NFS)" (up to and including SP 13).
If the Message Protocol "File Content Conversion" is used in a File Sender channel, consider that not only the size of the input file affects the File Adapter's memory usage, but even more the size of the XML resulting from the conversion, which is usually a few factors larger than the original plain text file.
To reduce the memory consumption in this scenario, consider configuring the setting "Maximum Recordsets per Message" for the sender channel. This will cause the input file to be split into multiple smaller mesages.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Naveen,
Text file size would be less when compared to the same text file converted in XML. As you know XI deals with XML it will show more size when compared to your normal text file. Apart from this there is nothing more increases your message size.
So when you are sizing your XI you should always consider the size of the XML message rather than your original text file.
I hope it gives you some idea.....
---Satish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.