Notes for Testing Job Actions

Note the following as you develop Job actions:

  • Use the Reflection Gateway Administrator and Reflection Hub server.log for troubleshooting. See Job Troubleshooting for additional troubleshooting help.

  • You can use the Run Now button regardless of State (Enabled or Disabled). This enables you to ensure that the Job actions perform as expected before setting up the scan interval and enabling the Job.

  • A Run Now test won’t trigger Job actions if the scan directory contents have not changed since your last test. For testing repeatedly from the same directory, you can use the following commands to update the timestamp on all files in a directory:

    On UNIX, from a terminal window:

    touch *

    On Windows, from a command window

    copy *.* +,,

  • Use cmd /c before DOS commands to run on a Windows server. The /c switch specifies that cmd should exit after the specified command is carried out. For example

    cmd /c echo $FILENAME$ >> filelist.txt

  • Job actions configured using Execute Command run on the specified server as a remote SSH command. The command is executed using the user account specified for the UserID of that server. This user must have access to all directories required by the command. When $RELATIVE_FILE_NAME$ or $FILENAME$ are used with no preceding path information, output is directed to the terminal login directory for that user. For more information see Set Up Directory Access on your SFTP Servers.

  • Job actions configured using Transfer File use the SFTP directory access for the UserID for the specified server. When $RELATIVE_FILE_NAME$ or $FILENAME$ are used with no preceding path, output is directed to the SFTP login directory for that user. For more information see Set Up Directory Access on your SFTP Servers.

  • If you modify settings on an SFTP Server that affect SFTP directory access, you may not see the effects of your changes when you rerun the Job. This is because the Hub maintains and reuses existing connections to SFTP servers for up to 3 minutes of inactivity. (This improves performance because a typical scan requires multiple connections to the scanned server. It also helps improve the performance of Job actions that transfer multiple files.) To ensure that your Job action reflects changes made to the SFTP server configuration, either restart the Reflection Hub service or wait at least 3 minutes after all active scans and Job actions are complete.

  • The Transfer Site base directory specified in the SFTP server definition is used for Transfer Sites only. It does not affect the output locations for Job actions.

  • The Actions tab in Gateway Administrator is used for configuring Post Transfer Actions only. These actions can be associated with Transfer Sites and run after successful uploads from a transfer client. They are not associated with Jobs. Job actions are configured using the Transfer File and Execute Command dialog boxes, which are accessible from the Jobs tab.