User Guide > Objects > Alphabetical Listing > Partially Qualified FileTransfers

Partially Qualified File Transfer

As opposed to fully qualified file transfers, partially qualified file transfers can also transfer several files by using wildcard charactersThese are placeholders for characters when you specify filters. ? stands for exactly one character, * for any number of characters.. This document describes how you can define source and target file filters depending on the particular versionsAn application version holds zero or more deployment packages and may have dependencies to zero or more application versions of the same (or to different) applications of the source and target agents.

A file transferTransfers files from one computer to another. A particular Automation Engine object type (FileTransfer object). is partially qualified if one or several wildcard characters are used in order to specify the source and target file. The option Use wildcards must also be activated.

The file transfer protocol is decisive for the way that wildcard characters are used:


Old File Transfer Protocol

The old file transfer protocol is used if the source and/or target agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host are of a Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. version below 9.00A.

Source

To define the source file, you can use the wildcard characters * and/or ?. At least one wildcard character must be used.
"*" stands for any number of characters (including no character), "?" for exactly one. Fixed file name parts and wildcard characters form a filter which is used to retrieve the files that should be transferred.

Wildcard characters are always read from left to right. If the fixed part occurs several times in between wildcards in the source file, the filter applies as of the position at which the fixed part first occurs.

For example:
Source: *a*a*.txt
Name of a source file that complies with the filter: abrahamastreet.txt

In z/OS, the wildcard characters "*" and "?" must only be used once and not as the first character.

In OS/390, wildcard characters are not supported on GDG (generation data groups) files. However, you can use a scriptA particular Automation Engine object type. objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task with the prep_process_filename script functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… on the needed files with wildcards and start a JOBF for each returned file with the activate_uc_object script function.

Target:

In the target file, the wildcard character "*" must be used exactly once. It represents the source file's complete variableIt stores or retrieves values dynamically at runtime. An individual Automation Engine object type. part starting with its first wildcard character (? or *) and ending with its last wildcard character (? or *).

For example:

Source: ?C_SERVER_*_01.TXT
File that complies with the filter: UC_SERVER_LOGG_01.TXT
Target: TEST_*_A.TXT
Name of the target file: TEST_UC_SERVER_LOGG_A.TXT

Source: *_SERVER_*_0?.TXT
File that complies with the filter: UC_SERVER_LOGG_01.TXT
Target: TEST_*_A.TXT
Name of the target file: TEST_UC_SERVER_LOGG_01_A.TXT 


New File Transfer Protocol

The source and target agent must be of Automation Engine version 9.00A or later.

Source

See old file transfer protocol.

Target:

To define the target file, you can use the * character as often as you like. It represents the source file's complete variable part starting with its first wildcard character (? or *) and ending with its last wildcard character (? or *).

Note that for each * characters, the system will insert all applying characters in the target file name from the first to the last source file's wildcard character. The built target file name can become very long.

Nine placeholders are additionally available that can be used to specify the target file. They refer to a particular wildcard character (?,*) in the source file name. These placeholders are composed of the & character and the numbers 1-9: &1, &2, &3,... &9.
The number specifies the wildcard location in the source that is addressed:
For example: Placeholder &3 is replaced by the source file name's characters that are retrieved by the third wildcard character in the source file specification.
Starting the file transfer results in an error if the source file's filter includes fewer wildcards than are addressed in the target specification. Each placeholder can be used in the target file as often as required.

The wildcard characters * and &1, &2 ... &9 have different functions and can be used in parallel.

The wildcard character "?" must not be used in target file names.

Automic recommends using at least as many wildcards in the source and the target as are required in order to clearly identify the file name. Otherwise, the file transfer will try to create several target files of the same name in the same location. In this case, the actionActions are predefined building blocks for recurring activities. They are commonly used for managing third party systems or in deployment scenarios. that is defined in the file transfer setting "File exists" is executed (cancel, overwrite, append).

 

Example 1

The following complex example describes wildcard combinations that can be used in file transfers.

Source specification:   a?b*c?*?d*

Source files that comply with the filter, and their variable parts:

  File name &1 &2 &3 &4 &5 &6 *
1 a1b234c05670d.txt 1 234 0 567 0 .txt 1b234c05670d.txt
2 a2b345c17891d.txt 2 345 1 789 1 .txt 2b345c17891d.txt
3 a3b456c20903d.txt 3 456 2 090 3 .txt 3b456c20903d.txt

Target specification:

The following target file names are created:

  File name
1 234a1b234c05670d.txtb1c2341b234c05670d.txt0d.txt

2 345a2b345c17891d.txtb2c3452b345c17891d.txt1d.txt
3 456a3b456c20903d.txtb3c4563b456c20903d.txt2d.txt

 

Example 2

The following example reverts the date of the source file name in the target file name.

Source specification:

*????_*.*

Source files that comply with the filter:

  File name &1 &2 &3 &4 &5 &6 &7
1 20110307_reportA report provides more detailed information about a task's execution or a component..txt 2011 0 3 0 7 report txt
2 20110220_overview.doc 2011 0 2 2 0 overview doc
3 20110111_script.txt 2011 0 1 1 1 script txt

Target specification:

&6_&4&5&2&3&1.&7

The following target file names are created:

  File name
1 report_07032011.txt
2 overview_20022011.doc
3 script_11012011.txt

 

See also:

File transfer - Procedure
FileTransfer tab

 

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH