LAPI when your sole requirement is to mess with Records Management or Physical Objects Management

****************************************** ***START UPDATE 10/3/2016*****************

LAPI and its client installer has become very hard to find. Moreover clients written in LAPI  in say Java/.NET will only work if your Livelink a.k.a Content Server is of version less than CS16.Readers who are new to LL programming is encouraged to read this to the approach and not to the exact lines of the code.What I mean is when you used to program in LAPI you were basically passing parameters to discrete calls by modelling it based on the webgui of livelink .SOAP based webservices called CWS is also the same,so if you do not try to do the task in the webgui and try to understand the business rules you will almost have no success in CWS too. OT is notorious for not putting fully functioning use cases and a walk through,so whenever possible I write code assuming the user has not worked in Livelink for X number of years and try to educate you all. Livelink,Content Server,Enterprise Server all of this has been Livelink’s marketing brand name changes over the years.CS i sused in many of the integrations like AGA, XECM, RMLINK  and you know you are programming against livelink if you see a link that looks like this  http(s)://somefriendlyURL/livelink.exe|cs.exe|llisapi.dll|cs.dll|livelink.In many places SAP/ SP /Exchange will be configured to talk to Archive Server and then they will use Livelink to read into archive server and turn that into LL objects for better presentment/RM and other aspects. The AGA product is moving away from LAPI(not sure totally or not) to REST API in LL.

**********************************************END UPDATE****************************

 

LAPI is not dead it seems.Recently some posters wanted to do something with LAPI and especially with Physical Objects Management.The RM & PO modules are very great functional mods very easily installed and configured and works for almost any condition.Excellent design thoughts by OT(or is it iRIMS). The Web services bandwagon has not exactly swept in with the folks it seems.In any case for the old timers here is the cheat sheet

LAPI you are old need 32 bit computer also VJ redistributable on the livelink server if you are on LL9.7.1 or down

win7 64 bit computer livelink server if you are on CS10 or up but a downgraded .net framework

No installer is made for CS10 so I would just go to any old lapi project and put them in a .NET project which is less than 3.5 CLR

The programmer gets into a very simple document add or folder add routine so he /she has the bearings of how to work against livelink and LAPI if you have not messed with LAPI before do not think you can code in RM/PO LAPI API’s

Here’s the Rub.The RM/PO API is written to look like it is its own product in fact it is not.They are just interface files which the programmers can add to their project and nicely hidden in the server install modules.So if LAPI was given to you as a client installer the RM & PO API is sitting inside the SDK folder of the livelink server.I have many times had need to do this in java and C# so without prejudice this  how I do those tasks.Java is a little more complicated as I am not a full time java programmer or for that matter a C# programmer

https://communities.opentext.com/communities/cs.dll?func=ll&objId=8552848&objAction=download

If you had a IIS server serving your livelink things basically it takes less than 30 mins to create an application to expose DM services,PO services and RM services so if you are in a org that likes to be modern by all means do that approach

Intelligent people on the Sharepoint side have built and safeguarded their investments by creating their own API’s revolving around LAPI(the AGA framework) so I am thinking that LAPI has not been axed and retired.

BTW the ObjectImporter product plus its add on called OI for RM will allow you to bulk add PO and RM info much easier and much less to program than the lapi or webservices approach

Advertisements

About appukili

Oscripter and Livelink aficionado
This entry was posted in livelink records management and tagged , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.