From time to time I receive questions about large file uploads with ILINX Capture. ILINX Capture can upload files of any size. The limitation is within Internet Information Services(IIS) and or the amount of memory installed in the web server. This is not only true for ILINX Capture, but and ASP or ASP.Net application.
System Engineers must to be able to choose from a menu of technologies in order to solve ECM business problems. While ECM software vendors often strive to provide a complete set of tools for any anticipated business challenge, in reality, technology advances almost always outpace product release cycles.
Service Oriented Architecture (SOA), Simple Object Access Protocol (SOAP), Extensible Markup Language (XML), and many other similar, and often interoperable, technologies have and are being developed in an effort to provide the ability to glue disparate systems together using published, standards-based mechanisms. While extremely useful, these technologies suffer from some of the same issues as vendor software such versioning, bloat, vendor specificity, and so on.
As an engineer in the field, it’s critical to choose best-of-breed products that solve a core purpose extremely well, then extend the product with other current technologies until a complete solution emerges. Application Programming Interfaces (APIs), whether COM, Web Service, or something else is what makes this extensibility possible. The most useful ECM products provide rich APIs and callable interfaces.
I’m currently finishing a project that uses Oracle’s Imaging and Process Management (OIPM) product. The customer’s version of OIPM targets Microsoft Visual Basic 6 .dlls for custom scripts, and Microsoft .NET 1.1 framework for web development. However, I wanted to target the 2.0 .NET framework for the process scripts, and the 3.5 SP1 framework for the web interface. The web interface solution in particular takes advantage of LINQ, XML data stores, implicitly typed variables, jQuery, and AJAX.
Fortunately, OIPM, while using a fairly old COM-based codebase itself, provides mechanisms that allow an engineer to retain the proven usefulness of OIPM image storage and workflow, but extend to .NET managed code for scripts and web development. The sum of the parts becomes a much more useful solution then if all development was restricted to a closed ECM system that did not provide APIs or was completely COM based.
If you wish to dig deeper, or need a solution, ImageSource provides training, custom development, and field services for many of the popular ECM products.
Senior Systems Engineer