Production readiness of 'Connected Workspace' object access through SOAP and/or REST APIs?

hi Kris,

Your question...

As for SOAP, I cannot seem to find where the 'Connected Workspace' builders would be exposed. I am looking for the equivalent of performing a POST to the resource /api/v2/forms/businessworkspaces/create?parent_id=...&type=848&wksp_type_id=...&template_id=..

SOAP libraries are usually given out by OT and in regular services, it exists on OTHOME\webservices and java and dot net versions, The config file of that webservice determines which livelink server and port it works with.in IIS installations one is led to believe that something mysteriously exposed on the livelink server accomplishes SOAP but that is not the case the proxies that developers download allows the client code to reach a Livelink server. As for what happens at the end of the SOAP call is completely written inside oscript if you run Sysreport lite if you are not a programmer you will see the NodeTypes registration. Nowadays OT bundles subtype 848 part of the old XECM/TW in core code.In XECM installs one takes the jar equivalent of proxies and puts them in a TC server and calls that ECMLINK services. For reasons unknown to me, it is not given out as WCF as in the dot net equivalent.Side Note: When we create a web service as taught in SDK class one actually creates the LLNode/Webnode registration pair(think 0,144,848 and such like) then we run certain scripts in Visual Studio to generate the dot net proxies, then we take that and run ant scripts to generate the jars .it is very confusing if you do not come like me from the dot net or java world but at the end of it you get those proxies...What I am trying to say is that the 848 has been represented in core oscript that is why you can call the REST endpoints.REST also will only work if the subtype is defined.

SOAP is easier to work with when you are working with workspaces as one does not need to actually figure out the category information in CS so for e.g to create a WKSPACE in soap one just says the external system id,objectid, and objecttype the metadata if needed is passed as name-value pairs, the receiving code makes a determination of understanding how to take those name values and map it into categories which is a setup activity in XECM.

Compared to that a REST Wkspace creation means the caller needs to present this information in true gory fashion of CS category implementations a small payload shown that creates a business workspace

api/v2/businessworkspaces shown in Jquery code as taken form postman

The smartUI has helpers that allow it to form a form payload and so on..

var form = new FormData();

form.append("body", "{\"template_id\":93403,\"name\":\"Workspace name is generated automatically.\",\"type\":848,\"parent_id\":92964,\"bo_type\":\"ASSET\",\"bo_type_id\":2,\"bo_type_name\":\"ExtSystemID - Asset\",\"description\":\"\",\"ext_system_id\":\"ExtSystemID\",\"ext_system_name\":\"ExtSystemID\",\"external_identity\":\"\",\"external_identity_type\":\"\",\"external_source\":\"\",\"ibo_workspace_id\":0,\"reference_type\":\"1\",\"mime_type\":\"Business Workspace\",\"size\":\"\",\"roles\":{\"categories\":{\"94284\":{\"94284_2\":\"\",\"94284_3\":\"\",\"94284_4\":\"\",\"94284_5\":\"\",\"94284_6\":\"\",\"94284_7\":\"\",\"94284_8\":\"\",\"94284_9\":\"\",\"94284_10\":\"\",\"94284_11\":\"\",\"94284_12\":\"\",\"94284_13\":\"\",\"94284_14\":\"\",\"94284_15\":\"\",\"94284_16\":\"\",\"94284_17\":\"\",\"94284_18\":\"\",\"94284_19\":\"\",\"94284_1\":{\"version_number\":1}}},\"classifications\":{\"create_id\":[92965],\"id\":[]}},\"source_parent_id\":92964}");

var settings = {

"url": "http:///otcs/cs.exe/api/v2/businessworkspaces",

"method": "POST",

"timeout": 0,

"headers": {

"otdsticket": "*OTDSSSO**"

},

"processData": false,

"mimeType": "multipart/form-data",

"contentType": false,

"data": form

};

$.ajax(settings).done(function (response) {

console.log(response);

});

Note the integrator/ programmer needs to know that 93403 is a template 94284 is a category the trailing 2 and 3s are its attributes

compared to its soap implementation is much more verbose....

Hope that clears where you find the soap libraries :)