Update Inforiver EDITable Container Instances (for V4.6.x.x and above)

This guide details the required steps to update Inforiver Editable container instances within an Azure on-premises environment. Please follow these instructions carefully to ensure a smooth and successful update that incorporates the latest features.

1. Edit the CNI Configuration

1. Open your Azure CLI window and run the following command:

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

Launch Azure CLI and execute the command

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

Download the output file

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

Download locally

1. A secret environment variable with a minimum length of 32 characters is configured across all containers within the container instance. The secret should be generated as a secure alphanumeric value using a password generator.

• Example Value: dEvMOiJTIfjb5U1TVzzQhts2WLQR4GC1

Add the SECRET environment variable

1. Provide the username and password for pulling the image from the registry. You would have received this information during the initial deployment. If not, please get in touch with our support team.

2. Remove the IP configuration section from the configuration file for the ACI.

Remove the IP configuration

1. Provide the storage account details in the volume section for the container instance.

volumes:
  - azureFile:
      shareName: <fileshare_name>
      storageAccountName: <storage_account_name>
      storageAccountKey: <storage_account_primary_key>
    name: <volume_name>

Note: Storage account keys can be obtained from the respective storage account's Access keys section.

Storage account - Access key

1. Please update the API version as specified below.

apiVersion: '2023-02-01-preview'

1. Now configure the below-listed container configurations in this file for Inforiver EDITable container deployment.

Containers Instance List

The following is the set of containers required for the Inforiver deployment of the Azure Container Instance.

Note: Transition from Default Azure Domain to Custom Domain

When transitioning to a custom domain (e.g., https://webapp.inforiver.com) from the default Azure domain (e.g., https://webapp.azurewebsites.net), it is necessary to update the URL in the configuration settings of both the Azure App Service and the associated Container Instances. Specifically, ensure the environment variable ADMIN_PORTAL_URL is updated to reflect the new custom domain in both services.

1. inforiver-cron-container

- name: inforiver-cron-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: SECRET
        secureValue: <Secret_Value>         
      image: turing.azurecr.io/turing-cron:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 0.5

2. inforiver-audit-container

- name: inforiver-audit-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: SECRET
        secureValue: <Secret_Value>         
      image: turing.azurecr.io/turing-audit:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 0.5

3. inforiver-writeback-worker-container

- name: inforiver-writeback-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: SECRET
        secureValue: <Secret_Value>         
      image: turing.azurecr.io/turing-writeback-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 3.0

4. inforiver-infobridge-writeback-worker

- name: inforiver-infobridge-writeback-worker
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: PRODUCT_BUILD
        value: inforiver
      - name: LISTENER_MODE
        value: dataflow
      - name: SECRET
        secureValue: <Secret_Value>         
      image: turing.azurecr.io/turing-writeback-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 2.0
      volumeMounts:
      - mountPath: /mnt/azure
        name: infofile

5. inforiver-infobridge-transformation-worker

- name: inforiver-infobridge-transformation-worker
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: PRODUCT_BUILD
        value: inforiver
      - name: SERVICE_NAME
        value: infobridgeTransformationWorker
      - name: SECRET
        secureValue: <Secret_Value>              
      image: turing.azurecr.io/turing-datasource-integration-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 1.0
          memoryInGB: 2.0
      volumeMounts:
      - mountPath: /mnt/azure
        name: infofile

6. inforiver-infobridge-visual-worker

- name: inforiver-infobridge-visual-worker
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: PRODUCT_BUILD
        value: inforiver
      - name: SERVICE_NAME
        value: infobridgeVisualWorker
      - name: VISUAL_WORKER_LISTENER_MODE
        value: dataFlowSourceIntegration
      - name: DEFAULT_MODE
        value: Non-Aks
      - name: SECRET
        secureValue: <Secret_Value>              
      image: turing.azurecr.io/turing-visual-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 2.0
      volumeMounts:
      - mountPath: /mnt/azure
        name: infofile

7. inforiver-infobridge-engine-worker

- name: inforiver-infobridge-engine-worker
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: DUCKDB_MOUNT_PATH
        value: /mnt/azure
      - name: SERVER_MODE
        value: engine
      - name: SECRET
        secureValue: <Secret_Value>              
      image: turing.azurecr.io/turing-infobridge-engine:<tag>
      ports:
        - port: 9006
          protocol: tcp
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 4.0
      volumeMounts:
      - mountPath: /mnt/azure
        name: infofile

8. inforiver-writeback-worker-container-1

- name: inforiver-writeback-worker-container-1
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: SECRET
        secureValue: <Secret_Value>              
      image: turing.azurecr.io/turing-writeback-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 3.0

9. inforiver-auto-writeback-worker-container

- name: inforiver-auto-writeback-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: IS_AUTO_WRITEBACK_CONTAINER
        value: Y
      - name: SECRET
        secureValue: <Secret_Value>              
      image: turing.azurecr.io/turing-writeback-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 3.0

10. inforiver-visual-worker-container

- name: inforiver-visual-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: SECRET
        secureValue: <Secret_Value>              
      image: turing.azurecr.io/turing-visual-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 2.0

11. inforiver-etl-worker-container

- name: inforiver-etl-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: SECRET
        secureValue: <Secret_Value>              
      image: turing.azurecr.io/turing-etl-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 1.0

12. inforiver-comment-worker-container

- name: inforiver-comment-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: SERVICE_NAME
        value: "commentWorker"
      - name: SECRET
        secureValue: <Secret_Value>              
      image: turing.azurecr.io/turing-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 1.0

13. inforiver-worker-container

- name: inforiver-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: SECRET
        secureValue: <Secret_Value>              
      image: turing.azurecr.io/turing-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 3.0

14. inforiver-datainput-engine-worker-container

- name: inforiver-datainput-engine-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: DUCKDB_MOUNT_PATH
        value: <mountpath>
      - name: PORT
        value: 9007
      - name: SERVER_MODE
        value: ccv
      - name: SECRET
        secureValue: <Secret_Value>                          
      image: turing.azurecr.io/turing-infobridge-engine:<tag>
      ports:
        - port: 9007
          protocol: TCP
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 2.0
      volumeMounts:
      - mountPath: <mountpath>
        name: infofile 

15. inforiver-orchestrator-container

- name: inforiver-orchestrator-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: SECRET
        secureValue: <Secret_Value>              
      image: turing.azurecr.io/turing-orchestrator:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 1.0

16. editable-visual-worker-container

- name: editable-visual-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin_Portal_URL>
      - name: PRODUCT_BUILD
        value: mde
      - name: SECRET
        secureValue: <Secret_Value>              
      image: turing.azurecr.io/turing-visual-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 2.0

17. inforiver-mdm-worker-container

- name: inforiver-mdm-worker-container
      properties:
        configMap:
          keyValuePairs: {}
        environmentVariables:
        - name: ADMIN_PORTAL_URL
          value: <Admin_Portal_URL>
        - name: PRODUCT_BUILD
          value: mde
        - name: SECRET
          secureValue: <Secret_Value>           
        image: turing.azurecr.io/turing-mdm-worker:<tag>
        ports: []
        resources:
          requests:
            cpu: 1.0
            memoryInGB: 3.0
        volumeMounts:
        - mountPath: <mountpath>
          name: infofile

After adding the container configurations to all instances, verify the above steps again in each container's settings.

2. Create ACI

After adding all the containers in the configuration files, execute the following commands in the Azure CLI to create the container instance.

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

Create output file

The CNI will start provisioning with the latest configuration. Please wait until the status is complete.

After updating the ACI to the latest configuration, update the app service environment variables with the IP addresses of the container instance. To do this,

1. Navigate to Inforiver App Service > Settings > Environment Variables.

2. Add the following environment variables as shown below and click Apply.

• Name: IB_ENGINE_ENDPOINT

Value: <IP address of the container instance>:9006

Update the app service's environment variables

• Name: IR_ENGINE_ENDPOINT

Value: <IP address of the container instance>:9007

Update the app service's environment variables

1. The secret environment variable configured in the Container Instance also needs to be added as an environment variable in the App Service with the same value.

Add the SECRET as environment variable in the app service

By following the above steps, you will be able to successfully update your Inforiver EDITable container instance. The update brings enhanced features and improvements that will benefit your Azure on-premises environment. Ensure all the above steps are completed carefully, and refer to the provided screenshots for additional assistance.

If you encounter any issues or need further assistance, please contact our technical support team here.

We do support delta template updates, which are more efficient than manual updates; however, implementing them requires assistance from our DevOps team.