Versions Compared

Old Version 12

changes.mady.by.user Andrea Harvey

Saved on

compared with

New Version Current

changes.mady.by.user Andrea Harvey

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The first step is to create the connection by providing the connection information required for DryvIQ to connect to the platform/server. The connector can be created using any user account with permissions to access the content.

  1. Select Connections > Add connection.

  2. Select Azure Blob Storage as the platform on the Add connection modal.

  3. Enter the connection information. Reference the table below for details about each field.

  4. Test the connection to ensure DryvIQ can connect using the information entered.

  5. Select Done.


Add connection modal - Azure Blob Storage

...

Field

Description

Required

Display as

Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists.

If you do not add a display name, the connection will automatically be named using account name. For example, Azure Blob Storage (Account Name). If it will be useful for you to reference the connection by the account name, you should use the default name. 

Optional

Account Name

Enter the account name that should be used to connect to the platform.

Required

Access Key

Enter the access key ID required to access the account. Refer to the Manage storage account keys page in the Microsoft Azure product documentation for information on where to locate the access keys.

Required

Container Name

Enter the Blob container name you want to access.

Required

Snapshot blobs before overwrite

Select if you want to create snapshot of the blobs before overwriting. Refer to the Create a snapshot of a blob page in the Microsoft Azure product documentation for information about blob snapshots.

Optional

Connection Test Succeeded

...

Features and Limitations

Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows you to configure actions based on Job Policies and Behaviors. The information below is platform specific. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations. 

...

Below is list of supported and unsupported features as well as additional file/folder restrictions. 

Supported Features (tick)

Unsupported Features (error)

Version preservation

Timestamp preservation

Metadata map

Author/Owner preservation

File lock propagation

Mirror lock ownership

Invalid characters

File size maximum

Path length maximum

Restricted types

Segment path length

Account map

Group map

Permission preservation

User impersonation

Tags map

...

Create Connection | REST API

...

Create a basic connection using the example below. Replace the example values with the information relevant to your connection.

POST {{url}}v1/connections/

Code Block
{
  "name": "display name goes here",
  "platform": {
  	"id": "azure-blob"
  },
  "auth": {
        "client_secret": "this is the access key",
        "domain": "this is the account name",
        "container": "this is the container name"
	}
}

...

Create a Job | REST API Job Configuration Example

The sample code below shows how to create a basic copy job for a connection created to connect as a standard user. Replace the source and destination IDs and paths with information relevant to your connections and jobs.

POST {{url}}v1/jobs

Code Block
{
    "name":"Simple Job",
    "kind": "transfer",
    "transfer": {
      "transfer_type": "copy",
        "source": {
            "connection": { "id": "{{Connection_sourceID}}" },
            "target": {
                "path": "/sourceDocumentLibrary"
            }
        },
        "destination": {
            "connection": { "id": "{{Connection_destinationID}}" },
            "target": {
                "path": "/destinationFolder"
            }
        },
        "simulation_mode": false
    },
    "schedule": {
        "mode": "manual"
    },
    "stop_policy": {
        "on_success": 5,
        "on_failure": 5,
        "on_execute": 25
    },
    "category": {
      "name": "Report {Name}"
    }
}