move documents to Archive system

Hi All,

I am trying to move CS documents to OT Archive system.Can any one help me with sample code on how to do it using CS rest api's.

Thanks in Advance

Find more posts tagged with

Comments

eLink User

Does your Livelink Server have the Archive Server Module configured ?

What is your end goal?

Does the Livelink Document identified by a dataid ? would it still have to come from the Archive Server using its Docid?

The Livelink REST API/SOAP API/L API is agnostic about where Livelink will store the document .If a Livelink system has alternate storage providers

and have proper storage rules and if you find using the webgui you add a document lands it in a particular archive then using an api many times

will do the same thing.Further OT has utility oScript module with which you can create rules to move content between EFS or EASP's

Now if say you want all livelink documents moved to OT's archive server ,kind of a retirement of livelink then you are correct ,in that operation you would use the

Archive Server's native API's.They look like REST but basically is run as AL requests almost like URL's

I suggest you inform this forum about what in your mind is your project about and hopefully many people will try to help.

.....appu appnair appunair

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

On Tue, May 17, 2016 at 10:43 AM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

move documents to Archive system Posted byJ, BharaniLathaOn 05/17/2016 11:40 AM

Hi All,I am trying to move CS documents to OT Archive system.Can any one help me with sample code on how to do it using CS rest api's. Thanks in Advance
[To post a comment, use the normal reply function]
Forum: Content Web Services Forum
Content Server: Knowledge Center

Kyle_Swidrovich

You could also consider using Content Move on the Content Server instance itself.

This would relocate the storage of documents meeting your defined criteria to Archive Server.

I believe that Content Move is a part of standard CS product in CS 10.5 SP1+.

BharaniLatha_J

we have multiple versions of document in our CS10,so our aim is to move all older versions with metadata and hard copy of document to Archive Server 10.5 and delete the file from CS10 and live CS with only the latest version.

So we need to fetch the CS document with its dataid and unique id(which we use) and check if this is present in Archive if present the add versions to it and move.

eLink User

Metadata is database space and archive server cannot hold it the other one maybe possible with content move I am not sure

Ciao, Appu

On May 17, 2016, at 11:33 PM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

eLink : Re move documents to Archive system
Re move documents to Archive system Posted byJ, BharaniLathaOn 05/18/2016 12:33 AM

we have multiple versions of document in our CS10,so our aim is to move all older versions with metadata and hard copy of document to Archive Server 10.5 and delete the file from CS10 and live CS with only the latest version.So we need to fetch the CS document with its dataid and unique id(which we use) and check if this is present in Archive if present the add versions to it and move.
[To post a comment, use the normal reply function]
Topic: move documents to Archive system
Forum: Content Web Services Forum
Content Server: Knowledge Center

eLink User

My posting was made before I read your post again.Something about what you describe is the problems needs more clarity. I will explain hoping that it helps you.

I will say this LL as the Leading application to AS and a traditional EFS based system.

Let's say you are adding a Document and say you have only EFS configured at this time.Assume LL assigns 166825681 as the dataid. Internally in DVERSDATA a pointer is inserted and the PROVIDERDATA table has a row saying it is in EFS.

so this is how we find where a file really is in a LL system

select * from providerdata where providerid in(select providerid from dversdata where docid in (select dataid from dtree where dataid=166825681 ));

if you add a version to that file its dataid which is dtree(core).dataid does not change. LL maintains a 1 to many relation

What you are saying is

166825681 version 2 55 MB

166825681 version 2 50 MB

166825681 version 1 50 MB

You will maintain Version 1 and Version 2 in AS and DELETE Version 2 & Version 1. I don't think so unless you wrote the entire algorithms for retrieval.

Once livelink has "Purged" older versions it does not know how to source it from say an alternate provider like a EASP(AS).

Obviously if you have the Archive server SDK perhaps you can create code your self that maintains the relations.Anything is possible with custom coding and prudent design,but I sincerely do not think Content Move can be used to do what you want.You may want to ask the AS forum to see if Content Move can be used to maintain orphanned entries in LL.

If space is a concern then put a number for your versions so in my case if I put the versions to maintain as 1 ,then the next time a version is added LL will know that the user says maintain only Version 1 and it will add the new one as 2 and purge the version 1 and keep that rolling.This is considered a bad idea in a dms system because you always want to know what historically people have put in documents.

.....appu appnair appunair

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

On Wed, May 18, 2016 at 5:53 AM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Re Re move documents to Archive system Posted byeLinkOn 05/18/2016 06:53 AM

Metadata is database space and archive server cannot hold it the other one maybe possible with content move I am not sure

Ciao, Appu

On May 17, 2016, at 11:33 PM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Re move documents to Archive system Posted byJ, BharaniLathaOn 05/18/2016 12:33 AM

we have multiple versions of document in our CS10,so our aim is to move all older versions with metadata and hard copy of document to Archive Server 10.5 and delete the file from CS10 and live CS with only the latest version.So we need to fetch the CS document with its dataid and unique id(which we use) and check if this is present in Archive if present the add versions to it and move.
[To post a comment, use the normal reply function]
Topic: move documents to Archive system
Forum: Content Web Services Forum
Content Server: Knowledge Center
[To post a comment, use the normal reply function]
Topic: move documents to Archive system
Forum: Content Web Services Forum
Content Server: Knowledge Center

BharaniLatha_J

Thanks Sir.

Yes we have done a feasibilty study on content move already and it does not server our purpose.

The old version which we want to move to AS may /may not be retirved that frequently as we have latest version in CS still.So what I am thinking is will write a Oscript code to fetch all existing version except the last available version and move to AS leaving CS with latest version copy and hard delete the older versions copy from CS from EFS as well after moving to AS.

So need your inputs on we know fetch all version can be handled in oscript itself but uploading the document to AS should we use java and call CWS or is there any way to handle this completely from oscript using content server api's from oscript with out involving java or .net.

Thanks

eLink User

When you upload a document in CS and you have a rule that says put content in AS the code in the EASP module is used.If you put higher debugging you will get easp_dsh.log .dsh or dsclient is the standard client api we use to test archive server.So oScript technically knows how to use the Archive Link API.

Once you break the link of the older versions form livelink how will you get back the older versions from AS if there is a need?

.....appu appnair appunair

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

On Wed, May 18, 2016 at 11:21 AM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Re Re Re move documents to Archive system Posted byJ, BharaniLathaOn 05/18/2016 12:16 PM

Thanks Sir.Yes we have done a feasibilty study on content move already and it does not server our purpose.The old version which we want to move to AS may /may not be retirved that frequently as we have latest version in CS still.So what I am thinking is will write a Oscript code to fetch all existing version except the last available version and move to AS leaving CS with latest version copy and hard delete the older versions copy from CS from EFS as well after moving to AS.So need your inputs on we know fetch all version can be handled in oscript itself but uploading the document to AS should we use java and call CWS or is there any way to handle this completely from oscript using content server api's from oscript with out involving java or .net.Thanks
[To post a comment, use the normal reply function]Topic:move documents to Archive systemForum:Content Web Services ForumContent Server:Knowledge Center