You are here

README.txt in Web Service Clients 6.2

Clients for Drupal Services
===========================

This module contains client connection types for connecting to Services module
on Drupal (http://drupal.org/project/services).

The module allows for a client type for each version of Services, though
not all are done yet:
  Services 7.x-3.x on Drupal 7: TODO
  Services 6.x-3.x on Drupal 6: TODO
  Services 6.x-2.x on Drupal 6: TODO
  Services 5.x-0.92 on Drupal 5: working

Each different type is simply a subclass of the main Drupal Client class.

Setting up a client
--------------------

At admin/settings/clients, choose the type of connection you want to create.
The Drupal-specific options are as follows:

- Domain, Service key: These should match the key in the Services settings on
  the remote site.
  Note that the Domain property is actually an arbitrary string more akin to a
  username. You can set it to anything as long as it matches
- Service username, password: the details for a Drupal user on the remote site.
- Services, Views: these are obsolete and may be ignored.

It's a very good idea to go to the test page for your connection and try the
various actions such as connecting, logging in, retrieving a node. These show
you exactly what is returned from the remote server.

Setting up Services
------------------

Services 5.x-0.92 on Drupal 5

  - install:
    - services

  - enable:
    - services
    - xmlrpc server
    - system service
    - uprpc import source
    - uprpc import services
    - user service
    - user get service
    - node service (if required)
    - taxonomy service (ditto)
  - at admin/build/services, set up services:
    - create an API key for your Client site to use.
      - domain: the same string as for the client connection settings.
    - settings:
      - use keys: TRUE
      - token expiry: you may need to set this to a large number if you need to
        run many operations.
      - use sessid: TRUE
  - create a role for your webservice
  - create a user to access services, with this role.
  - add permissions for the anonymous role:
    - 'access services'
  - add permissions for the webservice role:
    - 'access services'
    - 'load raw node data'
    - 'load raw user data'
    - 'run content count queries'
    - 'run import flagging queries'

  Be aware that with these permissions, the webservice user can access data on
  your nodes such as hidden fields.






File

connections/clients_drupal/README.txt
View source
  1. Clients for Drupal Services
  2. ===========================
  3. This module contains client connection types for connecting to Services module
  4. on Drupal (http://drupal.org/project/services).
  5. The module allows for a client type for each version of Services, though
  6. not all are done yet:
  7. Services 7.x-3.x on Drupal 7: TODO
  8. Services 6.x-3.x on Drupal 6: TODO
  9. Services 6.x-2.x on Drupal 6: TODO
  10. Services 5.x-0.92 on Drupal 5: working
  11. Each different type is simply a subclass of the main Drupal Client class.
  12. Setting up a client
  13. --------------------
  14. At admin/settings/clients, choose the type of connection you want to create.
  15. The Drupal-specific options are as follows:
  16. - Domain, Service key: These should match the key in the Services settings on
  17. the remote site.
  18. Note that the Domain property is actually an arbitrary string more akin to a
  19. username. You can set it to anything as long as it matches
  20. - Service username, password: the details for a Drupal user on the remote site.
  21. - Services, Views: these are obsolete and may be ignored.
  22. It's a very good idea to go to the test page for your connection and try the
  23. various actions such as connecting, logging in, retrieving a node. These show
  24. you exactly what is returned from the remote server.
  25. Setting up Services
  26. ------------------
  27. Services 5.x-0.92 on Drupal 5
  28. - install:
  29. - services
  30. - enable:
  31. - services
  32. - xmlrpc server
  33. - system service
  34. - uprpc import source
  35. - uprpc import services
  36. - user service
  37. - user get service
  38. - node service (if required)
  39. - taxonomy service (ditto)
  40. - at admin/build/services, set up services:
  41. - create an API key for your Client site to use.
  42. - domain: the same string as for the client connection settings.
  43. - settings:
  44. - use keys: TRUE
  45. - token expiry: you may need to set this to a large number if you need to
  46. run many operations.
  47. - use sessid: TRUE
  48. - create a role for your webservice
  49. - create a user to access services, with this role.
  50. - add permissions for the anonymous role:
  51. - 'access services'
  52. - add permissions for the webservice role:
  53. - 'access services'
  54. - 'load raw node data'
  55. - 'load raw user data'
  56. - 'run content count queries'
  57. - 'run import flagging queries'
  58. Be aware that with these permissions, the webservice user can access data on
  59. your nodes such as hidden fields.