Previous Topic: Enable Web Services for Individual TasksNext Topic: WSDL Generation


Client Application Development

The following steps are an overview of the client application development process for submitting remote web service requests to CA IdentityMinder.

Note: This overview assumes that your integrated development environment includes a third-party tool like Axis that generates proxies. While this approach automates some of the development, it is not required.

  1. Be sure that web services are enabled for the CA IdentityMinder environment and for each task that is to support remote requests.
  2. Generate the WSDL code by invoking the following URL:
    http://host:port/iam/im/TEWS6/environmentalias?wsdl
    

    For example:

    http://tewstest.ca.com:7001/iam/im/TEWS6/neteauto?wsdl
    

    Note: The URL is case-sensitive, and environmentalias is the protected alias of the CA IdentityMinder environment.

  3. In your integrated development environment (IDE), create the proxies based on the WSDL document generated in the preceding step.

    Proxies reflect the operations that your client can submit to CA IdentityMinder. Java proxies generated by third-party tools such as Apache Axis provide precise, self-documenting entry points and parameters.

  4. In your IDE, develop the client code that formulates and submits the remote requests, and process the responses. Typically, you develop this code using a third-party tool such as Apache Axis and Microsoft .NET.

    Develop whatever programming logic is required to process the SOAP requests and responses in compliance with your business requirements.

  5. At run time, the client application submits a CA IdentityMinder request through a generated proxy. The proxy transforms the request into a SOAP document that the Task Execution Web Service can understand, and then submits the request to the web service.
  6. CA IdentityMinder processes the request and returns a SOAP response to the client application.

The following diagram illustrates the development and run-time processes:

TEWS Development and runtime diagrams