What is the internal difference between SOAP docMan.createDocument() and rest api api/v1/nodes

marimuthusundaraj · 2021-01-12T19:39:19+00:00

There was an error rendering this rich post.

Recently we have used cws soap api method for document creation using Java language.

docMan.createDocument() without metadata is working fine but, with metadata it is not working in our dev content server. But, same docMan.createDocument() with metadata is working fine in our client content server along with client's trigger setup too.

Both our Content Server and client's Content Server versions are same 16.2.11. Still we analyzing the issue from our end with SOAP api.

Meantime, we have created new code with Rest api implementations too. This Rest API code is working fine in our environment as well as client environment in most of the places. But, rest api code is failing in client environment for only one folder which has trigger configuration.

It seems trigger is moving the document immediately from that folder using trigger "Add Version" and Move to trigger events once the document is added/created in that parent folder. Trigger is throwing error as particular Category Attribute xxxxx is missing while doing the move trigger event.

My question here is, how both api are working internally with document creation along with category metadata and what is the difference between docMan.createDocument() and api/v1/nodes endpoint?

Do we have any other alternate or equivalent rest api endpoint for docMan.createDocument() SOAP api method? Because this SOAP method's createDocument with metadata is working fine in client environment with their trigger events.

SOAP api createDocument() with metadata is not working with our environment and as we have Rest API based implementation on hand, we are planning to stick with Rest api implementation instead of CWS SOAP.

So, we need alternative or equivalent endpoint for docMan.createDocument() soap api method. Any suggestion please?

Find more posts tagged with

Comments

Pramod Mohandas

Consider SOAP Web Services and the REST API as two doors to the same house. The core logic and codebase will essentially be one and the same irrespective of the integration path that you choose.

With regard to the differences between two Content Server instances that you had earlier highlighted, the only reason that I can think of is the difference in the level of patches that are present on either of these environments. With that in mind, do verify if both these instances are patched to the latest update for Content Server 16.2.11.

Though I cannot comment much on the trigger configuration that you have in place, what I would like to suggest is to first get the SOAP web services to work on both these environments because they should.

If the triggers are being fired earlier that it is supposed to, which seems to be your issue, think of revising your code logic into something that run on a scheduled basis. This approach will give you sufficient time for the document to be uploaded with its metadata before you apply your business logic.

Appu Nair

One other aspect that @"Ferdinand Prantl" said a while back is when you add something in Rest there is no extra code that Soap or Oscript things look at especially a flag that specifies should metadata be inherited... it is possible that the create node call back fires first and only later is the add version firing in that case if the create node fires and the trigger code is looking for categories it may not see that . I don’t know if the create node is happening with metadata . Another option is to use a simple folder like a interchange folder , use rest to create document with metadata then on success move it to the place where the folder with the trigger exists ...