Your browser does not allow this site to store cookies and other data. Some functionality on this site may not work without them. See Privacy Policy for details on how we would use cookies.

Tectia

Collecting Data from Distributed Environment

This use case shows a little more complicated scenario, and requires also working connections to remote hosts where you have valid user accounts.

Check if suitable connection profiles have been created during Tectia MFT Events installation. They can be viewed in Tectia MFT Events GUI via Tools - Tectia Connections. If no Connection profiles exist, create them according to instructions in Chapter Configuring Connections to Servers in Tectia MFT Events Administrator Manual.

This use case depicts an environment where data is collected from source hosts first to a regional office and then transferred further to a central datacenter over the Internet. In evaluation phase, select two remote hosts that have Tectia Server running, and prepare to open a connection to third (external) server over public network. Also the external server needs Tectia Server or another SFTP server. Tectia MFT Events operates between these three servers on a separate host (Regional Office Server in the example).

Collecting data from distributed environment with Tectia MFT Events

Figure 4.5. Collecting data from distributed environment with Tectia MFT Events

The scheduled file transfer operation is configured in the Tectia MFT Events configuration on the Regional Office Server. The server administrators can view the progress and success of the operations on the Tectia MFT Events administration interface, and Tectia MFT Events sends them notifications about the event results by email.

Tectia MFT Events on the Regional Office Server triggers the file transfer every 10 minutes and executes the following steps:

  1. Pulls transaction files from each source host to a backup folder on the Regional Office Server.

  2. Transfers them to the Datacenter Server (for example, at the corporate headquarters).

  3. Deletes the original source files from the source hosts after the transfer to the datacenter has succeeded.

  4. Sends notification email to one operator when all steps have been completed successfully, and to an other if the event ends in failure.

The previous step must always be completed successfully before proceeding to the next step. If any of the steps fail, Tectia MFT Events sends a notification email to the operator.

Steps 1 and 2 can be configured with a single file transfer action in the Tectia MFT Events administration interface.

Configuration in Tectia MFT Events administration interface

Figure 4.6. Configuration in Tectia MFT Events administration interface

To start creating the event, open the Event List view in the administration interface, and click New Event. The configuration is created as follows:

  1. Create a new event with a descriptive name.

  2. Add a periodic trigger to run it at 10 minute intervals. (Here the interval is kept short to be able to run the evaluation in a relatively short time.)

  3. Define file transfer actions by specifying each source file location (on the remote hosts or cash registers) and then the destination directories where the files will be copied to the local host (the back-office server) and on the remote datacenter host. Connection to the datacenter requires a connection profile.

  4. Define a second action to remove all successfully transferred files from the source location. This removal action will be run once the file transfer action has been completed successfully.

  5. Define an email notification to be sent once the above actions have been completed successfully. Enter the sender and receiver email addresses, and a subject text. If you leave these options empty, Tectia MFT Events will use the default information defined in the configuration.

  6. Add another email notification to be used if the above file transfer and removal actions have ended in failure. Enter the sender and receiver email addresses, and a subject text. If you leave these options empty, Tectia MFT Events will use the default information defined in the configuration.

    This can be used for example to alert the administrator to investigate the reasons for the failure. The general Tectia MFT Events configuration is defined to log all events, so the administrator can view the details of the performance in the event logs stored on the back-office server.

  7. Save the configuration.

Return to the Event List view, where all created events are listed, and you can see the status of each event. By default, all new events are enabled, meaning that they will be executed according to their triggers.

The Event List view in the administration interface also gives tools for running any individual event manually. In this example, we want to run the event immediately to verify that it operates as expected.

The selected event will be run once

Figure 4.7. The selected event will be run once

  1. Select the event by clicking it (and the row turns green).

  2. Click the Run button, and the event will be executed once immediately.

  3. See the logs in the Log view to verify that the event was executed as planned.

===AUTO_SCHEMA_MARKUP===