This section provides information on migration phases for Engage Analytics.
You can understand how to:
- Read the output of the migration process.
- Use the Spark UI.
- Explore the target database of the migration process.
- Explore the target database of the Engage Analytics processor run.
Understanding the Engage Analytics Migration Output
The ESRPipeline.jar file performs the following functions as orchestrated by the migrate.cmd script:
- Migrates data from the source landing (ldg) database to the target ldg database. This operation also includes populating the anl_dim_users table and the anl_dim_sources table, which are not part of the landing data in Engage Reporting 1.0.25.
- Runs the Engage Analytics processors to load the migrated data from the ldg tables into the vocera_analytics tables.
The command prompt window displays the following counts while the migration process runs:
- Input records found in the source database for a given table.
- Records from the source database that are already available in the migration target.
- Input records within the specified date range, or within the default date range if none is specified.
- New records to be inserted into the migration target database
The following screenshot displays an example migration run:
The command prompt window displays the following information when the Engage Analytics processors run:
- The name of the landing table being processed.
- The count of records in the source database.
- The count of records within the specified date range, or within the default date range if none is specified.
- The code fingerprint (MD5 hash) for the running Engage Analytics processor.
- The database configuration for the running Engage Analytics processor.
The following screenshot shows an example run of the Engage Analytics processors:
The loaded data is available in vocera_analytics database.
Using the Spark UI to track progress
The Spark user interface (UI) can be used to track the progress of the migration and processors. If the migrate.cmd script is running, you can browse to http://localhost:4040 to view the status information related to the Spark engine that performs the migration.
The following screenshot corresponds to the progress crawler that displays at the bottom of the output for each migration activity.
The following screenshot displays the Spark UI.
Exploring the Target Database of the Migration Process
The migration target is the MariaDB database on the server where Vocera Analytics is installed. The landing ldg database is where the records are copied when the migration is complete. To explore the migrated data, use the HeidiSQL tool that is installed with the MariaDB database. You can create a connection with the authentication credentials you specified during the installation procedure to perform this task, as shown in the following screenshot.
Exploring the Target Database of the Engage Analytics Processor Run
The target of the processor is the MariaDB database on the server where Vocera Analytics is installed. The vocera_analytics database and the tables named with an anl_ prefix are populated when the Vocera Analytics processors complete the task To explore the data populated by the processors, use the HeidiSQL tool that is installed with MariaDB database, as shown in the following screenshot.
