The Dispatcher is optional and is used for dispatching XML data files from source computer systems to the Hach WIMS computer when these two are not on the same computer or network.  The Dispatcher transfers XML data files to the Hach WIMS computer system via File Transfer Protocol (FTP) or Remote (Network) Path or a database cache. If the source data is on the same computer as the Hach WIMS database, then this component is not needed.

In addition, the Dispatcher will accept XML files (of the Hach OPS DATA XML File Format, Revision 3) and move those to a database that has tables conforming to the WIMS Cache schema.  The user can implement this schema in the caching database via by simply clicking on a button in the Dispatcher'd WIMS Cache target setup.

There is an overview of the interfaces including the dispatcher here. Each profile added to the dispatcher must have a source specifed (where to get the xml files) and a target (where to move them to or whare to place their data). Each Dispacher can have more than one profile.

• File Sources
• File System -A simple file copy routine with only a folder for the user to specify (setup)
• SFTP -A file transfer protocal that allows a secure connection (setup)
  The parameters specified include the Host Computer name or IP address, Port,  FTP Path and username and an optional password and private key
• FTP - The standard file transfer protocal (setup)
  The parameters specified include the Host Computer name or IP address, Port, FTP Path and username and an optional password
  
• Target Locations
• File System - A simple file copy routine with only a folder for the user to specify (setup)
• SFTP - A file transfer protocal that allows a secure connection (setup)
• FTP -The standard file transfer protocal (setup)
• WIMS Cache - A database destination that uses a specific set of tables (used with the Q13627 interface) (setup)
  The paramaters include connection information to the database, Host compter name or IP and optional instance name, database name and optional user name and password. In addition, A unique per cache database profile name and the maximum number of records/readings stored.
• SIMPLEMSSQLDB (Simple MS Sql Database) - Also a database destination that creates a table for each server found. (setup)
  The paramaters include connection information to the database, Host compter name or IP and optional instance name, database name and optional user name and password.

SFTP -Simple File Transfer Protocal
FTP -File Transfer Protocal

Figure 1 - A graphic of the Dispatcher profile sources:

Figure 2 - A graphic of the Dispatcher profile targets:

EXAMPLE CONFIGURATIONS
For examples of how the Dispatcher and the Q13627 interface can be configured click here.

Window and Control Descriptions

At the top middle of the window you will see the Service name and Decsription of the server this UI allows you to configure.  It is possible to change the name and description of the service by opening the dispatcher.config file and changing the ServiceName and ServiceDisplayName properties.

• Figure 1
• Profile Setup Tab
• Add button - This will bring up the Add/Edit Profile window in a state that allows a new profile to be entered.
  
• Edit button - This will bring up the Add/Edit Profile window with the data from the profile that is selected in the profile grid.
  
• Remove button - This will remove the selected profile in the profile grid.
  
• Profile Grid - This shows each profile that has been added to this profile.

Figure 1 - The main window of the application showing the Profile Setup tab selected:

• Figure 2
• Logging Setup Tab
• Logging Path - This is the folder the log is stored in for this profile.  Each profile can have its own log folder and should to make it easier to tell which process the log is for also to prevent the possibility of two profiles sharing the same file.
  
• Keep Logs For - This will tell the Dispatcher how long (in days) to keep the lg file before deleting them.
  
• Verbosity - How much information is put into the log file.
  
• Save Settings - Clicking this button will save the data you just entered or changed.

Figure 2 - The Logging Setup tab:

• Figure 3
• Service Control Tab
• Status - indicated if t he the service running or stopped
  
• Start - Starts the service when its status is stopped
  
• Stop - Stops a service that status is running
  
• Restart - Stops then starts the service again

Figure 3 - The Service Control tab: