Azure Blob storage is Microsoft's object storage solution for the cloud. Blob storage is optimized 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.
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.
- Proxy Information
Authentication Connection Fields
- 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.
- 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 Information Fields
- 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
There is no available Discovery Instance Connector available for Azure Blob.
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.
Integration Connection Fields
- Connection Name: This is a unique name given to the connector instance upon creation.
- Description: A description of the connector to help identify it better.
- Authentication Connection: The Azure connection that you want to use
A Simflofy Job is the process of moving or syncing content(including versions, ACL's, metadata) from one CMS (content management system) to another. Click here for details on how to set up an integration job.
- Output Specification
- DateTime Config (Output)
- Repository Specifications
Output Specification Fields
- Output Folder Path: The path of the root folder.
- 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.
- 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.
Date Time Output Configuration Fields
- Date Format: Date mappings will be converted to this ISO format
- Date Time Format: DateTme mappings will be converted to this ISO format
- 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 TSearch web application perform actions against specific repositories. More info
Basic Configuration Fields
- 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.
- Content Disposition: The content disposition to apply to metadata when updated from the content service connector.
- Extra parameters can be passed to the content service connection and vary by connection.
- Create File
- Delete Object By Id
- Get File Content
- Get Object Properties
- Update File
- Update Properties
Looking to integrate with Azure? We can help.