BCD2HDMS QC, Configuration, and Export Software

This software is always changing... (improving...)

This page covers the details of installing the conversion software. Occasionally, the software will be updated, and you may need to consult this page again to update your software. If you are performing an update (as opposed to a fresh installation), please see the Update Software section further below.

1. Create an 'hdms' subdirectory under the arev subdirectory.
2. Unzip the configuration package to the arev\hdms subdirectory (as of this writing, it is HCFG007a.ZIP). When it completes, you should have several files in an arev\hdms\ini subdirectory, as well as a few other zip and .JAR files in an arev\hdms\java\lib subdirectory.
3. Log into your production BCD or the static snapshot, depending on where you are in the preparation checklist. If you are logging into your production BCD, make sure no one else is logged in.
4. At TCL, execute RUN DOS C:\TEMP\BCD2HDMS\INSTALL, take the defaults at the prompts.
5. When the installation finishes, it will open the error log in Notepad. Scan it for ERROR or WARNING conditions--ignore any WARNINGS about files that are not in your BCD System.
6. On the machine that will be doing the final XML data dump for the data conversion, install or make sure you have the Java Runtime Environment version 1.4.1_02 or higher. Use the "International" version (not the "United States Only" version). As of this writing, the installation file to download is called j2re-1_4_1_02-windows-i586-i.exe (the "-i" at the end of the name indicates that it is the internationalized version); this file about 10MB.

   Try http://java.sun.com/j2se/downloads.html to download the latest release. After selecting the latest release, choose Windows (all languages) for the "International" version. If that link is broken, go to http://java.sun.com and click on "J2SE" and navigate to the downloads.

   CAUTION: If your computer uses an ATI Radeon video driver, make sure you install version 1_4_1_02 or higher. This driver has a known conflict with some earlier versions of Java.

7. Go on to the ConfigureTheSystem step (also known as the QC procedures).

The goal in updating software is to preserve your configurations while obtaining the latest software enhancements.

1. Rename the hdms\ini subdirectory to hdms\ini_bak.

   Typically, you only need to back up the custom.cfg file. The only reason to back up any other file is if you had special conversion issues and your Biotics 4 Installation Contact/Support person advised you to modify other files in this subdirectory.

2. Rename the hdms\java subdirectory to hdms\java_bak.

   Typically, you only need to back up the biotics_connection.xml file, and even then, it's only if you had to run an update after you've already exported data from a snapshot as a test-conversion.

3. Delete the contents of the hdms\symbolic subdirectory. This is absolutely imperative. This subdirectory holds the program that runs the REBUILD_SYN_FILE program as well as several helper symbolic fields--symbolic fields that probably exist in many BCD Systems and are only supplied in case your system is missing them. If this subdirectory is not cleared out, old software may be re-installed making the update only partially effective.
4. Unzip the configuration package to the arev\hdms subdirectory (HCFG007?.ZIP). When it completes, you should have several files in an arev\hdms\ini subdirectory, as well as a few other zip and .JAR files in an arev\hdms\java\lib subdirectory.
5. Log into the BCD (if you are running the final conversion, this will be the static snapshot).
6. At TCL, execute RUN DOS C:\TEMP\BCD2HDMS\INSTALL, take the defaults at the prompts.
7. When the installation finishes, it will open the error log in Notepad. Scan it for ERROR or WARNING conditions--ignore any WARNINGS about files that are not in your BCD System.

   KNOWN ISSUE: During an update (as opposed to a fresh installation), the log file that opens is very confusing. The information you should look for is at the very bottom of the file. If you end up doing several updates and find this to be highly annoying, you may want to delete the contents of the log file after you review it.

8. Notwithstanding the recommendation below, overwrite the following new files using your backup copies (this is necessary only if you have made configuration changes to these files):
   • arev\hdms\ini\custom.cfg
   • arev\hdms\java\biotics_connection.xml

   As a general recommendation, you are advised to use your backup copies of the INI and JAVA files as reference only. This is because the INI files may have been updated with new sections. Therefore, you need to move your configurations from the backup into the new files.

   However, if the version number of the configuration has not changed (e.g., if you are downloading a "006" version to update a previous "006" version), you may safely copy the arev\hdms\ini_bak\custom.cfg file to the arev\hdms\ini\ subdirectory. You may also copy your modified version of the arev\hdms\java_bak\biotics_connection.xml to the arev\hdms\java\ subdirectory.

   As for the hdms_es.ini & hdms_xml.ini, it is definitely possible that these have changed. If you KNOW you have made edits to these files, you should re-make them to the new copies since updates to these files are usually critical and unwise to override.

Back to RunningTheDumpForAnNHP