Configuring the RA Informatica Agent Solution Agent
On the General page of the RA Informatica Agent solution Agent object, you specify the path to the pmrep and pmcmd directory and several general Agent settings.
Install an RA Informatica Agent solution Agent object in your Automation Engine. The RA Informatica Agent must reside in a location where the Informatica Client or Informatica Server is installed.
Specifying RA Informatica Agent Solution Agent Settings
The fields are described below. After editing these fields, you must stop and restart the Agent.
PRREP and PMCMD Directory
- Job Start Timeout (seconds)
- Job Status Polling Interval (seconds)
- Job Finish Status Check After Started (seconds)
- Temporary File Purge (days)
- Maximum Workflow Log Fetching Retries
- Disable Synchronized Workflow Job Launching
- Session Log File Transfer Option
- Always: Transfers log files for all Sessions in this Workflow.
- For Failed Sessions or Workflows: Covers two cases:
- If the Workflow fails, all the session logs are transferred, regardless of the individual session status.
- If the Workflow does not fail, only the log files for failed sessions are transfered.
For example, in the case that "Fail parent if this task fails" is enabled.
- Only for Failed Sessions: Transfers log files for failed Sessions in this Workflow regardless of the Workflow status.
- Never: Does not transfer log files for Sessions in this Workflow.
- Enable Child Job Tracking
- Child Job Status Update Interval
- Child Job Template
The path to the pmrep, pmcmd, and infacmd directory where the Agent is installed.
The number of seconds before you want RA Informatica Agent Jobs to timeout after they are started in the Automation Engine, if they have not been started by the Integration Service. Default value is 180.
The number of seconds between Job status updates. Default value is 20.
The number of seconds to hold before making a check to see whether the Job has finished. The reason you might want to set this to a value other than 0, is to free resources to prioritize any newly requested Jobs to start before making this status check. A value other than 0 would be beneficial if you have a lot of Jobs launched at the same time. If you need to use this setting, you would only set it to a few seconds. This setting will have a minimal effect on your RA Informatica Agent Jobs, because they take more than a few seconds to finish anyway. Default value is 0.
The number of days to keep temporary restart files in the log folder before deleting them.
In a busy system, sometimes the Workflow log is not immediately available for the RA Informatica Agent to fetch. This option allows you to specify the number of retries to get the Workflow log. The default value is 6.
If the Workflow log still cannot be fetched after the maximum specified retries, the Workflow Job will fail, even though the Workflow is running normally on the Informatica server. The reason for this is that the Workflow log is used to parse the status of individual Sessions/Tasks to generate the report and that is part of the Informatica Job run.
Make sure the Informatica server has enough resources to handle the number of concurrently running Workflows you need to run.
Asynchronous Workflow Job Launching
By default, this option is unchecked and Workflow Jobs are launched sequentially. This is to reduce the contention of the Job launching on the Informatica server for better overall Job performance. If this option is unchecked, the Agent will not synchronize the Job launch.
When there are a large number of concurrent Workflow runs or the Informatica server is heavily used, Jobs may run slower and Workflow log fetching may also be slower. In this case, you may want to specify fewer retries to fetch the Workflow log in the Maximum Workflow Log Fetching Retries field.
By default, Workflow Jobs are launched sequentially. This is to reduce the contention of the Job launching on the Informatica server for better overall Job performance. If this option is checked, the Agent will not synchronize the Job launch.
When there are a large number of concurrent Workflow runs or the Informatica server is heavily used, Jobs may run slower and Workflow log fetching may also be slower. In this case, you may want to specify fewer retries to fetch the Workflow log.
Determines the default behavior for when the RA Informatica Agent transfers Session logs for Workflow Jobs. Whether or not you transfer Session log files affects how long it takes for the Jobs to complete in the Automation Engine. The options are:
The option you select here can be overridden in individual Workflow Job definitions. For more information, see topic
When you check the Generate on error only box on the Rapid Automation/Integration Reports page (the title depends on the AWI version that is installed in your environment), the Session Log File Transfer Options settings ignored and no Session logs will be transferred.
Workflow log files are always transferred.
This field is available in the Automation Engine only and is only supported for v11.1 and above. It enables child Job tracking for all Informatica Workflows (default disabled). If you do not wish to track child Jobs of one or more particular Workflows, you can disabled it in their Job definition.
Since this function requires periodic child Job status update, it may have some impact on the performance.
This field determines the number of seconds you want to update the statuses of child Jobs.
Default: 30
The shorter interval you specify, the more impact it will have on performance.
For finished Workflow Jobs, remote statuses of ‘Execution Abort',' Execution Stopped' or ' Execution Failed' from RA Informatica Agent Session/Task will map to 'ENDED_NOT_OK' status in the Automation Engine. All other remote status will map to 'ENDED_OK'.
This field is available in the Child Job Tracking box in Applications Manager only. You use it to specify the default template Job for child tracking.
You can define as many templates as you choose and this template can be overridden in the Workflow Job definitions.