Execu/Tech Data Upload - Amazon S3

---

Execu/Tech Data Upload is used to automatically prepare and upload files to an Amazon S3 destination.

Each upload configuration is stored in a Profile. A profile determines which files are processed, where they are uploaded, how the files are named, whether they are compressed or encrypted, and what happens to the source files after a successful upload.

Before You Begin Before configuring an Amazon S3 upload, obtain the following information from the company or service receiving the files: Region Bucket Prefix, if one is required Access Key ID Secret Key Any required file naming, compression or encryption instructions

Opening Execu/Tech Data Upload Execu/Tech Data Upload is located in the Execu/Tech application folder. Using Windows File Explorer, browse to the folder where the Execu/Tech application is installed and run: ETDataUpload.exe The application will open to the profile configuration screen where upload profiles can be created, edited, tested and enabled for automatic processing.

​

Create a Profile

A profile contains all of the settings required to select, prepare and upload one or more files.

1. Open Execu/Tech Data Upload and select the Profiles tab.
   
   
2. Click New Profile and enter a descriptive name for the profile.
   
   Examples:
   Statistics Production
   Reservations
   POS Statistics
   
   
3. Select Enabled to make the profile available for processing.
   
   
4. Select Allow auto-run if the profile should run automatically when Execu/Tech Data Upload is started by a scheduled task or with the /auto option.
   
   
5. Enter an optional Description to explain the purpose of the profile.
   
   

Profile Processing Order Profiles are displayed and processed in alphabetical order. If profiles need to run in a particular order, prefix the profile names with numbers. For example: 10 - Statistics Production 20 - Statistics Testing 30 - Reservations This is especially important when more than one profile processes the same source file.

Select the Amazon S3 tab on the right side of the Profiles screen.

1. Select Enabled in the Amazon S3 section.
   
   
2. Select the Region containing the destination S3 bucket.
   
   The Region must match the AWS region where the bucket is hosted.
   
   
3. Enter the Bucket name provided by the receiving company.
   
   Enter only the bucket name. Do not include s3:// or the Prefix in this field.
   
   
4. Enter the Prefix, if one was provided.
   
   The Prefix identifies the location within the S3 bucket where the files will be placed. It works much like a folder path.
   
   For example, if the Bucket is:
   
   company-data-transfer
   
   and the Prefix is:
   
   statistics
   
   a file named Statistics.csv would be uploaded using an S3 object name similar to:
   
   statistics/Statistics.csv
   
   Leave Prefix blank if the receiving company does not require one.
   
   
5. Enter the Access Key ID provided for the S3 destination.
   
   
6. Enter the corresponding Secret Key.
   
   
7. Click Save Profile.

Verify the S3 Information Carefully The Region, Bucket and Prefix determine where the file is sent. The Access Key ID and Secret Key determine whether Execu/Tech Data Upload is authorized to access that location. Copy these values exactly from the information supplied by the receiving company.

Select the Files to Upload tab.

A profile can process a specific file, a folder of files, or files selected using a wildcard.

1. Click Add File to select a specific file.
   
   For example:
   
   C:\executech\hotel\csv\statistics.csv
   
   
2. Click Add Folder when the profile should process files from a folder rather than one specific filename.
   
   Folder entries can be useful when filenames change over time.
   
   
3. Review the options for each entry in the list:
   
   Path
   The file, folder or wildcard that Execu/Tech Data Upload will look for.
   
   Decrypt?
   Select this option when the source file is encrypted and must be decrypted before the profile processes it.
   
   Send Once?
   Select this option when each file should only be successfully transmitted one time.
   
   Subfolders
   Select this option when a folder or wildcard selection should also include matching files in folders below the selected folder.
   
   

Using Send Once? Send Once? can be used with either a specific filename or files selected using a wildcard. For example, a folder might contain: Statistics-20261020.txt Statistics-20261021.txt Statistics-20261022.txt With Send Once? selected, a successfully processed file is not sent again on future runs of that profile. Newly created files continue to be processed normally. If an already processed file is subsequently changed, Execu/Tech Data Upload can recognize the changed file as a new version and process it again.

To remove an entry from the profile, select it and click Delete Selected Item.

Send Selected File can be used to immediately process and send the selected file using the current profile settings. This performs a real upload and should only be used when you intend to send the file.

Select the File Handling tab.

The options on this screen determine how files are prepared before they are uploaded and what happens after processing completes.

The Example File Name at the top of the screen changes as filename, compression and encryption options are selected. Use it to verify the expected name of the outgoing file.

Zip before Encrypting?

Select this option to combine all files being processed by the profile into a single ZIP archive.

When ZIP is selected, enter the desired filename in Archive Name (If you Zip before Encrypting.).

Use ZIP when the receiving company expects multiple files to be delivered together as one archive.

GZip before Encrypting?

Select this option to GZip each file individually.

Unlike ZIP, GZip does not combine multiple files into a single archive. Each file is compressed and uploaded separately.

ZIP and GZip are different processing methods. ZIP combines the selected files into one archive. GZip compresses each file separately. Select the method required by the receiving company.

Property ID to append to upload file name.

Enter a Property ID when an identifier should be appended to the outgoing filename. This field is optional and can be left blank.

For example, a Property ID of 01 could change:

FileName.txt

to:

FileName-01.txt

The Property ID can contain up to 20 characters.

Append Date to upload file name? (-yyyyMMdd)

Select this option to append the current date to the outgoing filename in yyyyMMdd format.

For example:

FileName-01-20261022.txt

Review Example File Name after changing these options to make sure the final filename matches the requirements of the receiving company.

Use the PGP Encryption section when the receiving company requires uploaded files to be encrypted using PGP.

• Select Encrypt Uploaded Files to enable PGP encryption.
  
  
• Use Public Key File to select the public key supplied by the receiving company.
  
  
• Select Enable PGP Compression if the receiving company requires compression within the PGP process.

When PGP encryption is enabled, the public key supplied by the receiving company is used to encrypt the outgoing data. The receiving company uses its corresponding private key to decrypt the file.

Use the encryption settings specified by the receiving company.

The Command Line Encryption Tool section is used when a separate encryption utility is required instead of the standard PGP processing.

• Use Command Line Encryption Tool enables this option.
• Command Line Tool identifies the encryption application to run.
• Shared Key contains the key required by that encryption utility.
• Encrypted File Extension specifies the extension to use for the encrypted output file.

Only configure these settings when you have been provided the required encryption utility and corresponding information.

Select Delete work files after processing to remove temporary files created while Execu/Tech Data Upload prepares files for transmission.

This option does not delete the original source file.

During initial setup or troubleshooting, leaving the work files in place can be useful because they can be reviewed after a test.

Select Delete original files after processing when the source file should be removed after it has been successfully sent.

This is especially useful for files that continually accumulate data.

For example, a statistics file may continue growing as activity occurs. In this type of configuration, the successful upload becomes the cutoff point:

1. The current statistics file contains all activity accumulated since the previous upload.
2. Execu/Tech Data Upload successfully uploads the file.
3. The original file is deleted.
4. The application that produces the statistics starts building a new file as new activity occurs.
5. The next upload therefore contains only the activity accumulated since the previous successful upload.

If More Than One Profile Uses the Same File If the same source file is processed by more than one profile, Delete original files after processing should only be enabled on the last profile that processes that file. For example: 10 - Statistics Production Do not delete the original file. 20 - Statistics Testing Delete the original file after successful processing. Because profiles are processed alphabetically, the numeric prefixes ensure that both profiles have an opportunity to process the file before the final profile deletes it.

After configuring the profile, click Save Profile.

Save the profile before performing the tests below.

After the profile has been configured and saved, select the Run tab.

The Selected Profile shown on the Run screen should be the profile you just configured.

We recommend testing a new profile in the following order.

1. Test File Selection
   
   Click Test File Selection under Test SELECTED Profile.
   
   This test does not upload anything. It examines the file selection rules and displays the files that currently match the profile.
   
   Verify that:
   • The expected files are listed.
   • Unexpected files are not listed.
   • Wildcard selections are matching the correct files.
   • The expected Send Once setting is shown.
   • Files requiring decryption are identified correctly.
   If no files are found, verify the configured paths, filenames, wildcards and folders before continuing.
   
   
2. Test Without Upload
   
   Click Test Without Upload.
   
   This runs the profile's processing steps without sending the resulting files to Amazon S3.
   
   This allows you to test file selection, filename changes, compression and encryption without performing a real upload.
   
   The prepared output is written to the Work folder so it can be reviewed.
   
   Review the Log for errors or warnings before continuing.
   
   
3. Test WITH Upload
   
   After file selection and processing have been verified, click Test WITH Upload.
   
   This performs the complete profile process and sends the resulting file to the configured Amazon S3 destination.
   
   A confirmation is displayed before the upload begins.

Test WITH Upload performs a real upload. Make sure the Bucket, Prefix, filename and file contents are appropriate for the destination before running this test.

After Test WITH Upload completes, review the Log.

Execu/Tech Data Upload uploads the file and then verifies that the resulting object exists in Amazon S3.

Review the Log for the S3 upload and verification information.

Verify the following:

• The upload completed without an error.
• The correct Bucket is shown.
• The S3 object key contains the expected Prefix and filename.
• The S3 verification reports that the object exists.
• The uploaded file size is reasonable for the file being sent.

Final Verification A successful S3 upload confirms that Execu/Tech Data Upload was able to place the object in the configured S3 location. When setting up a new interface, also confirm with the receiving company that: The file arrived in the expected location. The filename is correct. The file can be opened or decrypted as required. The contents are in the format expected by the receiving system. This should be completed before the profile is placed into automatic production use.

The Log on the Run screen shows activity as profiles are processed.

Log entries include a time, level and message. Review warnings and errors when a profile does not process as expected.

A persistent log is also stored in the Execu/Tech Data Upload application folder:

ETDataUploadLog.txt

When troubleshooting an Amazon S3 upload, the Log can provide information about:

• The profile being processed.
• The source files selected for processing.
• File preparation and compression.
• Encryption.
• The S3 Bucket and object key.
• Upload success or failure.
• S3 verification.
• Error information returned by Amazon S3.

After the profile has successfully completed a real S3 upload and the receiving company has verified the file:

1. Return to the Profiles tab.
2. Select the profile.
3. Make sure Enabled is selected.
4. Select Allow auto-run.
5. Click Save Profile.

The profile can now be processed when Execu/Tech Data Upload is run automatically.

Do not enable automatic production processing until the profile has been tested with an actual S3 upload and the destination has been verified.

1. Create and name the profile.
2. Select Enabled.
3. Configure Region, Bucket, Prefix, Access Key ID and Secret Key.
4. Add the files or folders to process.
5. Configure Send Once?, Decrypt? and Subfolders as required.
6. Configure filename, compression and encryption requirements.
7. Determine whether work files or original files should be deleted.
8. Click Save Profile.
9. Run Test File Selection.
10. Run Test Without Upload.
11. Review the prepared files and the Log.
12. Run Test WITH Upload.
13. Review the S3 verification in the Log.
14. Confirm that the receiving company received and can process the file.
15. Select Allow auto-run when the profile is ready for normal scheduled processing.