Tables

Overview

Data related to the application is stored in the storage account on either Tables or the Blob Storage. Some configuration resides in Tables and you must populate for proper functioning.

You can access the created storage either through the Storage Explorer or through the explorer within Azure Portal.

For more information on Tables, see Table storage.

Deployments

In the deployments table, insert data according to versioning and access.

For example, if the IBM Process Mining is version 1.12.X, then enter the data in the table in the following format:

{
    PartitionKey: "1.12" # just major-minor version
    RowKey: "default"
    url: "https://<url-to-requestJob-function>"
}

The url in the format refers to the complete URL with code to the requestJob function within the mlplatform Function App.

Note: You must deploy the function before populating the data in the table.

Router

In the gandalf table, ensure to insert data according to versioning and access.

For example, if the IBM Process Mining is version 1.12.X and the domain you are serving it on https://processmining.mydomain.com/, then enter the data in the table in the following format:

{
    PartitionKey: "processmining.mydomain.com" # strip the domain
    RowKey: "1.12" # just major-minor version
    apikey: "user-api-key" # created technical user api key on Process Mining
    user: "user-name" # created technical user username on Process Mining
    deployment: "default"
}