Teaching IBM OmniFind to Index IBM’s Portal Document Manager Content
June 11, 2009
I know you have been hungering for a fix to this thorny problem. My first brush with OmniFind and IBM’s Portal Document Manager triggered surprise. I assumed that a connector would allow one IBM product to connect to another IBM product. Well, it’s not that simple. You can work through eight pages of instructions starting here. It is not possible for me to summarize the steps in this Web log post. I can give you a preview of what you will learn, however. Step 15 in the procedure to install the HTTP Access Servlet in the Portal Server suggested:
You must also add a reference to the vbr.jar file as a shared library under the vbr_httpaccess.war file that you just installed. If you do not already have a shared library defined, go to Environment -> Shared Libraries in the WebSphere Application Server V6.0 administration console (Figure 14) and add a new library named VBR_JAR_SHARED_LIB.
Wait, there’s more. Explore the tutorial, screenshots, and sample code at your leisure. Intuitive stuff.
Stephen Arnold, June 11, 2009
Comments
One Response to “Teaching IBM OmniFind to Index IBM’s Portal Document Manager Content”
-
- Subscribe to Beyond Search
Feature archive
News archive
-
[…] recall that post and the eight Web pages of technical procedures and code snippets, you can read “Teaching IBM OmniFind to Index IBM’s Portal Document Manager Content” or my other Web log posts about IBM’s […]