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. Mass Ingestion Files REST API
  7. Mass Ingestion Streaming 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

Job status

Job status

Specify the frequency at which the
RunAJob utility
polls for status in the
restenv.properties
file.
You can use the following parameters:
Parameter
Description
ACTIVITYMONITORWAIT
The amount of time the utility waits before retrying if an internal exception occurs, such as a login failure or network problem.
Default is 5000 milliseconds.
TOTALWAIT
The maximum amount of time the utility waits for a job to complete before polling the activity monitor and activity log again for status.
Default is 5000 milliseconds.
RETRYCOUNT
The number of times the utility polls for status. This parameter is used for polling the activity monitor and activity log for job status and for internal exceptions such as login failure or network problems.
Default is 6.
Informatica Intelligent Cloud Services
adds 10 seconds between each API call to prevent server issues.
When configuring the
restenv.properties
file for polling job status, consider the values you set for TOTALWAIT in conjunction with RETRYCOUNT, keeping in mind the amount of time you expect a job to run.
For example, if you expect a job to run for approximately 25 minutes, you might want to set the parameters as follows:
TOTALWAIT=60000 RETRYCOUNT=30
With these settings, the utility polls for the job status every 60 seconds up to 30 times with 10 seconds between each retry, which totals 35 minutes. If the job executes more than 35 minutes, the command will exit with return code 6 (which means the job is running) and the job will continue to run in
Informatica Intelligent Cloud Services
.
When configuring the
restenv.properties
file for internal exceptions, consider the values you set for ACTIVITYMONITORLOG in conjunction with RETRYCOUNT.
For example, you might set these parameters as follows:
ACTIVITYMONITORWAIT=5000 RETRYCOUNT=30
With these settings, if a user login fails, the utility retries the login every 5 seconds up to 30 times.

0 COMMENTS

We’d like to hear from you!