****************************************** ***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****************************
In this the poster is asking whether this service exists.I have noticed very few good code examples in java and webservices for livelink so this is just an attempt to help.
What I am trying to show the user is I have deployed my webservices in IIS but I am writing client code in java
This link was very helpful in my endeavor
http://stackoverflow.com/questions/3588616/java-webservice-client-best-way
Common Sense tidbits
- CWS/EWS is a bunch of files ending in.svc.It takes less than 10 mins to expose a webservice in IIS.Probably the same amount of time in Tomcat
- If livelink has Records Management module and Physical Objects module then the installer will lay the svc files in the same hierarchy as the CWS/EWS
- Exposing the CWS/EWS will not have code for RM or PO you have to separately expose them or merge them as I do.
- The exposed web service should talk to a livelink server on its lapi port.Web services and livelink servers can be on two machines but it is easier to test and maintain if they are the same.The web.Config will have localhost and 2099 which means the webservices will call a livelink server using that.Now you can install livelink to listen to any free port it is just that most people would leave defaults.
- When using java make sure you understand classpaths and the jax-ws mumbo jumbo really well,in .NET it is very easy to do things
- Once webservices are deployed either in IIS or Tomcat you can mix and match client code.You could write a .NET client to talk to the Tomcat web service or as in my example you can use a java client to talk to IIS deployed web service.
- Rather than thinking that livelink client programming can be done entirely by reading javadocs ask the organization for a livelink web account and understand that the api’s are just making use of the livelink business rules .So 9 times out of 10 you could understand the parameters by watching how a create request,update request etc happens.An org can severely change the way livelink works,its add screens etc so you need a good understanding of how livelink is used in your organization.
- Content Server is livelink.There is no escaping that.Old wine in new bottle.I say that in a positive way as the oscript engine is much better.Any day better for DMS & RM & PO activities.Very strong architecture from ground up
Appukili's Weblog 