Supported Storage Types

Configuring a virtual folder with Amazon-S3 bucket

Following are the steps to configure the VFS with Amazon-S3:

  1. Specify the following information and click Save.

    Field Description
    Bucket name Specify the Amazon-S3 bucket name.
    Folder path Specify the folder path for the bucket. If you do not specify the folder path, then the root of the bucket is considered by default.
    Region name Choose the AWS (Amazon Web Services) region from the list. This is the location where your Amazon-S3 bucket resides.
    Access key ID Specify the Access key ID to access the Amazon-S3 bucket.
    Secret access key Specify the secret key which corresponds to the Access Key ID that has the access to Amazon-S3 bucket.
Note:
  • For more information about Amazon-S3 service, refer Amazon documentation.
  • When you provide a non-existent folder path in a VFS pointing to S3, the folder automatically gets created during file operations.

Configuring a virtual folder with Hosted-S3 bucket

Following are the steps to configure the VFS with Hosted-S3:

  1. Specify the following information and click Save.

    Field Description
    Bucket name Specify the Hosted-S3 bucket name.
    Folder path Specify the folder path for the bucket. If you do not specify the folder path, then the root of the bucket is considered by default.
    Access key ID Specify the Access key ID to access the Hosted-S3 bucket.
    Secret access key Specify the Secret access key which corresponds to the Access key ID that has the access to Hosted-S3 bucket.
    Endpoint Specify the Endpoint to access the Hosted-S3 bucket.
    URL Style Choose one of the following addressing models:
    1. Path. In this URL model, the hostname is s3-hosted.example.com and the bucket name is specified in the path as /bucket-name/.For example, https://s3-hosted.example.com/bucket-name/
    2. Virtual host. This URL model involves including the bucket name as a subdomain of the hostname. For example, https://bucket-name.s3-hosted.example.com/

Azure storage

If you want to configure the VFS with Azure storage type, then select the AZURE-FILE or AZURE-BLOB from the list.

Note: IBM® webMethods Managed File Transfer currently supports only AZURE-FILE shares and AZURE-BLOB containers.

Configuring a virtual folder with AZURE-FILE

Following are the steps to configure the VFS with AZURE-FILE:

  1. Specify the authentication information that must be sent to Azure storage type for authorizing access to specific resources. AZURE-FILE share supports Shared Key and Shared Access Signature (SAS) authentication types.

    Choose one of the following ways to provide the authentication information:

    Option Description
    Shared Key The shared key type passes a header with each request that is signed using the respective storage account access key. Specify the values for the following fields:
    • Account name. The account name that corresponds to the Azure account for the AZURE-FILE location.
    • Access key. The key that you create at the Azure portal for the corresponding account name.
    Shared access signature (SAS) The Shared Access Signature (SAS) type provides secure delegated access to resources in the storage account without compromising the security of the data. Additionally, control what resources the client may access, what permissions they have on those resources, and how long the SAS is valid, among other parameters.
    • Account name: Specify the account name that corresponds to the Azure account for the AZURE-FILE location.
    • SAS token: The SAS token is a string that you generate in the Azure portal for an account.
    High availability download recovery Select the option to allow IBM webMethods Managed File Transfer to resume a download that was not completed previously.
  2. Specify the location where the folder for the AZURE-FILE share resides.
Note: AZURE-FILE share supports headers for customization, security, caching, modification checks, and efficient transfers.

Configuring a virtual folder with AZURE-BLOB

Following are the steps to configure the VFS with AZURE-BLOB:

  1. Specify the authentication information that must be sent to the Azure storage for authorizing the access to resources. The AZURE-BLOB supports Shared Key, Shared Access Signature (SAS), and Anonymous public access authentication types.

    Choose one of the following ways to provide the authentication information:

    Option Description
    Shared Key The shared key type passes a header with each request that is signed using the respective Storage Account Access Key. Specify the values for the following fields:
    • Account name. The account name that corresponds to the Azure account for the blob location.
    • Account key. The key that you create at the Azure portal for the corresponding account name.
    Shared Access Signature (SAS) The Shared Access Signature (SAS) type provides secure delegated access to resources in your storage account without compromising the security of the data. Additionally, control what resources the client may access, what permissions they have on those resources, and how long the SAS is valid, among other parameters.
    • Account name. The account name that corresponds to the Azure account for the blob location.
    • SAS token. The SAS token is a string that you generate in the Azure portal for an account.
    Anonymous public read access The anonymous public read access type provides you with read access within a publicly accessible container without authorizing the request. Specify the values for the following fields:
    • Account name. The account name that corresponds to the Azure account for the blob location.
    High availability download recovery Select the option to allow IBM webMethods Managed File Transfer to resume a download that was not completed previously.
  2. Select a storage sub-type. The below mentioned are the two types of storage sub-types:
    • Block Blob: It stores the unstructured data such as files, media, images, and documents in blocks.
    • Append Blob: It appends the unstructured data such as files, media, images, documents and so on.
  3. Specify the Azure container folder path for the Location field.
  4. Specify the advance configuration options as follows:
    • Storage size: Specify the size of each part of the file which gets uploaded to the blob container.
    • Azure headers: Add additional header parameters to set the extra metadata for the blob container. Click  Add  to add the Header key and Header value information, respectively. The following are the list of supported headers:
      • cacheControl
      • contentType
      • contentEncoding
      • contentLanguage
      • contentDisposition
Note: AZURE-BLOB now supports creating and renaming of folders and files upto 256 MB.

Configuring a virtual folder with Google Cloud Platform (GCP) bucket

IBM webMethods Managed File Transfer supports GCP storage buckets using Google Cloud Service Account.

Following are the steps to configure the VFS with Google Cloud Platform:

  1. Specify the following information and click Save.
    Field Description
    Service account private key Specify the encoded private key (a JSON file) for a service account. This key is used to authenticate the service account and authorize it to access GCP resources.
    • Open your Google Cloud console settings.
    • Go to IAM & Admin > Service Accounts.
    • Click Create service account.
    • Provide the configured email address.
    • Click keys tab and add the JSON key.
    • Refer Google Cloud documentation for more details.
    Bucket name Specify the GCP bucket name.
    Folder path Specify the folder path for the bucket. If you do not specify the folder path, then the root of the bucket is considered by default.
    High availability download recovery Select the option to allow IBM webMethods Managed File Transfer to resume a download that was not completed previously.
Note:

  • Hosted-S3 and Google Cloud Platform configurations are available only on the Virtual folders tab. This cannot be configured while creating actions.

  • When you provide a non-existent folder path in a VFS pointing to GCP, the folder automatically gets created during file operations.