The WIMS login screen can prompt for the database server to use based on the following Hach_WIMS_Client.ini settings. Typically, these settings should not be used, however it can be useful for users that need to often switch between a production and test environment.
With Multi Server Support turned on the WIMS client login form displays a prompt for which server to use:
To setup Multi Server Support:
Edit your Hach_WIMS_Client.ini file and add the database connection settings:
MULTISERVER - Set to ON or YES to use multi server support
Sx_Name (Required) - The name or identifier of the x WIMS server. x is a number from 1 to 50 that links this name with the settings below. Can be any name you wish to use and will be shown in the Server pull down list on the login screen.
This settings informs the application which type of database is being connected to:
- ORACLE : HACHWIMS_CONNECTION_DBTYPE= 1
- Microsoft SQL : HACHWIMS_CONNECTION_DBTYPE= 2
This determines the OLEDB or Native Client Driver to be utilized by the application to communicate with the database:
- ORACLE : HACHWIMS_CONNECTION_PROVIDER= OraOLEDB.Oracle
- Microsoft SQL Server 2012, 2014, 2016, 2017 (SQL Native Client): HACHWIMS_CONNECTION_PROVIDER= SQLNCLI11
- Microsoft SQL Server 2005, 2008 (SQL Native Client): HACHWIMS_CONNECTION_PROVIDER= SQLNCLI
- Microsoft SQL Server 2000 (SQL OLEDB Driver): HACHWIMS_CONNECTION_PROVIDER= SQLOLEDB
This informs the application which database server or named instance is hosting the Hach WIMS Client database:
- ORACLE : HACHWIMS_CONNECTION_DATASOURCE= localhost:1521/XE
- Host/Server: localhost
- TCP/IP Port: 1521
- ORACLE 'DATABASE': XE
- Microsoft SQL : HACHWIMS_CONNECTION_DATASOURCE = IS021\OPSSQL
- Named Instance: OPSSQL
- Host/Server: IS021
Sx_HACHWIMS_CONNECTION_TIMEOUT (Optional. If not specified, value assumed to be 15)
This setting can be used to override the default database connection timeout of 15 seconds, which is how long the application will wait for a response when establishing a connection to the database. If the specific application is having trouble connecting to the database and a "time out" error is received, this setting could be increased to bypass the issue.
See 'Timeout Settings' below for more information
Sx_HACHWIMS_CONNECTION_COMMAND_TIMEOUT (Optional. If not specified, value assumed to be 30)
This setting can be used to override the default database command timeout, which specifies how long the application will wait for a response after sending a specific command or query to the database. If the application is getting a "command time out" error, this can help alleviate the situation:
- See 'Timeout Settings' below for more information
This setting is used under certain circumstances to customize how the application connects to the database.
The HACHWIMS_CONNECTION_TIMEOUT and HACHWIMS_CONNECTION_COMMAND_TIMEOUT settings can be set to pretty much anything you want and are measured in seconds. One important possible setting is 0 (zero). This means the application will wait indefinitely for the specified timeout condition. This is VERY DANGEROUS and should only be used by EXPERT USERS. Also, Hach Company does not recommend using settings above 60 (1 minute) unless absolutely necessary.
EXAMPLE Hach_WIMS_Client.ini with 2 servers setup: