I do not know SP that well but for what its worth SP is a .NET friendly environment.Frankly what the OT people have done is basically created plumbing conduits based on LAPI libraries(what is available to you and me and many more so think of it as a very high wrapper). In their implementation they move content to and fro between the two environments so both benefit from each other.I have not seen a solution where you use the AGA product to retire livelink or vice versa that is because each of these systems have made NON INTER OPERABLE objects.An Inter operable object may be a document is a document in SP and livelink.Livelink does not have lists or its implementation so you will aether have to map or create functionality To give you an e.g a WF in livelink is a workflow,but you cannot take a Livelink WF map and make it work in SP and vice versa.
So having said that if I were you I will 'Expose' the webservices in your livelink basicaly a 15 to half hour job.Then you would need some starter samples.The web is plenty with that.I would even use a try before you buy product like SOAP UI so you can even practice what your code should be like before you write.
Then if I am successful in doing that I will select a language of my choice and start progressing.Your job as you may soon realize will become less technical and more operational/functional.
I won't advice you to pursue LAPI as it is in a deprecated status
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