Using the Hach WIMS Cimplicity SQL Collector to convert Cimplicity SQL data into OPSDATAXML files.

The Hach WIMS Indirect Cimplicity SQL Interface does not communicate directly with the Cimplicity SQL Server. Instead, a collector will connect to the database and convert the data into OPSDATAXML files. The Hach WIMS Indirect Server-Side Interface to Cimplicity SQL will then import data in these files into the Hach WIMS Client.

In the default installation, the Interface, Collector and Cimplicity SQL Server reside on the same machine. You may also configure the Collector and Cimplicity SQL Server to be on the same machine but have the Interface on another machine. If you do this, you'll want to make sure that the Collector is saving the OPSDATAXML files to a location that the machine the Interface is installed on has access to (i.e. a shared network drive).

To start the Collector from the Interface click on Configuration/Collector Configuration.

From here you can either configure the Collector or start it.

If you choose to start the Collector before it has been configured, you will be presented with a warning message indicating that it has not been configured yet. You can dismiss the message and proceed to configure the Collector.

The Collector will not start collecting data until it has been configured. In the configuration screen you have two tabs of configuration settings. The "General Settings" tab contains information on how you want the Collector to run.

The "Cimplicity SQL Connection" tab allows you to configure the connection to your Cimplicity SQL Server.

The "Data Table Mappings" tab allows you to select which tables and columns withing that table contain data.

The "Tag Picker" tab allows you select the tags you want to import into Hach WIMS.

When you launch the Collector it will either start as a Windows Tray Application (default) or in NT Service View and Control mode. The standard screen is below.

If the status bar shows "RUNNING" then the Collector is scheduled to run and collect data from the Cimplicity SQL Server. If the status is "PAUSED" you need to configure the connection to Cimplicity SQL and click the Start button. If no Tags have been defined yet, then the Collector will not run. If you start the Collector and it does not appear on the screen then you can find it in the Windows System Tray (by default the Collector is hidden when it is started unless errors occur during startup). You can double click on it's icon in the System Tray to make it visible.

If you click on the Configure button when the Collector is running as a Windows Tray Application you are presented with a Proxy Setting screen before being able to configure the Collector's settings.

The proxy screen contains needed information on how you plan to run the Collector. For a standard installation just leave the settings the way that they are

When the Collector is installed to run as a service you are presented with the following screen when starting the application.

From here you can see if the Service is running, configure it, stop it, start it, and view the activity log files.