Setting up file system monitoring

Introduction

Many processes in SAP – especially batch processes – read from external filesystems. For example, you may have an external sales system in which sales orders are created. This external system exports new sales orders to a file which is then uploaded to SAP for the creation of sales order documents. It is obviously important that Testimony is able to capture these file accesses – and the files themselves – so that these processes can be played back.

File system monitoring configuration

In order for Testimony to be able to capture the files, we need to tell Testimony which filesystem directories to monitor for file access. When Testimony detects that a batch job or other process has accessed a file in the monitored directories, it will copy that file to its own directory. This copied file is later copied to the Central System for use in the playback.

*The method and directory locations for the file copy are configured during the installation of Testimony.

To add directories to the File System Monitoring configuration, go to Recording —> File System Monitoring, click on the Configuration tab, double-click on your source system and then click on Create.

Enter the information for your interfaces directories.

• If you have the same directory structure mounted on all application servers, then you can leave the Application Server field blank. This tells Testimony to monitor all application servers
• If you have only specific filenames that you want to monitor, then enter details in the Filename Mask field, otherwise, to monitor all files, leave this field to the default
• If you want Testimony to monitor all subdirectories of the main interfaces directory, then select the “Monitor all sub-directories of this directory also” checkbox
  

Click on the tick, and the monitored directory will appear in the Configured directories list.