Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Integration
  • All Products

Table of Contents

Search

  1. Preface
  2. Taskflows and linear taskflows
  3. Taskflows
  4. Linear taskflows

Taskflows

Taskflows

Back Next

Running a taskflow as an API

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.
  1. Navigate to the taskflow that you published as a service.
  2. 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 image displays the Properties Detail dialog box with the service URL and the SOAP service URL.
    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.
  3. 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.
  4. 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:
      <taskflow name>-<run ID>
    • 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.
0 COMMENTS
We’d like to hear from you!