# Update Inforiver EDITable Container Instances (for 4.x users) 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: {% code overflow="wrap" %} ```bash az container export -g -n --file output_file ``` {% endcode %} ![Launch Azure CLI and execute the command](/files/2ECZjm3TGgZJ4OE348lC) 2. To download the output file, click on **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](/files/NjWI4CqIEl5HGBpNM9OE) 4. 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. {% hint style="info" %} **Note: Transition from Default Azure Domain to Custom Domain** 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. {% endhint %} #### **i) Inforiver Cron** ```yaml - name: inforiver-cron-container properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: image: turing.azurecr.io/turing-cron: ports: [] resources: requests: cpu: 0.25 memoryInGB: 0.5 ``` #### **ii) Inforiver Audit** ```yaml - name: inforiver-audit-container properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: image: turing.azurecr.io/turing-audit: ports: [] resources: requests: cpu: 0.25 memoryInGB: 0.5 ``` #### **iii) MDM Worker** ```yaml - name: inforiver-mdm-worker-container properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: - name: PRODUCT_BUILD value: mde image: turing.azurecr.io/turing-mdm-worker: ports: [] resources: requests: cpu: 0.5 memoryInGB: 2.0 volumeMounts: - mountPath: name: infofile ``` #### **iv) Inforiver Writeback Worker** ```yaml - name: inforiver-writeback-worker-container properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: image: turing.azurecr.io/turing-writeback-worker: ports: [] resources: requests: cpu: 0.5 memoryInGB: 3.0 ``` #### **v) InfoBridge Writeback Worker** ```yaml - name: inforiver-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: ports: [] resources: requests: cpu: 0.5 memoryInGB: 2.0 volumeMounts: - mountPath: /mnt/azure name: infofile ``` #### **vi) InfoBridge Transformation Worker** ```yaml - name: inforiver-infobridge-transformation-worker 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: ports: [] resources: requests: cpu: 1 memoryInGB: 2.0 volumeMounts: - mountPath: /mnt/azure name: infofile ``` #### **vii) InfoBridge Visual Worker** ```yaml - name: inforiver-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 - name: DEFAULT_MODE value: Non-Aks image: turing.azurecr.io/turing-visual-worker: ports: [] resources: requests: cpu: 0.5 memoryInGB: 2.0 volumeMounts: - mountPath: /mnt/azure name: infofile ``` #### **viii) InfoBridge Engine Worker** ```yaml - name: inforiver-infobridge-engine-worker properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: - name: DUCKDB_MOUNT_PATH value: /mnt/azure - name: SERVER_MODE value: engine image: turing.azurecr.io/turing-infobridge-engine: ports: - port: 9006 protocol: tcp resources: requests: cpu: 0.5 memoryInGB: 4.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** ```yaml - name: inforiver-writeback-worker-container-1 properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: image: turing.azurecr.io/turing-writeback-worker: ports: [] resources: requests: cpu: 0.5 memoryInGB: 3.0 ``` #### **ii) Inforiver Auto Writeback Worker** ```yaml - name: inforiver-auto-writeback-worker-container properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: - name: IS_AUTO_WRITEBACK_CONTAINER value: Y image: turing.azurecr.io/turing-writeback-worker: ports: [] resources: requests: cpu: 0.25 memoryInGB: 2.0 ``` #### **iii) Inforiver Visual Worker** ```yaml - name: inforiver-visual-worker-container properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: image: turing.azurecr.io/turing-visual-worker: ports: [] resources: requests: cpu: 0.25 memoryInGB: 2.0 ``` #### **iv) Inforiver ETL Worker** ```yaml - name: inforiver-etl-worker-container properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: image: turing.azurecr.io/turing-etl-worker: ports: [] resources: requests: cpu: 0.25 memoryInGB: 1.0 ``` #### **v) Inforiver Comment Worker** ```yaml - name: inforiver-comment-worker-container properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: - name: SERVICE_NAME value: "commentWorker" image: turing.azurecr.io/turing-worker: ports: [] resources: requests: cpu: 0.25 memoryInGB: 1.0 ``` #### **vi) Inforiver Worker** ```yaml - name: inforiver-worker-container properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: image: turing.azurecr.io/turing-worker: ports: [] resources: requests: cpu: 0.25 memoryInGB: 2.0 ``` #### vii) EDITable Visual Worker ```yaml - name: editable-visual-worker-container properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: - name: PRODUCT_BUILD value: mde image: turing.azurecr.io/turing-visual-worker: ports: [] resources: requests: cpu: 0.25 memoryInGB: 3.0 ``` ### **Containers Instance List - 3** The following are the set of containers required for the Inforiver EDITable deployment of Azure container instance - 3. #### i) Inforiver Data Input Engine Worker ```yaml - name: inforiver-datainput-engine-worker-container properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: - name: DUCKDB_MOUNT_PATH value: - name: PORT value: 9007 - name: SERVER_MODE value: ccv image: turing.azurecr.io/turing-infobridge-engine: ports: - port: 9007 protocol: TCP resources: requests: cpu: 0.5 memoryInGB: 2.0 volumeMounts: - mountPath: name: infofile ``` #### **ii) Inforiver Orchestrator** ```yaml - name: inforiver-orchestrator-container properties: configMap: keyValuePairs: {} environmentVariables: - name: ADMIN_PORTAL_URL value: image: turing.azurecr.io/turing-orchestrator: ports: [] resources: requests: cpu: 0.25 memoryInGB: 1.0 ``` 5. After adding the container configurations to all instances, verify these steps again in each container's settings. 6. 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. 7. Remove the IP configuration section from the configuration file for the first two ACIs.

Remove the IP configuration

8. Provide the storage account details in the volume section for the first and the third container instances only. ```yaml volumes: - azureFile: shareName: storageAccountName: storageAccountKey: name: ``` **Note**: Storage account keys can be obtained from the respective storage account's **Access keys** section. ![Storage account - access key](/files/vGGR7WowbiNukQaS59ZY) 9. Update the API version as specified below. apiVersion: '2023-02-01-preview' ## **2. Create ACI** We need to separate the ACI into three container instances. * First, add the initial set of **InforiverEditable** containers from the [containers instance list-1](#containers-instance-list-1) into one configuration file and create the first ACI with a name, say **inforivercontainerinstance1.** * Then, add the second set of **InforiverEditable** containers from the [containers instance list-2](#containers-instance-list-2) in another configuration file and create the second ACI, say **inforivercontainerinstance2.** * Add the third set of **InforiverEditable** containers from the [containers instance list-3](#containers-instance-list-3) in a configuration file and create the third ACI, say **inforivercontainerinstance3.** After adding all the containers in the configuration files, execute the following commands in the Azure CLI to create three separate container instances. {% code overflow="wrap" %} ```bash az container create -g -n --file output_file1 ``` {% endcode %}

Create container instance 1

{% code overflow="wrap" %} ```bash az container create -g -n --file output_file2 ``` {% endcode %}

Create container instance 2

{% code overflow="wrap" %} ```bash az container create -g -n --file output_file3 ``` {% endcode %}

Create container instance 3

The CNI will start provisioning with the latest configuration. Please wait until the status is complete. After updating the ACIs to the latest configuration, update the app service's environment variables with the IP addresses of the **first** and **third** container instances. 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:** `:9007` * **Name:** `IR_ENGINE_ENDPOINT`\ **Value:** `:9007`

Update the app service's environment variables

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. If you encounter any issues or need further assistance, please contact our technical support team [here](https://inforiver.com/contact-us/). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.inforiver.com/inforiver-enterprise-on-prem/upgrade/for-legacy-versions-updating-container-instances/update-inforiver-editable-container-instances-for-4.x-users.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.