...

Azure Parameter Description

Configuration example

<Repo>.contentservice.azureblobstorev2.type = 
<Repo>.contentservice.azureblobstorev2.storageendpoint =
<Repo>.contentservice.azureblobstorev2.connectionstring = 
<Repo>.contentservice.azureblobstorev2.container = 
<Repo>.contentservice.azureblobstorev2.contrepinpath = true 
<Repo>.contentservice.azureblobstorev2.cleanversions =  true
<Repo>.contentservice.azureblobstorev2.calculatestreamhash = true
<Repo>.contentservice.azureblobstorev2.invalidcharacters= 
<Repo>.contentservice.azureblobstorev2.region = azure
<Repo>.contentservice.azureblobstorev2.minparallelsize = 4194304
<Repo>.contentservice.azureblobstorev2.maxconcurrency = 2
<Repo>.contentservice.azureblobstorev2.blocksize = 4194304
<Repo>.contentservice.azureblobstorev2.singleuploadsize = 4194304

...

To use this feature, it is necessary to create a container with the "version-level immutability" option. See: https://learn.microsoft.com/en-us/azure/storage/blobs/immutable-policy-configure-version-scope?tabs=azure-portal

tia Content Server will manage the retention periods do not set default retention times on Azure.

This can be enabled in the Azure StorageAccount in a manually creation process of a container or via a corresponding configuration in tia Core, which is described below.

If the container creation is to be done by tia core, the following parameters must be added to the repository.cfg.

Configuration example immutability policies

<Repo>.contentservice.azureblobstorev2.allowcreatecontainer=false
<Repo>.contentservice.azureblobstorev2.enableversioning=true
<Repo>.contentservice.azureblobstorev2.management.tenantId=
<Repo>.contentservice.azureblobstorev2.management.clientSecret=
<Repo>.contentservice.azureblobstorev2.management.clientId=
<Repo>.contentservice.azureblobstorev2.management.subcriptionId=
<Repo>.contentservice.azureblobstorev2.management.resourceGroupName=
<Repo>.contentservice.azureblobstorev2.management.accountName=

• Die Werte können anhand dieser Anleitung ermittelt/erstellt werden:

  • https://developer.ibm.com/recipes/tutorials/how-to-procure-tenant-id-client-id-and-client-secret-key-to-connect-to-microsoft-azure-data-lake-storage-gen2/

...

...

Konfigurationsparameter in der repository.cfg

<Repo>.contentservice.type = azureblobstorev2
<Repo>.contentservice.azureblobstorev2.connectionstring=DefaultEndpointsProtocol=http;AccountName=devstoreaccount1;AccountKey=Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==;BlobEndpoint=http://127.0.0.1:10000/devstoreaccount1;QueueEndpoint=http://127.0.0.1:10001/devstoreaccount1;TableEndpoint=http://127.0.0.1:10002/devstoreaccount1;
<Repo>.contentservice.azureblobstorev2.container=test-repo
#<Repo>.contentservice.azureblobstorev2.invalidcharacters= #default:
#<Repo>.contentservice.azureblobstorev2.calculatestreamhash= #default: true
#<Repo>.contentservice.azureblobstorev2.contrepinpath= #default: true
#<Repo>.contentservice.azureblobstorev2.cleanversions= #default:true
#<Repo>.contentservice.azureblobstorev2.region= #default:azure
#<Repo>.contentservice.azureblobstorev2.minparallelsize= #default:4194304
#<Repo>.contentservice.azureblobstorev2.maxconcurrency= #default:2
#<Repo>.contentservice.azureblobstorev2.blocksize= #default:4194304
#<Repo>.contentservice.azureblobstorev2.singleuploadsize= #default:4194304

Überlegung zu blocksize und maxconcurrency

Informationen von Microsoft: https://learn.microsoft.com/en-us/java/api/com.azure.storage.common.paralleltransferoptions?view=azure-java-stable#com-azure-storage-common-paralleltransferoptions-setmaxconcurrency(java-lang-integer)

Die singleuploadsize bis welcher Größe Daten “am Stück“ hochgeladen werden.
blocksize und maxconcurrency beeinflussen die Geschwindigkeit bei Daten die größer singleuploadsize sind. Höhere Parallelität und blocksize führ zu höheren Bedarf an CPU und Memory. Es gilt blocksize * maxconcurrency * Anzahl paralleler Anfragen = Memoryverbrauch.

Die Namensregeln sind wie bisher, siehe Namensregeln.

...

Containernamen

Ein Containername muss ein gültiger DNS-Name sein und den folgenden Benennungsregeln entsprechen:

• Container Namen müssen mit einem Buchstaben oder einer Zahl beginnen oder enden und dürfen nur Buchstaben, Ziffern und Bindestriche (-) enthalten.

• Jedem Bindestrich (-) muss unmittelbar ein Buchstabe oder eine Zahl vorangehen und folgen von einem Buchstaben oder einer Zahl; zudem dürfen nicht mehrere Bindestriche direkt aufeinander folgen.

• Der Containername darf ausschließlich Kleinbuchstaben enthalten.

• Containernamen müssen zwischen 3 und 63 Zeichen lang sein.

Quelle: https://docs.microsoft.com/de-de/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata

...

Anchor
Naming Naming

Container naming convention:

Container naming

A container name must be a valid DNS name and comply with the following naming rules:

• Container names must begin or end with a letter or number and may contain only letters, numbers, and hyphens (-).

• Each hyphen (-) must be immediately preceded and followed by a letter or number; in addition, multiple hyphens may not directly follow each other.

• The container name must contain lowercase letters only.

• Container names must be between 3 and 63 characters long.

Reference: https://learn.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata

0er Container (Feature for Migration) (not supported by azureblobstorev2)

As of tia® Core version 2.0.5, it is possible to configure a container for storing "expired" documents.

If a document with expired “expirationDate” is archived (during migration process) or updated, this document will be moved into the configured container “0” (with corresponding information on the "original" document).

<Repo>.contentservice.azureblobstore.container=test1                    # Container for metadata and retention information
<Repo>.contentservice.azureblobstore.container.retention.0=test-0       # Container for expired documents 

Managed Identity

Managed Identity bewares you of copying and configuring security relevant parameters. It only works if blob store and tia core is hosted in Azure. (Same is valid for SQL db)

Azure knows 2 kinds of managed identity. Tia core can use both. Here shown is only server managed identity. On tia core configuration this distinction has no influence.

Managed Identity (Storage Account)

The blob store needs to have the role “Storage Blob Data Contributor”. There you add the app id of tia core. Then you can configure for blob store the storageendpoint instead of connectionstring.

Here the way to allow tia core to use managed identity.

• enter resource group

  Image Added

• select your resource group or create a new one

• select your storage account:

  Image Added

• enter access control (IAM):

  Image Added

• Add a roll “Storage Blob Data Contributor”

  Image Added

• use search bar and enter enter: storage Blob Data Contributor

  Image Added

  • press next

• press select members

  Image Added

• paste the tia core app id in search bar

  Image Added

  • press select

  • press review and assign