Integrate Infobridge with Inforiver 3.x

This guide will help you deploy Infobridge in your Inforiver environment.

This guide is intended for customers who are upgrading from Inforiver 2.x to Inforiver 3.x. If you are deploying Inforiver 3.x for the first time, Infobridge is enabled by default.

Make sure you have already updated your existing Inforiver 2.x instance to 3.x by following the instructions on the previous Overview page.

Follow the steps mentioned in this guide to integrate Infobridge into your existing Inforiver environment. Infobridge is a powerful add-on that enhances Inforiver's data connectivity and management capabilities, offering a seamless bridge between your Power BI reports and a wider range of data sources.

You can find detailed instructions and screenshots to assist you through the process. Follow them carefully to ensure a smooth and successful update.

1. Create a file share

1. In the Azure portal, navigate to Storage accounts and select your storage account.

Select your storage account

2. To create a file share, select File shares under the Data storage menu. On the right, click 'File share'.

Select 'File share'

3. Enter a name for the file share and click Next. Note that this name will be used later to update the YAML configuration file.

Enter a name

4. You can check the box in the image below if you prefer a backup. Click Next.

Back up option

5. Once the validation is passed, click Create.

File share created

2. Create a private endpoint for the storage account

1. After creating the file share, navigate to the 'Networking' window by selecting Networking from the Security + networking menu. On the right pane, click '+Private endpoint' from the Private endpoint connections tab.

Add a private endpoint

2. Enter a name for the endpoint and choose the appropriate Resource Group and Region. Click Next.

Configuring name, resource group and region

3. Select 'file' as the target sub-resource.

target sub-resource

4. Choose the Virtual network and Subnet to deploy your private endpoint and proceed to the next steps.

select virtual network and subnet

5. After the validation is passed, click Create. The deployment is now complete.

validation passed

private endpoint - deployment complete

6. Navigate to the Access keys window in the storage account to get the access key. Copy the access key using the copy icon and retain it as it will be used while updating the Container Instances(ACI).

Copy the access key

3. Edit the ACI configuration

1. Launch the Azure CLI window and run the following command to export the container instance in a YAML script file.

az container export -g <resource_group_name> -n <container_instance_name> --file output_file 

Launch Azure CLI and execute the command

2. To download the output file, click Manage files -> Download and enter the path of the output file. Click Download.

Download the output file

3. Click on the output file to download it to your local system.

Download locally

4. Open the file in Visual Studio Code to add the new Infobridge container properties as below. We need to add 3 additional containers for Infobridge.

Container 1:

- name: infobridge-writeback-worker 
    properties: 
      configMap: 
        keyValuePairs: {} 
      environmentVariables: 
      - name: ADMIN_PORTAL_URL 
        value:  
      - name: PRODUCT_BUILD
        value: inforiver
      - name: LISTENER_MODE
        value: dataflow
      image: turing.azurecr.io/turing-writeback-worker:OPV3.0.2.0
      ports: []
      resources: 
        requests: 
          cpu: 0.5 
          memoryInGB: 2.0  

Container 2:

- name: infobridge-visual-worker
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value:
      - name: PRODUCT_BUILD
        value: inforiver
      - name: SERVICE_NAME
        value: infobridgeVisualWorker
      - name: VISUAL_WORKER_LISTENER_MODE
        value: dataFlowSourceIntegration
      image: turing.azurecr.io/turing-visual-worker:OPV3.0.2.0
      ports: []
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 1.0 

Container 3:

- name: infobridge-transformation-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value:
      - name: PRODUCT_BUILD
        value: inforiver
      - name: SERVICE_NAME
        value: infobridgeTransformationWorker
      image: turing.azurecr.io/turing-datasource-integration-worker:OPV3.0.2.0
      ports: []
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 2.0
      volumeMounts:
      - mountPath: /mnt/azure
        name: inforiverfile

5. Now, attach the volume properties as below:

imageRegistryCredentials:
  - isDelegatedIdentity: false
    server: turing.azurecr.io
    username: InfoRiverRead
    password:
  initContainers: []
  isCreatedFromStandbyPool: false
  isCustomProvisioningTimeout: false
  osType: Linux
  provisioningTimeoutInSeconds: 1800
  restartPolicy: Always
  sku: Standard
  subnetIds:
  - id: /subscriptions/<subscription-id>/resourceGroups/<rg-name>/providers/Microsoft.Network/virtualNetworks/<vnet-name>/subnets/background
  volumes:
  - azureFile:
      shareName: inforiverfile
      storageAccountName:
      storageAccountKey:
    name: inforiverfile
tags: null
type: Microsoft.ContainerInstance/containerGroups

6. Enter the password to pull the image from the registry. You would have received it during the initial deployment. If not, please get in touch with our support team. Also, add the Storage account name and the access keys in the respective sections. Access keys can be obtained from the respective storage account's Access keys section.

7. Replace the old tag version of the image with the new version. Choose 'Replace all' to update the changes on all the containers.

Replace image tag version

8. Now, change the apiVersion value to ‘2023-02-01-preview’

update apiVersion

9. We will now save the file and upload it back to the Azure CLI.

10. Open the Azure CLI, and remove the old output file by using the following command:

rm output_file 

11. To upload the updated output file back to Azure CLI, click Manage files -> Upload as shown below.

Upload file

12. Select the updated output file from the file explorer.

Select updated file

13. After uploading the file, go to the container instances - Overview page. Choose Delete to delete the container instances so that you can update them with the new configuration file.

click 'Delete'

Deleting container instances

14. After the ACI is deleted, execute the following command in the Azure CLI to create the container instances:

az container create -g <resource_group_name> -n <container_instance_name> --file output_file  

Create new container instance

15. Azure Container Instances will now begin provisioning with the latest configuration that we have uploaded. Please wait until the status is complete.

Updating container instances

4. Add Environment variables in the App service

1. Go to the App service and navigate to Settings -> Environment variables. Click Add on the right.

Add Env variables

2. Add the following env values and select Apply.

Environment variable 1:

Name: DUCKDB_MOUNT_PATH

Value: /mnt/azure

Environment variable 2:

Name: INFOBRIDGEVISUALWORKER_DEFAULT_MODE

Value: Non-Aks

Update env variable 1

Update env variable 2

3. Click Apply to save the settings.

click 'Apply'

4. Select Confirm to restart the app.

Confirm restart

Ensure all the above steps are completed carefully. With this, you have successfully updated your Inforiver container instances and app service to integrate Infobridge with Inforiver.

ACI Updated

If you encounter any issues or require further support, please get in touch with our technical support team.