File Deployer configuration parameters
You can create and deploy a custom binary payload across environments. The File Deployer process manages the custom binary payload operations. Administrators set the File Deployer configuration parameters via the AR System Configuration Generic UI.
To set the File Deployer configuration parameters
- Navigate to AR System Administration > AR System Administration Console > System > General > Centralized Configuration
The AR System Configuration Generic UI opens. - Click the Component Name field and select the com.bmc.arysys.filedeployer option.
The available components are displayed. - Select a component instance.
The AR System Configuration Generic UI fetches the available parameter information. - Edit the listed parameters, as needed.
- Click Apply and then Close.
List of File Deployer configuration parameters
The following table lists the File Deployer configuration parameters. You can edit the values from AR System Configuration Generic UI. You need not restart the AR Server after editing the values.
Parameter | Description |
---|---|
check-external-process-threshold | Number of times the File Deployer process checks the status after deploying the new files. This parameter applies only when the process runs as an external process and is started or stopped by the armonitor for the binary payload deployment purpose. Default value—18 Minimum value—3 Maximum value—30 |
check-external-process-polling-interval | Sleep interval (in seconds) between two retries when the File Deployer process checks the status after deploying the new files. This parameter applies only when the process runs as an external process and is started or stopped by the armonitor for the binary payload deployment purpose. Default value—10 seconds Minimum value—10 seconds Maximum value—60 seconds |
check-process-polling-interval | Sleep interval (in seconds) between the two retries when the File Deployer process checks the status after deploying the new files. This parameter applies only when the process runs as a child process of armonitor. Default value—10 seconds Minimum value—10 seconds Maximum value—30 seconds |
check-process-threshold | Number of times the File Deployer process checks the status after deploying the new files. This parameter applies when the process runs as a child process of armonitor. Default value—3 Minimum value—3 Maximum value—10 |
execute-timeout | Number of minutes the File Deployer process waits for a script or command to run before considering it as timed out. Default value—30 minutes Minimum value—30 minutes Maximum value—24 hours |
log-file-name | Path for the given log file name. When you provide the relative path, the log file is created in the <AR_INSTALL_DIR>\db directory for the ARServer File Deployer process. For other components, such as BMC Remedy Mid Tier or BMC Remedy Smart Reporting, the log file is created in the <FILE_DEPLOYER_INSTALL_DIR>\Logs directory. Default value—arfiledeployer.log |
log-level | Logging level for the selected component. Default value—INFO Allowed values—ALL, DEBUG, ERROR, FATAL, INFO, OFF, TRACE, WARN |
max-log-file-size | Maximum size (in megabytes) for the selected component. Default value—10 Minimum value—1 Maximum value—500 |
max-no-log-backup | Maximum number of backups maintained for the File Deployer log. Default value—10 Minimum value—1 Maximum value—20 |
max-query-size | Maximum number of entries the File Deployer process reads at a time from the AR System Single Point Payload Deployment form. Default value—10 Minimum value—0 Maximum value—Maximum integer value |
polling-interval | Time (in minutes) when the File Deployer should query the pending deployment requests. When there is no signal from the AR System server, the File Deployer process continues to check for new pending requests after the specified time. Default value—10 minutes Minimum value—1 minute Maximum value—10080 minutes (7 days) |
zip-read-buffer-size | Number of bytes the File Deployer process reads at a time from the zip file. Default value—1024 Minimum value—1024 Maximum value—4096 |
Related topics
Defining a custom binary payload
Configuring the File Deployer settings
Troubleshooting for Binary payload deployment
Comments
Log in or register to comment.