In an ascp command-line transfer, you can specify the transfer cookie with an environment variable.
set ASPERA_SCP_COOKIE=the_cookie
You can set up Console to match the cookie string (by creating a rule), and then substituting selected transfer information. To set up rules for matching the cookie string, select from the Console menu. On the Cookie Parsing Rules page, all existing rules are listed. To create a new rule, click New Rule.
The Creating New Rule page includes the following options:
| Item | Description |
|---|---|
| Rule name | Name for this parsing rule. |
| Regexp | The Cookie's regular expression. If this string matches, the cookie accompanies the transfer, and the following information is used in this transfer session. |
| Started via | Name of the transfer initiator. |
| Contact description | Description of this transfer initiator. |
| Transfer name | Name for this transfer. |
When finished, click Create to save the rule. When you have multiple cookie parsing rules, Console uses the first rule listed that matches the cookie string. To modify the order of the parsing rules, use drag-and-drop to move the rules in the list. If two rules have identical regular expressions, the rule that is higher in the list is applied.
The format used for regular expression is the RUBY format, as described here: "http://www.rubydoc.org/core/Regexp.html.
It is possible to capture parts of the cookie and reuse the value in the three parameters. For instance to enable setting the three transfer fields directly from the initiating application, one can fill in the fields with the following configurations:
- Rule name: MyCustomCookieRule
- Regexp: ^setcustomfields:(.+?):(.+?):(.+?):$
- Started via: \1
- Contact description: \2
- Transfer name: \3
For example, a transfer that started with the example cookie below will be displayed like in the following list and its session details will show.
ASPERA_SCP_COOKIE="setcustomfields:My App:My Contact:My Transfer:"
