RE:Trying to export all versions of docs with audit and version info 1

[AndyH1]

Our company is moving from Livelink to a SAP based system (not my choice), but we need to export all versions of documents and audit and version information for import into SAP. The database is set to external storage (ie the files are stored as .dat files)

Can anyone advise me of the best way of doing this. Opentext advised that an xmlExport may be the best way of doing this, but I am unclear how to do this to get the files. The only area I have used xmlExport in the past is for 'skinning' pages to give them a custom look, and whilst this gives xml information I am unclear how this can be used to export the files themselves?

can anyone advise or point me to information they feel would assist me.

Thanks
Andy

 

[ggriffit]

Causeway Technologies (

http://www.causeway.com)

have a module called PIE that does this kind of thing.

You could write a simple LAPI program that could do this for you.

Greg Griffiths
Livelink Certified Developer & ECM Global Star Champion 2005 & 2006

http://www.greggriffiths.org/livelink/

 

[appnair]

Using xml export you can export the file content as well.If there are large files this could be very time consuming.As Greg says a lapi exporter is all you need.The audit information for an object I do not know if there is a direct lapi way to do it other than running sql thru a livereport.Since the object id info is available in the audit tables,I belive SAP can call the audit tables directly or a copy as well.

Currently I am involved with retiring three livelink instances(again not my call).The way I am doing this is thru oscript.I basically extract all the required info from a folder downand put them into a staging table for the import process to consume.To this end I am using a cacheutil object in conjunction with a nodecrawler.the implementation is designed around the upgarde screen of the categories module,you know the one that goes after 5 nodes at a time.The cacheutil object gives me a nice object that is in the database so in case the server hangs or re-started I don't have to re-extract.






Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[AndyH1]

Thanks - sounds a bit beyond my skills however, as I said Iv'e only really used xmlexport for turning pages into xml so they can be skinned using an xsl stylesheet. I'm not really a livelink programmer - its just one of the systems we use here. Is there anything you could point me too to get my skills up to understanding/doing this.
Thanks
Andy

 

[appnair]

actually start with something small like lapi.Livelink is a very well architechted system although sometimes documentation on programming sometimes is not upto the plate.Using livelink api and any language you should feel comfortable,you should be able to get information for the object/node/datid you are looking for.Once you have that you just repeat it ofor all the others in your system.The one exporter I put in Greg's site was the one I used to export all content out a livelink system.That should still work,although some java methods may have been updated.

Oscript may be a little tough for a starter but it is going to be the most powerful thing you can program in livelink.

Greg's site,the communities.opentext.com and the knowledge base has plenty of handholding examples regarding livelink.

I hope this helps you somewhat.

If you write to me at appoos at hotmail.com I will send you samples in lapi,whatever I have done in the past.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937