Hello everyone, does anyone have an experiences to share regarding the use of EWS to do document uploads where the document is greater than 4MB? How about with large numbers i.e. 10,000 per day?
Thanks for your input.
Philip,
I am in process of using EWS to import ~50K files ranging up to 200MB size (including metadata). I've transferred 8000 of the files for a test group.
There are several "lessons learned" (and I'm not finished learning them -- LOL). I'm using CS 10 with IIS7. There are several configuration changes that are not mentioned in documentation. I can probably help you with some of the hurdles.
Mark Hamby
Hi Mark, If there are details that you would like mentioned in the documentation, please let us know, and we can do our best to have the documentation updated with the information. Thanks, Kyle
I will, Kyle. I am working through a couple final issues. Once those are fully resolved, I will post my lessons-learned and config settings both here and in a no-reply-needed support ticket.
Thanks,
That's fantastic. Thanks Mark!
Hi Mark,
I am working with Philip on a project to integrate a number of systems with Open Text using the Web Services. We are very interested in your approach as it seems that we will have similar loads. Would it be alright for us to contact you directly through email with additional questions as they come up?
Regards,
Michael
What changes do we need to do in the config file to upload documents over 100 MB? I have been trying to invoke uploadContent with bigger files. I was successful with files upto 130MB. But, I get an error when I try a bigger file. It is an instant error as if there is a check on the server side which looks at the file size and sends the error out. I am not able to figure it out yet and would like to see your approach and config file settings.
Thanks, Kapil
Sorry, all. I've been out of the loop for a while.
I believe OT should make these changes or document them to allow transfer of large files and node lists.
Here are the ContentService and DocumentManangement serivce binding changes we made on the client side to enable large files. I guess you could also add it to service binding definitions on the server Document Management needs them if you are requesting large node lists.
We also added this to our IIS7 web.config in OpenText\webservices\dotnet\les-services\. (Not sure how to do the equivalent in Tomcat.)
<!-- IIS 7 configuration --> <!-- GEN3: Allow large files cause errors. Needed for IIS7 too for unknown reason. --> <system.web> <httpRuntime maxRequestLength="200000"/> </system.web> <system.webServer> <modules> <add name="LogModule" type="OpenText.Livelink.Service.Core.LogModule" preCondition="managedHandler"/> </modules> <validation validateIntegratedModeConfiguration="false"/> <!-- GEN3: Uncomment if large files cause errors. --> <security> <requestFiltering> <requestLimits maxAllowedContentLength="524288000"/> </requestFiltering> </security> </system.webServer>
Feel free to contact me if you have questions, but I prefer to document the solutions in this forum.
Mark Hamby GEN2 Technologies 913-620-0480
Trying this again with better formatting. -- Mark
Sorry, all. I've been out of the loop for a while. I believe OT should make these changes or document them to allow transfer of large files and node lists.
<!-- IIS 7 configuration --> <!-- GEN3: Allow large files cause errors. Needed for IIS7 too for unknown reason. --> <system.web> <httpRuntime maxRequestLength="200000"/> </system.web> <system.webServer> <modules> <add name="LogModule" type="OpenText.Livelink.Service.Core.LogModule" preCondition="managedHandler"/> </modules> <validation validateIntegratedModeConfiguration="false"/> <!-- GEN3: Prevent large files from causing errors. --> <security> <requestFiltering> <requestLimits maxAllowedContentLength="524288000"/> </requestFiltering> </security> </system.webServer>
Mark Hamby GEN2 Technologies913-620-0480
Thanks for the posting right information. It was very usefull
Kumar
