Taskflows

Back Next

Running a taskflow as an API

After you publish a taskflow as a service, you can run the taskflow as an API or schedule the taskflow. You can use the endpoint URLs to run the taskflow as an API, and dynamically provide input parameters for the tasks that the taskflow contains and perform orchestration.

Navigate to the taskflow that you published as a service.

From the

Actions

menu, select

Properties Detail

The

Properties Detail

dialog box appears displaying the service URL and the SOAP service URL as shown in the following image:

The service URL uses the following format:

<Informatica Intelligent Cloud Services URL>/active-bpel/rt/<API_name>

The SOAP service URL uses the following format:

<Informatica Intelligent Cloud Services URL>/active-bpel/soap/<API_name>

You can also view the associated Swagger file and WSDL file.

To run the taskflow, perform one of the following steps based on the type of client that you want to use:

If you use a REST client, use the service URL and the API definition available in the Swagger file to send a request through the REST client.

If you use a SOAP client, use the SOAP service URL and the API definition available in the WSDL file to send a request through the SOAP client.

You can pass inputs using the service URL through a browser or a third-party tool. For more information, see Passing inputs through a browser or Passing inputs through a REST client.

You receive the taskflow run ID as the response.

To monitor the taskflow with the run ID, perform one of the following steps:

Use the run ID to monitor the taskflow run in the

My Jobs

page. The instance name uses the following format:

Use the status resource to query the status of the taskflow based on the run ID. For more information about using the status resource, see Monitoring taskflow status with the status resource.

Taskflows

Passing inputs through a browser

Passing inputs through a REST client

Resume a suspended taskflow