We have implemented a small desktop application for our customer. This application can access LiveLink documents by using LAPI 9.7.0.
My question is: is this allowed to put LAPI dll into our setup package?
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
Is the SDK an additional part you have to puy, if you purchase an LiveLink Enterprise Server?
The license politic of OT is unknown to me. We just want to destribute our LiveLink connector. And this connector uses LAPI. Which options are there to do this easier for us and for our customer? We can say - the customer has to install LAPI on every client (we have to add this to our prerequisites). Or is there a posibility to deploy LAPI together with our setup?
lapi is just client side files like lapi.jar and dll's in the windows platform.When you install lapi in your computer it gets added to the system path .When I develop applications using lapi I use the deployment wizard and it picks up the dependencies.
So when deploying my application it will say VJ redristributable not found,would you like to install.Once done it will work on the lapi.dll bundled in my app.
I work in organization where they have bought livelink and the SDK, the one that you use to develop lapi. I am not a attorney or lawyer so I could not tell you whether OT will come after you for using lapi
Lapi is being deprecated so I started writing most of the stuff in websvcs.
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
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.