What is the best way to move folder/files from Livelink to Sharepoint? 1

[smallredville]

Hi All,

Through this post, I would like to check on whether anyone has experienced to move/migrate files/folders from livelink to sharepoint.

I initially intended to do it manually, but it is simply too many. In addition, I found that sharepoint platform has limitation on the length of the path (max: 256 char).

Is there any API for livelink to communicate with sharepoint?

Hope someone who knows about it can be generous enough to share with me in this forum.

Sorry for asking sharepoint here in livelink forum, but seriously no offence.

Lastly, many thanks in advance =)

smallredville

 

[appnair]

H'mm quite the opposite to what everybody is doing.OT makes a lot of money by offloading files from SP to LL.That integration exists as a CLM solution for sharepoint.However SP is .NET compatible so If you can find its API on how to create files one could assume that using LAPI the file you want in livelink can be downloaded temporarily(or streamed as well).Once the file handle is obtained wouldn't you just use the SP API's to upload content .....Check the SP forum of tek tips for that.

As far as OT having pre-built communication methods to accomplish this I am not sure but the CLM guys like Ferda who sees this might be able to give you some hints.

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

http://www.tek-tips.com/faqs.cfm?fid=2884

http://www.linkedin.com/in/appunair

 

[smallredville]

Thanks for feedback, Appnair =)

smallredville

 

[prantlf]

Appu is right, OT develops and sells a product for the integration of SP with LL - CLM Services for SharePoint (CLMSP, CLM = Content Lifecycle Management). It is for customers that run both SP and LL and want to access LL data from SP or copy/move/link/search the data between SP and LL in archiving or RM scenarios.

The CLMSP product itself does not have components for a complete migration (a long-running migration service, etc.), it is rather an integration product where the customer can move data around by ASP.NET pages and web parts in the SP UI or set up a scheduled archiving/synchronizing job SP->LL. For example, the customers tend to like the slick SharePoint UI but want to use the more mature RM in LL. Not all customers can switch from one product to the other from some internal reasons; it can end up that SP and LL are running side-by-side.

CLMSP has an SDK to accomplish tasks which do not have UI in the CLMSP product. There are more levels of the API functionality, beginning from the pure LAPI and ending at CLMSP classes executing the high-level data-moving-around scenarios with user, permission, property and RM mapping between the two systems. I have heard about migration projects SP -> LL and LL -> SP done by the OT GS (GS = Global Services) with a help of the CLMSP SDK. (I think that they used mostly just the C# LAPI to upload/download documents but every project chooses the API to fit the best its needs.)

The SharePoint API usable from the Livelink side would be only the web services and they are quite clumsy (MOSS 2k7). But Livelink modules can consume web services and thus such integration could be possible. I find more convenient using the SP object model than the SP web services and using LAPI to communicate with LL. It means that the software must run on a SP server. CLMSP SDK supports the latter approach.

I would suggest you check on the features of CLMSP in OT KC; I believe that there are some data sheets and presentations there. It could give you some hints even if you end up making your own tool based on LAPI and the SP OM. You can also contact OT for more information. The CLMSP SDK is available at OTDN too with documentation and examples. LAPI is available for C++, Java and .NET; its documentation is on OTDN too.

Good luck,
Ferda

--- Ferdinand Prantl