Adding an upload folder to a connection

Note: Upload folders are only supported for LN environments that run on a Windows platform. On the LN server, Tools version 10.6.0.1 or later is required.

You can use two types of storage for the location of an upload folder in the cloud:

  • A location relative to the ${BSE}/appdata folder on the LN server
  • A location relative to a tenant-specific path in an Amazon S3 bucket

In the configuration console, these storage types are displayed as "LN" and "S3" respectively.

To use the "S3" functionality, Tools version 10.7.0.1 is required on the LN server. The ttrpiln-transfer-service.javaapp Java application must be deployed on the LN server. If required, use the Deploy Java Applications (ttadv2570m300) LN session to deploy the latest version of this application.

  1. This step is only applicable for the "LN" storage type. On the LN server, create a folder to be used as “target folder” for the upload. Create this folder as a subfolder of ${BSE}/appdata.
    The service uploads files from a source folder on a local system into this target folder, and creates subfolders as required.
  2. This step is only applicable for the "LN" storage type. Ensure that the folder permissions allow read and write access to the LN account that is used for the connection.
  3. On the local system, create a folder to be used as “source folder” for the upload.
    Create this folder on one of these locations:
    • The file system of the system that runs the LN Transfer Service
    • A network share of a Windows system in the local network
    Files from this source folder and its subfolders are uploaded to the remote LN server into a matching folder structure in the “target folder”. After a successful upload, the files are removed from the source folder. If an archive folder has been defined on a local system, the files are placed in that folder. Otherwise the files are deleted. Ensure the permissions on the source folder and, if applicable, archive folder allow read and write access to the account that runs the service.
  4. In the configuration console, select the connection node in the tree and click Add Upload Folder.
    1. Specify a name for the upload folder. This name is displayed in the tree. It does not have to match the actual folder name on the LN server or the local system.
    2. Click OK.
  5. After the upload folder is added, it is displayed in the tree as a child node of the connection. Select the upload folder node to open the Upload Folder view.
  6. Specify this information:
    Enabled
    If this check box is selected, the upload folder is processed by the service, if the connection itself is also enabled.
    If this check box is cleared, the upload folder is not processed.
    Local Source
    Specify the folder that contains the files to be uploaded.
    This is a folder on a local system. For example:
    • If you specify C:\data\lndata\upload, the C:\data\lndata\upload folder on the local machine that runs the service is used as source folder for files to be uploaded.
    • If you specify \\server\share\upload, the upload folder on the \\server\share network share is used as source folder.

    Optionally, click Browse to browse to a folder instead of manually typing the path.

    Archive files after transfer
    If this check box is selected, the files from the source folder are relocated to the archive folder after a successful upload by the service.
    If this check box is cleared, the files from the source folder are deleted after a successful upload by the service.
    Local archive
    Specify the folder where the processed files must be placed.
    This is a folder on a local system. For example:
    • If you specify C:\data\lndata\archive, the C:\data\lndata\archive folder on the local machine that runs the service is used as archive folder for files to be uploaded.
    • If you specify \\server\share\archive, the archive folder on the \\server\share network share is used as archive folder

    Optionally, click Browse to browse to a folder instead of manually typing the path.

    Storage Type
    Specify the desired type of storage by selecting one of these options:
    • LN

      The target path is a path relative to the ${BSE}/appdata folder in LN.

    • S3

      The target path is a path relative to the tenant-specific data area in the S3 bucket.

    Note: The "LN" storage type can only be used for files smaller than 10 MB.
    Remote Target
    Specify the folder to which the files must be uploaded:
    • For the "LN" storage type, this is a path on the LN server, relative to ${BSE}/appdata. The path consists of folder names, separated by "/" characters. For example, if you specify lndata/upload, ${BSE}/appdata/lndata/upload is defined as target folder.
    • For the "S3" storage type, this is a folder path relative to a tenant-specific area in Amazon S3.
      • If the path starts with “AWS_S3_admin/”, the path is defined in the temporary AWS S3 bucket.
      • If the path starts with “AWS_S3/”, the path is defined in the AWS S3 bucket for app data.

    “AWS_S3_admin/” or “AWS_S3/” must be followed by one or more folder names, separated by “/“ characters. The AWS S3 bucket for app data is the default; a path that does not start with “AWS_S3_admin/” or “AWS_S3/” is equivalent to a path that starts with “AWS_S3/”.

    Overwrite existing files
    If this check box is selected, new upload files overwrite old upload files with the same name.
    If this check box is cleared, new upload files do not overwrite old upload files with the same name; instead, new files are renamed so that both old and new files can exist in the same folder.
    File Name Filter
    If this check box is selected, file name filtering is applied to the files in the source folder. Only files that match the pattern are uploaded.
    If this check box is cleared, all files in the source folder are uploaded. The filter is applied to the file name only; the folder path of the file is not filtered.

    See File name filtering.

    Pattern
    The pattern expression. This is either a "wildcard expression" or a "regular expression". For example:
    • You specify this wildcard expression: *.pdf

      The abc.pdf and 123.pdf files are uploaded. The abc.dat and 123.txt files are not uploaded.

    • You specify this regular expression: .+\.(pdf|txt)$

      The abc.pdf and 123.txt files are uploaded. The abc.dat and 123.txt.tmp files are not uploaded.

    The pattern expression. This is either a "wildcard expression" or a "regular expression". For example:
    Regular expression
    If this check box is selected, the specified pattern is interpreted as a regular expression.
    If this check box is cleared, the specified pattern is interpreted as a wildcard expression.
    Case sensitive
    If this check box is selected, the pattern is interpreted as case-sensitive.
    If this check box is cleared, the specified pattern is interpreted as case-insensitive.
    For example:
    • A case-sensitive wildcard pattern a*.txt accepts file name all.txt, but does not accept ALL.txt.
    • A case-insensitive wildcard pattern a*.txt accepts both all.txt and ALL.txt.
  7. Optionally, test the status of the folders, to ensure you specified the correct paths for the folders.
  8. Click Save.