This topic provides alphabetized reference pages for deprecated Web services operations provided by Novell Teaming.
NOTE:Novell recommends that you do not use these Web services operations in new applications. Instead, use the operations documented in Section A.0, Web Services Operations. Novell continues to support the operations in this appendix for backward compatibility for applications written to interoperate with Teaming 1.0.3 or earlier.
The following are conventions used in this reference section:
|
What you see |
What it means |
|---|---|
|
Click the button. Click the link. |
Items that are clickable on the page, programming variables, or syntax parameters are presented in font. |
|
Blog summary - Provides a.... Note: Remember that.... |
Defined terms in a list, note headers, section headers on a reference page, and list items on a reference page are presented in bold font. |
|
Type status, then press Enter. Open the ManagerGuide.pdf file. Use the open_db routine with its lock parameter. |
Text that you must type, file names, commands, command options, routines, Web services messages, and parameters are presented in Courier font when occurring in a body of text. |
|
[page] |
Optional syntax parameters are enclosed in brackets ([ ]). |
|
..., paramSyntax1 | paramSyntax2,... |
Required parameters that accept two or more optional syntaxes are separated by the vertical-line character. |
|
(V1—V1.0.3) |
The versions of Teaming that support the Web services operation (“all versions between Version 1.0 through Version 1.0.3”) |
NOTE:All examples in this reference section use Apache Axis run-time library methods that specify Web service operations and their argument lists. If you are not using Apache Axis, map the Apache methods to those you are using to implement your Web service calls.
The search operation is under development and subject to change or deletion at any time. Do not use this operation in your client applications.
Web service operations contained in this reference section are used by this Windows based client: /ssf/samples/wsclient/facade-client.bat. With the exception of uploadCalendarEntries, use the same parameters for the batch-file command that you use for the corresponding Web service message.
The following table maps the facade-client.bat command name to its corresponding, linked Web services message, which is documented in this reference section:
|
facade-client.bat command |
Web services message |
|---|---|
|
addEntry |
|
|
addFolder |
|
|
addReply |
|
|
[none] |
|
|
indexBinder |
|
|
listDefinitions |
|
|
migrateBinder |
|
|
migrateEntry |
|
|
migrateReply |
|
|
migrateFile |
|
|
migrateFileStaged |
|
|
migrateWorkflow |
|
|
modifyEntry |
|
|
printAllPrincipals |
|
|
printDefinition |
|
|
printDefinitionConfig |
|
|
printFolderEntry |
|
|
printFolderEntries |
|
|
printPrincipal |
|
|
printTeamMembers |
|
|
printTeams |
|
|
printWorkspaceTree |
|
|
setDefinitions |
|
|
setFunctionMembership |
|
|
setFunctionMembershipInherited |
|
|
setOwner |
|
|
setTeamMembers |
|
|
synchronize |
|
|
uploadCalendar |
|
|
uploadFile |