Use Web Services to Manage Groups › Create Groups Programmatically › Basic Operations in REST Web Services

Basic Operations in REST Web Services

The REST specification leaves room for some flexibility. As a result, REST web services can use basic HTTP syntax to perform different tasks. All of the CA Performance Center REST web services require user and password authorization in the HTTP request header. You can use the same credentials that you use to log in from the CA Performance Center user interface.

In this implementation, the basic REST commands are used as follows:

• GET - Log in or retrieve information from a server database. Only requires a browser session.
• POST - Create an object. Often requires XML input to supply parameters.
• PUT - Edit an existing object. Occasionally also used to create an object. Usually does not require XML input to supply parameters.
• DELETE - Delete an existing object.

Here is an example of a simple PUT operation that updates the description parameter of a tenant:

http://CA Performance Center Server IP Address:8181/pc
/center/webservice/tenants/tenantName/tenantName/tenantDescription
/{NewDescription}

You would substitute the desired values inside the braces { } for the required parameters:

tenantName

The name of the tenant that you want to edit.

tenantDescription

The new description to identify this tenant.

Here is an example of a simple GET operation that returns a list of the supported ID names that can be used to specify a group using the groups web service:

http://CA Performance Center Server IP Address:8181/pc
/center/webservice/groups/idNames

The following XML is returned:

<?xml version="1.0" encoding="UTF-8"?>

<idNames>

  <idName value="groupItemId" />

  <idName value="groupPath" />

</idNames>

HTTP requests always return a response and a status code, even when successful. The response text is either the expected result or an error message to indicate a problem. The status code is 200 for a successful response, or a numeric error indicator. The following HTTP response code ranges are used:

• 200 - Command status is 'OK'.
• 400 - A user error has occurred. Errors in this range indicate a problem with the input text (400) or the user credentials (403) and can usually be easily corrected.
• 500 - A system error occurred. Errors in this range typically indicate a system fault. Such errors can require assistance from CA Technical Support to resolve them.

For more information about HTTP status codes, see the following IETF website:

http://www.ietf.org/rfc/rfc2616.txt