XI : File Size Volume Handling

[ashish_sharma3]

Hi All,

We are facing an issue for a file to file based scenario . We have a file which is downloaded on the application server of ECC and picked up XI transformed in the mapping and sent out as a fixed field length file at the target.However the issue arises when we start processing file size of 14 MB . In the content conversion the file gets convered into a 200 MB file and while passing it to the Integration Engine using the ICM the XML file fails . We had set the http profile server parameters in rz10 hence the messages started coming in to the Integration Engine but the messages are getting stuck in the queue due to file size and are not processing the same and after some time the queues goes in the SYSTEM FAIL status . The error message which we get is "time limit exceeded " when we click on the queue status.In this scenario we cannot split the file using recorset per message as file generated at the target end has a counter and all the records have to go into one single file.

Requesting some pointers on the same.

[Former Member · Accepted solution]

Hi,

You have to do following parameter settings...

For the parameter tuning for messages >= 100 mb

The main parameters are as follows:

java :

In configtool go to Instance_<XXX> -> dispatcher_ID<XXXX> -> services ->

http and increase the property MaxRequestContentLength.

One suggested combination could be increasing MaxRequestContentLength to

256 000 and -Xms and -Xmx in the dispatcher JVM parameters to 512m.

- Java -Xmx max heap setting = 2gb for 64 bit systems.

(thumbrule > 6 * largest message size : therefore if message size is 500 mb then change max heap size to around 4gb)

on the abap side:

icm/HTTP/max_request_size_KB = 2097152

icm/server_port_6 = PROT=HTTP, PORT=5$(SAPSYSTEM)00, TIMEOUT=600

rdisp/max_wprun_time = 3600

ztta/max_memreq_MB = 2048

The last parameter only works for 64-Bit systems.

with regards,

Ravi Siddam

[former_member289598 · Accepted solution]

Thanks for the input.

The key changes regarding the dispatcher adjustments above also described in SAPnote 1031733 have corrected the problem.

We actually tested using MaxRecordContentLength to -1 and increased the Dispatcher JVM values to 512. The 205Mb XML file transfer now processes in just over 1 minute.

Thanks for the support

[ashish_sharma3 · Accepted solution]

Thanks Ravi !!! We have been able to solve the issue based on the pointers given by you.

Appreciate the same.

[agasthuri_doss]

Hi,

Is any transformation needed or do you want to pass just the file ( With out converting to XML )

Cheers

Agasthuri Doss

[ashish_sharma3]

We have to do a transformation for the file hence we have to take into consideration the file content conversion otherwise we could have done a file pass without content conversion.

[agasthuri_doss]

Hi Ashish Sharma,

Got it, Ok Do you maintain Application Server, If so assign the mentioned Interface to particular App Server only and try.

Cheers

Agasthuri Doss

[Former Member]

Hi,

Try to increase the timeout interval and see if it works fine,

SXMB_ADM -->Integration Engine Configuration --> Click on SPECIFIC CONFIGURATION ---> and change the timeout parameter.

Performance of File Adapter depends on many parameters-

Yes, depends on many parameters-

1) Memory - Sizing of hardware

2) Logic used to process the file ( for eg. write a script which will split the file etc)

3) If multiple files at a time having huge volume of data, you can go with EOIO method

Thanks

Swarup