Currently we access them using a third party application that requires iSeries to access the AS/400 (I don't know...
how the third party application makes the call to the optical drive).
The indexes are created manually by our scanning department. The indexes live on the AS/400. Here is the description of the process from our AS/400 programmer:
The keyword file (TMM0300) will give you the object ID. Use that to go to the link file (TMM0310). That will give you the document ID (aka internal object ID). Use that to get to the document file (TMM0320). That will give you data about the document, including the volume and optical path on which the document resides.
How do I make a connection from my Windows Web Server to the AS/400 to retrieve the images?
Finally, when writing the stream to a file on the WebSphere server, be sure to give it the right MIME type for the specific image format (eg .jpeg, etc.) so the client applications will correctly handle the file when accessing it in WebSphere.
Dig Deeper on Web Servers
Related Q&A from Jim Mason
Java to Excel with the AS400 may be attractive, but if you have complex VBA macros in Excel, the JDBCODBC bridge will not work well for you. A better...continue reading
There are a couple of options for accessing AS/400 data, from the old way using Client Access ODBC drivers, to Java, to a new application from Groovy.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.