Task Execution Web Service › Remote Task Requests › How a Remote Request Is Processed

How a Remote Request Is Processed

In this example, when a client application submits a ViewUserQuery request to the Task Execution Web Service, the following actions occur:

1. The client application gathers the required information. With ViewUserQuery, the required information consists of the following:
   • The task tag
   • The Identity Manager environment where the task is being submitted
   • The unique identifier of the administrator who is submitting the task
   • An identifier (such as a name or unique identifier) of the user whose profile information is being requested

     This information can come from any source, for example, from user-supplied data on a custom screen, from a static configuration file-driven application, or from a live data feed from some external source.

2. The application formats the SOAP request according to the XML element ViewUserQuery in the WSDL definition.
3. The application sends the XML document to the Task Execution Web Service as an HTTP POST request.
4. When the Task Execution Web Service receives the request, it instructs CA Identity Manager to execute the operation and returns the status and profile information in a SOAP response.
5. Depending on the outcome of the request, the application processes the result (for example, displays the result in a custom UI) or takes an appropriate action based on any error information included in the result.