Azure Blob Connector

Azure Blob storage is Microsoft's object storage solution for the cloud. Blob storage is optimised for storing massive amounts of unstructured data.

Unstructured data is data that doesn't adhere to a particular data model or definition, such as text or binary data.

More info on Azure Blob

Authentication Connection

The Azure Blob Auth Connector allows three different methods of authentication on the same connection. The field descriptions will tell you which to leave blank for your particular method.

All of these keys generated in the Azure portal.

Azure Key: Security + networking > Access Keys

SAS Token: Security + networking > Shared access signature

Application Credentials (Client ID/Secret): Follow Microsoft's instructions to generate these values

Click here for more information on setting up Authentication Connections.

Configuration

Field

Description

Name

Name of the Azure Blob Auth Connector

Azure Account Name

Name of the account associated with your blob storage

Azure Key

Azure authentication key. This can be obtained within your Azure portal

Azure Container Name

Name of the container within your azure blob storage. Leave blank for root

Use SAS Token

Tells the connection to look for a configured SAS token

SAS Token

Hidden unless above is checked. Put your SAS token here

Use Application Credentials

Tells connection to look for application credentials

Azure Storage Client ID

Leave blank if using SAS or Azure Key Auth

Azure Storage Client Secret

Leave blank if using SAS or Azure Key Auth

Azure Storage Tenant Id

Leave blank if using SAS or Azure Key Auth

Number of seconds for each attempt to upload

Default is 60s. Multiplying by the average MB per file is recommended. Must be between 1 and 2147483647.

Url to use instead of
https://[account].blob.core.windows.net.

Only used in cases where some custom url has been configured. Leave blank to use default url.

Proxy Configuration

This tab is for if you're connecting through a proxy, and is optional. Leave this tab blank if you aren't using a proxy.

Field

Description

ProxyURL

The URL of the proxy server

ProxyPort

The port of the proxy server

ProxyUsername

(Optional) The username to authenticate to the proxy server

ProxyPassword

(Optional) The password to authenticate to the proxy server

Integration Connection

Every job requires an integration connection for both the source repository connection and the output connection. Also known as input an output connections. Their job is to query or crawl remote systems for files, folders, metadata, versions, and renditions. In repo mode, it will retrieve list items and all of their relevant metadata from a list or library on the specified site. In output mode, the connection will write content and assign the mapped content type (from type mappings), or simply leave the new list item as a Document. Click here for more information on setting up an integration connection.

  1. Select integration and click on the new connection button.

  2. Enter the name and description of your connection.

  3. Select the connection type from the drop down list.

  4. Click Save on the Create Connection form.

  5. Click Save on the Edit Connection page.

There are no fields to configure in an integration connection.

Guide to Integration connections

Job Configuration

A 3Sixty Job is the process of moving or syncing content (including versions, ACL's, metadata) from one CMS (content management system) to another. Add tasks to your job to have better control over how your data gets migrated. Click here for details on how to set up an integration job.

Guide to Integration jobs

  1. Select List Jobs under Jobs on the navigation menu or the dashboard

  2. Click the create job button

  3. In the New Job form

    1. Name the job

    2. Select Simple Migration from the job type drop down

    3. Select the Repository Connection

    4. Select the Output connection

    5. Select your Content Service Connection

      (Only required if you will be using Federation)

    6. Click Save to open the Edit Job page

    7. Fill in the configurations for the Repo and Output Configuration tabs

  4. Click save to save your new integration job

  1. Select Run and Monitor Jobs under Integration in the navigation menu

  2. Click the play button next to the job you want to run

  3. Click the refresh button to view your completed job status

    (Larger jobs will take longer to run)

The Azure Blob Connector supports repo and output modes. Repo mode will require no additional configuration on the job, as it will simply crawl the entire configured container on the auth connection.

In output mode, the connector will output documents in the same fashion as the BFS Connector. The binaries will have a matching xml metadata file.

Click here for more information on setting up Integration Connections.

Output Specification

Field

Description

Output Folder Path

The path of the root folder. This field must either be left empty, start with “/”, or start with “\\”.

Include Batch ID in Output Path

If using a batch migration, the batch ID will be included in the output path.

Include Un-Mapped Properties

If selected, all available properties will be included in the metadata output file. If not selected, only mapped properties will be included in the metadata output.

Object Metadata Fields

A Comma delimited list of fields to add to the Azure Blob file as metadata. By default, metadata will only be written to the xml metadata file.

Object Headers

A comma-delimited list of header mappings to add to the Azure Blob file as metadata. Currently supported, and case-sensitive, headers: Content-Type, Cache-Control, Content-Encoding, Content-Language, Content-Disposition.

Example:
content-Disposition=content_disposition, Content-Type=content_type

Perform MD-5 Integrity Check

This check uses MD5 to verify authenticity and integrity of the data transfer. This requires an MD5 Hash Value Generator task to perform.

Aspect Remove Field Mapping

Currently not in use

Multi-value field separator

Some documents have fields that contain multiple values. Azure Blob does not support this, and will use this separator to form a list of these values as a string before upload.

DateTime Config (Output) Configuration Fields

Field

Description

Date Format

Date mappings will be converted to this ISO format

Date Time Format

DateTme mappings will be converted to this ISO format

Repository Specifications

Field

Description

Root Folders

Which root folders in the container to crawl. Leave blank to crawl all folders in the container.

Timeout in Second

The number of seconds before hitting a timeout and failing the document. Timeouts below 60 seconds might cause read issues.

Content Service Connection

Content Service Connections define connections to specific repositories. Actions in the Content Services API or the Discovery web application perform actions against specific repositories.

More info

Basic Configuration

Field

Description

Connector ID

Give your connector a unique name

Description

Provide a description for this connection

Type

Select your DocuWare connector

Keep Connection Alive

Keep this connection active

Keep alive in Milliseconds
(300000 is 5 minutes)

How long until connection expires if unused

Connection URL

The web address for your connection

Security mode

Select your preferred type of security credential access(Service Provided, User Pass through or Authentication Connector)

Mapping Type

Choose a single map or group mapping. Learn more about content service mappings.

Connection Configuration

Field

Description

Content Disposition

The content disposition to apply to metadata when updated from the content service connector.

Custom Parameters

Extra parameters can be passed to the content service connection and vary by connection.

Supported Methods

  • createFile

  • deleteObjectByID

  • getFileContent

  • getObjectProperties

  • updateFile

  • updateProperties

API Keys

Azure Blob Connector: Read=true: Write=true: MIP=false

Repo (Read) Specs

Key

Description

Data Type
rootFolders Root Folders. Leave empty to crawl all folders in container. String

readTimeout

Read timeout in seconds.

Integer

Output (Write) Specs

Key

Description

Data Type
outputfolderpath Output Folder Path String

azureMetaAsXML

Output Metadata as XML

Boolean

includedBatchId

Include Batch ID in Output Path

Boolean

includedUnMapped

Include Un-Mapped Properties

Boolean

objectmetadatafields

Object Metadata Fields

String

PARAM_AZ_OBJECT_HEADERS

Object Headers

String

PARAM_AZ_INTEGRITY_CHECK

Perform MD-5 Integrity Check

Boolean

arfm

Aspect Remove Field Mapping

String

multivalueseparator

Multi-value field separator

String

azureDateFormat

Date Format

String

azureDateTimeFormat

Date Time Format

String

Looking to integrate with Azure? We can help.