Page History

Introduction

What is the History Viewer?

The History Viewer is installed on the server alongside the JobScheduler providing the Background Service. It accesses the Background Service database tables containing the file transfer history information and presents this information in a table in the History Viewer interface. This interface comes with a range of filters that can be used to restrict the information being shown to, for example, transfers from a particular source or with a particular status, that have taken place within a given time period or were carried out for a particular mandator.

Use Cases

The History Viewer is designed to meet the following use cases:

• As a

  tool for

  Support

  Teams

  Team Tool

  • The automatic screen update function and clear indicator of file transfer operation end status means that Support Teams can be informed of the status of completed operations at a glance and initiate action accordingly.
  • The high configurability of the History Viewer allows flexible configuration of the operations shown - for example to follow transfers for particular Mandators or file transfer targets.
  • Note that the History Viewer currently does not show file transfer operations that do not start because, for example authentication at the source server is not successful, or because no files for transfer are found, even if these scenarios should cause an error in the JADE client operation. This feature is planned for the

• As a Compliance Reporting Tool

  • Access records for particular file transfer operations
  • Provide information jobs that have been run for a particular mandator

• As a File Transfer Information Retrieval / Debugging Tool

  • Retrieval of detailed information about a particular file transfer

What is the History Viewer?

Note

The history viewer currently shows information drawn from The History Viewer is installed on the server alongside the JobScheduler providing the Background Service. It accesses the Background Service database tables containing the file transfer history information and presents this information in a table in the History Viewer interface. This interface comes with a range of filters that can be used to restrict the information being shown to. If a file transfer operation does not start, because, for example, transfers from a particular source or with a particular status, that have taken place within a given time period or were carried out for a particular mandatorconnection to the source server could not be made or because no file were found, then no file transfer information will be recorded in the history.

The History Viewer Interface

...