Q13627 and the Dispatcher (Q12497) are Designed to Work Together

There is a WIMS Cache output profile that is used to pull data from OPS DATA XML File Format, Revision 3 specification, and place that data into a SQL Server Cache table set (a set of tables assigned only to the caching process).  The Q13627 interface and the Q13628 Browser are designed to be used with this Cache exclusively. See KB Article 13630: Source Version tested for a database schema diagram.

The parts of the WIMS Cache System are:

• Source Configuration - in this case the source is XML files conforming to the OPS DATA XML File Format, Revision 3 format. They are placed in a folder specified by the user in the Dispatcher/Profile that is watched for files to be added to it.  When an XML file is added to the monitored folder the Profile tries to load its data into the cache.
  
• Dispatcher - a windows service from Hach that can coordinate several profiles
  
• Each profile specifies a source and a target. The application that allows the user to configure the source and target has an interface of three tabs.  One allows the user to set general data and the other two allow the user to specify the source and target. The input source always results in supplying an XML file to the target configuration. The WIMS Cache target in the Dispatcher is designed to accept OPSDATAXML Revision 3 files and place that data into the Cache table structure.
  
• The Create Cache button on the Target Setup tab provides the ability to create the tables for the cache in any SQL Server 2005 or later database.
  
• Cache - the Cache is a set of tables outlined in KB Article 13630: Source Version tested.
  
• Q13627 Interface - this is a Hach WIMS interface designed to move data from the Cache to a WIMS database.
  
• WIMS Database - This is a standard Oracle or SQL Server database use by WIMS.
• The variable configuration is where the Profile:Server:Tag values are entered (using colons to separate the fields).  There is an interface browser that allows the user to select the values and helps ensure a correct tag is placed in the variable setup the first time. The Browser reads the profile, server and tag data from the Cache database in realtime, so as soon as the first XML is read by the Dispatcher there is data to pick from in the browser.

Figure 1 - An example of the Dispatcher Caching system with notes:

Figure 2 - The simplest layout for the Dispatcher Cache system:

Figure 3 - Another example of how the cache system can be configured:

Figure 4 - The caching system using a custom import process from the customer: