However if you are looking for a layman explanation here's how I would put it.
Components of a File Upload in livelink- User's file(cal also be Read as Hacker's File)+Upload to Webserver's temp directory+Node created and file from webserver's temp goes to permanent storage(EFS,Archive or BLOB)
In SEA a SERVLET is used to send the file straight(streamed) into
the +Node created and file from webserver's temp goes to permanent storage(EFS,Archive or BLOB thereby minmizing the intermediate foot print into the webserver.In both cases a virus or trojan can be placed in the EFS. In any good company file shares are usually scanned so the risk is found and quarantined.In the former case the livelink infrastructure the webserver and the communication network can be compromised which is quite a hassle.In the latter the only part that is at risk is the EFS.This is what Security pundits call ASR which stands for Attack Surface Reduction technique.
The deployment is very simple a Tomcat Server is hosted in the DMZ and it contacts the real livelink server through the lapi port.You would consider it if you need to expose the livelink URL in an extranet or internet situation.
Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937
Certified OT Developer,Livelink ECM Champion 2008,Livelink ECM Champion 2010
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.