This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

File Deployer configuration parameters

Starting with BMC Remedy AR System 9.1.04, 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

  1. Navigate to AR System Administration >  AR System Administration Console > System > General > Centralized Configuration
    The AR System Configuration Generic UI opens.
  2. Click the Component Name field and select the com.bmc.arysy.filedeployer option.
    The available components are displayed.
  3. Select a component instance.
    The AR System Configuration Generic UI fetches the available parameter information.
  4. Edit the listed parameters, as needed.
  5. 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.

ParameterDescription
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 valuearfiledeployer.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 value10080 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


Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Tony Worthington

    The Troubleshooting link here is broken.

    Feb 16, 2018 06:25
    1. Anagha Deshpande

      Hello Tony,

      I have fixed the link.

      Regards,

      Anagha

      Feb 18, 2018 09:22
      1. Piotr Sadowski

        Hi @Anagha Deshpande, link still does not work, when I try open it I receive error message: "Forbidden

        Sorry, an error occured.

        Error code - 403 (Forbidden)"

        Best regards, Piotr

        Feb 19, 2018 03:08
        1. Anagha Deshpande

          Hello Piotr,

          Please check the link. It is now working.

          Regards,

          Anagha

          Feb 19, 2018 09:32
          1. Piotr Sadowski

            Hi Anagha, now it is working fine. Thank you :)

            Feb 20, 2018 03:04