Grouper client version
v1.4, v1.5, v1.6, v2.0 (server version) Endpoint
WSDL from server
WSDL from SVN
- If REST:
- Decide what format you want to send and receive data. grouper-ws supports XHTML, XML, and JSON, as well as query strings for input (in URL or message body)
- For example, in the URL you can set the content type you want back:
/grouper-ws/servicesRest/xml/v2_1_000/groups/aStem%3AaGroup/members/10021368 /grouper-ws/servicesRest/json/v2_1_000/groups/aStem%3AaGroup/members/10021368 /grouper-ws/servicesRest/xhtml/v2_1_000/groups/aStem%3AaGroup/members/10021368
- Or you can set the content type of the request and it will use that for the response
- There are many samples
- Understand versioning
Guidelines For Working With Grouper Web Services
- Test if server up
- There is a bug we are tracking with Axis, where if you skip String params, it will mix up the params. So, if you are passing a param to a web service, make sure you pass empty strings for all null params before the param
- Code clients with a mindset that the service might change in subtle ways. e.g. a result code might be added (check for success flag element, not success result code), an element might be added in a result object, another input element might be added to end of list, etc. Expect elements to be added in data. Note if you send the same version in the request, you will never get a response with a different structure. Grouper WS are backwards compatible.
- Make sure there is a property in the client of the URL and version for the service. The version of the service might change the URL (up to service deployer)...
- Note that Grouper WS can be setup with multiple instances. If you have database replication (even readonly), then you can setup Grouper WS application servers is multiple data centers, and you can have the Grouper Client can failover among the nodes if there are errors or timeouts.