Device-ManageR-to-Room-Alert-Manager Import Tool – AVTECH https://avtech.com/articles Frequently Asked Questions Tue, 22 Nov 2022 19:36:01 +0000 en-US hourly 1 https://wordpress.org/?v=6.2.2 How To Use The Device-ManageR-to-Room-Alert-Manager Import Tool (Legacy) https://avtech.com/articles/19676/how-to-use-the-device-manger-to-room-alert-manager-import-tool/ Tue, 24 Nov 2020 20:46:28 +0000 https://avtech.com/articles/?p=19676 The post How To Use The Device-ManageR-to-Room-Alert-Manager Import Tool (Legacy) appeared first on AVTECH.

]]>

This legacy tool was removed from Room Alert Manager in v2.3.1.

What to expectHow to run the Import ToolWhere to look in Room Alert Manager for imported items

Please read the information below so that you know what to expect from the Import Tool.

The Device ManageR source folder

You can import from one of two different Device ManageR source folders:

  1. Your Device ManageR v6.3.6 program installation folder.
    • This is the easiest option. You can use this option if your Device ManageR writes to the default  embedded H2-type database that comes with the program.
    • By default, Device ManageR’s installation folder is:
      • C:\Program Files (x86)\AVTECH Device ManageR (on 64-bit Windows computers)
      • C:\Program Files\AVTECH Device ManageR (on 32-bit Windows computers)
  2. A custom folder that you put together than has just the required files from Device ManageR v6.3.6.
    • You must use this option if you configured your Device ManageR to write to an external database (MySQL, SQL Server or Postgres).
    • Please note that Room Alert Manager currently only supports its own embedded database. It does not support external databases.

For instructions for the custom folder, please see our FAQ, How to Make a Custom Device ManageR Folder for the Room Alert Manager Import Tool.

The software you need

You need the following software for the import:

  1. Your existing Device ManageR installation, which must be on v6.3.6 before you begin.
  2. The latest version of the Device-ManageR-to-Room-Alert-Manager Import Tool.
  3. The latest version of Room Alert Manager.
  • Device ManageR v6.3.6
  • Device-ManageR-to-Room-Alert-ManageR Import Tool
    • Available in Room Alert Manager’s Installation Directory.
  • Room Alert Manager
    • Available on the Downloads page.
    • Requires a Professional (or higher) level account.

If your Device ManageR is on a lower version, update to v6.3.6 before you begin. For instructions, please see our FAQ, How To Install Device ManageR.

Where that software should be installed
  • The Import Tool must be installed on the same computer as Device ManageR.
  • Room Alert Manager may be installed on the same computer or a different computer on your network.
    • Room Alert Manager must be installed and running when you initiate an import.

You must have Windows administrator privileges on the computers that host the Import Tool and Room Alert Manager.

What the Import Tool imports

The Import Tool imports configurations from Device ManageR v6.3.6 that are compatible with Room Alert Manager. It does not import your historical sensor and alert data.

The following items are imported:

  1. From your Alerts/Tasks tab:
    • From Contacts: email addresses (including email-to-SMS addresses).
      • Those email addresses become “Notify” Actions in Room Alert Manager.
      • Those “Notify” Actions have the name you gave the Contact record in Device ManageR.
    • From Alerts: alerts that meet the following criteria.
      • The alert is on a sensor supported by Room Alert Manager.
      • That sensor is on a device that is supported by Room Alert Manager.
    • From Action/Notification Lists that are attached to the imported alerts:
      • The “Send Email to Configured Contact” action items.
      • Any “Perform the Action after X seconds” delays on those actions.
  2. From your Settings tab:
    • These Discovery settings:
      • Discovery Scan Interval
      • Auto Discovery Timeout
      • Manual Discovery Timeout
      • Data Refresh Interval
      • Disable Auto Discovery
      • Missed Scans Before Disabling Devices
    • Your SMTP Email settings for Primary and Secondary Mail Servers (except the Test Email Recipient).
    • Your Blocked devices
  3. From the Device Status –> Advanced Discovery Options –> Manually Add Devices via IP Address feature: your manually-discovered IP addresses.
  4. From your Device ManageR database: the following information so that Room Alert Manager knows what device and sensor your imported Alerts go with:
    • The MAC address and device model that an imported alert points to
    • The sensor type, channel, and port that the imported alert points to (Example: Temperature & Humidity Sensor, Heat Index, Ext Sensor 2)

Please note that the devices and sensors themselves are not imported into Room Alert Manager—just information about them to complete an Alert.

No other items are imported by the Import Tool.

You must have Windows administrator privileges to install and run the Import Tool.

Before you begin…

Step 1: Run the Import Tool
  1. Locate the Import Tool within Room Alert Manager’s installation directory (C:\Program Files\AVTECH Room Alert Manager\adm2ram by default).
  2. Click (or double-click) on the AVTECH-ADM2RAM-import-tool-vX.X.X.exe file.
  3. If the User Account Control dialog box appears, select Yes to continue.
  4. The Windows Command Prompt opens to the following screen:
Step 2: Answer the prompts.
  1. Answer the 6 prompts that appear. The prompts ask you these questions:
    • What folder are you importing from?
    • What is the path to that folder?
    • Is Room Alert Manager on this computer? (If not, what is the IP address or computer name of Room Alert Manager’s host computer?)
    • What HTTP port is Room Alert Manager using?
    • Enter the username of any Admin-level user in Room Alert Manager.
    • Enter password for that user.

As much as possible, answer choices are spelled out for you on-screen so that you simply pick the correct one. Some things you will have to type in yourself. For example, if Room Alert Manager is installed on a different computer than the Import Tool, you will have to type out the IP address or computer name of that system.

  1. After you enter the last answer, a summary of your choices will appear. Read it to make sure your choices are correct.
  2. If you are satisfied with your choices, enter “y” to run the import. (If not, enter “n.” The command prompt will close. You can restart by opening the program through the Start menu.)
  3. Once you enter “y,” the import begins and the results print onscreen. You’ll see the imported items and a confirmation message at the end.
  4. Press the Enter key to close the screen. You are done with the Import Tool.

If you run the Import Tool again, the same Alerts and Actions will be added a second time (and a third time, a fourth time, etc). The duplicate Alerts and Actions will need to be deleted from Room Alert Manager.

Open Room Alert Manager in your browser. By default, you can open it a localhost:9393 or IPAddress:9393 (example 192.168.2.123:9393) in your browser’s address bar.

Navigate to:

  • Alerts –> Alerts to view your imported Alerts and the associated imported Actions.
  • Alerts –> Actions to view your imported email Contacts. (Remember that email Contacts become Actions in Room Alert Manager.)
  • Settings –> Discovery to view your imported Discovery settings, Blocked devices and manually-discovered IP addresses.
  • Settings –> Email to view your imported SMTP Email settings.

The post How To Use The Device-ManageR-to-Room-Alert-Manager Import Tool (Legacy) appeared first on AVTECH.

]]>
How to Make a Custom Device ManageR Folder for the Room Alert Manager Import Tool (Legacy) https://avtech.com/articles/19679/how-to-make-a-custom-device-manager-folder-for-the-room-alert-manager-import-tool/ Tue, 24 Nov 2020 17:25:03 +0000 https://avtech.com/articles/?p=19679 The post How to Make a Custom Device ManageR Folder for the Room Alert Manager Import Tool (Legacy) appeared first on AVTECH.

]]>

This legacy tool was removed from Room Alert Manager in v2.3.1.

Before you start: Preview the custom folder contents.

The folder you create will look as shown below.

  • The root folder, here called “Custom_DeviceManageR_Source_Folder,” will contain 7 files from Device ManageR’s “conf” folder.
7 files (xml and txt) from Device ManageR’s “conf” folder
  • A sub-folder, which must be called “db,” will contain the SENSORS and DEVICES tables from your Device ManageR database.
2 exported Device ManageR database tables in csv format
Step 1: Stop the Device ManageR service.

Stop the Device ManageR service. This FAQ shows you how: How To Stop, Start And Restart The Device ManageR Service.

Step 2: Copy and paste 7 files from Device ManageR's conf folder.

On Device ManageR’s host computer:

  1. Create an empty folder some place easy to remember, like Documents or your Desktop. Call the folder whatever you want. (You could call it, for example, “Custom_DeviceManageR_Source_Folder.”)
  2. In Windows Explorer, navigate to Device ManageR’s installation folder. By default, this folder is located at:
    • C:\Program Files (x86)\AVTECH Device ManageR (on 64-bit Windows computers)
    • C:\Program Files\AVTECH Device ManageR (on 32-bit Windows computers)
  3. First, copy and paste the just the required “conf” folder files.
  4. Locate and open the “conf” folder.
  5. Copy just the 7 files listed below and paste them into your source folder:
    • action_schedules.xml
    • actions.xml
    • alerts.xml
    • blacklist.txt
    • contacts.xml
    • settings.xml
    • tcphostlist.txt
  6. Now create a sub-folder in your source folder. Name it “db.” (It MUST be called that.) You’ll need this sub-folder for the next step, where you export 2 tables from your Device ManageR database.
Step 3: Export the SENSORS and DEVICES tables from your Device ManageR database.

Follow the instructions below to export your SENSORS and DEVICES tables to csv files and put them into your “db” sub folder.

How to Export from MySQLHow to Export from SQL ServerHow to Export from Device ManageR v6.3.6 Embedded H2 Database
  1. Open MySQL Workbench.
  2. Open a New Query tab. Enter and execute this query:
    • Use devicedb
  3. Open another New Query tab.
    • Enter and execute this query: Select * from sensors
    • In the output toolbar, select the Export recordset to an external file button.
    • Call the file SENSORS.csv. (It MUST be named that.)
    • Save it to the “db” sub-folder inside your custom Device ManageR source folder.
  4. Open a third New Query tab.
    • Enter and execute this query: Select * from devices
    • In the output toolbar, select the Export recordset to an external file button.
    • Call the file DEVICES.csv. (It MUST be named that.)
    • Save it to the “db” sub-folder inside your custom Device ManageR source folder.
  1. Open Microsoft SQL Server Management Studio.
  2. Open a New Query.
    • Enter and execute this query: SELECT * FROM [DeviceDB].[dbo].[SENSORS]
    • In the Results panel, right-click on any of the column headers and select Save Results As…
    • Call the file SENSORS.csv. (It MUST be named that.)
    • Save it to the “db” sub-folder inside your custom Device ManageR source folder.
  3. Open another New Query.
    • Enter and execute this query: SELECT * FROM [DeviceDB].[dbo].[DEVICES]
    • In the Results panel, right-click on any of the column headers and select Save Results As…
    • Call the file DEVICES.csv. (It MUST be named that.)
    • Save it to the “db” sub-folder inside your custom Device ManageR source folder.

Typically, you do not need to create a custom folder if you are importing from a Device ManageR v6.3.6 that writes to the embedded H2 database. You can point the Import Tool directly at your Device ManageR installation folder.

However, if your situation requires it, you can follow these steps to export the SENSORS and DEVICES tables from your embedded database into the “db” subfolder you created earlier.

Step 1: Download and install the H2 Database Engine Console.

  1. In your browser, go to https://www.h2database.com/html/main.html
  2. In the Download section, select Windows Installer.
  3. Run the installer. Keep the default options.

Step 2: Open the console and test its connection to Device ManageR.

  1. Open the H2 console by navigating in Windows to StartH2H2 Console.
  2. The Login page of the console opens. Leave everything on that page at defaults except JDBC URL . . .
  3. In JDBC URL, enter “jdbc:h2:file:” followed by the full path to Device ManageR’s installation folder.
    • Use forward slashes (“/”), not back slashes (“\”) between the folders.
    • Here is an example:
      • jdbc:h2:file:C:/Program Files (x86)/AVTECH Device ManageR/DeviceDB/DeviceDB
  4. Then select Test Connection.
  5. Confirm that you see the Test successful message at the bottom of the window.

Step 3: Connect to the database and export the files.

  1. Select Connect.
  2. Your embedded H2 database opens in your browser.
  3. In the SQL statement box (under the Run button):
    • Enter these 2 commands:
      • call CSVWRITE (‘path to the db sub-folder/SENSORS.csv’, ‘SELECT * FROM SENSORS’);
      • call CSVWRITE (‘path to the db sub-folder/DEVICES.csv’, ‘SELECT * FROM DEVICES’);
    • Here is an example. (Be sure to put forward-slashes “/” between the folders, not back slashes “\”.)
      • call CSVWRITE (‘C:/Users/Laptop/Documents/Custom_DeviceManageR_Source_Folder/db/SENSORS.csv’, ‘SELECT * FROM SENSORS’ );
      • call CSVWRITE (‘C:/Users/Laptop/Documents/Custom_DeviceManageR_Source_Folder/db/DEVICES.csv’, ‘SELECT * FROM DEVICES’ );
  4. Select Run. Notice the confirmation messages below the commands.
  5. Then check your “db” sub-folder–the CSV files should be there.

Once you have your source folder ready, you may run the Device-ManageR-to-Room-Alert-ManageR Import Tool and point it at that folder.

The post How to Make a Custom Device ManageR Folder for the Room Alert Manager Import Tool (Legacy) appeared first on AVTECH.

]]>