Converting LAPI code to CS Web service calls
hi all,
when converting LAPI code to CS web service calls, it seems like there are lot less API from the web service. The following is an example of creating a sub folder with LAPI:
//create session and document object.
var LLs = New LLSession(…);
var DOCUMENTS = New LAPI_DOCUMENTS(LLs);
var LL_ATTR = New LAPI_ATTRIBUTES(LLs);
//find the parent folder category list, objCategoryID is the folder ID
int status = DOCUMENTS.ListObjectCategoryIDs(objCategoryID, catIDList);
//get the categoryVersion that matched the given categoryID:catID
status = DOCUMENTS.GetObjectAttributesEx(objCategoryID, catID, categoryVersion);
//create the folder, set VolumeID to -2000, passing some custom attribute info in createInfo object.
status = DOCUMENTS.CreateObjectEx(VolumeID, dataID, LAPI_DOCUMENTS.OBJECTTYPE, LAPI_DOCUMENTS.FOLDERSUBTYPE, folderName, createInfo, objectInfo);
what's the equivalent API from CS Web service? the closet method from DocumentManagement API is CreateFolder(OTAuthentication otauth, string parentFolder, string folderName, string comments, Metadata metadata)
Metadata can contain key/value list, think that's for the custom attributes.
any pointer to any guide on converting LAPI to CS web service calls are appreciated.
thx
Comments
-
Hi,
I also need a solution for this.
0
Categories
- All Categories
- 108 Developer Announcements
- 49 Articles
- 100 General Questions
- 122 IM Services
- 40 OpenText Hackathon
- 31 Developer Tools
- 20.6K Analytics
- 4.1K AppWorks
- 8.9K Extended ECM
- 897 Cloud Fax and Notifications
- 77 Digital Asset Management
- 9.3K Documentum
- 29 eDOCS
- 120 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management