how to learn livelink API

[mohanbond]

Hi Gurus,

I'm new to livelink. I need to pull millions of documents from Livelink. Can some one suggests me how to start learning Livelink Java APIs.

I believe there is a developer guide with APIs and example. Please suggest if there is any such document.

Thanks.

Regards,
Mohan

 

[appnair]

I am assuming you mean to learn a API to do programming in livelink. The LAPI stuff is very old and deprecated that you find here

http://greggriffiths.org/livelink/development/lapi/

It will work but you will need a lot of hand holding.also support for it form the
old programmers is almost non existent.Many times I reply to old lapi qns because it interests me .

The best option is for you to go to knowledge.opentext.com and look at OT published samples for Web Services API (it is either called CWS or EWS)

I also program in WSAPI and you will find my samples at my blog livelink.in I just suppplement what users ask me to do or things that end users find difficult
to do. Downloading documents is the easiest thing one can do with the wsapi and is clearly illustrated in the KB.

BTW You will not be able to practice lapi or wsapi if you do not have access to a livelink server and OT code is heavily geared to
protectionism so you willnot find a lot of free samples outside the OT KB.





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

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

http://www.linkedin.com/in/appunair

http://www.livelink.in

 

[mohanbond]

Thanks Appnair, I'm using webDav to get the files. As of now, I'm not pulling metadata. Using webDav it is not be possible to get metadata.
I believe WSAPI is best bet to get full information related to documents.

 

[LAMINI]

I believe WebDAV will get you user docs, nothing more. Just like copying files from a folder and pasting to a destination. You'll lose anything and everything that system was purposed to do. That is, unless the org for some reason just used the app as an overpriced documentation repository. In that case, better for you. Youre either gonna pay big bucs$ or spend a whole lot of time figuring out that mess.

Step 1: get a support account with the vendor. I do hope you have an existing support contract.