Inforiver
On-Prem Inforiver Writeback Matrix
On-Prem Inforiver Writeback Matrix
  • 👋Inforiver Writeback Matrix On-Prem
  • Before You Start
    • đŸĒ„Basic Requirements
    • đŸĨŒEntra ID App
    • 📧SMTP Service
    • đŸ•šī¸Inforiver Credentials
    • đŸ“ŗVirtual Network (Optional)
  • Deployment
    • Microsoft Azure
      • Basics
      • Networking
      • SQL Database
      • Inforiver Workspace
      • SMTP
      • Final Deployment
    • Custom Visual Generation
    • Azure AD App Post Configuration
  • Architecture Concepts
    • Overview
    • O365 Permissions
    • External Connections
    • Azure Cost
  • Upgrade
    • Overview
    • Integrate Infobridge with Inforiver (for 2.x users)
    • Integrate EDITable with Inforiver (for 2.x users)
    • Update Inforiver Container Instances (for 3.x users)
    • Update EDITable Container Instance (for 3.x users)
    • Update Inforiver EDITable Container Instances (for 3.x users)
    • Update Inforiver EDITable Container Instances (for 4.x users)
  • How To Guides
    • Overview
    • Register Inforiver App with Certificate
    • Key Vault Integration
    • Custom Domain and SSL
    • Application Gateway Integration
    • Private App Service
    • Diagnostic Settings
    • Configuring Office 365 SMTP
    • Scaling Up Azure Database
    • Creation and Deletion of Database
    • Enabling App Service Logs
    • Scaling Up the App Service Plan
    • Scaling Redis Cache
    • Update Inforiver License
    • Update Azure AD Client & Other Environment Variables
  • Troubleshooting Steps
    • Overview
Powered by GitBook
On this page
  • 1. Edit the CNI Configuration
  • Containers Instance List - 1
  • Containers Instance List - 2
  • 2. Create ACI
  1. Upgrade

Update Inforiver EDITable Container Instances (for 3.x users)

PreviousUpdate EDITable Container Instance (for 3.x users)NextUpdate Inforiver EDITable Container Instances (for 4.x users)

Last updated 1 month ago

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
  1. To download the output file, click on Manage files -> Download and enter the path of the output file. Click Download.

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

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

Containers Instance List - 1

The following are the set of containers required for the Inforiver deployment of Azure container instance - 1.

Note: Transition from Default Azure Domain to Custom Domain

i) Inforiver Cron

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

ii) Inforiver Audit

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

iii) Inforiver Orchestrator

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

iv) Inforiver Worker

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

v) Inforiver Writeback Worker

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

vi) 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
      image: turing.azurecr.io/turing-writeback-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 2.0
      volumeMounts:
      - mountPath: /mnt/azure
        name: infofile

vii) 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: GRPC_URL
        value: localhost:9006
      image: turing.azurecr.io/turing-datasource-integration-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 1
          memoryInGB: 2.0
      volumeMounts:
      - mountPath: /mnt/azure
        name: infofile

viii) 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
      image: turing.azurecr.io/turing-visual-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 2.0
      volumeMounts:
      - mountPath: /mnt/azure
        name: infofile

ix) 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
      image: turing.azurecr.io/turing-infobridge-engine:<tag>
      ports:
        - port: 9006
          protocol: tcp
      resources:
        requests:
          cpu: 0.5
          memoryInGB: 2.0
      volumeMounts:
      - mountPath: /mnt/azure
        name: infofile

Containers Instance List - 2

The following are the set of containers required for the Inforiver EDITable deployment of Azure container instance - 2.

i) Inforiver Writeback Worker-1

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

ii) Inforiver Auto Writeback Worker

- 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
      image: turing.azurecr.io/turing-writeback-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 2.0

iii) Inforiver Visual Worker

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

iv) Inforiver ETL Worker

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

v) Inforiver Comment Worker

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

vi) MDM Worker

- name: mdm-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      - name: PRODUCT_BUILD
        value: mde
      image: turing.azurecr.io/turing-mdm-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 2.0

vii) EDITable Visual Worker

- name: editable-visual-worker-container
    properties:
      configMap:
        keyValuePairs: {}
      environmentVariables:
      - name: ADMIN_PORTAL_URL
        value: <Admin Portal URL>
      - name: PRODUCT_BUILD
        value: mde
      image: turing.azurecr.io/turing-visual-worker:<tag>
      ports: []
      resources:
        requests:
          cpu: 0.25
          memoryInGB: 3.0
  1. After adding the list of container configurations in both container instances, verify these steps in both container instance configurations.

  2. 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.

  3. Remove the IP configuration section from the configuration file from both ACIs.

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

volumes:
  - azureFile:
      shareName: <filesharename>
      storageAccountName: <storage account name>
      storageAccountKey: <storage account primary key>
    name: <volumename>

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

  1. Update the API version as specified below.

apiVersion: '2023-02-01-preview'

2. Create ACI

We need to separate the ACI into two container instances.

  • First, add the initial set of Inforiver containers into one configuration file and create the first ACI with a name, say inforivercontainerinstance.

  • Then, add the second set of InforiverEditable containers in another configuration file and create the second ACI, say inforivercontainerinstancenew.

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

az container create -g <resource group name> -n <container instance name> --file output_file
az container create -g <resource group name> -n <container instance name> --file output_file1

The CNI will start provisioning with the latest configuration.

Please wait until the status is complete.

By following the above steps, you will be able to successfully update your Inforiver EDITable container instances.

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.

When transitioning to a custom domain (e.g., ) from the default Azure domain (e.g., ), 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.

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

https://webapp.inforiver.com
https://webapp.azurewebsites.net
here
Launch Azure CLI and execute the command
Download the output file
Download locally
Remove the IP configuration
Storage account - access key
Create container instance 1
Create container instance 2