Azure Blob Files in IMS

Azure Blob Files in IMS

1.     Introduction


This new service allows IMS users to set up an external Azure container for saving files for certain functionality such as file Exports. This way anytime a user (in the same DB) generates an export file this will be saved in the Azure container.

2.     Location

 

Up to this day it has been implemented in:

- Tools => Reports => Network Export (NetworkExport.dll)

- FTTH => GlasDraad => Export naar FC (GlasDraadPlugin.dll)

3.     Prerequisites

-Having an account in Azure Blob Storage: Azure Blob Storage | Microsoft Azure

4.     Setup

In Azure:

 

1.     In the Azure portal, select Your storage account > Containers.

 

2.     Select a container from the list.

 

3.     Right of the main window and select the three ellipses associated with your container.

 

4.      Select Generate SAS from the dropdown menu to open the Generate SAS window.

 

 

5.     Select Signing method > User delegation key.

 

6.     Define Permissions by selecting or clearing the appropriate checkbox. Make sure all permissions are selected.

 

7.     Specify the signed key Start and Expiry times. Since its for internal use only we can put an expiry date of years from now.

 

8.     For Allowed protocols  keep the default value  HTTPS.

 

9.     Select Generate SAS token and URL.

 

10.  The Blob SAS token query string and Blob SAS URL appear in the lower area of the window. Save this URL for later.

 

11.  Copy and paste the Blob SAS token and Blob SAS URL values in a secure location. They're displayed only once and can't be retrieved after the window is closed.

 

In case any of our clients want to access the container a new SAS token should be generated with the desired rights (depending on the users needs).

 

In IMS:

 

With administrator rights hold shift and click on any of the buttons where this module has been implemented (see Location ).

Then a small window like the following will appear where the appropriate fields can be filled:

 

 

When doing this the appropriate fields will be created in the target database. If those three fields are kept empty then the tool will ignore this functionality.

5.     Result

 

 

When accessing the container though Microsoft Azure Storage Explorer all saved files will appear:

 

 

In properties of the file we can find generated metadata that could be use for future automation:

 

 


    • Related Articles

    • Inframap making IMS crash

      Whenever opening InfraMap is making IMS crash, you can export the Admin Map settings to the users account to fix this.
    • Release 2022

      Generic notes Numerous bugfixes; GeoWorks V2 rolled out: Complete overhaul of the existing GeoWorks with a modern, robust, and futureproof interface. Connect SubObjects V2 (pre-)released. Under further construction due to very active feedback (thank ...
    • Release 2021

      General improvements Speed of connection created using auto connectivity rules is substantial increased. In the Edit Model section the type of columns can be changed. In the Projects Panel all projects can be collapsed at once. In the Object Files ...
    • Release 2022.5

      Generic Notes Numerous bug fixes; HLD Wizard (in beta): create your HLD Designs automatically via an elegant wizard; DP Organizer added: one function to sort and reconnect clients and ducts on a DP; KadasterTools: divide in clients highrise button ...