How to link existing archived Document to Content Server

Dear all,

I’m a bit disappointed and honestly surprised by what seems to be a simple use case.

I would like to create a node through the API in Content Server and link it to a document that is already physically stored in Archive Server.

At first glance, this sounds trivial, but in practice it does not seem to be.

The standard method to create a node via API is:

cs.exe/api/v2/nodes

With this endpoint, I can define the node properties I need, but I cannot find any way to indicate that the file already exists in Archive Server and should be linked from there instead of being uploaded again.

On top of that, when I try to pass category values as described in the documentation, the values are simply not stored, and the physical file property is mandatory…

So I am wondering whether I am missing something.

Is this actually possible through the standard REST API, or do we absolutely need to use a WebReport, OScript, or another custom approach for this kind of requirement?

Has anyone successfully implemented this and, if so, would you have a working example to share?

Thanks in advance for your help.

Best regards,
Cédric

Find more posts tagged with

API

xECM

Archive and Document Access

Content Storage Service

Archiving

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

Greg Griffiths

If the document already exists in OTAS, is this document loaded into just OTAS or OTAS and OTCS ? if its already available in OTCS then you are better using the copy rather than create function. If only in a separate OTAS then you will need to download it from OTAS using the OTAS APIs and then upload it into OTCS using the relevant APIs, there is no out of the box API for pointing a dummy file upload to a location in OTAS, this would need development with OScript

Greg Griffiths

depends on the settings in OTAS etc, it may use a pointer to the original etc.

If you wanted something to do a "create me a stub in OTCS that is attached to this doc in OTAS" then that is custom OScript Dev given the low level work required.

All comments

Greg Griffiths

CedricLaurent

Hi Greg,

It is only in OTAS, so my assumptions were right :)

That means also if I download it from OTAS and reupload it in OTCS, it will be stored twice, right ?

Thanks for your help !
Cédric

Greg Griffiths

depends on the settings in OTAS etc, it may use a pointer to the original etc.

If you wanted something to do a "create me a stub in OTCS that is attached to this doc in OTAS" then that is custom OScript Dev given the low level work required.

CedricLaurent

I am more familiar using REST services, so now I know I should dive into OScript haha :-)

Many thanks for confirmation,
Cédric

appuq

See if someone will give you a hand in doing this using RMlink, which is similar to what you want. Leading App(SAP) store in OTAS, so the document is visible using the SAP Archive Link.OT does not get too much benefit by doing this, so they created a program called RMLink, which was exposing the existing AL in OTCS, whereby people could see the Document in OTCS as well as SAP and OTAS.OTAS basically comes in a DSH client or the older DSAdmin client. This was a precursor to OT Extended ECM.OTCS already has the necessary dsh built into its code nowadays.RMlink itself is now deprecated, but the idea remains. That way you dont have to re-upload the OTAS document.

Hans_Stoop

There is REST call for doing this, because opentext is using it themselves with their xECM SAP integration.

Unfortunately this call is not publicly available.