Thickness Monitoring Upgrade

1. Access the TM Dataloggers page.
2. In the Select TMLs pane, select the check box next to a TML, and then select Apply.
3. Select Send To Device.
   Note: A datalogger does not need to be connected.

   The Meridium Device Service Not Found window appears.
4. Select the Download link.
   MeridiumDevices.exe is downloaded.
5. Run MeridiumDevices.exe, and then follow the instructions in the installer.
   The Meridium Device Service is installed.
6. In the Meridium Device Service Not Found window, select Continue.
   Dataloggers can now be used with Thickness Monitoring.

After the database upgrade for APM, if the entity key fields are of the type string, you must modify the catalog query parameters to use the correct type by performing the following steps.

1. Access the Query page.
2. Select Browse.
   The Select a query from the catalog window appears.
3. Navigate to the folder containing the query that you want to update, and select the link for the query.
   The Results workspace appears.
4. Select the SQL tab.
   The SQL workspace appears, where you can modify the SQL code.
5. Modify all the entity key numeric parameters to key.
   For example, (? :n) must be updated to (? :k).
6. Select Save.
   The modified query is saved.

This action is required only if you have modified the Thickness Monitoring queries.

1. Access the Catalog page.
2. Navigate to the Public folder for the query that you want to revert.
   For Thickness Monitoring, the public queries are stored in the following folder:
   Public/Meridium/Modules/Thickness Monitoring/Queries
3. Select the check box next to the query that you want to revert, and then select .
   The Confirm Delete window appears, asking you to confirm if you want to delete the selected query.
4. Select OK.
   The selected query is deleted.
5. Navigate to the Baseline folder for queries.
   For Thickness Monitoring, the baseline queries are stored in the following folder:
   Baseline/Meridium/Modules/Thickness Monitoring/Queries
6. Select the check box next to the query that you want to revert, and then select .
   The Catalog Folder Browser window appears.
7. Navigate to the folder containing the public query that you deleted in step 3.
8. Select OK.
   A success message appears indicating that the selected item has been copied successfully.
9. Repeat Steps 2-8 for each query that you want to revert to baseline.

The MIExecution Service,on each APM Server serves RBI, Inspection and Thickness Monitoring module queues. This service is configured to use a single shared ActiveMQ queue service across APM. Available queue configuration options include retries and concurrency limit.

1. On the APM Server, access the folder that contains the MIExecution Service files.
   Note: If you have installed APM in the default location, you can locate the folder in C:\Program Files\Meridium\ApplicationServer\mi-execution
2. Access the appsettings.json file in an application that can be used to modify JSON files (for example, Notepad++).
3. In the file, locate the following text:

   "Queue_Config": {
   	    "Queues": [
   	      {
   	        "Name": "MI_TM_Queue", 
   	        "ConcurrencyLimit": 100,
   	        "Retries": 5,
                  "LimitPerTenantRequired": true
   	      }
   	    ]
             }

   Note: ConcurrencyLimit indicates the maximum number of messages that will be consumed concurrently. Retries indicates the number of times it retries to send the messages to ActiveMQ if it fails. LimitPerTenantRequired indicates whether Maximum Concurrency limit per Tenant is specified in scheduler service for the queue.
4. Update the key values as desired.
5. Save and close the file.
   The updated settings will be applied when the MIExecution Service is stopped and restarted.