Extract document info from Livelink to enable viewing in external app

[felim]

I want to be able to view LiveLink documents in an external web based application. What I'd like to do is to determine all the documents stored within or referenced by Livelink (either by Livelink producing a report or by writing an application that performs some queries). What I ultimately want is to have a file (XML, txt...) that tells me the name of each document Livelink knows about and a URL that a Web browser could use to display the document.

Is this possible?

Thanks

 

[appnair]

http://www.tek-tips.com/faqs.cfm?fid=3949

Livelink allows any userid maintained by livelink to export
objects to which the user has permissions as XML files.To another livelink system they can be consumed very easily because they both know the DTD's.For an external system you may have to write your style sheet to understand what all that means.The operation can be quite cumbersome if you are trying huge hirarchies and contains objects that cannot be xml exported from within livelink.Syntergy has tools,Causeway has tools.If you know livelink programming,it can be easily done thru oscript,I do not know whether LAPI can do this
One more thing that may be of interest.In the OpenText history book it says somwhere that one of the OT guys co authored or had something to do with writing the XML
standard.That I guess is why they tout it as one of the more friendly features.


Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[Syntergy]

You could create a SQL statement that gives you the document names and a "Fetch" URL to all the documents in Livelink. Someone selecting the URL would have to have access to Livelink and "See" permissions to view documents. Assuming you have an Oracle database supporting Livelink the SQL you would use to create URLs to all the documents would be something like

select name, '

http://server.domain.com/Livelink/livelink.exe/fetch/'

|| to_char(parentid) || '/' || name || '?nodeid=' || to_char(dataid) || '&' || 'vernum=0' URL from dtree where subtype = 144 order by name;

This would give you a list of all the documents (subtype=144) and build a url string similar to

http://server.domain.com/Livelink/livelink.exe/fetch/2000/mydocument.html?nodeid=52466&vernum=0

"vernum=0" will give you the latest version of the document. If you are using SQL*Plus the '&' is a substitution character unless it is the last character in a literal string, that's why it is shown as '&' || 'vernum=0'

 

[felim]

Thanks for the responses this has helped a lot.