Client Server Development Architecture 1

[amboswell]

Hi - Please help me get oriented to LiveLink client app development.

What is the preferred architecture for VB or .net client development? For example if a VB/.net client app wants to add and retreive a document from the LiveLink repository?

I'm reading that LAPI (I have done a bit of that) is outdated and OScript is the preferred LL development platform.

So - is an Oscript module created and stored server side, then the client app makes a URL call to that func to add and retreive the associated document? Or is there another method to be employed.

Thanks - Bert Boswell (Years of programming experience, new to LiveLink and OScript)

 

[appnair]

LAPI the server side remains and is part of the oscript layer.When you install lapi client files in your dev env and code your program in (C,C++,VB,VB.NET,C#,Java) then the program calls the relevant lapi call in the livelink server.Almost akin to telnet livelink server lapiport. Since OT cannot do justice to so many different language requirements they have deprecated lapi client side install.
Hope that is clear to you. LAPI also uses a lot of old data structure type programming that drives modern programmers crazy,so they have relied on the modern webservices paradigm.So in version livelink 9.7.1 and up you have true webservices so lo and behold you point to the wsdl generate java proxies and C#(the easiest) and start programming away.In contrast LAPI has been in service for more than 15 years so a lot of code has already been written for it by ot.Websvcs in livelink is only about 4 to 5 yrs and with every release new calls are added and at some point it will surpass lapi in its functionality.

Oscript is the langaue of livelink server,it is needed if you have a requiremsnt and OT or lapi or websvcs cannot get it done.Also a lot of livelink's webui does not have clean separation of oscript and html(which we call weblingo) so if user interface changes are warranted you use those.It needs you to take training and do/observe how livelink does its job.

For external interfaces like a program to download/upload files,change user stuff.search etc websvcs is sufficient.

Please ask your qns and if it is not clear/apparent we will try to help as much as possible

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