SOAP Groups API with Web Services 2.0
This topic discusses Web Services 2.0. For information on Web Services 1.0, see
Web Services 1.0.
Overview
The Groups SOAP API allows FullAccess users to add or modify groups. Using Web Services enables you to manage user and group information on a large scale. User information and groups can be modified using two methods.
You can generate a skeleton input for each operation in the Groups WSDL, which contains the following operations:
For each operation, the following fields are always required in the header:
-
UsernameToken
- category: Security
- schemaLocation
For all SOAP APIs, the Failure Response Variables are exceptionCode
and exceptionMessage
.
getGroups |
Allows you to obtain group information. |
- category
- schemaLocation
- variable_name
|
status
groups
|
modifyGroups |
Allows you to create a new group and add users to the group. You can also add or remove user(s) to/from an existing group(s). |
- category
- schemaLocation
- variable_name
|
status
|
Administration
- Click Admin to go to the Admin Home Page.
-
Click Web Services in the Integration Platform section.
The Web Services Test page opens.
- Confirm that the Web Service Version is 2.0.
- Click the Groups tab.
- Select an API from the drop-down.
-
Click Generate Input to retrieve the skeleton.
For more information on the body of the Groups Web Service, and for code examples, see the topic SOAP Groups API with Web Services 1.0. With the exception of the header, the Web Services 1.0 code examples are valid in Web Services 2.0.
For each API, the body of the SOAP XML is the same as it was for Web Services 1.0. This is the information contained between the <soapenv:Body> and </soapenv:Body> tags.
The header, contained between the <soapenv:Header> and </soapenv:Header> header, has changed with Web Services 2.0.
No change |
<soapenv:Header> |
<soapenv:Header> |
New tags |
|
<wsse:Security xmlns:wsse= "http://docs.oasis-open.org/wss/2004/ 01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
|
New user information replaces sessionId |
<bm:userInfo . . . >
<bm:sessionId>
. . . . . </bm:sessionId>
</bm:userInfo>
|
<wsse:UsernameToken wsu:Id="UsernameToken-2">
<wsse:Username/><wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText"/>
</wsse:UsernameToken>
|
This is now in the URL, with the unique end point specified. |
<bm:category xmlns:bm="urn:soap.bigmachines.com"> Commerce </bm:category> |
Now reflected in the SOAP Server URL field. |
No longer needed |
<bm:xsdInfo
. . . . .
</bm:xsdInfo>
|
|
Ending the new authentication |
|
</wsse:Security>
|
No change |
</soapenv:Header> |
</soapenv:Header> |
Related Topics
See Also