cancel
Showing results for 
Search instead for 
Did you mean: 

uploadContent from CWS does not work when used in SAP

ixdse
Explorer
0 Kudos

uploadContent from CWS does not work when used in SAP

 

We are working with the CWS-Integration in SAP, that means we are calling content-webservices from SAP by so called “service-consumers”. These consumers were created in SAP with a  wizzard based on the  WSDL from ECM. We are using this integration for several scenarios of exchanging documents between SAP and ECM .

In case of sending documents from SAP to ECM we want to replace the createDocument-method (from DocumentService) with uploadDocument (from Content-Service)  because of better performance and memory-usage.

Unfortunately it looks like that “uploadDocument” cannot be used in SAP – after creating the service-consumer the method doesn’t have all parameters in SAP, as they are described in the CWS-documentation.

The documentation looks like this:

-----------------------------------------------------------------------------------------------------------

public String uploadContent(String contextID,

                   FileAtts fileAtts,

                   StreamBody contents)

Upload content and create the node. A contextID must first be obtained by calling the original Context web service (e.g. CreateDocumentContext() method).

Parameters:

contextID - The context ID of the original request, containing the meta-data for this content.

fileAtts - The description of the content uploaded.

contents - Contents to be uploaded.

-----------------------------------------------------------------------------------------------------------

 

 

 

 

 

 

 

 

 

 

 

In SAP there is only the parameter “contents”:

ixdse_0-1706789378904.png

 

“contextId” and “fileAtts” are missing, which are necessary for specifying things like filename and storage-location – without these the method isn’t usable for us.

 

Anyone who is using a similar scenario and has an idea about a possible solution?

 

Thanks!

Accepted Solutions (0)

Answers (0)