Table of Contents

Search

  1. Preface
  2. Informatica Intelligent Cloud Services REST API
  3. Platform REST API version 2 resources
  4. Platform REST API version 3 resources
  5. Data Integration REST API
  6. File Ingestion and Replication REST API
  7. Streaming Ingestion and Replication REST API
  8. Model Serve REST API
  9. RunAJob utility
  10. ParamSetCli utility
  11. REST API codes
  12. REST API resource quick references

REST API Reference

REST API Reference

fetchState

fetchState

Use this resource with the loadState resource to synchronize object states across organizations.
Use the fetchState resource to create an object states package that you upload into other organizations using the loadState resource.
Creating the object states package includes a series of requests and responses, similar to the process of exporting assets. The end result is a ZIP file that contains the object states that you want to load to other organizations. To create the object states package, you perform the following tasks:
  1. Send a lookup GET request to receive the object IDs for the object states you want to synchronize.
    Informatica Intelligent Cloud Services
    returns the object IDs.
    See Lookup.
  2. Send a fetchState POST request to start the job, using the object IDs returned in the lookup response.
    Informatica Intelligent Cloud Services
    returns the job ID for the fetchState job.
  3. Send a fetchState GET request to get the status of the job, using the fetchState job ID for the object state package.
    Informatica Intelligent Cloud Services
    returns the job ID and status. The response can also include a list of the object IDs and associated object states that are in the package.
  4. Send a fetchState GET request to download the package.
    Informatica Intelligent Cloud Services
    returns the package in a ZIP file.
The object states package contains state information in a JSON file for each object. Each file name uses the following format:
<task name>.<task type>.runtime.json
For example, a file with the name of
mt_MappingTask106.MTT.runtime.json
might contain the following data:
{ "taskRun" : { "lastRuntime" : "2018-12-13T09:05:17.000Z" }, "taskStateVariables" : [ { "category" : "TX_VARIABLE", "name" : "Sequence", "value" : "26908" } ] }
You can change the following attributes in an object state file if required:
  • lastRuntime in the taskRun object
  • value in the taskStateVariables object (for mapping tasks only)
Other changes to the files in the package can cause unexpected behavior or errors.

0 COMMENTS

We’d like to hear from you!